curl before 7.53.0 has an incorrect TLS Certificate Status Request extension feature that asks for a fresh proof of the server's certificate's validity in the code that checks for a test success or failure. It ends up always thinking there's valid proof, even when there is none or if the server doesn't support the TLS extension in question. This could lead to users not detecting when a server's certificate goes invalid or otherwise be mislead that the server is in a better shape than it is in reality. This flaw also exists in the command line tool (--cert-status).

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - curl before 7.53.0 has an incorrect TLS Certificate Status Request extension feature that asks for a fresh
    proof of the server's certificate's validity in the code that checks for a test success or failure. It
    ends up always thinking there's valid proof, even when there is none or if the server doesn't support the
    TLS extension in question. This could lead to users not detecting when a server's certificate goes invalid
    or otherwise be mislead that the server is in a better shape than it is in reality. This flaw also exists
    in the command line tool (--cert-status). (CVE-2017-2629)

The remote NewStart CGSL host, running version MAIN 6.02, has curl packages installed that are affected by multiple vulnerabilities:

  - The redirect implementation in curl and libcurl 5.11 through 7.19.3, when CURLOPT_FOLLOWLOCATION is     enabled, accepts arbitrary Location values, which might allow remote HTTP servers to (1) trigger arbitrary     requests to intranet servers, (2) read or overwrite arbitrary files via a redirect to a file: URL, or (3)     execute arbitrary commands via a redirect to an scp: URL. (CVE-2009-0037)

  - The Curl_input_negotiate function in http_negotiate.c in libcurl 7.10.6 through 7.21.6, as used in curl     and other products, always performs credential delegation during GSSAPI authentication, which allows     remote servers to impersonate clients via GSSAPI requests. (CVE-2011-2192)

  - curl and libcurl 7.2x before 7.24.0 do not properly consider special characters during extraction of a     pathname from a URL, which allows remote attackers to conduct data-injection attacks via a crafted URL, as     demonstrated by a CRLF injection attack on the (1) IMAP, (2) POP3, or (3) SMTP protocol. (CVE-2012-0036)

  - Stack-based buffer overflow in the Curl_sasl_create_digest_md5_message function in lib/curl_sasl.c in curl     and libcurl 7.26.0 through 7.28.1, when negotiating SASL DIGEST-MD5 authentication, allows remote     attackers to cause a denial of service (crash) and possibly execute arbitrary code via a long string in     the realm parameter in a (1) POP3, (2) SMTP or (3) IMAP message. (CVE-2013-0249)

  - The tailMatch function in cookie.c in cURL and libcurl before 7.30.0 does not properly match the path     domain when sending cookies, which allows remote attackers to steal cookies via a matching suffix in the     domain of a URL. (CVE-2013-1944)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

There are packages installed that are affected by multiple vulnerabilities referenced in the following CVEs:

  - curl before 7.53.0 has an incorrect TLS Certificate Status Request extension feature that asks for a fresh
    proof of the server's certificate's validity in the code that checks for a test success or failure. It
    ends up always thinking there's valid proof, even when there is none or if the server doesn't support the
    TLS extension in question. This could lead to users not detecting when a server's certificate goes invalid
    or otherwise be mislead that the server is in a better shape than it is in reality. This flaw also exists
    in the command line tool (--cert-status). (CVE-2017-2629)

  - The ourWriteOut function in tool_writeout.c in curl 7.53.1 might allow physically proximate attackers to
    obtain sensitive information from process memory in opportunistic circumstances by reading a workstation
    screen during use of a --write-out argument ending in a '%' character, which leads to a heap-based buffer
    over-read. (CVE-2017-7407)

  - In curl and libcurl 7.52.0 to and including 7.53.1, libcurl would attempt to resume a TLS session even if
    the client certificate had changed. That is unacceptable since a server by specification is allowed to
    skip the client certificate check on resume, and may instead use the old identity which was established by
    the previous certificate (or no certificate). libcurl supports by default the use of TLS session id/ticket
    to resume previous TLS sessions to speed up subsequent TLS handshakes. They are used when for any reason
    an existing TLS connection couldn't be kept alive to make the next handshake faster. This flaw is a
    regression and identical to CVE-2016-5419 reported on August 3rd 2016, but affecting a different version
    range. (CVE-2017-7468)

