CVE-2015-8728 Détail

CVE-2015-8728

Score / Gravité

5.5

Moyen

OWSAP

A03-Injection

EPSS

0.4%V3

Vecteur

Local

Publié

2016-01-04
01h00 +00:00

Modifié

2016-12-05
13h57 +00:00

Liens officiels

CVE.org

NVD

Notifications pour un CVE

Restez informé de toutes modifications pour un CVE spécifique.

Gestion des notifications

Liste des Notifications

Notifications pour un CVE

Restez informé de toutes modifications pour un CVE spécifique.

Critères appliqués l'envoi de l'alerte : par rapport à la dernière alerte envoyée + différences au niveau de CISA, EPSS, CVSS, CWE, Solutions, CPE.

Paramètres

Vous pouvez spécifier un titre qui sera récupéré dans les alertes qui seront envoyées.

Spécifiez ici un CVE ID comme CVE-2025-1234

Planifications

Mois

Prochaine exécution calculée

Jour

Jour de la semaine

Heure

Minute

Date de création

Dernière exécution

Prochaine exécution

Fonctionnalité nécessitant une connexion

Cette fonctionnalité qui vous permet de recevoir des alertes, n'est active que lorsque vous êtes connecté à votre compte.

Descriptions du CVE

The Mobile Identity parser in (1) epan/dissectors/packet-ansi_a.c in the ANSI A dissector and (2) epan/dissectors/packet-gsm_a_common.c in the GSM A dissector in Wireshark 1.12.x before 1.12.9 and 2.0.x before 2.0.1 improperly uses the tvb_bcd_dig_to_wmem_packet_str function, which allows remote attackers to cause a denial of service (buffer overflow and application crash) via a crafted packet.

Informations du CVE

Faiblesses connexes

CWE-ID	Nom de la faiblesse	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.

Métriques

Métriques	Score	Gravité	CVSS Vecteur	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 More informations 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	[email protected]
V2	4.3		AV:N/AC:M/Au:N/C:N/I:N/A:P	[email protected]

EPSS

EPSS est un modèle de notation qui prédit la probabilité qu'une vulnérabilité soit exploitée.

Score EPSS

Le modèle EPSS produit un score de probabilité compris entre 0 et 1 (0 et 100 %). Plus la note est élevée, plus la probabilité qu'une vulnérabilité soit exploitée est grande.

Percentile EPSS

Le percentile est utilisé pour classer les CVE en fonction de leur score EPSS. Par exemple, une CVE dans le 95e percentile selon son score EPSS est plus susceptible d'être exploitée que 95 % des autres CVE. Ainsi, le percentile sert à comparer le score EPSS d'une CVE par rapport à d'autres CVE.

EPSS First.org

Informations sur l'Exploit

Exploit Database EDB-ID : 39000

Date de publication : 2015-12-15 23h00 +00:00
Auteur : Google Security Research
EDB Vérifié : Yes

