Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2024-41110: Moby authz zero length regression

CriticalCVSS 9.9 · v3.1—Proof of concept Fix available

Noroxi assessment

Priority: Plan (action score 44/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 16.4% (FIRST EPSS); higher than 97% of all records.
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: azl3 moby-engine 25.0.3-13 on Azure Linux 3.0 25.0.3-5; azl3 moby-engine 25.0.3-5 on Azure Linux 3.0 25.0.3-5; cbl2 moby-engine 24.0.9-17 on CBL Mariner 2.0 24.0.9-7.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Add it to your regular patch cycle. Upgrade to azl3 moby-engine 25.0.3-13 on Azure Linux 3.0 25.0.3-5; azl3 moby-engine 25.0.3-5 on Azure Linux 3.0 25.0.3-5; cbl2 moby-engine 24.0.9-17 on CBL Mariner 2.0 24.0.9-7 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Jul 24, 2024
Updated
Jun 17, 2026
EPSS
16.4% · 97th percentile

Report tools

JSON

Action score

44

Plan

Add it to your regular patch cycle.

CVSS
39 / 40 · 9.9 / 10
CISA KEV
0 / 30 · Not listed
EPSS
5 / 30 · 16.4%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
10.0
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-41110

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for moby records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
dockermoby

Using moby? Add it to your stack and be the first to know about CVEs like this one. (Docker)

Watch new CVEs for moby

When you'll hear from us

  • when a new CVE affecting this product is published
  • when a record in your stack enters KEV or is weaponized

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every Monday

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • moby moby

    • >= 19.03.0, <= 19.03.15, >= 20.0.0, <= 20.10.27, >= 23.0.0, <= 23.0.14, >= 24.0.0, <= 24.0.9, >= 25.0.0, <= 25.0.5, >= 26.0.0, <= 26.0.2, >= 26.1.0, <= 26.1.14, >= 27.0.0, <= 27.0.3, = 27.1.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.20dockerbefore 26.1.5-r026.1.5-r0
Alpine:v3.21dockerbefore 27.1.1-r027.1.1-r0
Debian:11docker.iobefore 20.10.5+dfsg1-1+deb11u320.10.5+dfsg1-1+deb11u3
Debian:12docker.iobefore 20.10.24+dfsg1-1+deb12u120.10.24+dfsg1-1+deb12u1
Debian:13docker.iobefore 26.1.5+dfsg1-226.1.5+dfsg1-2
Gogithub.com/docker/dockerfrom 19.03.0 · before 23.0.1523.0.15
Gogithub.com/docker/dockerfrom 20.10.0+incompatible · before 25.0.6+incompatible25.0.6+incompatible
Gogithub.com/docker/dockerfrom 24.0.0 · before 25.0.625.0.6
Gogithub.com/docker/dockerfrom 26.0.0 · before 26.1.526.1.5
Gogithub.com/docker/dockerfrom 26.0.0+incompatible · before 26.1.5+incompatible26.1.5+incompatible
Gogithub.com/docker/dockerfrom 27.0.0 · before 27.1.127.1.1
Gogithub.com/docker/dockerfrom 27.0.0+incompatible · before 27.1.1+incompatible27.1.1+incompatible
Gogithub.com/moby/mobyfrom 20.10.0+incompatible · before 25.0.6+incompatible25.0.6+incompatible
Gogithub.com/moby/mobyfrom 26.0.0+incompatible · before 26.1.5+incompatible26.1.5+incompatible
Gogithub.com/moby/mobyfrom 27.0.0+incompatible · before 27.1.1+incompatible27.1.1+incompatible
openSUSE:Leap 15.5docker-stablebefore 24.0.9_ce-150000.1.5.124.0.9_ce-150000.1.5.1
openSUSE:Leap 15.5docker-stablebefore 24.0.9_ce-150000.1.8.124.0.9_ce-150000.1.8.1
openSUSE:Leap 15.6apptainerbefore 1.3.6-150600.4.9.11.3.6-150600.4.9.1
openSUSE:Leap 15.6dockerbefore 27.5.1_ce-150000.218.127.5.1_ce-150000.218.1
openSUSE:Leap 15.6docker-stablebefore 24.0.9_ce-150000.1.39.124.0.9_ce-150000.1.39.1
openSUSE:Leap 15.6docker-stablebefore 24.0.9_ce-150000.1.11.124.0.9_ce-150000.1.11.1
openSUSE:Leap 15.6docker-stablebefore 24.0.9_ce-150000.1.15.124.0.9_ce-150000.1.15.1
openSUSE:Leap Micro 5.5dockerbefore 25.0.6_ce-150000.207.125.0.6_ce-150000.207.1
openSUSE:Leap Micro 5.5dockerbefore 26.1.5_ce-150000.212.126.1.5_ce-150000.212.1

+23

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
azl3 moby-engine 25.0.3-13 on Azure Linux 3.025.0.3-5 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 moby-engine 25.0.3-5 on Azure Linux 3.025.0.3-5 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 moby-engine 24.0.9-17 on CBL Mariner 2.024.0.9-7 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 moby-engine 24.0.9-17 on CBL-Mariner 2.024.0.9-7 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 moby-engine 24.0.9-7 on CBL Mariner 2.024.0.9-7 · CBL-Mariner ReleasesMicrosoft (MSRC)
alpine:docker26.1.5-r0 · Alpine:v3.20Package registry (OSV)
debian:docker.io20.10.24+dfsg1-1+deb12u1 · Debian:12Package registry (OSV)
Go:github.com/docker/docker23.0.15Package registry (OSV)
Go:github.com/docker/docker25.0.6Package registry (OSV)
Go:github.com/docker/docker25.0.6+incompatiblePackage registry (OSV)
Go:github.com/docker/docker26.1.5Package registry (OSV)
Go:github.com/docker/docker26.1.5+incompatiblePackage registry (OSV)
Go:github.com/docker/docker27.1.1Package registry (OSV)
Go:github.com/docker/docker27.1.1+incompatiblePackage registry (OSV)
Go:github.com/moby/moby25.0.6+incompatiblePackage registry (OSV)
Go:github.com/moby/moby26.1.5+incompatiblePackage registry (OSV)
Go:github.com/moby/moby27.1.1+incompatiblePackage registry (OSV)
opensuse:apptainer1.3.6-150600.4.9.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:docker25.0.6_ce-150000.207.1 · openSUSE:Leap Micro 5.5Package registry (OSV)
opensuse:docker-stable24.0.9_ce-150000.1.8.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:nova3.10.0-1.1 · openSUSE:TumbleweedPackage registry (OSV)
suse:apptainer1.3.6-150600.4.9.1 · SUSE:Linux Enterprise Module for HPC 15 SP6Package registry (OSV)
suse:buildah1.35.4-150300.8.25.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSPackage registry (OSV)
suse:docker25.0.6_ce-150000.207.1 · SUSE:Linux Enterprise Micro 5.3Package registry (OSV)
suse:docker25.0.6_ce-98.115.1 · SUSE:Linux Enterprise Module for Containers 12Package registry (OSV)
suse:docker-stable24.0.9_ce-150000.1.8.1 · SUSE:Linux Enterprise Module for Containers 15 SP5Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×2

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:62024-07-25
Proof-of-concept repository on GitHubstars:02024-07-26

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoCsame day
  3. TodayNov 12, 2026+841 d

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-187 · Partial String Comparison

CVSS vector

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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

Show all references (13 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records