ArtemisApplication · Apache
CVE-2017-12174
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIt was found that when Artemis and HornetQ before 2.4.0 are configured with UDP discovery and JGroups discovery a huge byte array is created when receiving an unexpected multicast message. This may result in a heap memory exhaustion, full GC, or OutOfMemoryError.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceWhen Artemis or HornetQ before version 2.4.0 are configured with UDP discovery or JGroups discovery protocols, receiving an unexpected multicast message triggers creation of an excessively large byte array. This leads to heap memory exhaustion, excessive garbage collection, and potential OutOfMemoryError, resulting in denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ArtemisApplication
< 2.4.0
HornetqApplication
< 2.4.0
Jboss Enterprise Application PlatformApplication
= 6.4.0= 7.1.0= 6.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the message broker product and versionLocate the Artemis or HornetQ installation and check the version file (e.g., lib/artemis-core-*.jar or check pom.xml, or run the broker with --version). For JBoss EAP, check the version via the JBoss CLI or management console.Affected if The installed version is below 2.4.0 for Artemis or HornetQ, or the EAP version is 6.4.0, 7.1.0, or 6.0.0.
-
Locate the broker configuration fileFind the broker.xml or hornetq-configuration.xml configuration file, typically in the etc/ or config/ directory of the broker installation.Affected if The configuration file exists in the standard configuration directory.
-
Check if UDP discovery is enabledOpen the broker configuration file and search for <discoveryGroup> elements with <groupAddress> and <udp> settings, or look for UDP-based discovery configuration in the transport connector settings.Affected if UDP discovery is configured (e.g., udp://239.0.0.0 or similar multicast addresses in discovery group settings).
-
Check if JGroups discovery is enabledOpen the broker configuration file and search for <discoveryGroup> elements that reference JGroups channels, or look for JGroups-specific discovery stack configurations.Affected if JGroups discovery is configured (e.g., jgroups-cluster or reference to a JGroups channel file).
You are affected if your broker version is below 2.4.0 and either UDP discovery or JGroups discovery is currently enabled in your configuration.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data2.4.0
Upgrade to Artemis or HornetQ version 2.4.0 or later, or alternatively disable UDP/JGroups discovery and use more secure, authenticated discovery mechanisms.
Fix this in Artemis
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12174 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-12174 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data