When generating the systemd service units for the docker snap (and other similar snaps), snapd does not specify Delegate=yes - as a result systemd will move processes from the containers created and managed by these snaps into the cgroup of the main daemon within the snap itself when reloading system units. This may grant additional privileges to a container within the snap that were not originally intended.
Weakness
The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Snapd | Canonical | * | 2.48.3 (excluding) |
| Snapd | Ubuntu | bionic | * |
| Snapd | Ubuntu | devel | * |
| Snapd | Ubuntu | esm-infra/bionic | * |
| Snapd | Ubuntu | esm-infra/focal | * |
| Snapd | Ubuntu | esm-infra/xenial | * |
| Snapd | Ubuntu | focal | * |
| Snapd | Ubuntu | groovy | * |
| Snapd | Ubuntu | snap | * |
| Snapd | Ubuntu | trusty | * |
| Snapd | Ubuntu | xenial | * |
Potential Mitigations
Related Attack Patterns
- https://cwe.mitre.org/data/definitions/122.html
- https://cwe.mitre.org/data/definitions/233.html
- https://cwe.mitre.org/data/definitions/58.html