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

> A buffer over-read in curl's URL globbing feature allows attackers to cause crashes or disclose memory contents via crafted URLs.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 4 Oct 2017
- **Updated:** 16 Apr 2026
- **Also known as:** ALPINE-CVE-2017-1000101, CLEANSTART-2026-WP63137, CURL-CVE-2017-1000101, DEBIAN-CVE-2017-1000101, GHSA-qxxx-25g2-qj92, UBUNTU-CVE-2017-1000101

## What is CVE-2017-1000101?

CVE-2017-1000101 is a medium-severity memory corruption vulnerability in Haxx Curl, published on 4 Oct 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

curl supports "globbing" of URLs, in which a user can pass a numerical range to have the tool iterate over those numbers to do a sequence of transfers. In the globbing function that parses the numerical range, there was an omission that made curl read a byte beyond the end of the URL if given a carefully crafted, or just wrongly written, URL. The URL is stored in a heap based buffer, so it could then be made to wrongly read something else instead of crashing. An example of a URL that triggers the flaw would be `http://ur%20[0-60000000000000000000`.

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

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

It affects 1 product.


Products: Haxx Curl.

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

Apply the vendor's patch.

## Is CVE-2017-1000101 being exploited?

There is no known exploitation of CVE-2017-1000101 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-1000101 and fix it if it is affected.

What it is: CVE-2017-1000101 is a medium-severity memory corruption vulnerability in Haxx Curl, published on 4 Oct 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-1000101 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-1000101/ (Markdown: https://insights.sbomify.com/CVE-2017-1000101/index.md)
```

## Sources

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

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