lunary-ai/lunary: Insecure Storage of Sensitive Information
CVE-2024-3501 is a high-severity insecure storage of sensitive information vulnerability in lunary-ai/lunary from Lunary-ai, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists version 1.2.6 as the first without the flaw, so updating lunary-ai/lunary to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.41% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update lunary-ai/lunary to 1.2.6 or a later version.
- Update Lunary to 1.2.6 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Lunary-ai | lunary-ai/lunary | before 1.2.6 | 1.2.6 |
| Lunary | Lunary | before 1.2.6 | 1.2.6 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.1 | High | NVD |
| CVSS 3.1 | 9.1 | Critical | CISA (ADP) |
| CVSS 3.0 | 9.1 | Critical | CNA (huntr.dev) |
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Insecure Storage of Sensitive Information
The product stores sensitive information without properly limiting read or write access by unauthorized actors.
More Insecure Storage of Sensitive Information vulnerabilities (CWE-922)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- github.com/lunary-ai/lunary/commit/17e95f6c99c7d5ac4ee5451c5857b97a12892c74
- huntr.com/bounties/8fdfdb9d-10bd-4f00-8004-d5baabc20c6eIssue Tracking, Third Party Advisory
Other vulnerabilities in lunary-ai/lunary
- 8.8 High severity
- 8.8 High severity
- 9.6 Critical severity
- 7.7 High severity
- 8.1 High severity
- 7.1 High severity
Recent Insecure Storage of Sensitive Information vulnerabilities
- 8.1 High severity
- 9.1 Critical severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 9.9 Critical severity
Spotted an error? Tell us.