CVE-2024-32114
highPriorität · beachten · 48OT-Risiko · hochEPSS 0.071 · 94. PerzentilExploit · PoCDEEUNLRUUSEPSS · bewertet 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
Technischer Schweregrad, 0–10. Eine Zeile je Quelle.
Basiswert 0–10 · höher = schwerwiegender · Vektor überfahren zum Auflösen
SSVC
Eine Handlungsentscheidung — aus Ausnutzung und Auswirkung.
schwächen
Die CWE-Schwächeklassen, zu denen dies gehört.
Exploits (1)
Öffentlicher Proof-of-Concept- und Exploit-Code.
betroffene Produkte (93)
Betroffene Produkte und Versionsbereiche.
- Oracle Financial Services Applications 14.4.0.0.0alle Versionencert_bundDEcpe:/a:oracle:financial_services_applications:14.4.0.0.0
- Oracle Financial Services Applications 14.5.0.0.0alle Versionencert_bundDEcpe:/a:oracle:financial_services_applications:14.5.0.0.0
- Oracle Financial Services Applications 14.5.0.12.0alle Versionencert_bundDEcpe:/a:oracle:financial_services_applications:14.5.0.12.0
- Oracle Financial Services Applications 14.6.0.0.0alle Versionencert_bundDEcpe:/a:oracle:financial_services_applications:14.6.0.0.0
- Oracle Financial Services Applications 14.7.0.0.0alle Versionencert_bundDEcpe:/a:oracle:financial_services_applications:14.7.0.0.0
- Oracle Financial Services Applications 14.7.0.6.0alle Versionencert_bundDEcpe:/a:oracle:financial_services_applications:14.7.0.6.0
- Oracle Financial Services Applications 14.7.4.0.0alle Versionencert_bundDEcpe:/a:oracle:financial_services_applications:14.7.4.0.0
- Oracle Financial Services Applications 14.7.5.0.0alle Versionencert_bundDEcpe:/a:oracle:financial_services_applications:14.7.5.0.0
- Oracle Financial Services Applications 19.2.0.0.0alle Versionencert_bundDEcpe:/a:oracle:financial_services_applications:19.2.0.0.0
- Oracle Financial Services Applications 21.1.0.0.0alle Versionencert_bundDEcpe:/a:oracle:financial_services_applications:21.1.0.0.0
- Oracle Financial Services Applications 22.1.0.0.0alle Versionencert_bundDEcpe:/a:oracle:financial_services_applications:22.1.0.0.0
- Oracle Financial Services Applications 22.2.0.0.0alle Versionencert_bundDEcpe:/a:oracle:financial_services_applications:22.2.0.0.0
- Oracle Financial Services Applications 3.0.0.0.0alle Versionencert_bundDEcpe:/a:oracle:financial_services_applications:3.0.0.0.0
- Oracle Financial Services Applications 4.0.0.0.0alle Versionencert_bundDEcpe:/a:oracle:financial_services_applications:4.0.0.0.0
- Oracle Financial Services Applications 5.0.0.0.0alle Versionencert_bundDEcpe:/a:oracle:financial_services_applications:5.0.0.0.0
- Oracle Financial Services Applications 8.1.2.7alle Versionencert_bundDEcpe:/a:oracle:financial_services_applications:8.1.2.7
- Oracle Financial Services Applications 8.1.2.8alle Versionencert_bundDEcpe:/a:oracle:financial_services_applications:8.1.2.8
Advisories (7)
Hersteller- und Ökosystem-Meldungen dazu.
- 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.
auch bekannt als (6)
Weitere Namen und Kennungen dieser Entität.
quellen
Welche Quellen diesen Datensatz belegen und wann.
Referenzen (6)
Externe Belege — Patches, Meldungen, Analysen.
- 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
Angreifer nutzen Schwachstellen wie diese gegen im Internet exponierte Dienste aus. Sehen Sie mit einem kostenlosen Passiv-Scan, was exponiert ist.
Kostenloser Scan