{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-10044 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"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."},"fix_prompt":"Check this codebase for CVE-2019-10044 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2019-10044 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2019-10044/ (Markdown: https://insights.sbomify.com/CVE-2019-10044/index.md)","id":"CVE-2019-10044","markdown":"https://insights.sbomify.com/CVE-2019-10044/index.md","name":"CVE-2019-10044","record":{"aliases":["DEBIAN-CVE-2019-10044","GHSA-9gmh-43p9-37g6","UBUNTU-CVE-2019-10044"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Telegram Desktop","requires_auth":"none","summary":"Telegram Desktop and mobile apps allow IDN homograph attacks, enabling users to be tricked into visiting malicious URLs disguised as legitimate ones.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"telegram","vendor":"telegram"},{"product":"telegram_desktop","vendor":"telegram"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Other in n/a","id":"CVE-2019-10044","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2019-10045"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2019-10042"},"products":["n/a"],"published":"2019-03-25","related":[{"cvss_score":8.1,"headline":"Server-side request forgery in n/a","id":"CVE-2018-20436","kev_date_added":null,"published":"2018-12-24"},{"cvss_score":7.1,"headline":"Improper multimedia file attachment validation in Telegram for Android app","id":"CVE-2024-7014","kev_date_added":null,"published":"2024-07-23"},{"cvss_score":7.1,"headline":"Memory corruption in n/a","id":"CVE-2021-31320","kev_date_added":null,"published":"2021-05-18"},{"cvss_score":7.1,"headline":"Memory corruption in n/a","id":"CVE-2021-31321","kev_date_added":null,"published":"2021-05-18"},{"cvss_score":6.8,"headline":"Auth bypass in n/a","id":"CVE-2018-15543","kev_date_added":null,"published":"2018-10-09"},{"cvss_score":6.5,"headline":"Other in n/a","id":"CVE-2020-12474","kev_date_added":null,"published":"2020-05-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Telegram Desktop and mobile apps allow IDN homograph attacks, enabling users to be tricked into visiting malicious URLs disguised as legitimate ones.","url":"https://insights.sbomify.com/CVE-2019-10044/"}