Classpath-dependent compromise via unfiltered JMX credential objects
Published Jan 26, 2022 · Updated Aug 4, 2024
Unsafe deserialization in Apache Karaf before 4.3.6 allows remote attackers to trigger classpath-dependent impacts through JMX. The RMI connector accepts serialized credential objects without limiting their classes to java.lang.String before authentication. No credentials or user interaction are required, but consequences depend on gadget-capable system classes, which are limited in the default JMX server classpath.
Summary
What happened
Unsafe deserialization in Apache Karaf before 4.3.6 allows remote attackers to trigger classpath-dependent impacts through JMX. The RMI connector accepts serialized credential objects without limiting their classes to java.lang.String before authentication. No credentials or user interaction are required, but consequences depend on gadget-capable system classes, which are limited in the default JMX server classpath.
The record
- CVE
- CVE-2021-41766
- Published
- Jan 26, 2022
- Updated
- Aug 4, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache Karaf
- Classifications
- CWE-502, T1210
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 26, 2022CVE 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 Karaf <4.3.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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