Risk
6/27/2011
03:07 PM
Connect Directly
Twitter
RSS
E-Mail
100%
0%

Feds Identify Top 25 Software Vulnerabilities

Department of Homeland Security worked with non-profits and the private sector to come up with a list of the most worrisome threats and how organizations can mitigate them.

Inside DHS' Classified Cyber-Coordination Headquarters
(click image for larger view)
Slideshow: Inside DHS' Classified Cyber-Coordination Headquarters
The Department of Homeland Security on Monday announced detailed guidance for how software companies and others writing code can avoid the most widespread and serious vulnerabilities in software.

Working with technology research non-profit Mitre and security training organization the SANS Instittute, as well as a number of private sector organizations from Apple to Oracle, DHS' National Cyber Security Division drew up a list of software vulnerabilities called the Common Weakness Enumeration, developed a scoring system and risk analysis framework for evaluating the seriousness of the flaws and prioritizing the weaknesses, and released a top 25 list of the most dangerous software errors.

The list includes high-level overviews and examples of each of the vulnerabilities, common consequences of the problem, likely modes of detection and attack, and potential mitigations for each type of attack at various steps in the software development process.

Initiative leaders anticipate that the Common Weakness Enumeration, top 25 list, and scoring system will let users compare weaknesses, educate themselves, and prioritize their security efforts. This isn't the first release of the top 25 list or of the Common Weakness Enumeration, but is the first one to take as detailed and data-intensive look at the vulnerabilities, thus making it significantly more useful than previous versions, initiative leaders said on a conference call about the effort.

"This will allow agencies and organizations to take a tactical approach to addressing vulnerabilities." Will Pelgrin, director of the Multi-State Information Sharing and Analysis Center, a collaborative cybersecurity effort that includes state and local governments, said on the call. "I see this as a management tool to focus the team on things that are the greatest threat and that have the greatest consequences."

Atop this year's list are SQL injection flaws, which are the most serious due to their common nature and the ease and frequency of exploit online. Other top vulnerabilities include operating system command injection, classic buffer overflow, and cross-site scripting.

The effort is exemplary of the increasing frequency with which DHS is collaborating with the private sector on cybersecurity efforts. In addition to this initiative, for example, DHS' National Cybersecurity and Communications Integration Center has private sector reps working side by side with feds to uncover and address vulnerabilities in their systems, and the IT sector has worked on a major risk assessment effort with DHS.

"Whether you call it partnership or collaboration, the relationship between the government and the private sector has been on the increase," Joe Jarzombek, director for software assurance at the National Cyber Security Division, said on the call.

The scoring system takes into consideration the potential technical and business impacts of exploited weaknesses, the operational layer to which the attacker might gain access (i.e. application-level versus, say, network-level), the effectiveness of available mitigating controls, the privilege level needed to access the vulnerability, the likelihood of discovery and exploit of the weakness, and more.

What industry can teach government about IT innovation and efficiency. Also in the new, all-digital issue of InformationWeek Government: Federal agencies have to shift from annual IT security assessments to continuous monitoring of their risks. Download it now. (Free registration required.)

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-9710
Published: 2015-05-27
The Btrfs implementation in the Linux kernel before 3.19 does not ensure that the visible xattr state is consistent with a requested replacement, which allows local users to bypass intended ACL settings and gain privileges via standard filesystem operations (1) during an xattr-replacement time windo...

CVE-2014-9715
Published: 2015-05-27
include/net/netfilter/nf_conntrack_extend.h in the netfilter subsystem in the Linux kernel before 3.14.5 uses an insufficiently large data type for certain extension data, which allows local users to cause a denial of service (NULL pointer dereference and OOPS) via outbound network traffic that trig...

CVE-2015-2666
Published: 2015-05-27
Stack-based buffer overflow in the get_matching_model_microcode function in arch/x86/kernel/cpu/microcode/intel_early.c in the Linux kernel before 4.0 allows context-dependent attackers to gain privileges by constructing a crafted microcode header and leveraging root privileges for write access to t...

CVE-2015-2830
Published: 2015-05-27
arch/x86/kernel/entry_64.S in the Linux kernel before 3.19.2 does not prevent the TS_COMPAT flag from reaching a user-mode task, which might allow local users to bypass the seccomp or audit protection mechanism via a crafted application that uses the (1) fork or (2) close system call, as demonstrate...

CVE-2015-2922
Published: 2015-05-27
The ndisc_router_discovery function in net/ipv6/ndisc.c in the Neighbor Discovery (ND) protocol implementation in the IPv6 stack in the Linux kernel before 3.19.6 allows remote attackers to reconfigure a hop-limit setting via a small hop_limit value in a Router Advertisement (RA) message.

Dark Reading Radio
Archived Dark Reading Radio
After a serious cybersecurity incident, everyone will be looking to you for answers -- but you’ll never have complete information and you’ll never have enough time. So in those heated moments, when a business is on the brink of collapse, how will you and the rest of the board room executives respond?