{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2015-9259 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2015-9259 is a critical vulnerability in n/a, published on 31 Mar 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-2015-9259 and fix it if it is affected.\n\nWhat it is: CVE-2015-9259 is a critical vulnerability in n/a, published on 31 Mar 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-2015-9259 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2015-9259/ (Markdown: https://insights.sbomify.com/CVE-2015-9259/index.md)","id":"CVE-2015-9259","markdown":"https://insights.sbomify.com/CVE-2015-9259/index.md","name":"CVE-2015-9259","record":{"aliases":["DEBIAN-CVE-2015-9259","GHSA-2m6m-p8vh-r2f9"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Docker Notary","requires_auth":"none","summary":"Docker Notary fails to validate root.json expiry, allowing attackers to bypass security checks using old root files after key compromise.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"notary","vendor":"docker"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"In Docker Notary before 0.1, the checkRoot function in gotuf/client/client.go does not check expiry of root.json files, despite a comment stating that it does. Even if a user creates a new root.json file after a key compromise, an attacker can produce update files referring to an old root.json file.","ecosystems":[],"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":"Security feature bypass in n/a","id":"CVE-2015-9259","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2015"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2015-9260"},"packages":[],"prev":{"headline":"Docker Notary Signature Algorithm Not Matched to Key vulnerability","id":"CVE-2015-9258"},"products":["n/a"],"published":"2018-03-31","related":[{"cvss_score":7.5,"headline":"Docker Notary Signature Algorithm Not Matched to Key vulnerability","id":"CVE-2015-9258","kev_date_added":null,"published":"2018-03-31"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"Docker Notary fails to validate root.json expiry, allowing attackers to bypass security checks using old root files after key compromise.","url":"https://insights.sbomify.com/CVE-2015-9259/"}