ZeroHour
Security Affairspublished ()ingested @securityaffairs1

Critical bug in Docker Engine allowed attackers to bypass authorization plugins

Vulnerabilities mentionedAll →

CVEVulnerabilityCVSSEPSSFlagsAffectedExposurePublished
CVE-2024-21412
CVE-2024-21412: Security Feature Bypass in Microsoft Windows Internet Shortcut Files

CVE-2024-21412 is a security feature bypass (CWE-693) in how Microsoft Windows handles Internet Shortcut files: a crafted shortcut can make Windows skip the security warning prompt that normally appears before untrusted internet content is opened or downloaded. Triggering it requires user interaction — an attacker must deliver a malicious shortcut file, typically via email or a malicious website, and convince the user to open it, which is reflected in the CVSS vector's UI:R component. An attacker who succeeds gains a bypass of those prompts, making it easier to retrieve and execute malicious remote content with fewer warnings; the DarkGate malware operators used exactly this technique in zero-day campaigns to distribute their loader. Anyone running the affected Windows 10 (1809, 21H2, 22H2), Windows 11 (21H2, 22H2, 23H2), Windows Server 2019, or Windows Server 2022 (including 23H2) builds was exposed. The flaw was patched in Microsoft's February 2024 Patch Tuesday release (2024-02-13), the same day CISA added it to the KEV catalog, and it is under active exploitation with known ransomware association and a 95.4% EPSS score.

Do: Apply the February 2024 Windows cumulative security update (released 2024-02-13) or any later monthly cumulative update to every affected Windows 10, Windows 11, Windows Server 2019, and Windows Server 2022 build, and verify patch levels through your endpoint inventory. Because exploitation requires user interaction, as an interim control flag or block .url/Internet Shortcut attachments at email gateways and remind users not to open shortcuts from untrusted sources. Prioritize internet-facing and shared endpoints given the KEV listing and known ransomware use.

8.195% KEV ransomware
  • microsoft Windows 10 1809, 21H2, 22H2
  • microsoft Windows 11 21H2, 22H2, 23H2
  • microsoft Windows Server 2019 all supported editions
  • +1 more
mass≈1 billion Windows 10/11/Server installations potentially affected worldwide (pre-patch installed base)
CVE-2024-41110
Moby is an open-source project created by Docker for software containerization.

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.

NVD description · AI analysis pending
9.916%
Full article504 words · extracted from securityaffairs.com · click to collapse

A critical flaw in some versions of Docker Engine can be exploited to bypass authorization plugins (AuthZ) under specific circumstances.

A vulnerability, tracked as CVE-2024-41110 (CVSS score of 10.0), in certain versions of Docker Engine can allow an attacker to bypass authorization plugins (AuthZ) under specific circumstances.

“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.” reads the advisory published by the Moby Project maintainers. “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 flaw that was discovered in 2018 allowed attackers to bypass authorization (AuthZ) plugins in Docker Engine using crafted API requests, potentially leading to unauthorized actions, including privilege escalation. The vulnerability was addressed with the release of Docker Engine v18.09.1, but it was not included in subsequent major versions, causing a regression. This issue does not affect Docker EE v19.03.x or any version of Mirantis Container Runtime.

The vulnerability was discovered in April 2024 and has been addressed with the release of versions 23.0.14 and 27.1.0 in July 23, 2024. Below is the list of versions of Docker Engine that are impacted if the AuthZ plugin is used:

  • <= v19.03.15
  • <= v20.10.27
  • <= v23.0.14
  • <= v24.0.9
  • <= v25.0.5
  • <= v26.0.2
  • <= v26.1.4
  • <= v27.0.3, and
  • <= v27.1.0

Docker Engine v19.03.x and later versions are not affected if authorization plugins are not used for access control decisions. Similarly, all versions of Mirantis Container Runtime remain unaffected by the issue.

“Users of Docker commercial products and internal infrastructure who do not rely on AuthZ plugins are unaffected.” continues the advisory.

Docker Desktop up to version 4.32.0 includes vulnerable versions of Docker Engine. However, the risk is mitigated because exploitation requires access to the Docker API, which usually needs local access to the host machine. By default, Docker Desktop does not include AuthZ plugins, limiting privilege escalation to the Docker Desktop VM rather than the underlying host. A fixed version of Docker Engine is expected in Docker Desktop v4.33, addressing these security concerns.

Below are the remediation steps proposed by Docker maintainers:

  1. Update Docker Engine:
  • If you are running an affected version, update to the most recent patched version.
  1. 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.
  1. Update Docker Desktop:
  • If using an affected version, update to Docker Desktop 4.33 after it is released.
  • Ensure AuthZ plugins are not used and do not expose the Docker API over TCP without protection.
  • Docker Business subscribers can use Settings Management to enforce secure settings.

Follow me on Twitter: @securityaffairs and Facebook and Mastodon

Pierluigi Paganini

(SecurityAffairs – hacking, CVE-2024-21412)



Text extracted automatically; images, tables and formatting may be missing. Original: https://securityaffairs.com/166160/hacking/docker-engine-critical-flaw.html