News & Events

Right-click and copy a URL to share an article. Send feedback about this page to cve@mitre.org.
Please use our LinkedIn page to comment on the articles below.

Minutes from CVE Board Teleconference Meeting on August 9 Now Available
August 16, 2017 | Share this article

The CVE Board held a teleconference meeting on August 9, 2017. Read the meeting minutes.

Airbus and Kaspersky Labs Added as CVE Numbering Authorities (CNAs)
August 10, 2017 | Share this article

Airbus and Kaspersky Labs are now CVE Numbering Authorities (CNAs). The scope for Airbus is all Airbus products as well as vulnerabilities in third-party software discovered by Airbus that are not covered by another CNA and for Kaspersky Labs it is their B2C products (Kaspersky Free, Kaspersky Privacy Cleaner, Kaspersky Secure Connection, Kaspersky Password Manager, Kaspersky Anti-Virus, Kaspersky Internet Security, Kaspersky Total Security, Kaspersky Password Manager, Kaspersky Safe Kids, Kaspersky Virus Scanner, Kaspersky Virus Scanner Pro, Kaspersky Security Scan, Kaspersky Software Updater, Kaspersky System Checker, Kaspersky AdCleaner, Kaspersky QR Scanner, Kaspersky Safe Browser, Kaspersky Threat Scan, Kaspersky Virus Removal Tool, and Kaspersky Rescue Disk) and B2B products (Kaspersky Small Office Security, Kaspersky Endpoint Security Cloud, Kaspersky Endpoint Security for Business Select, Kaspersky Endpoint Security for Business Advanced, Kaspersky Endpoint Security for Business Total, Kaspersky Security for Mail Server, Kaspersky Security for File Server, Kaspersky Security for Mobile, Kaspersky Security for Internet Gateway, Kaspersky Security for Virtualization, Kaspersky Security for Collaboration, Kaspersky Systems Management, Kaspersky Security for Storage, Kaspersky DDoS Protection, Kaspersky Embedded Systems Security, Kaspersky Anti-Targeted Attack Platform, Kaspersky Security Intelligence Services, Kaspersky Fraud Prevention, and Kaspersky Industrial CyberSecurity) as well as vulnerabilities discovered in third-party software not covered by another CNA.

CNAs are OS and product vendors, developers, security researchers, and research organizations that assign CVE IDs to newly discovered issues without directly involving MITRE in the details of the specific vulnerabilities, and include the CVE IDs in the first public disclosure of the vulnerabilities.

CNAs are the main method for requesting a CVE ID. The following 72 organizations currently participate as CNAs: Adobe; Airbus, Alibaba; Apache; Apple; Atlassian; Autodesk; BlackBerry; Brocade; CA; Canonical; CERT/CC; Check Point; Cisco; Dahua; Debian GNU/Linux; Dell EMC; Distributed Weakness Filing Project; Drupal.org; Duo; Eclipse Foundation; Elastic; F5; Flexera Software; Fortinet; FreeBSD; Google; HackerOne; HP; Hewlett Packard Enterprise; Huawei; IBM; ICS-CERT; Intel; IOActive; ISC; JPCERT/CC; Juniper; Kaspersky Labs; KrCERT/CC; Larry Cashdollar; Lenovo; MarkLogic; McAfee; Micro Focus; Microsoft; MITRE (primary CNA); Mozilla; Netflix; Netgear; Nvidia; Objective Development; OpenSSL; Oracle; Puppet; Qihoo 360; Qualcomm; Rapid 7; Red Hat; Schneider Electric; Siemens; Silicon Graphics; Symantec; Synology; Talos; Tenable; TIBCO; Trend Micro; VMware; Yandex; Zero Day Initiative, and ZTE.

For more information about requesting CVE ID numbers from CNAs, visit Request a CVE ID.

Autodesk Added as CVE Numbering Authority (CNA)
August 9, 2017 | Share this article

Autodesk is now a CVE Numbering Authority (CNA) for all currently supported Autodesk Applications and Cloud Services.

CNAs are OS and product vendors, developers, security researchers, and research organizations that assign CVE IDs to newly discovered issues without directly involving MITRE in the details of the specific vulnerabilities, and include the CVE IDs in the first public disclosure of the vulnerabilities.

CNAs are the main method for requesting a CVE ID. The following 70 organizations currently participate as CNAs: Adobe; Alibaba; Apache; Apple; Atlassian; Autodesk; BlackBerry; Brocade; CA; Canonical; CERT/CC; Check Point; Cisco; Dahua; Debian GNU/Linux; Dell EMC; Distributed Weakness Filing Project; Drupal.org; Duo; Eclipse Foundation; Elastic; F5; Flexera Software; Fortinet; FreeBSD; Google; HackerOne; HP; Hewlett Packard Enterprise; Huawei; IBM; ICS-CERT; Intel; IOActive; ISC; JPCERT/CC; Juniper; KrCERT/CC; Larry Cashdollar; Lenovo; MarkLogic; McAfee; Micro Focus; Microsoft; MITRE (primary CNA); Mozilla; Netflix; Netgear; Nvidia; Objective Development; OpenSSL; Oracle; Puppet; Qihoo 360; Qualcomm; Rapid 7; Red Hat; Schneider Electric; Siemens; Silicon Graphics; Symantec; Synology; Talos; Tenable; TIBCO; Trend Micro; VMware; Yandex; Zero Day Initiative, and ZTE.

For more information about requesting CVE ID numbers from CNAs, visit Request a CVE ID.

Alibaba Added as CVE Numbering Authority (CNA)
August 2, 2017 | Share this article

Alibaba, Inc. is now a CVE Numbering Authority (CNA) for projects listed on its Alibaba GitHub website only.

CNAs are OS and product vendors, developers, security researchers, and research organizations that assign CVE IDs to newly discovered issues without directly involving MITRE in the details of the specific vulnerabilities, and include the CVE IDs in the first public disclosure of the vulnerabilities.

CNAs are the main method for requesting a CVE ID. The following 69 organizations currently participate as CNAs: Adobe; Alibaba; Apache; Apple; Atlassian; BlackBerry; Brocade; CA; Canonical; CERT/CC; Check Point; Cisco; Dahua; Debian GNU/Linux; Dell EMC; Distributed Weakness Filing Project; Drupal.org; Duo; Eclipse Foundation; Elastic; F5; Flexera Software; Fortinet; FreeBSD; Google; HackerOne; HP; Hewlett Packard Enterprise; Huawei; IBM; ICS-CERT; Intel; IOActive; ISC; JPCERT/CC; Juniper; KrCERT/CC; Larry Cashdollar; Lenovo; MarkLogic; McAfee; Micro Focus; Microsoft; MITRE (primary CNA); Mozilla; Netflix; Netgear; Nvidia; Objective Development; OpenSSL; Oracle; Puppet; Qihoo 360; Qualcomm; Rapid 7; Red Hat; Schneider Electric; Siemens; Silicon Graphics; Symantec; Synology; Talos; Tenable; TIBCO; Trend Micro; VMware; Yandex; Zero Day Initiative, and ZTE.

