Credential theft via suffix-only registry validation
Published Oct 19, 2023 · Updated Sep 12, 2024
Credential exposure in Artifact Hub before 1.16.0 allows remote authenticated users to steal configured Docker Hub credentials. The registryIsDockerHub function treats any registry hostname ending in docker.io as Docker Hub, causing requests to an attacker-owned lookalike registry to include those credentials. Exploitation requires adding a crafted OCI registry, and the exposed access is limited to the permissions granted to the configured credentials.
Summary
What happened
Credential exposure in Artifact Hub before 1.16.0 allows remote authenticated users to steal configured Docker Hub credentials. The registryIsDockerHub function treats any registry hostname ending in docker.io as Docker Hub, causing requests to an attacker-owned lookalike registry to include those credentials. Exploitation requires adding a crafted OCI registry, and the exposed access is limited to the permissions granted to the configured credentials.
The record
- CVE
- CVE-2023-45821
- Published
- Oct 19, 2023
- Updated
- Sep 12, 2024
- Vendor
- Artifact Hub
- Product
- Artifact Hub
- Classifications
- CWE-494, T1583.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 19, 2023CVE publishedPublication date reported by the CVE source.
- Sep 12, 2024Record 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=< 1.16.0
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.
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