Skip to content

Artifact Hub arbitrary file read vulnerability

High 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 by using symbolic links in certain kinds of repositories loaded into Artifact Hub, it was possible to read internal files.

Artifact Hub indexes content from a variety of sources, including git repositories. When processing git based repositories, Artifact Hub clones the repository and, depending on the artifact kind, reads some files from it. During this process, in some cases, no validation was done to check if the file was a symbolic link. This made possible to read arbitrary files in the system, potentially leaking sensitive information.

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

High

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.112%
(45th percentile)

Weaknesses

CVE ID

CVE-2023-45823

GHSA ID

GHSA-hmq4-c2r4-5q8h

Source code

Credits

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