2017, The Flood of CVEs
Last Updated: 2017-12-30 08:05:30 UTC
by Xavier Mertens (Version: 1)
2017 is almost done and it’s my last diary for this year. I made a quick review of my CVE database (I’m using a local cve-search instance). The first interesting number is the amount of CVE’s created this year. Do you remember when the format was CVE-YYYY-XXXX? The CVE ID format changed in 2014 to break the limit of 9999 entries per year. This was indeed a requirement when you see the number of entries for the last five years:
If more and more organisations are taking security into consideration, how to explain this peak of reported vulnerabilities? First, I think that, in parallel to organisations focusing on security, “attackers” are also more and more active. Not only bad guys who are always looking into ways to make more profit but also students and security researchers. In Europe, offensive security trainings are very popular. People like to learn how to “break stuff”. Also, there was a huge increase in bug bounty programs which motivate people to search for new vulnerabilities.
We also see new vendors that are not coming directly from the IT field but that make intensive use of these technologies. Some examples that received (at least) a CVE in 2017:
- Tesla - CVE-2016-9337
- Bavarian-Motor-Works (BMW) - CVE-2017-9212
- Miele (home appliances) - CVE-2017-7240
- GMV (ATMs) - https://www.cvedetails.com/cve/CVE-2017-6968/
Note: I did not even mention all products related to small IoT gadgets, industrial systems, etc.
Does this mean that the security of our products is worse? For many of them, I don’t think so. Most of those vulnerabilities have been fixed by vendors. This makes their products stronger. Let's think about this scenario: You're looking for a new "device" and you have the choice between two vendors. You have a look at the vulnerabilities associated with them. The first one has 10 CVEs and the second one only 2. Does it mean that the second one is better? Not necessarily, the first one might have a bug bounty program, can have a broader users bases (which means that more people are looking into its products). The most important is to check how they react when a vulnerability is reported to them. Do they fix quickly the vulnerability? Do they try to reduce the noise? To prosecute the researcher (sometimes)? Once the vulnerability has been fixed, the main problem remains the process of patching or updating the affected products!
Xavier Mertens (@xme)
ISC Handler - Freelance Security Consultant