{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-9230 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-9230 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-9230 is a critical vulnerability in n/a, published on 2 Apr 2018. 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-9230 and fix it if it is affected.\n\nWhat it is: CVE-2018-9230 is a critical vulnerability in n/a, published on 2 Apr 2018. 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-9230 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-9230/ (Markdown: https://insights.sbomify.com/CVE-2018-9230/index.md)","id":"CVE-2018-9230","markdown":"https://insights.sbomify.com/CVE-2018-9230/index.md","name":"CVE-2018-9230","record":{"aliases":["GHSA-fgf7-9g3w-445r"],"analysis":{"component_type":"server_software","fix_type":"configuration_change","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenResty web server","requires_auth":"none","summary":"Attackers can bypass Web Application Firewall protections by sending more than 100 URI parameters, which OpenResty ignores by default.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"openresty","vendor":"openresty"}],"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-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"In OpenResty through 1.13.6.1, URI parameters are obtained using the ngx.req.get_uri_args and ngx.req.get_post_args functions that ignore parameters beyond the hundredth one, which might allow remote attackers to bypass intended access restrictions or interfere with certain Web Application Firewall (ngx_lua_waf or X-WAF) products. NOTE: the vendor has reported that 100 parameters is an intentional default setting, but is adjustable within the API. The vendor's position is that a security-relevant misuse of the API by a WAF product is a vulnerability in the WAF product, not a vulnerability in OpenResty","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Security feature bypass in n/a","id":"CVE-2018-9230","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2018-9232"},"packages":[],"prev":{"headline":"FineUploader php-traditional-server unauthenticated arbitrary file upload vulnerability","id":"CVE-2018-9209"},"products":["n/a"],"published":"2018-04-02","related":[{"cvss_score":7.5,"headline":"OpenResty: Buffer overflow when writing PROXY protocol v2 header to upstream","id":"CVE-2026-55233","kev_date_added":null,"published":"2026-07-10"},{"cvss_score":5.9,"headline":"Denial of service in n/a","id":"CVE-2024-39702","kev_date_added":null,"published":"2024-07-23"}],"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 Web Application Firewall protections by sending more than 100 URI parameters, which OpenResty ignores by default.","url":"https://insights.sbomify.com/CVE-2018-9230/"}