Forged attestation acceptance via fail-open signature checks
Published Oct 15, 2025 · Updated Oct 15, 2025
Improper certificate validation in go-witness before 0.9.1 allows remote attackers to submit forged EC2 identity documents. The AWS attestor's Verify method returns success for missing or empty signatures and for errors from RSA PKCS#1 v1.5 verification. Exploitation requires use of the AWS attestor and attacker control or interception of instance identity data, causing false trust in a forged attestation.
Summary
What happened
Improper certificate validation in go-witness before 0.9.1 allows remote attackers to submit forged EC2 identity documents. The AWS attestor's Verify method returns success for missing or empty signatures and for errors from RSA PKCS#1 v1.5 verification. Exploitation requires use of the AWS attestor and attacker control or interception of instance identity data, causing false trust in a forged attestation.
The record
- CVE
- CVE-2025-62375
- Published
- Oct 15, 2025
- Updated
- Oct 15, 2025
- Vendor
- in-toto
- Product
- go-witness
- Classifications
- CWE-295, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 15, 2025CVE publishedPublication date reported by the CVE source.
- Oct 15, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.9.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo