Samsung Galaxy S4/S5/S6/S7 OTA WAP PUSH SMS wifi-service.jar WifiServiceImpl 7pk security
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Samsung Galaxy S4/S5/S6/S7. Impacted is the function WifiServiceImpl of the file wifi-service.jar of the component OTA WAP PUSH SMS. The manipulation leads to 7pk security.
This vulnerability is uniquely identified as CVE-2016-7989. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability, which was classified as critical, has been found in Samsung Galaxy S4/S5/S6/S7 (Smartphone Operating System). This issue affects the function WifiServiceImpl of the file wifi-service.jar of the component OTA WAP PUSH SMS. The manipulation with an unknown input leads to a 7pk security vulnerability. Using CWE to declare the problem leads to CWE-254. Impacted is availability. The summary by CVE is:
On Samsung Galaxy S4 through S7 devices, a malformed OTA WAP PUSH SMS containing an OMACP message sent remotely triggers an unhandled ArrayIndexOutOfBoundsException in Samsung's implementation of the WifiServiceImpl class within wifi-service.jar. This causes the Android runtime to continually crash, rendering the device unusable until a factory reset is performed, a subset of SVE-2016-6542.
The weakness was disclosed 10/31/2016 (Website). The advisory is shared at security.samsungmobile.com. The identification of this vulnerability is CVE-2016-7989 since 09/09/2016. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1211 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 94082†). The entries VDB-93196, VDB-93198, VDB-93199 and VDB-95506 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
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: 7.5VulDB Meta Temp Score: 7.5
VulDB Base Score: 7.5
VulDB Temp Score: 7.5
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: 7pk securityCWE: CWE-254
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
09/09/2016 🔍10/31/2016 🔍
10/31/2016 🔍
10/31/2016 🔍
10/31/2016 🔍
05/21/2019 🔍
Sources
Vendor: samsung.comAdvisory: security.samsungmobile.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2016-7989 (🔍)
GCVE (CVE): GCVE-0-2016-7989
GCVE (VulDB): GCVE-100-93197
SecurityFocus: 94082 - Multiple Samsung Galaxy Devices CVE-2016-7989 Denial of Service Vulnerability
See also: 🔍
Entry
Created: 10/31/2016 16:15Updated: 05/21/2019 09:22
Changes: 10/31/2016 16:15 (53), 05/21/2019 09:22 (12)
Complete: 🔍
Cache ID: 216:7E3:103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.