dbcve.org
CurlApplication · Haxx

CVE-2017-1000101

MEDIUM · 6.5 CVSS v3.1 Published 2017-10-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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`.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

curl's URL globbing feature contains an off-by-one (or more) out-of-bounds read vulnerability when parsing numerical ranges in URLs. The parsing function fails to properly validate buffer boundaries when processing extremely large range values like [0-60000000000000000000], causing reads past the end of the heap-allocated URL buffer. This could allow exposure of adjacent heap memory contents.

MitigationUpdate curl to a patched version that includes bounds checking in the URL globbing range parser. If updating is not immediately possible, avoid processing untrusted URLs with globbing enabled or disable globbing functionality entirely.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CurlApplication
Affected:= 7.4.1= 7.35.0= 7.36.0= 7.37.0= 7.37.1= 7.38.0= 7.39.0= 7.40.0= 7.41.0= 7.42.0= 7.42.1= 7.43.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed curl version
    Run 'curl --version' or 'curl -V' to see the exact version of curl installed on the system
    Affected if The version shown matches one of these: 7.4.1, 7.35.0, 7.36.0, 7.37.0, 7.37.1, 7.38.0, 7.39.0, 7.40.0, 7.41.0, 7.42.0, 7.42.1, or 7.43.0
  2. Identify curl usage in scripts or applications
    Search for curl invocations in your codebase, cron jobs, or automation scripts using grep or similar tools. Look for URLs containing bracket patterns like [0-N] which indicate globbing usage
    Affected if curl is being used with URLs containing numerical range patterns such as [0-100] or similar glob syntax
  3. Check for globbing-enabled curl configurations
    Inspect any curl configuration files (.curlrc, ~/.curlrc, or custom config files) for the 'globoff' setting. If globoff is not set to true, globbing is enabled by default
    Affected if Globbing is enabled (globoff is absent or set to false) and curl version is in the affected list
  4. Monitor or inspect URL inputs to curl
    Review any system that passes user-supplied or remote URLs to curl. Check if these URLs could contain the special range syntax that triggers the overflow
    Affected if Your system processes URLs that could contain extremely large numerical ranges like [0-60000000000000000000] and the curl version is affected

You are affected if your curl version matches 7.4.1 through 7.43.0 and you process URLs containing globbing range patterns with the globbing feature enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update curl to a patched version that includes bounds checking in the URL globbing range parser. If updating is not immediately possible, avoid processing untrusted URLs with globbing enabled or disable globbing functionality entirely.

Fix this in Curl Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-1000101 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-1000101 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data