SSRF (Server-Side Request Forgery) in label-studio (CVE-2022-36551)
Summary
SSRF in label-studio (CVE-2022-36551). Confidential information can be exposed externally. Mitigation: upgrade to 1.5.0.post0 or later.
Original description
The description as published by the source.
A Server Side Request Forgery (SSRF) in the Data Import module in Heartex - Label Studio Community Edition versions 1.5.0 and earlier allows an authenticated user to access arbitrary files on the system. Furthermore, self-registration is enabled by default in these versions of Label Studio enabling a remote attacker to create a new account and then exploit the SSRF.
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-2022-36551 has been found in label-studio.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade label-studio to 1.5.0.post0 or later.
If unsure, ask your IT team or search "label-studio CVE-2022-36551" on the vendor's site.
CVE-2022-36551 (label-studio) — CWE-918 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.5.0.post0 — 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.
SSRF (CWE-918) exists in label-studio.
Check the vendor advisory for the affected versions of label-studio.
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.
Update to 1.5.0.post0.
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 'label-studio' . 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 'label-studio' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
label-studioを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade label-studio to 1.5.0.post0ステージング環境で 1.5.0.post0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- patch github.com
- web heartex.com
- web labelstud.io
- web packetstormsecurity.com