NginxWeb server / proxy · F5
CVE-2017-7529
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedNginx versions since 0.5.6 up to and including 1.13.2 are vulnerable to integer overflow vulnerability in nginx range filter module resulting into leak of potentially sensitive information triggered by specially crafted request.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA signed integer overflow vulnerability exists in nginx's range filter module (ngx_http_range_parse) from version 0.5.6 through 1.13.2. By sending a crafted HTTP Range request with overlapping or negative range values, an attacker can cause the module to miscalculate buffer sizes, potentially allowing exfiltration of sensitive files from the server such as /proc/self/environ or other process-accessible files.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
NginxWeb server / proxy
>= 0.5.6, <= 1.12.1>= 1.13.0, <= 1.13.2< 2016.4.7>= 2017.1.0, <= 2017.1.1>= 2017.2.1, <= 2017.2.3< 13.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed nginx versionRun 'nginx -v' or 'nginx -V 2>&1 | grep version' to obtain the exact version number. For F5 Nginx, check the package manager or installed RPM/DEB. For Puppet Enterprise, check /opt/puppetlabs/server/bin/nginx -v or the installed package version.Affected if Version is 0.5.6 through 1.13.2 inclusive, or matches the specific F5/Apple/Puppet Enterprise ranges in the CVE (F5 >= 0.5.6 <= 1.12.1, F5 >= 1.13.0 <= 1.13.2; Puppet < 2016.4.7, 2017.1.0-2017.1.1, 2017.2.1-2017.2.3; Apple Xcode < 13.0).
-
Verify range request handling is enabledSearch nginx configuration files (nginx.conf, included conf files) for the 'max_ranges' directive. Run: grep -r 'max_ranges' /etc/nginx/ or review your nginx configuration.Affected if The directive 'max_ranges 0;' is NOT present, meaning range requests are still processed by nginx.
-
Confirm nginx is exposed to untrusted HTTP clientsCheck network configuration to verify nginx listens on a port accessible to clients (including as a reverse proxy). Review listen directives in nginx config and firewall rules.Affected if Nginx is accessible over HTTP/HTTPS from network clients and the previous version check shows an affected version.
You are affected if nginx (or the bundled nginx in F5/Puppet/Apple) is version 0.5.6 through 1.13.2 AND range requests are not explicitly disabled with 'max_ranges 0;' in the configuration.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data13.02016.4.7
Upgrade nginx to version 1.13.3 or later (or 1.12.1 for the 1.12.x stable branch) to patch the integer overflow. If immediate upgrade is not possible, disable range requests using 'max_ranges 0;' as a temporary mitigation.
Fix this in Nginx
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7529 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-7529 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data