How Aster receives, triages, fixes, scores and discloses vulnerabilities, and how it prepares for EU Cyber Resilience Act reporting.
Reporters should start with Security policy. This document describes what happens next. Status: the process is defined and reports go to [email protected]; the CNA arrangement is not yet confirmed (see Aster Trust Center).
Process
| Stage | What happens | Owner |
|---|---|---|
| 1. Receive | Report arrives at [email protected]. A private tracking record is opened. Reports are never discussed in public channels. | Security lead |
| 2. Acknowledge | Reporter gets an acknowledgement within 5 business days. | Security lead |
| 3. Triage | Reproduce, decide valid / invalid / duplicate, identify affected versions and Cargo features, score with CVSS 4.0, and decide whether it is actively exploited. Target: 15 business days. | Security lead plus one engineer |
| 4. Fix | Fix on a private branch with a regression test (and a fuzz corpus entry where it applies). Independent review before merge. | Engineer, reviewer |
| 5. Verify and release | Build, sign and publish the fixed version (Releases: signing, provenance and verification). Update the SBOM and VEX statement (Supply chain: SBOM, licences, advisories, vetting, reproducibility). | Release owner |
| 6. Advise | Publish the advisory: affected and fixed versions, CVSS 4.0 vector, CWE, workaround, credit. Customers are notified directly. Request a CVE ID where criteria are met. | Security lead |
| 7. Review | Within 30 days after release: root cause, whether a class of bug can be removed (a lint, a fuzz target, an API change). | Engineering |
Role names are functions, not individuals; until the team is larger one person may hold several.
Severity scoring
We score with CVSS v4.0 (FIRST) and publish the full vector, not only the number. CVSS measures technical severity, so we add context in the advisory: whether a default configuration is affected, whether the vulnerable code is reachable only with an off-by-default feature (for example net-sync), and whether it is exploited. Severity bands follow CVSS: Critical 9.0-10.0, High 7.0-8.9, Medium 4.0-6.9, Low 0.1-3.9.
| Band | Fix target after confirmation |
|---|---|
| Critical | 30 days or less; mitigation sooner where possible |
| High | 60 days |
| Medium / Low | next scheduled release, and within 90 days where practical |
These are targets for a small team and may be missed; if we expect to miss one we tell the reporter and affected users.
Advisories and CVEs
- Advisories are published with the release that contains the fix, and are linked from the release notes.
- Each advisory carries: identifier (CVE when assigned), title, summary, affected versions, fixed versions, CVSS 4.0 vector and score, CWE, workarounds, credits and timeline.
- Machine-readable status for downstream users is given as a VEX statement (CSAF or OpenVEX) next to the SBOM.
- CVE IDs are requested through a CNA that can assign for this product. to be decided has not been decided. Until it is, we publish our own advisory identifier and state that a CVE is pending.
- Vulnerabilities in third-party dependencies are tracked from the SBOM against public advisory databases and handled as in Supply chain: SBOM, licences, advisories, vetting, reproducibility.
Coordinated disclosure
Default window: 90 days from report, shorter when a fix is already available. Active exploitation shortens it. The reporter is told the planned date and credited unless they decline. See Security policy.
EU Cyber Resilience Act reporting readiness
Whether Aster's maintainer counts as a manufacturer under Regulation (EU) 2024/2847 depends on commercial facts that are not decided (see EU Cyber Resilience Act readiness); we prepare to the stricter reading. Article 14 obliges a manufacturer (and, to the extent it is involved in development, a steward) to report to the CSIRT designated as coordinator and to ENISA, through the single reporting platform that ENISA establishes under Article 16:
| Trigger | Deadline | Content |
|---|---|---|
| Actively exploited vulnerability, Art. 14(2) | 24 hours after becoming aware: early warning | Early warning, including the Member States where the product is available |
| Same | 72 hours: notification | Product, nature of the exploit and vulnerability, corrective or mitigating measures taken and users can take, how sensitive the information is |
| Same | 14 days after a corrective or mitigating measure is available: final report | Description, severity and impact, malicious actor information if known, patch details, mitigation |
| Severe incident having an impact on the security of the product, Art. 14(4) | 24h early warning, 72h notification, final report within one month of the notification | Same structure |
Dates: the Article 14 reporting obligations apply from 11 September 2026. The rest of the regulation applies from 11 December 2027. Both dates are in Article 71 of the regulation (https://eur-lex.europa.eu/eli/reg/2024/2847/oj).
What we have in place and what is open:
| Item | State |
|---|---|
| Written process and decision tree for "actively exploited" | This document; the 24h clock starts when we become aware |
| Named duty contacts (primary and backup) who can file within 24 hours, including weekends | Open: needs named people |
| Account on the ENISA single reporting platform | Open: not registered. The platform's access arrangements must be checked once ENISA publishes them |
| Identify the coordinating CSIRT for our Member State of main establishment | Open: depends on where the maintainer is established; the maintainer is in the US, so the rules for entities established outside the EU must be confirmed with counsel |
| Report templates for the three stages | Planned; will be added under docs/trust/ |
| Customer notification channel (the duty to inform affected users) | Planned: public advisory, release notes and a mailing list or watch feature on the repository |
| Tabletop exercise | Planned before the first public release |
This describes our understanding of the regulation and is not legal advice. Read the regulation text and the Commission and ENISA guidance, and confirm the details with counsel.