{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-24395 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-24395 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-24395 is a medium-severity code injection vulnerability in n/a, published on 20 May 2021. 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-2020-24395 and fix it if it is affected.\n\nWhat it is: CVE-2020-24395 is a medium-severity code injection vulnerability in n/a, published on 20 May 2021. 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-2020-24395 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-2020-24395/ (Markdown: https://insights.sbomify.com/CVE-2020-24395/index.md)","id":"CVE-2020-24395","markdown":"https://insights.sbomify.com/CVE-2020-24395/index.md","name":"CVE-2020-24395","record":{"aliases":["GHSA-mw35-grpm-83j9"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"homee Brain Cube","requires_auth":"none","summary":"An attacker with physical access can install compromised firmware on homee Brain Cube devices due to insufficient validation, leading to code execution.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"brain_cube_core","vendor":"hom.ee"}],"cvss":{"score":6.8,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"The USB firmware update script of homee Brain Cube v2 (2.28.2 and 2.28.4) devices allows an attacker with physical access to install compromised firmware. This occurs because of insufficient validation of the firmware image file and can lead to code execution on the device.","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-2020-24395","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2020-24396"},"packages":[],"prev":{"headline":"Misconfiguration in n/a","id":"CVE-2020-24394"},"products":["n/a"],"published":"2021-05-20","related":[{"cvss_score":7.5,"headline":"Hardcoded credentials in n/a","id":"CVE-2020-24396","kev_date_added":null,"published":"2021-05-20"},{"cvss_score":6.8,"headline":"Auth bypass in n/a","id":"CVE-2019-16258","kev_date_added":null,"published":"2020-03-20"}],"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 with physical access can install compromised firmware on homee Brain Cube devices due to insufficient validation, leading to code execution.","url":"https://insights.sbomify.com/CVE-2020-24395/"}