The remote host is running a version of Mac OS X version 10.x prior to 10.12.6, and is affected by multiple vulnerabilities :

 - An overflow condition exists in the curl component in the 'dprintf_formatf()' function that is triggered when handling floating point conversion. An unauthenticated, remote attacker can exploit this to cause a denial of service condition or the execution of arbitrary code. (CVE-2016-9586)
 - A flaw exits in the curl component in the 'randit()' function within file lib/rand.c due to improper initialization of the 32-bit random value, which is used, for example, to generate Digest and NTLM authentication nonces, resulting in weaker cryptographic operations than expected. (CVE-2016-9594)
 - A flaw exists in the curl component in the 'allocate_conn()' function in lib/url.c when using the OCSP stapling feature for checking a X.509 certificate revocation status. The issue is triggered as the request option for OCSP stapling is not properly passed to the TLS library, resulting in no error being returned even when no proof of the validity of the certificate could be provided. A man-in-the-middle attacker can exploit this to provide a revoked certificate. (CVE-2017-2629)
 - A remote code execution vulnerability exists in the CoreAudio component due to improper validation of user-supplied input when handling movie files. An unauthenticated, remote attacker can exploit this, by convincing a user to play a specially crafted movie file, to cause a denial of service condition or the execution of arbitrary code. (CVE-2017-7008)
 - A memory corruption issue exists in the IOUSBFamily component due to improper validation of user-supplied input. A local attacker can exploit this, via a specially crafted application, to cause a denial of service condition or the execution of arbitrary code. (CVE-2017-7009)
 - Multiple out-of-bounds read errors exist in the libxml2 component due to improper handling of specially crafted XML documents. An unauthenticated, remote attacker can exploit these to disclose user information. (CVE-2017-7010, CVE-2017-7013)
 - Multiple memory corruption issues exist in the Intel Graphics Driver component due to improper validation of input. A local attacker can exploit these issues to execute arbitrary code with elevated privileges. (CVE-2017-7014, CVE-2017-7017, CVE-2017-7035, CVE-2017-7044)
 - A remote code execution vulnerability exists in the Audio component due to improper validation of user-supplied input when handling audio files. An unauthenticated, remote attacker can exploit this, by convincing a user to play a specially crafted audio file, to execute arbitrary code. (CVE-2017-7015)
 - Multiple remote code execution vulnerabilities exist in the afclip component due to improper validation of user-supplied input when handling audio files. An unauthenticated, remote attacker can exploit these vulnerabilities, by convincing a user to play a specially crafted audio file, to execute arbitrary code. (CVE-2017-7016, CVE-2017-7033)
 - A memory corruption issue exists in the AppleGraphicsPowerManagement component due to improper validation of input. A local attacker can exploit this to cause a denial of service condition or the execution of arbitrary code with system privileges. (CVE-2017-7021)
 - Multiple memory corruption issues exist in the kernel due to improper validation of input. A local attacker can exploit these issues to cause a denial of service condition or the execution of arbitrary code with system privileges. (CVE-2017-7022, CVE-2017-7024, CVE-2017-7026)
 - Multiple memory corruption issues exist in the kernel due to improper validation of input. A local attacker can exploit these issues to cause a denial of service condition or the execution of arbitrary code with kernel privileges. (CVE-2017-7023, CVE-2017-7025, CVE-2017-7027, CVE-2017-7069)
 - Multiple unspecified flaws exist in the kernel due to a failure to properly sanitize input. A local attacker can exploit these issues, via a specially crafted application, to disclose restricted memory contents. (CVE-2017-7028, CVE-2017-7029, CVE-2017-7067)
 - A flaw exists in the Foundation component due to improper validation of input. A unauthenticated, remote attacker can exploit this, by convincing a user to open specially crafted file, to execute arbitrary code. (CVE-2017-7031)
 - A memory corruption issue exists in the 'kext tools' component due to improper validation of input. A local attacker can exploit this to execute arbitrary code with elevated privileges. (CVE-2017-7032)
 - Multiple unspecified flaws exist in the Intel Graphics Driver component due to a failure to properly sanitize input. A local attacker can exploit these issues, via a specially crafted application, to disclose restricted memory contents. (CVE-2017-7036, CVE-2017-7045)
 - A memory corruption issue exists in the libxpc component due to improper validation of input. A local attacker can exploit this issue, via a specifically crafted application, to cause a denial of service condition or the execution of arbitrary code with system privileges. (CVE-2017-7047)
 - Multiple memory corruption issues exist in the Bluetooth component due to improper validation of input. A local attacker can exploit these issues to execute arbitrary code with system privileges. (CVE-2017-7050, CVE-2017-7051)
 - A memory corruption issue exists in the Bluetooth component due to improper validation of input. A local attacker can exploit these issues to execute arbitrary code with system privileges. (CVE-2017-7054)
 - A buffer overflow condition exists in the Contacts component due to improper validation of user-supplied input. An unauthenticated, remote attacker can exploit this to cause a denial of service condition or the execution of arbitrary code. (CVE-2017-7062)
 - A buffer overflow condition exists in the libarchive component due to improper validation of user-supplied input. An unauthenticated, remote attacker can exploit this, via a specially crafted archive file, to cause a denial of service condition or the execution of arbitrary code. (CVE-2017-7068)
 - A certificate validation bypass vulnerability exists in the curl component due to the program attempting to resume TLS sessions even if the client certificate fails. An unauthenticated, remote attacker can exploit this to bypass validation mechanisms. (CVE-2017-7468)
 - A memory corruption issue exists in the Broadcom BCM43xx family Wi-Fi Chips component that allows an unauthenticated, remote attacker to execute arbitrary code. (CVE-2017-9417)


