Approved changes feed: RSS · Atom

cpe:2.3:a:trailofbits:uthenticode:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorTrailofbits (6524af29-571d-5cd0-b937-ac8aee3b3053)
ProductUthenticode (69847d81-6300-5879-a506-db77fb94c44d)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:github/trailofbits/uthenticode purl2cpe 2026-06-01 10:13:04.358830

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2023-40012 vulnerable 2026-06-08 06:09:41.020703 uthenticode EKU validation bypass
MEDIUM (5.9)
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.
Published: 2023-08-09T15:33:54.406Z
Updated: 2024-10-03T15:15:51.372Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-39969 vulnerable 2026-06-08 06:09:38.211921 uthenticode signature validation bypass vulnerability
CRITICAL (9.1)
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.
Published: 2023-08-09T15:34:07.776Z
Updated: 2024-10-03T15:15:12.245Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.