Skip to content

Withdrawn: Runc allows an arbitrary systemd property to be injected

High severity GitHub Reviewed Published Apr 26, 2024 to the GitHub Advisory Database • Updated Jun 5, 2024
Withdrawn This advisory was withdrawn on Apr 30, 2024

Package

gomod github.com/opencontainers/runc (Go)

Affected versions

< 1.2.0-rc.1

Patched versions

1.2.0-rc.1

Description

Withdrawn Advisory

This advisory has been withdrawn because it was incorrectly attributed to runc. Please see the issue here for more information.

Original Description

A flaw was found in cri-o, where an arbitrary systemd property can be injected via a Pod annotation. Any user who can create a pod with an arbitrary annotation may perform an arbitrary action on the host system. This issue has its root in how runc handles Config Annotations lists.

References

Published by the National Vulnerability Database Apr 26, 2024
Published to the GitHub Advisory Database Apr 26, 2024
Reviewed Apr 26, 2024
Withdrawn Apr 30, 2024
Last updated Jun 5, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Weaknesses

CVE ID

No known CVE

GHSA ID

GHSA-c5pj-mqfh-rvc3

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.