Moby: Off-by-one error in plugin privilege validation
moby
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/docker/docker Go |
| No fix yet |
| github.com/moby/moby/v2 Go |
|
|
| github.com/moby/moby Go |
|
moby
| Product | Affected | Fixed in |
|---|---|---|
| github.com/docker/docker Go |
| No fix yet |
| github.com/moby/moby/v2 Go |
|
|
| github.com/moby/moby Go |
|
| No fix yet |
Moby is an open source container framework. Prior to version 29.3.1, a security vulnerability has been detected that allows plugins privilege validation to be bypassed during docker plugin install. Due to an error in the daemon's privilege comparison logic, the daemon may incorrectly accept a privilege set that differs from the one approved by the user. Plugins that request exactly one privilege are also affected, because no comparison is performed at all. This issue has been patched in version 29.3.1.
From the CVE record · GitHub_M
Before Moby 29.3.1, the daemon may accept plugin privileges that differ from those a user approved during `docker plugin install`. The validation is also bypassed for plugins requesting exactly one privilege. Exploitation requires a user to install a plugin; the input does not specify network access or authentication requirements.
Check deployments running Moby before 29.3.1 or using Go packages github.com/moby/moby/v2 before 2.0.0-beta.8, github.com/moby/moby at any version, or github.com/docker/docker at any version.