{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-39969 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-39969 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-39969 is a critical 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-39969 and fix it if it is affected.\n\nWhat it is: CVE-2023-39969 is a critical 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-39969 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-39969/ (Markdown: https://insights.sbomify.com/CVE-2023-39969/index.md)","id":"CVE-2023-39969","markdown":"https://insights.sbomify.com/CVE-2023-39969/index.md","name":"CVE-2023-39969","record":{"aliases":["GHSA-rc7g-99x7-4p9g"],"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 modify binary code without invalidating the Authenticode signature due to incorrect hashing logic in the uthenticode library.","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":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"uthenticode is a small cross-platform library for partially verifying Authenticode digital signatures. Version 1.0.9 of uthenticode hashed the entire file rather than hashing sections by virtual address, in violation of the Authenticode specification. As a result, an attacker could modify code within a binary without changing its Authenticode hash, making it appear valid from uthenticode's perspective. Versions of uthenticode prior to 1.0.9 are not vulnerable to this attack, nor are versions in the 2.x series. By design, uthenticode does not perform full-chain validation. However, the malleability of signature verification introduced in 1.0.9 was an unintended oversight. The 2.x series addresses the vulnerability. Versions prior to 1.0.9 are also not vulnerable, but users are encouraged to upgrade rather than downgrade. 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 signature validation bypass vulnerability","id":"CVE-2023-39969","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":"Extension - acymailing.com - RCE in AcyMailing component for Joomla 6.7.0-8.5.0","id":"CVE-2023-39970"},"packages":[],"prev":{"headline":"Open Redirect Vulnerability in jupyter-server","id":"CVE-2023-39968"},"products":["uthenticode"],"published":"2023-08-09","related":[{"cvss_score":5.9,"headline":"uthenticode EKU validation bypass","id":"CVE-2023-40012","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":"total"},"state":"PUBLISHED","updated":"2024-10-03","vendors":["trailofbits"]},"summary":"Attackers can modify binary code without invalidating the Authenticode signature due to incorrect hashing logic in the uthenticode library.","url":"https://insights.sbomify.com/CVE-2023-39969/"}