Vulnerability in net-tools (DEBIAN-CVE-2025-46836)

Summary

vulnerability in net-tools (DEBIAN-CVE-2025-46836). Risk of unauthorized operations or information disclosure. Exploitable via ``interface.c``. Mitigation: upgrade to `1.60+git20181103.0eebece-1+deb11u2` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **DEBIAN-CVE-2025-46836** has been found in net-tools. Attackers can target a specific entry point like ``interface.c`` over the network to misuse the product. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade net-tools to **1.60+git20181103.0eebece-1+deb11u2** or later. If unsure, ask your IT team or search "net-tools DEBIAN-CVE-2025-46836" on the vendor's site.

DEBIAN-CVE-2025-46836 (net-tools) — Attack surface: `interface.c` Patched: `1.60+git20181103.0eebece-1+deb11u2` — 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 net-tools. Attackers reach the vulnerable code path via ``interface.c`` without authentication.

📍 Affected scope

net-tools — . Attack surface: `interface.c`.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure

🔧 How to fix

Update to **1.60+git20181103.0eebece-1+deb11u2**.

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

Affected packages

Debian:11 net-tools

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.60+git20181103.0eebece-1+deb11u2"}]}]

Debian:12 net-tools

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.10-0.1+deb12u1"}]}]

Debian:13 net-tools

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.10-1.2"}]}]

Debian:14 net-tools