# CVE-2024-51127: hornetq vulnerable to file overwrite, sensitive information disclosure > Attackers can exploit a path traversal flaw in HornetQ to overwrite arbitrary files or access sensitive information. - **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 4 Nov 2024 - **Updated:** 5 Jul 2026 - **Also known as:** GHSA-r7mv-mv7m-pjw3, RHSA-2024:11529, RHSA-2025:0371, RHSA-2025:1636, RHSA-2025:1637, RHSA-2025:1638 ## What is CVE-2024-51127? CVE-2024-51127 is a critical path traversal vulnerability in n/a, published on 4 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description An issue in the createTempFile method of hornetq v2.4.9 allows attackers to arbitrarily overwrite files or access sensitive information. Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2024-51127? 2 open source packages ship an affected version, including org.hornetq:hornetq-core-client. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.hornetq:hornetq-core-client` | Maven | All versions to 2.4.9 | None | | `org.hornetq:hornetq-core-client` | Maven | All versions to 2.4.9 | None | | `eap7-hal-console` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:3.3.25-1.Final_redhat_00001.1.el7eap | | `eap7-hibernate` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:5.3.37-1.Final_redhat_00001.1.el7eap | | `eap7-hibernate-core` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:5.3.37-1.Final_redhat_00001.1.el7eap | | `eap7-hibernate-entitymanager` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:5.3.37-1.Final_redhat_00001.1.el7eap | | `eap7-hibernate-envers` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:5.3.37-1.Final_redhat_00001.1.el7eap | | `eap7-hibernate-java8` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:5.3.37-1.Final_redhat_00001.1.el7eap | | `eap7-hornetq` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:2.4.11-1.Final_redhat_00001.1.el7eap | | `eap7-hornetq-commons` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:2.4.11-1.Final_redhat_00001.1.el7eap | | `eap7-hornetq-core-client` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:2.4.11-1.Final_redhat_00001.1.el7eap | | `eap7-hornetq-jms-client` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:2.4.11-1.Final_redhat_00001.1.el7eap | | `eap7-jbossws-common` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:3.4.0-1.Final_redhat_00001.1.el7eap | | `eap7-jbossws-cxf` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:5.4.14-1.Final_redhat_00001.1.el7eap | | `eap7-opensaml` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:3.4.6-1.redhat_00001.1.el7eap | | `eap7-opensaml-core` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:3.4.6-1.redhat_00001.1.el7eap | | `eap7-opensaml-profile-api` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:3.4.6-1.redhat_00001.1.el7eap | | `eap7-opensaml-saml-api` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:3.4.6-1.redhat_00001.1.el7eap | | `eap7-opensaml-saml-impl` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:3.4.6-1.redhat_00001.1.el7eap | | `eap7-opensaml-security-api` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:3.4.6-1.redhat_00001.1.el7eap | | `eap7-opensaml-security-impl` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:3.4.6-1.redhat_00001.1.el7eap | | `eap7-opensaml-soap-api` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:3.4.6-1.redhat_00001.1.el7eap | | `eap7-opensaml-xacml-api` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:3.4.6-1.redhat_00001.1.el7eap | | `eap7-opensaml-xacml-impl` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:3.4.6-1.redhat_00001.1.el7eap | | `eap7-opensaml-xacml-saml-api` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:3.4.6-1.redhat_00001.1.el7eap | | `eap7-opensaml-xacml-saml-impl` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:3.4.6-1.redhat_00001.1.el7eap | | `eap7-opensaml-xmlsec-api` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:3.4.6-1.redhat_00001.1.el7eap | | `eap7-opensaml-xmlsec-impl` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:3.4.6-1.redhat_00001.1.el7eap | | `eap7-wildfly` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:7.4.21-2.GA_redhat_00001.1.el7eap | | `eap7-wildfly-java-jdk11` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:7.4.21-2.GA_redhat_00001.1.el7eap | | `eap7-wildfly-java-jdk8` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:7.4.21-2.GA_redhat_00001.1.el7eap | | `eap7-wildfly-javadocs` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:7.4.21-2.GA_redhat_00001.1.el7eap | | `eap7-wildfly-modules` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:7.4.21-2.GA_redhat_00001.1.el7eap | | `eap7-xml-security` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:2.3.5-1.redhat_00001.1.el7eap | | `eap7-hal-console` | Red Hat:jboss_enterprise_application_platform:7.4::el8 | All versions | 0:3.3.25-1.Final_redhat_00001.1.el8eap | | `eap7-hibernate` | Red Hat:jboss_enterprise_application_platform:7.4::el8 | All versions | 0:5.3.37-1.Final_redhat_00001.1.el8eap | | `eap7-hibernate-core` | Red Hat:jboss_enterprise_application_platform:7.4::el8 | All versions | 0:5.3.37-1.Final_redhat_00001.1.el8eap | | `eap7-hibernate-entitymanager` | Red Hat:jboss_enterprise_application_platform:7.4::el8 | All versions | 0:5.3.37-1.Final_redhat_00001.1.el8eap | | `eap7-hibernate-envers` | Red Hat:jboss_enterprise_application_platform:7.4::el8 | All versions | 0:5.3.37-1.Final_redhat_00001.1.el8eap | | `eap7-hibernate-java8` | Red Hat:jboss_enterprise_application_platform:7.4::el8 | All versions | 0:5.3.37-1.Final_redhat_00001.1.el8eap | Products: Redhat Hornetq. ## How do I fix CVE-2024-51127? Apply the vendor's patch. ## Is CVE-2024-51127 being exploited? There is no known exploitation of CVE-2024-51127 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [CVE-2014-3599](https://insights.sbomify.com/CVE-2014-3599/): HornetQ REST vulnerable to Improper Restriction of XML External Entity Reference (medium 6.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-51127 and fix it if it is affected. What it is: CVE-2024-51127 is a critical path traversal vulnerability in n/a, published on 4 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-51127 in the wild and no public exploit code. Affected packages and fixed versions: - org.hornetq:hornetq-core-client (Maven): affected all versions up to 2.4.9; no fix listed - org.hornetq:hornetq-core-client (Maven): affected all versions up to 2.4.9; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-51127/ (Markdown: https://insights.sbomify.com/CVE-2024-51127/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-51127 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-51127 - OSV: https://osv.dev/vulnerability/CVE-2024-51127 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-51127/ Summaries are generated and may contain mistakes; the official description above is the record.