Username enumeration via distinct authentication errors
Published Apr 15, 2025 · Updated Apr 15, 2025
Username enumeration in Perforce ALM before 2025.1 allows remote attackers to identify valid accounts through authentication attempts. The web authentication flow returns different error responses for existing and nonexistent usernames instead of a uniform failure. Unauthenticated network access to the web client is sufficient to test account names, exposing only username validity rather than credentials or account data.
Summary
What happened
Username enumeration in Perforce ALM before 2025.1 allows remote attackers to identify valid accounts through authentication attempts. The web authentication flow returns different error responses for existing and nonexistent usernames instead of a uniform failure. Unauthenticated network access to the web client is sufficient to test account names, exposing only username validity rather than credentials or account data.
The record
- CVE
- CVE-2024-11084
- Published
- Apr 15, 2025
- Updated
- Apr 15, 2025
- Vendor
- BlazeMeter
- Product
- Perforce ALM
- Classifications
- CWE-203, CAPEC-189, T1087
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 15, 2025CVE publishedPublication date reported by the CVE source.
- Apr 15, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2025.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo