# What is CVE-2017-7529? > CVE-2017-7529 is a high-severity flaw (CVSS 7.5) in Nginx from F5, published on 13 July 2017. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 63%. If you run an affected version, plan in the vendor’s fix. Canonical page: https://www.precursorintelligence.com/what-is/cve-2017-7529 ## At a glance - **Verdict:** Fix this soon. Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month. - **Precursor Intelligence risk score:** 55 out of 100 (Medium); action: Plan remediation. Kept up to date as the evidence changes. - **Severity:** High (CVSS 7.5 out of 10) - **Known to be exploited:** No, not on the list of flaws known to be exploited today - **Chance of use in the next 30 days:** 63% (latest exploit-likelihood forecast) - **Published:** 13 July 2017 - **Record last updated:** 20 April 2025 - **Main product:** Nginx from F5 - **Affected products:** 3 ## What is CVE-2017-7529? In plain terms It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data. ### The official description 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. ### What kind of flaw is it? - CWE-190: Integer Overflow or Wraparound ### How an attack on it works - Where an attacker can be: Anywhere on the internet - How hard it is to pull off: Easy: no special conditions - Login needed first: No login needed - Does someone have to click: No, nobody has to do anything - What an attacker gets: Can read data Severity vector: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N` ## Is CVE-2017-7529 being exploited? Not that we know of It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 63%. That can change at any time, which is why we keep watching. Exploit likelihood over the last 7 days: 63%, 63%, 63%, 63%, 63%, 63%, 63%. ### Timeline - 13 July 2017: Published - 20 April 2025: Record last updated - 16 June 2026: Exploit likelihood fell ### How Precursor Intelligence ranks it CVE-2017-7529 scores **55 out of 100 (Medium)**, with the action "Plan remediation". Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less: - Evidence it is being exploited: biggest factor - How severe it is: strong factor - How widely exposed it is: smaller factor - Threat activity around it: smaller factor 85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it. ## Who is affected by CVE-2017-7529? The published record lists 3 products. Versions are as published: "before 2016.4.7" means every version up to, but not including, 2016.4.7. - [Nginx](https://www.precursorintelligence.com/product/f5/nginx) by [F5](https://www.precursorintelligence.com/vendors/f5) (Application): 0.5.6 to 1.12.1, 1.13.0 to 1.13.2 - [Puppet Enterprise](https://www.precursorintelligence.com/product/puppet/puppet_enterprise) by [Puppet](https://www.precursorintelligence.com/vendors/puppet) (Application): before 2016.4.7, 2017.1.0 to 2017.1.1, 2017.2.1 to 2017.2.3 - [Xcode](https://www.precursorintelligence.com/product/apple/xcode) by [Apple](https://www.precursorintelligence.com/vendors/apple) (Application): before 13.0 ## How do I fix CVE-2017-7529? 1. **Check whether you run it.** Compare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list. 2. **Apply the vendor’s fix.** Install the update named in the vendor’s advisory. We’ve put the advisory first in the list. 3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in. 4. **Keep an eye on it.** Track the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood. ### References - [mailman.nginx.org](http://mailman.nginx.org/pipermail/nginx-announce/2017/000200.html) (Vendor advisory) - [seclists.org](http://seclists.org/fulldisclosure/2021/Sep/36) (Mailing list, Third-party advisory) - [securityfocus.com](http://www.securityfocus.com/bid/99534) (Third-party advisory, Vulnerability database) - [securitytracker.com](http://www.securitytracker.com/id/1039238) (Third-party advisory, Vulnerability database) - [access.redhat.com](https://access.redhat.com/errata/RHSA-2017:2538) (Third-party advisory) - [puppet.com](https://puppet.com/security/cve/cve-2017-7529) (Third-party advisory) - [support.apple.com](https://support.apple.com/kb/HT212818) (Third-party advisory) ## Questions ### What is CVE-2017-7529? CVE-2017-7529 is a high-severity flaw in Nginx from F5, published on 13 July 2017. It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data. ### How serious is CVE-2017-7529? It scores 7.5 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2017-7529 is 55 out of 100, which is Medium. Its action is "Plan remediation". Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month. ### Is CVE-2017-7529 being exploited? It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 63%. That can change at any time, which is why we keep watching. ### Which versions does CVE-2017-7529 affect? For Nginx from F5: 0.5.6 to 1.12.1, 1.13.0 to 1.13.2. The record lists 3 products in all, each with its versions, under "Who is affected" on this page. ### How do I fix CVE-2017-7529? Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet. ## Does CVE-2017-7529 affect you? Precursor Intelligence keeps checking for you: - **Tell us what you run.** Pick your software from a list, or let us work it out from your website. - **We match it to every flaw.** Over 400,000 published flaws, checked against your list. - **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it. - **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools. Start free (no card, nothing to install): https://www.precursorintelligence.com/register Book a demo: https://www.precursorintelligence.com/contact