Approved changes feed: RSS · Atom

cpe:2.3:a:trailofbits:rfc3161-client:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorTrailofbits (6524af29-571d-5cd0-b937-ac8aee3b3053)
ProductRfc3161 Client (b3a0355c-28cc-5860-b1c3-c91c082e2691)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from gcve-enriched-dumps CVE data

PURL mappings

PURLSourceLast updated
pkg:github/trailofbits/rfc3161-client purl2cpe 2026-07-28 16:40:57.248827

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-33753 vulnerable 2026-06-08 07:59:10.706181 Improper Certificate Validation in rfc3161-client
MEDIUM (6.2)
rfc3161-client is a Python library implementing the Time-Stamp Protocol (TSP) described in RFC 3161. Prior to 1.0.6, an Authorization Bypass vulnerability in rfc3161-client's signature verification allows any attacker to impersonate a trusted TimeStamping Authority (TSA). By exploiting a logic flaw in how the library extracts the leaf certificate from an unordered PKCS#7 bag of certificates, an attacker can append a spoofed certificate matching the target common_name and Extended Key Usage (EKU) requirements. This tricks the library into verifying these authorization rules against the forged certificate while validating the cryptographic signature against an actual trusted TSA (such as FreeTSA), thereby bypassing the intended TSA authorization pinning entirely. This vulnerability is fixed in 1.0.6.
Published: 2026-04-08T14:54:59.704Z
Updated: 2026-04-08T16:12:57.796Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2025-52556 vulnerable 2026-06-08 07:31:11.818699 rfc3161-client has insufficient verification for timestamp response signatures
rfc3161-client is a Python library implementing the Time-Stamp Protocol (TSP) described in RFC 3161. Prior to version 1.0.3, there is a flaw in the timestamp response signature verification logic. In particular, chain verification is performed against the TSR's embedded certificates up to the trusted root(s), but fails to verify the TSR's own signature against the timestamping leaf certificates. Consequently, vulnerable versions perform insufficient signature validation to properly consider a TSR verified, as the attacker can introduce any TSR signature so long as the embedded leaf chains up to some root TSA. This issue has been patched in version 1.0.3. There is no workaround for this issue.
Published: 2025-06-21T01:33:18.829Z
Updated: 2025-06-23T15:13:49.905Z
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.