CVE intelligence and bounded remediation
CVE-2024-3501 — Lunary Lunary security vulnerability
In lunary-ai/lunary versions up to and including 1.2.5, an information disclosure vulnerability exists due to the inclusion of single-use tokens in the responses of `GET /v1/users/me` and `GET /v1/users/me/org` API endpoints. These tokens, intended for sensitive operations such as password resets or account verification, are exposed to unauthorized actors, potentially allowing them to perform actions on behalf of the user. This issue was addressed in version 1.2.6, where the exposure of single-use tokens in user-facing queries was mitigated.
- Severity
- Critical
- CVSS
- 9.1 (3.1)
- Published
- 2024-11-14
- CISA KEV
- Not currently listed
- Ecosystem
- software/application
- Weaknesses
- CWE-922
Affected products
- lunary / lunary
Matched remediation archetype
Information disclosure and sensitive data exposure
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Trace sensitive data through responses, errors, logs, metrics, traces, caches, exports, files, backups, and client bundles.
- Identify affected subjects, tenants, retention windows, access controls, and downstream copies without opening unnecessary sensitive records.
- Review metadata, timing, status, length, and existence signals as well as direct content disclosure.
Remediate safely
- Minimize collection and output, apply field-level authorization and redaction at a centralized boundary, and return generic external errors.
- Remove secrets and sensitive data from logs, artifacts, URLs, caches, and client-side bundles; rotate credentials that may have been exposed.
- Update the affected component and add synthetic-data tests for response, error, observability, and export paths.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.