{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-12569 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-12569 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-12569 is a high-severity path traversal vulnerability in n/a, published on 3 Jun 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-12569 and fix it if it is affected.\n\nWhat it is: CVE-2019-12569 is a high-severity path traversal vulnerability in n/a, published on 3 Jun 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-12569 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-12569/ (Markdown: https://insights.sbomify.com/CVE-2019-12569/index.md)","id":"CVE-2019-12569","markdown":"https://insights.sbomify.com/CVE-2019-12569/index.md","name":"CVE-2019-12569","record":{"aliases":["GHSA-gp9r-j3mw-3g9f"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Viber Desktop","requires_auth":"none","summary":"An attacker can execute arbitrary commands by tricking a user into following a malicious link that loads libraries from an unsafe path.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"viber","vendor":"rakuten"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-426","name":"Untrusted Search Path"}],"description":"A vulnerability in Viber before 10.7.0 for Desktop (Windows) could allow an attacker to execute arbitrary commands on a targeted system. This vulnerability is due to unsafe search paths used by the application URI. An attacker could exploit this vulnerability by convincing a targeted user to follow a malicious link. Successful exploitation could cause the application to load libraries from the directory targeted by the URI link. The attacker could use this behavior to execute arbitrary commands on the system with the privileges of the targeted user, if the attacker can place a crafted library in a directory that is accessible to the vulnerable system.","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":"Path traversal in n/a","id":"CVE-2019-12569","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection in n/a","id":"CVE-2019-12570"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2019-12568"},"products":["n/a"],"published":"2019-06-03","related":[{"cvss_score":9.8,"headline":"Rakuten Viber uses broken or risky cryptographic Algorithm","id":"CVE-2025-13476","kev_date_added":null,"published":"2026-03-05"},{"cvss_score":8.8,"headline":"Information disclosure in n/a","id":"CVE-2019-18800","kev_date_added":null,"published":"2019-11-06"},{"cvss_score":7.5,"headline":"Other in n/a","id":"CVE-2020-14049","kev_date_added":null,"published":"2020-06-22"},{"cvss_score":6.3,"headline":"Cross-site scripting in n/a","id":"CVE-2025-55996","kev_date_added":null,"published":"2025-09-12"},{"cvss_score":4.2,"headline":"Information disclosure in Rakuten Viber","id":"CVE-2018-3987","kev_date_added":null,"published":"2020-02-12"}],"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 can execute arbitrary commands by tricking a user into following a malicious link that loads libraries from an unsafe path.","url":"https://insights.sbomify.com/CVE-2019-12569/"}