Alpine: libcurl, multiple curl packages: security update to 8.1.0-r0

high Tenable Self-Hosted Container Security Plugin ID 423821

Description

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

- A use after free vulnerability exists in curl <v8.1.0 in the way libcurl offers a feature to verify an SSH
server's public key using a SHA 256 hash. When this check fails, libcurl would free the memory for the
fingerprint before it returns an error message containing the (now freed) hash. This flaw risks inserting
sensitive heap-based data into the error message that might be shown to users or otherwise get leaked and
revealed. (CVE-2023-28319)

- A denial of service vulnerability exists in curl <v8.1.0 in the way libcurl provides several different
backends for resolving host names, selected at build time. If it is built to use the synchronous resolver,
it allows name resolves to time-out slow operations using `alarm()` and `siglongjmp()`. When doing this,
libcurl used a global buffer that was not mutex protected and a multi-threaded application might therefore
crash or otherwise misbehave. (CVE-2023-28320)

- An improper certificate validation vulnerability exists in curl <v8.1.0 in the way it supports matching of
wildcard patterns when listed as "Subject Alternative Name" in TLS server certificates. curl can be built
to use its own name matching function for TLS rather than one provided by a TLS library. This private
wildcard matching function would match IDN (International Domain Name) hosts incorrectly and could as a
result accept patterns that otherwise should mismatch. IDN hostnames are converted to puny code before
used for certificate checks. Puny coded names always start with `xn--` and should not be allowed to
pattern match, but the wildcard check in curl could still check for `x*`, which would match even though
the IDN name most likely contained nothing even resembling an `x`. (CVE-2023-28321)

- An information disclosure vulnerability exists in curl <v8.1.0 when doing HTTP(S) transfers, libcurl might
erroneously use the read callback (`CURLOPT_READFUNCTION`) to ask for data to send, even when the
`CURLOPT_POSTFIELDS` option has been set, if the same handle previously wasused to issue a `PUT` request
which used that callback. This flaw may surprise the application and cause it to misbehave and either send
off the wrong data or use memory after free or similar in the second transfer. The problem exists in the
logic for a reused handle when it is (expected to be) changed from a PUT to a POST. (CVE-2023-28322)

Plugin Details

Severity: High

ID: 423821

Version: Revision 1.8

Type: Local

Family: Alpine Linux Local Security Checks

Published: 4/4/2025

Updated: 7/2/2026

Supported Sensors: Agentless Assessment, Tenable Cloud Security, Tenable Self-Hosted Container Security

Risk Information

VPR

Risk Factor: Medium

Score: 5

Percentile: 94.66

CVSS v2

Risk Factor: High

Base Score: 7.8

Temporal Score: 6.1

Vector: CVSS2#AV:N/AC:L/Au:N/C:C/I:N/A:N

CVSS Score Source: CVE-2023-28319

CVSS v3

Risk Factor: High

Base Score: 7.5

Temporal Score: 6.7

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Temporal Vector: CVSS:3.0/E:P/RL:O/RC:C

Vulnerability Information

Exploit Available: true

Exploit Ease: Exploits are available

Vulnerability Publication Date: 5/19/2023

Reference Information

CVE: CVE-2023-28319, CVE-2023-28320, CVE-2023-28321, CVE-2023-28322

IAVA: 2023-A-0259-S, 2023-A-0531-S

Detections

Analytics