{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-6737 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-6737 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-6737 is a high-severity path traversal vulnerability in Bitdefender SafePay, published on 3 Jun 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-6737 and fix it if it is affected.\n\nWhat it is: CVE-2019-6737 is a high-severity path traversal vulnerability in Bitdefender SafePay, published on 3 Jun 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-6737 in the wild and no public exploit code.\n\nAffected product: Bitdefender SafePay. 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-6737/ (Markdown: https://insights.sbomify.com/CVE-2019-6737/index.md)","id":"CVE-2019-6737","markdown":"https://insights.sbomify.com/CVE-2019-6737/index.md","name":"CVE-2019-6737","record":{"aliases":["GHSA-qjm4-qw2v-5phj"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Bitdefender SafePay","requires_auth":"none","summary":"Remote attackers can execute arbitrary code via malicious files due to unsafe file handling in Bitdefender SafePay.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"zdi","cpe":[{"product":"safepay","vendor":"bitdefender"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-356","name":"Missing User Interaction for Potentially Unsafe Action"}],"description":"This vulnerability allows remote attackers to execute arbitrary code on vulnerable installations of Bitdefender SafePay 23.0.10.34. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the processing of TIScript. The issue lies in the handling of the openFile method, which allows for an arbitrary file write with attacker controlled data. An attacker can leverage this vulnerability execute code in the context of the current process. Was ZDI-CAN-7247.","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 SafePay","id":"CVE-2019-6737","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Command injection in SafePay","id":"CVE-2019-6738"},"packages":[],"prev":{"headline":"Command injection in SafePay","id":"CVE-2019-6736"},"products":["SafePay"],"published":"2019-06-03","related":[{"cvss_score":8.8,"headline":"Command injection in SafePay","id":"CVE-2019-6736","kev_date_added":null,"published":"2019-06-03"},{"cvss_score":8.8,"headline":"Command injection in SafePay","id":"CVE-2019-6738","kev_date_added":null,"published":"2019-06-03"},{"cvss_score":5.5,"headline":"Same-origin policy vulnerability in Bitdefender Safepay","id":"CVE-2020-15734","kev_date_added":null,"published":"2021-04-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":["Bitdefender"]},"summary":"Remote attackers can execute arbitrary code via malicious files due to unsafe file handling in Bitdefender SafePay.","url":"https://insights.sbomify.com/CVE-2019-6737/"}