CVE Details for CVE: CVE-2018-16058
Summary
In Wireshark 2.6.0 to 2.6.2, 2.4.0 to 2.4.8, and 2.2.0 to 2.2.16, the Bluetooth AVDTP dissector could crash. This was addressed in epan/dissectors/packet-btavdtp.c by properly initializing a data structure.
Timestamps | |
---|---|
Last major update | 07-11-2023 - 02:53 |
Published | 30-08-2018 - 01:29 |
Last modified | 07-11-2023 - 02:53 |
References
- https://www.wireshark.org/security/wnpa-sec-2018-44.html
- https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14884
- http://www.securityfocus.com/bid/105174
- http://www.securitytracker.com/id/1041609
- https://www.debian.org/security/2018/dsa-4315
- https://lists.debian.org/debian-lts-announce/2019/01/msg00010.html
- http://lists.opensuse.org/opensuse-security-announce/2020-03/msg00027.html
- https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=c48d6a6d60c5c9111838a945966b6cb8750777be
Vulnerable Configurations
-
cpe:2.3:a:wireshark:wireshark:2.2.0:*:*:*:*:*:*:*
cpe:2.3:a:wireshark:wireshark:2.2.0:*:*:*:*:*:*:*
-
cpe:2.3:a:wireshark:wireshark:2.2.1:*:*:*:*:*:*:*
cpe:2.3:a:wireshark:wireshark:2.2.1:*:*:*:*:*:*:*
-
cpe:2.3:a:wireshark:wireshark:2.2.2:*:*:*:*:*:*:*
cpe:2.3:a:wireshark:wireshark:2.2.2:*:*:*:*:*:*:*
-
cpe:2.3:a:wireshark:wireshark:2.2.3:*:*:*:*:*:*:*
cpe:2.3:a:wireshark:wireshark:2.2.3:*:*:*:*:*:*:*
-
cpe:2.3:a:wireshark:wireshark:2.2.4:*:*:*:*:*:*:*
cpe:2.3:a:wireshark:wireshark:2.2.4:*:*:*:*:*:*:*
-
cpe:2.3:a:wireshark:wireshark:2.2.5:*:*:*:*:*:*:*
cpe:2.3:a:wireshark:wireshark:2.2.5:*:*:*:*:*:*:*
-
cpe:2.3:a:wireshark:wireshark:2.2.6:*:*:*:*:*:*:*
cpe:2.3:a:wireshark:wireshark:2.2.6:*:*:*:*:*:*:*
-
cpe:2.3:a:wireshark:wireshark:2.2.7:*:*:*:*:*:*:*
cpe:2.3:a:wireshark:wireshark:2.2.7:*:*:*:*:*:*:*
-
cpe:2.3:a:wireshark:wireshark:2.2.8:*:*:*:*:*:*:*
cpe:2.3:a:wireshark:wireshark:2.2.8:*:*:*:*:*:*:*
-
cpe:2.3:a:wireshark:wireshark:2.2.9:*:*:*:*:*:*:*
cpe:2.3:a:wireshark:wireshark:2.2.9:*:*:*:*:*:*:*
-
cpe:2.3:a:wireshark:wireshark:2.2.10:*:*:*:*:*:*:*
cpe:2.3:a:wireshark:wireshark:2.2.10:*:*:*:*:*:*:*
-
cpe:2.3:a:wireshark:wireshark:2.2.11:*:*:*:*:*:*:*
cpe:2.3:a:wireshark:wireshark:2.2.11:*:*:*:*:*:*:*
-
cpe:2.3:a:wireshark:wireshark:2.2.12:*:*:*:*:*:*:*
cpe:2.3:a:wireshark:wireshark:2.2.12:*:*:*:*:*:*:*
-
cpe:2.3:a:wireshark:wireshark:2.2.13:*:*:*:*:*:*:*
cpe:2.3:a:wireshark:wireshark:2.2.13:*:*:*:*:*:*:*
-
cpe:2.3:a:wireshark:wireshark:2.2.14:*:*:*:*:*:*:*
cpe:2.3:a:wireshark:wireshark:2.2.14:*:*:*:*:*:*:*
-
cpe:2.3:a:wireshark:wireshark:2.2.15:*:*:*:*:*:*:*
cpe:2.3:a:wireshark:wireshark:2.2.15:*:*:*:*:*:*:*
-
cpe:2.3:a:wireshark:wireshark:2.2.16:*:*:*:*:*:*:*
cpe:2.3:a:wireshark:wireshark:2.2.16:*:*:*:*:*:*:*
-
cpe:2.3:a:wireshark:wireshark:2.4.0:*:*:*:*:*:*:*
cpe:2.3:a:wireshark:wireshark:2.4.0:*:*:*:*:*:*:*
-
cpe:2.3:a:wireshark:wireshark:2.4.1:*:*:*:*:*:*:*
cpe:2.3:a:wireshark:wireshark:2.4.1:*:*:*:*:*:*:*
-
cpe:2.3:a:wireshark:wireshark:2.4.2:*:*:*:*:*:*:*
cpe:2.3:a:wireshark:wireshark:2.4.2:*:*:*:*:*:*:*
-
cpe:2.3:a:wireshark:wireshark:2.4.3:*:*:*:*:*:*:*
cpe:2.3:a:wireshark:wireshark:2.4.3:*:*:*:*:*:*:*
-
cpe:2.3:a:wireshark:wireshark:2.4.4:*:*:*:*:*:*:*
cpe:2.3:a:wireshark:wireshark:2.4.4:*:*:*:*:*:*:*
-
cpe:2.3:a:wireshark:wireshark:2.4.5:*:*:*:*:*:*:*
cpe:2.3:a:wireshark:wireshark:2.4.5:*:*:*:*:*:*:*
-
cpe:2.3:a:wireshark:wireshark:2.4.6:*:*:*:*:*:*:*
cpe:2.3:a:wireshark:wireshark:2.4.6:*:*:*:*:*:*:*
-
cpe:2.3:a:wireshark:wireshark:2.4.7:*:*:*:*:*:*:*
cpe:2.3:a:wireshark:wireshark:2.4.7:*:*:*:*:*:*:*
-
cpe:2.3:a:wireshark:wireshark:2.4.8:*:*:*:*:*:*:*
cpe:2.3:a:wireshark:wireshark:2.4.8:*:*:*:*:*:*:*
-
cpe:2.3:a:wireshark:wireshark:2.6.0:*:*:*:*:*:*:*
cpe:2.3:a:wireshark:wireshark:2.6.0:*:*:*:*:*:*:*
-
cpe:2.3:a:wireshark:wireshark:2.6.1:*:*:*:*:*:*:*
cpe:2.3:a:wireshark:wireshark:2.6.1:*:*:*:*:*:*:*
-
cpe:2.3:a:wireshark:wireshark:2.6.2:*:*:*:*:*:*:*
cpe:2.3:a:wireshark:wireshark:2.6.2:*:*:*:*:*:*:*
-
cpe:2.3:o:debian:debian_linux:8.0:*:*:*:*:*:*:*
cpe:2.3:o:debian:debian_linux:8.0:*:*:*:*:*:*:*
-
cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:*
cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:*
CAPEC
Click the CAPEC title to display a description
-
Leveraging Race Conditions
The adversary targets a race condition occurring when multiple processes access and manipulate the same resource concurrently, and the outcome of the execution depends on the particular order in which the access takes place. The adversary can leverage a race condition by "running the race", modifying the resource and modifying the normal execution flow. For instance, a race condition can occur while accessing a file: the adversary can trick the system by replacing the original file with their version and cause the system to read the malicious file.
-
Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions
This attack targets a race condition occurring between the time of check (state) for a resource and the time of use of a resource. A typical example is file access. The adversary can leverage a file access race condition by "running the race", meaning that they would modify the resource between the first time the target program accesses the file and the time the target program uses the file. During that period of time, the adversary could replace or modify the file, causing the application to behave unexpectedly.
CWE
CVSS
Base
5.0
Impact
2.9
Exploitability
10.0
Access
Vector | Complexity | Authentication |
---|---|---|
NETWORK | LOW | NONE |
Impact
Confidentiality | Integrity | Availability |
---|---|---|
NONE | NONE | PARTIAL |
CVSS3
Base
7.5
Impact
3.6
Exploitability
3.9
Access
Attack Complexity | Attack vector | Privileges Required | Scope | User Interaction |
---|---|---|---|---|
LOW | NETWORK | NONE | UNCHANGED | NONE |
Impact
Confidentiality | Integrity | Availability |
---|---|---|
NONE | NONE | HIGH |