Headline
GHSA-vq59-5x26-h639: Authorization Bypass Through User-Controlled Key play-with-docker
Impact Give that CORS configuration was not correct, an attacker could use play-with-docker.com as an example, set origin header in http request as evil-play-with-docker.com, it will be echo in response header, which successfully bypass the CORS policy and retrieves basic user information.
Patches It has been fixed in lastest version, Please upgrade to latest version
Workarounds No, users have to upgrade version.
Package
gomod github.com/play-with-docker/play-with-docker (Go)
Affected versions
<= 0.0.2
Patched versions
None
Description
Impact
Give that CORS configuration was not correct, an attacker could use play-with-docker.com as an example, set origin header in http request as evil-play-with-docker.com, it will be echo in response header, which successfully bypass the CORS policy and retrieves basic user information.
Patches
It has been fixed in lastest version, Please upgrade to latest version
Workarounds
No, users have to upgrade version.
References
- GHSA-vq59-5x26-h639
- https://nvd.nist.gov/vuln/detail/CVE-2023-28109
- play-with-docker/play-with-docker@ed82247
marcosnils published to play-with-docker/play-with-docker
Mar 16, 2023
Published by the National Vulnerability Database
Mar 16, 2023
Published to the GitHub Advisory Database
Mar 17, 2023
Reviewed
Mar 17, 2023
Last updated
Mar 17, 2023
Related news
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.