# CVE-2017-7529: Integer overflow in nginx

> An integer overflow in the Nginx range filter module allows attackers to leak sensitive information via specially crafted requests.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Jul 2017
- **Updated:** 16 Sep 2024
- **Also known as:** ALPINE-CVE-2017-7529, CLEANSTART-2026-IH30576, DEBIAN-CVE-2017-7529, DLA-1024-1, DSA-3908-1, GHSA-85mj-h68w-w736, MGASA-2017-0231, RHSA-2017:2538, SUSE-SU-2017:2387-1, UBUNTU-CVE-2017-7529, USN-3352-1, openSUSE-SU-2018:0813-1

## What is CVE-2017-7529?

CVE-2017-7529 is a high-severity vulnerability in Apple Xcode, published on 13 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### 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.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2017-7529?

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rh-nginx110-nginx` | Red Hat:rhel_software_collections:2::el6 | All versions | 1:1.10.2-8.el6 |
| `rh-nginx110-nginx-debuginfo` | Red Hat:rhel_software_collections:2::el6 | All versions | 1:1.10.2-8.el6 |
| `rh-nginx110-nginx-mod-http-image-filter` | Red Hat:rhel_software_collections:2::el6 | All versions | 1:1.10.2-8.el6 |
| `rh-nginx110-nginx-mod-http-perl` | Red Hat:rhel_software_collections:2::el6 | All versions | 1:1.10.2-8.el6 |
| `rh-nginx110-nginx-mod-http-xslt-filter` | Red Hat:rhel_software_collections:2::el6 | All versions | 1:1.10.2-8.el6 |
| `rh-nginx110-nginx-mod-mail` | Red Hat:rhel_software_collections:2::el6 | All versions | 1:1.10.2-8.el6 |
| `rh-nginx110-nginx-mod-stream` | Red Hat:rhel_software_collections:2::el6 | All versions | 1:1.10.2-8.el6 |
| `rh-nginx110-nginx` | Red Hat:rhel_software_collections:2::el7 | All versions | 1:1.10.2-8.el7 |
| `rh-nginx110-nginx-debuginfo` | Red Hat:rhel_software_collections:2::el7 | All versions | 1:1.10.2-8.el7 |
| `rh-nginx110-nginx-mod-http-image-filter` | Red Hat:rhel_software_collections:2::el7 | All versions | 1:1.10.2-8.el7 |
| `rh-nginx110-nginx-mod-http-perl` | Red Hat:rhel_software_collections:2::el7 | All versions | 1:1.10.2-8.el7 |
| `rh-nginx110-nginx-mod-http-xslt-filter` | Red Hat:rhel_software_collections:2::el7 | All versions | 1:1.10.2-8.el7 |
| `rh-nginx110-nginx-mod-mail` | Red Hat:rhel_software_collections:2::el7 | All versions | 1:1.10.2-8.el7 |
| `rh-nginx110-nginx-mod-stream` | Red Hat:rhel_software_collections:2::el7 | All versions | 1:1.10.2-8.el7 |
| `nginx-1.0` | SUSE:Lifecycle Management Server 1.3 | All versions | 1.0.15-0.35.3.1 |
| `nginx` | SUSE:Package Hub 12 | All versions | 1.13.9-12.1 |
| `nginx-1.0` | SUSE:Studio Onsite 1.3 | All versions | 1.0.15-0.35.3.1 |
| `nginx-1.0` | SUSE:WebYast 1.3 | All versions | 1.0.15-0.35.3.1 |

Products: Apple Xcode, F5 Nginx, Puppet Puppet Enterprise.

## How do I fix CVE-2017-7529?

Upgrade to a fixed version.

## Is CVE-2017-7529 being exploited?

There is no known exploitation of CVE-2017-7529 in the wild and no public exploit code.

Public exploit code:

- CVE-2017-7529_PoC (github_poc): https://github.com/en0f/CVE-2017-7529_PoC
- https://github.com/liusec/CVE-2017-7529 (github_poc): https://github.com/liusec/CVE-2017-7529
- CVE-2017-7529 | nginx on the range 0.5.6 - 1.13.2 (github_poc): https://github.com/gemboxteam/exploit-nginx-1.10.3
- 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. (github_poc): https://github.com/Shehzadcyber/CVE-2017-7529
- https://github.com/MaxSecurity/CVE-2017-7529-POC (github_poc): https://github.com/MaxSecurity/CVE-2017-7529-POC
- https://github.com/cyberharsh/nginx-CVE-2017-7529 (github_poc): https://github.com/cyberharsh/nginx-CVE-2017-7529

## Other vulnerabilities in Apple Xcode

- [CVE-2025-48384](https://insights.sbomify.com/CVE-2025-48384/): Git Link Following (high 8.1, exploited in the wild)
- [CVE-2014-9390](https://insights.sbomify.com/CVE-2014-9390/): JGit Improper Input Validation vulnerability (critical 9.8)
- [CVE-2019-14379](https://insights.sbomify.com/CVE-2019-14379/): Deserialization of untrusted data in FasterXML jackson-databind (critical 9.8)
- [CVE-2018-4164](https://insights.sbomify.com/CVE-2018-4164/): An issue was discovered in certain Apple products. (critical 9.8)
- [CVE-2016-0746](https://insights.sbomify.com/CVE-2016-0746/): Use after free in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-7529 and fix it if it is affected.

What it is: CVE-2017-7529 is a high-severity vulnerability in Apple Xcode, published on 13 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-7529 in the wild and no public exploit code.

Affected product: Apple Xcode. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-7529/ (Markdown: https://insights.sbomify.com/CVE-2017-7529/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-7529
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-7529
- OSV: https://osv.dev/vulnerability/CVE-2017-7529

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-7529/
Summaries are generated and may contain mistakes; the official description above is the record.