Facebook WhatsApp up to 2.18 on Android Call memory corruption
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
8.4 | $0-$5k | 0.00 |
A vulnerability, which was classified as critical, has been found in Facebook WhatsApp up to 2.18 on Android (Social Network Software). This issue affects an unknown code block of the component Call Handler. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
When receiving calls using WhatsApp for Android, a missing size check when parsing a sender-provided packet allowed for a stack-based overflow. This issue affects WhatsApp for Android prior to 2.18.248 and WhatsApp Business for Android prior to 2.18.132.
The weakness was published 06/14/2019 (Website). The advisory is shared at securityfocus.com. The identification of this vulnerability is CVE-2018-6349 since 01/26/2018. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.
Upgrading eliminates this vulnerability.
Similar entries are available at VDB-136506 and VDB-136504. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
01/26/2018 🔍06/14/2019 🔍
06/15/2019 🔍
10/05/2023 🔍
Sources
Advisory: securityfocus.com⛔Status: Not defined
CVE: CVE-2018-6349 (🔍)
GCVE (CVE): GCVE-0-2018-6349
GCVE (VulDB): GCVE-100-136505
SecurityFocus: 108804
scip Labs: https://www.scip.ch/en/?labs.20130704
See also: 🔍
Entry
Created: 06/15/2019 12:50 PMUpdated: 10/05/2023 11:51 AM
Changes: 06/15/2019 12:50 PM (57), 06/24/2020 02:58 PM (1), 10/05/2023 11:51 AM (4)
Complete: 🔍
Cache ID: 18:AEF:40
No comments yet. Languages: en.
Please log in to comment.