CVE-2019-9893 Security feature bypass in n/a
Critical 9.8
Published
Updated
Check this codebase for CVE-2019-9893 and fix it if it is affected.
What it is: CVE-2019-9893 is a critical vulnerability in n/a, published on 21 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-9893 in the wild and no public exploit code.
Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2019-9893/ (Markdown: https://insights.sbomify.com/CVE-2019-9893/index.md)
A flaw in libseccomp allows bypassing seccomp filters via incorrect 64-bit comparisons, potentially enabling privilege escalation.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2019-9893?
CVE-2019-9893 is a critical vulnerability in n/a, published on 21 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Which versions are affected by CVE-2019-9893?
It affects 1 product.
Linux distribution packages (35)
libseccomp-debuginfo Red Hat:enterprise_linux:8::appstream | All versions | 0:2.4.1-1.el8 |
libseccomp-debugsource Red Hat:enterprise_linux:8::appstream | All versions | 0:2.4.1-1.el8 |
libseccomp-devel Red Hat:enterprise_linux:8::appstream | All versions | 0:2.4.1-1.el8 |
libseccomp-devel-debuginfo Red Hat:enterprise_linux:8::appstream | All versions | 0:2.4.1-1.el8 |
libseccomp Red Hat:enterprise_linux:8::baseos | All versions | 0:2.4.1-1.el8 |
libseccomp-debuginfo Red Hat:enterprise_linux:8::baseos | All versions | 0:2.4.1-1.el8 |
libseccomp-debugsource Red Hat:enterprise_linux:8::baseos | All versions | 0:2.4.1-1.el8 |
libseccomp-devel-debuginfo Red Hat:enterprise_linux:8::baseos | All versions | 0:2.4.1-1.el8 |
libseccomp-debuginfo Red Hat:enterprise_linux:8::crb | All versions | 0:2.4.1-1.el8 |
libseccomp-debugsource Red Hat:enterprise_linux:8::crb | All versions | 0:2.4.1-1.el8 |
libseccomp-devel Red Hat:enterprise_linux:8::crb | All versions | 0:2.4.1-1.el8 |
libseccomp-devel-debuginfo Red Hat:enterprise_linux:8::crb | All versions | 0:2.4.1-1.el8 |
libseccomp SUSE:Enterprise Storage 5 | All versions | 2.4.1-11.3.2 |
libseccomp SUSE:HPE Helion OpenStack 8 | All versions | 2.4.1-11.3.2 |
libseccomp SUSE:Linux Enterprise Desktop 12 SP4 | All versions | 2.4.1-11.3.2 |
libseccomp SUSE:Linux Enterprise Module for Basesystem 15 | All versions | 2.4.1-3.3.1 |
libseccomp SUSE:Linux Enterprise Module for Basesystem 15 SP1 | All versions | 2.4.1-3.3.1 |
libseccomp SUSE:Linux Enterprise Server 12 SP2-BCL | All versions | 2.4.1-11.3.2 |
libseccomp SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 2.4.1-11.3.2 |
libseccomp SUSE:Linux Enterprise Server 12 SP3-BCL | All versions | 2.4.1-11.3.2 |
libseccomp SUSE:Linux Enterprise Server 12 SP3-LTSS | All versions | 2.4.1-11.3.2 |
libseccomp SUSE:Linux Enterprise Server 12 SP4 | All versions | 2.4.1-11.3.2 |
libseccomp SUSE:Linux Enterprise Server 12 SP5 | All versions | 2.4.1-11.3.2 |
libseccomp SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 2.4.1-11.3.2 |
libseccomp SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 2.4.1-11.3.2 |
libseccomp SUSE:Linux Enterprise Server for SAP Applications 12 SP4 | All versions | 2.4.1-11.3.2 |
libseccomp SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 2.4.1-11.3.2 |
libseccomp SUSE:Linux Enterprise Software Development Kit 12 SP4 | All versions | 2.4.1-11.3.2 |
libseccomp SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 2.4.1-11.3.2 |
libseccomp SUSE:OpenStack Cloud 7 | All versions | 2.4.1-11.3.2 |
libseccomp SUSE:OpenStack Cloud 8 | All versions | 2.4.1-11.3.2 |
libseccomp SUSE:OpenStack Cloud Crowbar 8 | All versions | 2.4.1-11.3.2 |
libseccomp openSUSE:Leap 15.0 | All versions | 2.4.1-lp150.2.3.1 |
libseccomp openSUSE:Leap 15.1 | All versions | 2.4.1-lp151.3.3.1 |
libseccomp openSUSE:Tumbleweed | All versions | 2.5.2-2.1 |
Products include Libseccomp Project Libseccomp.
How do I fix CVE-2019-9893?
Upgrade to a fixed version.
Is CVE-2019-9893 being exploited?
There is no known exploitation of CVE-2019-9893 in the wild and no public exploit code.
Sources
Also known as ALPINE-CVE-2019-9893, DEBIAN-CVE-2019-9893, GHSA-8qf7-26p9-j472, MGASA-2020-0136, RHSA-2019:3624, SUSE-SU-2019:2517-1 and 7 more.