rkt through version 1.30.0 does not isolate processes in containers that are run with `rkt enter`. Processes run with `rkt enter` do not have seccomp filtering during stage 2 (the actual environment in which the applications run). Compromised containers could exploit this flaw to access host resources.
References
Link | Resource |
---|---|
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10145 | Issue Tracking Third Party Advisory |
https://www.twistlock.com/labs-blog/breaking-out-of-coresos-rkt-3-new-cves/ | Exploit Third Party Advisory |
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10145 | Issue Tracking Third Party Advisory |
https://www.twistlock.com/labs-blog/breaking-out-of-coresos-rkt-3-new-cves/ | Exploit Third Party Advisory |
Configurations
History
21 Nov 2024, 04:18
Type | Values Removed | Values Added |
---|---|---|
References | () https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10145 - Issue Tracking, Third Party Advisory | |
References | () https://www.twistlock.com/labs-blog/breaking-out-of-coresos-rkt-3-new-cves/ - Exploit, Third Party Advisory |
Information
Published : 2019-06-03 19:29
Updated : 2024-11-21 04:18
NVD link : CVE-2019-10145
Mitre link : CVE-2019-10145
CVE.ORG link : CVE-2019-10145
JSON object : View
Products Affected
redhat
- rkt