VDB

CVE-2024-41110

CVE-2024-41110 PUBLISHED CVSS 10 CRITICAL

Moby authz zero length regression

Reported by github_m · Published July 24, 2024

github.com/docker/docker is fixed in 27.1.1, 26.1.5, 25.0.6 and 1 more (Go Modules)

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.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
github.com/docker/dockerGo Modules27.1.1, 26.1.5, 25.0.6, 23.0.15
kyverno-fips-1.11Chainguard1.11.5-r21
policy-controllerChainguard0.9.0-r7
cadvisorWolfi0.50.0-r0
falcoctlChainguard0.8.0-r5
ctopWolfi0.7.7-r17
harbor-scanner-trivyWolfi0.31.3-r3
helmChainguard3.15.3-r1
filebeatChainguard8.15.0-r0
wolfictlChainguard0.21.0-r1
aactlChainguard0.4.12-r16
loki-3Chainguard3.1.0-r1

44 more packages have a fixed version. See every fix in Lookup.

Risk scores

CVSS 3.1
10
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Affected products

VendorProductVersions
mobymoby>= 19.03.0, <= 19.03.15, >= 20.0.0, <= 20.10.27, >= 23.0.0, <= 23.0.14
chainguardkyverno-fips-1.110
chainguardpolicy-controller0
wolficadvisor0
chainguardfalcoctl0
wolfictop0
wolfiharbor-scanner-trivy0
chainguardhelm0
chainguardfilebeat0
chainguardwolfictl0
chainguardaactl0
chainguardloki-30
github.comdocker/docker27.0.0, 19.03.0, 26.0.0
chainguardcert-manager-cmctl-fips0
chainguardgitlab-rails-ee-fips-17.30
chainguarddocker0
chainguardbom0
wolficilium-cli0
chainguardcosign-fips0
chainguardrancher-agent-2.11*

…and 265 more

Timeline

  • Jul 23, 2024 CVE Published
  • Jul 25, 2024 EPSS Score (30 in total, the first dated here)
  • Oct 4, 2024 Coalition ESS Score (11 in total, the first dated here)
  • Jan 7, 2026 Security Advisory (14 in total, the first dated here)
  • Aug 10, 2026 Distribution Patch (7 in total, the first dated here)

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2024-41110
vulnetix vdb fixes CVE-2024-41110

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2024-41110/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›