CVE-2017-7529
Nginx 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.
- CVSS
- 7.5High
- Exploited in the wild
- Not knownUnvetted proof-of-concept code on GitHub; not in CISA KEV
- EPSS
- 62.6%chance of exploitation in the next 30 daystop 0.8% of scored CVEsFIRST score of 11 Nov 2026
- Fix
- Patch availablesee the advisories in the references
- Published
- 13 Jul 2017analysed here 12 Nov 2026
Summary
Triage
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
Products named in our analysis
- f5:nginx
- puppet:puppet_enterprise
- apple:xcode
Fix and mitigation
WAF and other mitigations
Can a WAF block it? No. This is an integer overflow, usually triggered by an ordinary-looking number or size. Generic WAF rules do not recognise it; only a rule written for this specific CVE can.
Also consider: patch
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Not listed as of our last sync.
- Public exploit code
- Unvetted proof-of-concept code on GitHub: 18 GitHub proofs of concept
GitHub proofs of concept
- en0f/CVE-2017-7529_PoC19 stars
- liusec/CVE-2017-752916 stars
- gemboxteam/exploit-nginx-1.10.312 stars
- Shehzadcyber/CVE-2017-752911 stars
and 14 more repositories
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
Timeline
- 13 Jul 2017Published
- 19 Jul 2017First proof-of-concept repository on GitHub (unvetted)5 days later
- 16 Sept 2024CVE record last updated2,617 days (about 7 years) later
- 12 Nov 2026Analysed by vulneraibility.com787 days (about 2 years) later
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
| Metric | Value | What it means |
|---|---|---|
| Attack vector | NetworkReachable over the internet or any routable network. | Reachable over the internet or any routable network. |
| Attack complexity | LowRepeatable attack, no special conditions. | Repeatable attack, no special conditions. |
| Privileges required | NoneThe attacker needs no prior access. | The attacker needs no prior access. |
| User interaction | NoneNo victim action needed. | No victim action needed. |
| Scope | UnchangedImpact stays within the vulnerable component. | Impact stays within the vulnerable component. |
| Confidentiality | HighTotal data disclosure possible. | Total data disclosure possible. |
| Integrity | NoneNo unauthorised modification. | No unauthorised modification. |
| Availability | NoneThe service stays up. | The service stays up. |
Common questions
Is CVE-2017-7529 being exploited?
Not confirmed. CVE-2017-7529 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 63% probability of exploitation in the next 30 days.
How severe is CVE-2017-7529?
CVE-2017-7529 is rated High with a CVSS score of 7.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2017-7529?
Yes. A fix has been recorded for CVE-2017-7529. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2017-7529 affect?
CVE-2017-7529 affects f5:nginx, puppet:puppet_enterprise, apple:xcode. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
7 references in the CVE record, grouped by the tags the record gives them.
Advisories (1)
- access.redhat.com /errata/RHSA-2017:2538
Other links (6)
- mailman.nginx.org /pipermail/nginx-announce/2017/000200.html
- securityfocus.com /bid/99534
- securitytracker.com /id/1039238
- puppet.com /security/cve/cve-2017-7529
- support.apple.com /kb/HT212818
- seclists.org /fulldisclosure/2021/Sep/36
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- FIRST EPSS: exploit probability and percentile
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.