A security issue was identified in nginx range filter. A specially crafted
request might result in an integer overflow and incorrect processing of
ranges, potentially resulting in sensitive information leak.
When using nginx with standard modules this allows an attacker to
obtain a cache file header if a response was returned from cache.
In some configurations a cache file header may contain IP address
of the backend server or other sensitive information.
Besides, with 3rd party modules it is potentially possible that
the issue may lead to a denial of service or a disclosure of
a worker process memory. No such modules are currently known though.
The issue affects nginx 0.5.6 - 1.13.2.
The issue is fixed in nginx 1.13.3, 1.12.1.
For older versions, the following configuration can be used
as a temporary workaround:
Patch for the issue can be found here:
Now in repository via https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d195ea6ec9933d558fecdfb30edebca2ea413c13
please test and mark stable: =www-servers/nginx-1.12.1
Maintainer(s), please cleanup.
Security, please vote.
Repository is now clean: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a10dc685fb4d5ab1d8f0ed6a5e6a0ec536552ace
GLSA Vote: No