# CVE-2020-1905: Information disclosure in WhatsApp for Android

> Sequentially generated URIs allowed malicious apps to guess and access previously opened attachments in WhatsApp for Android.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Oct 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-wprc-r97f-h356

## What is CVE-2020-1905?

CVE-2020-1905 is a low-severity vulnerability in Facebook WhatsApp for Android, published on 6 Oct 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-330 (Use of Insufficiently Random Values), CWE-340 (Generation of Predictable Numbers or Identifiers)

## Which versions are affected by CVE-2020-1905?

It affects 1 product.


Products: Whatsapp Whatsapp.

## How do I fix CVE-2020-1905?

No fix has been published for CVE-2020-1905 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-1905 being exploited?

There is no known exploitation of CVE-2020-1905 in the wild and no public exploit code.

## Other vulnerabilities in Facebook WhatsApp for Android

- [CVE-2019-3568](https://insights.sbomify.com/CVE-2019-3568/): WhatsApp VOIP Stack Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2019-18426](https://insights.sbomify.com/CVE-2019-18426/): WhatsApp Cross-Site Scripting (high 8.2, exploited in the wild)
- [CVE-2025-55177](https://insights.sbomify.com/CVE-2025-55177/): Meta Platforms WhatsApp Incorrect Authorization (medium 5.4, exploited in the wild)
- [CVE-2022-36934](https://insights.sbomify.com/CVE-2022-36934/): Integer overflow in WhatsApp Business for Android (critical 9.8)
- [CVE-2021-24042](https://insights.sbomify.com/CVE-2021-24042/): Memory corruption in WhatsApp Business for Android (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-1905 and fix it if it is affected.

What it is: CVE-2020-1905 is a low-severity vulnerability in Facebook WhatsApp for Android, published on 6 Oct 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-1905 in the wild and no public exploit code.

Affected product: Facebook WhatsApp for Android. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-1905/ (Markdown: https://insights.sbomify.com/CVE-2020-1905/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-1905
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-1905
- OSV: https://osv.dev/vulnerability/CVE-2020-1905

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-1905/
Summaries are generated and may contain mistakes; the official description above is the record.