# CVE-2024-3502: Exposure of Sensitive Information in lunary-ai/lunary

> Authenticated users can access sensitive account recovery hashes via API endpoints, potentially enabling account takeover attacks.

- **Severity:** Critical 9.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Nov 2024
- **Updated:** 15 Oct 2025
- **Also known as:** GHSA-cgjv-g7x3-8jrm

## What is CVE-2024-3502?

CVE-2024-3502 is a critical vulnerability in Lunary Lunary, published on 14 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In lunary-ai/lunary versions up to and including 1.2.5, an information disclosure vulnerability exists where account recovery hashes of users are inadvertently exposed to unauthorized actors. This issue occurs when authenticated users inspect responses from `GET /v1/users/me` and `GET /v1/users/me/org` endpoints. The exposed account recovery hashes, while not directly related to user passwords, represent sensitive information that should not be accessible to unauthorized parties. Exposing these hashes could potentially facilitate account recovery attacks or other malicious activities. The vulnerability was addressed in version 1.2.6.

Weakness: CWE-922 (Insecure Storage of Sensitive Information), CWE-201 (Insertion of Sensitive Information Into Sent Data)

## Which versions are affected by CVE-2024-3502?

It affects 1 product.


Products: Lunary Lunary.

## How do I fix CVE-2024-3502?

No fix has been published for CVE-2024-3502 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-3502 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-3502 exists.

## Other vulnerabilities in Lunary Lunary

- [CVE-2024-8999](https://insights.sbomify.com/CVE-2024-8999/): Improper Access Control in lunary-ai/lunary (critical 9.8)
- [CVE-2024-9095](https://insights.sbomify.com/CVE-2024-9095/): Improper Authorization in lunary-ai/lunary (critical 9.8)
- [CVE-2024-7456](https://insights.sbomify.com/CVE-2024-7456/): SQL Injection in lunary-ai/lunary (critical 9.8)
- [CVE-2024-4146](https://insights.sbomify.com/CVE-2024-4146/): Incorrect Authorization in lunary-ai/lunary (critical 9.8)
- [CVE-2024-5386](https://insights.sbomify.com/CVE-2024-5386/): Account Hijacking via Password Reset Token Leak in lunary-ai/lunary (critical 9.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-3502 and fix it if it is affected.

What it is: CVE-2024-3502 is a critical vulnerability in Lunary Lunary, published on 14 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-3502 exists.

Affected product: Lunary Lunary. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-3502/ (Markdown: https://insights.sbomify.com/CVE-2024-3502/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-3502
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-3502
- OSV: https://osv.dev/vulnerability/CVE-2024-3502

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-3502/
Summaries are generated and may contain mistakes; the official description above is the record.