Apache ActiveMQ Client, Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ Web, Apache ActiveMQ: Improper Limitation of a Pathname to a Restricted Classpath Directory
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- The rating the maker of the software gives it. Shown when it differs from the CVSS level.What do these mean? →
- Low (apache)
- Fix
- Fixed in 5.19.3, 6.2.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Improper validation and restriction of a classpath path name vulnerability in Apache ActiveMQ Client, Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ Web, Apache ActiveMQ. In two instances (when creating a Stomp consumer and also browsing messages in the Web console) an authenticated user provided "key" value could be constructed to traverse the classpath due to path concatenation. As a result, the application is exposed to a classpath path resource loading vulnerability that could potentially be chained together with another attack to lead to exploit. This issue affects Apache ActiveMQ Client: before 5.19.3, from 6.0.0 before 6.2.2; Apache ActiveMQ Broker: before 5.19.3, from 6.0.0 before 6.2.2; Apache ActiveMQ All: before 5.19.3, from 6.0.0 before 6.2.2; Apache ActiveMQ Web: before 5.19.3, from 6.0.0 before 6.2.2; Apache ActiveMQ: before 5.19.3, from 6.0.0 before 6.2.2. Users are recommended to upgrade to version 5.19.4 or 6.2.3, which fixes the issue. Note: 5.19.3 and 6.2.2 also fix this issue, but that is limited to non-Windows environments due to a path separator resolution bug fixed in 5.19.4 and 6.2.3.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- org.apache.activemq:activemq-client
fixed in 5.19.3; From 6.0.0 · fixed in 6.2.2
- org.apache.activemq:activemq-broker
fixed in 5.19.3; From 6.0.0 · fixed in 6.2.2
- org.apache.activemq:activemq-all
fixed in 5.19.3; From 6.0.0 · fixed in 6.2.2
- org.apache.activemq:activemq-web
fixed in 5.19.3; From 6.0.0 · fixed in 6.2.2
- org.apache.activemq:apache-activemq
fixed in 5.19.3; From 6.0.0 · fixed in 6.2.2
- org.apache.activemq:activemq-clientMaven
fixed in 5.19.3
- org.apache.activemq:activemq-clientMaven
From 6.0.0 · fixed in 6.2.2
- org.apache.activemq:activemq-brokerMaven
fixed in 5.19.3
- org.apache.activemq:activemq-brokerMaven
From 6.0.0 · fixed in 6.2.2
- org.apache.activemq:activemq-allMaven
fixed in 5.19.3
- org.apache.activemq:activemq-allMaven
From 6.0.0 · fixed in 6.2.2
- org.apache.activemq:activemq-webMaven
fixed in 5.19.3
- org.apache.activemq:activemq-webMaven
From 6.0.0 · fixed in 6.2.2