{"answers":{"affected":"1 open source package ship an affected version, including keystone. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-20170 in the wild and no public exploit code.","fix":"Upgrade keystone to 14.1.0 or later.","what":"CVE-2018-20170 is a medium-severity vulnerability in n/a, published on 17 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-20170 and fix it if it is affected.\n\nWhat it is: CVE-2018-20170 is a medium-severity vulnerability in n/a, published on 17 Dec 2018. 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-2018-20170 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- keystone (PyPI): affected all versions; fixed in 14.1.0\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-2018-20170/ (Markdown: https://insights.sbomify.com/CVE-2018-20170/index.md)","id":"CVE-2018-20170","markdown":"https://insights.sbomify.com/CVE-2018-20170/index.md","name":"CVE-2018-20170","record":{"aliases":["GHSA-jpv2-hwjh-97c7","PYSEC-2018-9","UBUNTU-CVE-2018-20170"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenStack Identity Service","requires_auth":"none","summary":"OpenStack Keystone allows user enumeration via timing differences in authentication responses, enabling attackers to identify valid usernames.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"keystone","vendor":"openstack"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"OpenStack Keystone through 14.0.1 has a user enumeration vulnerability because invalid usernames have much faster responses than valid ones for a POST /v3/auth/tokens request. NOTE: the vendor's position is that this is a hardening opportunity, and not necessarily an issue that should have an OpenStack Security Advisory","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Information disclosure in n/a","id":"CVE-2018-20170","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2018"},"n_packages":1,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-20171"},"packages":[{"ecosystem":"PyPI","fixed":["14.1.0"],"introduced":["0"],"last_affected":[],"package":"keystone","purl":"pkg:pypi/keystone","source":"PYSEC-2018-9"}],"prev":{"headline":"Denial of service in n/a","id":"CVE-2018-20169"},"products":["n/a"],"published":"2018-12-17","related":[{"cvss_score":8.8,"headline":"Insufficient Session Expiration in OpenStack Keystone","id":"CVE-2020-12690","kev_date_added":null,"published":"2020-05-06"},{"cvss_score":8.8,"headline":"OpenStack Keystone Credential Leakage","id":"CVE-2019-19687","kev_date_added":null,"published":"2019-12-09"},{"cvss_score":7.9,"headline":"OpenStack Keystone has an Incorrect Authorization Issue","id":"CVE-2026-43001","kev_date_added":null,"published":"2026-05-01"},{"cvss_score":7.8,"headline":"OpenStack Identity (Keystone) DoS through V3 API authentication chaining","id":"CVE-2014-2828","kev_date_added":null,"published":"2014-04-15"},{"cvss_score":7.5,"headline":"OpenStack Keystone allows information disclosure during account locking","id":"CVE-2021-38155","kev_date_added":null,"published":"2021-08-06"},{"cvss_score":7.5,"headline":"OpenStack Identity Keystone and keystonemiddleware Insufficiently Protected Credentials","id":"CVE-2015-7546","kev_date_added":null,"published":"2016-02-03"},{"cvss_score":7.5,"headline":"OpenStack Keystone Improper Authentication vulnerability","id":"CVE-2012-4456","kev_date_added":null,"published":"2012-10-09"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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":"2024-11-14","vendors":["n/a"]},"summary":"OpenStack Keystone allows user enumeration via timing differences in authentication responses, enabling attackers to identify valid usernames.","url":"https://insights.sbomify.com/CVE-2018-20170/"}