CVE-2024-32114
highpriority · attend · 48OT risk · highEPSS 0.071 · 94 %ileexploit · PoCDEEUNLRUUSEPSS · scored 2026-10-26
In Apache ActiveMQ 6.x, the default configuration doesn't secure the API web context (where the Jolokia JMX REST API and the Message REST API are located). It means that anyone can use these layers without any required authentication. Potentially, anyone can interact with the broker (using Jolokia JMX REST API) and/or produce/consume messages or purge/delete destinations (using the Message REST API). To mitigate, users can update the default conf/jetty.xml configuration file to add authentication requirement: <bean id="securityConstraintMapping" class="org.eclipse.jetty.security.ConstraintMapping"> <property name="constraint" ref="securityConstraint" /> <property name="pathSpec" value="/" /> </bean> Or we encourage users to upgrade to Apache ActiveMQ 6.1.2 where the default configuration has been updated with authentication by default.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
exploits (1)
Public proof-of-concept and weaponised exploit code.
affected products (93)
Products and version ranges known to be affected.
- Oracle Financial Services Applications 14.4.0.0.0all versionscert_bundDEcpe:/a:oracle:financial_services_applications:14.4.0.0.0
- Oracle Financial Services Applications 14.5.0.0.0all versionscert_bundDEcpe:/a:oracle:financial_services_applications:14.5.0.0.0
- Oracle Financial Services Applications 14.5.0.12.0all versionscert_bundDEcpe:/a:oracle:financial_services_applications:14.5.0.12.0
- Oracle Financial Services Applications 14.6.0.0.0all versionscert_bundDEcpe:/a:oracle:financial_services_applications:14.6.0.0.0
- Oracle Financial Services Applications 14.7.0.0.0all versionscert_bundDEcpe:/a:oracle:financial_services_applications:14.7.0.0.0
- Oracle Financial Services Applications 14.7.0.6.0all versionscert_bundDEcpe:/a:oracle:financial_services_applications:14.7.0.6.0
- Oracle Financial Services Applications 14.7.4.0.0all versionscert_bundDEcpe:/a:oracle:financial_services_applications:14.7.4.0.0
- Oracle Financial Services Applications 14.7.5.0.0all versionscert_bundDEcpe:/a:oracle:financial_services_applications:14.7.5.0.0
- Oracle Financial Services Applications 19.2.0.0.0all versionscert_bundDEcpe:/a:oracle:financial_services_applications:19.2.0.0.0
- Oracle Financial Services Applications 21.1.0.0.0all versionscert_bundDEcpe:/a:oracle:financial_services_applications:21.1.0.0.0
- Oracle Financial Services Applications 22.1.0.0.0all versionscert_bundDEcpe:/a:oracle:financial_services_applications:22.1.0.0.0
- Oracle Financial Services Applications 22.2.0.0.0all versionscert_bundDEcpe:/a:oracle:financial_services_applications:22.2.0.0.0
- Oracle Financial Services Applications 3.0.0.0.0all versionscert_bundDEcpe:/a:oracle:financial_services_applications:3.0.0.0.0
- Oracle Financial Services Applications 4.0.0.0.0all versionscert_bundDEcpe:/a:oracle:financial_services_applications:4.0.0.0.0
- Oracle Financial Services Applications 5.0.0.0.0all versionscert_bundDEcpe:/a:oracle:financial_services_applications:5.0.0.0.0
- Oracle Financial Services Applications 8.1.2.7all versionscert_bundDEcpe:/a:oracle:financial_services_applications:8.1.2.7
- Oracle Financial Services Applications 8.1.2.8all versionscert_bundDEcpe:/a:oracle:financial_services_applications:8.1.2.8
advisories (7)
Vendor and ecosystem advisories describing this.
- NCSC-2024-0297 Kwetsbaarheden verholpen in Oracle Financial Services ApplicationsNL2024-07-17csaf · ncsc_nlNL
Er zijn kwetsbaarheden verholpen in Oracle Financial Services Applications.
- NCSC-2024-0416Kwetsbaarheden verholpen in Oracle Financial Services ApplicationsNL2024-10-17csaf · ncsc_nlNL
Oracle heeft kwetsbaarheden verholpen in Financial Services Applications.
- WID-SEC-W-2024-1010Apache ActiveMQ: Schwachstelle ermöglicht Umgehen von SicherheitsvorkehrungenDeutsch2024-05-01csaf · cert_bundDE
Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Apache ActiveMQ ausnutzen, um Sicherheitsvorkehrungen zu umgehen.
- WID-SEC-W-2024-1638Oracle Financial Services Applications: Mehrere SchwachstellenDeutsch2024-07-16csaf · cert_bundDE
Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Financial Services Applications ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.
- WID-SEC-W-2024-3192Oracle Financial Services Applications: Mehrere SchwachstellenDeutsch2024-10-15csaf · cert_bundDE
Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Financial Services Applications ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.
- GHSA-gj5m-m88j-v7c3Apache ActiveMQ's default configuration doesn't secure the API web context2024-05-02ghsa · osvUS
In Apache ActiveMQ 6.x, the default configuration doesn't secure the API web context (where the Jolokia JMX REST API and the Message REST API are located). It means that anyone can use these layers without any required authentication. Potentially, anyone can interact with the broker (using Jolokia JMX REST API) and/or produce/consume messages or purge/delete destinations (using the Message REST API). To mitigate, users can update the default conf/jetty.xml configuration file to add authentication requirement: <bean id="securityConstraintMapping" class="org.eclipse.jetty.security.ConstraintMapping"> <property name="constraint" ref="securityConstraint" /> <property name="pathSpec" value="/" /> </bean> Or we encourage users to upgrade to Apache ActiveMQ 6.1.2 where the default configuration has been updated with authentication by default.
- BIT-activemq-2024-321142024-05-04vendor · osvUS
In Apache ActiveMQ 6.x, the default configuration doesn't secure the API web context (where the Jolokia JMX REST API and the Message REST API are located).It means that anyone can use these layers without any required authentication. Potentially, anyone can interact with the broker (using Jolokia JMX REST API) and/or produce/consume messages or purge/delete destinations (using the Message REST API).To mitigate, users can update the default conf/jetty.xml configuration file to add authentication requirement:<bean id="securityConstraintMapping" class="org.eclipse.jetty.security.ConstraintMapping"> <property name="constraint" ref="securityConstraint" /> <property name="pathSpec" value="/" /></bean>Or we encourage users to upgrade to Apache ActiveMQ 6.1.2 where the default configuration has been updated with authentication by default.
also known as (6)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (6)
External citations — patches, advisories, analysis.
- https://activemq.apache.org/security-advisories.data/CVE-2024-32114-announcement.txtcnnvd
- https://cxsecurity.com/cveshow/CVE-2024-32114/cnnvd
- https://www.oracle.com/security-alerts/cpujul2024.htmlcnnvd
- https://www.oracle.com/security-alerts/cpuoct2024.htmlcnnvd
- https://activemq.apache.org/security-advisories.data/CVE-2024-32114-announcement.txtenisa_euvd
- https://activemq.apache.org/security-advisories.data/CVE-2024-32114-announcement.txtVendor Advisorynvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan