Impact
During a security audit of Artifact Hub's code base, security researcher Dejan Zelic 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.
dejanzelic Finder
Impact
During a security audit of Artifact Hub's code base, security researcher Dejan Zelic at OffSec identified a bug in which the
registryIsDockerHubfunction was only checking that the registry domain had thedocker.iosuffix.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.ioand 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.