CVE-2019-15890

libslirp 4.0.0, as used in QEMU 4.1.0, has a use-after-free in ip_reass in ip_input.c.

Published: 2019-09-06 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2019-15890 is rated Moderate Risk (54.1/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.57%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2019-15890

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-02-26 0.38% 0.57% +0.20%
2 2025-11-21 1.45% 0.38% -1.07%
3 2025-11-18 — 1.45% —

Full EPSS history (21 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2019-15890

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 [email protected]
5.0 2.0 MEDIUM
AV:N/AC:L/Au:N/C:N/I:N/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:P)
Partial availability impact.
 10.0 2.9 [email protected]

Weakness enumeration for CVE-2019-15890

OS Trackers for CVE-2019-15890

vendor priority summary link
debian not yet assigned CVE-2019-15890 not yet assigned priority: Debian including 2 source packages (qemu, slirp4netns), 10 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 10. https://security-tracker.debian.org/tracker/CVE-2019-15890
redhat medium — https://access.redhat.com/security/cve/CVE-2019-15890
suse medium CVE-2019-15890 severity moderate: SUSE including 1070 source package names (0.45.0.7.7.1:qemu-5.2.0-17.1, 0.45.0.7.7.1:qemu-ipxe-1.0.0+-17.1, …), 1766 product×package rows across 106 product lines (Container suse/sle-micro-rancher/5.2, Container suse/sles/15.3/cdi-importer, … (106 product lines)): Fixed 1440, Known Affected 225, Known Not Affected 101. https://www.suse.com/security/cve/CVE-2019-15890/
ubuntu low CVE-2019-15890 low priority: Ubuntu including 20 source packages (android, basilisk2, …), 360 status rows across 18 suites (bionic, disco, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 149, ignored 88, needs-triage 69, not-affected 36, released 18. https://ubuntu.com/security/CVE-2019-15890

Affected software / configurations for CVE-2019-15890

Vendor Product Version Raw CPE
libslirp_project libslirp 4.0.0 cpe:2.3:a:libslirp_project:libslirp:4.0.0:-:*:*:*:*:*:*
qemu qemu 4.1.0 cpe:2.3:a:qemu:qemu:4.1.0:*:*:*:*:*:*:*

References for CVE-2019-15890

cvelogic Threat Intelligence