Denial of Service (DoS) Affecting org.apache.activemq:artemis-core-client package, versions [2.0.0, 2.4.0)[1.0.0, 1.5.6)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-JAVA-ORGAPACHEACTIVEMQ-585944
- published19 Jul 2020
- disclosed7 Mar 2018
- creditBharti Kundal of Red Hat Inc
Introduced: 7 Mar 2018
CVE-2017-12174 (opens in a new tab)How to fix?
Upgrade org.apache.activemq:artemis-core-client to version 2.4.0, 1.5.6 or higher.
Overview
org.apache.activemq:artemis-core-client is a High-performance, non-blocking architecture for the next generation of event-driven messaging applications.
Affected versions of this package are vulnerable to Denial of Service (DoS). If an Apache Artemis broker is configured with discovery enabled (either UDP or JGroups), on receiving of a packet over a discovery endpoint, Apache Artemis will attempt to decode the packet and as part of it an encoded simple string. The first four bytes of the encoded simple string represent it's length. During the decoding process Apache Artemis will create a byte array of the same length. It is possible therefore to send a manipulated packet to Apache Artemis with a very large integer in the first four bytes of the simple string encoding. Upon receiving the packet the broker will attempt to allocate a byte array of this large size. This could result in heap memory exhaustion, full GC or in the worst case an unrecoverable OutOfMemoryError, resulting in loss of service.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
Two common types of DoS vulnerabilities:
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm
wspackage