Open Redirect in github.com/prometheus/prometheus (CVE-2021-29622)
Summary
Vulnerability in github.com/prometheus/prometheus (CVE-2021-29622). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.27.1 or later.
Original description
The description as published by the source.
Prometheus is an open-source monitoring system and time series database. In 2.23.0, Prometheus changed its default UI to the New ui. To ensure a seamless transition, the URL's prefixed by /new redirect to /. Due to a bug in the code, it is possible for an attacker to craft an URL that can redirect to any other URL, in the /new endpoint. If a user visits a prometheus server with a specially crafted address, they can be redirected to an arbitrary URL. The issue was patched in the 2.26.1 and 2.27.1 releases. In 2.28.0, the /new endpoint will be removed completely. The workaround is to disable access to /new via a reverse proxy in front of Prometheus.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-29622 has been found in github.com/prometheus/prometheus.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/prometheus/prometheus to 2.27.1 or later.
If unsure, ask your IT team or search "github.com/prometheus/prometheus CVE-2021-29622" on the vendor's site.
CVE-2021-29622 (github.com/prometheus/prometheus) — CWE-601
Attack vector: remote (network-reachable) / unauthenticated
Patched: 2.27.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-601) exists in github.com/prometheus/prometheus.
Check the vendor advisory for the affected versions of github.com/prometheus/prometheus.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.27.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/prometheus/prometheus' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/prometheus/prometheus' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/prometheus/prometheusを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/prometheus/prometheus to 2.27.1ステージング環境で 2.27.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory github.com
- web nvd.nist.gov