Cybersecurity

5751 readers

482 users here now

c/cybersecurity is a community centered on the cybersecurity and information security profession. You can come here to discuss news, post something interesting, or just chat with others.

THE RULES

Instance Rules

Be respectful. Everyone should feel welcome here.
No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia.
No Ads / Spamming.
No pornography.

Community Rules

Idk, keep it semi-professional?
Nothing illegal. We're all ethical here.
Rules will be added/redefined as necessary.

If you ask someone to hack your "friends" socials you're just going to get banned so don't do that.

Learn about hacking

Hack the Box

Try Hack Me

Pico Capture the flag

Other security-related communities !databreaches@lemmy.zip !netsec@lemmy.world !cybersecurity@lemmy.capebreton.social !securitynews@infosec.pub !netsec@links.hackliberty.org !cybersecurity@infosec.pub !pulse_of_truth@infosec.pub

Notable mention to !cybersecuritymemes@lemmy.world

founded 1 year ago

MODERATORS

kid@sh.itjust.works

Lanky_Pomegranate530@midwest.social

Holes in Your Bitbucket: Why Your CI/CD Pipeline Is Leaking Secrets (cloud.google.com)

submitted 6 months ago by kid@sh.itjust.works to c/cybersecurity@sh.itjust.works

1 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] chamomile@furry.engineer 6 points 6 months ago

@kid TL;DR: If you have a secret variable in your CI/CD pipeline and it's written to a file that subsequently gets artifacted, anyone who can access that artifact can also read your secret variable.

Feels like a "no shit" moment but I guess I can see how someone could make this mistake in a more complicated setup than the example in the blog.