Cyber Resilience

CVE-2023-24537

Memory Safety in Golang Go ≤ 1.19.8

Memory Safety
Published
06 April 2023
Modified
12 February 2025
Patch / advisory
View advisory
CVSS Score v3.1 7.5
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:N/A:H
EPSS Score 0.014 70th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2023-24537 is a high-severity Integer Overflow or Wraparound (CWE-190) vulnerability in Golang Go. Its CVSS base score is 7.5 (High).

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

EU & UK References

Vulnerability Data

Calling any of the Parse functions on Go source code which contains //line directives with very large line numbers can cause an infinite loop due to integer overflow.

CWE(s)
CWE-190

Related Threats

CVEs Like This One

CVE-2026-27139Same product: Golang Go
CVE-2023-39326Same product: Golang Go
CVE-2025-61724Same product: Golang Go
CVE-2023-39320Same product: Golang Go
CVE-2025-58188Same product: Golang Go
CVE-2023-24540Same product: Golang Go
CVE-2023-24534Same product: Golang Go
CVE-2026-39817Same product: Golang Go
CVE-2026-27143Same product: Golang Go
CVE-2023-24538Same product: Golang Go

Affected Assets

golang
go
≤ 1.19.8 · 1.20.0 — 1.20.3

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V5.2.6

Mitigating Controls (NIST CSF 2.0) AI

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

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require use of safe arithmetic, bounds checks, and testing that prevent integer overflows.

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.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing in development can detect integer overflows before release.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates input validation and arithmetic checks that prevent integer overflows.

A.8.26 Application security requirements partial match
degrades

Application security requirements include bounds checking and safe arithmetic to avoid overflow conditions.

A.8.27 Secure system architecture and engineering principles partial match
degrades

Secure architecture principles require defensive coding patterns that mitigate integer wraparound risks.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly forbid unsafe integer operations and mandate overflow-safe constructs.

References