Skip to content
Fencer Intel
high 7.8

CVE-2019-8343 json

In Netwide Assembler (NASM) 2.14.02, there is a use-after-free in paste_tokens in asm/preproc.c.

published 7y ago modified 4mo ago also EUVD-2019-17733

cvss
7.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.1%
EPSS 1.1% chance of exploitation in 30 days, percentile 66%
public exploits
0
none known

Summary

In Netwide Assembler (NASM) 2.14.02, there is a use-after-free in paste_tokens in asm/preproc.c.

Patch / fix

  • nasm Arch Linux 2.15.02-1

arch linux advisories AVG-903

Is CVE-2019-8343 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-8343 updated cvss 7.3

nasm: use-after-free in paste_tokens in asm/preproc.c

  • Red Hat Enterprise Linux 6 nasm, nasm-rdoff
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 7 nasm, nasm-rdoff
    affected: no fix available “Fix deferred”
  • Red Hat Enterprise Linux 8 nasm
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 5 nasm
    not affected: vulnerable code not present

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

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

Exploits and checks

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

CVSS scores

assigned by version score vector
NVD 3.0 7.8 CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/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.