CVE-2024-23652CriticalMicrosoft CVSS 9.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Microsoft security update for CVE-2024-23652

Published
February 5, 2024
Last Modified
—

🔗 CVE IDs covered (1)

📋 Microsoft's advisory

EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-23652. This page also shows what EchelonGraph holds for CVE-2024-23652, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.

🎯 Affected products5

  • azl3 moby-engine 20.10.25-3 on Azure Linux 3.0
  • azl3 moby-engine 25.0.3-1 on Azure Linux 3.0
  • cbl2 moby-engine 20.10.27-4 on CBL Mariner 2.0
  • cbl2 moby-engine 24.0.9-16 on CBL Mariner 2.0
  • cbl2 moby-engine 24.0.9-16 on CBL-Mariner 2.0

✅ Updates Microsoft lists: 2 updates

2 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.

KB articleUpdateFixed build
—Security Update20.10.27-4
—Security Update25.0.3-1

🧭 EchelonGraph on CVE-2024-23652

EchelonGraph score
10.0 CRITICAL
CISA KEV
Not listed
Fix status
A fix is available — apply it.

Description from the CVE record (CVE.org), as published by its numbering authority

BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. A malicious BuildKit frontend or Dockerfile using RUN --mount could trick the feature that removes empty files created for the mountpoints into removing a file outside the container, from the host system. The issue has been fixed in v0.12.5. Workarounds include avoiding using BuildKit frontends from an untrusted source or building an untrusted Dockerfile containing RUN --mount feature.

Published by GitHub, Inc., the CVE Numbering Authority that assigned CVE-2024-23652, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).

🔗 References (2)