# CVE-2023-28109: Play With Docker vulnerable to Authorization Bypass Through User-Controlled Key

> Attackers can bypass CORS policies via domain hijacking to retrieve basic user information from the Play With Docker web application.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Mar 2023
- **Updated:** 25 Feb 2025
- **Also known as:** GHSA-vq59-5x26-h639

## What is CVE-2023-28109?

CVE-2023-28109 is a medium-severity authentication bypass vulnerability in play-with-docker, published on 16 Mar 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Play With Docker is a browser-based Docker playground. Versions 0.0.2 and prior are vulnerable to domain hijacking.
Because CORS configuration was not correct, an attacker could use `play-with-docker.com` as an example and set the origin header in an http request as `evil-play-with-docker.com`. The domain would echo in response header, which successfully bypassed the CORS policy and retrieved basic user information. This issue has been fixed in commit ed82247c9ab7990ad76ec2bf1498c2b2830b6f1a. There are no known workarounds.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2023-28109?

2 open source packages ship an affected version, including github.com/play-with-docker/play-with-docker. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/play-with-docker/play-with-docker` | Go | All versions to 0.0.2 | None |
| `github.com/play-with-docker/play-with-docker` | Go | All versions to 0.0.2 | None |

Products: Play-With-Docker Play With Docker.

## How do I fix CVE-2023-28109?

No fix has been published for CVE-2023-28109 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-28109 being exploited?

There is no known exploitation of CVE-2023-28109 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-28109 and fix it if it is affected.

What it is: CVE-2023-28109 is a medium-severity authentication bypass vulnerability in play-with-docker, published on 16 Mar 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-28109 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/play-with-docker/play-with-docker (Go): affected all versions up to 0.0.2; no fix listed
- github.com/play-with-docker/play-with-docker (Go): affected all versions up to 0.0.2; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-28109/ (Markdown: https://insights.sbomify.com/CVE-2023-28109/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-28109
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-28109
- OSV: https://osv.dev/vulnerability/CVE-2023-28109

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-28109/
Summaries are generated and may contain mistakes; the official description above is the record.