Advisory

GHSA-674j-7m97-j2p9

Also known as: CURL-CVE-2018-1000120, CVE-2018-1000120

Summary

curl FTP path confusion leads to NIL byte out of bounds write

Details

curl can be coerced into writing a zero byte out of bounds.

This bug can trigger when curl is told to work on an FTP URL, with the setting to only issue a single CWD command (--ftp-method singlecwd or the libcurl alternative CURLOPT_FTP_FILEMETHOD).

curl then URL-decodes the given path, calls strlen() on the result and deducts the length of the file name part to find the end of the directory within the buffer. It then writes a zero byte on that index, in a buffer allocated on the heap.

If the directory part of the URL contains a %00 sequence, the directory length might end up shorter than the file name path, making the calculation size_t index = directory_len - filepart_len end up with a huge index variable for where the zero byte gets stored: heap_buffer[index] = 0. On several architectures that huge index will wrap and work as a negative value, thus overwriting memory before the intended heap buffer.

By using different file part lengths and putting the string %00 in different places in the URL, an attacker that can control what paths a curl-using application uses can write that zero byte on different indexes.

Severity

Critical Basis: The source's own band: CRITICAL

Dates

Published
2022-05-14 00:58 UTC
Modified
2024-03-12 05:17 UTC

Affected packages and fixes

curl

NuGet · All systems

Affected

  • introduced 7.12.3 (ecosystem)

Fixed versions

None listed

Fix

No fixed version is listed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences