dbcve.org
WiresharkApplication

CVE-2018-14369

HIGH · 7.5 CVSS v3.0 Published 2018-07-19
Fix available
A fix is available. Upgrade to after 2.6.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.2.15, the HTTP2 dissector could crash. This was addressed in epan/dissectors/packet-http2.c by verifying that header data was found before proceeding to header decompression.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The HTTP2 dissector in Wireshark versions 2.6.0-2.6.1, 2.4.0-2.4.7, and 2.2.0-2.2.15 could crash when processing malformed HTTP2 packets. The vulnerability stems from the dissector proceeding to header decompression without first verifying that valid header data exists, likely causing a NULL pointer dereference or similar memory access error leading to a crash.

MitigationUpgrade Wireshark to version 2.6.2, 2.4.8, 2.2.16 or later. Until upgraded, avoid opening untrusted packet capture files or monitoring live traffic with Wireshark where malicious HTTP2 packets may be present.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WiresharkApplication
Affected:>= 2.2.0, <= 2.2.15>= 2.4.0, <= 2.4.7>= 2.6.0, <= 2.6.1
Debian LinuxOperating system
Affected:= 8.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Wireshark version
    Run 'wireshark --version' or 'tshark --version' from the command line
    Affected if Version is 2.6.0 through 2.6.1, 2.4.0 through 2.4.7, or 2.2.0 through 2.2.15
  2. Confirm HTTP2 dissector is present
    Start Wireshark and go to Help > About Wireshark > Plugins tab, or run 'tshark -G dissectors' and search for http2 in the output
    Affected if The http2 dissector is loaded (present by default in affected versions)
  3. Identify capture file or live traffic exposure
    Determine if you open pcap files or capture live network traffic that may contain HTTP2 packets
    Affected if You open pcap files or monitor live traffic with Wireshark where HTTP2 traffic may be present

You are affected if your Wireshark version falls within 2.2.0-2.2.15, 2.4.0-2.4.7, or 2.6.0-2.6.1 and you process pcap files or live captures containing HTTP2 traffic.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 2.6.1
Interim mitigation

Upgrade Wireshark to version 2.6.2, 2.4.8, 2.2.16 or later. Until upgraded, avoid opening untrusted packet capture files or monitoring live traffic with Wireshark where malicious HTTP2 packets may be present.

Fix this in Wireshark Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-14369 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-14369 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data