Vulnerability in libnbd
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 DEBIAN-CVE-2019-14842 has been found in libnbd.
Successful exploitation can lead to full system takeover.
What to do: upgrade libnbd to 1.0.3-1 or later.
If unsure, ask your IT team or search "libnbd DEBIAN-CVE-2019-14842" on the vendor's site.
DEBIAN-CVE-2019-14842 (libnbd)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.0.3-1 — 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 libnbd.
Check the vendor advisory for the affected versions of libnbd.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 1.0.3-1.
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 'libnbd' . 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
-
1
Identify exposureidentify
grep -r 'libnbd' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
libnbdを grep し、稼働しているサービス・バージョンを把握する。 -
2
Apply patchpatch
Upgrade libnbd to 1.0.3-1ステージング環境で 1.0.3-1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3
Post-deployment verificationverify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
| Ecosystem | Package | Affected | Fixed |
|---|---|---|---|
| Debian:12 | libnbd |
< 1.0.3-1 |
1.0.3-1 |
| Debian:13 | libnbd |
< 1.0.3-1 |
1.0.3-1 |
| Debian:14 | libnbd |
< 1.0.3-1 |
1.0.3-1 |
Original description The description as published by the source.
Structured reply is a feature of the newstyle NBD protocol allowing the server to send a reply in chunks. A bounds check which was supposed to test for chunk offsets smaller than the beginning of the request did not work because of signed/unsigned confusion. If one of these chunks contains a negative offset then data under control of the server is written to memory before the read buffer supplied by the client. If the read buffer is located on the stack then this allows the stack return address from nbd_pread() to be trivially modified, allowing arbitrary code execution under the control of the server. If the buffer is located on the heap then other memory objects before the buffer can be overwritten, which again would usually lead to arbitrary code execution.
Source: OSV.dev (Open Source Vulnerabilities) OSV
References
- advisory security-tracker.debian.org