# CVE-2020-12474: Other in n/a

> Attackers can spoof trusted domains using IDN homograph attacks in Telegram URLs, potentially deceiving users into visiting malicious sites.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 1 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2020-12474, GHSA-mf6c-m6cw-6m7x, UBUNTU-CVE-2020-12474

## What is CVE-2020-12474?

CVE-2020-12474 is a medium-severity vulnerability in n/a, published on 1 May 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Telegram Desktop through 2.0.1, Telegram through 6.0.1 for Android, and Telegram through 6.0.1 for iOS allow an IDN Homograph attack via Punycode in a public URL or a group chat invitation URL.

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

It affects 2 products.


Products: Telegram Telegram, Telegram Telegram Desktop.

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

Upgrade to a fixed version.

## Is CVE-2020-12474 being exploited?

There is no known exploitation of CVE-2020-12474 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-12474 and fix it if it is affected.

What it is: CVE-2020-12474 is a medium-severity vulnerability in n/a, published on 1 May 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-12474 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-12474/ (Markdown: https://insights.sbomify.com/CVE-2020-12474/index.md)
```

## Sources

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

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