CVE-2022-27492
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn integer underflow in WhatsApp could have caused remote code execution when receiving a crafted video file.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAn integer underflow vulnerability exists in WhatsApp's video file parsing functionality. When processing a specially crafted video file, the integer underflow can cause memory corruption that leads to remote code execution. The attacker exploits this by sending a malicious video to the victim.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.22.15.9< 2.22.16.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed WhatsApp versionOpen WhatsApp, go to Settings > Help > App Info to view the current version numberAffected if Version is below 2.22.15.9 (Android) or below 2.22.16.2 (iOS)
-
Verify platform and version mappingConfirm whether you are using WhatsApp on Android or iOS, then cross-reference with the appropriate version thresholdAffected if Android version < 2.22.15.9 OR iOS version < 2.22.16.2
-
Confirm video reception is enabledCheck that WhatsApp can receive video files (default setting allows video downloads from contacts)Affected if Video file reception is enabled and the app processes incoming video files
You are affected if your installed WhatsApp version is below 2.22.15.9 on Android or below 2.22.16.2 on iOS, and the app processes incoming video files.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.22.15.92.22.16.2
Update WhatsApp to the latest version available in the respective app stores. Do not accept video files from untrusted or unknown sources.
WhatsApp version 2.22.16.2 or later (or 2.22.15.9 or later for Android)
- Open the WhatsApp application on your device
- Navigate to Settings > Help > App Info (or Settings > About on some platforms)
- Check the current version number displayed
- If version is below 2.22.15.9 (Android) or 2.22.16.2 (iOS), proceed to update
- Open your device's app store (Google Play Store or Apple App Store)
- Search for WhatsApp and tap Update to install the latest version
- Alternatively, enable automatic app updates in your device settings to ensure future security patches are applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27492 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-27492 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data