{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-17231 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-17231 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-17231 is a high-severity denial of service vulnerability in n/a, published on 19 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-17231 and fix it if it is affected.\n\nWhat it is: CVE-2018-17231 is a high-severity denial of service vulnerability in n/a, published on 19 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-17231 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-2018-17231/ (Markdown: https://insights.sbomify.com/CVE-2018-17231/index.md)","id":"CVE-2018-17231","markdown":"https://insights.sbomify.com/CVE-2018-17231/index.md","name":"CVE-2018-17231","record":{"aliases":["DEBIAN-CVE-2018-17231","GHSA-fh6g-c662-cccm"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Telegram Desktop","requires_auth":"none","summary":"Attackers can cause Telegram Desktop to crash via a specific search input, though the issue is disputed as it does not cross privilege boundaries.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"telegram_desktop","vendor":"telegram"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-617","name":"Reachable Assertion"}],"description":"Telegram Desktop (aka tdesktop) 1.3.14 might allow attackers to cause a denial of service (assertion failure and application exit) via an \"Edit color palette\" search that triggers an \"index out of range\" condition. NOTE: this issue is disputed by multiple third parties because the described attack scenario does not cross a privilege boundary","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Denial of service in n/a","id":"CVE-2018-17231","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection in n/a","id":"CVE-2018-17232"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2018-17230"},"products":["n/a"],"published":"2018-09-19","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.8,"headline":"Security feature bypass in n/a","id":"CVE-2020-17448","kev_date_added":null,"published":"2020-08-11"},{"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-09-16","vendors":["n/a"]},"summary":"Attackers can cause Telegram Desktop to crash via a specific search input, though the issue is disputed as it does not cross privilege boundaries.","url":"https://insights.sbomify.com/CVE-2018-17231/"}