Vulnerability in github.com/goharbor/harbor (CVE-2024-22261)
Summary
Vulnerability in github.com/goharbor/harbor (CVE-2024-22261). Risk of unauthorized operations or information disclosure. Exploitable via GET /api/v2.0/projects/{project_name}/repositories/{repository_name}/artifacts/{refer. Mitigation: upgrade to 2.10.2 or later.
Original description
The description as published by the source.
SQL-Injection in Harbor allows priviledge users to leak the task IDs
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-2024-22261 has been found in github.com/goharbor/harbor.
Attackers can target a specific entry point like GET /api/v2.0/projects/{project_name}/repositories/{repository_name}/artifacts/{refer over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/goharbor/harbor to 2.10.2 or later.
If unsure, ask your IT team or search "github.com/goharbor/harbor CVE-2024-22261" on the vendor's site.
CVE-2024-22261 (github.com/goharbor/harbor) — CWE-566
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/v2.0/projects/{project_name}/repositories/{repository_name}/artifacts/{refer
Patched: 2.10.2 — apply immediately
Workaround: There is no workaround for this issue.
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-566) exists in github.com/goharbor/harbor. Attackers reach the vulnerable code path via GET /api/v2.0/projects/{project_name}/repositories/{repository_name}/artifacts/{refer.
Check the vendor advisory for the affected versions of github.com/goharbor/harbor. Attack surface: GET /api/v2.0/projects/{project_name}/repositories/{repository_name}/artifacts/{refer.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.10.2.
Workaround: There is no workaround for this issue.
Search webserver/proxy logs for unusual GET /api/v2.0/projects/{project_name}/repositories/{repository_name}/artifacts/{refer requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/goharbor/harbor' . 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/goharbor/harbor' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/goharbor/harborを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /api/v2.0/projects/{project_name}/repositories/{repository_name}/artifacts/{refer' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/v2.0/projects/{project_name}/repositories/{repository_name}/artifacts/{referへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply temporary workaround mitigate
There is no workaround for this issue.パッチが適用されるまでの応急処置として、There is no workaround for this issue. を実施。回避策の副作用 (機能低下) を確認した上で。
-
4Apply patch patch
Upgrade github.com/goharbor/harbor to 2.10.2ステージング環境で 2.10.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
5Post-deployment verification verify
Replay attack against GET /api/v2.0/projects/{project_name}/repositories/{repository_name}/artifacts/{refer on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web pkg.go.dev
- web github.com