← Back
USN-8523-1
Vulnerability in libsoup2.4 (USN-8523-1)
Summary
vulnerability in libsoup2.4 (USN-8523-1). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `2.52.2-1ubuntu0.3+esm6` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **USN-8523-1** has been found in libsoup2.4.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade libsoup2.4 to **2.52.2-1ubuntu0.3+esm6** or later.
If unsure, ask your IT team or search "libsoup2.4 USN-8523-1" on the vendor's site.
USN-8523-1 (libsoup2.4) —
Patched: `2.52.2-1ubuntu0.3+esm6` — 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.
❓ What is the problem
**A vulnerability** (unclassified) exists in libsoup2.4.
📍 Affected scope
libsoup2.4 — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.52.2-1ubuntu0.3+esm6**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'libsoup2.4' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'libsoup2.4' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `libsoup2.4` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade libsoup2.4 to 2.52.2-1ubuntu0.3+esm6ステージング環境で 2.52.2-1ubuntu0.3+esm6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Ubuntu:Pro:16.04:LTS
libsoup2.4
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.52.2-1ubuntu0.3+esm6"}]}]
Ubuntu:Pro:18.04:LTS
libsoup2.4
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.62.1-1ubuntu0.4+esm7"}]}]
Ubuntu:Pro:20.04:LTS
libsoup2.4
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.70.0-1ubuntu0.5+esm2"}]}]
Ubuntu:22.04:LTS
libsoup2.4
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.74.2-3ubuntu0.7"}]}]
Ubuntu:24.04:LTS
libsoup2.4
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.74.3-6ubuntu1.7"}]}]
Ubuntu:25.10
libsoup2.4
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.74.3-10.1ubuntu4.1"}]}]
Ubuntu:Pro:26.04:LTS
libsoup2.4
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.74.3-10.1ubuntu5+esm1"}]}]