runc vulnerabilities

Direct Vulnerabilities

Known vulnerabilities in the runc package. This does not include vulnerabilities belonging to this package’s dependencies.

Fix vulnerabilities automatically

Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

Fix for free

Vulnerability	Vulnerable Version
H Excessive Platform Resource Consumption within a Loop	*
M Improper Certificate Validation	*
M Resource Exhaustion	*
M Reachable Assertion	*
H Link Following	<4:1.3.0-4.el9_7
H Link Following	<4:1.3.0-4.el9_7
H Link Following	<4:1.3.0-4.el9_7
M Allocation of Resources Without Limits or Throttling	*
M Allocation of Resources Without Limits or Throttling	*
M Improper Output Neutralization for Logs	*
M Expected Behavior Violation	*
M Time-of-check Time-of-use (TOCTOU)	*
L Incorrect Authorization	*
L Incorrect Authorization	*
L Improper Verification of Cryptographic Signature	*
M Use of Uninitialized Variable	*
L Directory Traversal	*
M Loop with Unreachable Exit Condition ('Infinite Loop')	<4:1.1.13-4.el9
H Memory Leak	<4:1.1.12-3.el9_4
M Improper Input Validation	<4:1.1.12-4.el9_4
H Information Exposure	<4:1.1.12-1.el9_3
M Information Exposure	<4:1.1.12-2.el9
M Buffer Access with Incorrect Length Value	<4:1.1.9-2.el9_3
M Allocation of Resources Without Limits or Throttling	<4:1.1.9-2.el9_3
M Resource Exhaustion	<4:1.1.9-2.el9_3
M Incorrect Default Permissions	<4:1.1.9-1.el9
M Authentication Bypass by Primary Weakness	<4:1.1.9-1.el9
M Resource Exhaustion	<4:1.1.9-1.el9
M Path Equivalence	<4:1.1.9-1.el9
M CVE-2022-41715	*
L Resource Exhaustion	*
M Improperly Controlled Sequential Memory Allocation	<4:1.1.12-2.el9
M Improperly Controlled Sequential Memory Allocation	<4:1.1.12-2.el9
M Improperly Controlled Sequential Memory Allocation	<4:1.1.12-2.el9
L Incorrect Default Permissions	<4:1.1.4-1.el9
L Insufficient Entropy	*
M Integer Overflow or Wraparound	<4:1.1.9-1.el9
M Improper Input Validation	*

Vulnerability

Vulnerable Version

Excessive Platform Resource Consumption within a Loop