Homepage
About Snyk

Memory Leak Affecting runc package, versions <4:1.1.12-3.el9_4

Severity

 Recommended
high

Based on AlmaLinux security rating

    Threat Intelligence

    EPSS
    0.07% (32nd 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-ALMALINUX9-RUNC-7568938
  • published 25 Jul 2024
  • disclosed 30 Apr 2024
Report a new vulnerability Found a mistake?

Introduced: 30 Apr 2024

CVE-2024-1394 Open this link in a new tab
CWE-401 Open this link in a new tab

How to fix?

Upgrade AlmaLinux:9 runc to version 4:1.1.12-3.el9_4 or higher.
This issue was patched in ALSA-2024:4762.

NVD Description

Note: Versions mentioned in the description apply only to the upstream runc package and not the runc package as distributed by AlmaLinux. See How to fix? for AlmaLinux:9 relevant fixed versions and status.

A memory leak flaw was found in Golang in the RSA encrypting/decrypting code, which might lead to a resource exhaustion vulnerability using attacker-controlled inputs​. The memory leak happens in github.com/golang-fips/openssl/openssl/rsa.go#L113. The objects leaked are pkey​ and ctx​. That function uses named return parameters to free pkey​ and ctx​ if there is an error initializing the context or setting the different properties. All return statements related to error cases follow the "return nil, nil, fail(...)" pattern, meaning that pkey​ and ctx​ will be nil inside the deferred function that should free them.

References

CVSS Scores

version 3.1
Expand this section

Red Hat

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