By the Year
In 2022 there have been 0 vulnerabilities in Openresty . Last year Openresty had 1 security vulnerability published. Right now, Openresty is on track to have less security vulnerabilities in 2022 than it did last year.
It may take a day or so for new Openresty vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Openresty Security Vulnerabilities
A security issue in nginx resolver was identified, which might
9.4 - Critical
- June 01, 2021
A security issue in nginx resolver was identified, which might allow an attacker who is able to forge UDP packets from the DNS server to cause 1-byte memory overwrite, resulting in worker process crash or potential other impact.
An issue was discovered in OpenResty before 18.104.22.168
7.5 - High
- April 12, 2020
An issue was discovered in OpenResty before 22.214.171.124. ngx_http_lua_subrequest.c allows HTTP request smuggling, as demonstrated by the ngx.location.capture API.
HTTP Request Smuggling
** DISPUTED ** In OpenResty through 126.96.36.199, URI parameters are obtained using the ngx.req.get_uri_args and ngx.req.get_post_args functions
9.8 - Critical
- April 02, 2018
** DISPUTED ** In OpenResty through 188.8.131.52, 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.