← gociux.comall exploited CVEs

Exploited vulnerability · CISA KEV

Is CVE-2020-17519 exploited? Yes: in CISA KEV since 23 May 2024

Gociux · Apache Flink · data: CISA KEV, CVE record, FIRST EPSS

Yes. CVE-2020-17519, Apache Flink Improper Access Control Vulnerability, is being exploited in the wild. CISA added it to its Known Exploited Vulnerabilities catalog on 23 May 2024, 1234 days after it was published. It affects Apache Flink. If you run it, CISA's required action is: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

exploitedYesCISA KEV · 23 May 2024
ransomwareNot knownno confirmed use
EPSStop 1%among the most likely CVEs to be exploited
severity9.1CVSS 3.1 · critical
US federal due13 Jun 2024BOD 22-01 deadline

What it is

Apache Flink contains an improper access control vulnerability that allows an attacker to read any file on the local filesystem of the JobManager through its REST interface.

VendorApache (41 exploited CVEs in KEV)
ProductFlink
VulnerabilityApache Flink Improper Access Control Vulnerability
WeaknessCWE-552
Published5 Jan 2021
Added to KEV23 May 2024
Reported by (CNA)apache

What to do

  1. Check whether you run it. Look for Flink in your asset inventory, including appliances and cloud images. Stack check lists every exploited Apache CVE at once.
  2. Apply the fix. Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
  3. If you can't patch today, take the affected service off the internet or restrict who can reach it, and check its logs for signs of compromise since 5 Jan 2021.
  4. Get told next time. Email alerts when CISA adds a CVE for Apache.

References

Questions

Is CVE-2020-17519 being exploited?

Yes. CISA added CVE-2020-17519 to the Known Exploited Vulnerabilities catalog on 23 May 2024, which means there is reliable evidence of exploitation in the wild.

Is CVE-2020-17519 used in ransomware attacks?

CISA does not list known ransomware use for it. That can change, and exploitation alone is reason to fix it first.

How do I fix CVE-2020-17519?

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. Check Apache's advisory for the fixed versions, and if you can't patch quickly, restrict access to the affected Flink and watch it for signs of compromise.

Sources: CISA KEV (exploitation, ransomware use, required action, due date), the CVE record (publication date, CVSS, CNA), NVD and FIRST EPSS (live score). More: all KEV additions in May 2024 · Apache scorecard · act-now radar.

Running Apache in a regulated environment?

We check exposure across your estate, patch or mitigate with your team, and set up detection for what attackers do after exploiting it.

Get in touch →