{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-8102 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-8102 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-8102 is a high-severity command injection vulnerability in Bitdefender Total Security 2020, published on 22 Jun 2020. 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-2020-8102 and fix it if it is affected.\n\nWhat it is: CVE-2020-8102 is a high-severity command injection vulnerability in Bitdefender Total Security 2020, published on 22 Jun 2020. 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-2020-8102 in the wild and no public exploit code.\n\nAffected product: Bitdefender Total Security 2020. 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-8102/ (Markdown: https://insights.sbomify.com/CVE-2020-8102/index.md)","id":"CVE-2020-8102","markdown":"https://insights.sbomify.com/CVE-2020-8102/index.md","name":"CVE-2020-8102","record":{"aliases":["GHSA-frgh-7pf4-6v6f"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Bitdefender Total Security","requires_auth":"none","summary":"An attacker can execute remote commands in the Safepay Utility process via a crafted web page due to insufficient URL validation in Bitdefender Total Security.","user_interaction":"required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Bitdefender","cpe":[{"product":"total_security_2020","vendor":"bitdefender"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Improper Input Validation vulnerability in the Safepay browser component of Bitdefender Total Security 2020 allows an external, specially crafted web page to run remote commands inside the Safepay Utility process. This issue affects Bitdefender Total Security 2020 versions prior to 24.0.20.116.","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":"Insufficient URL sanitization and validation in Safepay Browser (VA-8631)","id":"CVE-2020-8102","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Link Resolution Privilege Escalation Vulnerability in Bitdefender Antivirus Free (VA-8604)","id":"CVE-2020-8103"},"packages":[],"prev":{"headline":"Command execution due to unsanitized input in LifeShield DIY HD Video Doorbell","id":"CVE-2020-8101"},"products":["Bitdefender Total Security 2020"],"published":"2020-06-22","related":[{"cvss_score":5.2,"headline":"Untrusted Search Path vulnerability in Bitdefender Total Security 2020 (VA-5895)","id":"CVE-2019-17100","kev_date_added":null,"published":"2020-01-27"},{"cvss_score":4.9,"headline":"Bitdefender Total Security Link Resolution Denial-of-Service Vulnerability","id":"CVE-2020-8095","kev_date_added":null,"published":"2020-01-30"}],"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-09-17","vendors":["Bitdefender"]},"summary":"An attacker can execute remote commands in the Safepay Utility process via a crafted web page due to insufficient URL validation in Bitdefender Total Security.","url":"https://insights.sbomify.com/CVE-2020-8102/"}