VYPR
Unrated severityNVD Advisory· Published Oct 3, 2019· Updated Dec 3, 2025

CVE-2018-16452

CVE-2018-16452

Description

Stack exhaustion in tcpdump's SMB parser (smb_fdata) via recursion leads to denial of service; fixed in version 4.9.3.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Stack exhaustion in tcpdump's SMB parser (smb_fdata) via recursion leads to denial of service; fixed in version 4.9.3.

Vulnerability

The SMB parser in tcpdump before version 4.9.3 contains a stack exhaustion vulnerability in the smb_fdata() function within smbutil.c. This occurs due to uncontrolled recursion when processing crafted SMB packets, leading to a crash. The issue affects all versions prior to 4.9.3, as confirmed by the Debian security advisory [4].

Exploitation

An attacker can exploit this vulnerability by sending a specially crafted SMB packet to a target system that is running an affected version of tcpdump and capturing network traffic. No authentication or special privileges are required; the attacker only needs the ability to transmit packets visible to the target's tcpdump instance. The malicious packet triggers deep recursion in smb_fdata(), consuming the stack space and causing the process to crash.

Impact

Successful exploitation results in a denial of service (crash) of the tcpdump process. There is no indication of arbitrary code execution or information disclosure; the primary impact is loss of availability for network monitoring and analysis tools relying on tcpdump.

Mitigation

The vulnerability is fixed in tcpdump version 4.9.3. For Debian systems, updates have been released for the oldstable (stretch) and stable (buster) distributions as per DSA-4547-1 [4]. Users are advised to upgrade to the latest available patched version. If upgrading is not immediately possible, avoiding the capture or parsing of untrusted SMB traffic may reduce risk.

AI Insight generated on May 25, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

11

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

16

News mentions

0

No linked articles in our index yet.