# CVE-2019-10044: Other in n/a

> Telegram Desktop and mobile apps allow IDN homograph attacks, enabling users to be tricked into visiting malicious URLs disguised as legitimate ones.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 25 Mar 2019
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-10044, GHSA-9gmh-43p9-37g6, UBUNTU-CVE-2019-10044

## What is CVE-2019-10044?

CVE-2019-10044 is a high-severity vulnerability in n/a, published on 25 Mar 2019. 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 before 1.5.12 on Windows, and the Telegram applications for Android, iOS, and Linux, is vulnerable to an IDN homograph attack when displaying messages containing URLs. This occurs because the application produces a clickable link even if (for example) Latin and Cyrillic characters exist in the same domain name, and the available font has an identical representation of characters from different alphabets.

## Which versions are affected by CVE-2019-10044?

It affects 2 products.


Products: Telegram Telegram, Telegram Telegram Desktop.

## How do I fix CVE-2019-10044?

Upgrade to a fixed version.

## Is CVE-2019-10044 being exploited?

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

## Other vulnerabilities in n/a

- [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)
- [CVE-2018-15543](https://insights.sbomify.com/CVE-2018-15543/): Auth bypass in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-10044 and fix it if it is affected.

What it is: CVE-2019-10044 is a high-severity vulnerability in n/a, published on 25 Mar 2019. 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-2019-10044 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-2019-10044/ (Markdown: https://insights.sbomify.com/CVE-2019-10044/index.md)
```

## Sources

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

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