{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-4018 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-4018 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-4018 is a critical vulnerability in Novatek, published on 13 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-4018 and fix it if it is affected.\n\nWhat it is: CVE-2018-4018 is a critical vulnerability in Novatek, published on 13 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-4018 in the wild and no public exploit code.\n\nAffected product: Novatek. 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-2018-4018/ (Markdown: https://insights.sbomify.com/CVE-2018-4018/index.md)","id":"CVE-2018-4018","markdown":"https://insights.sbomify.com/CVE-2018-4018/index.md","name":"CVE-2018-4018","record":{"aliases":["GHSA-v2pp-7fp2-vfjg"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Dashcam firmware","requires_auth":"none","summary":"An attacker can upload arbitrary firmware binaries via HTTP PUT requests to the dashcam, leading to code execution upon reboot.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"roav_dashcam_a1_firmware","vendor":"anker-in"}],"cvss":{"score":10,"severity":"critical","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.0"},"cwes":[],"description":"An exploitable firmware update vulnerability exists in the NT9665X Chipset firmware, running on Anker Roav A1 Dashcam version RoavA1SWV1.9. The HTTP server allows for arbitrary firmware binaries to be uploaded which will be flashed upon next reboot. An attacker can send an HTTP PUT request or upgrade firmware request to trigger this vulnerability.","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":"File upload in Novatek","id":"CVE-2018-4018","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Command injection in Netgate pfSense","id":"CVE-2018-4019"},"packages":[],"prev":{"headline":"Hardcoded credentials in Anker","id":"CVE-2018-4017"},"products":["Novatek"],"published":"2019-05-13","related":[{"cvss_score":10,"headline":"Memory corruption in Novatek","id":"CVE-2018-4023","kev_date_added":null,"published":"2019-05-13"},{"cvss_score":10,"headline":"Memory corruption in Novatek","id":"CVE-2018-4029","kev_date_added":null,"published":"2019-05-13"},{"cvss_score":8,"headline":"Memory corruption in Anker","id":"CVE-2018-4014","kev_date_added":null,"published":"2019-05-13"},{"cvss_score":8,"headline":"Memory corruption in Anker","id":"CVE-2018-4016","kev_date_added":null,"published":"2019-05-13"},{"cvss_score":7.5,"headline":"Null dereference in Novatek","id":"CVE-2018-4024","kev_date_added":null,"published":"2019-05-13"},{"cvss_score":7.5,"headline":"Denial of service in Novatek","id":"CVE-2018-4025","kev_date_added":null,"published":"2019-05-13"}],"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-05","vendors":["n/a"]},"summary":"An attacker can upload arbitrary firmware binaries via HTTP PUT requests to the dashcam, leading to code execution upon reboot.","url":"https://insights.sbomify.com/CVE-2018-4018/"}