Bug-hunters: They're coming outta the goddamn walls, aargh!
Security bods prep for more and more aliens bursting out of software
Regcast training : Hyper-V 3.0, VM high availability and disaster recovery
The organisation that administers the industry standard for classifying computer system security vulnerabilities wants to prepare its classification system for a world with an even greater number of bugs.
Mitre Corp is considering adding a 100 times more CVE (Common Vulnerabilities and Exposures) slots each year to accommodate bug reports.
The current syntax CVE-YYYY-NNNN supports up to 9,999 vulnerabilities. However the increasing number of software flaw reports means Mitre is considering extending this range up to 999,999.
In a call for public feedback explaining the proposed changes, Mitre explains that a system that only tracks 10,000 vulnerabilities or possible bugs is no longer enough. The move is due to be discussed at the upcoming RSA conference before a decision is made in early March.
Three options are on the table.
-
Option A (year + six digits, with leading 0s)
Examples: CVE-2014-000001, CVE-2014-009999, CVE-2014-123456
-
Option B (year + arbitrary digits, no leading 0s except in IDs 1 to 999)
Examples: CVE-2014-0001, CVE-2014-54321, CVE-2014-123456
-
Option C (year + arbitrary digits + check digit)
Examples: CVE-2014-1-8, CVE-2014-9999-3, CVE-2014-123456-5
Any change would only come into effect at the start of next year.
The greater volume of software applications out there is probably the greatest factor in annual bug count inflation but an increase in the number of security researchers looking for flaws as well as a growth in vulnerability reward programmes are also playing a role.
The absolute number of bugs varies but normally runs into the low thousands. The historic trend over many years is towards a greater number of bugs, hence a desire to rethink the numbering system. At the moment, it is only early February and we're already up to 462 CVEs this year already. Last year the total reached 5,373. ®
COMMENTS
Re: "Goddamn The Walls"
You guys are too quick to spot my screw-ups..
C.
Suggested sliding scale of IT security event categorizations
In inverse order by severity....
A) Use harsh language
B) Lay down suppressing fire with the incinerators while withdrawing
C) LET'S ROCK!!!!
D) We have 4 canisters of nerve gas, let's just roll em' in their and gas the whole joint!
E) Take off and nuke the site from orbit. It's the only way to be sure.
F) Game over, man!! Game over!!!
(Even with the paraphrasing, I've obviously seen "Aliens" a few too many times.)
Re: year + arbitrary digits + check digit
Check digits are useful if people are typing or reading the digits manually. A decent check digit will catch one or two mistakes in other digits.
Your debit or credit card includes a parity check - search online for the Luhn algorithm. Amongst other things, it means websites can check that you've typed it correctly before sending the number to the payment processing company.
IT infrastructure monitoring strategies
Agentless Backup is Not a Myth
Top 10 SIEM implementer’s checklist
Steps to Take Before Choosing a Business Continuity Partner
Requirements Checklist for Choosing a Cloud Backup and Recovery Service Provider
