# CVE-2024-54002: Dependency-Track allows enumeration of managed users via /api/v1/user/login endpoint

> Attackers can enumerate valid usernames by observing response time differences in the login endpoint, exposing managed user identities.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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:** 4 Dec 2024
- **Updated:** 4 Dec 2024
- **Also known as:** GHSA-9w3m-hm36-w32w

## What is CVE-2024-54002?

CVE-2024-54002 is a medium-severity vulnerability in DependencyTrack dependency-track, published on 4 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Dependency-Track is a Component Analysis platform that allows organizations to identify and reduce risk in the software supply chain. Performing a login request against the /api/v1/user/login endpoint with a username that exist in the system takes significantly longer than performing the same action with a username that is not known by the system. The observable difference in request duration can be leveraged by actors to enumerate valid names of managed users. LDAP and OpenID Connect users are not affected. The issue has been fixed in Dependency-Track 4.12.2.

Weakness: CWE-203 (Observable Discrepancy)

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


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

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

## Is CVE-2024-54002 being exploited?

There is no known exploitation of CVE-2024-54002 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-54002 is a medium-severity vulnerability in DependencyTrack dependency-track, published on 4 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-54002 in the wild and no public exploit code.

Affected product: DependencyTrack dependency-track. 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-54002/ (Markdown: https://insights.sbomify.com/CVE-2024-54002/index.md)
```

## Sources

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

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