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.
Allocation of Resources Without Limits or Throttling
See which of your images are affected by this CVE and how to fix them by signing into Docker Scout.
Sign in