CVE-2022-2879HighMicrosoft CVSS 7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Microsoft security update for CVE-2022-2879

Published
May 31, 2026
Last Modified
—

🔗 CVE IDs covered (1)

CVE-2022-2879 →

📋 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-2022-2879. This page also shows what EchelonGraph holds for CVE-2022-2879, 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 products15

  • azl3 containerized-data-importer 1.57.0-14 on Azure Linux 3.0
  • azl3 containerized-data-importer 1.57.0-3 on Azure Linux 3.0
  • azl3 golang 1.27.0-1 on Azure Linux 3.0
  • azl3 ig 0.25.0-2 on Azure Linux 3.0
  • azl3 ig 0.29.0-1 on Azure Linux 3.0
  • azl3 libcontainers-common 20240213-2 on Azure Linux 3.0
  • azl3 libcontainers-common 20240213-3 on Azure Linux 3.0
  • azl3 moby-engine 25.0.3-13 on Azure Linux 3.0
  • azl3 moby-engine 25.0.3-3 on Azure Linux 3.0
  • azl3 skopeo 1.14.4-1 on Azure Linux 3.0
  • azl3 skopeo 1.14.4-5 on Azure Linux 3.0
  • cbl2 golang 1.17.13-2 on CBL Mariner 2.0
  • cbl2 golang 1.19.10-1 on CBL Mariner 2.0
  • cbl2 golang 1.21.6-1 on CBL Mariner 2.0
  • cm1 golang 1.17.13-2 on CBL Mariner 1.0

✅ Updates Microsoft lists: 10 updates

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

KB articleUpdateFixed build
—Security Update25.0.3-3
—Security Update0.29.0-1
—Security Update20240213-2
—Security Update1.14.4-1
—Security Update1.17.13-2
—Security Update1.21.6-1
—Security Update1.19.10-1
—Security Update1.57.0-3
—Security Update—
—Security Update—

🧭 EchelonGraph on CVE-2022-2879

EchelonGraph score
7.5 HIGH
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

Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to allocate unbounded amounts of memory, potentially causing resource exhaustion or panics. After fix, Reader.Read limits the maximum size of header blocks to 1 MiB.

Published by Go Project, the CVE Numbering Authority that assigned CVE-2022-2879, 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)