{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-3985 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-3985 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-3985 is a high-severity use after free vulnerability in CUJO, published on 21 Mar 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-3985 and fix it if it is affected.\n\nWhat it is: CVE-2018-3985 is a high-severity use after free vulnerability in CUJO, published on 21 Mar 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-3985 in the wild and no public exploit code.\n\nAffected product: CUJO. 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-3985/ (Markdown: https://insights.sbomify.com/CVE-2018-3985/index.md)","id":"CVE-2018-3985","markdown":"https://insights.sbomify.com/CVE-2018-3985/index.md","name":"CVE-2018-3985","record":{"aliases":["GHSA-x6vq-vc9q-792p"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"CUJO Smart Firewall","requires_auth":"none","summary":"An unauthenticated attacker can achieve arbitrary code execution on the CUJO Smart Firewall by sending a malicious mDNS packet that triggers a double free vulnerability.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"smart_firewall","vendor":"getcujo"}],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L","version":"3.0"},"cwes":[{"id":"CWE-415","name":"Double Free"}],"description":"An exploitable double free vulnerability exists in the mdnscap binary of the CUJO Smart Firewall. When parsing mDNS packets, a memory space is freed twice if an invalid query name is encountered, leading to arbitrary code execution in the context of the mdnscap process. An unauthenticated attacker can send an mDNS message 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":"Use after free in CUJO","id":"CVE-2018-3985","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in Telegram","id":"CVE-2018-3986"},"packages":[],"prev":{"headline":"Memory corruption in Atlantis Word Processor","id":"CVE-2018-3984"},"products":["CUJO"],"published":"2019-03-21","related":[{"cvss_score":9,"headline":"Code injection in CUJO","id":"CVE-2018-4031","kev_date_added":null,"published":"2019-10-31"},{"cvss_score":9,"headline":"Command injection in CUJO","id":"CVE-2018-3963","kev_date_added":null,"published":"2019-03-21"},{"cvss_score":8.3,"headline":"Memory corruption in CUJO","id":"CVE-2018-4003","kev_date_added":null,"published":"2019-03-21"},{"cvss_score":8.2,"headline":"Command injection in CUJO","id":"CVE-2018-3969","kev_date_added":null,"published":"2019-03-21"},{"cvss_score":6.5,"headline":"Integer overflow in CUJO","id":"CVE-2018-4011","kev_date_added":null,"published":"2019-03-21"},{"cvss_score":5.3,"headline":"Security feature bypass in CUJO","id":"CVE-2018-4030","kev_date_added":null,"published":"2019-03-21"}],"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":"An unauthenticated attacker can achieve arbitrary code execution on the CUJO Smart Firewall by sending a malicious mDNS packet that triggers a double free vulnerability.","url":"https://insights.sbomify.com/CVE-2018-3985/"}