Allocation of Resources Without Limits or Throttling Affecting containers-common package, versions <2:1-81.0.1.module+el8.10.0+90298+77a9814d


Severity

Recommended
medium

Based on Oracle Linux security rating

    Threat Intelligence

    EPSS
    0.21% (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 ID SNYK-ORACLE8-CONTAINERSCOMMON-6156351
  • published 14 Jan 2024
  • disclosed 14 Oct 2022

How to fix?

Upgrade Oracle:8 containers-common to version 2:1-81.0.1.module+el8.10.0+90298+77a9814d or higher.
This issue was patched in ELSA-2024-2988.

NVD Description

Note: Versions mentioned in the description apply only to the upstream containers-common package and not the containers-common package as distributed by Oracle. See How to fix? for Oracle: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
Expand this section

NVD

7.5 high
  • Attack Vector (AV)
    Network
  • Attack Complexity (AC)
    Low
  • Privileges Required (PR)
    None
  • User Interaction (UI)
    None
  • Scope (S)
    Unchanged
  • Confidentiality (C)
    None
  • Integrity (I)
    None
  • Availability (A)
    High
Expand this section

SUSE

7.5 high
Expand this section

Red Hat

6.5 medium