Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

ABTV

11/29/2019
10:05 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

The Top 25 Most Dangerous Software Errors

'Improper Restriction of Operations within the Bounds of a Memory Buffer' tops this year's list.

The Common Weakness Enumeration (CWE) Top 25 Most Dangerous Software Errors (CWE Top 25) is a list of what has been judged to be the most widespread and critical weaknesses that can lead to serious vulnerabilities in software. These kinds of weaknesses are often easy to find and exploit. They can be dangerous because they can frequently allow threat actors to completely take over execution of software, steal data, or prevent the software from working.

MITRE is saying that this current list is data driven in how it has been approached; using Common Vulnerabilities and Exposures (CVE) data and related CWE mappings that are found within the National Institute of Standards and Technology (NIST) National Vulnerability Database (NVD), as well as the Common Vulnerability Scoring System (CVSS) scores associated with each of the CVEs. A scoring formula was then applied by MITRE to determine the level of prevalence and danger each weakness presents.

At the time of the last list compilation eight years ago, the top spot of the list was taken by SQL injection techniques. The 2011 list was constructed by a different method; from surveys conducted of developers, top security analysts, researchers and vendors. It involved some subjectivity on the part of those surveyed.

But this year, it's "Improper Restriction of Operations within the Bounds of a Memory Buffer" as top dog which shows the changes that have happened to the list. The current top spot is a class level of wide-ranging errors, not one bugaboo. The data-driven approach to generating the list gave rise to solidifying root causes of multiple vulnerabilities into one class-level description.

The 2019 CWE Top 25 leverages NVD data from the years 2017 and 2018, which consisted of approximately 25,000 CVEs. The scoring formula combines the frequency that a CWE is the root cause of a vulnerability with the projected severity of its exploitation. In both cases, the frequency and severity are normalized relative to the minimum and maximum values seen.

So, what kinds of problems will not show up in the list? Weaknesses that are rarely exploited will not receive a high score, regardless of the typical severity associated with any exploitation. Weaknesses with a low impact will not receive a high score, which makes sense. It makes sense that weaknesses that are both common and can cause harm should receive a high score.

The methodology does have limitations. This approach to the list only uses data that was publicly reported and captured in NVD, and there are numerous vulnerabilities exist that do not have CVE IDs. Vulnerabilities which are not included in NVD will be excluded from this approach. The authors of the list also admit that it indirectly prioritizes implementation flaws over design flaws, due to their prevalence within individual software packages.

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Cloud Security Threats for 2021
Or Azarzar, CTO & Co-Founder of Lightspin,  12/3/2020
Why Vulnerable Code Is Shipped Knowingly
Chris Eng, Chief Research Officer, Veracode,  11/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Assessing Cybersecurity Risk in Todays Enterprises
Assessing Cybersecurity Risk in Todays Enterprises
COVID-19 has created a new IT paradigm in the enterprise and a new level of cybersecurity risk. This report offers a look at how enterprises are assessing and managing cyber-risk under the new normal.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-27772
PUBLISHED: 2020-12-04
A flaw was found in ImageMagick in coders/bmp.c. An attacker who submits a crafted file that is processed by ImageMagick could trigger undefined behavior in the form of values outside the range of type `unsigned int`. This would most likely lead to an impact to application availability, but could po...
CVE-2020-27773
PUBLISHED: 2020-12-04
A flaw was found in ImageMagick in MagickCore/gem-private.h. An attacker who submits a crafted file that is processed by ImageMagick could trigger undefined behavior in the form of values outside the range of type `unsigned char` or division by zero. This would most likely lead to an impact to appli...
CVE-2020-28950
PUBLISHED: 2020-12-04
The installer of Kaspersky Anti-Ransomware Tool (KART) prior to KART 4.0 Patch C was vulnerable to a DLL hijacking attack that allowed an attacker to elevate privileges during installation process.
CVE-2020-27774
PUBLISHED: 2020-12-04
A flaw was found in ImageMagick in MagickCore/statistic.c. An attacker who submits a crafted file that is processed by ImageMagick could trigger undefined behavior in the form of a too large shift for 64-bit type `ssize_t`. This would most likely lead to an impact to application availability, but co...
CVE-2020-27775
PUBLISHED: 2020-12-04
A flaw was found in ImageMagick in MagickCore/quantum.h. An attacker who submits a crafted file that is processed by ImageMagick could trigger undefined behavior in the form of values outside the range of type unsigned char. This would most likely lead to an impact to application availability, but c...