Description
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.
CVSS breakdown
Affected products
- Apache Software Foundation / Apache ActiveMQ0 – 5.19.3
- Apache Software Foundation / Apache ActiveMQ6.0.0 – 6.2.2
- Apache Software Foundation / Apache ActiveMQ All6.0.0 – 6.2.2
- Apache Software Foundation / Apache ActiveMQ All0 – 5.19.3
- Apache Software Foundation / Apache ActiveMQ Broker0 – 5.19.3
- Apache Software Foundation / Apache ActiveMQ Broker6.0.0 – 6.2.2
- Apache Software Foundation / Apache ActiveMQ Client6.0.0 – 6.2.2
- Apache Software Foundation / Apache ActiveMQ Client0 – 5.19.3
- Apache Software Foundation / Apache ActiveMQ Web0 – 5.19.3
- Apache Software Foundation / Apache ActiveMQ Web6.0.0 – 6.2.2