Kurz gesagt
- CVE-2023-45821 ist eine Schwachstelle (MITTEL (CVSS 6.3)) in github.com/artifacthub/hub, hub (artifacthub).
- Wahrscheinlichkeit einer Ausnutzung in den nächsten 30 Tagen (EPSS): 0.24%, höher als bei 15.6% aller Schwachstellen.
- Abhilfe: auf 1.16.0 oder neuer aktualisieren.
Description
Impact
During a security audit of Artifact Hub's code base, a security researcher at OffSec 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.
Patches
This issue has been resolved in version 1.16.0.
NVD description
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.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free