CVE-2017-9502: n/a vulnerability

CVE-2017-9502: In curl before 7.54.1 on Windows and DOS, libcurl's default protocol function, which is the logic that allo...

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://").

UnknownCVSS not scoredNot KEV-listedUpdatedAug 5, 2024, 17:11 UTC (UTC+00:00)

Security readout for executives and security teams

This is a narrow curl/libcurl memory corruption flaw affecting Windows and DOS builds before 7.54.1. It can occur when an application processes certain local file-style URLs or scheme-less paths. Business urgency depends on whether Windows applications accept untrusted URLs through libcurl. Exposure is most likely in Windows applications embedding libcurl before 7.54.1 that accept user-controlled URLs, paths, or configuration values. Non-Windows and non-DOS builds are not indicated by the provided sources. Prioritize remediation for internet-facing or multi-user Windows software that accepts user-supplied URLs. For internal tools with fixed trusted inputs, track the upgrade through normal dependency maintenance. Mitigation focus: Upgrade curl/libcurl to 7.54.1 or later where affected builds are present.; Check vendor guidance for products that bundle libcurl rather than using the system library.; Constrain or disable FILE URL handling where the application does not require local file access..

Prepared: Jun 13, 2026, 04:43 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2017-9502 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Jun 14, 2017, 13:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
https://curl.haxx.se/docs/adv_20170614.htmlCVE reference · x_refsource_CONFIRM

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.