Vulnerability in inetutils (USN-8387-1)

Summary

vulnerability in inetutils (USN-8387-1). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `2:1.9.2-1ubuntu0.1~esm4` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **USN-8387-1** has been found in inetutils. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade inetutils to **2:1.9.2-1ubuntu0.1~esm4** or later. If unsure, ask your IT team or search "inetutils USN-8387-1" on the vendor's site.

USN-8387-1 (inetutils) — Patched: `2:1.9.2-1ubuntu0.1~esm4` — 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 inetutils.

📍 Affected scope

inetutils — .

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure

🔧 How to fix

Update to **2:1.9.2-1ubuntu0.1~esm4**.

🛡️ 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 'inetutils' .` 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

1
Identify exposure identify
```
grep -r 'inetutils' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `inetutils` を grep し、稼働しているサービス・バージョンを把握する。
6
Apply patch patch
```
Upgrade inetutils to 2:1.9.2-1ubuntu0.1~esm4
```
ステージング環境で 2:1.9.2-1ubuntu0.1~esm4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
7
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

Ubuntu:Pro:14.04:LTS inetutils

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.9.2-1ubuntu0.1~esm4"}]}]

Ubuntu:Pro:16.04:LTS inetutils

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.9.4-1ubuntu0.1~esm6"}]}]

Ubuntu:Pro:18.04:LTS inetutils

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.9.4-3ubuntu0.1+esm5"}]}]

Ubuntu:Pro:20.04:LTS inetutils

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.9.4-11ubuntu0.2+esm4"}]}]

Ubuntu:Pro:22.04:LTS inetutils

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:2.2-2ubuntu0.2+esm1"}]}]

Ubuntu:24.04:LTS inetutils

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:2.5-3ubuntu4.2"}]}]

Ubuntu:25.10 inetutils

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:2.6-1ubuntu3.2"}]}]

Ubuntu:26.04:LTS inetutils

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:2.7-2ubuntu1.1"}]}]

References

advisory https://ubuntu.com/security/notices/USN-8387-1
report https://ubuntu.com/security/CVE-2026-28372
report https://ubuntu.com/security/CVE-2026-32746
report https://ubuntu.com/security/CVE-2026-32772