# CVE-2019-10147: Privilege escalation in rkt

> Attackers can escape container isolation via rkt enter to access host resources due to missing cgroup limits.

- **Severity:** Medium 4.7 (`CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-mr55-c2c7-jch7, UBUNTU-CVE-2019-10147

## What is CVE-2019-10147?

CVE-2019-10147 is a medium-severity vulnerability in [UNKNOWN] rkt, published on 3 Jun 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-862 (Missing Authorization), CWE-250 (Execution with Unnecessary Privileges)

## Which versions are affected by CVE-2019-10147?

It affects 1 product.


Products: Redhat Rkt.

## How do I fix CVE-2019-10147?

No fix has been published for CVE-2019-10147 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-10147 being exploited?

There is no known exploitation of CVE-2019-10147 in the wild and no public exploit code.

## Other vulnerabilities in [UNKNOWN] rkt

- [CVE-2019-10144](https://insights.sbomify.com/CVE-2019-10144/): Privilege escalation in rkt (high 7.0)
- [CVE-2019-10145](https://insights.sbomify.com/CVE-2019-10145/): Security feature bypass in rkt (high 7.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-10147 and fix it if it is affected.

What it is: CVE-2019-10147 is a medium-severity vulnerability in [UNKNOWN] rkt, published on 3 Jun 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-10147 in the wild and no public exploit code.

Affected product: [UNKNOWN] rkt. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-10147/ (Markdown: https://insights.sbomify.com/CVE-2019-10147/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-10147
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-10147
- OSV: https://osv.dev/vulnerability/CVE-2019-10147

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-10147/
Summaries are generated and may contain mistakes; the official description above is the record.