{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-20849 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-20849 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-20849 is a medium-severity vulnerability in n/a, published on 19 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-20849 and fix it if it is affected.\n\nWhat it is: CVE-2019-20849 is a medium-severity vulnerability in n/a, published on 19 Jun 2020. 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-2019-20849 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-20849/ (Markdown: https://insights.sbomify.com/CVE-2019-20849/index.md)","id":"CVE-2019-20849","markdown":"https://insights.sbomify.com/CVE-2019-20849/index.md","name":"CVE-2019-20849","record":{"aliases":["GHSA-qhj6-chh8-8c88"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Mattermost Mobile App","requires_auth":"none","summary":"Attackers can access persistent cookie data on a device after a user logs out of the Mattermost mobile application.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mattermost_mobile","vendor":"mattermost"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-459","name":"Incomplete Cleanup"}],"description":"An issue was discovered in Mattermost Mobile Apps before 1.26.0. Cookie data can persist on a device after a logout.","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-2019-20849","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":"Information disclosure in n/a","id":"CVE-2019-20850"},"packages":[],"prev":{"headline":"Other in n/a","id":"CVE-2019-20848"},"products":["n/a"],"published":"2020-06-19","related":[{"cvss_score":7.5,"headline":"Other in n/a","id":"CVE-2019-20848","kev_date_added":null,"published":"2020-06-19"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2019-20852","kev_date_added":null,"published":"2020-06-19"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2020-14449","kev_date_added":null,"published":"2020-06-19"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2020-14451","kev_date_added":null,"published":"2020-06-19"},{"cvss_score":6.5,"headline":"Denial of Service Via Malicious GIF","id":"CVE-2025-1558","kev_date_added":null,"published":"2025-03-24"},{"cvss_score":6.5,"headline":"Mobile crash via improper validation of proto style in attachments","id":"CVE-2025-20072","kev_date_added":null,"published":"2025-01-16"},{"cvss_score":6.5,"headline":"Mobile crash via object that can't be cast to String in Attachment Field","id":"CVE-2025-20630","kev_date_added":null,"published":"2025-01-16"}],"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":"Attackers can access persistent cookie data on a device after a user logs out of the Mattermost mobile application.","url":"https://insights.sbomify.com/CVE-2019-20849/"}