Bug 2126222 (CVE-2022-34916) - CVE-2022-34916 flume: JNDI Injection in JMSMessageConsumer
Summary: CVE-2022-34916 flume: JNDI Injection in JMSMessageConsumer
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2022-34916
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 2120123
TreeView+ depends on / blocked
 
Reported: 2022-09-12 22:16 UTC by Chess Hazlett
Modified: 2026-08-04 06:26 UTC (History)
39 users (show)

Fixed In Version: flume 1.10.1
Clone Of:
Environment:
Last Closed: 2022-11-30 10:32:13 UTC
Embargoed:

Attachments (Terms of Use)

Description Chess Hazlett 2022-09-12 22:16:44 UTC 
Apache Flume versions 1.4.0 through 1.10.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.
Comment 1 Chess Hazlett 2022-09-12 23:30:53 UTC 
jdg does not ship flume in its delivered code, deptopia references indicate log4j2 for some reason.
amq clients points to affected version in maven pom.
amq streams does not ship.
eap-7 appears to enable flume.
eap-xp4 does not ship.
Comment 6 Product Security DevOps Team 2022-11-30 10:32:11 UTC 
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2022-34916
Note You need to log in before you can comment on or make changes to this bug.