Information Exposure Affecting runc package, versions <4:1.1.12-1.el9_3


Severity

Recommended
0.0
high
0
10

Based on CentOS security rating.

Threat Intelligence

EPSS
5.06% (94th 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 Learn

Learn about Information Exposure vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-CENTOS9-RUNC-6222634
  • published1 Feb 2024
  • disclosed31 Jan 2024

Introduced: 31 Jan 2024

CVE-2024-21626  (opens in a new tab)
CWE-200  (opens in a new tab)

How to fix?

Upgrade Centos:9 runc to version 4:1.1.12-1.el9_3 or higher.

NVD Description

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

runc is a CLI tool for spawning and running containers on Linux according to the OCI specification. In runc 1.1.11 and earlier, due to an internal file descriptor leak, an attacker could cause a newly-spawned container process (from runc exec) to have a working directory in the host filesystem namespace, allowing for a container escape by giving access to the host filesystem ("attack 2"). The same attack could be used by a malicious image to allow a container process to gain access to the host filesystem through runc run ("attack 1"). Variants of attacks 1 and 2 could be also be used to overwrite semi-arbitrary host binaries, allowing for complete container escapes ("attack 3a" and "attack 3b"). runc 1.1.12 includes patches for this issue.

CVSS Scores

version 3.1