Metrics
Affected Vendors & Products
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-18798 | rfc3161-client has insufficient verification for timestamp response signatures |
Github GHSA |
GHSA-6qhv-4h7r-2g9m | rfc3161-client has insufficient verification for timestamp response signatures |
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Mon, 23 Jun 2025 16:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Sat, 21 Jun 2025 02:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | rfc3161-client has insufficient verification for timestamp response signatures | |
| Weaknesses | CWE-347 | |
| References |
| |
| Metrics |
cvssV4_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2025-06-23T15:13:49.905Z
Reserved: 2025-06-18T03:55:52.035Z
Link: CVE-2025-52556
Updated: 2025-06-23T15:13:31.272Z
Status : Awaiting Analysis
Published: 2025-06-21T02:15:19.947
Modified: 2025-06-23T20:16:21.633
Link: CVE-2025-52556
No data.
OpenCVE Enrichment
No data.
EUVD
Github GHSA