Vulnerability in bind9 (UBUNTU-CVE-2016-6170)
Summary
Vulnerability in bind9 (UBUNTU-CVE-2016-6170). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1:9.10.3.dfsg.P4-8ubuntu1.19+esm5 or later.
Original description
The description as published by the source.
ISC BIND through 9.9.9-P1, 9.10.x through 9.10.4-P1, and 9.11.x through 9.11.0b1 allows primary DNS servers to cause a denial of service (secondary DNS server crash) via a large AXFR response, and possibly allows IXFR servers to cause a denial of service (IXFR client crash) via a large IXFR response and allows remote authenticated users to cause a denial of service (primary DNS server crash) via a large UPDATE message.
Source: OSV.dev (Open Source Vulnerabilities) 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 UBUNTU-CVE-2016-6170 has been found in bind9.
Risk of unauthorized operations or information disclosure.
What to do: upgrade bind9 to 1:9.10.3.dfsg.P4-8ubuntu1.19+esm5 or later.
If unsure, ask your IT team or search "bind9 UBUNTU-CVE-2016-6170" on the vendor's site.
UBUNTU-CVE-2016-6170 (bind9)
Attack vector: remote (network-reachable) / no user interaction
Patched: 1:9.10.3.dfsg.P4-8ubuntu1.19+esm5 — 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.
A vulnerability (unclassified) exists in bind9.
Check the vendor advisory for the affected versions of bind9.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1:9.10.3.dfsg.P4-8ubuntu1.19+esm5.
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 'bind9' . 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 'bind9' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
bind9を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade bind9 to 1:9.10.3.dfsg.P4-8ubuntu1.19+esm5ステージング環境で 1:9.10.3.dfsg.P4-8ubuntu1.19+esm5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory ubuntu.com
- report ubuntu.com
- report lists.dns-oarc.net
- report lists.dns-oarc.net
- report lists.dns-oarc.net
- report github.com
- report openwall.com
- report kb.isc.org
- report gitlab.isc.org
- report cve.org