News for hackers. Stuff that matters.
Re:Npm Audit: broken by design? by cratermoon on Wednesday July 07, 2021 @11:19AM (#27762100)
This kind of nonsense really goes back to the broken CVE process. https://opensourcesecurity.io/2021/03/30/its-time-to-fix-cve...

Linux kernel maintainer Greg Kroah-Hartman has a similar opinion. https://github.com/gregkh/presentation-cve-is-dead/blob/mast...

Edit: LWN mention https://lwn.net/Articles/801157/

Re:Npm Audit: broken by design? by zinekeller on Wednesday July 07, 2021 @11:32AM (#27762254)
The view of SQLite developers on CVEs is also dim: https://www.sqlite.org/cves.html
Re:Npm Audit: broken by design? by cratermoon on Wednesday July 07, 2021 @11:48AM (#27762428)
Beautifully succinct. This quote: "Grey-hat hackers are rewarded based on the number and severity of CVEs that they write. This results in a proliferation of CVEs that have minor impact, or no impact at all, but which make exaggerated impact claims." Alignment of incentives is messed up. Goodhart-Strathern's and Campbell's laws apply.
Re:Npm Audit: broken by design? by BeFlatXIII on Wednesday July 07, 2021 @02:54PM (#27764561)
Sounds like academic research publications. Sure, that will totally be a key step toward cancer therapy or better biofuels (realistically, the PI gets his jollies by shoving aldehyde groups onto random molecules)
Re:Npm Audit: broken by design? by cratermoon on Wednesday July 07, 2021 @09:09PM (#27767504)
Oh, you mean like the guys who tried to inject vulnerabilities into the linux kernel and got their entire university on Greg Kroah-Hartman's shit list? https://news.ycombinator.com/item?id=26887670
Re:Npm Audit: broken by design? by randomswede on Thursday July 08, 2021 @02:22AM (#27768941)
That sounds better than a PI that gets their jollies by shoving nitro groups into unsuspecting organic molecules.

Although I still have a deep admiration for the Klapötke "Energetic Materials" group at Munich Uni.

Re:Npm Audit: broken by design? by G3rn0ti on Wednesday July 07, 2021 @12:30PM (#27762951)
Maybe then writing and submitting a CVE should cost some money that’s payed back together with the reward if the vulnerability is found to be „reasonable“ upon review?
Re:Npm Audit: broken by design? by cratermoon on Wednesday July 07, 2021 @12:51PM (#27763207)
I'm always suspicious of just throwing money at a problem, particularly in things like open source where money isn't always the motivator and can often be a corrupting influence. In some cases this will reduce the ability of genuinely well-intentioned people to participate, simply because they don't have the money up front, and for well-funded organizations the money would have to be quite a lot.

I'd like to ask what, other than money directly motivates people? Is it prestige? A line on their resume? A requirement for a bootcamp class? In addition, we should re-evaluate the difficulty of submitting a CVE. Is it too easy? The story about a mass of "hey your regex parser could choke on this weird expression[1]" reports suggest that perhaps so. What can we do to make it so that CVEs and equivalents are truly meaningful? Also, just the fact that CVE reports are given a great deal of respect could be the problem, although at this point that seems to be self-correcting.

[1] Some classes of regex parsers are known to be vulnerable by nature, those that do backtracking for example, because their worst-case runtime grows exponentially and can run in unbounded time. This has been known since at least 2009. There are other implementations with better worst-case runtimes, but worse performance in typical cases. The fact that it's trivially easy to look at a regex parser to see if it does backtracking and construct an "evil" expression that breaks it means it's trivially easy to file a DOS report against any such parser.

Re:Npm Audit: broken by design? by smsm42 on Wednesday July 07, 2021 @01:02PM (#27763340)
AFAIK MITRE has a process for an organization to register as vendor, and then it would accept CVEs for their products only from the vendor, not from random people. Of course this has an opposite failure mode that may have unscrupulous vendors hide issues or just be lazy in issuing CVEs for existing bugs, but it eliminates the problem of random people issuing a ton of CVEs for non-issue bugs.
Re:Npm Audit: broken by design? by cratermoon on Wednesday July 07, 2021 @02:02PM (#27764012)
I'm pretty sure CVEs and the like came about because vendors were choosing to hide or deny security vulnerabilities. Vulnerability disclosure policies are a whole different kettle of worms.
Re:Npm Audit: broken by design? by trey-jones on Wednesday July 07, 2021 @12:43PM (#27763114)
Maybe, but you risk swinging too far in the opposite direction into under-reporting of vulnerabilities.
Re:Npm Audit: broken by design? by px43 on Wednesday July 07, 2021 @02:54PM (#27764569)
Believe me, 90% of people who find bugs for a living are perfectly content with keeping them to themselves and/or selling them privately.
Re:Npm Audit: broken by design? by twistedpair on Wednesday July 07, 2021 @03:20PM (#27764809)
I had a researcher contact me about a "vuln" in an OSS effort of mine once. The vuln made no sense w/ how the tool was used, but they published and I earned a CVE scarlet letter nonetheless. I finally "fixed" it, but IMHO, nothing was ever broken or vulnerable.
Re:Npm Audit: broken by design? by jrockway on Wednesday July 07, 2021 @05:24PM (#27765883)
I wouldn't call a CVE a scarlet letter. Given the current state of software engineering, it's more like "my project is valuable enough to be used by someone that cares about security". You fixed it, one less bug to worry about. No doubt there are many less popular products with many worse vulnerabilities that don't have a CVE.

Even OpenBSD had to change their tagline to "Only two remote holes in the default install, in a heck of a long time!" (from "Five years without a remote hole in the default install!") Still a pretty impressive track record.

Re:Npm Audit: broken by design? by DaiPlusPlus on Wednesday July 07, 2021 @06:31PM (#27766507)
> You fixed it, one less bug to worry about.

Those "bugs" can be features though - or the work involved to fix the bug meant that high-impact feature work - or other bugfixes, had to be postponed or even cancelled.

Our SaaS frequently gets security "researchers" (read: people running online scanners) submitting emails through our contact-form informing us about click-jacking attacks on our login-page - the problem for us is that we have a lot of second-party and third-party integrations on unbounded origins that offer access to our application, and by extension our login-screen through an <iframe> on their own origin, which is sometimes even an on-prem LAN web-server accessed through embedded devices where we can't use popups to do it properly - let alone switch to a more robust OIDC system - so there is no easy solution that makes the "I ran a tool, gimme $100" people go-away without causing a much bigger problem to now exist.

Re:Npm Audit: broken by design? by jrockway on Wednesday July 07, 2021 @06:48PM (#27766647)
> there is no easy solution that makes the "I ran a tool, gimme $100" people go-away

I use the "mark as spam" button :)

Re:Npm Audit: broken by design? by staticassertion on Wednesday July 07, 2021 @06:51PM (#27766668)
> so there is no easy solution that makes the "I ran a tool, gimme $100" people go-away without causing a much bigger problem to now exist.

Maybe consider setting up a free-tier HackerOne bounty program? I think they triage to some degree on your behalf.

Re:Npm Audit: broken by design? by thaumasiotes on Wednesday July 07, 2021 @10:35PM (#27767955)
In the free tier? Triage is a paid service.
Re:Npm Audit: broken by design? by apayan on Wednesday July 07, 2021 @02:46PM (#27764468)
Here's the video of the talk that goes with Greg Kroah-Hartman's slides: https://www.youtube.com/watch?v=HeeoTE9jLjM
Re:Npm Audit: broken by design? by Tomte on Thursday July 08, 2021 @02:19AM (#27768922)
CVEs can be used to try and extort OSS maintainers into expensive consulting gigs: https://www.patreon.com/posts/unfixed-security-21250652
Re:Npm Audit: broken by design? by staticassertion on Wednesday July 07, 2021 @06:50PM (#27766662)
I wouldn't take Greg's opinions on security too seriously.

Spender has a much more nuanced, informed view. I think it covers the issues of the CVE process well, but doesn't make the same mistakes that Greg does.

https://www.grsecurity.com/reports_of_cves_death_greatly_exa...