CVE-2019-5736
Public exploit code exists, so attacks usually follow. Schedule the vendor fix ahead of your normal cycle.
What it is
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.
Live exploitation on the huntback network (30 days)
Detection
Evidence
Weaponised. Exploit code is public but no exploitation is reported yet.
Published
Exploit code published (ExploitDB)
Exploit code published (Metasploit)
Observed: our own decoys saw it. Reported: CISA, the vendor or another named source says so. Weaponised: public exploit code or a scanner template exists. Methodology
Questions
Is CVE-2019-5736 being exploited in the wild?
Not on our sensors so far: the huntback decoy network has not captured an exploitation attempt, and it is not in the CISA KEV catalogue.
Can CVE-2019-5736 be detected on the network?
huntback has no wire signature for CVE-2019-5736 yet; it may need local or authenticated access to exploit.
How huntback helps
Deploy a decoy that emulates Backports Sle and you will see every attempt at this CVE the moment it lands, with the full payload, the attacker's infrastructure, and any stage-2 loader. Then huntback can scan the attacker back.
Related
NVD record → Browse all CVEs → Live malware and C2 finds → Novel-attack discovery → Deploy a decoy →API
This record, with its evidence timeline, as JSON:
curl -H "X-API-Key: $HUNTBACK_KEY" https://app.huntback.io/api/v1/evidence/CVE-2019-5736