# CVE-2024-41110: Moby authz zero length regression > Attackers can bypass Docker authorization plugins by sending crafted API requests without bodies, potentially leading to unauthorized actions and privilege escalation. - **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 24 Jul 2024 - **Updated:** 13 Oct 2024 - **Also known as:** AZL-47017, AZL-47042, BELL-CVE-2024-41110, CLEANSTART-2026-OZ76094, CLEANSTART-2026-PX86725, CLEANSTART-2026-US13665, CLEANSTART-2026-XQ75557, DEBIAN-CVE-2024-41110, DLA-3918-1, GHSA-v23v-6jw2-98fq, GO-2024-3005, MINI-323p-75c5-m7rf, MINI-336v-2p5r-p25p, MINI-4mcv-mp2g-88h9, MINI-57r4-jvjg-7pp9, MINI-5gjc-pgj6-vr9j, MINI-5h44-rpq5-3fqr, MINI-7crc-8p2c-c26p, MINI-9f9c-f9w4-gv4c, MINI-9hrp-c429-rj9c, MINI-f48v-r9mx-8pfc, MINI-f7f2-q8qw-jh4q, MINI-fcw9-5xwh-5pmf, MINI-fmc7-8g6w-mq52, MINI-hcqv-2vj9-fc83, MINI-hqx4-67x3-99rm, MINI-hvpv-v287-472w, MINI-jcv9-fm5v-7pgj, MINI-pw36-qm67-c4vg, MINI-qh3v-536v-wc34, MINI-qq92-5cx3-6346, MINI-vf2h-7wc3-wgr9, MINI-vr82-hf5x-mv7m, MINI-vr8r-h5gg-6v8j, MINI-w2xc-mj53-cjh7, MINI-wp7p-wqmm-4v7j, OESA-2024-1959, OESA-2024-2074, SUSE-SU-2024:2709-1, SUSE-SU-2024:4204-1, SUSE-SU-2024:4205-1, UBUNTU-CVE-2024-41110, USN-7161-3, openSUSE-SU-2024:14229-1, openSUSE-SU-2024:14235-1, openSUSE-SU-2024:14446-1 ## What is CVE-2024-41110? CVE-2024-41110 is a critical authentication bypass vulnerability in moby, published on 24 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description 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. Using 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. A 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. Docker EE v19.03.x and all versions of Mirantis Container Runtime are not vulnerable. docker-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. Weakness: CWE-863 (Incorrect Authorization), CWE-444 (Inconsistent Interpretation of HTTP Requests), CWE-187 (Partial String Comparison) ## Which versions are affected by CVE-2024-41110? 10 open source packages ship an affected version, including github.com/moby/moby and github.com/docker/docker. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/moby/moby` | Go | From 20.10.0+incompatible | 25.0.6+incompatible, 26.1.5+incompatible, 27.1.1+incompatible | | `github.com/docker/docker` | Go | From 19.03.0 | 23.0.15 | | `github.com/docker/docker` | Go | From 19.03.0 | 23.0.15 | | `github.com/docker/docker` | Go | From 20.10.0+incompatible | 25.0.6+incompatible, 26.1.5+incompatible, 27.1.1+incompatible | | `github.com/docker/docker` | Go | From 24.0.0 | 25.0.6 | | `github.com/docker/docker` | Go | From 24.0.0 | 25.0.6 | | `github.com/docker/docker` | Go | From 26.0.0 | 26.1.5 | | `github.com/docker/docker` | Go | From 26.0.0 | 26.1.5 | | `github.com/docker/docker` | Go | From 27.0.0 | 27.1.1 | | `github.com/docker/docker` | Go | From 27.0.0 | 27.1.1 | | `docker-stable` | SUSE:Enterprise Storage 7.1 | All versions | 24.0.9_ce-150000.1.5.1 | | `docker-stable` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 24.0.9_ce-150000.1.5.1 | | `docker-stable` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 24.0.9_ce-150000.1.5.1 | | `docker-stable` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 24.0.9_ce-150000.1.5.1 | | `docker` | SUSE:Linux Enterprise Module for Containers 12 | All versions | 25.0.6_ce-98.115.1 | | `docker-stable` | SUSE:Linux Enterprise Module for Containers 15 SP5 | All versions | 24.0.9_ce-150000.1.5.1 | | `docker-stable` | SUSE:Linux Enterprise Module for Containers 15 SP6 | All versions | 24.0.9_ce-150000.1.5.1 | | `docker-stable` | SUSE:Linux Enterprise Server 12 SP5-LTSS | All versions | 24.0.9_ce-1.5.1 | | `docker-stable` | SUSE:Linux Enterprise Server 15 SP3-LTSS | All versions | 24.0.9_ce-150000.1.5.1 | | `docker-stable` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 24.0.9_ce-150000.1.5.1 | | `docker-stable` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 24.0.9_ce-1.5.1 | | `docker-stable` | SUSE:Linux Enterprise Server for SAP Applications 15 SP3 | All versions | 24.0.9_ce-150000.1.5.1 | | `docker-stable` | SUSE:Linux Enterprise Server for SAP Applications 15 SP4 | All versions | 24.0.9_ce-150000.1.5.1 | | `docker-stable` | openSUSE:Leap 15.5 | All versions | 24.0.9_ce-150000.1.5.1 | | `docker-stable` | openSUSE:Leap 15.6 | All versions | 24.0.9_ce-150000.1.5.1 | | `docker` | openSUSE:Tumbleweed | All versions | 26.1.5_ce-1.1 | | `docker-stable` | openSUSE:Tumbleweed | All versions | 24.0.9_ce-1.1 | | `nova` | openSUSE:Tumbleweed | All versions | 3.10.0-1.1 | ## How do I fix CVE-2024-41110? Upgrade github.com/moby/moby to a fixed version for your release line: 25.0.6+incompatible, 26.1.5+incompatible or 27.1.1+incompatible. ## Is CVE-2024-41110 being exploited? There is no known exploitation of CVE-2024-41110 in the wild and no public exploit code. Public exploit code: - https://github.com/vvpoglazov/cve-2024-41110-checker (github_poc): https://github.com/vvpoglazov/cve-2024-41110-checker - https://github.com/PauloParoPP/CVE-2024-41110-SCAN (github_poc): https://github.com/PauloParoPP/CVE-2024-41110-SCAN ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-41110 and fix it if it is affected. What it is: CVE-2024-41110 is a critical authentication bypass vulnerability in moby, published on 24 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-41110 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/moby/moby (Go): affected from 20.10.0+incompatible; fixed in 25.0.6+incompatible, 26.1.5+incompatible, 27.1.1+incompatible - github.com/docker/docker (Go): affected from 19.03.0; fixed in 23.0.15 - github.com/docker/docker (Go): affected from 19.03.0; fixed in 23.0.15 - github.com/docker/docker (Go): affected from 20.10.0+incompatible; fixed in 25.0.6+incompatible, 26.1.5+incompatible, 27.1.1+incompatible - github.com/docker/docker (Go): affected from 24.0.0; fixed in 25.0.6 - github.com/docker/docker (Go): affected from 24.0.0; fixed in 25.0.6 - github.com/docker/docker (Go): affected from 26.0.0; fixed in 26.1.5 - github.com/docker/docker (Go): affected from 26.0.0; fixed in 26.1.5 - github.com/docker/docker (Go): affected from 27.0.0; fixed in 27.1.1 - github.com/docker/docker (Go): affected from 27.0.0; fixed in 27.1.1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-41110/ (Markdown: https://insights.sbomify.com/CVE-2024-41110/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-41110 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-41110 - OSV: https://osv.dev/vulnerability/CVE-2024-41110 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-41110/ Summaries are generated and may contain mistakes; the official description above is the record.