LiveActive security incident?Get immediate response
CVE Record

CVE-2022-36934: An integer overflow in WhatsApp could result in remote code execution in an established video call.

An integer overflow in WhatsApp could result in remote code execution in an established video call.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This CVE is a critical WhatsApp flaw where a video call condition could allow remote code execution. For leaders, the main concern is unmanaged mobile exposure: employee or executive phones using outdated WhatsApp or WhatsApp Business may be at risk. The provided sources do not identify specific vulnerable or fixed version numbers.

Executive priority

Treat as urgent for mobile fleet hygiene, especially where WhatsApp is used for business communication. The lack of version detail means the practical priority is rapid inventory, update enforcement, and exception tracking.

Technical view

CVE-2022-36934 is described as an integer overflow in WhatsApp that could lead to remote code execution in an established video call. The record lists WhatsApp and WhatsApp Business for iOS and Android, CVSS 3.1 score 9.8, and CWE-122. Version detail is unspecified in the provided bundle.

Likely exposure

Exposure is most likely on iOS or Android devices running affected WhatsApp or WhatsApp Business builds. The affected versions are unspecified, so organizations need mobile app inventory rather than product-name assumptions.

Exploitation context

The provided sources do not state active exploitation, and the bundle marks CISA KEV as false. Treat this as a high-impact remote code execution risk, but do not claim known exploitation from this evidence.

Researcher notes

The public description is brief and does not provide affected version ranges, fixed versions, root-cause detail, or exploit indicators. Analysis should stay anchored to the CVE record, CVSS vector, CWE-122, affected product list, and WhatsApp advisory.

Mitigation direction

  • Review WhatsApp's 2022 security advisory for fixed-version guidance.
  • Update WhatsApp and WhatsApp Business to current supported releases.
  • Use MDM controls to enforce minimum mobile app versions.
  • Prioritize executive, privileged, and high-risk user devices.
  • Restrict business use of unmanaged outdated WhatsApp builds.

Validation and detection

  • Inventory WhatsApp and WhatsApp Business versions across managed devices.
  • Compare installed versions against WhatsApp advisory guidance.
  • Confirm app update enforcement through MDM or app-store policy.
  • Check whether BYOD users handle sensitive business communications.
  • Document any devices that cannot be verified or updated.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-122: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-36934 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2022-36934Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MetaWhatsApp for iOSunspecifiedListed
MetaWhatsApp Business for iOSunspecifiedListed
MetaWhatsApp for AndroidunspecifiedListed
MetaWhatsApp Business for AndroidunspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-122 · source CWE mapping

Heap-based Buffer Overflow

Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.