CVE-2015-8735 : Detail

CVE-2015-8735

5.5
/
Medium
A03-Injection
0.71%V3
Local
2016-01-04
01h00 +00:00
2016-12-05
13h57 +00:00
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

The get_value function in epan/dissectors/packet-btatt.c in the Bluetooth Attribute (aka BT ATT) dissector in Wireshark 2.0.x before 2.0.1 uses an incorrect integer data type, which allows remote attackers to cause a denial of service (invalid write operation and application crash) via a crafted packet.

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-20 Improper Input Validation
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

Metrics

Metrics Score Severity CVSS Vector Source
V3.0 5.5 MEDIUM CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Base: Exploitabilty Metrics

The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component.

Attack Vector

This metric reflects the context by which vulnerability exploitation is possible.

Local

A vulnerability exploitable with Local access means that the vulnerable component is not bound to the network stack, and the attacker's path is via read/write/execute capabilities. In some cases, the attacker may be logged in locally in order to exploit the vulnerability, otherwise, she may rely on User Interaction to execute a malicious file.

Attack Complexity

This metric describes the conditions beyond the attacker's control that must exist in order to exploit the vulnerability.

Low

Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.

Privileges Required

This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.

None

The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.

User Interaction

This metric captures the requirement for a user, other than the attacker, to participate in the successful compromise of the vulnerable component.

Required

Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited. For example, a successful exploit may only be possible during the installation of an application by a system administrator.

Base: Scope Metrics

An important property captured by CVSS v3.0 is the ability for a vulnerability in one software component to impact resources beyond its means, or privileges.

Scope

Formally, Scope refers to the collection of privileges defined by a computing authority (e.g. an application, an operating system, or a sandbox environment) when granting access to computing resources (e.g. files, CPU, memory, etc). These privileges are assigned based on some method of identification and authorization. In some cases, the authorization may be simple or loosely controlled based upon predefined rules or standards. For example, in the case of Ethernet traffic sent to a network switch, the switch accepts traffic that arrives on its ports and is an authority that controls the traffic flow to other switch ports.

Unchanged

An exploited vulnerability can only affect resources managed by the same authority. In this case the vulnerable component and the impacted component are the same.

Base: Impact Metrics

The Impact metrics refer to the properties of the impacted component.

Confidentiality Impact

This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.

None

There is no loss of confidentiality within the impacted component.

Integrity Impact

This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.

None

There is no loss of integrity within the impacted component.

Availability Impact

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.

High

There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Temporal Metrics

The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence that one has in the description of a vulnerability.

Environmental Metrics

nvd@nist.gov
V2 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P nvd@nist.gov

EPSS

EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.

EPSS Score

The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.

EPSS Percentile

The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.

Exploit information

Exploit Database EDB-ID : 38998

Publication date : 2015-12-15 23h00 +00:00
Author : Google Security Research
EDB Verified : Yes

Source: https://code.google.com/p/google-security-research/issues/detail?id=653 The following SIGSEGV crash due to an invalid memory write can be observed in an ASAN build of Wireshark (current git master), by feeding a malformed file to tshark ("$ ./tshark -nVxr /path/to/file"): --- cut --- ==31799==ERROR: AddressSanitizer: SEGV on unknown address 0x00000000fff3 (pc 0x7f538efe2e98 bp 0x7ffff1414290 sp 0x7ffff1413a18 T0) #0 0x7f538efe2e97 /build/buildd/eglibc-2.19/string/../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:1812 #1 0x4aaeac in __asan_memcpy llvm/projects/compiler-rt/lib/asan/asan_interceptors.cc:393 #2 0x7f53989ebdee in get_value wireshark/epan/dissectors/packet-btatt.c:6021:9 #3 0x7f53989cd2a1 in dissect_btatt wireshark/epan/dissectors/packet-btatt.c:6434:40 #4 0x7f539841bcc1 in call_dissector_through_handle wireshark/epan/packet.c:616:8 #5 0x7f539840e5ea in call_dissector_work wireshark/epan/packet.c:691:9 #6 0x7f539840ddbd in dissector_try_uint_new wireshark/epan/packet.c:1148:9 #7 0x7f5398abde89 in dissect_btl2cap wireshark/epan/dissectors/packet-btl2cap.c:2217:26 #8 0x7f539841bcc1 in call_dissector_through_handle wireshark/epan/packet.c:616:8 #9 0x7f539840e5ea in call_dissector_work wireshark/epan/packet.c:691:9 #10 0x7f53984182be in call_dissector_only wireshark/epan/packet.c:2662:8 #11 0x7f5398409ccf in call_dissector_with_data wireshark/epan/packet.c:2675:8 #12 0x7f5398add99f in dissect_btle wireshark/epan/dissectors/packet-btle.c:760:21 #13 0x7f539841bcc1 in call_dissector_through_handle wireshark/epan/packet.c:616:8 #14 0x7f539840e5ea in call_dissector_work wireshark/epan/packet.c:691:9 #15 0x7f53984182be in call_dissector_only wireshark/epan/packet.c:2662:8 #16 0x7f5398409ccf in call_dissector_with_data wireshark/epan/packet.c:2675:8 #17 0x7f5398ae089b in dissect_btle_rf wireshark/epan/dissectors/packet-btle_rf.c:221:27 #18 0x7f539841bcc1 in call_dissector_through_handle wireshark/epan/packet.c:616:8 #19 0x7f539840e5ea in call_dissector_work wireshark/epan/packet.c:691:9 #20 0x7f539840ddbd in dissector_try_uint_new wireshark/epan/packet.c:1148:9 #21 0x7f53989467c5 in dissect_bluetooth wireshark/epan/dissectors/packet-bluetooth.c:1748:10 #22 0x7f539841bcc1 in call_dissector_through_handle wireshark/epan/packet.c:616:8 #23 0x7f539840e5ea in call_dissector_work wireshark/epan/packet.c:691:9 #24 0x7f539840ddbd in dissector_try_uint_new wireshark/epan/packet.c:1148:9 #25 0x7f539911d5f6 in dissect_frame wireshark/epan/dissectors/packet-frame.c:500:11 #26 0x7f539841bcc1 in call_dissector_through_handle wireshark/epan/packet.c:616:8 #27 0x7f539840e5ea in call_dissector_work wireshark/epan/packet.c:691:9 #28 0x7f53984182be in call_dissector_only wireshark/epan/packet.c:2662:8 #29 0x7f5398409ccf in call_dissector_with_data wireshark/epan/packet.c:2675:8 #30 0x7f539840933b in dissect_record wireshark/epan/packet.c:501:3 #31 0x7f53983b73c9 in epan_dissect_run_with_taps wireshark/epan/epan.c:373:2 #32 0x5264eb in process_packet wireshark/tshark.c:3728:5 #33 0x51f960 in load_cap_file wireshark/tshark.c:3484:11 #34 0x515daf in main wireshark/tshark.c:2197:13 AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV /build/buildd/eglibc-2.19/string/../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:1812 ==31799==ABORTING --- cut --- The crash was reported at https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11817. Attached are two files which trigger the crash. Proof of Concept: https://gitlab.com/exploit-database/exploitdb-bin-sploits/-/raw/main/bin-sploits/38998.zip

Products Mentioned

Configuraton 0

Wireshark>>Wireshark >> Version 2.0.0

References

http://www.securityfocus.com/bid/79382
Tags : vdb-entry, x_refsource_BID
https://security.gentoo.org/glsa/201604-05
Tags : vendor-advisory, x_refsource_GENTOO
http://www.securitytracker.com/id/1034551
Tags : vdb-entry, x_refsource_SECTRACK