|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Current and future CVE states
- To: Kurt Seifried <kurt@seifried.org>, cve-editorial-board-list <cve-editorial-board-list@LISTS.MITRE.ORG>
- Subject: Re: Current and future CVE states
- From: Art Manion <amanion@cert.org>
- Date: Wed, 3 May 2017 18:12:25 -0400
- Authentication-results: spf=none (sender IP is 129.83.29.2) smtp.mailfrom=LISTS.MITRE.ORG; mitre.mail.onmicrosoft.com; dkim=none (message not signed) header.d=none;mitre.mail.onmicrosoft.com; dmarc=none action=none header.from=cert.org;
- Delivery-date: Thu May 4 07:43:56 2017
- Dkim-filter: OpenDKIM Filter v2.11.0 veto.sei.cmu.edu v43MCWGk005104
- In-reply-to: <CABqVa3_POGWZecLZE9+DeOu1GPNFxs05T8DgcEKhzoz6Ex9rcA@mail.gmail.com>
- List-help: <mailto:LISTSERV@LISTS.MITRE.ORG?body=INFO%20CVE-EDITORIAL-BOARD-LIST>
- List-owner: <mailto:CVE-EDITORIAL-BOARD-LIST-request@LISTS.MITRE.ORG>
- List-subscribe: <mailto:CVE-EDITORIAL-BOARD-LIST-subscribe-request@LISTS.MITRE.ORG>
- List-unsubscribe: <mailto:CVE-EDITORIAL-BOARD-LIST-unsubscribe-request@LISTS.MITRE.ORG>
- References: <CABqVa3_POGWZecLZE9+DeOu1GPNFxs05T8DgcEKhzoz6Ex9rcA@mail.gmail.com>
- Sender: <owner-cve-editorial-board-list@lists.mitre.org>
- Spamdiagnosticmetadata: 6cdb8bfc89744bd8bfee511e3e65aa05
- Spamdiagnosticoutput: 1:2
- User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
On 2017-05-03 15:36, Kurt Seifried wrote: > DUPLICATE_OF [CVE] > > SPLIT_TO [list of CVEs] > > MERGED_TO [lCVE] If we're going to get into relationships between vulnerabilities -- which is related to, but possibly a bit beyond state -- I'd like to brief the board (or automation group) on vxref, which is a structured relationship system. https://github.com/FIRSTdotorg/vrdx-sig-vxref-wip/tree/master/vxref https://github.com/CERTCC-Vulnerability-Analysis/Vulnerability-Data-Archive-Tools Regards, - Art
- Follow-Ups:
- Re: Current and future CVE states
- From: "Landfield, Kent" <Kent_Landfield@McAfee.com>
- Re: Current and future CVE states
- References:
- Current and future CVE states
- From: Kurt Seifried <kurt@seifried.org>
- Current and future CVE states
- Prev by Date: Current and future CVE states
- Next by Date: Re: Current and future CVE states
- Previous by thread: Current and future CVE states
- Next by thread: Re: Current and future CVE states
- Index(es):