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.

Vulnerabilities / Threats //

Vulnerability Management

11:50 AM

CISA Joins MITRE to Issue Vulnerability Identifiers

The Cybersecurity and Infrastructure Security Agency will become a peer of MITRE in the CVE program, likely leading to continued increases in disclosed vulnerabilities.

The US Department of Homeland Security's Cybersecurity and Infrastructure Agency (CISA) has taken over responsibility for assigning Common Vulnerability Enumeration (CVE) identifiers for software vulnerabilities in two specific industries — medical devices and industrial control systems — as part of a planned expansion in the number of organizations managing vulnerability information, according to CISA and government contractor MITRE.

Related Content:

MITRE Releases 2019 List of Top 25 Software Weaknesses

Special Report: Computing's New Normal, a Dark Reading Perspective

New on The Edge: 5 Security Lessons Humans Can Learn From Their Dogs

CISA, which informs and manages cybersecurity risk for the United States, will become a so-called "root-level CVE Number Authority (CNA)," initially managing seven different organizations: Alias Robotics, ABB, [email protected], Gallagher Group, Johnson Controls, Robert Bosch, and Siemens. Each of the organizations issue CVEs for their own products — or, in the case of [email protected], a German technical organization, for the group's partners in the automation industry — but CISA will oversee the program and expanding membership among those industries. 

The addition of CISA marks the first time MITRE has "a peer organization within the program," says Chris Levendis, CVE Program board member and a principal systems engineer at MITRE. 

"They will have the same responsibilities as the MITRE CNA," he says. "They are responsible, for example, for recruiting and onboarding new CNAs within their ICS and medical device scope, ensuring retail assignment of CVE IDs within their scope, adjudicating disputes within their scope, [and] participating in program working groups ... They are responsible for ensuring coordinated and responsible vulnerability disclosure within their scope."

Both CISA and MITRE's root-level groups will report to the board managing the CVE program, according to the Sept. 15 announcement. While Japan's Computer Emergency Response Team (JP-CERT) is currently designated as a root-level CVE Numbering Authority (CNA), the group does not currently manage any other subsidiary CNAs, according to MITRE. 

"Continuing to encourage public and transparent disclosure of industrial control systems and medical device vulnerabilities is a critical mission for CISA," said Bryan Ware, assistant director for cybersecurity at CISA, in a statement. "This expansion will encourage more vendors to participate in the CVE program and allow CISA to better support stakeholders as they become more engaged."

The addition of CISA continues MITRE's efforts to increase participation in the CVE program following a problematic period between 2014 and 2016 that led to process breakdowns and increasing delays in the assignation of CVE identifiers to vulnerabilities. The CVE program adopted a federated management approach that expanded the number of CNAs from less than two dozen in 2016 to 139 as of Sept. 16. Partly as a result, the number of documented vulnerabilities has nearly tripled from less than 6,500 in 2016 to more than 17,300 last year.

MITRE continues to work to expand the program, Levendis says.

"The goal of the CVE program is to scale the program through its federated growth strategy," he says. "The CVE program intends to add more root CNAs as willing participants are identified. This enables federated and distributed governance and operation of the CVE program by an engaged community of stakeholders."

In the past year alone, the CVE program has added as CVE Numbering Authorities a variety of companies that manage significant repositories of code. Both GitHub and Gitlab — which host code for a large number of open source projects and private software repositories — became CNAs this year, for example.  

The addition of a managing CNA for the medical devices and industrial control system (ICS) industries should result in more coverage of software in those sectors and, as a result, a greater number of vulnerabilities, says Chris Wysopal, founder and chief technology officer at application-security firm Veracode.

"This should give extra capacity for naming unique vulnerabilities and getting the information to the appropriate vendor for ICS and medical device vulnerabilities," he says. "When you look at the CNA list, there aren't many ICS vendors and not a single medical device vendor. As the number of individual software products, open source packages, IoT, and embedded devices continues to expand rapidly, this should help more vulnerabilities be named and addressed properly."

As the CVE board continues to expand the number of CNAs and root-level CNAs, the overall number of vulnerabilities will likely increase, Wysopal says.

"The CVE program was conceived in a different world before SaaS, IoT, TCP/IP-connected ICS, open source libraries, and network-connected medical devices," he says, adding that, for example, more than 40% of vulnerabilities in open source software have not had a CVE identifier assigned. "As testing capabilities expand to more platforms and devices, there will undoubtedly be more vulnerabilities to track and manage. As more people focus on these devices, the numbers will go up."


Veteran technology journalist of more than 20 years. Former research engineer. Written for more than two dozen publications, including CNET News.com, Dark Reading, MIT's Technology Review, Popular Science, and Wired News. Five awards for journalism, including Best Deadline ... View Full Bio

Recommended Reading:

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Google Cloud Debuts Threat-Detection Service
Robert Lemos, Contributing Writer,  9/23/2020
Shopify's Employee Data Theft Underscores Risk of Rogue Insiders
Kelly Sheridan, Staff Editor, Dark Reading,  9/23/2020
Register for Dark Reading Newsletters
White Papers
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2020-09-27
XSS exists in the MobileFrontend extension for MediaWiki before 1.34.4 because section.line is mishandled during regex section line replacement from PageGateway. Using crafted HTML, an attacker can elicit an XSS attack via jQuery's parseHTML method, which can cause image callbacks to fire even witho...
PUBLISHED: 2020-09-27
An issue was discovered in the FileImporter extension for MediaWiki before 1.34.4. An attacker can import a file even when the target page is protected against "page creation" and the attacker should not be able to create it. This occurs because of a mishandled distinction between an uploa...
PUBLISHED: 2020-09-27
An issue was discovered in MediaWiki 1.34.x before 1.34.4. On Special:Contributions, the NS filter uses unescaped messages as keys in the option key for an HTMLForm specifier. This is vulnerable to a mild XSS if one of those messages is changed to include raw HTML.
PUBLISHED: 2020-09-27
In MediaWiki before 1.31.10 and 1.32.x through 1.34.x before 1.34.4, Special:UserRights exposes the existence of hidden users.
PUBLISHED: 2020-09-27
In MediaWiki before 1.31.10 and 1.32.x through 1.34.x before 1.34.4, XSS related to jQuery can occur. The attacker creates a message with [javascript:payload xss] and turns it into a jQuery object with mw.message().parse(). The expected result is that the jQuery object does not contain an <a> ...