Threats / Meta Platforms / CVE-2019-3568
CVE-2019-3568
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Meta Platforms WhatsApp vulnerability
Buffer overflow in WhatsApp VOIP stack enables remote code execution through specially crafted RTCP packets, exploitable without user interaction.
Verdict
Today item — known-exploited.
A remote attacker can execute arbitrary code on a target device by sending malicious RTCP packets to a WhatsApp user's phone number. The vulnerability requires no user action and has been actively exploited in the wild.
CISA KEV Yes · 2022-04-195EPSS 0.39166 (verify live)6CVSS 9.8 (CISA)4CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
5 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-04-19).
Probability (EPSS)
EPSS 0.39166 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: Meta Platforms, WhatsApp. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-122 Heap-based Buffer Overflow — weakness family: Memory safety.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 1071 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a series of malicious RTCP packets designed to overflow a buffer in the WhatsApp VOIP stack.
Business
WhatsApp users face unauthorized code execution on their devices without any warning or interaction required.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I send these packets to a target phone number, triggering the vulnerability during VOIP processing.
Business
Meta Platforms faces reputational damage and user trust erosion due to a critical remote code execution flaw in a widely-used communication platform.
3
Lateral reach — past segmentation narrative 3
Attacker
I gain code execution with the privileges of the WhatsApp process on the target device.
Business
User data, communications, and device security are compromised, creating liability and regulatory exposure for Meta Platforms.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05