{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-39312 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2024-39312 is a medium-severity vulnerability in randombit botan, published on 8 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-39312 and fix it if it is affected.\n\nWhat it is: CVE-2024-39312 is a medium-severity vulnerability in randombit botan, published on 8 Jul 2024. 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-2024-39312 in the wild and no public exploit code.\n\nAffected product: randombit botan. 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-2024-39312/ (Markdown: https://insights.sbomify.com/CVE-2024-39312/index.md)","id":"CVE-2024-39312","markdown":"https://insights.sbomify.com/CVE-2024-39312/index.md","name":"CVE-2024-39312","record":{"aliases":["ALPINE-CVE-2024-39312","AZL-43825","AZL-44286","DEBIAN-CVE-2024-39312","GHSA-jp24-56jm-gg86","UBUNTU-CVE-2024-39312"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"C++ cryptography library","requires_auth":"none","summary":"Attackers can bypass X.509 name constraint checks in Botan, allowing certificates that should be rejected to be accepted.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"botan","vendor":"botan_project"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"Botan is a C++ cryptography library. X.509 certificates can identify elliptic curves using either an object identifier or using explicit encoding of the parameters. A bug in the parsing of name constraint extensions in X.509 certificates meant that if the extension included both permitted subtrees and excluded subtrees, only the permitted subtree would be checked. If a certificate included a name which was permitted by the permitted subtree but also excluded by excluded subtree, it would be accepted. Fixed in versions 3.5.0 and 2.19.5.","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":"Botan has an Authorization Error due to Name Constraint Decoding Bug","id":"CVE-2024-39312","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"toy-blog Improper Input Validation vulnerability","id":"CVE-2024-39313"},"packages":[],"prev":{"headline":"Publify Vulnerable To Cross-Site Scripting (XSS) Via Redirects Requiring User Interaction","id":"CVE-2024-39311"},"products":["botan"],"published":"2024-07-08","related":[{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2021-24115","kev_date_added":null,"published":"2021-02-22"},{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2018-9127","kev_date_added":null,"published":"2018-04-02"},{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2015-7826","kev_date_added":null,"published":"2017-04-10"},{"cvss_score":9.8,"headline":"Other in n/a","id":"CVE-2016-6878","kev_date_added":null,"published":"2017-04-10"},{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2016-9132","kev_date_added":null,"published":"2017-01-30"},{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2016-2195","kev_date_added":null,"published":"2016-05-13"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2016-2196","kev_date_added":null,"published":"2016-05-13"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["randombit"]},"summary":"Attackers can bypass X.509 name constraint checks in Botan, allowing certificates that should be rejected to be accepted.","url":"https://insights.sbomify.com/CVE-2024-39312/"}