Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven
Not in CISA KEV
HIGH severity

CVE-2017-12174 hornetq-server

HIGH

CVE-2017-12174 is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in org.hornetq:hornetq-server. A fix is available for org.hornetq:hornetq-server — see the affected versions and patch details below.

Uncontrolled Resource Consumption in Artemis and HornetQ

Also known asGHSA-gc96-h5pr-839j
Published
Mar 7, 2018
Updated
Jul 8, 2026
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Sep 21, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
6.0%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs93th percentile — riskier than 93% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

CVE-2017-12174 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

2 pkgs affected
org.hornetq:hornetq-serverorg.apache.activemq:artemis-native

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

It 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.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.hornetq:hornetq-serverall versions2.4.0.Finalorg.hornetq:hornetq-server:2.4.0.Final
Mavenorg.apache.activemq:artemis-nativeall versions2.4.0org.apache.activemq:artemis-native:2.4.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.hornetq:hornetq-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.hornetq:hornetq-server to 2.4.0.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-12174 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2017-12174 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2017-12174. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant
ProductFixed inAdvisory
Red Hat JBoss EAP 7apache-artemisRHSA-2018:0478
Red Hat JBoss Enterprise Application Platform 6.4hornetqRHSA-2018:0269
Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 5hornetq-0:2.3.25-25.SP23_redhat_1.1.ep6.el5RHSA-2018:0271
Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6hornetq-0:2.3.25-25.SP23_redhat_1.1.ep6.el6RHSA-2018:0270
Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6jboss-ec2-eap-0:7.5.19-2.Final_redhat_2.ep6.el6RHSA-2018:0275
Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 7hornetq-0:2.3.25-25.SP23_redhat_1.1.ep6.el7RHSA-2018:0268
Red Hat JBoss Enterprise Application Platform 7.1 for RHEL 6eap7-activemq-artemis-0:1.5.5.009-1.redhat_1.1.ep7.el6RHSA-2018:0479
Red Hat JBoss Enterprise Application Platform 7.1 for RHEL 6eap7-jboss-ec2-eap-0:7.1.1-3.1.GA_redhat_3.ep7.el6RHSA-2018:0481

Frequently Asked Questions

It 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.
O3 Security · Impact-Aware SCA

Is CVE-2017-12174 in your dependencies?

O3 Security finds CVE-2017-12174 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

CVE-2017-12174: hornetq-server (High 7.5) | O3 Security