cve-2024-51988
Vulnerability from cvelistv5
Published
2024-11-06 19:15
Modified
2024-11-06 19:53
Severity ?
EPSS score ?
Summary
HTTP API's queue deletion endpoint does not verify that the user has a required permission
References
Impacted products
▼ | Vendor | Product |
---|---|---|
rabbitmq | rabbitmq-server |
{ "containers": { "adp": [ { "metrics": [ { "other": { "content": { "id": "CVE-2024-51988", "options": [ { "Exploitation": "none" }, { "Automatable": "no" }, { "Technical Impact": "partial" } ], "role": "CISA Coordinator", "timestamp": "2024-11-06T19:53:13.523222Z", "version": "2.0.3" }, "type": "ssvc" } } ], "providerMetadata": { "dateUpdated": "2024-11-06T19:53:22.685Z", "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP" }, "title": "CISA ADP Vulnrichment" } ], "cna": { "affected": [ { "product": "rabbitmq-server", "vendor": "rabbitmq", "versions": [ { "status": "affected", "version": "Open source RabbitMQ: \u003e= 3.12.7, \u003c 3.12.11" }, { "status": "affected", "version": "Tanzu RabbitMQ: \u003e= 2.0.0, \u003c 3.13.0" }, { "status": "affected", "version": "Tanzu RabbitMQ: \u003c 1.5.2" } ] } ], "descriptions": [ { "lang": "en", "value": "RabbitMQ is a feature rich, multi-protocol messaging and streaming broker. In affected versions queue deletion via the HTTP API was not verifying the `configure` permission of the user. Users who had all of the following: 1. Valid credentials, 2. Some permissions for the target virtual host \u0026 3. HTTP API access. could delete queues it had no (deletion) permissions for. This issue has been addressed in version 3.12.11 of the open source rabbitMQ release and in versions 1.5.2, 3.13.0, and 4.0.0 of the tanzu release. Users are advised to upgrade. Users unable to upgrade may disable management plugin and use, for example, Prometheus and Grafana for monitoring." } ], "metrics": [ { "cvssV3_1": { "attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 6.5, "baseSeverity": "MEDIUM", "confidentialityImpact": "NONE", "integrityImpact": "HIGH", "privilegesRequired": "LOW", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N", "version": "3.1" } } ], "problemTypes": [ { "descriptions": [ { "cweId": "CWE-284", "description": "CWE-284: Improper Access Control", "lang": "en", "type": "CWE" } ] } ], "providerMetadata": { "dateUpdated": "2024-11-06T19:15:17.391Z", "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "shortName": "GitHub_M" }, "references": [ { "name": "https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-pj33-75x5-32j4", "tags": [ "x_refsource_CONFIRM" ], "url": "https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-pj33-75x5-32j4" }, { "name": "https://www.rabbitmq.com/docs/prometheus", "tags": [ "x_refsource_MISC" ], "url": "https://www.rabbitmq.com/docs/prometheus" } ], "source": { "advisory": "GHSA-pj33-75x5-32j4", "discovery": "UNKNOWN" }, "title": "HTTP API\u0027s queue deletion endpoint does not verify that the user has a required permission" } }, "cveMetadata": { "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "assignerShortName": "GitHub_M", "cveId": "CVE-2024-51988", "datePublished": "2024-11-06T19:15:17.391Z", "dateReserved": "2024-11-04T17:46:16.775Z", "dateUpdated": "2024-11-06T19:53:22.685Z", "state": "PUBLISHED" }, "dataType": "CVE_RECORD", "dataVersion": "5.1", "meta": { "nvd": "{\"cve\":{\"id\":\"CVE-2024-51988\",\"sourceIdentifier\":\"security-advisories@github.com\",\"published\":\"2024-11-06T20:15:06.513\",\"lastModified\":\"2024-11-08T19:01:25.633\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"RabbitMQ is a feature rich, multi-protocol messaging and streaming broker. In affected versions queue deletion via the HTTP API was not verifying the `configure` permission of the user. Users who had all of the following: 1. Valid credentials, 2. Some permissions for the target virtual host \u0026 3. HTTP API access. could delete queues it had no (deletion) permissions for. This issue has been addressed in version 3.12.11 of the open source rabbitMQ release and in versions 1.5.2, 3.13.0, and 4.0.0 of the tanzu release. Users are advised to upgrade. Users unable to upgrade may disable management plugin and use, for example, Prometheus and Grafana for monitoring.\"},{\"lang\":\"es\",\"value\":\"RabbitMQ es un agente de mensajer\u00eda y transmisi\u00f3n de m\u00faltiples protocolos con numerosas funciones. En las versiones afectadas, la eliminaci\u00f3n de colas a trav\u00e9s de la API HTTP no verificaba el permiso `configure` del usuario. Los usuarios que ten\u00edan todo lo siguiente: 1. Credenciales v\u00e1lidas, 2. Algunos permisos para el host virtual de destino y 3. Acceso a la API HTTP pod\u00edan eliminar colas para las que no ten\u00edan permisos (de eliminaci\u00f3n). Este problema se ha solucionado en la versi\u00f3n 3.12.11 de la versi\u00f3n de c\u00f3digo abierto rabbitMQ y en las versiones 1.5.2, 3.13.0 y 4.0.0 de la versi\u00f3n tanzu. Se recomienda a los usuarios que actualicen. Los usuarios que no puedan actualizar pueden deshabilitar el complemento de administraci\u00f3n y usar, por ejemplo, Prometheus y Grafana para la supervisi\u00f3n.\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"NONE\",\"baseScore\":6.5,\"baseSeverity\":\"MEDIUM\"},\"exploitabilityScore\":2.8,\"impactScore\":3.6}]},\"weaknesses\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-284\"}]}],\"references\":[{\"url\":\"https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-pj33-75x5-32j4\",\"source\":\"security-advisories@github.com\"},{\"url\":\"https://www.rabbitmq.com/docs/prometheus\",\"source\":\"security-advisories@github.com\"}]}}" } }
Loading...
Loading...
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- 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.