Incorrect Docker Hub registry check in Artifact Hub
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Code execution
- Confidentiality · integrity · availability
- Low · Low · Low
- Fix status
- Fixed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA and GitHub. Impact type from CWE-494.
Summary
Artifact Hub is a web-based application that enables finding, installing, and publishing packages and configurations for CNCF projects. During a security audit of Artifact Hub's code base a security researcher identified a bug in which the `registryIsDockerHub` function was only checking that the registry domain had the `docker.io` suffix. Artifact Hub allows providing some Docker credentials that are used to increase the rate limit applied when interacting with the Docker Hub registry API to read publicly available content. Due to the incorrect check described above, it'd be possible to hijack those credentials by purchasing a domain which ends with `docker.io` and deploying a fake OCI registry on it. <https://artifacthub.io/> uses some credentials that only have permissions to read public content available in the Docker Hub. However, even though credentials for private repositories (disabled on `artifacthub.io`) are handled in a different way, other Artifact Hub deployments could have been using them for a different purpose. This issue has been resolved in version `1.16.0`. Users are advised to upgrade. There are no known workarounds for this vulnerability.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| artifacthub | hub | before 1.16.0 | 1.16.0 | Patch available | CNA |
| — | github.com/artifacthub/hub (Go) | before 1.16.0 | 1.16.0 | Patch available | GHSA-g6pq-x539-7w4j |
- hub Vendorartifacthub Affected before 1.16.0 Fixed in 1.16.0 Patch available CNA
- github.com/artifacthub/hub (Go) Vendor— Affected before 1.16.0 Fixed in 1.16.0 Patch available GHSA-g6pq-x539-7w4j
CPE configurations NVD · 1
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:artifacthub:hub:*:*:*:*:*:*:*:* | before 1.16.0 | Vulnerable | artifacthub |
- cpe:2.3:a:artifacthub:hub:*:*:*:*:*:*:*:* Versions before 1.16.0 Vulnerable ·artifacthub
Remediation
- Fix · CNA hub (artifacthub) Fixed in 1.16.0
- Fix · GHSA-g6pq-x539-7w4j github.com/artifacthub/hub (Go) Fixed in 1.16.0 Advisory →
Timeline
- 2026-10-02 Threatist record created from CVE-2023-45821
- 2026-10-03 Alias added: GHSA-g6pq-x539-7w4j
References
More artifacthub Hub vulnerabilities
- TI-2023-24583 Arbitrary file read in Artifact Hub CVSS 3.1HIGH 7.5
- TI-2023-24582 Unsafe rego built-in allowed in Artifact Hub CVSS 3.1MEDIUM 5.3
Sources
- CVE-2023-45821 · CVE Program
- CVE-2023-45821 · NVD
- FIRST EPSS
- GHSA-g6pq-x539-7w4j · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences