CVE Program

CVE ID Assignment

How we assign CVE IDs and publish CVE Records for vulnerabilities in Sigenergy products and services.

Status: Sigenergy has applied to become a CVE Numbering Authority (CNA) under the CVE Program. Until the authorization is complete, CVE IDs for our advisories are requested through a CNA, and entries in the CVE Index remain marked Pending assignment. The process described on this page applies from the date our authorization takes effect.

Scope of coverage

We assign CVE IDs and publish CVE Records for cybersecurity vulnerabilities affecting:

Third-party components

Where an upstream supplier is itself a CNA, we notify that CNA and defer first-refusal assignment, in line with CNA Rule 4.2.16.6. We assign a CVE ID for such a vulnerability only where no upstream CNA exists, or where the upstream CNA declines to assign.

Out of scope

Vulnerabilities that exist solely in a third-party product or service, and that cannot be reached through, and do not affect the security of, a Sigenergy product or service, are outside our scope.

How to request a CVE ID

  1. Report the issue. Email csirt@sigenergy.cloud or use the vulnerability report form. For sensitive details, encrypt with our PGP key.
  2. We validate it. We reproduce the issue in a controlled environment and confirm the affected products and versions, and whether it meets the CVE Program definition of a vulnerability.
  3. We confirm the CVE ID. We send you the assigned CVE ID before publication, and you may cite it in your write-up.
  4. We agree a disclosure date. The date is coordinated with you and with any affected third party.
  5. We publish. A security advisory and the corresponding CVE Record are published together. Reporters who wish to be named are credited on our acknowledgements page.
Requests outside our scope are referred to the appropriate CNA, and to the supplier of the affected product where that supplier is not us.

Response and publication times

ActionTarget
First response to a vulnerability reportWithin 24 hours for critical issues and 3 business days for high severity, as set out in our vulnerability handling process
Response to a CVE ID assignment request3 business days
CVE ID assigned and confirmed to the reporter5 business days after validation
CVE Record publishedWithin 24 hours of public disclosure, and never later than 72 hours (CNA Rule 4.5.1)
CVE Record updates5 business days after material new information becomes available
These are service objectives for requests concerning Sigenergy products, consistent with the response times published in our vulnerability handling process.

How CVE IDs are assigned

End-of-life products

We assign CVE IDs for vulnerabilities affecting end-of-life products when the vulnerability is, or is expected to be, publicly disclosed, and we tag those CVE Records unsupported-when-assigned (CNA Rule 4.2.17.1). We do not assign a CVE ID solely because a product has reached end-of-life (CNA Rule 4.2.17.7).

Contact

Published CVE Records appear on the CVE List at cve.org. This page is reviewed whenever our scope, contact details or the CNA Rules change.