For more information about requesting CVE ID numbers from CNAs, visit Request a CVE ID.

Minutes from CVE Board Teleconference Meeting on July 26 Now Available
August 2, 2017 | Share this article

The CVE Board held a teleconference meeting on July 26, 2017. Read the meeting minutes.

Slides from “CVE IDs and How to Get Them” Talk at DEF CON 25 Now Available
August 2, 2017 | Share this article

Briefing slides are now available from the CVE talk entitled “CVE IDs and How to Get Them” by CVE Numbering Authority Program Lead Dan Adinolfi and CVE Team Member Anthony Singleton on July 28, 2017 at the “Wall of Sheep” at DEF CON 25 in Las Vegas, Nevada, USA.

Talk synopsis from the conference website: “The Common Vulnerabilities and Exposures (CVE) program uniquely identifies and names publicly-disclosed vulnerabilities in software and other codebases. Whether you are a vulnerability researcher, a vendor, or a project maintainer, it has never been easier to have CVE IDs assigned to vulnerabilities you are disclosing or coordinating around. This presentation will be an opportunity to find out how to participate as well as a chance to offer your thoughts, questions, or feedback about CVE. Attendees will learn what is considered a vulnerability for CVE, how to assign CVE IDs to vulnerabilities, how to describe those vulnerabilities within CVE ID entries, how to submit those assignments, and where to get more information about CVE assignment.”

Visit the CVE Calendar for information on this and other events.

Minutes from CVE Board Teleconference Meeting on May 24 Now Available
August 2, 2017 | Share this article

The CVE Board held a teleconference meeting on May 24, 2017. Read the meeting minutes.

REMINDER: “REJECT” Is Not Always a Permanent State for a CVE ID Begins July 27, 2017
July 27, 2017 | Share this article

CVE IDs in the "REJECT" state can now be changed to another state at any time as appropriate.

Please see FOCUS ON: Marking a CVE ID “REJECT” Is Not Permanent; It Can Be Updated and Added to the CVE List for details.

Tenable Added as CVE Numbering Authority (CNA)
July 24, 2017 | Share this article

Tenable Network Security, Inc. is now a CVE Numbering Authority (CNA) for Tenable products and third-party products upon which they perform their vulnerability research that are not covered by another CNA.

CNAs are OS and product vendors, developers, security researchers, and research organizations that assign CVE IDs to newly discovered issues without directly involving MITRE in the details of the specific vulnerabilities, and include the CVE IDs in the first public disclosure of the vulnerabilities.

CNAs are the main method for requesting a CVE ID. The following 68 organizations currently participate as CNAs: Adobe; Apache; Apple; Atlassian; BlackBerry; Brocade; CA; Canonical; CERT/CC; Check Point; Cisco; Dahua; Debian GNU/Linux; Dell EMC; Distributed Weakness Filing Project; Drupal.org; Duo; Eclipse Foundation; Elastic; F5; Flexera Software; Fortinet; FreeBSD; Google; HackerOne; HP; Hewlett Packard Enterprise; Huawei; IBM; ICS-CERT; Intel; IOActive; ISC; JPCERT/CC; Juniper; KrCERT/CC; Larry Cashdollar; Lenovo; MarkLogic; McAfee; Micro Focus; Microsoft; MITRE (primary CNA); Mozilla; Netflix; Netgear; Nvidia; Objective Development; OpenSSL; Oracle; Puppet; Qihoo 360; Qualcomm; Rapid 7; Red Hat; Schneider Electric; Siemens; Silicon Graphics; Symantec; Synology; Talos; Tenable; TIBCO; Trend Micro; VMware; Yandex; Zero Day Initiative, and ZTE.

For more information about requesting CVE ID numbers from CNAs, visit Request a CVE ID.

Duo Added as CVE Numbering Authority (CNA)
July 18, 2017 | Share this article

Duo Security, Inc. is now a CVE Numbering Authority (CNA) for Duo products and any third-party research targets not covered by another CNA.

CNAs are OS and product vendors, developers, security researchers, and research organizations that assign CVE IDs to newly discovered issues without directly involving MITRE in the details of the specific vulnerabilities, and include the CVE IDs in the first public disclosure of the vulnerabilities.

CNAs are the main method for requesting a CVE ID. The following 67 organizations currently participate as CNAs: Adobe; Apache; Apple; Atlassian; BlackBerry; Brocade; CA; Canonical; CERT/CC; Check Point; Cisco; Dahua; Debian GNU/Linux; Dell EMC; Distributed Weakness Filing Project; Drupal.org; Duo; Eclipse Foundation; Elastic; F5; Flexera Software; Fortinet; FreeBSD; Google; HackerOne; HP; Hewlett Packard Enterprise; Huawei; IBM; ICS-CERT; Intel; IOActive; ISC; JPCERT/CC; Juniper; KrCERT/CC; Larry Cashdollar; Lenovo; MarkLogic; McAfee; Micro Focus; Microsoft; MITRE (primary CNA); Mozilla; Netflix; Netgear; Nvidia; Objective Development; OpenSSL; Oracle; Puppet; Qihoo 360; Qualcomm; Rapid 7; Red Hat; Schneider Electric; Siemens; Silicon Graphics; Symantec; Synology; Talos; TIBCO; Trend Micro; VMware; Yandex; Zero Day Initiative, and ZTE.

For more information about requesting CVE ID numbers from CNAs, visit Request a CVE ID.

Minutes from CVE Board Teleconference Meeting on July 12 Now Available
July 18, 2017 | Share this article

The CVE Board held a teleconference meeting on July 12, 2017. Read the meeting minutes.

Minutes from CVE Board Teleconference Meeting on June 28 Now Available
July 13, 2017 | Share this article

The CVE Board held a teleconference meeting on June 28, 2017. Read the meeting minutes.

ZTE Added as CVE Numbering Authority (CNA)
July 11, 2017 | Share this article

ZTE Corporation is now a CVE Numbering Authority (CNA) for ZTE products only.

CNAs are OS and product vendors, developers, security researchers, and research organizations that assign CVE IDs to newly discovered issues without directly involving MITRE in the details of the specific vulnerabilities, and include the CVE IDs in the first public disclosure of the vulnerabilities.

CNAs are the main method for requesting a CVE ID. The following 66 organizations currently participate as CNAs: Adobe; Apache; Apple; Atlassian; BlackBerry; Brocade; CA; Canonical; CERT/CC; Check Point; Cisco; Dahua; Debian GNU/Linux; Dell EMC; Distributed Weakness Filing Project; Drupal.org; Eclipse Foundation; Elastic; F5; Flexera Software; Fortinet; FreeBSD; Google; HackerOne; HP; Hewlett Packard Enterprise; Huawei; IBM; ICS-CERT; Intel; IOActive; ISC; JPCERT/CC; Juniper; KrCERT/CC; Larry Cashdollar; Lenovo; MarkLogic; McAfee; Micro Focus; Microsoft; MITRE (primary CNA); Mozilla; Netflix; Netgear; Nvidia; Objective Development; OpenSSL; Oracle; Puppet; Qihoo 360; Qualcomm; Rapid 7; Red Hat; Schneider Electric; Siemens; Silicon Graphics; Symantec; Synology; Talos; TIBCO; Trend Micro; VMware; Yandex; Zero Day Initiative, and ZTE.

For more information about requesting CVE ID numbers from CNAs, visit Request a CVE ID.

IMPORTANT: CVE Identifier (CVE ID) Reference Updates Begin on July 10, 2017
July 3, 2017 | Share this article

To help keep CVE ID References up-to-date within the CVE List, the CVE Team will be updating a large number of References where necessary in the coming months.

The CVE IDs affected include those from years 1999 through 2016. CVE List consumers will see up to 5,000 CVE IDs with updated references beginning on July 10, 2017. On 8-day intervals thereafter, additional batches of up to 5,000 CVE IDs with updated references will occur. These updates will occur indefinitely until further notice.

If you have any comments or concerns about this process, please send them to our CVE Request web form, and select the Other request type.

CVE Adds 3 New CVE Numbering Authorities (CNAs): Netflix, Trend Micro, and Zero Day Initiative
June 29, 2017 | Share this article

The following two software vendors and one third-party coordinator are now CVE Numbering Authorities (CNAs): Netflix, Inc. for Netflix Mobile Streaming Application and Netflix Open Source projects only; Trend Micro, Inc. for Trend Micro issues only; and Zero Day Initiative, as a third-party coordinator, for products and projects covered by its bug bounty programs not already covered by another CNA.

CNAs are OS and product vendors, developers, security researchers, and research organizations that assign CVE IDs to newly discovered issues without directly involving MITRE in the details of the specific vulnerabilities, and include the CVE IDs in the first public disclosure of the vulnerabilities.

CNAs are the main method for requesting a CVE ID. The following 65 organizations currently participate as CNAs: Adobe; Apache; Apple; Atlassian; BlackBerry; Brocade; CA; Canonical; CERT/CC; Check Point; Cisco; Dahua; Debian GNU/Linux; Dell EMC; Distributed Weakness Filing Project; Drupal.org; Eclipse Foundation; Elastic; F5; Flexera Software; Fortinet; FreeBSD; Google; HackerOne; HP; Hewlett Packard Enterprise; Huawei; IBM; ICS-CERT; Intel; IOActive; ISC; JPCERT/CC; Juniper; KrCERT/CC; Larry Cashdollar; Lenovo; MarkLogic; McAfee; Micro Focus; Microsoft; MITRE (primary CNA); Mozilla; Netflix; Netgear; Nvidia; Objective Development; OpenSSL; Oracle; Puppet; Qihoo 360; Qualcomm; Rapid 7; Red Hat; Schneider Electric; Siemens; Silicon Graphics; Symantec; Synology; Talos; TIBCO; Trend Micro; VMware; Yandex; and Zero Day Initiative.

For more information about requesting CVE ID numbers from CNAs, visit Request a CVE ID.

FOCUS ON: Marking a CVE ID “REJECT” Is Not Permanent; It Can Be Updated and Added to the CVE List
June 27, 2017 | Share this article

The CVE Team and CVE Board have recently revisited the use of CVE Identifier (CVE ID) states — REJECT, RESERVED, DISPUTED — and are planning to make some necessary changes to them in the coming months.

One of the changes recently discussed was in how the “REJECT” state is applied, and specifically whether a REJECT CVE ID can change states again at a later date.

What REJECT Means for a CVE ID

As a recap, a CVE ID marked as REJECT is a CVE ID that is not accepted as a CVE ID. The reason a CVE ID is marked REJECT will most often be stated in the Description of the CVE ID. Possible examples include it being a duplicate CVE ID, it being withdrawn by the original requester, it being assigned incorrectly, or some other administrative reason.

As a rule, REJECT CVE IDs should be ignored. However, there may be cases where a CVE ID previously marked as REJECT might need to move back to RESERVED or a populated state (i.e., the details and References are published and included).

A REJECT State Is Not Permanent

The CVE Team and CVE Board agree that the REJECT state should NOT be considered permanent, and that changes to this CVE ID state should be allowed in the future.

An example case could include a simple accidental REJECT, where a CVE ID was marked as REJECT by a CVE Numbering Authority (CNA) but the CVE ID was used publicly. In this case, it would create more confusion and additional work to REJECT the already used CVE ID, assign a new CVE ID, and also make sure that all public references are updated. The change discussed here would be to simply change the REJECT CVE ID and populate it with the details that were intended.

Both the CVE Team and CVE Board agree that some downstream consumers of CVE may be currently interpreting the REJECT state as permanent and that the CVE ID will never change in the future. It was also agreed that we should provide proper notice to the community that this change in use of the REJECT state should be provided.

Moving Forward

This announcement serves as notice that beginning July 27, 2017, CVE IDs in the REJECT state can be changed to another state at any time as appropriate.

If you have any comments or concerns about this change, please send them to our CVE Request web form, and select the Other request type.

Atlassian Added as CVE Numbering Authority (CNA)
June 12, 2017 | Share this article

Atlassian is now a CVE Numbering Authority (CNA) for Atlassian issues only.

CNAs are OS and product vendors, developers, security researchers, and research organizations that assign CVE IDs to newly discovered issues without directly involving MITRE in the details of the specific vulnerabilities, and include the CVE IDs in the first public disclosure of the vulnerabilities.

CNAs are the main method for requesting a CVE ID. The following 62 organizations currently participate as CNAs: Adobe; Apache; Apple; Atlassian; BlackBerry; Brocade; CA; Canonical; CERT/CC; Check Point; Cisco; Dahua; Debian GNU/Linux; Dell EMC; Distributed Weakness Filing Project; Drupal.org; Eclipse Foundation; Elastic; F5; Flexera Software; Fortinet; FreeBSD; Google; HackerOne; HP; Hewlett Packard Enterprise; Huawei; IBM; ICS-CERT; Intel; IOActive; ISC; JPCERT/CC; Juniper; KrCERT/CC; Larry Cashdollar; Lenovo; MarkLogic; McAfee; Micro Focus; Microsoft; MITRE (primary CNA); Mozilla; Netgear; Nvidia; Objective Development; OpenSSL; Oracle; Puppet; Qihoo 360; Qualcomm; Rapid 7; Red Hat; Schneider Electric; Siemens; Silicon Graphics; Symantec; Synology; Talos; TIBCO; VMware; and Yandex.

For more information about requesting CVE ID numbers from CNAs, visit Request a CVE ID.

CA Technologies Added as CVE Numbering Authority (CNA)
June 5, 2017 | Share this article

CA Technologies is now a CVE Numbering Authority (CNA) for CA Technologies issues only.

CNAs are OS and product vendors, developers, security researchers, and research organizations that assign CVE IDs to newly discovered issues without directly involving MITRE in the details of the specific vulnerabilities, and include the CVE IDs in the first public disclosure of the vulnerabilities.

CNAs are the main method for requesting a CVE ID. The following 61 organizations currently participate as CNAs: Adobe; Apache; Apple; BlackBerry; Brocade; CA; Canonical; CERT/CC; Check Point; Cisco; Dahua; Debian GNU/Linux; Dell EMC; Distributed Weakness Filing Project; Drupal.org; Eclipse Foundation; Elastic; F5; Flexera Software; Fortinet; FreeBSD; Google; HackerOne; HP; Hewlett Packard Enterprise; Huawei; IBM; ICS-CERT; Intel; IOActive; ISC; JPCERT/CC; Juniper; KrCERT/CC; Larry Cashdollar; Lenovo; MarkLogic; McAfee; Micro Focus; Microsoft; MITRE (primary CNA); Mozilla; Netgear; Nvidia; Objective Development; OpenSSL; Oracle; Puppet; Qihoo 360; Qualcomm; Rapid 7; Red Hat; Schneider Electric; Siemens; Silicon Graphics; Symantec; Synology; Talos; TIBCO; VMware; and Yandex.

For more information about requesting CVE ID numbers from CNAs, visit Request a CVE ID.

Dahua Added as CVE Numbering Authority (CNA)
June 5, 2017 | Share this article

Dahua Technologies is now a CVE Numbering Authority (CNA) for Dahua issues only.

CNAs are OS and product vendors, developers, security researchers, and research organizations that assign CVE IDs to newly discovered issues without directly involving MITRE in the details of the specific vulnerabilities, and include the CVE IDs in the first public disclosure of the vulnerabilities.

CNAs are the main method for requesting a CVE ID. The following 61 organizations currently participate as CNAs: Adobe; Apache; Apple; BlackBerry; Brocade; CA; Canonical; CERT/CC; Check Point; Cisco; Dahua; Debian GNU/Linux; Dell EMC; Distributed Weakness Filing Project; Drupal.org; Eclipse Foundation; Elastic; F5; Flexera Software; Fortinet; FreeBSD; Google; HackerOne; HP; Hewlett Packard Enterprise; Huawei; IBM; ICS-CERT; Intel; IOActive; ISC; JPCERT/CC; Juniper; KrCERT/CC; Larry Cashdollar; Lenovo; MarkLogic; McAfee; Micro Focus; Microsoft; MITRE (primary CNA); Mozilla; Netgear; Nvidia; Objective Development; OpenSSL; Oracle; Puppet; Qihoo 360; Qualcomm; Rapid 7; Red Hat; Schneider Electric; Siemens; Silicon Graphics; Symantec; Synology; Talos; TIBCO; VMware; and Yandex.

For more information about requesting CVE ID numbers from CNAs, visit Request a CVE ID.

Synology Added as CVE Numbering Authority (CNA)
June 1, 2017 | Share this article

Synology Inc. is now a CVE Numbering Authority (CNA) for Synology issues including its network attached storage (NAS) products only.

CNAs are OS and product vendors, developers, security researchers, and research organizations that assign CVE IDs to newly discovered issues without directly involving MITRE in the details of the specific vulnerabilities, and include the CVE IDs in the first public disclosure of the vulnerabilities.

CNAs are the main method for requesting a CVE ID. The following 59 organizations currently participate as CNAs: Adobe; Apache; Apple; BlackBerry; Brocade; Canonical; CERT/CC; Check Point; Cisco; Debian GNU/Linux; Dell EMC; Distributed Weakness Filing Project; Drupal.org; Eclipse Foundation; Elastic; F5; Flexera Software; Fortinet; FreeBSD; Google; HackerOne; HP; Hewlett Packard Enterprise; Huawei; IBM; ICS-CERT; Intel; IOActive; ISC; JPCERT/CC; Juniper; KrCERT/CC; Larry Cashdollar; Lenovo; MarkLogic; McAfee; Micro Focus; Microsoft; MITRE (primary CNA); Mozilla; Netgear; Nvidia; Objective Development; OpenSSL; Oracle; Puppet; Qihoo 360; Qualcomm; Rapid 7; Red Hat; Schneider Electric; Siemens; Silicon Graphics; Symantec; Synology; Talos; TIBCO; VMware; and Yandex.

For more information about requesting CVE ID numbers from CNAs, visit Request a CVE ID.

Minutes from CVE Board Teleconference Meeting on May 3 Now Available
June 1, 2017 | Share this article

The CVE Board held a teleconference meeting on May 3, 2017. Read the meeting minutes.

Ambionics Security Makes Declaration of CVE Compatibility
May 22, 2017 | Share this article

Ambionics Security declared that its Ambionics Security Service is CVE-Compatible. For additional information about this and other CVE-Compatible products, visit the CVE-Compatible Products and Services section.

Bluedon Information Security Technologies Makes Declaration of CVE Compatibility
May 22, 2017 | Share this article

Bluedon Information Security Technologies Co., Ltd. declared that its Bluedon Vulnerability Scanning System is CVE-Compatible. For additional information about this and other CVE-Compatible products, visit the CVE-Compatible Products and Services section.

NOTICE: CVE Request Web Form — Outage from 8:00 a.m. - 12:00 p.m. EDT on May 20
May 16, 2017 | Share this article

Due to scheduled maintenance, the submission confirmation email replies to CVE Request web form submissions may not be sent out from 8:00 a.m. until 12:00 p.m. Eastern time on Saturday, May 20, 2017.

Requests may still be made via the web form during this time, and the submission confirmation email replies will be sent after maintenance is complete.

This temporary outage affects requests to MITRE only. All other CVE Numbering Authorities (CNAs) can still be contacted during this time to request CVE IDs.

We apologize for any inconvenience. Please contact cve@mitre.org with any comments or concerns.

New CVE Board Member from Lenovo
May 11, 2017 | Share this article

Beverly Finch of Lenovo Group Ltd. has joined the CVE Board.

Read the full announcement and welcome message in the CVE Board email discussion list archive.

IMPORTANT: CVE Will Reject a Group of Unused CVE IDs on May 11
May 10, 2017 | Share this article

To help reduce the number of reserved but unused CVE IDs in the CVE List, the CVE Team will reject CVE IDs that CVE Numbering Authorities (CNAs) have indicated as being unused from their prior CVE ID allocations.

The CVE IDs affected include those from years 1999 through 2016. CVE List consumers will see 3,306 reserved CVE IDs become rejected in an update on May 11, 2017.

What to Expect

Once these CVE IDs are rejected, the Description portion of each CVE ID will be updated with the text below, with [Year] replacing the four-digit year:

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during [Year]. Notes: none.

For additional information about CVE IDs marked as RESERVED and REJECT, please see Why is a CVE entry marked as "RESERVED" when a CVE ID is being publicly used? and What does it mean when a CVE Identifier is marked "REJECT”?.

Moving Forward

Each year, CNAs are given blocks of CVE IDs that are marked as "RESERVED" in the CVE List until they are assigned to a vulnerability and published. CNAs often do not use all the CVE IDs they are allocated, which means many reserved CVE IDs that will never be assigned to a vulnerability. As a result, the unused CVE IDs need to be moved from RESERVED to REJECT status to avoid confusion and make it clear to CVE List consumers that the unused CVE IDs do not represent unannounced vulnerabilities.

