{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-4026 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-4026 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-4026 is a high-severity 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-4026 and fix it if it is affected.\n\nWhat it is: CVE-2018-4026 is a high-severity 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-4026 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-4026/ (Markdown: https://insights.sbomify.com/CVE-2018-4026/index.md)","id":"CVE-2018-4026","markdown":"https://insights.sbomify.com/CVE-2018-4026/index.md","name":"CVE-2018-4026","record":{"aliases":["GHSA-h2jp-r7hc-h3mc"],"analysis":{"component_type":"hardware_firmware","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Dashcam firmware","requires_auth":"none","summary":"A specially crafted set of packets can cause an invalid memory dereference in the Anker Roav A1 Dashcam firmware, resulting in a device reboot.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"roav_dashcam_a1_firmware","vendor":"anker-in"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-754","name":"Improper Check for Unusual or Exceptional Conditions"}],"description":"An exploitable denial-of-service vulnerability exists in the XML_GetScreen Wi-Fi command of the NT9665X Chipset firmware, running on the Anker Roav A1 Dashcam, version RoavA1SWV1.9. A specially crafted set of packets can cause an invalid memory dereference, resulting in a device reboot.","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":"Null dereference in Novatek","id":"CVE-2018-4026","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in Novatek","id":"CVE-2018-4027"},"packages":[],"prev":{"headline":"Denial of service in Novatek","id":"CVE-2018-4025"},"products":["Novatek"],"published":"2019-05-13","related":[{"cvss_score":10,"headline":"File upload in Novatek","id":"CVE-2018-4018","kev_date_added":null,"published":"2019-05-13"},{"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":"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-05","vendors":["n/a"]},"summary":"A specially crafted set of packets can cause an invalid memory dereference in the Anker Roav A1 Dashcam firmware, resulting in a device reboot.","url":"https://insights.sbomify.com/CVE-2018-4026/"}