CVE-2024-41110
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMoby 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a regression vulnerability in Docker Engine where specially-crafted API requests cause the daemon to forward requests or responses to authorization plugins without the body content. AuthZ plugins that rely on inspecting request/response bodies to make access control decisions may incorrectly allow requests they would otherwise deny. The original fix was in v18.09.1 (January 2019) but was not carried forward to later major versions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Docker Engine versionRun `docker version --format '{{.Server.Version}}'` or `docker info --format '{{.ServerVersion}}'`Affected if Version is between 18.09.1 and 27.0.x inclusive (not fixed in 27.1.1 or later)
-
Identify enabled AuthZ pluginsRun `docker info` and look for Authorization Plugins in the output, or inspect the Docker daemon config file (usually /etc/docker/daemon.json) for the 'authorization-plugins' arrayAffected if One or more AuthZ plugins are listed as enabled
-
Verify plugin inspects request or response bodiesReview documentation or configuration of each enabled AuthZ plugin to determine if it makes access control decisions based on request body, response body, or bothAffected if Any enabled plugin relies on body content for allow/deny decisions
-
Check Docker API access controlReview network configuration (e.g.,iptables, dockerd --tcp flag, socket permissions) to determine who can send API requests to the Docker daemonAffected if The API is accessible to untrusted users or networks (e.g., exposed TCP socket, unrestricted Unix socket)
User is affected if running a Docker version between 18.09.1 and 27.0.x with an AuthZ plugin enabled that inspects request/response bodies for access control decisions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Docker Engine to v27.1.1 or later (or patched versions on branches 19.03, 20.0, 23.0, 24.0, 25.0, 26.0, 26.1). If immediate upgrade is not possible, disable AuthZ plugins and restrict access to the Docker API following least-privilege principles.
docker-ce v27.1.1 or later (or latest patch for branches 19.03, 20.0, 23.0, 24.0, 25.0, 26.0, 26.1)
- Identify the current Docker Engine version using `docker version`
- If running an affected version (pre-27.1.1 or unpatched branch), plan for upgrade
- For docker-ce users: upgrade to docker-ce v27.1.1 or later using your package manager (e.g., `apt-get update && apt-get upgrade docker-ce` or equivalent)
- For docker-ce on older branches (19.03, 20.0, 23.0, 24.0, 25.0, 26.0, 26.1): apply vendor patches from respective branch or upgrade to latest patch version in that branch
- Alternatively, if immediate upgrade is not possible: disable AuthZ plugins and restrict Docker API access to trusted parties only using firewall rules or authentication
- After upgrade, verify the Docker Engine version is 27.1.1 or later using `docker version`
- Test that authorization policies function correctly if you resume using AuthZ plugins
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-41110 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-41110 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data