Security Resilience

CVE-2023-24532

Golang Go ≤ 1.19.7

Published
08 March 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS Score 0.0082 56th percentile
Risk Priority 46 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-24532 is a medium-severity Incorrect Calculation (CWE-682) vulnerability in Golang Go. Its CVSS base score is 5.3 (Medium).

Operationally, ranked in the top 44% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

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.

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-42501Same product: Golang Go
CVE-2023-39326Same product: Golang Go
CVE-2026-32281Same product: Golang Go
CVE-2025-58188Same product: Golang Go
CVE-2025-47906Same product: Golang Go
CVE-2025-61731Same product: Golang Go
CVE-2025-61730Same product: Golang Go
CVE-2025-58189Same product: Golang Go
CVE-2025-22873Same product: Golang Go
CVE-2023-39319Same product: Golang Go

Affected Assets

golang
go
≤ 1.19.7 · 1.20.0 — 1.20.2

Mitigating Controls

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

blocks

Secure development lifecycle mandates verification steps that catch incorrect calculations before they reach production.

blocks

A.8.26 requires that security requirements (including resilience against attacks such as buffer overflows or SQL injection) be identified during development or acquisition; it does not itself enforce correct calculations or stop an arithmetic error from being introduced or exploited.

removes

A.8.27 mandates establishing and applying secure engineering principles (including secure-by-design, least privilege, and design reviews) but does not itself remove or rewrite an incorrect calculation already present in first-party code; that is a code defect class reached only by testing or remediation controls per the locus rule.

prevents

Secure coding standards directly prohibit unsafe arithmetic and require defensive checks against incorrect results.

finds

Security testing in development and acceptance can detect calculation flaws before deployment.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-682, a pillar-level weakness, and none of its children carries one either.

References