{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2013-6391 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2013-6391 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 14 Dec 2013. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2013-6391 and fix it if it is affected.\n\nWhat it is: CVE-2013-6391 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 14 Dec 2013. 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-6391 in the wild and no public exploit code.\n\nAffected product: Canonical Ubuntu Linux. 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-2013-6391/ (Markdown: https://insights.sbomify.com/CVE-2013-6391/index.md)","id":"CVE-2013-6391","markdown":"https://insights.sbomify.com/CVE-2013-6391/index.md","name":"CVE-2013-6391","record":{"aliases":["DEBIAN-CVE-2013-6391","GHSA-3fpm-8w39-5p69","RHSA-2014:0089"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenStack Identity","requires_auth":"low_privilege","summary":"Remote trust users can escalate privileges by generating EC2 credentials from a trust-scoped token and using them in the ec2tokens API.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"ubuntu_linux","vendor":"canonical"},{"product":"keystone","vendor":"openstack"},{"product":"openstack","vendor":"redhat"}],"cvss":{"score":5.8,"severity":"medium","source":"nvd","vector":"AV:N/AC:M/Au:N/C:P/I:P/A:N","version":"2.0"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"The ec2tokens API in OpenStack Identity (Keystone) before Havana 2013.2.1 and Icehouse before icehouse-2 does not return a trust-scoped token when one is received, which allows remote trust users to gain privileges by generating EC2 credentials from a trust-scoped token and using them in an ec2tokens API request.","ecosystems":["Red Hat:openstack:4::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":"Privilege escalation in n/a","id":"CVE-2013-6391","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"canonical:ubuntu_linux","products":["canonical:ubuntu_linux","redhat:openstack"],"type":"privilege_escalation","year":"2013"},"n_packages":3,"n_references":8,"next":{"headline":"Information disclosure in n/a","id":"CVE-2013-6392"},"packages":[{"ecosystem":"Red Hat:openstack:4::el6","fixed":["0:2013.2.1-1.el6ost"],"introduced":["0"],"last_affected":[],"package":"openstack-keystone","purl":"pkg:rpm/redhat/openstack-keystone","source":"RHSA-2014:0089"},{"ecosystem":"Red Hat:openstack:4::el6","fixed":["0:2013.2.1-1.el6ost"],"introduced":["0"],"last_affected":[],"package":"openstack-keystone-doc","purl":"pkg:rpm/redhat/openstack-keystone-doc","source":"RHSA-2014:0089"},{"ecosystem":"Red Hat:openstack:4::el6","fixed":["0:2013.2.1-1.el6ost"],"introduced":["0"],"last_affected":[],"package":"python-keystone","purl":"pkg:rpm/redhat/python-keystone","source":"RHSA-2014:0089"}],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2013-6390"},"products":["n/a"],"published":"2013-12-14","related":[{"cvss_score":9.8,"headline":"SaltStack Salt Authentication Bypass","id":"CVE-2020-11651","kev_date_added":"2021-11-03","published":"2020-04-30"},{"cvss_score":9.8,"headline":"OpenSMTPD Remote Code Execution","id":"CVE-2020-7247","kev_date_added":"2022-03-25","published":"2020-01-29"},{"cvss_score":9.8,"headline":"Exim Out-of-bounds Write","id":"CVE-2019-16928","kev_date_added":"2022-03-03","published":"2019-09-27"},{"cvss_score":9.8,"headline":"Exim Buffer Overflow","id":"CVE-2018-6789","kev_date_added":"2021-11-03","published":"2018-02-08"},{"cvss_score":9.8,"headline":"Oracle Java SE and Java SE Embedded Remote Code Execution","id":"CVE-2015-2590","kev_date_added":"2022-03-03","published":"2015-07-16"},{"cvss_score":9.8,"headline":"Oracle JRE Remote Code Execution","id":"CVE-2013-0422","kev_date_added":"2022-05-25","published":"2013-01-10"},{"cvss_score":9.8,"headline":"Oracle Java SE Runtime Environment (JRE) Arbitrary Code Execution","id":"CVE-2011-3544","kev_date_added":"2022-03-03","published":"2011-10-19"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"Remote trust users can escalate privileges by generating EC2 credentials from a trust-scoped token and using them in the ec2tokens API.","url":"https://insights.sbomify.com/CVE-2013-6391/"}