CVE-2019-10044 Details
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.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/blazeinfosec/advisories/blob/master/telegram-advisory.txt | CVE | ExploitThird Party Advisory |
| http://www.securityfocus.com/bid/107610 | CVE | Third Party AdvisoryVDB Entry |
| https://github.com/blazeinfosec/advisories/blob/master/telegram-advisory.txt | [email protected] | ExploitThird Party Advisory |
| http://www.securityfocus.com/bid/107610 | [email protected] | Third Party AdvisoryVDB Entry |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| telegram telegram | All versions |
CPE
Remediation
| |
| telegram telegram desktop | < 1.5.12 |
CPE
Remediation
| |
| microsoft windows | All versions |
CPE
Remediation
| |
Change History
6 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Nov 21, 2024 | CVE Modified | CVE |
| May 14, 2024 | CVE Modified | [email protected] |
| Jul 21, 2021 | CWE Remap | [email protected] |
| Apr 8, 2019 | Initial Analysis | [email protected] |
| Mar 29, 2019 | CVE Modified | [email protected] |