{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-17448 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2020-17448 is a high-severity vulnerability in n/a, published on 11 Aug 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-17448 and fix it if it is affected.\n\nWhat it is: CVE-2020-17448 is a high-severity vulnerability in n/a, published on 11 Aug 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-17448 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-2020-17448/ (Markdown: https://insights.sbomify.com/CVE-2020-17448/index.md)","id":"CVE-2020-17448","markdown":"https://insights.sbomify.com/CVE-2020-17448/index.md","name":"CVE-2020-17448","record":{"aliases":["DEBIAN-CVE-2020-17448","GHSA-ccch-f948-2h8c","UBUNTU-CVE-2020-17448"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Telegram Desktop","requires_auth":"none","summary":"Attackers can bypass dangerous file type execution protections in Telegram Desktop by using filenames without extensions, potentially leading to malicious file execution.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"telegram_desktop","vendor":"telegram"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"Telegram Desktop through 2.1.13 allows a spoofed file type to bypass the Dangerous File Type Execution protection mechanism, as demonstrated by use of the chat window with a filename that lacks an extension.","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":"Security feature bypass in n/a","id":"CVE-2020-17448","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2020"},"n_packages":0,"n_references":4,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2020-17449"},"packages":[],"prev":{"headline":"Asyncpg Arbitrary Code Execution Via Access to an Uninitialized Pointer","id":"CVE-2020-17446"},"products":["n/a"],"published":"2020-08-11","related":[{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2018-17613","kev_date_added":null,"published":"2018-09-28"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2018-17231","kev_date_added":null,"published":"2018-09-19"},{"cvss_score":6.5,"headline":"Information disclosure in n/a","id":"CVE-2018-17780","kev_date_added":null,"published":"2018-09-29"},{"cvss_score":4.6,"headline":"Telegram Desktop 2.9.2 - Denial of Service (PoC)","id":"CVE-2021-47793","kev_date_added":null,"published":"2026-01-15"},{"cvss_score":2.4,"headline":"Missing authorization in n/a","id":"CVE-2020-25824","kev_date_added":null,"published":"2020-10-14"}],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"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":"Attackers can bypass dangerous file type execution protections in Telegram Desktop by using filenames without extensions, potentially leading to malicious file execution.","url":"https://insights.sbomify.com/CVE-2020-17448/"}