You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
CVE-2023-45821 references github.com/artifacthub/hub, which may be a Go module.
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 thedocker.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 withdocker.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 onartifacthub.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 version1.16.0
. Users are advised to upgrade. There are no known workarounds for this vulnerability.References:
Cross references:
No existing reports found with this module or alias.
See doc/triage.md for instructions on how to triage this report.
The text was updated successfully, but these errors were encountered: