Play With Docker
Approved changes feed: RSS · Atom
cpe:2.3:a:play-with-docker:play-with-docker:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Play With Docker (60c9a5c9-37b8-5a84-8cc6-7e2903512015) |
|---|---|
| Product | Play With Docker (36d4ce5d-eb59-5ef9-a836-39515d68f7c4) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2023-28109 |
vulnerable | 2026-06-08 06:01:09.670360 |
Play With Docker vulnerable to Authorization Bypass Through User-Controlled Key
MEDIUM (6.5)
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.
Published: 2023-03-16T16:49:17.956Z
Updated: 2025-02-25T14:55:02.690Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.