# CVE-2017-9502: Memory corruption in n/a

> Heap buffer overflow in libcurl on Windows/DOS allows attackers to execute arbitrary code or cause denial of service via crafted URLs.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** CURL-CVE-2017-9502, GHSA-2p6v-q44g-p7m7

## What is CVE-2017-9502?

CVE-2017-9502 is a medium-severity memory corruption vulnerability in Haxx Curl, published on 14 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In curl before 7.54.1 on Windows and DOS, libcurl's default protocol function, which is the logic that allows an application to set which protocol libcurl should attempt to use when given a URL without a scheme part, had a flaw that could lead to it overwriting a heap based memory buffer with seven bytes. If the default protocol is specified to be FILE or a file: URL lacks two slashes, the given "URL" starts with a drive letter, and libcurl is built for Windows or DOS, then libcurl would copy the path 7 bytes off, so that the end of the given path would write beyond the malloc buffer (7 bytes being the length in bytes of the ascii string "file://").

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Haxx Curl.

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

Upgrade to a fixed version.

## Is CVE-2017-9502 being exploited?

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

## Other vulnerabilities in Haxx Curl

- [CVE-2026-19931](https://insights.sbomify.com/CVE-2026-19931/): Negotiate ambient user conn reuse (critical 9.8)
- [CVE-2026-10536](https://insights.sbomify.com/CVE-2026-10536/): HTTP/2 stream-dependency tree UAF (critical 9.8)
- [CVE-2026-11856](https://insights.sbomify.com/CVE-2026-11856/): cross-origin Digest auth state leak (critical 9.8)
- [CVE-2026-8925](https://insights.sbomify.com/CVE-2026-8925/): SASL double-free (critical 9.8)
- [CVE-2026-9079](https://insights.sbomify.com/CVE-2026-9079/): stale proxy password leak (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-9502 is a medium-severity memory corruption vulnerability in Haxx Curl, published on 14 Jun 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-9502 in the wild and no public exploit code.

Affected product: Haxx Curl. 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-9502/ (Markdown: https://insights.sbomify.com/CVE-2017-9502/index.md)
```

## Sources

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

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