Skip to content

Artifact Hub has Incorrect Docker Hub registry check

Moderate severity GitHub Reviewed Published Oct 19, 2023 in artifacthub/hub • Updated Nov 6, 2023

Package

gomod github.com/artifacthub/hub (Go)

Affected versions

< 1.16.0

Patched versions

1.16.0

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.

References

@tegioz tegioz published to artifacthub/hub Oct 19, 2023
Published to the GitHub Advisory Database Oct 19, 2023
Reviewed Oct 19, 2023
Published by the National Vulnerability Database Oct 19, 2023
Last updated Nov 6, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L

EPSS score

0.053%
(22nd percentile)

Weaknesses

CVE ID

CVE-2023-45821

GHSA ID

GHSA-g6pq-x539-7w4j

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.