CVE-2020-1960 is a vulnerability in Apache Flink affecting versions 1.1.0 through 1.10.0 across multiple release branches. The issue occurs when a Flink process is started with JMXReporter enabled and a JMX reporter port explicitly configured. Under those conditions, an attacker with local access to the host and access to the JMX port can send a specially crafted request that rebinds the JMXRMI registry to an attacker-controlled registry. This enables a man-in-the-middle condition on JMX communications to the affected Flink process, compromising the integrity and confidentiality of JMX sessions and exposing credentials and other data transmitted over those connections.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A man-in-the-middle vulnerability in Apache Flink's JMXReporter/JMXRMI handling that allows a local attacker with access to the machine and JMX port to rebind the JMXRMI registry, intercept JMX connections, and extract credentials and transferred data.
A known Apache Flink security vulnerability mentioned as one of several recently known flaws that were fixed in Flink 1.12.2-rc2.
A fixed vulnerability affecting multiple Apache Flink versions, with users advised to upgrade to Flink 1.9.3 or 1.10.1 or later.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.