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`.
References
Link | Resource |
---|---|
http://www.debian.org/security/2017/dsa-3992 | |
http://www.securityfocus.com/bid/100249 | Third Party Advisory VDB Entry |
http://www.securitytracker.com/id/1039117 | Third Party Advisory VDB Entry |
https://access.redhat.com/errata/RHSA-2018:3558 | |
https://curl.haxx.se/docs/adv_20170809A.html | Issue Tracking Vendor Advisory |
https://security.gentoo.org/glsa/201709-14 | Issue Tracking Third Party Advisory |
https://support.apple.com/HT208221 |
Configurations
Configuration 1 (hide)
|
History
No history.
Information
Published : 2017-10-05 01:29
Updated : 2024-02-04 19:29
NVD link : CVE-2017-1000101
Mitre link : CVE-2017-1000101
CVE.ORG link : CVE-2017-1000101
JSON object : View
Products Affected
haxx
- curl
CWE
CWE-119
Improper Restriction of Operations within the Bounds of a Memory Buffer