CVE-2024-32114
Vulnerability from cvelistv5
Published
2024-05-02 08:29
Modified
2024-08-02 02:06
Severity ?
EPSS score ?
Summary
Apache ActiveMQ: Jolokia and REST API were not secured with default configuration
References
Impacted products
▼ | Vendor | Product |
---|---|---|
Apache Software Foundation | Apache ActiveMQ |
{ "containers": { "adp": [ { "affected": [ { "cpes": [ "cpe:2.3:a:apache:activemq:-:*:*:*:*:*:*:*" ], "defaultStatus": "unknown", "product": "activemq", "vendor": "apache", "versions": [ { "status": "affected", "version": "6.x" } ] } ], "metrics": [ { "other": { "content": { "id": "CVE-2024-32114", "options": [ { "Exploitation": "none" }, { "Automatable": "no" }, { "Technical Impact": "total" } ], "role": "CISA Coordinator", "timestamp": "2024-05-02T17:11:27.204773Z", "version": "2.0.3" }, "type": "ssvc" } } ], "providerMetadata": { "dateUpdated": "2024-06-04T17:50:57.920Z", "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP" }, "title": "CISA ADP Vulnrichment" }, { "providerMetadata": { "dateUpdated": "2024-08-02T02:06:44.047Z", "orgId": "af854a3a-2127-422b-91ae-364da2661108", "shortName": "CVE" }, "references": [ { "tags": [ "vendor-advisory", "x_transferred" ], "url": "https://activemq.apache.org/security-advisories.data/CVE-2024-32114-announcement.txt" } ], "title": "CVE Program Container" } ], "cna": { "affected": [ { "defaultStatus": "unaffected", "product": "Apache ActiveMQ", "vendor": "Apache Software Foundation", "versions": [ { "lessThanOrEqual": "6.1.1", "status": "affected", "version": "6.0.0", "versionType": "semver" } ] } ], "credits": [ { "lang": "en", "type": "finder", "value": "Martin Zeissig" } ], "descriptions": [ { "lang": "en", "supportingMedia": [ { "base64": false, "type": "text/html", "value": "In Apache ActiveMQ 6.x, the default configuration doesn\u0027t secure the API web context (where the Jolokia JMX REST API and the Message REST API are located).\u003cbr\u003eIt 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).\u003cbr\u003e\u003cbr\u003eTo mitigate, users can update the default conf/jetty.xml configuration file to add authentication requirement:\u003cbr\u003e\u003cblockquote\u003e\u003cpre\u003e\u0026lt;bean id=\"securityConstraintMapping\" class=\"org.eclipse.jetty.security.ConstraintMapping\"\u0026gt;\n\u0026nbsp; \u0026lt;property name=\"constraint\" ref=\"securityConstraint\" /\u0026gt;\n\u0026nbsp; \u0026lt;property name=\"pathSpec\" value=\"/\" /\u0026gt;\n\u0026lt;/bean\u0026gt;\u003c/pre\u003e\u003c/blockquote\u003eOr we encourage users to upgrade to Apache ActiveMQ 6.1.2 where the default configuration has been updated with authentication by default.\u003cbr\u003e" } ], "value": "In Apache ActiveMQ 6.x, the default configuration doesn\u0027t secure the API web context (where the Jolokia JMX REST API and the Message REST API are located).\nIt 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).\n\nTo mitigate, users can update the default conf/jetty.xml configuration file to add authentication requirement:\n\u003cbean id=\"securityConstraintMapping\" class=\"org.eclipse.jetty.security.ConstraintMapping\"\u003e\n\u00a0 \u003cproperty name=\"constraint\" ref=\"securityConstraint\" /\u003e\n\u00a0 \u003cproperty name=\"pathSpec\" value=\"/\" /\u003e\n\u003c/bean\u003e\n\nOr we encourage users to upgrade to Apache ActiveMQ 6.1.2 where the default configuration has been updated with authentication by default.\n" } ], "metrics": [ { "other": { "content": { "text": "low" }, "type": "Textual description of severity" } }, { "cvssV3_1": { "attackComplexity": "LOW", "attackVector": "ADJACENT_NETWORK", "availabilityImpact": "HIGH", "baseScore": 8.5, "baseSeverity": "HIGH", "confidentialityImpact": "HIGH", "integrityImpact": "NONE", "privilegesRequired": "NONE", "scope": "CHANGED", "userInteraction": "REQUIRED", "vectorString": "CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:H", "version": "3.1" }, "format": "CVSS", "scenarios": [ { "lang": "en", "value": "GENERAL" } ] } ], "problemTypes": [ { "descriptions": [ { "cweId": "CWE-1188", "description": "CWE-1188 Insecure Default Initialization of Resource", "lang": "en", "type": "CWE" } ] } ], "providerMetadata": { "dateUpdated": "2024-05-02T08:29:18.219Z", "orgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09", "shortName": "apache" }, "references": [ { "tags": [ "vendor-advisory" ], "url": "https://activemq.apache.org/security-advisories.data/CVE-2024-32114-announcement.txt" } ], "source": { "defect": [ "AMQ-9477" ], "discovery": "EXTERNAL" }, "title": "Apache ActiveMQ: Jolokia and REST API were not secured with default configuration", "x_generator": { "engine": "Vulnogram 0.1.0-dev" } } }, "cveMetadata": { "assignerOrgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09", "assignerShortName": "apache", "cveId": "CVE-2024-32114", "datePublished": "2024-05-02T08:29:18.219Z", "dateReserved": "2024-04-11T08:12:15.896Z", "dateUpdated": "2024-08-02T02:06:44.047Z", "state": "PUBLISHED" }, "dataType": "CVE_RECORD", "dataVersion": "5.1", "meta": { "nvd": "{\"cve\":{\"id\":\"CVE-2024-32114\",\"sourceIdentifier\":\"security@apache.org\",\"published\":\"2024-05-02T09:15:06.990\",\"lastModified\":\"2024-05-02T13:27:25.103\",\"vulnStatus\":\"Awaiting Analysis\",\"descriptions\":[{\"lang\":\"en\",\"value\":\"In Apache ActiveMQ 6.x, the default configuration doesn\u0027t secure the API web context (where the Jolokia JMX REST API and the Message REST API are located).\\nIt 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).\\n\\nTo mitigate, users can update the default conf/jetty.xml configuration file to add authentication requirement:\\n\u003cbean id=\\\"securityConstraintMapping\\\" class=\\\"org.eclipse.jetty.security.ConstraintMapping\\\"\u003e\\n\u00a0 \u003cproperty name=\\\"constraint\\\" ref=\\\"securityConstraint\\\" /\u003e\\n\u00a0 \u003cproperty name=\\\"pathSpec\\\" value=\\\"/\\\" /\u003e\\n\u003c/bean\u003e\\n\\nOr we encourage users to upgrade to Apache ActiveMQ 6.1.2 where the default configuration has been updated with authentication by default.\\n\"},{\"lang\":\"es\",\"value\":\"En Apache ActiveMQ 6.x, la configuraci\u00f3n predeterminada no protege el contexto web de la API (donde se encuentran la API REST de Jolokia JMX y la API REST de mensajes). Significa que cualquiera puede utilizar estas capas sin necesidad de autenticaci\u00f3n. Potencialmente, cualquiera puede interactuar con el corredor (usando la API REST de Jolokia JMX) y/o producir/consumir mensajes o purgar/eliminar destinos (usando la API REST de mensajes). Para mitigar, los usuarios pueden actualizar el archivo de configuraci\u00f3n predeterminado conf/jetty.xml para agregar el requisito de autenticaci\u00f3n: O recomendamos a los usuarios que actualicen a Apache ActiveMQ 6.1.2, donde la configuraci\u00f3n predeterminada se actualiz\u00f3 con autenticaci\u00f3n de forma predeterminada.\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"security@apache.org\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:H\",\"attackVector\":\"ADJACENT_NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"REQUIRED\",\"scope\":\"CHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"HIGH\",\"baseScore\":8.5,\"baseSeverity\":\"HIGH\"},\"exploitabilityScore\":2.1,\"impactScore\":5.8}]},\"weaknesses\":[{\"source\":\"security@apache.org\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-1188\"}]}],\"references\":[{\"url\":\"https://activemq.apache.org/security-advisories.data/CVE-2024-32114-announcement.txt\",\"source\":\"security@apache.org\"}]}}" } }
Loading...
Loading...
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.