CVE-2017-12174: Uncontrolled Resource Consumption in Artemis and HornetQ

org.hornetq:hornetq-server Updated 02 Oct 2025

Summary

13/05/2022
Yes i
High
7.5

CVE-2017-12174: Uncontrolled Resource Consumption in Artemis and HornetQ. Affects org.hornetq:hornetq-server versions < 2.4.0.Final. Fixed in 2.4.0.Final. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Artemis and HornetQ are messaging systems that provide support for the Java Message Service (JMS) API. They are commonly used in enterprise applications for reliable and scalable messaging. These systems use UDP and JGroups discovery for network communication. However, versions before 2.4.0 are vulnerable to uncontrolled resource consumption when receiving unexpected multicast messages. This can lead to heap memory exhaustion, full garbage collection, or OutOfMemoryError.

Vulnerability Detail

The vulnerability arises from the creation of a large byte array when Artemis and HornetQ receive unexpected multicast messages. This can result in excessive memory usage, potentially leading to system instability or crashes. Attackers can exploit this vulnerability by sending specially crafted multicast messages, causing denial-of-service (DoS) conditions. The severity of this vulnerability is rated as HIGH with a CVSS score of 7.5.

How To Fix

Minimum fixed version

2.4.0.Final

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to apply the recommended fix by upgrading to the fixed versions of Artemis and HornetQ.

Conclusion

The vulnerability in Artemis and HornetQ versions before 2.4.0 can lead to uncontrolled resource consumption and potential denial-of-service (DoS) conditions. It is crucial to upgrade to the fixed versions and apply the recommended fix. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.hornetq:hornetq-server →

Share this vulnerability

FAQ

Artemis and HornetQ are messaging systems that provide support for the Java Message Service (JMS) API. They are commonly used in enterprise applications for reliable and scalable messaging.

The vulnerability can lead to uncontrolled resource consumption, potentially causing system instability or crashes. Attackers can exploit this vulnerability to create denial-of-service (DoS) conditions.

To fix this vulnerability, upgrade Artemis and HornetQ to version 2.4.0 or later. Update your dependencies and rebuild your applications. Review and update network configurations to prevent unauthorized multicast messages.

No, there is no known workaround for this vulnerability. It is crucial to apply the recommended fix by upgrading to the fixed versions of Artemis and HornetQ.

The severity of this vulnerability is rated as HIGH with a CVSS score of 7.5.

How To Fix

Minimum fixed version

2.4.0.Final

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback