{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-17613 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-17613 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-17613 is a critical vulnerability in n/a, published on 28 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-17613 and fix it if it is affected.\n\nWhat it is: CVE-2018-17613 is a critical vulnerability in n/a, published on 28 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-17613 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-17613/ (Markdown: https://insights.sbomify.com/CVE-2018-17613/index.md)","id":"CVE-2018-17613","markdown":"https://insights.sbomify.com/CVE-2018-17613/index.md","name":"CVE-2018-17613","record":{"aliases":["DEBIAN-CVE-2018-17613","GHSA-f948-97vm-63xw","UBUNTU-CVE-2018-17613"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Telegram Desktop","requires_auth":"none","summary":"Telegram Desktop sends credentials and data in cleartext over SOCKS5 when proxy is enabled, exposing sensitive information to network attackers.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"telegram_desktop","vendor":"telegram"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-522","name":"Insufficiently Protected Credentials"}],"description":"Telegram Desktop (aka tdesktop) 1.3.16 alpha, when \"Use proxy\" is enabled, sends credentials and application data in cleartext over the SOCKS5 protocol.","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":"Information disclosure in n/a","id":"CVE-2018-17613","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in Losant Arduino MQTT Client","id":"CVE-2018-17614"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2018-17612"},"products":["n/a"],"published":"2018-09-28","related":[{"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":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-05","vendors":["n/a"]},"summary":"Telegram Desktop sends credentials and data in cleartext over SOCKS5 when proxy is enabled, exposing sensitive information to network attackers.","url":"https://insights.sbomify.com/CVE-2018-17613/"}