{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-0693 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-0693 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-0693 is a medium-severity vulnerability in AWS Sign-in IAM Login Flow, published on 23 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-0693 and fix it if it is affected.\n\nWhat it is: CVE-2025-0693 is a medium-severity vulnerability in AWS Sign-in IAM Login Flow, published on 23 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-0693 in the wild and no public exploit code.\n\nAffected product: AWS Sign-in IAM Login Flow. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-0693/ (Markdown: https://insights.sbomify.com/CVE-2025-0693/index.md)","id":"CVE-2025-0693","markdown":"https://insights.sbomify.com/CVE-2025-0693/index.md","name":"CVE-2025-0693","record":{"aliases":["GHSA-8rcr-h4v8-qpq5"],"analysis":{"component_type":"cloud_service","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"AWS Sign-in IAM","requires_auth":"none","summary":"Attackers can enumerate valid IAM usernames in AWS accounts by analyzing variable response times during the login flow.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"AMZN","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-208","name":"Observable Timing Discrepancy"},{"id":"CWE-204","name":"Observable Response Discrepancy"}],"description":"Variable response times in the AWS Sign-in IAM user login flow allowed for the use of brute force enumeration techniques to identify valid IAM usernames in an arbitrary AWS account.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Issue with AWS Sign-in IAM User Login Flow - Possible Username Enumeration","id":"CVE-2025-0693","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"CODESYS Control V3 removable media path traversal","id":"CVE-2025-0694"},"packages":[],"prev":{"headline":"Simple Video Management System \u003c= 1.0.4 - Admin+ Stored XSS","id":"CVE-2025-0692"},"products":["AWS Sign-in IAM Login Flow"],"published":"2025-01-23","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-14","vendors":["AWS"]},"summary":"Attackers can enumerate valid IAM usernames in AWS accounts by analyzing variable response times during the login flow.","url":"https://insights.sbomify.com/CVE-2025-0693/"}