Moving forward, the CVE Team will now ask CNAs for their lists of unused CVE IDs from their allocations at the start of each new calendar year, and those unused CVE IDs will be updated to "REJECT" status at that time.

If you have any comments or concerns about this process, please contact us using the CVE Request web form.

Elastic Added as CVE Numbering Authority (CNA)
May 4, 2017 | Share this article

Elastic is now a CVE Numbering Authority (CNA) for Elasticsearch, Kibana, Beats, Logstash, X-Pack, and Elastic Cloud Enterprise products only.

CNAs are OS and product vendors, developers, security researchers, and research organizations that assign CVE IDs to newly discovered issues without directly involving MITRE in the details of the specific vulnerabilities, and include the CVE IDs in the first public disclosure of the vulnerabilities.

CNAs are the main method for requesting a CVE ID. The following 58 organizations currently participate as CNAs: Adobe; Apache; Apple; BlackBerry; Brocade; Canonical; CERT/CC; Check Point; Cisco; Debian GNU/Linux; Dell EMC; Distributed Weakness Filing Project; Drupal.org; Eclipse Foundation; Elastic; F5; Flexera Software; Fortinet; FreeBSD; Google; HackerOne; HP; Hewlett Packard Enterprise; Huawei; IBM; ICS-CERT; Intel; IOActive; ISC; JPCERT/CC; Juniper; KrCERT/CC; Larry Cashdollar; Lenovo; MarkLogic; McAfee; Micro Focus; Microsoft; MITRE (primary CNA); Mozilla; Netgear; Nvidia; Objective Development; OpenSSL; Oracle; Puppet; Qihoo 360; Qualcomm; Rapid 7; Red Hat; Schneider Electric; Siemens; Silicon Graphics; Symantec; Talos; TIBCO; VMware; and Yandex.

For more information about requesting CVE ID numbers from CNAs, visit Request a CVE ID.

"Expanding and Improving" CVE Talk at European Government CERTs (EGC) Group Meeting on May 18
May 4, 2017 | Share this article

CVE Numbering Authorities Program Lead Dan Adinolfi will give a talk entitled "Expanding and Improving CVE to Facilitate Vulnerability Disclosure and Management" on May 18, 2017 at the European Government CERTs (EGC) Group Meeting in The Hague, the Netherlands.

Talk synopsis: "The Common Vulnerabilities and Exposures (CVE) program uniquely identifies and names publicly-disclosed vulnerabilities in software and other codebases. CVE Numbering Authorities (CNAs) are an important part of the CVE program and are given the ability to identify and name CVE IDs in coordination with the MITRE CVE team. Participating as a CVE CNA allows organizations to have more control over their vulnerability management and disclosure processes while also ensuring a consistent level of service and a high quality of content within the CVE list. Becoming a CNA can be beneficial to vendors, coordination centers, and their customers, and it helps build a community of practice that continues to help improve the state of vulnerability management across many sectors."

Visit the CVE Calendar for information on this and other events.

"Expanding and Improving" CVE Talk at TF-CSIRT Annual Group Meeting on May 15
May 4, 2017 | Share this article

CVE Numbering Authorities Program Lead Dan Adinolfi will give a talk entitled "Expanding and Improving CVE to Facilitate Vulnerability Disclosure and Management" on May 15, 2017 at the Task Force-Computer Security Incident Response Team (TF-CSIRT) Group Annual Meeting in The Hague, the Netherlands.

Talk synopsis: "The Common Vulnerabilities and Exposures (CVE) program uniquely identifies and names publicly-disclosed vulnerabilities in software and other codebases. CVE Numbering Authorities (CNAs) are an important part of the CVE program and are given the ability to identify and name CVE IDs in coordination with the MITRE CVE team. Participating as a CVE CNA allows organizations to have more control over their vulnerability management and disclosure processes while also ensuring a consistent level of service and a high quality of content within the CVE list. Becoming a CNA can be beneficial to vendors, coordination centers, and their customers, and it helps build a community of practice that continues to help improve the state of vulnerability management across many sectors."

Visit the CVE Calendar for information on this and other events.

IOActive Added as CVE Numbering Authority (CNA)
April 25, 2017 | Share this article

IOActive is now a CVE Numbering Authority (CNA) for third-party products it researches.

CNAs are OS and product vendors, developers, security researchers, and research organizations that assign CVE IDs to newly discovered issues without directly involving MITRE in the details of the specific vulnerabilities, and include the CVE IDs in the first public disclosure of the vulnerabilities.

CNAs are the main method for requesting a CVE ID. The following 57 organizations currently participate as CNAs: Adobe; Apache; Apple; BlackBerry; Brocade; Canonical; CERT/CC; Check Point; Cisco; Debian GNU/Linux; Dell EMC; Distributed Weakness Filing Project; Drupal.org; Eclipse Foundation; F5; Flexera Software; Fortinet; FreeBSD; Google; HackerOne; HP; Hewlett Packard Enterprise; Huawei; IBM; ICS-CERT; Intel; IOActive; ISC; JPCERT/CC; Juniper; KrCERT/CC; Larry Cashdollar; Lenovo; MarkLogic; McAfee; Micro Focus; Microsoft; MITRE (primary CNA); Mozilla; Netgear; Nvidia; Objective Development; OpenSSL; Oracle; Puppet; Qihoo 360; Qualcomm; Rapid 7; Red Hat; Schneider Electric; Siemens; Silicon Graphics; Symantec; Talos; TIBCO; VMware; and Yandex.

For more information about requesting CVE ID numbers from CNAs, visit Request a CVE ID.

Schneider Electric Added as CVE Numbering Authority (CNA)
April 20, 2017 | Share this article

Schneider Electric SE is now a CVE Numbering Authority (CNA) for Schneider Electric products only.

CNAs are OS and product vendors, developers, security researchers, and research organizations that assign CVE IDs to newly discovered issues without directly involving MITRE in the details of the specific vulnerabilities, and include the CVE IDs in the first public disclosure of the vulnerabilities.

CNAs are the main method for requesting a CVE ID. The following 56 organizations currently participate as CNAs: Adobe; Apache; Apple; BlackBerry; Brocade; Canonical; CERT/CC; Check Point; Cisco; Debian GNU/Linux; Dell EMC; Distributed Weakness Filing Project; Drupal.org; Eclipse Foundation; F5; Flexera Software; Fortinet; FreeBSD; Google; HackerOne; HP; Hewlett Packard Enterprise; Huawei; IBM; ICS-CERT; Intel; ISC; JPCERT/CC; Juniper; KrCERT/CC; Larry Cashdollar; Lenovo; MarkLogic; McAfee; Micro Focus; Microsoft; MITRE (primary CNA); Mozilla; Netgear; Nvidia; Objective Development; OpenSSL; Oracle; Puppet; Qihoo 360; Qualcomm; Rapid 7; Red Hat; Schneider Electric; Siemens; Silicon Graphics; Symantec; Talos; TIBCO; VMware; and Yandex.

