Integrity bypass via exposed weak checksum defaults
Published Mar 5, 2025 · Updated Mar 7, 2025
Risky cryptography in National Security Agency Emissary before 8.24.0 allows attackers to bypass integrity checks with hash collisions. Public ChecksumCalculator constructors default to SHA-1, enable CRC32, and expose KFF similarity hashing for use outside its intended package. Exploitation requires consuming code to treat these outputs as cryptographically secure integrity or authentication values.
Summary
What happened
Risky cryptography in National Security Agency Emissary before 8.24.0 allows attackers to bypass integrity checks with hash collisions. Public ChecksumCalculator constructors default to SHA-1, enable CRC32, and expose KFF similarity hashing for use outside its intended package. Exploitation requires consuming code to treat these outputs as cryptographically secure integrity or authentication values.
The record
- CVE
- CVE-2025-27508
- Published
- Mar 5, 2025
- Updated
- Mar 7, 2025
- Vendor
- National Security Agency
- Product
- Emissary
- Classifications
- CWE-327, T1565
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 5, 2025CVE publishedPublication date reported by the CVE source.
- Mar 7, 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=< 8.24.0
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.
Weakness, pattern, technique
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