Skip to content
Fencer Vulns
high 7.8

CVE-2018-8883 json

Netwide Assembler (NASM) 2.13.02rc2 has a buffer over-read in the parse_line function in asm/parser.c via uncontrolled access to nasm_reg_f…

published 2018-03-20 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-20491

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

Summary

Netwide Assembler (NASM) 2.13.02rc2 has a buffer over-read in the parse_line function in asm/parser.c via uncontrolled access to nasm_reg_flags.

Patch / fix

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

debian advisories DEBIAN-CVE-2018-8883

  • nasm SLE Module for Development Tools 15 SP2, SLE Module for Development Tools 15 SP1 2.14.02-3.4.1

suse advisories SUSE-SU-2020:1843-1

  • nasm openSUSE Leap 15.2 2.14.02-lp152.4.3.1
  • nasm openSUSE Leap 15.1 2.14.02-lp151.3.3.1

opensuse advisories openSUSE-SU-2020:0954-1openSUSE-SU-2020:0952-1

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-2018-8883 updated cvss 3.3

nasm: Buffer over-read in parse_line function in asm/parser.c

  • Red Hat Enterprise Linux 5 nasm 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 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.37% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.0 7.8 CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 4.6 AV:L/AC:L/Au:N/C:P/I:P/A:P

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.