runc up to 1.0-rc6 /proc/self/exe container error

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
8.9$0-$5k0.00

Summaryinfo

A vulnerability classified as critical was found in runc up to 1.0-rc6. Affected by this vulnerability is an unknown functionality of the file /proc/self/exe. The manipulation results in container error. This vulnerability is identified as CVE-2019-5736. The attack can be executed remotely. Additionally, an exploit exists.

Detailsinfo

A vulnerability, which was classified as very critical, was found in runc up to 1.0-rc6. Affected is an unknown function of the file /proc/self/exe. The manipulation with an unknown input leads to a container error vulnerability. CWE is classifying the issue as CWE-216. This entry has been deprecated, as it was not effective as a weakness and was structured more like a category. In addition, the name is inappropriate, since the "container" term is widely understood by developers in different ways than originally intended by PLOVER, the original source for this entry. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

runc through 1.0-rc6, as used in Docker before 18.09.2 and other products, allows attackers to overwrite the host runc binary (and consequently obtain host root access) by leveraging the ability to execute a command as root within one of these types of containers: (1) a new container with an attacker-controlled image, or (2) an existing container, to which the attacker previously had write access, that can be attached with docker exec. This occurs because of file-descriptor mishandling, related to /proc/self/exe.

The weakness was released 02/13/2019 by Adam Iwaniuk and Borys Pop?awski (Website). The advisory is available at exploit-db.com. This vulnerability is traded as CVE-2019-5736 since 01/08/2019. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. Technical details and a public exploit are known. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 10/01/2025). This vulnerability is assigned to T1611 by the MITRE ATT&CK project.

A public exploit has been developed by Aleksa Sarai (EMBARGO) and been published immediately after the advisory. The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 266258 (NewStart CGSL MAIN 6.06 : docker-ce Multiple Vulnerabilities (NS-SA-2025-0217)), which helps to determine the existence of the flaw in a target environment. The commercial vulnerability scanner Qualys is able to test this issue with plugin 157926 (Oracle Enterprise Linux Security Update for docker-engine (ELSA-2019-4551)).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the databases at Exploit-DB (46369), Tenable (266258) and SecurityFocus (BID 106976†). Entry connected to this vulnerability is available at VDB-122781. If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 9.1
VulDB Meta Temp Score: 8.6

VulDB Base Score: 9.6
VulDB Temp Score: 8.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 8.6
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Container error
CWE: CWE-216
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Yes

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Author: Aleksa Sarai (EMBARGO)
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 266258
Nessus Name: NewStart CGSL MAIN 6.06 : docker-ce Multiple Vulnerabilities (NS-SA-2025-0217)

Qualys ID: 🔍
Qualys Name: 🔍

Exploit-DB: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍
Exploit Delay Time: 🔍

Upgrade: github.com
Patch: github.com

Timelineinfo

01/08/2019 🔍
02/11/2019 +34 days 🔍
02/11/2019 +0 days 🔍
02/13/2019 +2 days 🔍
02/13/2019 +0 days 🔍
02/13/2019 +0 days 🔍
10/01/2025 +2422 days 🔍

Sourcesinfo

Advisory: RHSA-2019:0303
Researcher: Adam Iwaniuk, Borys Pop?awski
Status: Confirmed

CVE: CVE-2019-5736 (🔍)
GCVE (CVE): GCVE-0-2019-5736
GCVE (VulDB): GCVE-100-130746
SecurityFocus: 106976 - Opencontainers runc CVE-2019-5736 Local Command Execution Vulnerability

scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍

Entryinfo

Created: 02/12/2019 00:08
Updated: 10/01/2025 10:46
Changes: 02/12/2019 00:08 (46), 01/02/2020 13:12 (24), 07/09/2023 11:27 (6), 12/26/2024 16:00 (17), 10/01/2025 10:46 (3)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!