{"answers":{"affected":"3 open source packages ship an affected version, including python-keystoneclient. It affects 1 product.","exploited":"There is no known exploitation of CVE-2013-2104 in the wild and no public exploit code.","fix":"Upgrade python-keystoneclient to 0.2.4 or later.","what":"CVE-2013-2104 is a medium-severity vulnerability in n/a, published on 21 Jan 2014. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2013-2104 and fix it if it is affected.\n\nWhat it is: CVE-2013-2104 is a medium-severity vulnerability in n/a, published on 21 Jan 2014. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2013-2104 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- python-keystoneclient (PyPI): affected all versions; fixed in 0.2.4\n- python-keystoneclient (PyPI): affected all versions; fixed in 0.2.4\n- python-keystoneclient (PyPI): affected all versions; fixed in 0.2.4\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-2013-2104/ (Markdown: https://insights.sbomify.com/CVE-2013-2104/index.md)","id":"CVE-2013-2104","markdown":"https://insights.sbomify.com/CVE-2013-2104/index.md","name":"CVE-2013-2104","record":{"aliases":["DEBIAN-CVE-2013-2104","GHSA-4rrr-j7ff-r844","PYSEC-2014-69","RHSA-2013:0944"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenStack Keystone client","requires_auth":"low_privilege","summary":"Authenticated users can bypass token expiration and revocation checks in the OpenStack Keystone client, retaining unauthorized access.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"python-keystoneclient","vendor":"openstack"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:S/C:N/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-264","name":null}],"description":"python-keystoneclient before 0.2.4, as used in OpenStack Keystone (Folsom), does not properly check expiry for PKI tokens, which allows remote authenticated users to (1) retain use of a token after it has expired, or (2) use a revoked token once it expires.","ecosystems":["PyPI","Red Hat:openstack:3::el6"],"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":"python-keystoneclient missing expiration check in PKI token validation","id":"CVE-2013-2104","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"security_feature_bypass","year":"2013"},"n_packages":5,"n_references":6,"next":{"headline":"Script Injection in Show In Browser gem","id":"CVE-2013-2105"},"packages":[{"ecosystem":"PyPI","fixed":["0.2.4"],"introduced":["0"],"last_affected":[],"package":"python-keystoneclient","purl":null,"source":"GHSA-4rrr-j7ff-r844"},{"ecosystem":"PyPI","fixed":["0.2.4"],"introduced":["0"],"last_affected":[],"package":"python-keystoneclient","purl":"pkg:pypi/python-keystoneclient","source":"GHSA-4rrr-j7ff-r844"},{"ecosystem":"PyPI","fixed":["0.2.4"],"introduced":["0"],"last_affected":[],"package":"python-keystoneclient","purl":"pkg:pypi/python-keystoneclient","source":"PYSEC-2014-69"},{"ecosystem":"Red Hat:openstack:3::el6","fixed":["1:0.2.3-2.el6ost"],"introduced":["0"],"last_affected":[],"package":"python-keystoneclient","purl":"pkg:rpm/redhat/python-keystoneclient","source":"RHSA-2013:0944"},{"ecosystem":"Red Hat:openstack:3::el6","fixed":["1:0.2.3-2.el6ost"],"introduced":["0"],"last_affected":[],"package":"python-keystoneclient-doc","purl":"pkg:rpm/redhat/python-keystoneclient-doc","source":"RHSA-2013:0944"}],"prev":{"headline":"Server-side request forgery in OpenShift cartridge","id":"CVE-2013-2103"},"products":["n/a"],"published":"2014-01-21","related":[{"cvss_score":6,"headline":"python-keystoneclient vulnerable to context confusion in Keystone auth_token middleware","id":"CVE-2014-0105","kev_date_added":null,"published":"2014-04-15"},{"cvss_score":2.1,"headline":"python-keystoneclient unsecure user password update","id":"CVE-2013-2013","kev_date_added":null,"published":"2013-10-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CC BY 4.0","name":"Red Hat","prefix":"RHSA"},{"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Authenticated users can bypass token expiration and revocation checks in the OpenStack Keystone client, retaining unauthorized access.","url":"https://insights.sbomify.com/CVE-2013-2104/"}