User-information disclosure via permissive CORS suffix matching
Published Mar 16, 2023 · Updated Feb 25, 2025
CORS authorization bypass in Docker Play with Docker 0.0.2 and earlier allows remote attackers to read basic user information. The origin validator in handlers/bootstrap.go accepts any Origin value ending in a trusted domain and reflects that origin in access-control response headers. A user must interact with the attacker-controlled origin; successful exploitation exposes basic user information without write or service-interruption impact.
Summary
What happened
CORS authorization bypass in Docker Play with Docker 0.0.2 and earlier allows remote attackers to read basic user information. The origin validator in handlers/bootstrap.go accepts any Origin value ending in a trusted domain and reflects that origin in access-control response headers. A user must interact with the attacker-controlled origin; successful exploitation exposes basic user information without write or service-interruption impact.
The record
- CVE
- CVE-2023-28109
- Published
- Mar 16, 2023
- Updated
- Feb 25, 2025
- Vendor
- Docker
- Product
- Play with Docker
- Classifications
- CWE-639, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 16, 2023CVE publishedPublication date reported by the CVE source.
- Feb 25, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=<= 0.0.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo