CVE-2024-41110

{"id": "CVE-2024-41110", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "CHANGED", "version": "3.1", "baseScore": 9.9, "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 6.0, "exploitabilityScore": 3.1}]}, "published": "2024-07-24T17:15:11.053", "references": [{"url": "https://github.com/moby/moby/commit/411e817ddf710ff8e08fa193da80cb78af708191", "source": "security-advisories@github.com"}, {"url": "https://github.com/moby/moby/commit/42f40b1d6dd7562342f832b9cd2adf9e668eeb76", "source": "security-advisories@github.com"}, {"url": "https://github.com/moby/moby/commit/65cc597cea28cdc25bea3b8a86384b4251872919", "source": "security-advisories@github.com"}, {"url": "https://github.com/moby/moby/commit/852759a7df454cbf88db4e954c919becd48faa9b", "source": "security-advisories@github.com"}, {"url": "https://github.com/moby/moby/commit/a31260625655cff9ae226b51757915e275e304b0", "source": "security-advisories@github.com"}, {"url": "https://github.com/moby/moby/commit/a79fabbfe84117696a19671f4aa88b82d0f64fc1", "source": "security-advisories@github.com"}, {"url": "https://github.com/moby/moby/commit/ae160b4edddb72ef4bd71f66b975a1a1cc434f00", "source": "security-advisories@github.com"}, {"url": "https://github.com/moby/moby/commit/ae2b3666c517c96cbc2adf1af5591a6b00d4ec0f", "source": "security-advisories@github.com"}, {"url": "https://github.com/moby/moby/commit/cc13f952511154a2866bddbb7dddebfe9e83b801", "source": "security-advisories@github.com"}, {"url": "https://github.com/moby/moby/commit/fc274cd2ff4cf3b48c91697fb327dd1fb95588fb", "source": "security-advisories@github.com"}, {"url": "https://github.com/moby/moby/security/advisories/GHSA-v23v-6jw2-98fq", "source": "security-advisories@github.com"}, {"url": "https://www.docker.com/blog/docker-security-advisory-docker-engine-authz-plugin", "source": "security-advisories@github.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-187"}, {"lang": "en", "value": "CWE-444"}, {"lang": "en", "value": "CWE-863"}]}], "descriptions": [{"lang": "en", "value": "Moby is an open-source project created by Docker for software containerization. A security vulnerability has been detected in certain versions of Docker Engine, which could allow an attacker to bypass authorization plugins (AuthZ) under specific circumstances. The base likelihood of this being exploited is low.\n\nUsing a specially-crafted API request, an Engine API client could make the daemon forward the request or response to an authorization plugin without the body. In certain circumstances, the authorization plugin may allow a request which it would have otherwise denied if the body had been forwarded to it.\n\nA security issue was discovered In 2018, where an attacker could bypass AuthZ plugins using a specially crafted API request. This could lead to unauthorized actions, including privilege escalation. Although this issue was fixed in Docker Engine v18.09.1 in January 2019, the fix was not carried forward to later major versions, resulting in a regression. Anyone who depends on authorization plugins that introspect the request and/or response body to make access control decisions is potentially impacted.\n\nDocker EE v19.03.x and all versions of Mirantis Container Runtime are not vulnerable.\n\ndocker-ce v27.1.1 containes patches to fix the vulnerability. Patches have also been merged into the master, 19.03, 20.0, 23.0, 24.0, 25.0, 26.0, and 26.1 release branches. If one is unable to upgrade immediately, avoid using AuthZ plugins and/or restrict access to the Docker API to trusted parties, following the principle of least privilege."}, {"lang": "es", "value": "Moby es un proyecto de c\u00f3digo abierto creado por Docker para la contenedorizaci\u00f3n de software. Se ha detectado una vulnerabilidad de seguridad en determinadas versiones de Docker Engine, que podr\u00eda permitir a un atacante omitir los complementos de autorizaci\u00f3n (AuthZ) en circunstancias espec\u00edficas. La probabilidad b\u00e1sica de que esto sea explotado es baja. Utilizando una solicitud de API especialmente manipulada, un cliente de Engine API podr\u00eda hacer que el daemon reenv\u00ede la solicitud o respuesta a un complemento de autorizaci\u00f3n sin el cuerpo. En determinadas circunstancias, el complemento de autorizaci\u00f3n puede permitir una solicitud que, de otro modo, habr\u00eda rechazado si se le hubiera enviado el organismo. En 2018 se descubri\u00f3 un problema de seguridad en el que un atacante pod\u00eda omitir los complementos de AuthZ mediante una solicitud API especialmente manipulada. Esto podr\u00eda dar lugar a acciones no autorizadas, incluida la escalada de privilegios. Aunque este problema se solucion\u00f3 en Docker Engine v18.09.1 en enero de 2019, la soluci\u00f3n no se traslad\u00f3 a versiones principales posteriores, lo que result\u00f3 en una regresi\u00f3n. Cualquiera que dependa de complementos de autorizaci\u00f3n que introspeccionen el cuerpo de solicitud y/o respuesta para tomar decisiones de control de acceso se ver\u00e1 potencialmente afectado. Docker EE v19.03.x y todas las versiones de Mirantis Container Runtime no son vulnerables. docker-ce v27.1.1 contiene parches para corregir la vulnerabilidad. Los parches tambi\u00e9n se han fusionado en las ramas de versi\u00f3n maestra, 19.0, 20.0, 23.0, 24.0, 25.0, 26.0 y 26.1. Si uno no puede actualizar inmediatamente, evite usar complementos de AuthZ y/o restrinja el acceso a la API de Docker a partes confiables, siguiendo el principio de privilegio m\u00ednimo."}], "lastModified": "2024-07-30T20:15:04.567", "sourceIdentifier": "security-advisories@github.com"}