Sign inStart freeBook a demo

What is CVE-2019-5736?A high-severity flaw in Docker, explained.

High severity19 affected products
The short answer

CVE-2019-5736 is a high-severity flaw (CVSS 8.6) in Docker, published on 11 February 2019. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 98%. If you run an affected version, plan in the vendor’s fix.

Check if it affects you →How to fix it

Published 11 February 2019. Record last updated 2 February 2024. We keep this page's data up to date.

What it does

What is CVE-2019-5736? In plain terms.

An attacker has to be already on the device without logging in, but a person has to take an action first. If it works, the attacker can read data, change data and take it offline.

The official description

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.

What kind of flaw is it?

  • CWE-78Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
CVSS 3.1 scoreHigh · 8.6

How an attack on it works

Read straight from its severity rating, translated out of the shorthand.

  • Where an attacker can beAlready on the device
  • How hard it is to pull offEasy: no special conditions
  • Login needed firstNo login needed
  • Does someone have to clickYes, a person has to take an action
  • What an attacker getsCan read data, change data and take it offline

Severity vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Exploitation

Is CVE-2019-5736 being exploited? Not that we know of.

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 98%. That can change at any time, which is why we keep watching.

Known to be exploitedNoNot on the list of exploited flaws today
Chance of use in the next 30 days98%Its EPSS score, from the latest forecast

Timeline

  1. Published
  2. Record last updated
  3. Exploit likelihood fell
  4. Exploit likelihood jumped
How Precursor Intelligence ranks it
74out of 100High

CVE-2019-5736 scores 74. Action: Patch now.

We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:

  • Evidence it is being exploitedBiggest factor
  • How severe it isStrong factor
  • How widely exposed it isSmaller factor
  • Threat activity around itSmaller factor

85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.

When CVE-2019-5736 matches software you track, it lands in your list with its score and the reasons behind it.

See your own ranked list →
Affected products

Who is affected by CVE-2019-5736? 19 products.

The published record lists 19 products from 13 vendors. Versions are shown as published: "before 18.09.2" means every version up to, but not including, 18.09.2. If you run one of these, check your version, then go to the fix below.

Remediation

How do I fix CVE-2019-5736? Four steps.

  1. Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
  2. Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list.
  3. If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
  4. Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.

References

50 links
Precursor Intelligence

Does CVE-2019-5736 affect you? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Start free →Book a demo

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

CVE-2019-5736 is a high-severity flaw in Docker, published on 11 February 2019. An attacker has to be already on the device without logging in, but a person has to take an action first. If it works, the attacker can read data, change data and take it offline.

It scores 8.6 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2019-5736 is 74 out of 100, which is High. Its action is "Patch now". Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month.

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 98%. That can change at any time, which is why we keep watching.

For Docker: before 18.09.2. The record lists 19 products in all, each with its versions, under "Who is affected" on this page.

Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.

Keep exploring