The NTLM authentication feature in curl and libcurl before 7.57.0 on 32-bit platforms allows attackers to cause a denial of service (integer overflow and resultant buffer overflow, and application crash) or possibly have unspecified other impact via vectors involving long user and password fields.

The remote host is running a version of macOS that is 10.13.x prior to 10.13.4. It is, therefore, affected by multiple vulnerabilities in the following components :

 - Admin Framework
 - APFS
 - ATS
 - CoreFoundation
 - CoreText
 - Disk Images
 - Disk Management
 - File System Events
 - iCloud Drive
 - Intel Graphics Driver
 - IOFireWireFamily
 - Kernel
 - kext tools
 - LaunchServices
 - Mail
 - Notes
 - NSURLSession
 - NVIDIA Graphics Drivers
 - PDFKit
 - PluginKit
 - Quick Look
 - Security
 - Storage
 - System Preferences
 - Terminal
 - WindowServer

Note that successful exploitation of the most serious issues can result in arbitrary code execution.

libcurl is vulnerable to a heap buffer out-of-bounds read. The function handling incoming NTLM type-2 messages (`lib/vauth/ntlm.c:ntlm_decode_type2_target`) does not validate incoming data correctly and is subject to an integer overflow vulnerability. Using that overflow, a malicious or broken NTLM server could trick libcurl to accept a bad length + offset combination that would lead to a buffer read out-of-bounds.(CVE-2018-16890)

The NTLM authentication feature in curl and libcurl before 7.57.0 on 32-bit platforms allows attackers to cause a denial of service (integer overflow and resultant buffer overflow, and application crash) or possibly have unspecified other impact via vectors involving long user and password fields.(CVE-2017-8816)

curl and libcurl before 7.57.0 on 32-bit platforms allow attackers to cause a denial of service (out-of-bounds access and application crash) or possibly have unspecified other impact because too little memory is allocated for interfacing to an SSL library.(CVE-2017-8818)

