rkt through version 1.30.0 does not isolate processes in containers that are run with `rkt enter`. Processes run with `rkt enter` are given all capabilities during stage 2 (the actual environment in which the applications run). Compromised containers could exploit this flaw to access host resources.
The product performs an operation at a privilege level that is higher than the minimum level required, which creates new weaknesses or amplifies the consequences of other weaknesses.
The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
Link | Tags |
---|---|
https://www.twistlock.com/labs-blog/breaking-out-of-coresos-rkt-3-new-cves/ | third party advisory exploit |
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10144 | third party advisory issue tracking |