Skip to content
Fencer Intel
high 7.1

CVE-2019-20352 json

In Netwide Assembler (NASM) 2.15rc0, a heap-based buffer over-read occurs (via a crafted .asm file) in set_text_free when called from expan…

published 6y ago modified 4mo ago also EUVD-2019-10905

cvss
7.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 58%
public exploits
0
none known

Summary

In Netwide Assembler (NASM) 2.15rc0, a heap-based buffer over-read occurs (via a crafted .asm file) in set_text_free when called from expand_one_smacro in asm/preproc.c.

Patch / fix

  • nasm Debian 14, Debian 13, Debian 12 2.15.04-1

debian advisories DEBIAN-CVE-2019-20352

Is CVE-2019-20352 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2019-20352 updated cvss 7.1

nasm: heap-based buffer over-read in set_text_free when called from expand_one_smacro in asm/preproc.c

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

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

Exploit prediction

0.84% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

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

CVSS scores

assigned by version score vector
NVD 3.1 7.1 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H
NVD 2.0 5.8 AV:N/AC:M/Au:N/C:P/I:N/A:P

Classification

Weakness

References

Sources

Fencer Intel 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.