libcurl may read outside of a heap allocated buffer when doing FTP.
When libcurl connects to an FTP server and successfully logs in (anonymous or not), it asks the server for the current directory with the `PWD` command. The server then responds with a 257 response containing the path, inside double quotes. The returned path name is then kept by libcurl for subsequent uses. Due to a flaw in the string parser for this directory name, a directory name passed like this but without a closing double quote would lead to libcurl not adding a trailing NUL byte to the buffer holding the name. When libcurl would then later access the string, it could read beyond the allocated heap buffer and crash or wrongly access data beyond the buffer, thinking it was part of the path. A malicious server could abuse this fact and effectively prevent libcurl-based clients to work with it - the PWD command is always issued on new FTP connections and the mistake has a high chance of causing a segfault. The simple fact that this has issue remained undiscovered for this long could suggest that malformed PWD responses are rare in benign servers. We are not aware of any exploit of this flaw. This bug was introduced in commit [415d2e7cb7](https://github.com/curl/curl/commit/415d2e7cb7), March 2005. In libcurl version 7.56.0, the parser always zero terminates the string but also rejects it if not terminated properly with a final double quote.(CVE-2017-1000254)

Curl versions 7.14.1 through 7.61.1 are vulnerable to a heap-based buffer over-read in the tool_msgs.c:voutf() function that may result in information exposure and denial of service.(CVE-2018-16842)

libcurl is vulnerable to a stack-based buffer overflow. The function creating an outgoing NTLM type-3 header (`lib/vauth/ntlm.c:Curl_auth_create_ntlm_type3_message()`), generates the request HTTP header contents based on previously received data.
The check that exists to prevent the local buffer from getting overflowed is implemented wrongly (using unsigned math) and as such it does not prevent the overflow from happening. This output data can grow larger than the local buffer if very large 'nt response' data is extracted from a previous NTLMv2 header provided by the malicious or broken HTTP server. Such a 'large value' needs to be around 1000 bytes or more. The actual payload data copied to the target buffer comes from the NTLMv2 type-2 response header.(CVE-2019-3822)

libcurl is vulnerable to a heap out-of-bounds read in the code handling the end-of-response for SMTP. If the buffer passed to `smtp_endofresp()` isn't NUL terminated and contains no character ending the parsed number, and `len` is set to 5, then the `strtol()` call reads beyond the allocated buffer. The read contents will not be returned to the caller.(CVE-2019-3823)

The FTP wildcard function in curl and libcurl before 7.57.0 allows remote attackers to cause a denial of service (out-of-bounds read and application crash) or possibly have unspecified other impact via a string that ends with an '[' character.(CVE-2017-8817)

set_file_metadata in xattr.c in GNU Wget before 1.20.1 stores a file's origin URL in the user.xdg.origin.url metadata attribute of the extended attributes of the downloaded file, which allows local users to obtain sensitive information (e.g., credentials contained in the URL) by reading this attribute, as demonstrated by getfattr. This also applies to Referer information in the user.xdg.referrer.url metadata attribute. According to 2016-07-22 in the Wget ChangeLog, user.xdg.origin.url was partially based on the behavior of fwrite_xattr in tool_xattr.c in curl.(CVE-2018-20483)

A buffer overrun flaw was found in the IMAP handler of libcurl. By tricking an unsuspecting user into connecting to a malicious IMAP server, an attacker could exploit this flaw to potentially cause information disclosure or crash the application.(CVE-2017-1000257)

A heap use-after-free flaw was found in curl versions from 7.59.0 through 7.61.1 in the code related to closing an easy handle. When closing and cleaning up an 'easy' handle in the `Curl_close()` function, the library code first frees a struct (without nulling the pointer) and might then subsequently erroneously write to a struct field within that already freed struct.(CVE-2018-16840)

Curl versions 7.33.0 through 7.61.1 are vulnerable to a buffer overrun in the SASL authentication code that may lead to denial of service.(CVE-2018-16839)

An update of the curl package has been released.

The remote host is running Mac OS X 10.11.6 or Mac OS X 10.12.6 and is missing a security update. It is therefore, affected by multiple vulnerabilities affecting the following components :

  - ATS
  - CFNetwork Session
  - CoreFoundation
  - CoreTypes
  - curl
  - Disk Images
  - iCloud Drive
  - Kernel
  - kext tools
  - LaunchServices
  - PluginKit
  - Security
  - Storage
  - Terminal

The remote host is running a version of Mac OS X that is 10.13.x prior to 10.13.3. It is, therefore, affected by multiple vulnerabilities in the following components :

  - Audio
  - curl
  - IOHIDFamily
  - Kernel
  - LinkPresentation
  - QuartzCore
  - Sandbox
  - Security
  - WebKit
  - Wi-Fi

Note that successful exploitation of the most serious issues can result in arbitrary code execution.

This update for curl fixes the following issues :

Security issues fixed :

  - CVE-2017-8816: Buffer overrun flaw in the NTLM     authentication code (bsc#1069226).

  - CVE-2017-8817: Read out of bounds flaw in the FTP     wildcard function (bsc#1069222).

This update was imported from the SUSE:SLE-12:Update update project.

This update for curl fixes the following issues: Security issues fixed :

  - CVE-2017-8816: Buffer overrun flaw in the NTLM     authentication code (bsc#1069226).

  - CVE-2017-8817: Read out of bounds flaw in the FTP     wildcard function (bsc#1069222).

Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

- fix NTLM buffer overflow via integer overflow     (CVE-2017-8816)

  - fix FTP wildcard out of bounds read (CVE-2017-8817)

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website.
Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The NTLM authentication feature in curl and libcurl before 7.57.0 on 32-bit platforms allows attackers to cause a denial of service (integer overflow and resultant buffer overflow, and application crash) or possibly have unspecified other impact via vectors involving long user and password fields. (CVE-2017-8816)

The FTP wildcard function in curl and libcurl before 7.57.0 allows remote attackers to cause a denial of service (out-of-bounds read and application crash) or possibly have unspecified other impact via a string that ends with an '[' character. (CVE-2017-8817)

The remote host is affected by the vulnerability described in GLSA-201712-04 (cURL: Multiple vulnerabilities)

    Multiple vulnerabilities have been discovered in cURL. Please review the       CVE identifiers referenced below for details.
  Impact :

    Remote attackers could cause a Denial of Service condition, disclose       sensitive information or other unspecified impacts.
  Workaround :

    There is no known workaround at this time.

Alex Nichols discovered that curl incorrectly handled NTLM authentication credentials. A remote attacker could use this issue to cause curl to crash, resulting in a denial of service, or possibly execute arbitrary code. This issue only affected Ubuntu 16.04 LTS, Ubuntu 17.04 and Ubuntu 17.10. (CVE-2017-8816)

It was discovered that curl incorrectly handled FTP wildcard matching.
A remote attacker could use this issue to cause curl to crash, resulting in a denial of service, or possibly obtain sensitive information. (CVE-2017-8817).

Note that Tenable Network Security has extracted the preceding description block directly from the Ubuntu security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The cURL project reports :

- NTLM buffer overflow via integer overflow (CVE-2017-8816)libcurl contains a buffer overrun flaw in the NTLM authentication code. The internal function Curl_ntlm_core_mk_ntlmv2_hash sums up the lengths of the user name + password (= SUM) and multiplies the sum by two (= SIZE) to figure out how large storage to allocate from the heap.

- FTP wildcard out of bounds read (CVE-2017-8817) libcurl contains a read out of bounds flaw in the FTP wildcard function. libcurl's FTP wildcard matching feature, which is enabled with the CURLOPT_WILDCARDMATCH option can use a built-in wildcard function or a user provided one. The built-in wildcard function has a flaw that makes it not detect the end of the pattern string if it ends with an open bracket ([) but instead it will continue reading the heap beyond the end of the URL buffer that holds the wildcard.

- SSL out of buffer access (CVE-2017-8818) libcurl contains an out boundary access flaw in SSL related code. When allocating memory for a connection (the internal struct called connectdata), a certain amount of memory is allocated at the end of the struct to be used for SSL related structs. Those structs are used by the particular SSL library libcurl is built to use. The application can also tell libcurl which specific SSL library to use if it was built to support more than one.

Two vulnerabilities were discovered in cURL, an URL transfer library.

  - CVE-2017-8816     Alex Nichols discovered a buffer overrun flaw in the     NTLM authentication code which can be triggered on 32bit     systems where an integer overflow might occur when     calculating the size of a memory allocation.

  - CVE-2017-8817     Fuzzing by the OSS-Fuzz project led to the discovery of     a read out of bounds flaw in the FTP wildcard function     in libcurl. A malicious server could redirect a     libcurl-based client to an URL using a wildcard pattern,     triggering the out-of-bound read.

New curl packages are available for Slackware 14.0, 14.1, 14.2, and
-current to fix security issues.

ID	Name	Product	Family	Severity
700515	macOS 10.13.x < 10.13.4 Multiple Vulnerabilities	Nessus Network Monitor	Operating System Detection	critical
122260	Amazon Linux 2 : curl (ALAS-2019-1162)	Nessus	Amazon Linux Local Security Checks	critical
121916	Photon OS 2.0: Curl PHSA-2018-2.0-0016	Nessus	PhotonOS Local Security Checks	critical
121808	Photon OS 1.0: Curl PHSA-2018-1.0-0108	Nessus	PhotonOS Local Security Checks	critical
108787	macOS and Mac OS X Multiple Vulnerabilities (Security Update 2018-002)	Nessus	MacOS X Local Security Checks	high
106296	macOS 10.13.x < 10.13.3 Multiple Vulnerabilities	Nessus	MacOS X Local Security Checks	critical
106219	openSUSE Security Update : curl (openSUSE-2018-56)	Nessus	SuSE Local Security Checks	critical
106132	SUSE SLED12 / SLES12 Security Update : curl (SUSE-SU-2018:0122-1)	Nessus	SuSE Local Security Checks	critical
105863	Fedora 27 : curl (2017-45bdf4dace)	Nessus	Fedora Local Security Checks	critical
105516	Amazon Linux AMI : curl (ALAS-2018-938)	Nessus	Amazon Linux Local Security Checks	critical
105264	GLSA-201712-04 : cURL: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	critical
105124	Fedora 26 : curl (2017-0c062324cd)	Nessus	Fedora Local Security Checks	critical
104881	Ubuntu 14.04 LTS / 16.04 LTS : curl vulnerabilities (USN-3498-1)	Nessus	Ubuntu Local Security Checks	critical
104863	FreeBSD : cURL -- Multiple vulnerabilities (301a01b7-d50e-11e7-ac58-b499baebfeaf)	Nessus	FreeBSD Local Security Checks	critical
104861	Debian DSA-4051-1 : curl - security update	Nessus	Debian Local Security Checks	critical
104860	Slackware 14.0 / 14.1 / 14.2 / current : curl (SSA:2017-333-03)	Nessus	Slackware Local Security Checks	critical

Detections

Analytics

CVE-2017-8816

critical

Tenable Plugins

critical

critical

critical

critical

high

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical