Allocation of Resources Without Limits or Throttling Affecting container-tools:rhel8/criu package, versions <0:3.18-4.module+el8.9.0+20326+387084d0


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.22% (60th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL8-CONTAINERTOOLS-7055207
  • published23 May 2024
  • disclosed4 Oct 2022

Introduced: 4 Oct 2022

CVE-2022-2879  (opens in a new tab)
CWE-770  (opens in a new tab)

How to fix?

Upgrade RHEL:8 container-tools:rhel8/criu to version 0:3.18-4.module+el8.9.0+20326+387084d0 or higher.
This issue was patched in RHSA-2024:2988.

NVD Description

Note: Versions mentioned in the description apply only to the upstream container-tools:rhel8/criu package and not the container-tools:rhel8/criu package as distributed by RHEL. See How to fix? for RHEL:8 relevant fixed versions and status.

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.

CVSS Scores

version 3.1