{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-17102 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-17102 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-17102 is a high-severity vulnerability in Bitdefender BOX 2, published on 27 Jan 2020. 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-17102 and fix it if it is affected.\n\nWhat it is: CVE-2019-17102 is a high-severity vulnerability in Bitdefender BOX 2, published on 27 Jan 2020. 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-17102 in the wild and no public exploit code.\n\nAffected product: Bitdefender BOX 2. 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-17102/ (Markdown: https://insights.sbomify.com/CVE-2019-17102/index.md)","id":"CVE-2019-17102","markdown":"https://insights.sbomify.com/CVE-2019-17102/index.md","name":"CVE-2019-17102","record":{"aliases":["GHSA-j5g5-24v2-cpf4"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Bitdefender BOX 2","requires_auth":"none","summary":"A race condition in the recovery partition allows attackers to bypass firmware signature checks and execute arbitrary system commands on Bitdefender BOX 2 devices.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Bitdefender","cpe":[{"product":"box_2_firmware","vendor":"bitdefender"}],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-367","name":"Time-of-check Time-of-use (TOCTOU) Race Condition"},{"id":"CWE-413","name":"Improper Resource Locking"}],"description":"An exploitable command execution vulnerability exists in the recovery partition of Bitdefender BOX 2, version 2.0.1.91. The API method `/api/update_setup` does not perform firmware signature checks atomically, leading to an exploitable race condition (TOCTTOU) that allows arbitrary execution of system commands. This issue affects: Bitdefender Bitdefender BOX 2 versions prior to 2.1.47.36.","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":"Bitdefender BOX v2 bootstrap update_setup command execution vulnerability (VA-2226)","id":"CVE-2019-17102","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Get-task-allow entitlement via BDLDaemon on macOS","id":"CVE-2019-17103"},"packages":[],"prev":{"headline":"Command execution due to unsanitized input in Netatmo Smart Indoor Security Camera","id":"CVE-2019-17101"},"products":["Bitdefender BOX 2"],"published":"2020-01-27","related":[{"cvss_score":9,"headline":"Bitdefender BOX 2 bootstrap get_image_size command injection vulnerability","id":"CVE-2019-17096","kev_date_added":null,"published":"2020-01-28"},{"cvss_score":8.1,"headline":"Bitdefender BOX 2 bootstrap download_image command injection vulnerability","id":"CVE-2019-17095","kev_date_added":null,"published":"2020-01-27"}],"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":"A race condition in the recovery partition allows attackers to bypass firmware signature checks and execute arbitrary system commands on Bitdefender BOX 2 devices.","url":"https://insights.sbomify.com/CVE-2019-17102/"}