Skip to content
Fencer Intel
medium 5.0

CVE-2015-3815 json

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 leng…

published 11y ago modified 4mo ago also EUVD-2015-3851

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.6%
EPSS 2.6% chance of exploitation in 30 days, percentile 85%
public exploits
0
none known

Summary

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 length of the payload, which allows remote attackers to cause a denial of service (out-of-bounds read and application crash) via a packet with a crafted payload, as demonstrated by a length of zero, a different vulnerability than CVE-2015-3906.

Patch / fix

  • wireshark Debian 14, Debian 13, Debian 12 1.12.5+g5819e5b-1

debian advisories DEBIAN-CVE-2015-3815

  • wireshark openSUSE Tumbleweed 2.2.2-1.1

opensuse advisories openSUSE-SU-2024:10199-1

Is CVE-2015-3815 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2015-3815 updated cvss 4.3

wireshark: Android Logcat file parser crash (wnpa-sec-2015-18)

  • Red Hat Enterprise Linux 5 wireshark Red Hat Enterprise Linux 6 wireshark, wireshark-gnome Red Hat Enterprise Linux 7 wireshark, wireshark-gnome
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.60% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.