Advisory

GHSA-5ffw-gxpp-mxpf

Also known as: CVE-2022-31030, GO-2022-0482

Summary

containerd CRI plugin: Host memory exhaustion through ExecSync

Details

Impact

A bug was found in containerd's CRI implementation where programs inside a container can cause the containerd daemon to consume memory without bound during invocation of the ExecSync API. This can cause containerd to consume all available memory on the computer, denying service to other legitimate workloads. Kubernetes and crictl can both be configured to use containerd's CRI implementation; ExecSync may be used when running probes or when executing processes via an "exec" facility.

Patches

This bug has been fixed in containerd 1.6.6 and 1.5.13. Users should update to these versions to resolve the issue.

Workarounds

Ensure that only trusted images and commands are used.

References

  • Similar fix in cri-o's CRI implementation https://github.com/cri-o/cri-o/security/advisories/GHSA-fcm2-6c3h-pg6j

Credits

The containerd project would like to thank David Korczynski and Adam Korczynski of ADA Logics for responsibly disclosing this issue in accordance with the containerd security policy during a security audit sponsored by CNCF and facilitated by OSTIF.

For more information

If you have any questions or comments about this advisory:

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2022-06-06 22:07 UTC
Modified
2026-09-10 03:49 UTC

Affected packages and fixes

github.com/containerd/containerd

Go · All systems

Affected

  • introduced 0, fixed 1.5.13 (semver)

Fixed versions

1.5.13

Fix

github.com/containerd/containerd

Go · All systems

Affected

  • introduced 1.6.0, fixed 1.6.6 (semver)

Fixed versions

1.6.6

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences