CVE-2023-24532: Incorrect calculation on P256 curves in crypto/internal/nistec
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.81% (FIRST EPSS); higher than 57.6% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Go standard library crypto/internal/nistec 1.19.7, 1.20.2.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Go standard library crypto/internal/nistec 1.19.7, 1.20.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The ScalarMult and ScalarBaseMult methods of the P256 Curve may return an incorrect result if called with some specific unreduced scalars (a scalar larger than the order of the curve). This does not impact usages of crypto/ecdsa or crypto/ecdh.
- Published
- Mar 8, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.8% · 57th percentile
- CWE
- CWE-682
Report tools
Action score
21
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.8%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| golang | go | cpe:2.3:a:golang:go |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Go). Independent of NVD's CPE analysis and usually ahead of it.
Go standard library crypto/internal/nistec
- before 1.19.7affected · semver
- 1.20.0-0 and later · before 1.20.2affected · semver
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- golang gobefore 1.19.7
- golang go1.20.0 and later · before 1.20.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.17 | go | from 1.20.0 · before 1.19.7-r0 | 1.19.7-r0 |
| Alpine:v3.18 | go | from 1.20.0 · before 1.20.2-r0 | 1.20.2-r0 |
| Debian:12 | golang-1.19 | before 1.19.8-2 | 1.19.8-2 |
| Go | stdlib | from 1.20.0-0 · before 1.20.2 | 1.20.2 |
| Go | stdlib | before 1.19.7 | 1.19.7 |
| openSUSE:Leap 15.4 | go1.19 | before 1.19.7-150000.1.23.1 | 1.19.7-150000.1.23.1 |
| openSUSE:Leap 15.4 | go1.20 | before 1.20.2-150000.1.5.1 | 1.20.2-150000.1.5.1 |
| openSUSE:Tumbleweed | go1.19 | before 1.19.7-1.1 | 1.19.7-1.1 |
| openSUSE:Tumbleweed | go1.20 | before 1.20.2-1.1 | 1.20.2-1.1 |
| Red Hat:enterprise_linux:8::appstream | delve | before 0:1.9.1-1.module+el8.8.0+16778+5fbb74f5 | 0:1.9.1-1.module+el8.8.0+16778+5fbb74f5 |
| Red Hat:enterprise_linux:8::appstream | delve-debuginfo | before 0:1.9.1-1.module+el8.8.0+16778+5fbb74f5 | 0:1.9.1-1.module+el8.8.0+16778+5fbb74f5 |
| Red Hat:enterprise_linux:8::appstream | delve-debugsource | before 0:1.9.1-1.module+el8.8.0+16778+5fbb74f5 | 0:1.9.1-1.module+el8.8.0+16778+5fbb74f5 |
| Red Hat:enterprise_linux:8::appstream | go-toolset | before 0:1.19.9-1.module+el8.8.0+18857+fca43658 | 0:1.19.9-1.module+el8.8.0+18857+fca43658 |
| Red Hat:enterprise_linux:8::appstream | golang | before 0:1.19.9-1.module+el8.8.0+18857+fca43658 | 0:1.19.9-1.module+el8.8.0+18857+fca43658 |
| Red Hat:enterprise_linux:8::appstream | golang-bin | before 0:1.19.9-1.module+el8.8.0+18857+fca43658 | 0:1.19.9-1.module+el8.8.0+18857+fca43658 |
| Red Hat:enterprise_linux:8::appstream | golang-docs | before 0:1.19.9-1.module+el8.8.0+18857+fca43658 | 0:1.19.9-1.module+el8.8.0+18857+fca43658 |
| Red Hat:enterprise_linux:8::appstream | golang-misc | before 0:1.19.9-1.module+el8.8.0+18857+fca43658 | 0:1.19.9-1.module+el8.8.0+18857+fca43658 |
| Red Hat:enterprise_linux:8::appstream | golang-race | before 0:1.19.9-1.module+el8.8.0+18857+fca43658 | 0:1.19.9-1.module+el8.8.0+18857+fca43658 |
| Red Hat:enterprise_linux:8::appstream | golang-src | before 0:1.19.9-1.module+el8.8.0+18857+fca43658 | 0:1.19.9-1.module+el8.8.0+18857+fca43658 |
| Red Hat:enterprise_linux:8::appstream | golang-tests | before 0:1.19.9-1.module+el8.8.0+18857+fca43658 | 0:1.19.9-1.module+el8.8.0+18857+fca43658 |
| Red Hat:enterprise_linux:9::appstream | golang | before 0:1.19.9-2.el9_2 | 0:1.19.9-2.el9_2 |
| Red Hat:enterprise_linux:9::appstream | golang-bin | before 0:1.19.9-2.el9_2 | 0:1.19.9-2.el9_2 |
| Red Hat:enterprise_linux:9::appstream | golang-docs | before 0:1.19.9-2.el9_2 | 0:1.19.9-2.el9_2 |
| Red Hat:enterprise_linux:9::appstream | golang-misc | before 0:1.19.9-2.el9_2 | 0:1.19.9-2.el9_2 |
+6
Same product
golang: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-7187The "go get" implementation in Go 1.9.4, when the -insecure command-line option is used, does not validate the import path (get/vcs.go only…54Plan
- CVE-2018-16873In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to remote code execution when executed with the -u flag…52Plan
- CVE-2021-38297Go before 1.16.9 and 1.17.x before 1.17.2 has a Buffer Overflow via large arguments in a function invocation from a WASM module, when…42Plan
Published before and after this one in the same product
- ← EarlierCVE-2022-41724Feb 28, 2023 · Panic on large handshake records in crypto/tls30Monitor
- ← EarlierCVE-2022-41725Feb 28, 2023 · Excessive resource consumption in mime/multipart30Monitor
- Later →CVE-2023-24534Apr 6, 2023 · Excessive memory allocation in net/http and net/textproto31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go standard library crypto/internal/nistec | 1.19.7 | Vendor (CNA) |
| Go standard library crypto/internal/nistec | 1.20.2 | Vendor (CNA) |
| alpine:go | 1.19.7-r0 · Alpine:v3.17 | Package registry (OSV) |
| debian:golang-1.19 | 1.19.8-2 · Debian:12 | Package registry (OSV) |
| Go:stdlib | 1.19.7 | Package registry (OSV) |
| Go:stdlib | 1.20.2 | Package registry (OSV) |
| opensuse:go1.19 | 1.19.7-150000.1.23.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| opensuse:go1.20 | 1.20.2-150000.1.5.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| red hat:delve | 0:1.9.1-1.module+el8.8.0+16778+5fbb74f5 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:delve-debuginfo | 0:1.9.1-1.module+el8.8.0+16778+5fbb74f5 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:delve-debugsource | 0:1.9.1-1.module+el8.8.0+16778+5fbb74f5 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:go-toolset | 0:1.19.9-1.module+el8.8.0+18857+fca43658 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:golang | 0:1.19.9-2.el9_2 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:golang-bin | 0:1.19.9-2.el9_2 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:golang-docs | 0:1.19.9-2.el9_2 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:golang-misc | 0:1.19.9-2.el9_2 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:golang-race | 0:1.19.9-2.el9_2 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:golang-src | 0:1.19.9-2.el9_2 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:golang-tests | 0:1.19.9-2.el9_2 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| suse:container-suseconnect | 2.4.0-150000.4.24.1 · SUSE:Linux Enterprise Module for Containers 15 SP4 | Package registry (OSV) |
| suse:go1.19 | 1.19.7-150000.1.23.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP4 | Package registry (OSV) |
| suse:go1.20 | 1.20.2-150000.1.5.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP4 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-23-0169 · Mar 23, 2023(SUSE Güvenlik Güncellemesi)
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-682 · Incorrect CalculationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.