Skip to content
Fencer Intel
critical 9.8

CVE-2019-9893 json

libseccomp before 2.4.0 did not correctly generate 64-bit syscall argument comparisons using the arithmetic operators (LT, GT, LE, GE), whi…

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

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

Summary

libseccomp before 2.4.0 did not correctly generate 64-bit syscall argument comparisons using the arithmetic operators (LT, GT, LE, GE), which might able to lead to bypassing seccomp filters and potential privilege escalations.

Patch / fix

  • libseccomp_project libseccomp 2.4.0
  • libseccomp Debian 14, Debian 13, Debian 12 2.4.1-1

debian advisories DEBIAN-CVE-2019-9893

  • libseccomp Ubuntu 16.04 LTS 2.4.1-0ubuntu0.16.04.2
  • libseccomp Ubuntu 18.04 LTS 2.4.1-0ubuntu0.18.04.2
  • libseccomp Ubuntu Pro 14.04 LTS 2.4.1-0ubuntu0.14.04.2

ubuntu advisories UBUNTU-CVE-2019-9893

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

  • libseccomp RHEL 8 2.4.1-1.el8

red hat advisories RHSA-2019:3624

  • libseccomp SLES for SAP 12 SP5, SLES for SAP 12 SP4, SLES for SAP 12 SP3 +15 more 2.4.1-11.3.2
  • libseccomp SLE Module for Basesystem 15 SP1, SLE Module for Basesystem 15 2.4.1-3.3.1

suse advisories SUSE-SU-2019:2941-1SUSE-SU-2019:2517-1

  • libseccomp openSUSE Tumbleweed 2.5.2-2.1
  • libseccomp openSUSE Leap 15.1 2.4.1-lp151.3.3.1
  • libseccomp openSUSE Leap 15.0 2.4.1-lp150.2.3.1

opensuse advisories openSUSE-SU-2024:10989-1openSUSE-SU-2019:2283-1openSUSE-SU-2019:2280-1

  • libseccomp Alpine 3.24, Alpine 3.23, Alpine 3.22 +14 more 2.4.0-r0

alpine advisories ALPINE-CVE-2019-9893

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • libseccomp Arch Linux 2.4.0-1

arch linux advisories AVG-928

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

libseccomp: incorrect generation of syscall filters in libseccomp

  • Red Hat Enterprise Linux 7 libseccomp
    affected: no fix planned “Will not fix”
  • Red Hat CodeReady Linux Builder (v. 8) libseccomp-devel 2.4.1-1.el8, libseccomp-debuginfo 2.4.1-1.el8, libseccomp-debugsource 2.4.1-1.el8, libseccomp-devel-debuginfo 2.4.1-1.el8 Red Hat Enterprise Linux AppStream (v. 8) libseccomp-devel 2.4.1-1.el8, libseccomp-debuginfo 2.4.1-1.el8, libseccomp-debugsource 2.4.1-1.el8, libseccomp-devel-debuginfo 2.4.1-1.el8 Red Hat Enterprise Linux BaseOS (v. 8) libseccomp 2.4.1-1.el8
    fixed: vendor fix RHSA-2019:3624

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 ICSA-24-284-16 updated cvss 9.8

Rockwell Automation DataMosaix Private Cloud

  • Rockwell Automation DataMosaix Private Cloud <=7.07
    affected: mitigation “Rockwell Automation encourages users to implement security best practices to minimize the risk of the vulnerability.” rockwellautomation.custhelp.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Exploit prediction

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

CVSS scores

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

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.