ChainApache FlumeMaven:org.apache.flume.flume-ng-sources:flume-jms-source
Apache Flume: successive fixes (2022)
3 CVEs over 3 generations, 14 Jun 2022 to 26 Oct 2022.
Family tree
Left to right by publication date.Oldest first. Select a CVE to open it.- CVE-2022-2516714 Jun 2022 First in the chain
- CVE-2022-3491621 Aug 2022 next fix after CVE-2022-25167
- CVE-2022-4246826 Oct 2022 related to CVE-2022-34916related to CVE-2022-25167
Exploited in the wild (CISA KEV) Not in KEV Priority score (0 to 100) High confidence Medium Low Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
CVEs in this family
Table view of the tree| CVE | Published | Title | Linked from | Priority |
|---|---|---|---|---|
| CVE-2022-25167 | 14 Jun 2022 | Apache Flume vulnerable to a JNDI RCE in JMSSource · fixed in 1.10.0 | First in chain | 18.5 |
| CVE-2022-34916 | 21 Aug 2022 | Improper Input Validation (JNDI Injection) in JMSMessageConsumer · fixed in 1.10.1 | CVE-2022-25167 · Next fix in the same package · Medium | 17.4 |
| CVE-2022-42468 | 26 Oct 2022 | Apache Flume prior to 1.11.0 has an Improper Input Validation (JNDI Injection) in JMSSource · fixed in 1.11.0 | CVE-2022-34916 · related · High | 24.8 |