{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-4030 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-4030 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-4030 is a medium-severity 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-4030 and fix it if it is affected.\n\nWhat it is: CVE-2018-4030 is a medium-severity 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-4030 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-4030/ (Markdown: https://insights.sbomify.com/CVE-2018-4030/index.md)","id":"CVE-2018-4030","markdown":"https://insights.sbomify.com/CVE-2018-4030/index.md","name":"CVE-2018-4030","record":{"aliases":["GHSA-547r-pc3f-h39w"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"CUJO Smart Firewall","requires_auth":"none","summary":"Attackers can bypass the firewall's safe browsing protection by manipulating HTTP Host headers, allowing access to malicious websites.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"smart_firewall","vendor":"getcujo"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-444","name":"Inconsistent Interpretation of HTTP Requests"}],"description":"An exploitable vulnerability exists the safe browsing function of the CUJO Smart Firewall, version 7003. The bug lies in the way the safe browsing function parses HTTP requests. The \"Host\" header is incorrectly extracted from captured HTTP requests, which would allow an attacker to visit any malicious websites and bypass the firewall. An attacker could send an HTTP request to exploit 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":"Security feature bypass in CUJO","id":"CVE-2018-4030","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Code injection in CUJO","id":"CVE-2018-4031"},"packages":[],"prev":{"headline":"Memory corruption in Novatek","id":"CVE-2018-4029"},"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":"Use after free in CUJO","id":"CVE-2018-3985","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"}],"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":"Attackers can bypass the firewall's safe browsing protection by manipulating HTTP Host headers, allowing access to malicious websites.","url":"https://insights.sbomify.com/CVE-2018-4030/"}