Technical impact
NORA is a self‑hosted artifact registry that authenticates the token‑management UI but, prior to version 0.9.5, it does not enforce administrator‑level authorization for state‑changing token operations. The middleware allows a bearer token with write rights or a write‑capable OIDC identity to call endpoints that list all tokens or revoke tokens based solely on a role.can_write() check. Consequently, any authenticated user who can write can enumerate the identifiers, owners, roles, descriptions, expiries, and last‑used timestamps of every token in the system. A bearer token possessing write privileges can also revoke arbitrary admin or service tokens, effectively disrupting the registry and forcing credential recovery. This flaw represents a Missing Permissions weakness (CWE‑862) that can lead to privilege escalation and denial of service for the registry occupant.
Affected Systems
The issue affects the getnora‑io/nora artifact registry software. Versions prior to 0.9.5 are vulnerable. The vulnerability is relevant to deployments of the self-hosted registry that expose the token‑management UI or API endpoints (e.g., /ui/tokens, /api/ui/tokens).
Risk and Exploitability
The CVSS score for this vulnerability is 7.1, indicating a medium‑high severity. EPSS is currently not available, but the flaw has not been reported as a known exploited vulnerability in the CISA KEV catalogue. The attack requires an authenticated bearer token that has write permissions or a write‑capable identity. Attackers with such credentials can enumerate all tokens and revoke privileged tokens, causing a denial of service or facilitating further credential compromise. The lack of an administrative check makes the vulnerability exploitable without needing elevated privileges beyond a standard write user.