Re: Agenda for CVE Board Meeting Wednesday, 15 November 2017

To: jericho <jericho@attrition.org>, Kurt Seifried <kseifried@redhat.com>
Subject: Re: Agenda for CVE Board Meeting Wednesday, 15 November 2017
From: Art Manion <amanion@cert.org>
Date: Wed, 15 Nov 2017 16:59:28 -0500
Authentication-results: spf=none (sender IP is 129.83.29.3) smtp.mailfrom=LISTS.MITRE.ORG; mitre.mail.onmicrosoft.com; dkim=none (message not signed) header.d=none;mitre.mail.onmicrosoft.com; dmarc=fail action=none header.from=cert.org;
Cc: cve-editorial-board-list <cve-editorial-board-list@LISTS.MITRE.ORG>
Delivery-date: Thu Nov 16 07:59:48 2017
Dkim-filter: OpenDKIM Filter v2.11.0 veto.sei.cmu.edu vAFLxV2l033232
In-reply-to: <2ed0a011-d988-ee4e-7477-9213b9840c65@cert.org>
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: <DM5PR09MB1164A57009F7CC7D275E262AB1280@DM5PR09MB1164.namprd09.prod.outlook.com> <MWHPR09MB14566C5E6F01CE19610BB9E2A1280@MWHPR09MB1456.namprd09.prod.outlook.com> <CY4PR09MB14959ACE05638F0FFBD1E464F0290@CY4PR09MB1495.namprd09.prod.outlook.com> <CANO=Ty3Bw9eT7qsSVBzRs65+xEbhDp3kpVciqWZLaP+K+kZQfA@mail.gmail.com> <alpine.LNX.2.00.1711151207550.22101@forced.attrition.org> <2ed0a011-d988-ee4e-7477-9213b9840c65@cert.org>
Sender: <owner-cve-editorial-board-list@lists.mitre.org>
Spamdiagnosticmetadata: 5952c28dcc454f0789fb433d26f936ef
Spamdiagnosticoutput: 1:2
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.4.0

On 2017-11-15 16:32, Art Manion wrote:

> (*) YYYY is meant to be the year the vulnerability (not the CVE ID) 
> was published, right?  Not year the CVE ID was requested, assigned, 
> or published?

CVE web site says:

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3222

Date Entry Created: 20161205

Disclaimer: The entry creation date may reflect when the CVE-ID was 
allocated or reserved, and does not necessarily indicate when this 
vulnerability was discovered, shared with the affected vendor, publicly 
disclosed, or updated in CVE. 

Best reasonable guess at ${date_public} really should be in CVE 
entries.  Possibly also ${date_last_updated}, which might be obtainable 
from github?

 - Art

References:
- Agenda for CVE Board Meeting Wednesday, 15 November 2017
  - From: Common Vulnerabilities & Exposures <cve@mitre.org>
- RE: Agenda for CVE Board Meeting Wednesday, 15 November 2017
  - From: "Coffin, Chris" <ccoffin@mitre.org>
- Re: Agenda for CVE Board Meeting Wednesday, 15 November 2017
  - From: "Waltermire, David A. (Fed)" <david.waltermire@nist.gov>
- Re: Agenda for CVE Board Meeting Wednesday, 15 November 2017
  - From: Kurt Seifried <kseifried@redhat.com>
- Re: Agenda for CVE Board Meeting Wednesday, 15 November 2017
  - From: jericho <jericho@attrition.org>
- Re: Agenda for CVE Board Meeting Wednesday, 15 November 2017
  - From: Art Manion <amanion@cert.org>

Prev by Date: Re: Agenda for CVE Board Meeting Wednesday, 15 November 2017
Next by Date: Re: CVE for services - already done? CVE-2017-10128
Previous by thread: Re: Agenda for CVE Board Meeting Wednesday, 15 November 2017
Next by thread: Canceled: Bi-Weekly CVE Board Meeting
Index(es):
- Date
- Thread