Stories
Slash Boxes
Comments

SoylentNews is people

posted by Fnord666 on Thursday February 28 2019, @02:55PM   Printer-friendly
from the hello-entropy dept.

The National Vulnerability Database (NVD) is a US government-funded resource that does exactly what the name implies-acts as a database of vulnerabilities in software. It operates as a superset of the Common Vulnerabilities and Exposures (CVE) system, operated by the non-profit Mitre Corporation, with additional government funding. For years, it has been good enough—while any organization or process has room to be made more efficient, curating a database of software vulnerabilities reported through crowdsourcing is a challenging undertaking.

Risk Based Security, the private operator of competing database VulnDB, aired their grievances with the public CVE/NVD system in their 2018 Vulnerability Trends report, released Wednesday, with charged conclusions including "there is fertile grounds for attorneys and regulators to argue negligence if CVE/NVD is the only source of vulnerability intelligence being used by your organization," and "organizations are getting late and at times unreliable vulnerability information from these two sources, along with significant gaps in coverage." This criticism is neither imaginative, nor unexpected from a privately-owned competitor attempting to justify their product.

In fairness to Risk Based Security, there is a known time delay in CVSS scoring, though they overstate the severity of the problem, as an (empirical) research report finds that "there is no reason to suspect that information for severe vulnerabilities would tend to arrive later (or earlier) than information for mundane vulnerabilities."

https://www.techrepublic.com/article/software-vulnerabilities-are-becoming-more-numerous-less-understood/


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 0) by Anonymous Coward on Thursday February 28 2019, @07:58PM (2 children)

    by Anonymous Coward on Thursday February 28 2019, @07:58PM (#808323)

    "Hello World" in Rust clocks in at 2MB. A huge attack surface. In my dictionary if Hello World goes over a few hundred bytes as a compiled executable, it is bloatware.
    Today much of the programming is glueing together large pre-made components or painting on top of a framework. The devs know the API, but have little to no information on the (often proprietary) base system - and that is where all the complexity and potential for bugs lives. Often these "higher" "safe" languages compile down to C or their runtimes were written in C, making them only as "safe" as the skills of the implementer.

  • (Score: 0) by Anonymous Coward on Thursday February 28 2019, @08:00PM

    by Anonymous Coward on Thursday February 28 2019, @08:00PM (#808325)

    But Rust is the safest, most perfect, and most loved programming language.

  • (Score: 2) by DannyB on Thursday February 28 2019, @09:29PM

    by DannyB (5839) Subscriber Badge on Thursday February 28 2019, @09:29PM (#808377) Journal

    I had no idea. I don't use Rust.

    Any idea why? Does it statically link a lot of unneeded library into the executable?

    I don't know what a "Hello World" in Java clocks in at, disk space wise. But I know that the new ZGC or Red Hat's new Shenandoah GC can handle Terabytes of heap, yes really, with 10 ms pause times -- so the Hello World should run efficiently!

    --
    The lower I set my standards the more accomplishments I have.