CVE-2024-11084: Potential Username Enumeration in Helix ALM
First published: Tue Apr 15 2025(Updated: )
Helix ALM prior to 2025.1 returns distinct error responses during authentication, allowing an attacker to determine whether a username exists.
Credit: security@puppet.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Perforce Helix ALM | <2025.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2024-11084?
CVE-2024-11084 is classified as a medium severity vulnerability.
How do I fix CVE-2024-11084?
To mitigate CVE-2024-11084, upgrade Helix ALM to version 2025.1 or later.
What does CVE-2024-11084 allow an attacker to do?
CVE-2024-11084 allows an attacker to determine the existence of a username through distinct error responses during authentication.
Which versions of Helix ALM are affected by CVE-2024-11084?
Helix ALM versions prior to 2025.1 are affected by CVE-2024-11084.
Is there a workaround for CVE-2024-11084?
There are no specific workarounds available for CVE-2024-11084 other than upgrading to a patched version.
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/title
- agent/first-publish-date
- agent/type
- agent/references
- agent/description
- agent/guess-ai
- agent/software-canonical-lookup
- agent/softwarecombine
- collector/nvd-api
- source/NVD
- agent/last-modified-date
- agent/author
- agent/source
- agent/severity
- agent/tags
- agent/event
- vendor/perforce
- canonical/perforce helix alm