Docker Sandboxes OAuth response masking could be bypassed with a case-variant token host
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Docker | Docker Sandboxes | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Docker | Sandboxes |
|
Vendor Solution
Upgrade to Docker Sandboxes 0.47.0 or later.
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.127% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Docker sandboxes
|
|
| Vendors & Products |
Docker sandboxes
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Docker Sandboxes compared OAuth token-endpoint hostnames case-sensitively when deciding whether to mask managed credential responses, while request routing treated DNS hostnames case-insensitively. Untrusted code inside a sandbox could use a case-variant hostname to reach the genuine provider endpoint while bypassing response masking. If a user completed the OAuth flow, the provider's access and refresh tokens could be returned unmasked to the sandbox, exposing host-managed credentials. | |
| Title | Docker Sandboxes OAuth response masking could be bypassed with a case-variant token host | |
| First Time appeared |
Docker
Docker docker Sandboxes |
|
| Weaknesses | CWE-178 | |
| CPEs | cpe:2.3:a:docker:docker_sandboxes:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Docker
Docker docker Sandboxes |
|
| References |
| |
| Metrics |
cvssV4_0
|