# CVE-2020-10570: Security feature bypass in n/a

> Physically proximate attackers can bypass passcode restrictions to read and reply to messages when the Show Popup feature is enabled.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-fwx7-h2cj-c566

## What is CVE-2020-10570?

CVE-2020-10570 is a medium-severity vulnerability in n/a, published on 24 Mar 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Telegram application through 5.12 for Android, when Show Popup is enabled, might allow physically proximate attackers to bypass intended restrictions on message reading and message replying. This might be interpreted as a bypass of the passcode feature.

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

It affects 1 product.


Products: Telegram Telegram.

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

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

## Is CVE-2020-10570 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-10044](https://insights.sbomify.com/CVE-2019-10044/): Other in n/a (high 8.8)
- [CVE-2018-20436](https://insights.sbomify.com/CVE-2018-20436/): Server-side request forgery in n/a (high 8.1)
- [CVE-2024-7014](https://insights.sbomify.com/CVE-2024-7014/): Improper multimedia file attachment validation in Telegram for Android app (high 7.1)
- [CVE-2021-31320](https://insights.sbomify.com/CVE-2021-31320/): Memory corruption in n/a (high 7.1)
- [CVE-2021-31321](https://insights.sbomify.com/CVE-2021-31321/): Memory corruption in n/a (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-10570 is a medium-severity vulnerability in n/a, published on 24 Mar 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-10570 in the wild and no public exploit code.

Affected product: n/a. 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-10570/ (Markdown: https://insights.sbomify.com/CVE-2020-10570/index.md)
```

## Sources

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

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