CVE-2019-16884: Affected product: Incorrect Authorization

Distribution release	Source package	Vendor state	Fixed version	Evidence
Alpine v3.23v3.23 · community	`containerd`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`1.3.0-r0`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.23v3.23 · community	`runc`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`1.0.0_rc9-r0`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.22v3.22 · community	`containerd`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`1.3.0-r0`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.22v3.22 · community	`runc`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`1.0.0_rc9-r0`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.21v3.21 · community	`containerd`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`1.3.0-r0`	Alpine Security Database ↗Source updated 19 Aug 2026
Alpine v3.21v3.21 · community	`runc`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`1.0.0_rc9-r0`	Alpine Security Database ↗Source updated 19 Aug 2026
Debian trixietrixie · source	`golang-github-opencontainers-selinux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`1.3.0-2`	Debian Security Tracker ↗Source updated 7 Oct 2026
Debian trixietrixie · source	`runc`	Vendor fix publishedDebian records a fixed source-package version for this release.	`1.0.0~rc9+dfsg1-1`	Debian Security Tracker ↗Source updated 7 Oct 2026
Debian bookwormbookworm · source	`golang-github-opencontainers-selinux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`1.3.0-2`	Debian Security Tracker ↗Source updated 7 Oct 2026
Debian bookwormbookworm · source	`runc`	Vendor fix publishedDebian records a fixed source-package version for this release.	`1.0.0~rc9+dfsg1-1`	Debian Security Tracker ↗Source updated 7 Oct 2026
Debian forkyforky · source	`golang-github-opencontainers-selinux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`1.3.0-2`	Debian Security Tracker ↗Source updated 7 Oct 2026
Debian forkyforky · source	`runc`	Vendor fix publishedDebian records a fixed source-package version for this release.	`1.0.0~rc9+dfsg1-1`	Debian Security Tracker ↗Source updated 7 Oct 2026
Debian sidsid · source	`golang-github-opencontainers-selinux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`1.3.0-2`	Debian Security Tracker ↗Source updated 7 Oct 2026
Debian sidsid · source	`runc`	Vendor fix publishedDebian records a fixed source-package version for this release.	`1.0.0~rc9+dfsg1-1`	Debian Security Tracker ↗Source updated 7 Oct 2026

Recommended actionWithin 7 days

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Fix not verified

What, why and how

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.

What

Why

The application performs an authorisation check, but it does not correctly enforce the required permission boundary.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Why

The application performs an authorisation check, but it does not correctly enforce the required permission boundary.

How

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path: a network path → Incorrect Authorization → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface: Network
Privileges required: None: unauthenticated exploitation is possible
User interaction: None
Attack complexity: Low: no specialised conditions are recorded
Security boundary: Unchanged: impact remains within the vulnerable component's security authority
Weakness ? CWE means Common Weakness Enumeration: a standard category for the underlying weakness.: CWE-863 ↗
CWE-863: Incorrect Authorization. The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
CVSS vector ? CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.IHighIntegrity impact: A successful attack can cause a major loss.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land: No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.

NetworkUnauthenticatedCWE-863Public exploit reference

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2022-0981Official EUVD mapping

0 linked advisory records.

Official EUVD record ↗

BSI · German · WID-SEC-2022-0510IBM DB2: Mehrere Schwachstellen

Ein entfernter, anonymer, authentisierter oder lokaler Angreifer kann mehrere Schwachstellen in IBM DB2 ausnutzen, um Dateien zu manipulieren, Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen, einen Denial-of-Service-Zustand auszulösen, willkürlichen Code mit erhöhten Rechten auszuführen, Informationen falsch darzustellen und beliebigen Code auszuführen.

Official advisory ↗

BSI · German · WID-SEC-2025-2547docker: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen

Ein lokaler Angreifer kann eine Schwachstelle in docker ausnutzen, um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗

BSI · German · WID-SEC-2025-2490Red Hat OpenShift Container Platform: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen

Ein lokaler Angreifer kann eine Schwachstelle in der Red Hat OpenShift Container Platform ausnutzen, um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗

CERT-FR · French · CERTFR-2022-AVI-591Multiples vulnérabilités dans les produits IBM