For more information about requesting CVE ID numbers from CNAs, visit Request a CVE ID.

Minutes from CVE Board Teleconference Meeting on April 5 Now Available
April 20, 2017 | Share this article

The CVE Board held a teleconference meeting on April 5, 2017. Read the meeting minutes.

Eclipse Foundation Added as CVE Numbering Authority (CNA)
April 14, 2017 | Share this article

The Eclipse Foundation is now a CVE Numbering Authority (CNA) for Eclipse IDE and the Eclipse Foundation’s eclipse.org, polarsys.org, and locationtech.org open source projects only.

CNAs are OS and product vendors, developers, security researchers, and research organizations that assign CVE IDs to newly discovered issues without directly involving MITRE in the details of the specific vulnerabilities, and include the CVE IDs in the first public disclosure of the vulnerabilities.

CNAs are the main method for requesting a CVE ID. The following 55 organizations currently participate as CNAs: Adobe; Apache; Apple; BlackBerry; Brocade; Canonical; CERT/CC; Check Point; Cisco; Debian GNU/Linux; Dell EMC; Distributed Weakness Filing Project; Drupal.org; Eclipse Foundation; F5; Flexera Software; Fortinet; FreeBSD; Google; HackerOne; HP; Hewlett Packard Enterprise; Huawei; IBM; ICS-CERT; Intel; ISC; JPCERT/CC; Juniper; KrCERT/CC; Larry Cashdollar; Lenovo; MarkLogic; McAfee; Micro Focus; Microsoft; MITRE (primary CNA); Mozilla; Netgear; Nvidia; Objective Development; OpenSSL; Oracle; Puppet; Qihoo 360; Qualcomm; Rapid 7; Red Hat; Siemens; Silicon Graphics; Symantec; Talos; TIBCO; VMware; and Yandex.

For more information about requesting CVE ID numbers from CNAs, visit Request a CVE ID.

"Expanding and Improving" CVE Talk at SOURCE Boston 2017 on April 27
April 14, 2017 | Share this article

CVE Numbering Authorities Program Lead Dan Adinolfi will give a talk entitled Expanding and Improving CVE to Facilitate Vulnerability Disclosure and Management on April 27, 2017 at SOURCE Boston 2017 in Boston, Massachusetts, USA. The event itself runs April 26-27.

From the event agenda:

“The Common Vulnerabilities and Exposures (CVE) program uniquely identifies and names publicly-disclosed vulnerabilities in software and other codebases. CVE Numbering Authorities (CNAs) are an important part of the CVE program and are given the ability to identify and name CVE IDs in coordination with the MITRE CVE team. Participating as a CVE CNA allows organizations to have more control over their vulnerability management and disclosure processes while also ensuring a consistent level of service and a high quality of content within the CVE list. Becoming a CNA can be beneficial to vendors, coordination centers, and their customers, and it helps build a community of practice that continues to help improve the state of vulnerability management across many sectors. Join Daniel Adinolfi of the CVE program to learn about these benefits and how to participate. Who should attend: CVE is a core piece of infrastructure that enables coordinated vulnerability disclosure and management. Developers, vulnerability researchers, product security incident response team (PSIRT) members, and anyone involved in vulnerability disclosure, research, or management processes would find value in attending.”

To register for the event, visit http://www.sourceconference.com/boston-2017-registration.

Minutes from CVE Board Teleconference Meeting on March 22 Now Available
April 6, 2017 | Share this article

The CVE Board held a teleconference meeting on March 22, 2017. Read the meeting minutes.

Qualcomm Added as CVE Numbering Authority (CNA)
April 4, 2017 | Share this article

Qualcomm, Inc. is now a CVE Numbering Authority (CNA) for Qualcomm and Snapdragon issues only.

CNAs are OS and product vendors, developers, security researchers, and research organizations that assign CVE IDs to newly discovered issues without directly involving MITRE in the details of the specific vulnerabilities, and include the CVE IDs in the first public disclosure of the vulnerabilities.

CNAs are the main method for requesting a CVE ID. The following 54 organizations currently participate as CNAs: Adobe; Apache; Apple; BlackBerry; Brocade; Canonical; CERT/CC; Check Point; Cisco; Debian GNU/Linux; Dell EMC; Distributed Weakness Filing Project; Drupal.org; F5; Flexera Software; Fortinet; FreeBSD; Google; HackerOne; HP; Hewlett Packard Enterprise; Huawei; IBM; ICS-CERT; Intel; ISC; JPCERT/CC; Juniper; KrCERT/CC; Larry Cashdollar; Lenovo; MarkLogic; McAfee; Micro Focus; Microsoft; MITRE (primary CNA); Mozilla; Netgear; Nvidia; Objective Development; OpenSSL; Oracle; Puppet; Qihoo 360; Qualcomm; Rapid 7; Red Hat; Siemens; Silicon Graphics; Symantec; Talos; TIBCO; VMware; and Yandex.

For more information about requesting CVE ID numbers from CNAs, visit Request a CVE ID.

Minutes from CVE Board Teleconference Meeting on March 8 Now Available
March 30, 2017 | Share this article

The CVE Board held a teleconference meeting on March 8, 2017. Read the meeting minutes.

Siemens Added as CVE Numbering Authority (CNA)
March 23, 2017 | Share this article

Siemens AG is now a CVE Numbering Authority (CNA) for Siemens issues only.

CNAs are OS and product vendors, developers, security researchers, and research organizations that assign CVE IDs to newly discovered issues without directly involving MITRE in the details of the specific vulnerabilities, and include the CVE IDs in the first public disclosure of the vulnerabilities.

CNAs are the main method for requesting a CVE ID. The following 53 organizations currently participate as CNAs: Adobe; Apache; Apple; BlackBerry; Brocade; Canonical; CERT/CC; Check Point; Cisco; Debian GNU/Linux; Dell EMC; Distributed Weakness Filing Project; Drupal.org; F5; Flexera Software; Fortinet; FreeBSD; Google; HackerOne; HP; Hewlett Packard Enterprise; Huawei; IBM; ICS-CERT; Intel; ISC; JPCERT/CC; Juniper; KrCERT/CC; Larry Cashdollar; Lenovo; MarkLogic; McAfee; Micro Focus; Microsoft; MITRE (primary CNA); Mozilla; Netgear; Nvidia; Objective Development; OpenSSL; Oracle; Puppet; Qihoo 360; Rapid 7; Red Hat; Siemens; Silicon Graphics; Symantec; Talos; TIBCO; VMware; and Yandex.

For more information about requesting CVE ID numbers from CNAs, visit Request a CVE ID.

FOCUS ON: The Significance and Meaning of a CVE Identifier Marked as "RESERVED"
March 16, 2017 | Share this article

A CVE Identifier (CVE ID) is marked as "RESERVED" when it has been reserved for use by a vendor or security researcher but the details of it are not yet populated by the requester.

A CVE ID can change from the RESERVED state to being populated at any time based on a number of factors both internal and external to MITRE.

