Skip to content

Authorization Bypass Through User-Controlled Key play-with-docker

Moderate severity GitHub Reviewed Published Mar 16, 2023 in play-with-docker/play-with-docker • Updated Mar 17, 2023

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

@marcosnils 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

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

EPSS score

0.209%
(59th percentile)

Weaknesses

CVE ID

CVE-2023-28109

GHSA ID

GHSA-vq59-5x26-h639

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.