CVE ID Assignment
How we assign CVE IDs and publish CVE Records for vulnerabilities in Sigenergy products and services.
Scope of coverage
We assign CVE IDs and publish CVE Records for cybersecurity vulnerabilities affecting:
- hardware designed, manufactured, sold or supported under the Sigenergy brand — energy storage systems, solar inverters, EV chargers, and the related accessories, sensors, meters and communication modules;
- firmware, embedded software, device management software and over-the-air update mechanisms for those products;
- Sigenergy-operated cloud services, APIs and backend platforms that connect to or manage those products, including SigenCloud;
- Sigenergy mobile and web applications, including installer and end-customer portals;
- SDKs, libraries and developer tools released by Sigenergy.
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
- Report the issue. Email csirt@sigenergy.cloud or use the vulnerability report form. For sensitive details, encrypt with our PGP key.
- 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.
- We confirm the CVE ID. We send you the assigned CVE ID before publication, and you may cite it in your write-up.
- We agree a disclosure date. The date is coordinated with you and with any affected third party.
- 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.
Response and publication times
| Action | Target |
|---|---|
| First response to a vulnerability report | Within 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 request | 3 business days |
| CVE ID assigned and confirmed to the reporter | 5 business days after validation |
| CVE Record published | Within 24 hours of public disclosure, and never later than 72 hours (CNA Rule 4.5.1) |
| CVE Record updates | 5 business days after material new information becomes available |
How CVE IDs are assigned
- One CVE ID per independently fixable vulnerability. Where we cannot determine whether two issues are independently fixable, we assign a single CVE ID (CNA Rule 4.2.12).
- Products that share the same vulnerable code share one CVE ID (CNA Rule 4.2.13).
- Interdependent conditions that together cause a single vulnerability receive a single CVE ID (CNA Rule 4.2.15).
- Updating a dependency is not by itself a vulnerability: the advisory references the upstream CVE ID rather than assigning a new one (CNA Rule 4.1.11).
- Vulnerabilities in upstream components are referred to the upstream CNA first (CNA Rule 4.2.16.6).
- Test and example records use
CVE-1900-IDs and are never treated as live data (CNA Rule 5.4.1).
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
- CVE ID requests and questions: csirt@sigenergy.cloud — please put
CVEin the subject line. - Encrypted reports: PGP key.
- Related pages: PSIRT · Responsible Disclosure Policy · Security Advisories · CVE Index.