d?id=CVE-2019-11247 Référence CVE CVE-2019-11249 https://www.cve.org/CVERecord?id=CVE-2019-11249 Référence CVE CVE-2019-11250 https://www.cve.org/CVERecord?id=CVE-2019-11250 Référence CVE CVE-2019-11251 https://www.cve.org/CVERecord?id=CVE-2019-11251 Référence CVE CVE-2019-11252 https://www.cve.org/CVERecord?id=CVE-2019-11252 Référence CVE CVE-2019-11253 https://www.cve.org/CVERecord?id=CVE-2019-11253 Référence CVE CVE-2019-11254 https://www.cve.org/CVERecord?id=CVE-2019-11254 Référence CVE CVE-2019-11840 https://www.cve.org/CVERecord?id=CVE-2019-11840 Référence CVE CVE-2019-11841 https://www.cve.org/CVERecord?id=CVE-2019-11841 Référence CVE CVE-2019-16884 https://www.cve.org/CVERecord?id=CVE-2019-16884 Référence CVE CVE-2020-10752 https://www.cve.org/CVERecord?id=CVE-2020-10752 Référence CVE CVE-2020-14040 https://www.cve.org/CVERecord?id=CVE-2020-14040 Référence CVE CVE-2020-15106 https://www.cve.org/CVERecord?id=CVE-2020-15106 Référence CVE CVE-2020-15112 https://www.cve.org/CVERecord?id=CVE-2020-15112 Référence CVE CVE-2020-15113 https://www.cve.org/CVERecord?id=CVE-2020-15113 Référence CVE CVE-2020-25704 https://www.cve.org/CVERecord?id=CVE-2020-25704 Référence CVE CVE-2020-26160 https://www.cve.org/CVERecord?id=CVE-2020-26160 Référence CVE CVE-2020-27813 https://www.cve.org/CVERecord?id=

Official advisory ↗

JVN iPedia · Japanese · JVNDB-2019-009746runc および Docker における不正な認証に関する脆弱性

runc および Docker には、不正な認証に関する脆弱性が存在します。

Official advisory ↗

Patch and workaround

Operational remediation based on structured source evidence.

Status ? Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.: Fix not verified
Affected: n/a
Fixed: No fixed version is explicitly recorded in the structured CVE data.
Action: No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
Workaround: No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.

Evidence and provenance

Published 25 Sept 2019 · Last source change 5 Aug 2024, 01:24 UTC · CWE-863 · Incorrect Authorization

CVE recordCVE.org · 5.1

CVSS sourceNIST NVD

EPSS source

The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.

FIRST · tracked since 2026-09-01

European sourceENISA EUVD · EUVD-2022-0981

Product sourceUnavailable

Remediation sourceCVE/CNA references

CWE sourceNIST NVD

NVD statusNVD modified after enrichment

Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗

1 Sep 2026, 02:42 UTC
ENISA EUVD mappingEUVD-2022-0981 was added to the official ENISA EUVD mapping for this CVE.
Before
not recorded
After
{"euvdId":"EUVD-2022-0981"}
ENISA EUVD ↗
5 Aug 2024, 01:24 UTC
Vendor guidanceAuthoritative vendor guidance changed: removed vendor advisory: access.redhat.com/RHSA-2019:3940; removed vendor advisory: access.redhat.com/RHSA-2019:4074; 9 further removals.
Before
vendor advisory: access.redhat.com/RHSA-2019:3940 · vendor advisory: access.redhat.com/RHSA-2019:4074 · vendor advisory: access.redhat.com/RHSA-2019:4269 · 8 more references
After
no authoritative guidance recorded
CNA ↗
5 Aug 2024, 01:24 UTC
Public exploit evidencePublic exploit evidence changed from No public exploit to Public exploit reference.
Before
No public exploit
After
Public exploit reference
github.com ↗
5 Aug 2024, 01:24 UTC
SeveritySeverity changed from Unknown to High.
Before
Unknown
After
High
NIST NVD ↗
5 Aug 2024, 01:24 UTC
CVSS scoreCVSS score changed from not recorded to 7.5 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N).
Before
not recorded
After
7.5 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N)
NIST NVD ↗
5 Aug 2024, 01:24 UTC
Catalogue recordCVE added to the BlackTree catalogue.
CNA ↗

2019-09-25CVE published

ENISA EUVD · EUVD-2022-0981↗Public exploit reference↗Official CVE record (CNA and ADP data)↗NVD record↗

Technical terms and abbreviations used in this report

CVE: Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS: Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS: Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE: Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA: CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP: Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD: National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT: A computer security incident response team that publishes warnings or coordinates incident response.
PoC: Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF: Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL: Living off the land: abuse of legitimate tools or system functions during an attack.

Affected product: Incorrect Authorization

Published severity in operational context

Evidence used

Compensating controls

Verification

Release-specific package status

National CERT insights
?
CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

ENISA European Vulnerability Database

EUVD-2022-0981

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

What changed after publication