Apache Flume vulnerable to remote code execution via deserialization of unsafe providerURL
Flume’s JMSSource class can be configured with a providerUrl parameter. A JNDI lookup is performed on this name without performing validation. This could result in untrusted data being deserialized, leading to remote code execution (RCE) attack when a configuration uses a JMS Source with an unsafe providerURL. This issue is fixed in version 1.11.0.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Java / Kotlin (Maven) | org.apache.flume.flume-ng-sources:flume-jms-source | < 1.11.0 | 1.11.0 |
References
- https://nvd.nist.gov/vuln/detail/CVE-2022-42468
- https://github.com/apache/flume/commit/eee179a09df405c1ab55ae25a53b76ca1050bb97
- https://github.com/apache/flume
- https://issues.apache.org/jira/browse/FLUME-3437
- https://lists.apache.org/thread/1ckhmp539zr2nd2rs45pocpywk2d9zvz
- https://lists.apache.org/thread/939wkx8o90bp6m2ht3t1sdyo1ncypl78
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H- Weakness (CWE)
CWE-20, CWE-502- Platform
- Java / Kotlin (Maven)
- Package
org.apache.flume.flume-ng-sources:flume-jms-source- Disclosed
- 26.10.2022
- Updated
- 11.10.2026 11:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-9w4g-fp9h-3q2v - CC BY 4.0
Vulnerability history: org.apache.flume.flume-ng-sources:flume-jms-source
All published vulnerabilities of this package (Java / Kotlin (Maven)), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 3
- First → latest
- 06.2022 10.2022
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- Critical 2
- High 1
Disclosures per year
- 2022: 3
- 2023: 0
- 2024: 0
- 2025: 0
- 2026: 0
-
Apache Flume vulnerable to remote code execution via deserialization of unsafe providerURL this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.