@attritionorg Are you looking for # of CVEs per year?
-
-
-
@justin_foster If they are the totals from any year before 2010. e.g. The total of CVEs per year, generated off today's data != good -
@attritionorg CVEs 2005 - 4,811 2006 - 7,320 2007 - 6,602 2008 - 7,139 2009 - 4,904 2010 - 7,709 2011 - 3,452 (It has slowed) -
@justin_foster when was that data generated? if today, not what i need. -
@attritionorg Based on the CVE's in the DB in Jan last year. Each year is year start to end no offset -
@justin_foster cite your source please? Jan 2012 CVE totals is helpful. Older even better... -
@attritionorg Based on the year-by-year XML dumps from Mitre with a custom parser Jan 2012. I don't have data earlier -
@justin_foster excellent, that is helpful =) wonder if we can get previous dumps... checked http://bit.ly/Mc9oa ?
End of conversation
New conversation -
-
-
@attritionorg I might still have the raw data gathered in 2005/06 used for the paper http://bit.ly/Wr7uuA - Interested? -
@stefan_frei absolutely, especially if you have it for cve, osvdb, etc -
@attritionorg I will check my archive when back home in 10d. Let you know what I find -
@stefan_frei appreciate it!
End of conversation
New conversation -
-
-
@attritionorg didn't BUGTRAQ keep records like that for many years? -
@epigrammaticus probably. historic BID totals would be great. only found last couple of years via Symantec reports
End of conversation
New conversation -
-
-
@attritionorg have you checked http://www.cert.org/stats/#vuls ? Not much info, but some... -
@infoseconlinept got CERT covered yes. thanks
End of conversation
New conversation -
-
-
@attritionorg I believe I have an old CSI/FBI. Can send to Jericho if interested. -
@mtezna If they have CERT data, got that covered I think -
@attritionorg OK. I'll take a peek in the morning. If its not, will send.
End of conversation
New conversation -
-
-
@attritionorg I can help you. Privmsg me an email address.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.