diff --git a/src/views/ProgramOrganization/WorkingGroups.vue b/src/views/ProgramOrganization/WorkingGroups.vue index 323fe2670..10f61264e 100644 --- a/src/views/ProgramOrganization/WorkingGroups.vue +++ b/src/views/ProgramOrganization/WorkingGroups.vue @@ -84,7 +84,7 @@ CVE Services Project
  • - CVE List GitHub Automation Project + CVE List Bulk Downloads Repository
  • @@ -93,9 +93,6 @@
  • AWG GitHub Repository
  • -
  • - CVE Program Automation Website -
  • diff --git a/src/views/ResourcesSupport/AllResources/CveServices.vue b/src/views/ResourcesSupport/AllResources/CveServices.vue index a8876098a..5f3f27555 100644 --- a/src/views/ResourcesSupport/AllResources/CveServices.vue +++ b/src/views/ResourcesSupport/AllResources/CveServices.vue @@ -42,17 +42,31 @@

    Current Status

    - As of March 29, 2023, the CVE Program achieved hard deploy of CVE Services 2.1, - CVE JSON 5.0, - and the CVE JSON 5.0 Bulk Download - capability. “Hard deploy” means issues with the CVE Services - “soft - deploy” - phase that began in October 2022 and ended in March 2023 have been addressed, and the CVE JSON 5.0 Bulk Download - capability is available for community use. For hard deploy known issues click - here. - To learn more about the new bulk download capability, click - here. + As of March 29, 2023, the CVE Program achieved hard deploy of CVE Services 2.1, + CVE JSON 5.0, + and the CVE JSON 5.0 Bulk Download + capability. “Hard deploy” means issues with the CVE Services “soft deploy” phase that began in October 2022 and ended in March 2023 + have been addressed, and the CVE JSON 5.0 Bulk Download capability is available for community use. To learn more about the new bulk + download capability, click here. +

    +

    Known Issues

    +

    + CVE Record Retrieval returning over 500 records may return incomplete results +

    +

    + Added: 4/14/2023 — In a situation where the following conditions are present: (1) A CNA submits + a request for a CVE Record lookup that results in over 500 records being returned, AND (2) that CNA owns records that are being + updated (either by the CNA or the Secretariat) at the exact instance the retrieval is processing. The results returned may not be + complete (i.e., one record may be dropped). It is suggested that if CNAs are repeatedly retrieving more than 500 records from CVE + Services (using the GET /cve-id endpoint), that they contact the Secretariat for guidance on how best to implement/use this function + in their client. +

    +

    + NOTE: Please report any anomalous behavior in CVE Services to the CVE Automation Working + Group (AWG) at awg@cve-cwe-programs.groups.io. Questions about your chosen + CVE Services Client + should be directed to the client developers (learn more + here).

    CVE Services Architecture

    @@ -401,11 +415,11 @@ If a CNA or individual is interested in fielding its own CVE Services client, the CVE Services Server API documentation will provide the interface specification to allow you to develop your own client. Also, a CVE Services “test environment” is available.

    -

    CVE Services API

    +

    CVE Services API

    Of specific interest in the API documentation are these four endpoints, which are important functions for publishing CVE Records to @@ -422,22 +436,22 @@ Additionally, concrete examples of the data (referred to as a “CNA Container”) to submit via a POST /cve/{id}/cna endpoint (or PUT /cve/{id}/cna endpoint) can be found at the following links:

    - -

    Test Environment

    + +

    Test Environment

    A CVE Services “Test Environment” consisting of the CVE Services test instance API noted above and a CVE website test instance @@ -495,15 +509,6 @@

  • Downloads page
  • cvelistV5 repository on GitHub
  • -

    CVE Services resources hosted on the CVE Automation Transition website:

    -

    Other helpful resources: