Tag: CVE

  • Rebuttal: Dark Reading’s “9” Sources for Tracking New Vulnerabilities

    Rebuttal: Dark Reading’s “9” Sources for Tracking New Vulnerabilities

    [This was originally published on the OSVDB blog.] Earlier today, Sean Martin published an article on Dark Reading titled “9 Sources For Tracking New Vulnerabilities“. Spanning 10 pages, likely for extra ad revenue, the sub-title reads: Keeping up with the latest vulnerabilities — especially in the context of the latest threats — can be a…

  • Response to Kenna Security’s Explanation of the DBIR Vulnerability Mess

    Response to Kenna Security’s Explanation of the DBIR Vulnerability Mess

    [This was originally published on the OSVDB blog.] Earlier this week, Michael Roytman of Kenna Security wrote a blog with more details about the vulnerability section of the Verizon DBIR report, partially in response to my last blog here questioning how some of the data was generated and the conclusions put forth. The one real…

  • A Note on the Verizon DBIR 2016 Vulnerabilities Claims

    A Note on the Verizon DBIR 2016 Vulnerabilities Claims

    [This was originally published on the OSVDB blog.] [Updated 4/28/2016] Verizon released their yearly Data Breach Investigations Report (DBIR) and it wasn’t too long before I started getting asked about their “Vulnerabilities” section (page 13). After bringing up some highly questionable points about last year’s report regarding vulnerabilities, several people felt that the report did…

  • MITRE’s Horrible New CVE ID Scheme and Spindoctoring

    MITRE’s Horrible New CVE ID Scheme and Spindoctoring

    [This was originally published on the OSVDB blog.] Today, The Register wrote an article on MITRE’s announcement of a new CVE ID scheme, and got many things wrong about the situation. As I began to write out the errata in an email, someone asked that I make it public so they could learn from the…

  • Our New Year Vulnerability “Trends” Prediction!

    Our New Year Vulnerability “Trends” Prediction!

    [This was originally published on RiskBasedSecurity.com.] Shortly after a year closes out, the industry is treated to dozens of security companies that want to tell you all about vulnerability totals and trends from the previous year. In many cases, the companies offering the predictions are armchair experts of a sorts, who do not aggregate vulnerability…

  • Ruminations on David Weinstein’s “Ruminations on App CVEs”

    Ruminations on David Weinstein’s “Ruminations on App CVEs”

    [This was originally published on the OSVDB blog.] David Weinstein, a researcher at NowSecure, has posted a blog titled “Ruminations on App CVEs“. Thanks to Will Dormann’s Tweet it came to our attention, and he is correct! We have opinions on this. Quoted material below is from Weinstein’s blog unless otherwise attributed. CVE is well-positioned…

  • CVE/NVD: The High Price of ‘Free’

    CVE/NVD: The High Price of ‘Free’

    [This was originally published for RiskBasedSecurity.com. I can’t find the original on archive.org and this was written too long ago to have access to the original Google Doc.] Vulnerability Intelligence (VI) is not a new offering by any stretch of the imagination. However, in the past few years VI has gained more attention and become…

  • A Note on the Verizon DBIR 2015, “Incident Counting”, and VDBs

    A Note on the Verizon DBIR 2015, “Incident Counting”, and VDBs

    [This was originally published on the OSVDB blog.] Recently, the Verizon 2015 Data Breach Investigations Report (DBIR) was released to much fanfare as usual, prompting a variety of media outlets to analyze the analysis. A few days after the release, I caught a Tweet linking to a blog from Rory McCune that challenged one aspect…

  • Reviewing the Secunia 2015 Vulnerability Review (A Redux)

    Reviewing the Secunia 2015 Vulnerability Review (A Redux)

    It’s that time of year again! Vulnerability databases whip up reports touting statistics and observations based on their last year of collecting data. It’s understandable, especially for a commercial database, to show why your data source is the best. In the past, we haven’t had a strong desire to whip up a flashy PDF with…

  • We’re “critical”, not “immature”.

    We’re “critical”, not “immature”.

    [This was originally published on the OSVDB blog.] Recently, we got feedback via Twitter that we come across as “immature”. On the surface, perhaps. Not all of our Tweets are critical of CVE though. I replied pretty quickly that said criticism is also us “pushing for them to improve since so much of the industry…