An example of an internal factor could include the bulk assignment of CVE IDs to a CVE Numbering Authority (CNA). These CVE IDs are marked as RESERVED upon allocation to a CNA, before they are assigned to a specific vulnerability. An example of an external factor could include a vulnerability that have not yet been publicly disclosed, such as when the affected product vendor is still developing a mitigation.

It is also important to note that when a CVE ID is marked as RESERVED, it will not yet be available in the U.S. National Vulnerability Database (NVD). NVD is based-upon and fed by the CVE List.

However, once the CVE ID is populated with details and published on the CVE List on the CVE website, it will become available in NVD. As one of the final steps in the overall process, the NVD Common Vulnerability Scoring System (CVSS) scores for the CVE ID are assigned by the NIST NVD team.

Visit the CVE Identifiers section of the FAQs page for answers to other questions about CVE IDs. You may also contact us with any comments or concerns.

CVE Launches "@CVEannounce" Twitter Feed
March 16, 2017 | Share this article

Please follow our second Twitter account at https://twitter.com/CVEannounce/ to get the latest CVE news and announcements.

Minutes from CVE Board Teleconference Meetings on February 8 and February 22 Now Available
March 16, 2017 | Share this article

The CVE Board held teleconference meetings on February 8, 2017 and February 22, 2017. Read the February 8 or February 22 meeting minutes.

Flexera Software and Netgear Added as CVE Numbering Authorities (CNAs)
March 14, 2017 | Share this article

Two additional organizations are now CVE Numbering Authorities (CNAs): Flexera Software LLC for all Flexera products and vulnerabilities discovered by Secunia Research that are not covered by another CNA, and Netgear, Inc. for Netgear issues only.

CNAs are OS and product vendors, developers, security researchers, and research organizations that assign CVE IDs to newly discovered issues without directly involving MITRE in the details of the specific vulnerabilities, and include the CVE IDs in the first public disclosure of the vulnerabilities.

CNAs are the main method for requesting a CVE ID. The following 52 organizations currently participate as CNAs: Adobe; Apache; Apple; BlackBerry; Brocade; Canonical; CERT/CC; Check Point; Cisco; Debian GNU/Linux; Dell EMC; Distributed Weakness Filing Project; Drupal.org; F5; Flexera Software; Fortinet; FreeBSD; Google; HackerOne; HP; Hewlett Packard Enterprise; Huawei; IBM; ICS-CERT; Intel; ISC; JPCERT/CC; Juniper; KrCERT/CC; Larry Cashdollar; Lenovo; MarkLogic; McAfee; Micro Focus; Microsoft; MITRE (primary CNA); Mozilla; Netgear; Nvidia; Objective Development; OpenSSL; Oracle; Puppet; Qihoo 360; Rapid 7; Red Hat; Silicon Graphics; Symantec; Talos; TIBCO; VMware; and Yandex.

For more information about requesting CVE ID numbers from CNAs, visit Request a CVE ID.

Qihoo 360 Added as CVE Numbering Authority (CNA)
March 9, 2017 | Share this article

Qihoo 360 Technology Co., Ltd. is now a CVE Numbering Authority (CNA) for 360 Safeguard, 360 Mobile Safe, and 360 Safe Router issues only.

CNAs are OS and product vendors, developers, security researchers, and research organizations that assign CVE IDs to newly discovered issues without directly involving MITRE in the details of the specific vulnerabilities, and include the CVE IDs in the first public disclosure of the vulnerabilities.

CNAs are the main method for requesting a CVE ID. The following 50 organizations currently participate as CNAs: Adobe; Apache; Apple; BlackBerry; Brocade; Canonical; CERT/CC; Check Point; Cisco; Debian GNU/Linux; Dell EMC; Distributed Weakness Filing Project; Drupal.org; F5; Fortinet; FreeBSD; Google; HackerOne; HP; Hewlett Packard Enterprise; Huawei; IBM; ICS-CERT; Intel; ISC; JPCERT/CC; Juniper; KrCERT/CC; Larry Cashdollar; Lenovo; MarkLogic; McAfee; Micro Focus; Microsoft; MITRE (primary CNA); Mozilla; Nvidia; Objective Development; OpenSSL; Oracle; Puppet; Qihoo 360; Rapid 7; Red Hat; Silicon Graphics; Symantec; Talos; TIBCO; VMware; and Yandex.

For more information about requesting CVE ID numbers from CNAs, visit Request a CVE ID.

CVE Launches New "CVE-CWE-CAPEC" Page on LinkedIn
March 9, 2017 | Share this article

The CVE Team has launched a "CVE-CWE-CAPEC page on LinkedIn" as an easy way for the community to comment on and share CVE Blog posts. Please stop by our new page and say hello. We very much look forward to hearing from you.

UPDATED NOTICE: CVE Request Web Form – Outage Rescheduled to 9:30 p.m.-11:30 p.m. EDT on March 8
March 8, 2017 | Share this article

The previously announced scheduled maintenance outage time for today has changed. The CVE Request Web Form will now be temporarily unavailable from 9:30 p.m. until 11:30 p.m. Eastern time, Wednesday, March 8, 2017. Please disregard the times stated in the previous announcement.

This temporary outage affects requests to MITRE only. All other CVE Numbering Authorities (CNAs) can still be contacted during this time to request CVE IDs.

We apologize for any inconvenience. Please contact cve@mitre.org with any comments or concerns.

NOTICE: CVE Request Web Form – Outage from 8:00 p.m.-10:00 p.m. EDT on March 8
March 6, 2017 | Share this article

Due to scheduled maintenance, the CVE Request Web Form will be temporarily unavailable from 8:00 p.m. until 10:00 p.m. Eastern time on Wednesday, March 8, 2017.

This temporary outage affects requests to MITRE only. All other CVE Numbering Authorities (CNAs) can still be contacted during this time to request CVE IDs.

We apologize for any inconvenience. Please contact cve@mitre.org with any comments or concerns.

CVE Launches Twitter Feed of Newest CVE IDs
March 2, 2017 | Share this article

Please follow our new Twitter feed at https://twitter.com/CVEnew/ to get regular updates of the newest CVE IDs.

Drupal.org Added as CVE Numbering Authority (CNA)
February 28, 2017 | Share this article

Drupal.org is now a CVE Numbering Authority (CNA) for all issues for projects hosted under Drupal.org only.

CNAs are OS and product vendors, developers, security researchers, and research organizations that assign CVE IDs to newly discovered issues without directly involving MITRE in the details of the specific vulnerabilities, and include the CVE IDs in the first public disclosure of the vulnerabilities.

CNAs are the main method for requesting a CVE ID. The following 49 organizations currently participate as CNAs: Adobe; Apache; Apple; BlackBerry; Brocade; Canonical; CERT/CC; Check Point; Cisco; Debian GNU/Linux; Dell EMC; Distributed Weakness Filing Project; Drupal.org; F5; Fortinet; FreeBSD; Google; HackerOne; HP; Hewlett Packard Enterprise; Huawei; IBM; ICS-CERT; Intel; ISC; JPCERT/CC; Juniper; KrCERT/CC; Larry Cashdollar; Lenovo; MarkLogic; McAfee; Micro Focus; Microsoft; MITRE (primary CNA); Mozilla; Nvidia; Objective Development; OpenSSL; Oracle; Puppet; Rapid 7; Red Hat; Silicon Graphics; Symantec; Talos; TIBCO; VMware; and Yandex.

