Host sysctl modification via namespace misvalidation
Published Feb 9, 2022 · Updated Aug 2, 2024
Incorrect sysctl validation in affected CRI-O releases allows remote authenticated users to alter host kernel parameters through a crafted pod. When a pod shares host network and IPC namespaces, pinns applies safe-listed pod sysctls to the host instead of an unshared pod namespace. The user must be authorized to create such a pod; the resulting host sysctl write can expose host data or disrupt node services.
Summary
What happened
Incorrect sysctl validation in affected CRI-O releases allows remote authenticated users to alter host kernel parameters through a crafted pod. When a pod shares host network and IPC namespaces, pinns applies safe-listed pod sysctls to the host instead of an unshared pod namespace. The user must be authorized to create such a pod; the resulting host sysctl write can expose host data or disrupt node services.
The record
- CVE
- CVE-2022-0532
- Published
- Feb 9, 2022
- Updated
- Aug 2, 2024
- Vendor
- CRI-O
- Product
- CRI-O
- Classifications
- CWE-732, T1611
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 9, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.18
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo