Skip to content
Heist/ feed
Back to feed
Medium

Play With Docker vulnerable to Authorization Bypass Through User-Controlled Key

Type: advisorySources: OSV

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.

Products
Not specified
Affected versions
Not specified
Fixed versions
Not specified
CVEs
CVE-2023-28109
Confirmed fixed CVEs
Not specified
Updated in this feed
4 Nov 2026, 21:06 UTC · Revision 1

Source evidence

Play With Docker vulnerable to Authorization Bypass Through User-Controlled Key

core-osv · Original source

Published 16 Mar 2023, 16:49 UTC

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.

osv:CVE-2023-28109
Complete source record
{
  "id": "5057dd70ebe732e659d64596d51a39c088c18846d1106891126b12faf66104f3",
  "url": "https://osv.dev/vulnerability/CVE-2023-28109",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "Play With Docker vulnerable to Authorization Bypass Through User-Controlled Key",
    "summary": "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.",
    "evidence": "osv:CVE-2023-28109",
    "products": [],
    "severity": "medium",
    "structured": {
      "id": "CVE-2023-28109",
      "aliases": [
        "CVE-2023-28109",
        "GHSA-vq59-5x26-h639"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://github.com/play-with-docker/play-with-docker",
              "type": "GIT",
              "events": [
                {
                  "introduced": "92aa3aa3f8838cccbcd3a4521bc9658c38d3a915"
                },
                {
                  "fixed": "ed82247c9ab7990ad76ec2bf1498c2b2830b6f1a"
                }
              ],
              "database_specific": {
                "extracted_events": [
                  {
                    "cpe": "cpe:2.3:a:play-with-docker:play_with_docker:0.0.1:*:*:*:*:go:*:*",
                    "range": [
                      {
                        "introduced": "0.0.1"
                      },
                      {
                        "last_affected": "0.0.1"
                      }
                    ],
                    "source": "CPE_STRING"
                  },
                  {
                    "cpe": "cpe:2.3:a:play-with-docker:play_with_docker:0.0.2:*:*:*:*:go:*:*",
                    "range": [
                      {
                        "introduced": "0.0.2"
                      },
                      {
                        "last_affected": "0.0.2"
                      }
                    ],
                    "source": "CPE_STRING"
                  },
                  {
                    "range": [
                      {
                        "fixed": "ed82247c9ab7990ad76ec2bf1498c2b2830b6f1a"
                      }
                    ],
                    "source": "REFERENCES_COMMIT"
                  }
                ]
              }
            }
          ],
          "versions": [
            "0.0.1",
            "0.0.2",
            "v0.0.2",
            "v0.0.1"
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-28109.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:39.640056194Z",
      "provider": "osv",
      "references": [
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/28xxx/CVE-2023-28109.json",
        "https://github.com/play-with-docker/play-with-docker/security/advisories/GHSA-vq59-5x26-h639",
        "https://nvd.nist.gov/vuln/detail/CVE-2023-28109",
        "https://github.com/play-with-docker/play-with-docker/commit/ed82247c9ab7990ad76ec2bf1498c2b2830b6f1a"
      ],
      "provider_metadata": {
        "cwe_ids": [
          "CWE-639"
        ],
        "cna_assigner": "GitHub_M",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/28xxx/CVE-2023-28109.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2023-28109",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 507027,
  "published_at": "2023-03-16T16:49:17.956+00:00"
}