High [CVE-2022-4318 +1] Fix Bypass for CVE-2022-4318 — /etc/passwd Injection via HOME env
This high-severity Red Hat Linux advisory covers CVE-2022-4318 and CVE-2026-15809 affecting Red Hat OpenShift Container Platform 4.22, Confidential Compute Attestation.
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
A flaw was found in CRI-O. The fix for a previous vulnerability (CVE-2022-4318) was incorrect, allowing it to be bypassed.
An attacker capable of setting environment variables on a container can inject a newline character into the HOME environment variable. This issue allows the addition of arbitrary lines into /etc/passwd by use of a specially crafted environment variable.
This Important flaw in CRI-O allows for arbitrary line injection into a container's `/etc/passwd` file. This risk is present in environments where untrusted users can influence container environment variable settings.
Red Hat severity: Important — CVSS 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Weakness: CWE-134.
Affected Red Hat products: Red Hat OpenShift Container Platform 4.22; Confidential Compute Attestation; Red Hat OpenShift Container Platform 4. Will not fix / out of support: Red Hat OpenShift Container Platform 4.
Red Hat fixing advisory: RHSA-2026:57361.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 6 days ago·verify at source
- cri-o-0:1.35.6-5.rhaos4.22.git41f610b.el9
- RHSA-2026:57361
Official advisory · high-confidence parse· fetched 6 days ago·verify at source
Mitigation checklist
- Restrict access to users who can create or modify container workloads through appropriate RBAC permissions, apply security controls such as Security Context Constraints (SCCs) to limit privilege escalation, and enforce policies to run containers with reduced privileges (for example, as non-root) to reduce the impact of potential exploitation. Enable SELinux on affected nodes and consider admission controls to prevent potentially unsafe workload configurations.
Official advisory · high-confidence parse· fetched 6 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.