For more information about requesting CVE ID numbers from CNAs, visit Request a CVE ID.

"CVE-2005-4900" Is SHA-1 Collision Attack "SHAttered"
February 23, 2017 | Share this article

Researchers have published a practical method for crafting a file that shares a valid SHA-1 signature with another file. This vulnerability in SHA-1 was assigned CVE ID CVE-2005-4900 in 2016. The vulnerability described in this new research is the same as the vulnerability described in CVE-2005-4900, and this CVE ID can be used when referencing this vulnerability.

For more information on the results of this additional research, visit https://security.googleblog.com/2017/02/announcing-first-sha1-collision.html or http://shattered.io/.

1 Product from Avatares Foundation Now Registered as Officially "CVE-Compatible"
February 23, 2017 | Share this article

cve compatible image

One additional cyber security product has achieved the final stage of MITRE's formal CVE Compatibility Process and is now officially "CVE-Compatible." The product is now eligible to use the CVE-Compatible Product/Service logo, and a completed and reviewed "CVE Compatibility Requirements Evaluation" questionnaire is posted for the product as part of the organization's listing on the CVE-Compatible Products and Services page on the CVE website. A total of 152 products to-date have been recognized as officially compatible

The following product is now registered as officially "CVE-Compatible":
Avatares Foundation -
Pandora-CSF

Use of the official CVE-Compatible logo will allow system administrators and other security professionals to look for the logo when adopting vulnerability management products and services for their enterprises and the compatibility process questionnaire will help end-users compare how different products and services satisfy the CVE compatibility requirements, and therefore which specific implementations are best for their networks and systems.

For additional information about CVE compatibility and to review all products and services listed, visit the CVE Compatibility Process and CVE-Compatible Products and Services.

NOTICE: CVE Request Web Form – Outage from 6:00 p.m.-7:00 p.m. EDT on February 21
February 17, 2017 | Share this article

Due to scheduled maintenance, the CVE Request Web Form will be temporarily unavailable from 6:00 p.m. until 7:00 p.m. Eastern time on Tuesday, February 21, 2017.

This temporary outage affects requests to MITRE only. All other CVE Numbering Authorities (CNAs) can still be contacted during this time to request CVE IDs.

We apologize for any inconvenience. Please contact cve@mitre.org with any comments or concerns.

NOTICE: CVE Request Web Form – Outage from 8:00 p.m.-10:00 p.m. EDT on February 15
February 14, 2017 | Share this article

Due to scheduled maintenance, the CVE Request Web Form will be temporarily unavailable from 8:00 p.m. until 10:00 p.m. Eastern time on Wednesday, February 15, 2017.

This temporary outage affects requests to MITRE only. All other CVE Numbering Authorities (CNAs) can still be contacted during this time to request CVE IDs.

We apologize for any inconvenience. Please contact cve@mitre.org with any comments or concerns.

Minutes from CVE Board Teleconference Meeting on January 25 Now Available
February 10, 2017 | Share this article

The CVE Board held a teleconference meeting on January 25, 2017. Read the meeting minutes.

Minutes from CVE Board Teleconference Meeting on January 11 Now Available
February 2, 2017 | Share this article

The CVE Board held a teleconference meeting on January 11, 2017. Read the meeting minutes.

New CVE Board Member from Black Duck Software
January 26, 2017 | Share this article

William Cox of Black Duck Software, Inc. has joined the CVE Board.

Read the full announcement and welcome message in the CVE Board email discussion list archive.

TIBCO Software Added as CVE Numbering Authority (CNA)
January 19, 2017 | Share this article

TIBCO Software, Inc. is now a CVE Numbering Authority (CNA) for TIBCO, Talarian, Spotfire, Data Synapse, Foresight, Kabira, Proginet, LogLogic, StreamBase, JasperSoft, and Mashery issues only.

CNAs are OS and product vendors, developers, security researchers, and research organizations that assign CVE IDs to newly discovered issues without directly involving MITRE in the details of the specific vulnerabilities, and include the CVE ID numbers in the first public disclosure of the vulnerabilities.

CNAs are the main method for requesting a CVE ID number. The following 48 organizations currently participate as CNAs: Adobe; Apache; Apple; BlackBerry; Brocade; Canonical; CERT/CC; Check Point; Cisco; Debian GNU/Linux; Dell EMC; Distributed Weakness Filing Project; F5; Fortinet; FreeBSD; Google; HackerOne; HP; Hewlett Packard Enterprise; Huawei; IBM; ICS-CERT; Intel; ISC; JPCERT/CC; Juniper; KrCERT/CC; Larry Cashdollar; Lenovo; MarkLogic; McAfee; Micro Focus; Microsoft; MITRE (primary CNA); Mozilla; Nvidia; Objective Development; OpenSSL; Oracle; Puppet; Rapid 7; Red Hat; Silicon Graphics; Symantec; Talos; TIBCO; VMware; and Yandex.

For more information about requesting CVE ID numbers from CNAs, visit Request a CVE ID.

Researcher Reservation Guidelines Document Now Available
January 12, 2017 | Share this article

The Researcher Reservation Guidelines document is now available on the CVE website. This document provides step-by-step guidelines on how to reserve a CVE ID(s) before publicizing a new vulnerability so that CVE IDs can be included in the initial public announcement of the vulnerability and can be used to track vulnerabilities.

CVE Updates Its Definition of "Vulnerability"
January 12, 2017 | Share this article

CVE has updated its definition of the term vulnerability as follows: "A 'vulnerability' is a weakness in the computational logic (e.g., code) found in software and some hardware components (e.g., firmware) that, when exploited, results in a negative impact to confidentiality, integrity, OR availability. Mitigation of the vulnerabilities in this context typically involves coding changes, but could also include specification changes or even specification deprecations (e.g., removal of affected protocols or functionality in their entirety)."

Visit the Terminology page for additional information. You may also contact us with any comments or concerns.

FOCUS ON: The Significance and Meaning of the Year Portion of a CVE Identifier
January 12, 2017 | Share this article

CVE Identifiers (CVE IDs) have the format CVE-YYYY-NNNNN. The YYYY portion is the year that the CVE ID was assigned OR the year the vulnerability was made public (if before the CVE ID was assigned).

The year portion is not used to indicate when the vulnerability was discovered, but only when it was made public or assigned.

Examples:

NOTE: Neither the date when a vulnerability was introduced into a product, or the date when a vulnerability was fixed in a product, factor into what year is indicated in the CVE ID assigned to that vulnerability.

Visit the CVE Identifiers section of the FAQs page for answers to other questions about CVE IDs. You may also contact us with any comments or concerns.

Page Last Updated or Reviewed: August 16, 2017