# CVE-2024-11084: Potential Username Enumeration in Helix ALM

> Attackers can enumerate valid usernames in Helix ALM by analyzing distinct authentication error responses, facilitating targeted attacks.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Apr 2025
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-7xmj-r3rh-c5m3

## What is CVE-2024-11084?

CVE-2024-11084 is a medium-severity vulnerability in Perforce Helix ALM, published on 15 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Helix ALM prior to 2025.1 returns distinct error responses during authentication, allowing an attacker to determine whether a username exists.

Weakness: CWE-203 (Observable Discrepancy)

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


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

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

## Is CVE-2024-11084 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-11084 is a medium-severity vulnerability in Perforce Helix ALM, published on 15 Apr 2025. 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-11084 in the wild and no public exploit code.

Affected product: Perforce Helix ALM. 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-11084/ (Markdown: https://insights.sbomify.com/CVE-2024-11084/index.md)
```

## Sources

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

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