dbcve.org
WiresharkApplication

CVE-2015-0564

MEDIUM · 5.0 CVSS v2.0 Published 2015-01-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
Buffer underflow in the ssl_decrypt_record function in epan/dissectors/packet-ssl-utils.c in Wireshark 1.10.x before 1.10.12 and 1.12.x before 1.12.3 allows remote attackers to cause a denial of service (application crash) via a crafted packet that is improperly handled during decryption of an SSL session.

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

A buffer underflow vulnerability exists in Wireshark's ssl_decrypt_record function within the packet-ssl-utils.c dissector. The flaw allows remote attackers to crash the application by sending a specially crafted SSL packet that triggers improper handling during decryption of an SSL session.

MitigationUpgrade Wireshark to version 1.10.12 or later for the 1.10.x branch, or version 1.12.3 or later for the 1.12.x branch to patch this vulnerability.

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:= 1.10.0= 1.10.1= 1.10.2= 1.10.3= 1.10.4= 1.10.5= 1.10.6= 1.10.7= 1.10.8= 1.10.9= 1.10.10= 1.10.11
LinuxOperating system
Affected:= 7
Debian LinuxOperating system
Affected:= 7.0= 8.0
SolarisOperating system
Affected:= 11.2
OpensuseOperating system
Affected:= 13.1= 13.2

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
Authentication
None
Confidentiality
None
Integrity
None
Availability
Partial

AV:N/AC:L/Au:N/C:N/I:N/A:P

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. Determine if Wireshark is installed
    Run 'wireshark --version' or check your package manager for the wireshark package
    Affected if Wireshark is not installed or the command fails, this CVE does not apply
  2. Identify the installed Wireshark version
    Execute 'wireshark --version' and note the version number in the output (for example: 1.10.5)
    Affected if The version falls within 1.10.0 through 1.10.11 inclusive - this indicates the vulnerable version range
  3. Verify SSL/TLS dissector is enabled
    Open Wireshark, go to Analyze > Enabled Protocols, and check if SSL or TLS protocols are enabled; or check the 'ssl' dissector status in the profile
    Affected if SSL/TLS dissector is enabled and the Wireshark version is in the 1.10.0-1.10.11 range, the vulnerability is present
  4. Confirm SSL traffic dissection is in use
    Inspect a capture file or live capture to see if it contains SSL/TLS traffic (look for packets on port 443 or other SSL-based protocols)
    Affected if You are actively dissecting SSL/TLS traffic with a vulnerable Wireshark version

You are affected if Wireshark version 1.10.0 through 1.10.11 is installed AND SSL/TLS dissector is enabled while processing SSL/TLS 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Wireshark to version 1.10.12 or later for the 1.10.x branch, or version 1.12.3 or later for the 1.12.x branch to patch this vulnerability.

Fix this in Wireshark Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-0564 — 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-2015-0564 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