Tag security

To keep the modern technological world of open source software safe, it is critical to efficiently and accurately communicate information about open source vulnerabilities. The OSV Schema, created through the collaboration between OpenSSF members and housed within the Vulnerability Disclosures Working Group, provides a minimal, easy-to-use first class JSON format for describing vulnerabilities in open source software.

How to verifiably link npm packages to their source repository and build instructions.

Software engineer and artist

OK, let's debate a definition. Today, let's talk about "vulnerability" in software. Your product, (let's call it A) uses a library (which we'll call X). X has a load of features. Among those is some function, "someFunc" which has a bug. It's supposed to be safe to call with untrusted data... but some clever researchers have found that they can craft input that results in remote code execution (RCE). X has a vulnerability. Does A?

Attached: 1 image The rumours of security being a paid feature on Twitter is true. Fucking hell.

Your two-factor authentication code is: 9 DO NOT SHARE THIS CODE WITH ANYONE.

A question for #infosec practitioners. I've found an abandoned AWS bucket from a very large company. It serves all the images & fonts in their billing emails. I defensively registered it to prevent an attacker from injecting malicious content into the emails I receive. Then I emailed their security.txt contact to inform them and offering to transfer it back (for free, obviously). Was that the right thing to do? Should I have waited for a response from them before securing the bucket?

I just wrote the following on a GitHub issue. I don't understand why people have not learned this yet: ⚠️ NEVER SEND POTENTIAL SECURITY ISSUES PUBLICLY. If the security issue is concrete, it also poses all the users at risk because the maintainers might not have time to act.

Matteo Collina (@matteocollina)Tue, 27 Dec 2022 17:04 GMT

The massive push for software supply-chain integrity and transparency has left organizations struggling to secure their pipelines and manage vulnerabilities. Existing tooling doesn’t support supply chain security natively and requires users to bolt on critical features like signatures, provenance, and software bills of material (SBOM). Everything you need to know about securing the software supply chain.

The story of how I could steal credentials on Infosec Mastodon with a HTML injection vulnerability, without needing to bypass CSP. Everybody on our Twitter feed seemed to be jumping ship to the infose

Infosys has a lot to say about security You can check out their website for a lot of buzwords , but it’s clear from all the stock photos that they take security Very Seriously Indeed ™️. However, from what I’ve found recently, it seems that Infosys use the following Comprehensive Management-Endorsed Proficiently Driven Cybersecurity Strategy and Framework items: Don’t use AWS roles or temporary credentials for your developers Instead, use IAM user keys and give them all FullAdminAccess permissions Never rotate these keys and store them as plaintext in git Use these keys to protect what appears to be medical data about COVID patients Have someone publish those keys and the code in a public package to pypi Keep those keys active for days after leakage Make nonsensical pull requests to try and remove all references to the leak The Leak This morning I woke up to a very strange pull request on my pypi-data project.

Public listings have made sensitive data searchable due to misconfigured third-party services

14 comments

Many of us use one-time passwords (OTP) regularly to log into different services. Most probably rely on Google Authenticator and similar tools. But what about building one by ourselves?

Announcing vulnerability management for Go, to help developers learn about known vulnerabilities in their dependencies.

The other day someone claimed a hostname on a domain I own and it took me a while to track down how. After a lot of digging around, trying to figure out how the hijack was accomplished, it turns out it was via GitHub Pages.

A tool for securing CI/CD workflows with version pinning. - GitHub - sethvargo/ratchet: A tool for securing CI/CD workflows with version pinning.

1. Buy expired NPM maintainer email domains. 2. Re-create maintainer emails 3. Take over packages 4. Submit legitimate security patches that include package.json version bumps to malicious dependency you pushed 5. Enjoy world domination.

Lance R. Vick ( @lrvick@mastodon.social ) (@lrvick)Mon, 09 May 2022 21:20 +0000

*sigh* 🥃

Jason Kikta 🌻 (@kikta)Mon, 09 May 2022 17:29 +0000

https://twitter.com/GitHubSecurity/status/1515101093419646976

If you need to verify the ID of the OAuth application, check the number at the end of the url like github.com/orgs/<org>/policies/applications/145909 coming from the github.com/organizations/<org>/settings/oauth_application_policy page.

chrismo (@the_chrismo)Sat, 16 Apr 2022 02:42 +0000

spent way too long making this

Alex Strook ⚡🐭 (@AlexStrook)Wed, 13 Apr 2022 16:12 +0000

Setup some MFA stuff last night and the amount of this is so annoying:

Matt Brunt (@Brunty)Wed, 13 Apr 2022 08:00 +0000

🧠 Reminder that "beefstew" is not a good password. It is not Str0g4|\|off

Chris Heilmann (@codepo8)Tue, 05 Apr 2022 08:57 +0000

My bank: 🏦: I need you to jump through security hurdles to keep your money safe. Me: 🙋‍♀️: No problem! Cybersecurity is a process, not a destination! Also My Bank: 🏦: Whoa, whoa, whoa. 21 digit password? Let's not get crazy. Also, I have never seen the character "&" in my life.

Brianna Wu (@BriannaWu)Tue, 29 Mar 2022 14:59 +0000

Wow, @Zoom's decision to bypass the security settings of their customers in order to boost its marketplace demand is a bold move, to put it mildly. CISOs discovering this after the fact will be fuming.

Tobie Langel (@tobie)Mon, 28 Mar 2022 08:33 +0000

Since #Log4j you've heard how OSS vulns impact most orgs, how OSS is underfunded & we need to do more to help, but did you know OSS security has improved drastically in the last 4 years? In 2017, 35% of OSS libs used had a known flaw. In 2022 it's < 10% veracode.com/state-of-softw…

Chris Wysopal (@WeldPond)Wed, 09 Feb 2022 19:36 GMT

Eight years later, and this is now a thing 😃 gov.uk/security.txt No monetary reward (sadly, but I get why).

Post details

Should GOV.UK Run A Bug Bounty? shkspr.mobi/blog/?p=9760

Terence Eden (@edent)Tue, 04 Feb 2014 12:05 GMT

Terence Eden (@edent)Fri, 04 Feb 2022 07:43 GMT

Federal government memo: "Consistent with the practices outlined in SP 800-63B, agencies must remove password policies that require special characters and regular password rotation from all systems within one year of the issuance of this memorandum." Yes!

Post details

The federal government just dropped a 29-pg memo laying out its "transition to a zero trust approach" A few surprises: ✴️ there's more in it than just zero-trust ✴️ it goes beyond what most orgs do today I read the whole thing so you don't have to... bastionzero.com/blog/i-read-th…

Sharon Goldberg (@goldbe)Thu, 27 Jan 2022 14:52 GMT

Simon Willison (@simonw)Thu, 27 Jan 2022 19:21 GMT

Please do not teach the computers how to recognize us even with most of our facial features covered.

Post details

iOS 15.4 beta has a new ‘Use Face ID with a Mask’ option and the masked FaceID icon is absolutely adorable.

Sebastiaan de With (@sdw)Thu, 27 Jan 2022 19:38 GMT

Renaissance Mandalorian (@indik)Fri, 28 Jan 2022 03:42 GMT