CVE-2020-17519
This CVE is being exploited. Apply the vendor fix, or take the service off the internet until you can, then check your logs for attempts.
What it is
A change introduced in Apache Flink 1.11.0 (and released in 1.11.1 and 1.11.2 as well) allows attackers to read any file on the local filesystem of the JobManager through the REST interface of the JobManager process. Access is restricted to files accessible by the JobManager process. All users should upgrade to Flink 1.11.3 or 1.12.0 if their Flink instance(s) are exposed. The issue was fixed in commit b561010b0ee741543c3953306037f00d7a9f0801 from apache/flink:master.
Live exploitation on the huntback network (30 days)
Detection
Evidence
Exploited (reported). CISA added it to KEV 902 days ago.
Added to CISA Known Exploited Vulnerabilities
Published
Exploit code published (ExploitDB)
Exploit code published (Metasploit)
Nuclei detection template available
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-2020-17519 being exploited in the wild?
Yes. It is listed in the CISA Known Exploited Vulnerabilities catalogue. Our decoy network has not captured an attempt yet.
Can CVE-2020-17519 be detected on the network?
Yes. huntback carries a network signature for CVE-2020-17519, so attempts against a decoy are tagged in real time.
How huntback helps
Deploy a decoy that emulates Flink 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-2020-17519