Low: runc security update

runc Updated 02 Oct 2025

Summary

15/11/2022
N/A
Yes i
Unrated
Not published

ALSA-2022:8090: Low: runc security update. Affects runc versions < 4:1.1.4-1.el9. Fixed in 4:1.1.4-1.el9. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The runC tool is a lightweight, portable implementation of the Open Container Format (OCF) that provides container runtime. It is used to create and run containers, isolating processes and resources within a container environment. runC is widely used in containerization platforms and is a critical component for ensuring the security and isolation of containerized applications.

Vulnerability Detail

The vulnerability (CVE-2022-29162) in runC is related to the incorrect handling of inheritable capabilities. Inheritable capabilities allow processes to inherit certain privileges from their parent processes. Due to a flaw in runC, an attacker could exploit this vulnerability to gain elevated privileges within a container. This could lead to unauthorized access, privilege escalation, or the ability to execute malicious code within the container environment.

How To Fix

Minimum fixed version

4:1.1.4-1.el9

This is the first release that contains the fix.

sudo dnf update runc

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to apply the security update as soon as possible to mitigate the risk.

Conclusion

The runC tool is a critical component in containerization platforms, and this vulnerability could potentially lead to unauthorized access and privilege escalation within container environments. It is crucial to update the runC package to the latest version to mitigate the risk. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for runc →

Share this vulnerability

FAQ

runC is a lightweight, portable implementation of the Open Container Format (OCF) that provides container runtime. It is used to create and run containers, isolating processes and resources within a container environment.

The vulnerability in runC could allow an attacker to gain elevated privileges within a container. This could lead to unauthorized access, privilege escalation, or the ability to execute malicious code within the container environment.

To fix this vulnerability, update the runC package to version 4:1.1.4-1.el9 or later. This update includes the necessary security patches to address the vulnerability.

There is no known workaround for this vulnerability. It is essential to apply the security update as soon as possible to mitigate the risk.

For more information about this vulnerability, refer to the CVE page(s) listed in the References section of the AlmaLinux Release Notes.

Related vulnerabilities

Recent vulnerabilities recorded for runc.

How To Fix

Minimum fixed version

4:1.1.4-1.el9

This is the first release that contains the fix.

sudo dnf update runc

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback