CVE-2015-3813: The fragment_add_work function in epan/reassemble.c in the packet-reassembly feature in Wireshark 1.12.x before 1.12.5 does not properly…
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 2.7% (FIRST EPSS); higher than 86.5% of all records.
- No special conditions are required; it is repeatable.
- Fixed version: wireshark (Debian:12) 1.12.5+g5819e5b-1; wireshark (Debian:8) 1.12.1+g01b65bf-4+deb8u1; wireshark (Red Hat:enterprise_linux:6::client) 0:1.8.10-25.el6.
Low priority for now. Upgrade to wireshark (Debian:12) 1.12.5+g5819e5b-1; wireshark (Debian:8) 1.12.1+g01b65bf-4+deb8u1; wireshark (Red Hat:enterprise_linux:6::client) 0:1.8.10-25.el6 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The fragment_add_work function in epan/reassemble.c in the packet-reassembly feature in Wireshark 1.12.x before 1.12.5 does not properly determine the defragmentation state in a case of an insufficient snapshot length, which allows remote attackers to cause a denial of service (memory consumption) via a crafted packet.
- Published
- May 26, 2015
- Updated
- Jun 16, 2026
- EPSS
- 2.7% · 86th percentile
- CWE
- CWE-399
Report tools
Action score
21
Low priority for now.
- CVSS
- 20 / 40 · 5.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.7%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| wireshark | wireshark | cpe:2.3:a:wireshark:wireshark |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- wireshark wireshark1.12.0
- wireshark wireshark1.12.1
- wireshark wireshark1.12.2
- wireshark wireshark1.12.3
- wireshark wireshark1.12.4
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | wireshark | before 1.12.5+g5819e5b-1 | 1.12.5+g5819e5b-1 |
| Debian:8 | wireshark | before 1.12.1+g01b65bf-4+deb8u1 | 1.12.1+g01b65bf-4+deb8u1 |
| Red Hat:enterprise_linux:6::client | wireshark | before 0:1.8.10-25.el6 | 0:1.8.10-25.el6 |
| Red Hat:enterprise_linux:6::client | wireshark-debuginfo | before 0:1.8.10-25.el6 | 0:1.8.10-25.el6 |
| Red Hat:enterprise_linux:6::client | wireshark-devel | before 0:1.8.10-25.el6 | 0:1.8.10-25.el6 |
| Red Hat:enterprise_linux:6::client | wireshark-gnome | before 0:1.8.10-25.el6 | 0:1.8.10-25.el6 |
| Red Hat:enterprise_linux:7::client | wireshark | before 0:1.10.14-7.el7 | 0:1.10.14-7.el7 |
| Red Hat:enterprise_linux:7::client | wireshark-debuginfo | before 0:1.10.14-7.el7 | 0:1.10.14-7.el7 |
| Red Hat:enterprise_linux:7::client | wireshark-devel | before 0:1.10.14-7.el7 | 0:1.10.14-7.el7 |
| Red Hat:enterprise_linux:7::client | wireshark-gnome | before 0:1.10.14-7.el7 | 0:1.10.14-7.el7 |
| SUSE:Linux Enterprise Desktop 12 | wireshark | before 1.10.14-12.1 | 1.10.14-12.1 |
| SUSE:Linux Enterprise Desktop 12 | wireshark | before 1.12.7-15.1 | 1.12.7-15.1 |
| SUSE:Linux Enterprise Software Development Kit 11 SP3 | wireshark | before 1.12.7-0.5.3 | 1.12.7-0.5.3 |
Same product
wireshark: all recordsOther highest-scoring records for the same primary product.
- CVE-2010-0304Multiple buffer overflows in the LWRES dissector in Wireshark 0.9.15 through 1.0.10 and 1.2.0 through 1.2.5 allow remote attackers to cause…52Plan
- CVE-2014-2299Buffer overflow in the mpeg_read function in wiretap/mpeg.c in the MPEG parser in Wireshark 1.8.x before 1.8.13 and 1.10.x before 1.10.6…51Plan
- CVE-2011-1591Stack-based buffer overflow in the DECT dissector in epan/dissectors/packet-dect.c in Wireshark 1.4.x before 1.4.5 allows remote attackers…50Plan
Published before and after this one in the same product
- ← EarlierCVE-2015-3811May 26, 2015 · epan/dissectors/packet-wcp.c in the WCP dissector in Wireshark 1.10.x before 1.10.14 and 1.12.x before 1.12.5 improperly refers to…21Monitor
- ← EarlierCVE-2015-3812May 26, 2015 · Multiple memory leaks in the x11_init_protocol function in epan/dissectors/packet-x11.c in the X11 dissector in Wireshark 1.10.x before…32Monitor
- Later →CVE-2015-3815May 26, 2015 · The detect_version function in wiretap/logcat.c in the Android Logcat file parser in Wireshark 1.12.x before 1.12.5 does not check the…21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:wireshark | 1.12.5+g5819e5b-1 · Debian:12 | Package registry (OSV) |
| red hat:wireshark | 0:1.10.14-7.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:wireshark-debuginfo | 0:1.10.14-7.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:wireshark-devel | 0:1.10.14-7.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:wireshark-gnome | 0:1.10.14-7.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| suse:wireshark | 1.10.14-12.1 · SUSE:Linux Enterprise Desktop 12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- P · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- P
Weakness class (CWE)
CWE-399 · Resource Management ErrorsCVSS vector
AV:N/AC:L/Au:N/C:N/I:N/A:P
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- www.debian.org/security/2015/dsa-3277
- www.oracle.com/technetwork/topics/security/linuxbulletinoct2015-2719645.html
- www.securityfocus.com/bid/74633
- www.wireshark.org/security/wnpa-sec-2015-16.html
- bugs.wireshark.org/bugzilla/show_bug.cgi?id=11129
- code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=c35f2ccb4433718416551cc7a85afb0860529d57
- security.gentoo.org/glsa/201510-03
Vendor advisories and official records. Exploit/PoC links are deliberately left out.