{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-12612 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-12612 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-12612 is a high-severity code injection vulnerability in n/a, published on 31 Oct 2019. 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-12612 and fix it if it is affected.\n\nWhat it is: CVE-2019-12612 is a high-severity code injection vulnerability in n/a, published on 31 Oct 2019. 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-12612 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-12612/ (Markdown: https://insights.sbomify.com/CVE-2019-12612/index.md)","id":"CVE-2019-12612","markdown":"https://insights.sbomify.com/CVE-2019-12612/index.md","name":"CVE-2019-12612","record":{"aliases":["GHSA-fq2g-9m6v-c9hw"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Bitdefender BOX firmware","requires_auth":"low_privilege","summary":"An attacker on the setup network can execute arbitrary code on Bitdefender BOX devices when they are in setup mode.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"box_firmware","vendor":"bitdefender"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"An issue was discovered in Bitdefender BOX firmware versions before 2.1.37.37-34 that allows an attacker to pass arbitrary code to the BOX appliance via the web API. In order to exploit this vulnerability, an attacker needs presence in Bitdefender BOX setup network and Bitdefender BOX be in setup mode.","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":"Code injection in n/a","id":"CVE-2019-12612","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2019-12613"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2019-12611"},"products":["n/a"],"published":"2019-10-31","related":[{"cvss_score":9.4,"headline":"Unauthenticated Command Injection in Bitdefender BOX v1","id":"CVE-2024-13871","kev_date_added":null,"published":"2025-03-12"},{"cvss_score":9.4,"headline":"Bitdefender Box Insecure Update Mechanism Vulnerability in libboxhermes.so","id":"CVE-2024-13872","kev_date_added":null,"published":"2025-03-12"},{"cvss_score":4.4,"headline":"Denial of service in n/a","id":"CVE-2019-12611","kev_date_added":null,"published":"2019-10-17"},{"cvss_score":1.8,"headline":"Unauthenticated Firmware Downgrade in Bitdefender Box v1","id":"CVE-2024-13870","kev_date_added":null,"published":"2025-03-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":"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 on the setup network can execute arbitrary code on Bitdefender BOX devices when they are in setup mode.","url":"https://insights.sbomify.com/CVE-2019-12612/"}