{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-14496 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-14496 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-14496 is a critical memory corruption vulnerability in n/a, published on 10 Jul 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-14496 and fix it if it is affected.\n\nWhat it is: CVE-2018-14496 is a critical memory corruption vulnerability in n/a, published on 10 Jul 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-14496 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-2018-14496/ (Markdown: https://insights.sbomify.com/CVE-2018-14496/index.md)","id":"CVE-2018-14496","markdown":"https://insights.sbomify.com/CVE-2018-14496/index.md","name":"CVE-2018-14496","record":{"aliases":["GHSA-53j5-53wj-w2fg"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Vivotek IP camera","requires_auth":"none","summary":"Remote attackers can execute arbitrary code on Vivotek FD8136 cameras via a stack-based buffer overflow in set_getparam.cgi.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"fd8136_firmware","vendor":"vivotek"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"Vivotek FD8136 devices allow remote memory corruption and remote code execution because of a stack-based buffer overflow, related to sprintf, vlocal_buff_4326, and set_getparam.cgi. NOTE: The vendor has disputed this as a vulnerability and states that the issue does not cause a web server crash or have any other affect on it's performance","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":"Memory corruption in n/a","id":"CVE-2018-14496","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-14497"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2018-14495"},"products":["n/a"],"published":"2019-07-10","related":[{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2018-14494","kev_date_added":null,"published":"2019-07-10"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2018-14495","kev_date_added":null,"published":"2019-07-10"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2026-30650","kev_date_added":null,"published":"2026-06-02"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2026-30652","kev_date_added":null,"published":"2026-06-02"},{"cvss_score":7.3,"headline":"Memory corruption in n/a","id":"CVE-2026-30649","kev_date_added":null,"published":"2026-06-02"},{"cvss_score":6.5,"headline":"Path traversal in n/a","id":"CVE-2026-35718","kev_date_added":null,"published":"2026-06-02"}],"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":"Remote attackers can execute arbitrary code on Vivotek FD8136 cameras via a stack-based buffer overflow in set_getparam.cgi.","url":"https://insights.sbomify.com/CVE-2018-14496/"}