The remote host is running Mac OS X 10.10.5, Mac OS X 10.11.6, or macOS 10.12.5 and is missing a security update. It is therefore, affected by multiple vulnerabilities :

  - An overflow condition exists in the curl component in     the dprintf_formatf() function that is triggered when     handling floating point conversion. An unauthenticated,     remote attacker can exploit this to cause a denial of     service condition or the execution of arbitrary code.
    (CVE-2016-9586)

  - A flaw exits in the curl component in the randit()     function within file lib/rand.c due to improper     initialization of the 32-bit random value, which is     used, for example, to generate Digest and NTLM     authentication nonces, resulting in weaker cryptographic     operations than expected. (CVE-2016-9594)

  - A flaw exists in the curl component in the     allocate_conn() function in lib/url.c when using the     OCSP stapling feature for checking a X.509 certificate     revocation status. The issue is triggered as the request     option for OCSP stapling is not properly passed to the     TLS library, resulting in no error being returned even     when no proof of the validity of the certificate could     be provided. A man-in-the-middle attacker can exploit     this to provide a revoked certificate. (CVE-2017-2629)

  - A remote code execution vulnerability exists in the     CoreAudio component due to improper validation of     user-supplied input when handling movie files. An     unauthenticated, remote attacker can exploit this, by     convincing a user to play a specially crafted movie     file, to cause a denial of service condition or the     execution of arbitrary code. (CVE-2017-7008)

  - A memory corruption issue exists in the IOUSBFamily     component due to improper validation of user-supplied     input. A local attacker can exploit this, via a     specially crafted application, to cause a denial of     service condition or the execution of arbitrary code.
    (CVE-2017-7009)

  - Multiple out-of-bounds read errors exist in the libxml2     component due to improper handling of specially crafted     XML documents. An unauthenticated, remote attacker can     exploit these to disclose user information.
    (CVE-2017-7010, CVE-2017-7013)

  - Multiple memory corruption issues exist in the Intel     Graphics Driver component due to improper validation of     input. A local attacker can exploit these issues to     execute arbitrary code with elevated privileges.
    (CVE-2017-7014, CVE-2017-7017, CVE-2017-7035,     CVE-2017-7044)

  - A remote code execution vulnerability exists in the     Audio component due to improper validation of     user-supplied input when handling audio files. An     unauthenticated, remote attacker can exploit this, by     convincing a user to play a specially crafted audio     file, to execute arbitrary code. (CVE-2017-7015)

  - Multiple remote code execution vulnerabilities exist in     the afclip component due to improper validation of     user-supplied input when handling audio files. An     unauthenticated, remote attacker can exploit these     vulnerabilities, by convincing a user to play a     specially crafted audio file, to execute arbitrary     code. (CVE-2017-7016, CVE-2017-7033)

  - A memory corruption issue exists in the     AppleGraphicsPowerManagement component due to improper     validation of input. A local attacker can exploit this     to cause a denial of service condition or the execution     of arbitrary code with system privileges.
    (CVE-2017-7021)

  - Multiple memory corruption issues exist in the kernel     due to improper validation of input. A local attacker     can exploit these issues to cause a denial of service     condition or the execution of arbitrary code with system     privileges. (CVE-2017-7022, CVE-2017-7024,     CVE-2017-7026)

  - Multiple memory corruption issues exist in the kernel     due to improper validation of input. A local attacker     can exploit these issues to cause a denial of service     condition or the execution of arbitrary code with kernel     privileges. (CVE-2017-7023, CVE-2017-7025,     CVE-2017-7027, CVE-2017-7069)

  - Multiple unspecified flaws exist in the kernel due to a     failure to properly sanitize input. A local attacker can     exploit these issues, via a specially crafted     application, to disclose restricted memory contents.
    (CVE-2017-7028, CVE-2017-7029, CVE-2017-7067)

  - A flaw exists in the Foundation component due to     improper validation of input. A unauthenticated, remote     attacker can exploit this, by convincing a user to open     specially crafted file, to execute arbitrary code.
    (CVE-2017-7031)

  - A memory corruption issue exists in the 'kext tools'     component due to improper validation of input. A local     attacker can exploit this to execute arbitrary code with     elevated privileges. (CVE-2017-7032)

  - Multiple unspecified flaws exist in the Intel Graphics     Driver component due to a failure to properly sanitize     input. A local attacker can exploit these issues, via a     specially crafted application, to disclose restricted     memory contents. (CVE-2017-7036, CVE-2017-7045)

  - A memory corruption issue exists in the libxpc component     due to improper validation of input. A local attacker     can exploit this issue, via a specifically crafted     application, to cause a denial of service condition or     the execution of arbitrary code with system privileges.
    (CVE-2017-7047)

  - Multiple memory corruption issues exist in the     Bluetooth component due to improper validation of input.
    A local attacker can exploit these issues to execute     arbitrary code with system privileges. (CVE-2017-7050,     CVE-2017-7051)

  - A memory corruption issue exists in the Bluetooth     component due to improper validation of input. A local     attacker can exploit these issues to execute arbitrary     code with system privileges. (CVE-2017-7054)

  - A buffer overflow condition exists in the Contacts     component due to improper validation of user-supplied     input. An unauthenticated, remote attacker can exploit     this to cause a denial of service condition or the     execution of arbitrary code. (CVE-2017-7062)

  - A buffer overflow condition exists in the libarchive     component due to improper validation of user-supplied     input. An unauthenticated, remote attacker can exploit     this, via a specially crafted archive file, to cause a     denial of service condition or the execution of     arbitrary code. (CVE-2017-7068)

  - A certificate validation bypass vulnerability exists in     the curl component due to the program attempting to     resume TLS sessions even if the client certificate     fails. An unauthenticated, remote attacker can exploit     this to bypass validation mechanisms. (CVE-2017-7468)

  - A memory corruption issue exists in the Broadcom BCM43xx     family Wi-Fi Chips component that allows an     unauthenticated, remote attacker to execute arbitrary     code. (CVE-2017-9417)

