{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-25824 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-25824 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-25824 is a low-severity missing authorization vulnerability in n/a, published on 14 Oct 2020. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-25824 and fix it if it is affected.\n\nWhat it is: CVE-2020-25824 is a low-severity missing authorization vulnerability in n/a, published on 14 Oct 2020. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-25824 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-25824/ (Markdown: https://insights.sbomify.com/CVE-2020-25824/index.md)","id":"CVE-2020-25824","markdown":"https://insights.sbomify.com/CVE-2020-25824/index.md","name":"CVE-2020-25824","record":{"aliases":["GHSA-hq26-6p72-9jg4"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Telegram Desktop","requires_auth":"none","summary":"An attacker with physical access can export all chat data without a passcode if the export wizard is open, leading to information disclosure.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"telegram_desktop","vendor":"telegram"}],"cvss":{"score":2.4,"severity":"low","source":"nvd","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"Telegram Desktop through 2.4.3 does not require passcode entry upon pushing the Export key within the Export Telegram Data wizard. The threat model is a victim who has voluntarily opened Export Wizard but is then distracted. An attacker then approaches the unattended desktop and pushes the Export key. This attacker may consequently gain access to all chat conversation and media files.","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":"Missing authorization in n/a","id":"CVE-2020-25824","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2020"},"n_packages":0,"n_references":4,"next":{"headline":"Information disclosure in n/a","id":"CVE-2020-25825"},"packages":[],"prev":{"headline":"Null dereference in n/a","id":"CVE-2020-25821"},"products":["n/a"],"published":"2020-10-14","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":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"}],"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":"An attacker with physical access can export all chat data without a passcode if the export wizard is open, leading to information disclosure.","url":"https://insights.sbomify.com/CVE-2020-25824/"}