Description
There are packages installed that are affected by multiple vulnerabilities referenced in the following CVEs:
- A malicious server can use the FTP PASV response to trick curl 7.73.0 and earlier into connecting back to
a given IP address and port, and this way potentially make curl extract information about services that
are otherwise private and not disclosed, for example doing port scanning and service banner extractions.
(CVE-2020-8284)
- When curl is instructed to get content using the metalink feature, and a user name and password are used
to download the metalink XML file, those same credentials are then subsequently passed on to each of the
servers from which curl will download or try to download the contents from. Often contrary to the user's
expectations and intentions and without telling the user it happened. (CVE-2021-22923)
- When sending data to an MQTT server, libcurl <= 7.73.0 and 7.78.0 could in some circumstances erroneously
keep a pointer to an already freed memory area and both use that again in a subsequent call to send data
and also free it *again*. (CVE-2021-22945)
- A user can tell curl >= 7.20.0 and <= 7.78.0 to require a successful upgrade to TLS when speaking to an
IMAP, POP3 or FTP server (`--ssl-reqd` on the command line or`CURLOPT_USE_SSL` set to `CURLUSESSL_CONTROL`
or `CURLUSESSL_ALL` withlibcurl). This requirement could be bypassed if the server would return a properly
crafted but perfectly legitimate response.This flaw would then make curl silently continue its operations
**withoutTLS** contrary to the instructions and expectations, exposing possibly sensitive data in clear
text over the network. (CVE-2021-22946)
- When curl >= 7.20.0 and <= 7.78.0 connects to an IMAP or POP3 server to retrieve data using STARTTLS to
upgrade to TLS security, the server can respond and send back multiple responses at once that curl caches.
curl would then upgrade to TLS but not flush the in-queue of cached responses but instead continue using
and trustingthe responses it got *before* the TLS handshake as if they were authenticated.Using this flaw,
it allows a Man-In-The-Middle attacker to first inject the fake responses, then pass-through the TLS
traffic from the legitimate server and trick curl into sending data back to the user thinking the
attacker's injected data comes from the TLS-protected server. (CVE-2021-22947)
Plugin Details
Supported Sensors: Agentless Assessment
Risk Information
Vector: CVSS2#AV:N/AC:M/Au:N/C:P/I:N/A:P
Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
Temporal Vector: CVSS:3.0/E:P/RL:O/RC:C
Vulnerability Information
Exploit Ease: Exploits are available
Vulnerability Publication Date: 12/9/2020