The remote host is affected by the vulnerability described in GLSA-201703-04 (cURL: Certificate validation error)

    cURL and applications linked against libcurl support &ldquo;OCSP       stapling&rdquo;, also known as the TLS Certificate Status Request extension       (using the CURLOPT_SSL_VERIFYSTATUS option). When telling cURL to use       this feature, it uses that TLS extension to ask for a fresh proof of the       server&rsquo;s certificate&rsquo;s validity. If the server doesn&rsquo;t support the       extension, or fails to provide said proof, cURL is expected to return an       error.
      Due to a coding mistake, the code that checks for a test success or       failure, ends up always thinking there&rsquo;s valid proof, even when there       is none or if the server doesn&rsquo;t support the TLS extension in question.
  Impact :

    Due to the error, a user maybe does not detect when a server&rsquo;s       certificate goes invalid or otherwise be mislead that the server is in a       better shape than it is in reality.
  Workaround :

    There is no known workaround at this time.

The cURL project reports :

SSL_VERIFYSTATUS ignored curl and libcurl support 'OCSP stapling', also known as the TLS Certificate Status Request extension (using the CURLOPT_SSL_VERIFYSTATUS option). When telling curl to use this feature, it uses that TLS extension to ask for a fresh proof of the server's certificate's validity. If the server doesn't support the extension, or fails to provide said proof, curl is expected to return an error. Due to a coding mistake, the code that checks for a test success or failure, ends up always thinking there's valid proof, even when there is none or if the server doesn't support the TLS extension in question. Contrary to how it used to function and contrary to how this feature is documented to work. This could lead to users not detecting when a server's certificate goes invalid or otherwise be mislead that the server is in a better shape than it is in reality.

