Moby authz zero length regression
cve-program · CVE-2024-41110
PublishedMoby 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.
Read the publisher's advisoryeuvd · EUVD-2024-2415
PublishedMoby 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.
Read the publisher's advisorynvd · CVE-2024-41110
PublishedMoby 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.
Read the publisher's advisoryosv · GHSA-v23v-6jw2-98fq
PublishedA security vulnerability has been detected in certain versions of Docker Engine, which could allow an attacker to bypass [authorization plugins (AuthZ)](https://docs.docker.com/engine/extend/plugins_authorization/) under specific circumstances. The base likelihood of this being exploited is low. This advisory outlines the issue, identifies the affected versions, and provides remediation steps for impacted users. ### Impact Using a specially-crafted API request, an Engine API client could make the daemon forward the request or response to an [authorization plugin](https://docs.docker.com/engine/extend/plugins_authorization/) 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](https://docs.docker.com/engine/release-notes/18.09/#security-fixes-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.** ### Vulnerability details - **AuthZ bypass and privilege escalation:** An attacker could exploit a bypass using an API request with Content-Length set to 0, causing the Docker daemon to forward the request without the body to the AuthZ plugin, which might approve the request incorrectly. - **Initial fix:** The issue was fixed in Docker Engine [v18.09.1](https://docs.docker.com/engine/release-notes/18.09/#security-fixes-1) January 2019.. - **Regression:** The fix was not included in Docker Engine v19.03 or newer versions. This was identified in April 2024 and patches were released for the affected versions on July 23, 2024. The issue was assigned [CVE-2024-41110](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-41110). ### Patches - docker-ce v27.1.1 containes patches to fix the vulnerability. - Patches have also been merged into the master, 19.0, 20.0, 23.0, 24.0, 25.0, 26.0, and 26.1 release branches. ### Remediation steps - If you are running an affected version, update to the most recent patched version. - Mitigation if unable to update immediately: - Avoid using AuthZ plugins. - Restrict access to the Docker API to trusted parties, following the principle of least privilege. ### References - https://github.com/moby/moby/commit/fc274cd2ff4cf3b48c91697fb327dd1fb95588fb - https://github.com/moby/moby/commit/a79fabbfe84117696a19671f4aa88b82d0f64fc1 - https://www.docker.com/blog/docker-security-advisory-docker-engine-authz-plugin/
Read the publisher's advisoryosv · GO-2024-3005
PublishedMoby authz zero length regression in github.com/moby/moby
Read the publisher's advisoryAffected versions, risk and source history
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
cve-program · CVE-2024-41110
PublishedMoby authz zero length regression
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.
- Source published
- 24 Jul 2024 16:49:53 UTC
- Source modified
- 13 Oct 2024 21:03:34 UTC
- Saved here
- 23 Oct 2026 15:48:27 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · 10.0 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
euvd · EUVD-2024-2415
PublishedMoby 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 spe…
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.
Additional publisher context
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Jul 24, 2024, 4:49:53 PM
dateUpdated: Oct 13, 2024, 9:03:34 PM
30 related source bulletins · separate from aliases
SUSE-SU-2026:1118-1: Security update for docker-stable
CVE-2024-23650 · CVE-2024-29018 · CVE-2024-41110 · CVE-2025-22868 · CVE-2025-22869 · CVE-2025-30204 · CVE-2025-58181
SUSE-SU-2025:03540-1: Security update for docker-stable
CVE-2014-3499 · CVE-2014-5277 · CVE-2014-6407 · CVE-2014-6408 · CVE-2014-8178 · CVE-2014-8179 · CVE-2014-9356 · CVE-2014-9357 · CVE-2014-9358 · CVE-2015-3627 · CVE-2015-3629 · CVE-2015-3630 · CVE-2015-3631 · CVE-2016-3697 · CVE-2016-8867 · CVE-2016-9962 · CVE-2017-14992 · CVE-2017-16539 · CVE-2018-10892 · CVE-2018-15664 · CVE-2018-16873 · CVE-2018-16874 · CVE-2018-16875 · CVE-2018-20699 · CVE-2019-13509 · CVE-2019-14271 · CVE-2020-12912 · CVE-2020-13401 · CVE-2020-15257 · CVE-2020-8694 · CVE-2020-8695 · CVE-2021-21284 · CVE-2021-21285 · CVE-2021-41089 · CVE-2021-41091 · CVE-2021-41092 · CVE-2021-41103 · CVE-2021-41190 · CVE-2021-43565 · CVE-2022-24769 · CVE-2022-27191 · CVE-2022-36109 · CVE-2023-28840 · CVE-2023-28841 · CVE-2023-28842 · CVE-2024-23650 · CVE-2024-23651 · CVE-2024-23652 · CVE-2024-23653 · CVE-2024-29018 · CVE-2024-41110 · CVE-2025-22868 · CVE-2025-22869
WID-SEC-W-2025-0225: Dell PowerProtect Data Domain: Mehrere Schwachstellen
CVE-2013-4235 · CVE-2015-8100 · CVE-2017-9271 · CVE-2018-6798 · CVE-2018-6913 · CVE-2019-20633 · CVE-2019-20892 · CVE-2020-12762 · CVE-2020-15861 · CVE-2020-15862 · CVE-2021-3521 · CVE-2021-37750 · CVE-2021-46933 · CVE-2021-46955 · CVE-2021-47074 · CVE-2021-47113 · CVE-2021-47131 · CVE-2021-47162 · CVE-2021-47171 · CVE-2021-47188 · CVE-2021-47206 · CVE-2021-47220 · CVE-2021-47229 · CVE-2021-47231 · CVE-2021-47235 · CVE-2022-2601 · CVE-2022-3775 · CVE-2022-44792 · CVE-2022-44793 · CVE-2022-48566 · CVE-2023-27043 · CVE-2023-28074 · CVE-2023-3164 · CVE-2023-36632 · CVE-2023-4421 · CVE-2023-44487 · CVE-2023-45288 · CVE-2023-45733 · CVE-2023-45745 · CVE-2023-45918 · CVE-2023-46103 · CVE-2023-4692 · CVE-2023-47233 · CVE-2023-47855 · CVE-2023-49083 · CVE-2023-50782 · CVE-2023-52425 · CVE-2023-52426 · CVE-2023-52428 · CVE-2023-52527 · CVE-2023-52586 · CVE-2023-52591 · CVE-2023-52646 · CVE-2023-52653 · CVE-2023-52655 · CVE-2023-52664 · CVE-2023-52685 · CVE-2023-52686 · CVE-2023-52691 · CVE-2023-52696 · CVE-2023-52698 · CVE-2023-52703 · CVE-2023-52730 · CVE-2023-52732 · CVE-2023-52741 · CVE-2023-52742 · CVE-2023-52747 · CVE-2023-52759 · CVE-2023-52774 · CVE-2023-52781 · CVE-2023-52796 · CVE-2023-52803 · CVE-2023-52821 · CVE-2023-52864 · CVE-2023-52865 · CVE-2023-52867 · CVE-2023-52875 · CVE-2023-52880 · CVE-2023-5388 · CVE-2023-5752 · CVE-2023-5992 · CVE-2023-6597 · CVE-2024-0397 · CVE-2024-0450 · CVE-2024-0639 · CVE-2024-0727 · CVE-2024-1737 · CVE-2024-1975 · CVE-2024-2004 · CVE-2024-20696 · CVE-2024-22195 · CVE-2024-2398 · CVE-2024-24577 · CVE-2024-24790 · CVE-2024-2511 · CVE-2024-25710 · CVE-2024-26130 · CVE-2024-26458 · CVE-2024-26461 · CVE-2024-26625 · CVE-2024-26739 · CVE-2024-26752 · CVE-2024-26775 · CVE-2024-26791 · CVE-2024-26828 · CVE-2024-26846 · CVE-2024-26874 · CVE-2024-26876 · CVE-2024-26900 · CVE-2024-26915 · CVE-2024-26920 · CVE-2024-26921 · CVE-2024-26929 · CVE-2024-26930 · CVE-2024-26931 · CVE-2024-26934 · CVE-2024-26957 · CVE-2024-26958 · CVE-2024-26984 · CVE-2024-26996 · CVE-2024-27008 · CVE-2024-27054 · CVE-2024-27059 · CVE-2024-27062 · CVE-2024-27388 · CVE-2024-27396 · CVE-2024-27398 · CVE-2024-27401 · CVE-2024-27419 · CVE-2024-27436 · CVE-2024-28085 · CVE-2024-28182 · CVE-2024-2961 · CVE-2024-32487 · CVE-2024-33599 · CVE-2024-33600 · CVE-2024-33601 · CVE-2024-33602 · CVE-2024-33871 · CVE-2024-34062 · CVE-2024-34064 · CVE-2024-34459 · CVE-2024-35195 · CVE-2024-35235 · CVE-2024-35789 · CVE-2024-35791 · CVE-2024-35809 · CVE-2024-35811 · CVE-2024-35830 · CVE-2024-35849 · CVE-2024-35877 · CVE-2024-35878 · CVE-2024-35887 · CVE-2024-35895 · CVE-2024-35914 · CVE-2024-35932 · CVE-2024-35935 · CVE-2024-35936 · CVE-2024-35944 · CVE-2024-35955 · CVE-2024-35969 · CVE-2024-35982 · CVE-2024-36015 · CVE-2024-36029 · CVE-2024-3651 · CVE-2024-36954 · CVE-2024-37370 · CVE-2024-37371 · CVE-2024-37891 · CVE-2024-38428 · CVE-2024-39689 · CVE-2024-4032 · CVE-2024-41110 · CVE-2024-4317 · CVE-2024-4741 · CVE-2024-5206 · CVE-2024-5535 · CVE-2024-6232 · CVE-2024-6345 · CVE-2024-6655 · CVE-2024-7264 · CVE-2024-7592 · CVE-2024-53295 · CVE-2024-51534 · CVE-2024-53296
SUSE-SU-2024:3120-1: Security update for buildah, docker
CVE-2024-1753 · CVE-2024-23651 · CVE-2024-23652 · CVE-2024-23653 · CVE-2024-24786 · CVE-2024-28180 · CVE-2024-3727 · CVE-2024-41110
SUSE-SU-2024:2709-1: Security update for docker
CVE-2024-41110
SUSE-SU-2024:4204-1: Security update for docker-stable
CVE-2024-41110
openSUSE-SU-2024:14229-1: docker-26.1.5_ce-1.1 on GA media
CVE-2024-41110
WID-SEC-W-2024-1703: docker: Schwachstelle ermöglicht Privilegieneskalation
CVE-2024-41110
WID-SEC-W-2025-0001: IBM DB2: Mehrere Schwachstellen
CVE-2021-32740 · CVE-2021-41186 · CVE-2022-0759 · CVE-2022-24795 · CVE-2022-31163 · CVE-2023-39325 · CVE-2023-41993 · CVE-2023-45283 · CVE-2023-45288 · CVE-2023-6597 · CVE-2024-0406 · CVE-2024-20918 · CVE-2024-20952 · CVE-2024-2398 · CVE-2024-24786 · CVE-2024-27281 · CVE-2024-2961 · CVE-2024-29857 · CVE-2024-33599 · CVE-2024-33883 · CVE-2024-37370 · CVE-2024-37371 · CVE-2024-37890 · CVE-2024-39338 · CVE-2024-4068 · CVE-2024-41110 · CVE-2024-41123 · CVE-2024-41946 · CVE-2024-45296 · CVE-2024-45491 · CVE-2024-45590 · CVE-2024-47220 · CVE-2024-47554 · CVE-2024-6119 · CVE-2024-6345
SUSE-SU-2025:0980-1: Security update for apptainer
CVE-2024-41110 · CVE-2024-45337 · CVE-2024-45338 · CVE-2025-22869 · CVE-2025-22870 · CVE-2025-27144
NCSC-2024-0318: Kwetsbaarheden verholpen in Docker Moby
CVE-2024-41110
openSUSE-SU-2024:14235-1: nova-3.10.0-1.1 on GA media
CVE-2024-41110
msrc_CVE-2024-41110: Moby authz zero length regression
CVE-2024-41110
SUSE-SU-2025:20259-1: Security update for docker
CVE-2023-45142 · CVE-2023-47108 · CVE-2024-29018 · CVE-2024-41110
SUSE-SU-2026:0972-1: Security update for docker-stable
CVE-2024-23650 · CVE-2024-29018 · CVE-2024-41110 · CVE-2025-22868 · CVE-2025-22869 · CVE-2025-30204 · CVE-2025-58181
openSUSE-SU-2026:20730-1: Security update for apptainer
CVE-2023-45288 · CVE-2024-28180 · CVE-2024-3727 · CVE-2024-41110 · CVE-2024-45337 · CVE-2024-45338 · CVE-2025-22869 · CVE-2025-22870 · CVE-2025-22872 · CVE-2025-27144 · CVE-2025-47911 · CVE-2025-47913 · CVE-2025-47914 · CVE-2025-58181 · CVE-2025-58190 · CVE-2025-65105 · CVE-2025-8556 · CVE-2026-24137 · CVE-2026-33186 · CVE-2026-34986
SUSE-SU-2024:4360-1: Security update for docker
CVE-2023-45142 · CVE-2023-47108 · CVE-2024-41110
RHSA-2025:3714: Red Hat Security Advisory: cert-manager Operator for Red Hat OpenShift 1.14.2
CVE-2024-6104 · CVE-2024-41110
SUSE-SU-2025:0226-1: Security update for docker-stable
CVE-2024-23650 · CVE-2024-23653 · CVE-2024-29018 · CVE-2024-41110
openSUSE-SU-2025:14909-1: apptainer-1.3.6-5.1 on GA media
CVE-2024-41110 · CVE-2024-45337 · CVE-2024-45338 · CVE-2025-22869 · CVE-2025-22870 · CVE-2025-27144
SUSE-SU-2025:20110-1: Security update for docker
CVE-2023-45142 · CVE-2023-47108 · CVE-2024-41110
openSUSE-SU-2024:14446-1: docker-stable-24.0.9_ce-1.1 on GA media
CVE-2024-41110
SUSE-SU-2025:03545-1: Security update for docker-stable
CVE-2014-3499 · CVE-2014-5277 · CVE-2014-6407 · CVE-2014-6408 · CVE-2014-8178 · CVE-2014-8179 · CVE-2014-9356 · CVE-2014-9357 · CVE-2014-9358 · CVE-2015-3627 · CVE-2015-3629 · CVE-2015-3630 · CVE-2015-3631 · CVE-2016-3697 · CVE-2016-8867 · CVE-2016-9962 · CVE-2017-14992 · CVE-2017-16539 · CVE-2018-10892 · CVE-2018-15664 · CVE-2018-16873 · CVE-2018-16874 · CVE-2018-16875 · CVE-2018-20699 · CVE-2019-13509 · CVE-2019-14271 · CVE-2020-12912 · CVE-2020-13401 · CVE-2020-15257 · CVE-2020-8694 · CVE-2020-8695 · CVE-2021-21284 · CVE-2021-21285 · CVE-2021-41089 · CVE-2021-41091 · CVE-2021-41092 · CVE-2021-41103 · CVE-2021-41190 · CVE-2021-43565 · CVE-2022-24769 · CVE-2022-27191 · CVE-2022-36109 · CVE-2023-28840 · CVE-2023-28841 · CVE-2023-28842 · CVE-2024-23650 · CVE-2024-23651 · CVE-2024-23652 · CVE-2024-23653 · CVE-2024-29018 · CVE-2024-41110 · CVE-2025-22868 · CVE-2025-22869
SUSE-SU-2024:4319-1: Security update for docker
CVE-2023-45142 · CVE-2023-47108 · CVE-2024-41110
NCSC-2024-0339: Kwetsbaarheden verholpen in Microsoft Mariner
CVE-2022-2601 · CVE-2022-3775 · CVE-2022-36648 · CVE-2019-3833 · CVE-2021-3929 · CVE-2021-4158 · CVE-2021-4206 · CVE-2021-4207 · CVE-2022-26353 · CVE-2022-35414 · CVE-2023-3354 · CVE-2022-3872 · CVE-2022-4144 · CVE-2023-45288 · CVE-2023-29404 · CVE-2023-29402 · CVE-2019-3816 · CVE-2021-3750 · CVE-2022-0358 · CVE-2022-26354 · CVE-2022-3165 · CVE-2022-2962 · CVE-2022-41722 · CVE-2022-29526 · CVE-2007-4559 · CVE-2019-9674 · CVE-2017-18207 · CVE-2019-20907 · CVE-2021-23336 · CVE-2017-17522 · CVE-2024-6655 · CVE-2024-2466 · CVE-2024-39331 · CVE-2021-43565 · CVE-2024-39277 · CVE-2024-38780 · CVE-2024-39292 · CVE-2024-39482 · CVE-2024-39484 · CVE-2024-39495 · CVE-2024-40902 · CVE-2024-41110 · CVE-2024-37298 · CVE-2024-0397 · CVE-2024-38571 · CVE-2024-42077 · CVE-2024-39473 · CVE-2024-26900 · CVE-2024-39474 · CVE-2024-42073 · CVE-2024-42074 · CVE-2024-42075 · CVE-2024-42078 · CVE-2024-0853 · CVE-2024-2004 · CVE-2024-2398 · CVE-2024-38662 · CVE-2024-36288 · CVE-2024-39480 · CVE-2024-39476 · CVE-2024-39475 · CVE-2024-37371 · CVE-2024-26461 · CVE-2024-37370 · CVE-2024-6104 · CVE-2024-6257 · CVE-2024-23722 · CVE-2024-40898 · CVE-2024-38583 · CVE-2024-39493 · CVE-2024-42068 · CVE-2024-39489 · CVE-2024-42070 · CVE-2024-42076 · CVE-2024-42080 · CVE-2024-38428 · CVE-2024-42082 · CVE-2022-48788 · CVE-2023-52340 · CVE-2022-48841 · CVE-2024-39485 · CVE-2024-39483 · CVE-2024-42071 · CVE-2024-42072 · CVE-2024-42237 · CVE-2024-42083
SUSE-SU-2024:4205-1: Security update for docker-stable
CVE-2024-41110
SUSE-SU-2025:1062-1: Security update for docker, docker-stable
CVE-2024-23650 · CVE-2024-29018 · CVE-2024-41110 · CVE-2025-22868 · CVE-2025-22869
SUSE-SU-2025:1102-1: Security update for docker, docker-stable
CVE-2024-23650 · CVE-2024-23653 · CVE-2024-29018 · CVE-2024-41110 · CVE-2025-22868 · CVE-2025-22869
SUSE-RU-2024:4391-1: Recommended update for docker-stable
CVE-2024-23653 · CVE-2024-41110
SUSE-SU-2025:20056-1: Security update for docker
CVE-2024-23651 · CVE-2024-23652 · CVE-2024-23653 · CVE-2024-41110
- Source published
- Jul 24, 2024, 4:49:53 PM (timezone not stated)
- Source modified
- Oct 13, 2024, 9:03:34 PM (timezone not stated)
- Saved here
- 15 Nov 2026 02:32:02 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
EUVD CVSS 3.1 · 10.0 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
nvd · CVE-2024-41110
PublishedMoby 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 spe…
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.
Additional publisher context
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Deferred
Weakness classifications: CWE-187 · CWE-444 · CWE-863
Original publisher date fields
published: 2024-07-24T17:15:11.053
lastModified: 2026-06-17T07:47:17.503
- Source published
- 24 Jul 2024 17:15:11 UTC
- Source modified
- 17 Jun 2026 07:47:17 UTC
- Saved here
- 25 Oct 2026 00:17:22 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · [email protected] · Secondary · 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
osv · GHSA-v23v-6jw2-98fq
PublishedAuthz zero length regression
A security vulnerability has been detected in certain versions of Docker Engine, which could allow an attacker to bypass [authorization plugins (AuthZ)](https://docs.docker.com/engine/extend/plugins_authorization/) under specific circumstances. The base likelihood of this being exploited is low. This advisory outlines the issue, identifies the affected versions, and provides remediation steps for impacted users. ### Impact Using a specially-crafted API request, an Engine API client could make the daemon forward the request or response to an [authorization plugin](https://docs.docker.com/engine/extend/plugins_authorization/) 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](https://docs.docker.com/engine/release-notes/18.09/#security-fixes-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.** ### Vulnerability details - **AuthZ bypass and privilege escalation:** An attacker could exploit a bypass using an API request with Content-Length set to 0, causing the Docker daemon to forward the request without the body to the AuthZ plugin, which might approve the request incorrectly. - **Initial fix:** The issue was fixed in Docker Engine [v18.09.1](https://docs.docker.com/engine/release-notes/18.09/#security-fixes-1) January 2019.. - **Regression:** The fix was not included in Docker Engine v19.03 or newer versions. This was identified in April 2024 and patches were released for the affected versions on July 23, 2024. The issue was assigned [CVE-2024-41110](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-41110). ### Patches - docker-ce v27.1.1 containes patches to fix the vulnerability. - Patches have also been merged into the master, 19.0, 20.0, 23.0, 24.0, 25.0, 26.0, and 26.1 release branches. ### Remediation steps - If you are running an affected version, update to the most recent patched version. - Mitigation if unable to update immediately: - Avoid using AuthZ plugins. - Restrict access to the Docker API to trusted parties, following the principle of least privilege. ### References - https://github.com/moby/moby/commit/fc274cd2ff4cf3b48c91697fb327dd1fb95588fb - https://github.com/moby/moby/commit/a79fabbfe84117696a19671f4aa88b82d0f64fc1 - https://www.docker.com/blog/docker-security-advisory-docker-engine-authz-plugin/
- Source published
- 30 Jul 2024 10:18:57 UTC
- Source modified
- 10 Sep 2026 03:50:16 UTC
- Saved here
- 24 Oct 2026 13:19:41 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CVSS_V4 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Publisher rating · CRITICAL
osv · GO-2024-3005
PublishedMoby authz zero length regression in github.com/moby/moby
Moby authz zero length regression in github.com/moby/moby
- Source published
- 29 Jul 2024 18:08:44 UTC
- Source modified
- 4 Feb 2026 02:35:10 UTC
- Saved here
- 24 Oct 2026 13:19:41 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.