CVE-2022-25167 json
Apache Flume vulnerable to a JNDI RCE in JMSSource
published 2022-06-14 4 y ago modified 2026-06-17 4 mo ago also GHSA-x5m7-rwfx-w7qm , EUVD-2022-6182
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 5.4%
- EPSS 5.4% chance of exploitation in 30 days, percentile 92%
- public exploits
- 0
- none known
Summary
Apache Flume versions 1.4.0 through 1.9.0 are vulnerable to a remote code execution (RCE) attack when a configuration uses a JMS Source with a JNDI LDAP data source URI when an attacker has control of the target LDAP server. This issue is fixed by limiting JNDI to allow only the use of the java protocol or no protocol.
Patch / fix
- maven org.apache.flume.flume-ng-sources:flume-jms-source 1.10.0
- Apache Software Foundation Apache Flume 1.10.0
Exploit prediction
5.40% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.flume.flume-ng-sources:flume-jms-source | >=1.4.0, <1.10.0 |
1.10.0 |
Affected products
- Apache Software Foundation Apache Flume
Classification
References
-
issues.apache.org
/jira/browse/FLUME-3416
web, issue-tracking, patch, vendor-advisory
-
github.com
/apache/flume/commit/dafb26ccb172141c6e14e95447e1b6ae38e9a7d0
web
-
lists.apache.org
/thread/16nf6b81zjpdc4y93ho99oxo83ddbsvg
web, broken-link
-
openwall.com
/lists/oss-security/2022/06/14/1
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-25167
advisory
-
github.com
/apache/flume
package
Sources
- CVE List CVE-2022-25167
- GitHub Advisory GHSA-x5m7-rwfx-w7qm
- NVD CVE-2022-25167
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.