Skip to content

Artifact Hub allows unsafe rego built-in

Low 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 a default unsafe rego built-in was allowed to be used when defining authorization policies.

Artifact Hub includes a fine-grained authorization mechanism that allows organizations to define what actions can be performed by their members. It is based on customizable authorization policies that are enforced by the Open Policy Agent. Policies are written using rego and their data files are expected to be json documents. By default, rego allows policies to make HTTP requests, which can be abused to send requests to internal resources and forward the responses to an external entity. In the context of Artifact Hub, this capability should have been disabled.

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

Low

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
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
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:H/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS score

0.101%
(43rd percentile)

Weaknesses

CVE ID

CVE-2023-45822

GHSA ID

GHSA-9pc8-m4vp-ggvf

Source code

Credits

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