{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-19362 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-19362 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-19362 is a medium-severity vulnerability in n/a, published on 2 Dec 2019. 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-2019-19362 and fix it if it is affected.\n\nWhat it is: CVE-2019-19362 is a medium-severity vulnerability in n/a, published on 2 Dec 2019. 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-2019-19362 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-19362/ (Markdown: https://insights.sbomify.com/CVE-2019-19362/index.md)","id":"CVE-2019-19362","markdown":"https://insights.sbomify.com/CVE-2019-19362/index.md","name":"CVE-2019-19362","record":{"aliases":["GHSA-rjwh-hm8r-vg38"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"TeamViewer desktop app","requires_auth":"low_privilege","summary":"Local attackers with sufficient privileges can read sensitive chat data from memory after logout or history deletion in TeamViewer.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"teamviewer","vendor":"teamviewer"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.0/AC:L/AV:P/A:N/C:H/I:N/PR:L/S:U/UI:N","version":"3.0"},"cwes":[{"id":"CWE-212","name":"Improper Removal of Sensitive Information Before Storage or Transfer"}],"description":"An issue was discovered in the Chat functionality of the TeamViewer desktop application 14.3.4730 on Windows. (The vendor states that it was later fixed.) Upon login, every communication is saved within Windows main memory. When a user logs out or deletes conversation history (but does not exit the application), this data is not wiped from main memory, and therefore could be read by a local user with the same or greater privileges.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2019-19362","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2019-19363"},"packages":[],"prev":{"headline":"Netis WF2419 Devices Remote Code Execution","id":"CVE-2019-19356"},"products":["n/a"],"published":"2019-12-02","related":[{"cvss_score":7,"headline":"TeamViewer Desktop Bypass Remote Login","id":"CVE-2019-18988","kev_date_added":"2021-11-03","published":"2020-02-07"},{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2018-16550","kev_date_added":null,"published":"2018-09-05"},{"cvss_score":9.3,"headline":"Path traversal in n/a","id":"CVE-2010-3128","kev_date_added":null,"published":"2010-08-26"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2020-13699","kev_date_added":null,"published":"2020-07-29"},{"cvss_score":8.1,"headline":"Information disclosure in n/a","id":"CVE-2018-14333","kev_date_added":null,"published":"2018-07-17"},{"cvss_score":7.8,"headline":"Memory corruption in TeamViewer","id":"CVE-2021-34858","kev_date_added":null,"published":"2022-01-13"},{"cvss_score":7.8,"headline":"Memory corruption in TeamViewer","id":"CVE-2021-34859","kev_date_added":null,"published":"2021-10-25"}],"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":"Local attackers with sufficient privileges can read sensitive chat data from memory after logout or history deletion in TeamViewer.","url":"https://insights.sbomify.com/CVE-2019-19362/"}