{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-40012 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-40012 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-40012 is a medium-severity vulnerability in trailofbits uthenticode, published on 9 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-40012 and fix it if it is affected.\n\nWhat it is: CVE-2023-40012 is a medium-severity vulnerability in trailofbits uthenticode, published on 9 Aug 2023. 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-2023-40012 in the wild and no public exploit code.\n\nAffected product: trailofbits uthenticode. 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-2023-40012/ (Markdown: https://insights.sbomify.com/CVE-2023-40012/index.md)","id":"CVE-2023-40012","markdown":"https://insights.sbomify.com/CVE-2023-40012/index.md","name":"CVE-2023-40012","record":{"aliases":["GHSA-gm2f-j4rj-6xqj"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Authenticode verification library","requires_auth":"none","summary":"Attackers can bypass Authenticode signature verification by using certificates not authorized for code signing, allowing malicious PE files to appear valid.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"uthenticode","vendor":"trailofbits"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"},{"id":"CWE-325","name":"Missing Cryptographic Step"}],"description":"uthenticode is a small cross-platform library for partially verifying Authenticode digital signatures. Versions of uthenticode prior to the 2.x series did not check Extended Key Usages in certificates, in violation of the Authenticode X.509 certificate profile. As a result, a malicious user could produce a \"signed\" PE file that uthenticode would verify and consider valid using an X.509 certificate that isn't entitled to produce code signatures (e.g., a SSL certificate). By design, uthenticode does not perform full-chain validation. However, the absence of EKU validation was an unintended oversight. The 2.0.0 release series includes EKU checks. There are no workarounds to this vulnerability.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"uthenticode EKU validation bypass","id":"CVE-2023-40012","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in external-svg-loader","id":"CVE-2023-40013"},"packages":[],"prev":{"headline":"WordPress Cost Calculator Builder plugin \u003c= 3.1.42 - Broken Access Control vulnerability","id":"CVE-2023-40011"},"products":["uthenticode"],"published":"2023-08-09","related":[{"cvss_score":9.1,"headline":"uthenticode signature validation bypass vulnerability","id":"CVE-2023-39969","kev_date_added":null,"published":"2023-08-09"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-10-03","vendors":["trailofbits"]},"summary":"Attackers can bypass Authenticode signature verification by using certificates not authorized for code signing, allowing malicious PE files to appear valid.","url":"https://insights.sbomify.com/CVE-2023-40012/"}