ghsa-6qhv-4h7r-2g9m
Vulnerability from github
Published
2025-06-20 18:08
Modified
2025-06-27 22:02
Severity ?
VLAI Severity ?
Summary
rfc3161-client has insufficient verification for timestamp response signatures
Details
Impact
rfc3161-client
1.0.2 and earlier contain a flaw in their timestamp response signature verification logic. In particular, it performs chain verification 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.
Patches
Users should immediately upgrade to rfc3161-client
1.0.3 or later.
Workarounds
There is no workaround possible. Users should immediately upgrade to a fixed version.
{ "affected": [ { "database_specific": { "last_known_affected_version_range": "\u003c= 1.0.2" }, "package": { "ecosystem": "PyPI", "name": "rfc3161-client" }, "ranges": [ { "events": [ { "introduced": "0" }, { "fixed": "1.0.3" } ], "type": "ECOSYSTEM" } ] } ], "aliases": [ "CVE-2025-52556" ], "database_specific": { "cwe_ids": [ "CWE-347" ], "github_reviewed": true, "github_reviewed_at": "2025-06-20T18:08:40Z", "nvd_published_at": "2025-06-21T02:15:19Z", "severity": "CRITICAL" }, "details": "### Impact\n\n`rfc3161-client` 1.0.2 and earlier contain a flaw in their timestamp response signature verification logic. In particular, it performs chain verification against the TSR\u0027s embedded certificates up to the trusted root(s), but fails to verify the TSR\u0027s 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.\n\n### Patches\n\nUsers should immediately upgrade to `rfc3161-client` 1.0.3 or later.\n\n### Workarounds\n\nThere is no workaround possible. Users should immediately upgrade to a fixed version.", "id": "GHSA-6qhv-4h7r-2g9m", "modified": "2025-06-27T22:02:46Z", "published": "2025-06-20T18:08:40Z", "references": [ { "type": "WEB", "url": "https://github.com/trailofbits/rfc3161-client/security/advisories/GHSA-6qhv-4h7r-2g9m" }, { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-52556" }, { "type": "WEB", "url": "https://github.com/trailofbits/rfc3161-client/commit/724a184f953e3f171f85cb223871172b41b0d0dc" }, { "type": "PACKAGE", "url": "https://github.com/trailofbits/rfc3161-client" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N", "type": "CVSS_V4" } ], "summary": "rfc3161-client has insufficient verification for timestamp response signatures" }
Loading…
Loading…
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…