Moby is an open source container framework. In Docker Engine prior to version 29.5.1, Docker Daemon versions 28.5.2 and prior, and Moby Daemon prior to version 2.0.0-beta.14, a race condition during docker cp mount setup allows a malicious container to create empty files or directories at arbitrary absolute paths on the host filesystem. This issue has been patched in Docker Engine version 29.5.1 and Moby Daemon version 2.0.0-beta.14.
Weakness
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters that could be interpreted as web-scripting elements when they are sent to an error page.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Engine | Docker | * | 29.5.1 (excluding) |
| Moby | Mobyproject | * | 28.5.2 (including) |
| Moby/v2 | Mobyproject | 2.0.0-beta0 (including) | 2.0.0-beta0 (including) |
| Moby/v2 | Mobyproject | 2.0.0-beta1 (including) | 2.0.0-beta1 (including) |
| Moby/v2 | Mobyproject | 2.0.0-beta10 (including) | 2.0.0-beta10 (including) |
| Moby/v2 | Mobyproject | 2.0.0-beta11 (including) | 2.0.0-beta11 (including) |
| Moby/v2 | Mobyproject | 2.0.0-beta12 (including) | 2.0.0-beta12 (including) |
| Moby/v2 | Mobyproject | 2.0.0-beta13 (including) | 2.0.0-beta13 (including) |
| Moby/v2 | Mobyproject | 2.0.0-beta2 (including) | 2.0.0-beta2 (including) |
| Moby/v2 | Mobyproject | 2.0.0-beta3 (including) | 2.0.0-beta3 (including) |
| Moby/v2 | Mobyproject | 2.0.0-beta4 (including) | 2.0.0-beta4 (including) |
| Moby/v2 | Mobyproject | 2.0.0-beta5 (including) | 2.0.0-beta5 (including) |
| Moby/v2 | Mobyproject | 2.0.0-beta6 (including) | 2.0.0-beta6 (including) |
| Moby/v2 | Mobyproject | 2.0.0-beta7 (including) | 2.0.0-beta7 (including) |
| Moby/v2 | Mobyproject | 2.0.0-beta8 (including) | 2.0.0-beta8 (including) |
| Moby/v2 | Mobyproject | 2.0.0-beta9 (including) | 2.0.0-beta9 (including) |
Extended Description
Error pages may include customized 403 Forbidden or 404 Not Found pages. When an attacker can trigger an error that contains script syntax within the attacker’s input, then cross-site scripting attacks may be possible.
Potential Mitigations
- Use and specify an output encoding that can be handled by the downstream component that is reading the output. Common encodings include ISO-8859-1, UTF-7, and UTF-8. When an encoding is not specified, a downstream component may choose a different encoding, either by assuming a default encoding or automatically inferring which encoding is being used, which can be erroneous. When the encodings are inconsistent, the downstream component might treat some character or byte sequences as special, even if they are not special in the original encoding. Attackers might then be able to exploit this discrepancy and conduct injection attacks; they even might be able to bypass protection mechanisms that assume the original encoding is also being used by the downstream component.
- The problem of inconsistent output encodings often arises in web pages. If an encoding is not specified in an HTTP header, web browsers often guess about which encoding is being used. This can open up the browser to subtle XSS attacks.