Artifact Hub allows unsafe rego built-in

中 5.3CVE-2023-45822 · GHSA-9pc8-m4vp-ggvf · GO-2023-2134 · 19/10/2023 公開 · 17/06/2026 更新

要点

CVE-2023-45822 は github.com/artifacthub/hub, hub (artifacthub) に影響する深刻度「中」 (CVSS 5.3) の脆弱性です。
今後30日間に悪用される確率（EPSS）：0.64%（全脆弱性の 50.8% より高い）。
対処：1.16.0 以降に更新してください。

パッケージ	影響を受けるバージョン	修正済みバージョン
github.com/artifacthub/hub Go	`< 1.16.0`	`1.16.0`
hub artifacthub	`< 1.16.0`	`1.16.0`

概要

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.

NVD の説明

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 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. This issue has been resolved in version `1.16.0`. Users are advised to upgrade. There are no known workarounds for this vulnerability.