Username enumeration via login response timing
Published Jan 23, 2025 · Updated Oct 14, 2025
Observable timing discrepancies in AWS Sign-In before January 16, 2025 allow remote attackers to enumerate valid IAM usernames. The IAM user login flow returned authentication-failure responses with measurably different delays depending on whether the submitted username existed. No authentication is required, but repeated login attempts against a chosen AWS account are needed; the disclosed result is username validity only and does not grant access to AWS resources.
Summary
What happened
Observable timing discrepancies in AWS Sign-In before January 16, 2025 allow remote attackers to enumerate valid IAM usernames. The IAM user login flow returned authentication-failure responses with measurably different delays depending on whether the submitted username existed. No authentication is required, but repeated login attempts against a chosen AWS account are needed; the disclosed result is username validity only and does not grant access to AWS resources.
The record
- CVE
- CVE-2025-0693
- Published
- Jan 23, 2025
- Updated
- Oct 14, 2025
- Vendor
- Amazon Web Services
- Product
- AWS Sign-In
- Classifications
- CWE-204, CWE-208, T1087.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 23, 2025CVE publishedPublication date reported by the CVE source.
- Oct 14, 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=N/A
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