Facebook WhatsApp Messenger on iOS/Android RTP Packet Video Call heap-based overflow

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.
4.8$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as critical, has been found in Facebook WhatsApp Messenger on iOS/Android. This impacts an unknown function of the component RTP Packet Handler. The manipulation as part of Video Call leads to heap-based overflow. It is possible to initiate the attack remotely. Furthermore, there is an exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Facebook WhatsApp Messenger on iOS/Android (Messaging Software) (affected version unknown). It has been rated as critical. This issue affects an unknown functionality of the component RTP Packet Handler. The manipulation as part of a Video Call leads to a heap-based overflow vulnerability. Using CWE to declare the problem leads to CWE-122. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). Impacted is availability.

The weakness was shared 10/10/2018 with Google Project Zero as Issue 1654 as confirmed bug report (Website). The advisory is shared at bugs.chromium.org. The vendor cooperated in the coordination of the public release. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are unknown but a public exploit is available.

A public exploit has been developed by Natashenka in C and been published even before and not after the advisory. The exploit is available at bugs.chromium.org. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 40 days. During that time the estimated underground price was around $5k-$25k.

Upgrading eliminates this vulnerability. The problem might be mitigated by replacing the product with Threema, Signal or Telegram as an alternative. The best possible mitigation is suggested to be upgrading to the latest version. A possible mitigation has been published immediately after the disclosure of the vulnerability.

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

Productinfo

Type

Vendor

Name

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 4.8

VulDB Base Score: 5.3
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

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

Exploitinginfo

Class: Heap-based overflow
CWE: CWE-122 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Author: Natashenka
Programming Language: 🔍
Download: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Alternative: Threema/Signal/Telegram

Timelineinfo

08/31/2018 🔍
10/10/2018 +40 days 🔍
10/10/2018 +0 days 🔍
10/10/2018 +0 days 🔍
04/01/2020 +539 days 🔍

Sourcesinfo

Advisory: Issue 1654
Organization: Google Project Zero
Status: Confirmed
Coordinated: 🔍

GCVE (VulDB): GCVE-100-125189
scip Labs: https://www.scip.ch/en/?labs.20130704

Entryinfo

Created: 10/10/2018 14:18
Updated: 04/01/2020 14:59
Changes: 10/10/2018 14:18 (53), 04/01/2020 14:59 (2)
Complete: 🔍
Cache ID: 216::103

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

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!