Incorrect P-256 results via unreduced scalars
Published Mar 8, 2023 · Updated Aug 2, 2024
Incorrect calculation in crypto/internal/nistec before 1.19.7 and 1.20.0 through 1.20.1 allows attackers to obtain wrong P-256 results. The P-256 assembly path accepts 32-byte scalars without reducing them modulo the curve order, so its incomplete addition formulas mishandle equal points. Reachability requires a caller to pass an unreduced scalar through the deprecated crypto/elliptic API; crypto/ecdsa and crypto/ecdh are unaffected.
Summary
What happened
Incorrect calculation in crypto/internal/nistec before 1.19.7 and 1.20.0 through 1.20.1 allows attackers to obtain wrong P-256 results. The P-256 assembly path accepts 32-byte scalars without reducing them modulo the curve order, so its incomplete addition formulas mishandle equal points. Reachability requires a caller to pass an unreduced scalar through the deprecated crypto/elliptic API; crypto/ecdsa and crypto/ecdh are unaffected.
The record
- CVE
- CVE-2023-24532
- Published
- Mar 8, 2023
- Updated
- Aug 2, 2024
- Vendor
- Go standard library
- Product
- crypto/internal/nistec
- Classifications
- CWE-682
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 8, 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=0 <1.19.7
- Affected versionversion=1.20.0-0 <1.20.2
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