ID	Name	Product	Family	Type	Severity
423792	Alpine: libcurl, multiple curl packages: security update to 7.53.0-r0	Tenable Cloud Security	Alpine Linux Local Security Checks	Local	medium
423792	Alpine: libcurl, multiple curl packages: security update to 7.53.0-r0	Tenable Self-Hosted Container Security	Alpine Linux Local Security Checks	Local	medium
206854	NewStart CGSL MAIN 6.02 : curl Multiple Vulnerabilities (NS-SA-2024-0050)	Nessus	NewStart CGSL Local Security Checks	Local	critical
403968	Alpine: curl: security update to 7.53.0	Tenable Cloud Security	Alpine Linux Local Security Checks	Local	medium
403968	Alpine: curl: security update to 7.53.0	Tenable Self-Hosted Container Security	Alpine Linux Local Security Checks	Local	medium
403964	Alpine: curl: security update to 7.52.1-r2	Tenable Cloud Security	Alpine Linux Local Security Checks	Local	high
403964	Alpine: curl: security update to 7.52.1-r2	Tenable Self-Hosted Container Security	Alpine Linux Local Security Checks	Local	high
403963	Alpine: curl: security update to 7.52.1-r1	Tenable Cloud Security	Alpine Linux Local Security Checks	Local	high
403963	Alpine: curl: security update to 7.52.1-r1	Tenable Self-Hosted Container Security	Alpine Linux Local Security Checks	Local	high
700170	Mac OS X 10.x < 10.12.6 Multiple Vulnerabilities	Nessus Network Monitor	Operating System Detection		critical
101957	macOS and Mac OS X Multiple Vulnerabilities (Security Update 2017-003)	Nessus	MacOS X Local Security Checks	Local	critical
99011	GLSA-201703-04 : cURL: Certificate validation error	Nessus	Gentoo Local Security Checks	Local	medium
97342	FreeBSD : cURL -- ocsp status validation error (311e4b1c-f8ee-11e6-9940-b499baebfeaf)	Nessus	FreeBSD Local Security Checks	Local	medium

Detections

Analytics

CVE-2017-2629

medium

Tenable Plugins

medium

medium

critical

medium

medium

high

high

high

high

critical

critical

medium

medium