Search guides, workflows, and reference pages.

Docs/Tools

tools/cve-org/

Capability: contract:cve-authority

Kind: implementation

Vendor: CVE.org

Read-only CVE.org publication-state check. Given a CVE ID, it asks the CVE Services API v2 whether the record is RESERVED, PUBLISHED or REJECTED on cve.org; it submits nothing and needs no credentials. security-issue-sync uses it to confirm that a record cleared in the CNA tool has propagated to the public registry before proposing the “CVE is live” reporter notification. Publishing a record is the CNA tool’s job (for ASF projects, tools/cve-tool-vulnogram/), not this adapter’s. See tool.md for the recipe and the state values.

Prerequisites

  • Runtime: Python 3.11+ via uv (through tools/vetted-ops dispatcher).
  • CLIs: vetted-op-read (from tools/vetted-ops) and jq.
  • Credentials / auth: None — cve.org is the public CVE registry and the CVE Services API has no auth.
  • Network: cveawg.mitre.org (CVE Services API v2), routed through vetted-ops HTTP read backend; www.cve.org (the HTML record); optionally nvd.nist.gov for the alternative public registry.

Configuration

None. The check runs the same way whichever CNA tool the project uses (cve_authority.tool in <project-config>/project.md), since every CNA tool publishes to the same public registry. Direct submission to CVE Services (cve_authority.tool: cve-org-direct) is a separate, planned adapter — see the CVE-tool table in tools/cve-tool/README.md — and is not implemented here.

Suggest a change