Debian LinuxOperating system · Debian
CVE-2013-2487
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 · uneditedepan/dissectors/packet-reload.c in the REsource LOcation And Discovery (aka RELOAD) dissector in Wireshark 1.8.x before 1.8.6 uses incorrect integer data types, which allows remote attackers to cause a denial of service (infinite loop) via crafted integer values in a packet, related to the (1) dissect_icecandidates, (2) dissect_kinddata, (3) dissect_nodeid_list, (4) dissect_storeans, (5) dissect_storereq, (6) dissect_storeddataspecifier, (7) dissect_fetchreq, (8) dissect_findans, (9) dissect_diagnosticinfo, (10) dissect_diagnosticresponse, (11) dissect_reload_messagecontents, and (12) dissect_reload_message functions, a different vulnerability than CVE-2013-2486.
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 confidenceThe RELOAD (Resource Location And Discovery) dissector in Wireshark 1.8.x before 1.8.6 uses incorrect integer data types in 12 different functions, allowing attackers to trigger infinite loops via crafted packets with specially formatted integer values.
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
Debian LinuxOperating system
= 7.0
WiresharkApplication
= 1.8.0= 1.8.1= 1.8.2= 1.8.3= 1.8.4= 1.8.5= 11.4= 12.1= 12.2= 12.3CVSS 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
- Complete
AV:N/AC:L/Au:N/C:N/I:N/A:C
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Wireshark installationRun 'wireshark --version' or check package manager (dpkg -l | grep wireshark, rpm -qa | grep wireshark)Affected if Wireshark is not installed - not affected
-
Determine installed Wireshark versionExecute 'wireshark --version' and note the version number in the output (e.g., Wireshark 1.8.5)Affected if Version is 1.8.0, 1.8.1, 1.8.2, 1.8.3, 1.8.4, or 1.8.5 - potentially affected
-
Confirm RELOAD dissector presenceCheck dissector files: look for 'packet-relay.c' or 'reload.so' in Wireshark plugins directory, or run 'tshark -G dissectors' and grep for RELOADAffected if RELOAD dissector exists in the installation - vulnerability is present in code
-
Test RELOAD dissector loadsOpen Wireshark, go to Analyze -> Enabled Protocols, search for RELOAD and verify it can be enabledAffected if RELOAD protocol is listed and enable-able - dissector is active and vulnerable
You are affected if Wireshark version 1.8.0-1.8.5 is installed and the RELOAD dissector is present and loadable in your environment.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade Wireshark to version 1.8.6 or later. Until then, avoid opening untrusted pcap files or disable the RELOAD dissector.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,688.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2487 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-2487 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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