Credential disclosure via JMXRMI registry rebinding
Published May 14, 2020 · Updated Aug 4, 2024
JMX injection in Apache Flink 1.1.0 through 1.9.2 and 1.10.0 allows local users to intercept JMX sessions and read transferred data. JMXReporter accepts a crafted request that rebinds its configured JMXRMI registry to an attacker-controlled endpoint. Exploitation requires local access to the host and JMX port; the resulting interception exposes credentials and other JMX data without reported integrity or availability impact.
Summary
What happened
JMX injection in Apache Flink 1.1.0 through 1.9.2 and 1.10.0 allows local users to intercept JMX sessions and read transferred data. JMXReporter accepts a crafted request that rebinds its configured JMXRMI registry to an attacker-controlled endpoint. Exploitation requires local access to the host and JMX port; the resulting interception exposes credentials and other JMX data without reported integrity or availability impact.
The record
- CVE
- CVE-2020-1960
- Published
- May 14, 2020
- Updated
- Aug 4, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache Flink
- Classifications
- CWE-74, T1557
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 14, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Apache Flink 1.1.0 to 1.1.5, 1.2.0 to 1.2.1, 1.3.0 to 1.3.3, 1.4.0 to 1.4.2, 1.5.0 to 1.5.6, 1.6.0 to 1.6.4, 1.7.0 to 1.7.2, 1.8.0 to 1.8.3, 1.9.0 to 1.9.2, 1.10.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo