Skip to content
Fencer Vulns
high 7.8

CVE-2023-31722 json

There exists a heap buffer overflow in nasm 2.16.02rc1 (GitHub commit: b952891).

published 2023-05-17 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-36013

cvss
7.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 28%
public exploits
0
none known

Summary

There exists a heap buffer overflow in nasm 2.16.02rc1 (GitHub commit: b952891).

Patch / fix

  • nasm Ubuntu Pro 22.04 LTS 2.15.05-1ubuntu0.1~esm1
  • nasm Ubuntu Pro 24.04 LTS 2.16.01-1ubuntu0.1~esm1

ubuntu advisories UBUNTU-CVE-2023-31722

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2023-31722 updated cvss 5.5

nasm: heap buffer overflow in expand_mmacro() asm/preproc.c

  • Red Hat Enterprise Linux 6 nasm, nasm-rdoff Red Hat Enterprise Linux 7 nasm, nasm-rdoff
    affected: no fix planned “Out of support scope”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
21 mo ago

Exploit prediction

0.35% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • bugzilla.nasm.us https://bugzilla.nasm.us/show_bug.cgi?id=3392857#c1 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CISA ADP 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CNA 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.