sigstore timestamp-authority up to 2.0.2 amplification
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in sigstore timestamp-authority up to 2.0.2. This affects an unknown part. Performing a manipulation results in amplification. This vulnerability was named CVE-2025-66564. The attack may be initiated remotely. There is no available exploit. You should upgrade the affected component.
Details
A vulnerability classified as problematic has been found in sigstore timestamp-authority up to 2.0.2. This affects some unknown functionality. The manipulation with an unknown input leads to a amplification vulnerability. CWE is classifying the issue as CWE-405. The product does not properly control situations in which an adversary can cause the product to consume or produce excessive resources without requiring the adversary to invest equivalent work or otherwise prove authorization, i.e., the adversary's influence is "asymmetric." This is going to have an impact on availability. The summary by CVE is:
Sigstore Timestamp Authority is a service for issuing RFC 3161 timestamps. Prior to 2.0.3, Function api.ParseJSONRequest currently splits (via a call to strings.Split) an optionally-provided OID (which is untrusted data) on periods. Similarly, function api.getContentType splits the Content-Type header (which is also untrusted data) on an application string. As a result, in the face of a malicious request with either an excessively long OID in the payload containing many period characters or a malformed Content-Type header, a call to api.ParseJSONRequest or api.getContentType incurs allocations of O(n) bytes (where n stands for the length of the function's argument). This vulnerability is fixed in 2.0.3.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2025-66564 since 12/04/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
The vulnerability scanner Nessus provides a plugin with the ID 277673 (Linux Distros Unpatched Vulnerability : CVE-2025-66564), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 2.0.3 eliminates this vulnerability. Applying the patch 0cae34e197d685a14904e0bad135b89d13b69421 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the databases at Tenable (277673) and EUVD (EUVD-2025-201319). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.5
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AmplificationCWE: CWE-405 / CWE-400 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 277673
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2025-66564
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: timestamp-authority 2.0.3
Patch: 0cae34e197d685a14904e0bad135b89d13b69421
Timeline
12/04/2025 CVE reserved12/05/2025 Advisory disclosed
12/05/2025 VulDB entry created
12/09/2025 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-4qg8-fj49-pxjh
Status: Confirmed
CVE: CVE-2025-66564 (🔒)
GCVE (CVE): GCVE-0-2025-66564
GCVE (VulDB): GCVE-100-334413
EUVD: 🔒
Entry
Created: 12/05/2025 02:06Updated: 12/09/2025 00:39
Changes: 12/05/2025 02:06 (65), 12/05/2025 20:45 (1), 12/09/2025 00:39 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.