Private-key recovery via invalid-curve public keys
Published Dec 4, 2023 · Updated Aug 2, 2024
Invalid-curve handling in ECIES Go before 2.0.8 allows attackers to recover private keys by submitting crafted public keys. The ECDH, Encapsulate, and Decapsulate paths derive secrets without first verifying that the supplied point lies on secp256k1. Exploitation requires repeated interaction with an application that exposes these functions and reveals outputs derived from the shared secret, enabling recovery of each participating private key.
Summary
What happened
Invalid-curve handling in ECIES Go before 2.0.8 allows attackers to recover private keys by submitting crafted public keys. The ECDH, Encapsulate, and Decapsulate paths derive secrets without first verifying that the supplied point lies on secp256k1. Exploitation requires repeated interaction with an application that exposes these functions and reveals outputs derived from the shared secret, enabling recovery of each participating private key.
The record
- CVE
- CVE-2023-49292
- Published
- Dec 4, 2023
- Updated
- Aug 2, 2024
- Vendor
- ECIES
- Product
- Go
- Classifications
- CWE-200
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 4, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record 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=< 2.0.8
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
- Invalid Curve Point Attack write-upproof of concept · unverified
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