Source: https://code.google.com/p/google-security-research/issues/detail?id=649 The following crash due to a static buffer overflow 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 --- ==8089==ERROR: AddressSanitizer: global-buffer-overflow on address 0x00000df60580 at pc 0x000000d6eb8c bp 0x7ffc622f4a80 sp 0x7ffc622f4a78 WRITE of size 1 at 0x00000df60580 thread T0 #0 0xd6eb8b in my_dgt_tbcd_unpack wireshark/epan/dissectors/packet-gsm_a_common.c:1972:16 #1 0xd71258 in de_mid wireshark/epan/dissectors/packet-gsm_a_common.c:2270:9 #2 0x3c7ce02 in dissect_uma_IE wireshark/epan/dissectors/packet-uma.c:912:3 #3 0x3c7bfd1 in dissect_uma wireshark/epan/dissectors/packet-uma.c:1664:13 #4 0x1317640 in tcp_dissect_pdus wireshark/epan/dissectors/packet-tcp.c:2740:13 #5 0x3c7b62b in dissect_uma_tcp wireshark/epan/dissectors/packet-uma.c:1699:2 #6 0xaf3794 in call_dissector_through_handle wireshark/epan/packet.c:616:8 #7 0xae5692 in call_dissector_work wireshark/epan/packet.c:691:9 #8 0xae4e1d in dissector_try_uint_new wireshark/epan/packet.c:1148:9 #9 0x1318ea7 in decode_tcp_ports wireshark/epan/dissectors/packet-tcp.c:4610:9 #10 0x131ea52 in process_tcp_payload wireshark/epan/dissectors/packet-tcp.c:4668:13 #11 0x1319ad8 in dissect_tcp_payload wireshark/epan/dissectors/packet-tcp.c:4743:9 #12 0x132fb70 in dissect_tcp wireshark/epan/dissectors/packet-tcp.c:5575:13 #13 0xaf3794 in call_dissector_through_handle wireshark/epan/packet.c:616:8 #14 0xae5692 in call_dissector_work wireshark/epan/packet.c:691:9 #15 0xae4e1d in dissector_try_uint_new wireshark/epan/packet.c:1148:9 #16 0x29c5318 in ip_try_dissect wireshark/epan/dissectors/packet-ip.c:2001:7 #17 0x29d0521 in dissect_ip_v4 wireshark/epan/dissectors/packet-ip.c:2485:10 #18 0xaf3794 in call_dissector_through_handle wireshark/epan/packet.c:616:8 #19 0xae5692 in call_dissector_work wireshark/epan/packet.c:691:9 #20 0xae4e1d in dissector_try_uint_new wireshark/epan/packet.c:1148:9 #21 0xae5a38 in dissector_try_uint wireshark/epan/packet.c:1174:9 #22 0x24e0824 in dissect_ethertype wireshark/epan/dissectors/packet-ethertype.c:307:21 #23 0xaf3794 in call_dissector_through_handle wireshark/epan/packet.c:616:8 #24 0xae5692 in call_dissector_work wireshark/epan/packet.c:691:9 #25 0xaefb1b in call_dissector_only wireshark/epan/packet.c:2662:8 #26 0xae09f3 in call_dissector_with_data wireshark/epan/packet.c:2675:8 #27 0x24dc752 in dissect_eth_common wireshark/epan/dissectors/packet-eth.c:545:5 #28 0x24d499a in dissect_eth_maybefcs wireshark/epan/dissectors/packet-eth.c:828:5 #29 0xaf3794 in call_dissector_through_handle wireshark/epan/packet.c:616:8 #30 0xae5692 in call_dissector_work wireshark/epan/packet.c:691:9 #31 0xae4e1d in dissector_try_uint_new wireshark/epan/packet.c:1148:9 #32 0x25dca12 in dissect_frame wireshark/epan/dissectors/packet-frame.c:500:11 #33 0xaf3794 in call_dissector_through_handle wireshark/epan/packet.c:616:8 #34 0xae5692 in call_dissector_work wireshark/epan/packet.c:691:9 #35 0xaefb1b in call_dissector_only wireshark/epan/packet.c:2662:8 #36 0xae09f3 in call_dissector_with_data wireshark/epan/packet.c:2675:8 #37 0xadffde in dissect_record wireshark/epan/packet.c:501:3 #38 0xab6d0d in epan_dissect_run_with_taps wireshark/epan/epan.c:373:2 #39 0x53c91b in process_packet wireshark/tshark.c:3728:5 #40 0x535d90 in load_cap_file wireshark/tshark.c:3484:11 #41 0x52c1df in main wireshark/tshark.c:2197:13 0x00000df60580 is located 0 bytes to the right of global variable 'a_bigbuf' defined in 'packet-gsm_a_common.c:762:13' (0xdf60180) of size 1024 SUMMARY: AddressSanitizer: global-buffer-overflow wireshark/epan/dissectors/packet-gsm_a_common.c:1972:16 in my_dgt_tbcd_unpack Shadow bytes around the buggy address: 0x000081be4060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x000081be4070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x000081be4080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x000081be4090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x000081be40a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 =>0x000081be40b0:[f9]f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 0x000081be40c0: f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 0x000081be40d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x000081be40e0: 00 00 00 00 f9 f9 f9 f9 00 00 00 00 00 00 00 00 0x000081be40f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x000081be4100: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Shadow byte legend (one shadow byte represents 8 application bytes): Addressable: 00 Partially addressable: 01 02 03 04 05 06 07 Heap left redzone: fa Heap right redzone: fb Freed heap region: fd Stack left redzone: f1 Stack mid redzone: f2 Stack right redzone: f3 Stack partial redzone: f4 Stack after return: f5 Stack use after scope: f8 Global redzone: f9 Global init order: f6 Poisoned by user: f7 Container overflow: fc Array cookie: ac Intra object redzone: bb ASan internal: fe Left alloca redzone: ca Right alloca redzone: cb ==8089==ABORTING --- cut --- The crash was reported at https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11797. Attached are three files which trigger the crash. Proof of Concept: https://gitlab.com/exploit-database/exploitdb-bin-sploits/-/raw/main/bin-sploits/39000.zip