Home / Docs / Security model

Reporting a vulnerability

Release v0.4.0

Una makes promises about programs: that they use no authority beyond what their headers declare, that labeled data does not flow where its labels forbid, and that proven contracts hold. A way to break one of those promises is a security problem, and we want to hear about it.

Reporting a vulnerability

Please report vulnerabilities privately, not in a public issue. Use any of these channels:

Include:

We will acknowledge your report, keep you informed while we work on it, and thank you by name in the release notes unless you prefer otherwise. Please give us a reasonable time to release a fix before you disclose the problem publicly.

Supported versions

Una is a research language and is not ready for production use; edition 0.4, the edition of v0.4.0, is a preview (ADR 0121). Fixes go into the next release. Past fixes were also released as patches of the lines v0.3.x (branch release/v0.3) and v0.1.x (branch release/v0.1): each advisory in docs/security/advisories.md names the releases that fix it, and says when a line is not fixed. A version is fixed only when an advisory names a release that carries the fix.

Scope

In scope:

Out of scope:

A soundness bug that does not put anyone at risk can be reported in public with the soundness report template. If you are unsure, report privately.