Non-repudiation bypass via invalid ECDSA signature acceptance
Published Jan 19, 2024 · Updated Jul 14, 2026
Improper signature verification in AWS Encryption SDK for Java before 1.9.0 and 2.0.0 through 2.1.x allows attackers to pass invalid signatures. During message decryption, the SDK's ECDSA verification path treats certain invalid signatures as valid instead of rejecting the message. Exploitation requires trusted KMS decrypt permissions; it can defeat signature-based non-repudiation but cannot alter authenticated ciphertext or decrypted plaintext.
Summary
What happened
Improper signature verification in AWS Encryption SDK for Java before 1.9.0 and 2.0.0 through 2.1.x allows attackers to pass invalid signatures. During message decryption, the SDK's ECDSA verification path treats certain invalid signatures as valid instead of rejecting the message. Exploitation requires trusted KMS decrypt permissions; it can defeat signature-based non-repudiation but cannot alter authenticated ciphertext or decrypted plaintext.
The record
- CVE
- CVE-2024-23680
- Published
- Jan 19, 2024
- Updated
- Jul 14, 2026
- Vendor
- Amazon Web Services
- Product
- AWS Encryption SDK for Java
- Classifications
- CWE-347
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 19, 2024CVE publishedPublication date reported by the CVE source.
- Jul 14, 2026Record 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 <1.9.0
- Affected versionversion=2.0.0 <2.2.0
What conditions does exploitation require?
What is affected?
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