How to report a vulnerability in Aster, what to expect from us, and which versions we fix.
The Aster SDK and examples are MIT licensed; the Aster Runtime is under the Aster Runtime EULA. Aster is developed and maintained by Barnyard Greens LLC. This policy covers the Aster rendering and UI toolkit and the release artifacts we publish. The full process is in Vulnerability handling policy.
Reporting a vulnerability
Report privately by email to [email protected]. Please do not open public issues or post details publicly before we have coordinated disclosure with you.
Include if you can:
- the affected version or commit, platform and Cargo features used;
- a minimal reproducer or proof of concept (for example a document, image, font or input sequence that triggers the problem);
- the impact you believe it has;
- whether you intend to publish, and any deadline you are working to.
If you need an encrypted channel, ask in your first message and we will agree one. We do not run a bug bounty at this time.
What we do
These are targets, not guarantees. We are a small team and have set them so that we can meet them.
| Step | Target |
|---|---|
| Acknowledge your report | within 5 business days |
| Initial assessment (valid or not, severity, affected versions) | within 15 business days |
| Fix or mitigation for a confirmed critical or high issue | 30 days for critical, 60 days for high, best effort for others, from confirmation |
| Status updates while the issue is open | at least every 30 days |
If a vulnerability is being actively exploited we treat it as urgent; see EU Cyber Resilience Act readiness for the reporting duties that may apply.
Coordinated disclosure
Our default is 90 days from your report to public disclosure, or earlier once a fix is released. We will agree a date with you; if a fix needs longer we will ask, and explain why, before the deadline. We credit reporters in the advisory unless you prefer not to be named. We consider good-faith research that follows this policy (no access to other people's data, no service degradation, stopping at a proof of concept) to be authorized, and we will not pursue it. The legal wording of this safe-harbor statement is pending review by counsel.
Scope
In scope:
- the core crates (
aster-ui,hudlife-core,hudlife-cpu,hudlife-opentype) andaster-appkit; - parsers and decoders for untrusted input (fonts, images, vector paths, documents, sync messages);
- memory-safety, denial-of-service (panics, unbounded memory or CPU on untrusted input) and logic flaws that break a documented guarantee, including the "no data" claims in No data: what Aster does and does not do;
- our release artifacts, signatures and SBOMs.
Out of scope:
- vulnerabilities in your application or in third-party code we only depend on (report those upstream; tell us too, and we will track them in our advisories);
- the lab, demo and benchmark binaries, and platform shell code that is not shipped as a product;
- social engineering, physical attacks, and reports from automated scanners without a demonstrated impact;
- the
net-synctransport being unencrypted. This is documented; wrap it in your own TLS or VPN. A flaw in message parsing is in scope.
CVEs and advisories
For confirmed vulnerabilities in released versions we publish a security advisory with affected and fixed versions, a CVSS 4.0 score, and credit, and we request a CVE ID through a CNA (see Vulnerability handling policy). Advisories are listed in the release notes (Releases: signing, provenance and verification).
Supported versions
Aster has not reached 1.0. Today only the latest release, and the development head, receive security fixes. After 1.0 the window in Support and versioning policy applies.
Check a release
How to check a release without the source is in Verifying a release.
