Vulnerability in github.com/goharbor/harbor (CVE-2023-20902)

Summary

Vulnerability in github.com/goharbor/harbor (CVE-2023-20902). Confidential information can be exposed externally. Exploitable via POST /api/v1/jobs. Mitigation: upgrade to 2.8.3 or later.

Original description

The description as published by the source.

A timing condition in Harbor 2.6.x and below, Harbor 2.7.2 and below, Harbor 2.8.2 and below, and Harbor 1.10.17 and below allows an attacker with network access to
create jobs/stop job tasks and retrieve job task information.

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-2023-20902 has been found in github.com/goharbor/harbor.
Attackers can target a specific entry point like POST /api/v1/jobs over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade github.com/goharbor/harbor to 2.8.3 or later.
If unsure, ask your IT team or search "github.com/goharbor/harbor CVE-2023-20902" on the vendor's site.

CVE-2023-20902 (github.com/goharbor/harbor) — CWE-208
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /api/v1/jobs / GET /api/v1/jobs/{job_id} / POST /api/v1/jobs/{job_id} / GET /api/v1/jobs/{job_id}/log
Patched: 2.8.3 — apply immediately
Workaround: Because the jobservice only exposes HTTP service to harbor-core containers, blocking any inbound traffic from the external network to the jobservice container can reduce the risk.
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.

❓ What is the problem

A vulnerability (CWE-208) exists in github.com/goharbor/harbor. Attackers reach the vulnerable code path via POST /api/v1/jobs without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/goharbor/harbor. Attack surface: POST /api/v1/jobs / GET /api/v1/jobs/{job_id} / POST /api/v1/jobs/{job_id} / GET /api/v1/jobs/{job_id}/log.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to 2.8.3.

🛡️ Workaround

Workaround: Because the jobservice only exposes HTTP service to harbor-core containers, blocking any inbound traffic from the external network to the jobservice container can reduce the risk.

🔍 Detection

Search webserver/proxy logs for unusual POST /api/v1/jobs 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

1
Identify 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 し、稼働しているサービス・バージョンを把握する。
2
Hunt for indicators of compromise detect
```
grep 'POST /api/v1/jobs' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'
```
アクセスログで POST /api/v1/jobs への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
3
Apply temporary workaround mitigate
```
Because the jobservice only exposes HTTP service to harbor-core containers, blocking any inbound traffic from the external network to the jobservice container can reduce the risk.
```
パッチが適用されるまでの応急処置として、Because the jobservice only exposes HTTP service to harbor-core containers, blocking any inbound traffic from the external network to the jobservice container can reduce the risk. を実施。回避策の副作用 (機能低下) を確認した上で。
4
Apply patch patch
```
Upgrade github.com/goharbor/harbor to 2.8.3
```
ステージング環境で 2.8.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
5
Post-deployment verification verify
```
Replay attack against POST /api/v1/jobs on staging to confirm patch closes the vector
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

Go github.com/goharbor/harbor

[{"type":"SEMVER","events":[{"introduced":"2.8.0"},{"fixed":"2.8.3"}]}]

Bitnami harbor

[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.10.17"},{"introduced":"2.6.0"},{"fixed":"2.6.5"},{"introduced":"2.7.0"},{"fixed":"2.7.3"},{"introduced":"2.8.0"},{"fixed":"2.8.3"}]}]

References

advisory github.com
package github.com
web nvd.nist.gov
web github.com
web github.com
web github.com
web github.com