# CVE-2019-16884: Incorrect Authorization in runc > A malicious Docker image can bypass AppArmor restrictions by mounting over /proc due to incorrect mount target checks in runc. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 25 Sep 2019 - **Updated:** 5 Aug 2024 - **Also known as:** CLEANSTART-2025-LA45180, CLEANSTART-2026-FJ66856, DEBIAN-CVE-2019-16884, DLA-3322-1, GHSA-fgv8-vj5c-2ppq, GO-2021-0085, MGASA-2020-0050, RHBA-2020:1232, RHSA-2019:3940, RHSA-2019:4074, SUSE-SU-2019:2786-1, SUSE-SU-2019:2787-1, SUSE-SU-2019:2810-1, SUSE-SU-2020:0035-1, SUSE-SU-2020:0065-1, UBUNTU-CVE-2019-16884, openSUSE-SU-2019:2418-1, openSUSE-SU-2019:2434-1, openSUSE-SU-2020:0045-1 ## What is CVE-2019-16884? CVE-2019-16884 is a high-severity vulnerability in Canonical Ubuntu Linux, published on 25 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description runc through 1.0.0-rc8, as used in Docker through 19.03.2-ce and other products, allows AppArmor restriction bypass because libcontainer/rootfs_linux.go incorrectly checks mount targets, and thus a malicious Docker image can mount over a /proc directory. Weakness: CWE-863 (Incorrect Authorization) ## Which versions are affected by CVE-2019-16884? 6 open source packages ship an affected version, including github.com/opencontainers/selinux and github.com/opencontainers/runc. It affects 10 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/opencontainers/selinux` | Go | All versions | 1.3.1-0.20190929122143-5215b1806f52 | | `github.com/opencontainers/selinux` | Go | All versions | 1.3.1-0.20190929122143-5215b1806f52 | | `github.com/opencontainers/selinux` | Go | All versions | 1.3.1-0.20190929122143-5215b1806f52 | | `github.com/opencontainers/runc` | Go | All versions | 1.0.0-rc8.0.20190930145003-cad42f6e0932 | | `github.com/opencontainers/runc` | Go | All versions | 1.0.0-rc8.0.20190930145003-cad42f6e0932 | | `github.com/opencontainers/runc` | Go | All versions | 1.0.0-rc8.0.20190930145003-cad42f6e0932 | | `runc` | Red Hat:openshift:4.1::el8 | All versions | 0:1.0.0-62.rc8.rhaos4.1.git3cbe540.el8 | | `runc-debuginfo` | Red Hat:openshift:4.1::el8 | All versions | 0:1.0.0-62.rc8.rhaos4.1.git3cbe540.el8 | | `runc-debugsource` | Red Hat:openshift:4.1::el8 | All versions | 0:1.0.0-62.rc8.rhaos4.1.git3cbe540.el8 | | `runc` | Red Hat:openshift:4.2::el8 | All versions | 0:1.0.0-63.rc8.el8 | | `runc-debuginfo` | Red Hat:openshift:4.2::el8 | All versions | 0:1.0.0-63.rc8.el8 | | `runc-debugsource` | Red Hat:openshift:4.2::el8 | All versions | 0:1.0.0-63.rc8.el8 | | `runc` | Red Hat:rhel_extras_other:7 | All versions | 0:1.0.0-67.rc10.el7_8 | | `runc-debuginfo` | Red Hat:rhel_extras_other:7 | All versions | 0:1.0.0-67.rc10.el7_8 | | `containerd` | SUSE:Linux Enterprise Module for Containers 12 | All versions | 1.2.10-16.26.1 | | `docker` | SUSE:Linux Enterprise Module for Containers 12 | All versions | 19.03.5_ce-98.51.1 | | `docker-runc` | SUSE:Linux Enterprise Module for Containers 12 | All versions | 1.0.0rc8+gitr3826_425e105d5a03-1.32.1 | | `docker-runc` | SUSE:Linux Enterprise Module for Containers 12 | All versions | 1.0.0rc8+gitr3917_3e425f80a8c9-1.35.1 | | `golang-github-docker-libnetwork` | SUSE:Linux Enterprise Module for Containers 12 | All versions | 0.7.0.1+gitr2877_3eb39382bfa6-28.1 | | `containerd` | SUSE:Linux Enterprise Module for Containers 15 | All versions | 1.2.10-5.19.1 | | `docker` | SUSE:Linux Enterprise Module for Containers 15 | All versions | 19.03.5_ce-6.31.1 | | `docker-runc` | SUSE:Linux Enterprise Module for Containers 15 | All versions | 1.0.0rc8+gitr3826_425e105d5a03-6.24.1 | | `docker-runc` | SUSE:Linux Enterprise Module for Containers 15 | All versions | 1.0.0rc8+gitr3917_3e425f80a8c9-6.27.1 | | `golang-github-docker-libnetwork` | SUSE:Linux Enterprise Module for Containers 15 | All versions | 0.7.0.1+gitr2877_3eb39382bfa6-4.18.1 | | `containerd` | SUSE:Linux Enterprise Module for Containers 15 SP1 | All versions | 1.2.10-5.19.1 | | `docker` | SUSE:Linux Enterprise Module for Containers 15 SP1 | All versions | 19.03.5_ce-6.31.1 | | `docker-runc` | SUSE:Linux Enterprise Module for Containers 15 SP1 | All versions | 1.0.0rc8+gitr3826_425e105d5a03-6.24.1 | | `docker-runc` | SUSE:Linux Enterprise Module for Containers 15 SP1 | All versions | 1.0.0rc8+gitr3917_3e425f80a8c9-6.27.1 | | `golang-github-docker-libnetwork` | SUSE:Linux Enterprise Module for Containers 15 SP1 | All versions | 0.7.0.1+gitr2877_3eb39382bfa6-4.18.1 | | `runc` | SUSE:Linux Enterprise Module for Containers 15 SP1 | All versions | 1.0.0~rc8-1.6.1 | | `docker-runc` | openSUSE:Leap 15.0 | All versions | 1.0.0rc8+gitr3826_425e105d5a03-lp150.5.28.1 | | `containerd` | openSUSE:Leap 15.1 | All versions | 1.2.10-lp151.2.9.1 | | `docker` | openSUSE:Leap 15.1 | All versions | 19.03.5_ce-lp151.2.15.1 | | `docker-runc` | openSUSE:Leap 15.1 | All versions | 1.0.0rc8+gitr3826_425e105d5a03-lp151.3.9.1 | | `docker-runc` | openSUSE:Leap 15.1 | All versions | 1.0.0rc8+gitr3917_3e425f80a8c9-lp151.3.12.1 | | `golang-github-docker-libnetwork` | openSUSE:Leap 15.1 | All versions | 0.7.0.1+gitr2877_3eb39382bfa6-lp151.2.9.1 | Products: Canonical Ubuntu Linux, Docker Docker, Fedoraproject Fedora, Linuxfoundation Runc, Opensuse Leap, Redhat Enterprise Linux, Redhat Enterprise Linux Eus, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Tus, Redhat Openshift Container Platform. ## How do I fix CVE-2019-16884? Upgrade github.com/opencontainers/selinux to 1.3.1-0.20190929122143-5215b1806f52 or later. ## Is CVE-2019-16884 being exploited? There is no known exploitation of CVE-2019-16884 in the wild and no public exploit code. ## Other vulnerabilities in Canonical Ubuntu Linux - [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild) - [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild) - [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild) - [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-16884 and fix it if it is affected. What it is: CVE-2019-16884 is a high-severity vulnerability in Canonical Ubuntu Linux, published on 25 Sep 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-16884 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/opencontainers/selinux (Go): affected all versions; fixed in 1.3.1-0.20190929122143-5215b1806f52 - github.com/opencontainers/selinux (Go): affected all versions; fixed in 1.3.1-0.20190929122143-5215b1806f52 - github.com/opencontainers/selinux (Go): affected all versions; fixed in 1.3.1-0.20190929122143-5215b1806f52 - github.com/opencontainers/runc (Go): affected all versions; fixed in 1.0.0-rc8.0.20190930145003-cad42f6e0932 - github.com/opencontainers/runc (Go): affected all versions; fixed in 1.0.0-rc8.0.20190930145003-cad42f6e0932 - github.com/opencontainers/runc (Go): affected all versions; fixed in 1.0.0-rc8.0.20190930145003-cad42f6e0932 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-16884/ (Markdown: https://insights.sbomify.com/CVE-2019-16884/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-16884 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-16884 - OSV: https://osv.dev/vulnerability/CVE-2019-16884 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-16884/ Summaries are generated and may contain mistakes; the official description above is the record.