CVE-2017-9353 : Detail

CVE-2017-9353

7.5
/
High
A03-Injection
1.61%V3
Network
2017-06-02
03h04 +00:00
2017-08-12
07h57 +00:00
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

In Wireshark 2.2.0 to 2.2.6, the IPv6 dissector could crash. This was addressed in epan/dissectors/packet-ipv6.c by validating an IPv6 address.

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 7.5 HIGH CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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.

Network

A vulnerability exploitable with network access means the vulnerable component is bound to the network stack and the attacker's path is through OSI layer 3 (the network layer). Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable one or more network hops away (e.g. across layer 3 boundaries from routers).

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.

None

The vulnerable system can be exploited without interaction from any user.

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 5 AV:N/AC:L/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 : 42123

Publication date : 2017-06-04 22h00 +00:00
Author : OSS-Fuzz
EDB Verified : Yes

Build Information: TShark (Wireshark) 2.3.0 (v2.3.0rc0-3369-g2e2ba64b72) Copyright 1998-2017 Gerald Combs <gerald@wireshark.org> and contributors. License GPLv2+: GNU GPL version 2 or later <http://www.gnu.org/licenses/old-licenses/gpl-2.0.html> This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Compiled (64-bit) with libpcap, with POSIX capabilities (Linux), with libnl 3, with GLib 2.50.3, with zlib 1.2.11, without SMI, with c-ares 1.12.0, with Lua 5.2.4, with GnuTLS 3.5.11, with Gcrypt 1.7.6, with MIT Kerberos, with GeoIP, with nghttp2 1.20.0, with LZ4, with Snappy, with libxml2 2.9.4. Running on Linux 4.10.13-1-ARCH, with Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (with SSE4.2), with 31996 MB of physical memory, with locale C, with libpcap version 1.8.1, with GnuTLS 3.5.11, with Gcrypt 1.7.6, with zlib 1.2.11. Built using clang 4.2.1 Compatible Clang 4.0.0 (tags/RELEASE_400/final). -- A problem was found by the oss-fuzz project: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=1303 Attached is the sample that triggers this error which can be reproduced with an ASAN+UBSAN build of Wireshark ("tshark -Vr test.pcap"). -- wsutil/inet_ipv6.h:111:15: runtime error: member access within null pointer of type 'const struct e_in6_addr' #0 0x7f2b8106b2b8 in in6_is_addr_multicast wsutil/inet_ipv6.h:111:15 #1 0x7f2b81068247 in dissect_routing6_rpl epan/dissectors/packet-ipv6.c:952:9 #2 0x7f2b81052227 in dissect_routing6 epan/dissectors/packet-ipv6.c:1217:9 #3 0x7f2b83aa6a6d in call_dissector_through_handle epan/packet.c:684:8 #4 0x7f2b83a9126f in call_dissector_work epan/packet.c:759:9 #5 0x7f2b83a9028d in dissector_try_uint_new epan/packet.c:1329:8 #6 0x7f2b83a917c9 in dissector_try_uint epan/packet.c:1353:9 #7 0x7f2b800c8361 in dissect_ayiya epan/dissectors/packet-ayiya.c:134:9 #8 0x7f2b83aa6a6d in call_dissector_through_handle epan/packet.c:684:8 #9 0x7f2b83a9126f in call_dissector_work epan/packet.c:759:9 #10 0x7f2b83a9028d in dissector_try_uint_new epan/packet.c:1329:8 #11 0x7f2b83a917c9 in dissector_try_uint epan/packet.c:1353:9 #12 0x7f2b822f9326 in decode_udp_ports epan/dissectors/packet-udp.c:678:7 #13 0x7f2b8230ee02 in dissect epan/dissectors/packet-udp.c:1131:5 #14 0x7f2b822fe12f in dissect_udp epan/dissectors/packet-udp.c:1137:3 #15 0x7f2b83aa6a6d in call_dissector_through_handle epan/packet.c:684:8 #16 0x7f2b83a9126f in call_dissector_work epan/packet.c:759:9 #17 0x7f2b83a9028d in dissector_try_uint_new epan/packet.c:1329:8 #18 0x7f2b80a62252 in dissect_exported_pdu epan/dissectors/packet-exported_pdu.c:307:17 #19 0x7f2b83aa6a6d in call_dissector_through_handle epan/packet.c:684:8 #20 0x7f2b83a9126f in call_dissector_work epan/packet.c:759:9 #21 0x7f2b83a9028d in dissector_try_uint_new epan/packet.c:1329:8 #22 0x7f2b80b803e7 in dissect_frame epan/dissectors/packet-frame.c:521:11 #23 0x7f2b83aa6a6d in call_dissector_through_handle epan/packet.c:684:8 #24 0x7f2b83a9126f in call_dissector_work epan/packet.c:759:9 #25 0x7f2b83a9fe87 in call_dissector_only epan/packet.c:2992:8 #26 0x7f2b83a88034 in call_dissector_with_data epan/packet.c:3005:8 #27 0x7f2b83a87054 in dissect_record epan/packet.c:567:3 #28 0x7f2b83a1f398 in epan_dissect_run_with_taps epan/epan.c:474:2 #29 0x561364f21686 in process_packet_single_pass tshark.c:3419:5 #30 0x561364f1a821 in process_cap_file tshark.c:3250:11 #31 0x561364f12549 in main tshark.c:1955:17 #32 0x7f2b754f9510 in __libc_start_main (/usr/lib/libc.so.6+0x20510) #33 0x561364dff4f9 in _start (run/tshark+0xd44f9) SUMMARY: AddressSanitizer: undefined-behavior wsutil/inet_ipv6.h:111:15 in Proof of Concept: https://gitlab.com/exploit-database/exploitdb-bin-sploits/-/raw/main/bin-sploits/42123.zip

Products Mentioned

Configuraton 0

Wireshark>>Wireshark >> Version From (including) 2.2.0 To (including) 2.2.6

References

http://www.securityfocus.com/bid/98805
Tags : vdb-entry, x_refsource_BID
https://www.exploit-db.com/exploits/42123/
Tags : exploit, x_refsource_EXPLOIT-DB
http://www.securitytracker.com/id/1038612
Tags : vdb-entry, x_refsource_SECTRACK