VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

tcpdump: vulnerability history, versions and safety

tcpdump is a package in the Debian ecosystem. Vulert records 303 vulnerabilities for it across 19 releases, from Jun 2002 to Apr 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
303 vulnerabilities recorded U303
i
5 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all tcpdump vulnerabilities

Vulert verdict on tcpdump i

Updated on 23 Oct 2026

Careful: 5 of the 303 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 303 vulnerabilities on record across 20 years, none in the last year.

What to do: Plan around the 5 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 303 over 20 years · 0 in the last year i
  • Latest disclosure 07 Apr 2023 i
  • Highest CVSS 9.8 i
  • With no published fix 5 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for tcpdump, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 19 of 19 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2002 4
  • 2003 6
  • 2004 12
  • 2005 8
  • 2007 4
  • 2014 8
  • 2015 8
  • 2017 221
  • 2018 2
  • 2019 27
  • 2020 1
  • 2022 1
  • 2023 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 303 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for tcpdump

The 5 most severe of 303 vulnerabilities recorded for this package

Search all 303 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Buffer Over-Read Vulnerability in tcpdump: CVE-2017-12896 9.8 critical 4.9.2-1 14 Sep 2017
Critical Integer Overflow Vulnerability in tcpdump Package 9.8 critical 3.9.5-3 16 Jul 2007
Critical Buffer Over-read Vulnerability in tcpdump: CVE-2017-12893 9.8 critical 4.9.2-1 14 Sep 2017
Buffer Over-read Vulnerability in tcpdump: CVE-2017-12895 9.8 critical 4.9.2-1 14 Sep 2017
Buffer Over-read Vulnerability in tcpdump: CVE-2017-12894 9.8 critical 4.9.2-1 14 Sep 2017

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About tcpdump

Is tcpdump safe to use?

Vulert records 303 vulnerabilities for tcpdump in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 303 not yet rated. 5 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does tcpdump have?

303 vulnerabilities are recorded for tcpdump in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 303 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new tcpdump vulnerabilities disclosed?

0 vulnerabilities were recorded for tcpdump in the last 12 months, and the oldest entry in this database dates to 18 Jun 2002. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of tcpdump are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor tcpdump for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the tcpdump version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.