Facebook WhatsApp Messenger on Android/iOS/Windows Phone/Tizen VoIP Stack SRTCP Packet memory corruption

entryeditHistoryDiffjsonxmlCTI
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.
8.2$5k-$25k0.00

A vulnerability was found in Facebook WhatsApp Messenger on Android/iOS/Windows Phone/Tizen (Messaging Software) (affected version not known) and classified as critical. Affected by this issue is some unknown processing of the component VoIP Stack. The manipulation as part of a SRTCP Packet leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. Impacted is confidentiality, integrity, and availability.

The bug was discovered 05/13/2019. The weakness was disclosed 05/13/2019 with Facebook as CVE-2019-3568 as confirmed advisory (Facebook). The advisory is shared for download at facebook.com. The public release has been coordinated in cooperation with the vendor. This vulnerability is handled as CVE-2019-3568 since 01/02/2019. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details are unknown but a private exploit is available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 06/13/2020). This vulnerability has a historic impact due to its background and reception. The advisory points out:

A buffer overflow vulnerability in WhatsApp VOIP stack allowed remote code execution via specially crafted series of SRTCP packets sent to a target phone number.

It is declared as highly functional. As 0-day the estimated underground price was around $25k-$100k.

Upgrading eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.

nytimes.com is providing further details.

Productinfoedit

Type

Vendor

Name

CPE 2.3infoedit

CPE 2.2infoedit

CVSSv3infoedit

VulDB Meta Base Score: 8.5
VulDB Meta Temp Score: 8.2

VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 9.8
NVD Vector: 🔍

CVSSv2infoedit

AVACAuCIA
🔍🔍🔍🔍🔍🔍
🔍🔍🔍🔍🔍🔍
🔍🔍🔍🔍🔍🔍
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock

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

NVD Base Score: 🔍

Exploitinginfoedit

Class: Memory corruption
CWE: CWE-119
ATT&CK: Unknown

Local: No
Remote: Yes

Availability: 🔍
Access: Private
Status: Highly functional

Price Prediction: 🔍
Current Price Estimation: 🔍

0-Dayunlockunlockunlockunlock
Todayunlockunlockunlockunlock

Threat Intelligenceinfoedit

Threat: 🔍
Adversaries: 🔍
Geopolitics: 🔍
Economy: 🔍
Predictions: 🔍
Remediation: 🔍

Countermeasuresinfoedit

Recommended: Upgrade
Status: 🔍

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

Timelineinfoedit

01/02/2019 🔍
05/13/2019 +131 days 🔍
05/13/2019 +0 days 🔍
05/13/2019 +0 days 🔍
05/14/2019 +1 days 🔍
06/13/2020 +396 days 🔍

Sourcesinfoedit

Advisory: CVE-2019-3568
Organization: Facebook
Status: Confirmed
Coordinated: 🔍

CVE: CVE-2019-3568 (🔍)
scip Labs: https://www.scip.ch/en/?labs.20130704
Misc.: 🔍

Entryinfoedit

Created: 05/14/2019 11:33 AM
Updated: 06/13/2020 08:51 AM
Changes: (2) vulnerability_discoverydate source_cve_assigned
Complete: 🔍

Comments

No comments yet. Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!