VDB-91709 · SVE-2016-6248 · GCVE-100-91709

Samsung Mobile Phone L(5.0/5.1)/M(6.0) SystemUI null pointer dereference

CVSS Meta Temp Score CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.	Current Exploit Price (≈) Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.	CTI Interest Score Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
3.1	$0-$5k	0.00

Summaryinfo

A vulnerability identified as problematic has been detected in Samsung Mobile Phone L(5.0/5.1)/M(6.0). This affects an unknown part of the component SystemUI. The manipulation leads to null pointer dereference. There is no exploit available. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability was found in Samsung Mobile Phone L(5.0/5.1)/M(6.0) (Smartphone Operating System). It has been rated as problematic. This issue affects some unknown functionality of the component SystemUI. The manipulation with an unknown input leads to a null pointer dereference vulnerability. Using CWE to declare the problem leads to CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. Impacted is availability.

The weakness was shared 09/08/2016 by 0xr0ot as SVE-2016-6248 as not defined mailinglist post (Full-Disclosure). The advisory is shared at seclists.org. The vendor cooperated in the coordination of the public release. Neither technical details nor an exploit are publicly available.

Applying a patch is able to eliminate this problem. The bugfix is ready for download at security.samsungmobile.com.

The entry VDB-93303 is related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Smartphone Operating System

Vendor

Samsung

Name

Mobile Phone

Version

License

commercial

Website

Vendor: https://www.samsung.com/

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.3
VulDB Meta Temp Score: 3.1

VulDB Base Score: 3.3
VulDB Temp Score: 3.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AV	AC	Au	C	I	A
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳

Vector	Complexity	Authentication	Confidentiality	Integrity	Availability
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Null pointer dereference
CWE: CWE-476 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔍

0-Day	Unlock	Unlock	Unlock	Unlock
Today	Unlock	Unlock	Unlock	Unlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Patch
Status: 🔍

0-Day Time: 🔍

Patch: security.samsungmobile.com

Timelineinfo

09/08/2016 🔍
09/21/2016 +13 days 🔍
04/21/2019 +942 days 🔍

Sourcesinfo

Vendor: samsung.com

Advisory: SVE-2016-6248
Researcher: 0xr0ot
Status: Not defined
Confirmation: 🔍
Coordinated: 🔍

GCVE (VulDB): GCVE-100-91709
See also: 🔍

Entryinfo

Created: 09/21/2016 11:14
Updated: 04/21/2019 09:44
Changes: 09/21/2016 11:14 (45), 04/21/2019 09:44 (2)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.