← Back
USN-5119-1
Vulnerability in libcaca (USN-5119-1)
Summary
vulnerability in libcaca (USN-5119-1). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `0.99.beta18-1ubuntu5.1+esm2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **USN-5119-1** has been found in libcaca.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade libcaca to **0.99.beta18-1ubuntu5.1+esm2** or later.
If unsure, ask your IT team or search "libcaca USN-5119-1" on the vendor's site.
USN-5119-1 (libcaca) —
Patched: `0.99.beta18-1ubuntu5.1+esm2` — 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 libcaca.
📍 Affected scope
libcaca — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.99.beta18-1ubuntu5.1+esm2**.
🛡️ 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 'libcaca' .` 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 'libcaca' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `libcaca` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade libcaca to 0.99.beta18-1ubuntu5.1+esm2ステージング環境で 0.99.beta18-1ubuntu5.1+esm2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Ubuntu:Pro:14.04:LTS
libcaca
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.99.beta18-1ubuntu5.1+esm2"}]}]
Ubuntu:Pro:16.04:LTS
libcaca
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.99.beta19-2ubuntu0.16.04.2+esm1"}]}]
Ubuntu:18.04:LTS
libcaca
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.99.beta19-2ubuntu0.18.04.3"}]}]
Ubuntu:20.04:LTS
libcaca
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.99.beta19-2.1ubuntu1.20.04.2"}]}]