Samsung S4 GT-I9500 up to 3.4 samsung_extdisp Driver information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in Samsung S4 GT-I9500 up to 3.4. Affected is an unknown function of the component samsung_extdisp Driver. Such manipulation leads to information disclosure. This vulnerability is listed as CVE-2015-1800. The attack may be performed from remote. There is no available exploit. A patch should be applied to remediate this issue.
Details
A vulnerability, which was classified as problematic, has been found in Samsung S4 GT-I9500 up to 3.4. Affected by this issue is an unknown code block of the component samsung_extdisp Driver. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. CVE summarizes:
The samsung_extdisp driver in the Samsung S4 (GT-I9500) I9500XXUEMK8 kernel 3.4 and earlier allows attackers to potentially obtain sensitive information.
The bug was discovered 09/21/2015. The weakness was presented 08/24/2017 by Jonathan Salwan (oss-sec). The advisory is available at openwall.com. This vulnerability is handled as CVE-2015-1800 since 02/17/2015. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1592 by the MITRE ATT&CK project.
The vulnerability was handled as a non-public zero-day exploit for at least 703 days. During that time the estimated underground price was around $0-$5k.
Applying a patch is able to eliminate this problem.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 76807†). See VDB-105699 for similar entry. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.samsung.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CVSSv2
| 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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Timeline
02/17/2015 🔍09/21/2015 🔍
09/21/2015 🔍
08/24/2017 🔍
08/24/2017 🔍
08/25/2017 🔍
11/10/2019 🔍
Sources
Vendor: samsung.comAdvisory: openwall.com
Researcher: Jonathan Salwan
Status: Not defined
CVE: CVE-2015-1800 (🔍)
GCVE (CVE): GCVE-0-2015-1800
GCVE (VulDB): GCVE-100-105698
SecurityFocus: 76807 - Samsung S4 GT-I9500 Memory Corruption and Information Disclosure Vulnerabilities
See also: 🔍
Entry
Created: 08/25/2017 08:42Updated: 11/10/2019 07:45
Changes: 08/25/2017 08:42 (57), 11/10/2019 07:45 (7)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.