Vulnerabilities

 58 via 102 paths

Dependencies

 45

Source

 Group 6 Copy Created with Sketch. Docker

Target OS

 alpine:3.15.4
Test your Docker Hub image against our market leading vulnerability database Sign up for free
Severity
  • 7
  • 27
  • 21
  • 3
Status
  • 58
  • 0
  • 0

critical severity

Exposure of Resource to Wrong Sphere

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.80.0-r1 and curl/libcurl@7.80.0-r1
  • Fixed in: 7.80.0-r4

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › curl/curl@7.80.0-r1
  • Introduced through: nginx@1.21-alpine-perl › curl/libcurl@7.80.0-r1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

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 was used 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 subsequent POST request. The problem exists in the logic for a reused handle when it is changed from a PUT to a POST.

Remediation

Upgrade Alpine:3.15 curl to version 7.80.0-r4 or higher.

References

Exposure of Resource to Wrong Sphere vulnerability report

critical severity

Incorrect Default Permissions

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.80.0-r1 and curl/libcurl@7.80.0-r1
  • Fixed in: 7.80.0-r2

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › curl/curl@7.80.0-r1
  • Introduced through: nginx@1.21-alpine-perl › curl/libcurl@7.80.0-r1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

When curl < 7.84.0 saves cookies, alt-svc and hsts data to local files, it makes the operation atomic by finalizing the operation with a rename from a temporary name to the final target file name.In that rename operation, it might accidentally widen the permissions for the target file, leaving the updated file accessible to more users than intended.

Remediation

Upgrade Alpine:3.15 curl to version 7.80.0-r2 or higher.

References

Incorrect Default Permissions vulnerability report

critical severity

Out-of-bounds Write

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.80.0-r1 and curl/libcurl@7.80.0-r1
  • Fixed in: 8.4.0-r0

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › curl/curl@7.80.0-r1
  • Introduced through: nginx@1.21-alpine-perl › curl/libcurl@7.80.0-r1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

This flaw makes curl overflow a heap based buffer in the SOCKS5 proxy handshake.

When curl is asked to pass along the host name to the SOCKS5 proxy to allow that to resolve the address instead of it getting done by curl itself, the maximum length that host name can be is 255 bytes.

If the host name is detected to be longer, curl switches to local name resolving and instead passes on the resolved address only. Due to this bug, the local variable that means "let the host resolve the name" could get the wrong value during a slow SOCKS5 handshake, and contrary to the intention, copy the too long host name to the target buffer instead of copying just the resolved address there.

The target buffer being a heap based buffer, and the host name coming from the URL that curl has been told to operate with.

Remediation

Upgrade Alpine:3.15 curl to version 8.4.0-r0 or higher.

References

Out-of-bounds Write vulnerability report

critical severity

Out-of-bounds Write

  • Vulnerable module: zlib/zlib
  • Introduced through: zlib/zlib@1.2.12-r0
  • Fixed in: 1.2.12-r2

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › zlib/zlib@1.2.12-r0

NVD Description

Note: Versions mentioned in the description apply only to the upstream zlib package and not the zlib package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

zlib through 1.2.12 has a heap-based buffer over-read or buffer overflow in inflate in inflate.c via a large gzip header extra field. NOTE: only applications that call inflateGetHeader are affected. Some common applications bundle the affected zlib source code but may be unable to call inflateGetHeader (e.g., see the nodejs/node reference).

Remediation

Upgrade Alpine:3.15 zlib to version 1.2.12-r2 or higher.

References

Out-of-bounds Write vulnerability report

critical severity

Cleartext Transmission of Sensitive Information

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.80.0-r1 and curl/libcurl@7.80.0-r1
  • Fixed in: 7.80.0-r6

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › curl/curl@7.80.0-r1
  • Introduced through: nginx@1.21-alpine-perl › curl/libcurl@7.80.0-r1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

A cleartext transmission of sensitive information vulnerability exists in curl <v7.88.0 that could cause HSTS functionality fail when multiple URLs are requested serially. Using its HSTS support, curl can be instructed to use HTTPS instead of usingan insecure clear-text HTTP step even when HTTP is provided in the URL. ThisHSTS mechanism would however surprisingly be ignored by subsequent transferswhen done on the same command line because the state would not be properlycarried on.

Remediation

Upgrade Alpine:3.15 curl to version 7.80.0-r6 or higher.

References

Cleartext Transmission of Sensitive Information vulnerability report

critical severity

Out-of-bounds Read

  • Vulnerable module: pcre2/pcre2
  • Introduced through: pcre2/pcre2@10.39-r0
  • Fixed in: 10.40-r0

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › pcre2/pcre2@10.39-r0

NVD Description

Note: Versions mentioned in the description apply only to the upstream pcre2 package and not the pcre2 package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

An out-of-bounds read vulnerability was discovered in the PCRE2 library in the compile_xclass_matchingpath() function of the pcre2_jit_compile.c file. This involves a unicode property matching issue in JIT-compiled regular expressions. The issue occurs because the character was not fully read in case-less matching within JIT.

Remediation

Upgrade Alpine:3.15 pcre2 to version 10.40-r0 or higher.

References

Out-of-bounds Read vulnerability report

critical severity

Out-of-bounds Read

  • Vulnerable module: pcre2/pcre2
  • Introduced through: pcre2/pcre2@10.39-r0
  • Fixed in: 10.40-r0

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › pcre2/pcre2@10.39-r0

NVD Description

Note: Versions mentioned in the description apply only to the upstream pcre2 package and not the pcre2 package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

An out-of-bounds read vulnerability was discovered in the PCRE2 library in the get_recurse_data_length() function of the pcre2_jit_compile.c file. This issue affects recursions in JIT-compiled regular expressions caused by duplicate data transfers.

Remediation

Upgrade Alpine:3.15 pcre2 to version 10.40-r0 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Arbitrary Code Injection

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.80.0-r1 and curl/libcurl@7.80.0-r1
  • Fixed in: 8.0.1-r0

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › curl/curl@7.80.0-r1
  • Introduced through: nginx@1.21-alpine-perl › curl/libcurl@7.80.0-r1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

A vulnerability in input validation exists in curl <8.0 during communication using the TELNET protocol may allow an attacker to pass on maliciously crafted user name and "telnet options" during server negotiation. The lack of proper input scrubbing allows an attacker to send content or perform option negotiation without the application's intent. This vulnerability could be exploited if an application allows user input, thereby enabling attackers to execute arbitrary code on the system.

Remediation

Upgrade Alpine:3.15 curl to version 8.0.1-r0 or higher.

References

Arbitrary Code Injection vulnerability report

high severity

Directory Traversal

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.80.0-r1 and curl/libcurl@7.80.0-r1
  • Fixed in: 8.0.1-r0

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › curl/curl@7.80.0-r1
  • Introduced through: nginx@1.21-alpine-perl › curl/libcurl@7.80.0-r1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

A path traversal vulnerability exists in curl <8.0.0 SFTP implementation causes the tilde () character to be wrongly replaced when used as a prefix in the first path element, in addition to its intended use as the first element to indicate a path relative to the user's home directory. Attackers can exploit this flaw to bypass filtering or execute arbitrary code by crafting a path like /2/foo while accessing a server with a specific user.

Remediation

Upgrade Alpine:3.15 curl to version 8.0.1-r0 or higher.

References

Directory Traversal vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: libwebp/libwebp
  • Introduced through: libwebp/libwebp@1.2.2-r0
  • Fixed in: 1.2.2-r2

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › libwebp/libwebp@1.2.2-r0

NVD Description

Note: Versions mentioned in the description apply only to the upstream libwebp package and not the libwebp package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

Heap buffer overflow in libwebp in Google Chrome prior to 116.0.5845.187 and libwebp 1.3.2 allowed a remote attacker to perform an out of bounds memory write via a crafted HTML page. (Chromium security severity: Critical)

Remediation

Upgrade Alpine:3.15 libwebp to version 1.2.2-r2 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Double Free

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.80.0-r1 and curl/libcurl@7.80.0-r1
  • Fixed in: 7.80.0-r4

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › curl/curl@7.80.0-r1
  • Introduced through: nginx@1.21-alpine-perl › curl/libcurl@7.80.0-r1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

curl before 7.86.0 has a double free. If curl is told to use an HTTP proxy for a transfer with a non-HTTP(S) URL, it sets up the connection to the remote server by issuing a CONNECT request to the proxy, and then tunnels the rest of the protocol through. An HTTP proxy might refuse this request (HTTP proxies often only allow outgoing connections to specific port numbers, like 443 for HTTPS) and instead return a non-200 status code to the client. Due to flaws in the error/cleanup handling, this could trigger a double free in curl if one of the following schemes were used in the URL for the transfer: dict, gopher, gophers, ldap, ldaps, rtmp, rtmps, or telnet. The earliest affected version is 7.77.0.

Remediation

Upgrade Alpine:3.15 curl to version 7.80.0-r4 or higher.

References

Double Free vulnerability report

high severity

Double Free

  • Vulnerable module: libxml2/libxml2
  • Introduced through: libxml2/libxml2@2.9.14-r0
  • Fixed in: 2.9.14-r2

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › libxml2/libxml2@2.9.14-r0

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

An issue was discovered in libxml2 before 2.10.3. Certain invalid XML entity definitions can corrupt a hash table key, potentially leading to subsequent logic errors. In one case, a double-free can be provoked.

Remediation

Upgrade Alpine:3.15 libxml2 to version 2.9.14-r2 or higher.

References

Double Free vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: ncurses/ncurses-libs
  • Introduced through: ncurses/ncurses-libs@6.3_p20211120-r0 and ncurses/ncurses-terminfo-base@6.3_p20211120-r0
  • Fixed in: 6.3_p20211120-r2

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › ncurses/ncurses-libs@6.3_p20211120-r0
  • Introduced through: nginx@1.21-alpine-perl › ncurses/ncurses-terminfo-base@6.3_p20211120-r0

NVD Description

Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

ncurses before 6.4 20230408, when used by a setuid application, allows local users to trigger security-relevant memory corruption via malformed data in a terminfo database file that is found in $HOME/.terminfo or reached via the TERMINFO or TERM environment variable.

Remediation

Upgrade Alpine:3.15 ncurses to version 6.3_p20211120-r2 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: perl/perl
  • Introduced through: perl/perl@5.34.0-r1
  • Fixed in: 5.34.2-r0

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › perl/perl@5.34.0-r1

NVD Description

Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

A vulnerability was found in perl 5.30.0 through 5.38.0. This issue occurs when a crafted regular expression is compiled by perl, which can allow an attacker controlled byte buffer overflow in a heap allocated buffer.

Remediation

Upgrade Alpine:3.15 perl to version 5.34.2-r0 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.80.0-r1 and curl/libcurl@7.80.0-r1
  • Fixed in: 8.3.0-r0

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › curl/curl@7.80.0-r1
  • Introduced through: nginx@1.21-alpine-perl › curl/libcurl@7.80.0-r1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

When curl retrieves an HTTP response, it stores the incoming headers so that they can be accessed later via the libcurl headers API.

However, curl did not have a limit in how many or how large headers it would accept in a response, allowing a malicious server to stream an endless series of headers and eventually cause curl to run out of heap memory.

Remediation

Upgrade Alpine:3.15 curl to version 8.3.0-r0 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

high severity

Cleartext Transmission of Sensitive Information

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.80.0-r1 and curl/libcurl@7.80.0-r1
  • Fixed in: 7.80.0-r4

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › curl/curl@7.80.0-r1
  • Introduced through: nginx@1.21-alpine-perl › curl/libcurl@7.80.0-r1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

In curl before 7.86.0, the HSTS check could be bypassed to trick it into staying with HTTP. Using its HSTS support, curl can be instructed to use HTTPS directly (instead of using an insecure cleartext HTTP step) even when HTTP is provided in the URL. This mechanism could be bypassed if the host name in the given URL uses IDN characters that get replaced with ASCII counterparts as part of the IDN conversion, e.g., using the character UTF-8 U+3002 (IDEOGRAPHIC FULL STOP) instead of the common ASCII full stop of U+002E (.). The earliest affected version is 7.77.0 2021-05-26.

Remediation

Upgrade Alpine:3.15 curl to version 7.80.0-r4 or higher.

References

Cleartext Transmission of Sensitive Information vulnerability report

high severity

Cleartext Transmission of Sensitive Information

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.80.0-r1 and curl/libcurl@7.80.0-r1
  • Fixed in: 7.80.0-r5

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › curl/curl@7.80.0-r1
  • Introduced through: nginx@1.21-alpine-perl › curl/libcurl@7.80.0-r1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

A vulnerability exists in curl <7.87.0 HSTS check that could be bypassed to trick it to keep using HTTP. Using its HSTS support, curl can be instructed to use HTTPS instead of using an insecure clear-text HTTP step even when HTTP is provided in the URL. However, the HSTS mechanism could be bypassed if the host name in the given URL first uses IDN characters that get replaced to ASCII counterparts as part of the IDN conversion. Like using the character UTF-8 U+3002 (IDEOGRAPHIC FULL STOP) instead of the common ASCII full stop (U+002E) .. Then in a subsequent request, it does not detect the HSTS state and makes a clear text transfer. Because it would store the info IDN encoded but look for it IDN decoded.

Remediation

Upgrade Alpine:3.15 curl to version 7.80.0-r5 or higher.

References

Cleartext Transmission of Sensitive Information vulnerability report

high severity

Improper Certificate Validation

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.80.0-r1 and curl/libcurl@7.80.0-r1
  • Fixed in: 7.80.0-r2

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › curl/curl@7.80.0-r1
  • Introduced through: nginx@1.21-alpine-perl › curl/libcurl@7.80.0-r1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

libcurl would reuse a previously created connection even when a TLS or SSHrelated option had been changed that should have prohibited reuse.libcurl keeps previously used connections in a connection pool for subsequenttransfers to reuse if one of them matches the setup. However, several TLS andSSH settings were left out from the configuration match checks, making themmatch too easily.

Remediation

Upgrade Alpine:3.15 curl to version 7.80.0-r2 or higher.

References

Improper Certificate Validation vulnerability report

high severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.80.0-r1 and curl/libcurl@7.80.0-r1
  • Fixed in: 7.80.0-r2

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › curl/curl@7.80.0-r1
  • Introduced through: nginx@1.21-alpine-perl › curl/libcurl@7.80.0-r1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

libcurl provides the CURLOPT_CERTINFO option to allow applications torequest details to be returned about a server's certificate chain.Due to an erroneous function, a malicious server could make libcurl built withNSS get stuck in a never-ending busy-loop when trying to retrieve thatinformation.

Remediation

Upgrade Alpine:3.15 curl to version 7.80.0-r2 or higher.

References

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability report

high severity

Server-Side Request Forgery (SSRF)

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.80.0-r1 and curl/libcurl@7.80.0-r1
  • Fixed in: 7.80.0-r2

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › curl/curl@7.80.0-r1
  • Introduced through: nginx@1.21-alpine-perl › curl/libcurl@7.80.0-r1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

The curl URL parser wrongly accepts percent-encoded URL separators like '/'when decoding the host name part of a URL, making it a different URL usingthe wrong host name when it is later retrieved.For example, a URL like http://example.com%2F127.0.0.1/, would be allowed bythe parser and get transposed into http://example.com/127.0.0.1/. This flawcan be used to circumvent filters, checks and more.

Remediation

Upgrade Alpine:3.15 curl to version 7.80.0-r2 or higher.

References

Server-Side Request Forgery (SSRF) vulnerability report

high severity

Use After Free

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.80.0-r1 and curl/libcurl@7.80.0-r1
  • Fixed in: 8.1.0-r0

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › curl/curl@7.80.0-r1
  • Introduced through: nginx@1.21-alpine-perl › curl/libcurl@7.80.0-r1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

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.

Remediation

Upgrade Alpine:3.15 curl to version 8.1.0-r0 or higher.

References

Use After Free vulnerability report

high severity

Out-of-bounds Read

  • Vulnerable module: freetype/freetype
  • Introduced through: freetype/freetype@2.11.1-r1
  • Fixed in: 2.11.1-r2

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › freetype/freetype@2.11.1-r1

NVD Description

Note: Versions mentioned in the description apply only to the upstream freetype package and not the freetype package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

FreeType commit 22a0cccb4d9d002f33c1ba7a4b36812c7d4f46b5 was discovered to contain a segmentation violation via the function FT_Request_Size.

Remediation

Upgrade Alpine:3.15 freetype to version 2.11.1-r2 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Out-of-bounds Read

  • Vulnerable module: freetype/freetype
  • Introduced through: freetype/freetype@2.11.1-r1
  • Fixed in: 2.11.1-r2

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › freetype/freetype@2.11.1-r1

NVD Description

Note: Versions mentioned in the description apply only to the upstream freetype package and not the freetype package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

FreeType commit 53dfdcd8198d2b3201a23c4bad9190519ba918db was discovered to contain a segmentation violation via the function FNT_Size_Request.

Remediation

Upgrade Alpine:3.15 freetype to version 2.11.1-r2 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Double Free

  • Vulnerable module: libwebp/libwebp
  • Introduced through: libwebp/libwebp@1.2.2-r0
  • Fixed in: 1.2.2-r1

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › libwebp/libwebp@1.2.2-r0

NVD Description

Note: Versions mentioned in the description apply only to the upstream libwebp package and not the libwebp package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

There exists a use after free/double free in libwebp. An attacker can use the ApplyFiltersAndEncode() function and loop through to free best.bw and assign best = trial pointer. The second loop will then return 0 because of an Out of memory error in VP8 encoder, the pointer is still assigned to trial and the AddressSanitizer will attempt a double free.

Remediation

Upgrade Alpine:3.15 libwebp to version 1.2.2-r1 or higher.

References

Double Free vulnerability report

high severity

Integer Overflow or Wraparound

  • Vulnerable module: libxml2/libxml2
  • Introduced through: libxml2/libxml2@2.9.14-r0
  • Fixed in: 2.9.14-r2

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › libxml2/libxml2@2.9.14-r0

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

An issue was discovered in libxml2 before 2.10.3. When parsing a multi-gigabyte XML document with the XML_PARSE_HUGE parser option enabled, several integer counters can overflow. This results in an attempt to access an array at a negative 2GB offset, typically leading to a segmentation fault.

Remediation

Upgrade Alpine:3.15 libxml2 to version 2.9.14-r2 or higher.

References

Integer Overflow or Wraparound vulnerability report

high severity

NULL Pointer Dereference

  • Vulnerable module: libxml2/libxml2
  • Introduced through: libxml2/libxml2@2.9.14-r0
  • Fixed in: 2.9.14-r1

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › libxml2/libxml2@2.9.14-r0

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

NULL Pointer Dereference allows attackers to cause a denial of service (or application crash). This only applies when lxml is used together with libxml2 2.9.10 through 2.9.14. libxml2 2.9.9 and earlier are not affected. It allows triggering crashes through forged input data, given a vulnerable code sequence in the application. The vulnerability is caused by the iterwalk function (also used by the canonicalize function). Such code shouldn't be in wide-spread use, given that parsing + iterwalk would usually be replaced with the more efficient iterparse function. However, an XML converter that serialises to C14N would also be vulnerable, for example, and there are legitimate use cases for this code sequence. If untrusted input is received (also remotely) and processed via iterwalk function, a crash can be triggered.

Remediation

Upgrade Alpine:3.15 libxml2 to version 2.9.14-r1 or higher.

References

NULL Pointer Dereference vulnerability report

high severity

CVE-2023-44487

  • Vulnerable module: nghttp2/nghttp2-libs
  • Introduced through: nghttp2/nghttp2-libs@1.46.0-r0
  • Fixed in: 1.46.0-r2

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › nghttp2/nghttp2-libs@1.46.0-r0

NVD Description

Note: Versions mentioned in the description apply only to the upstream nghttp2 package and not the nghttp2 package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.

Remediation

Upgrade Alpine:3.15 nghttp2 to version 1.46.0-r2 or higher.

References

CVE-2023-44487 vulnerability report

high severity

Incomplete Cleanup

  • Vulnerable module: nghttp2/nghttp2-libs
  • Introduced through: nghttp2/nghttp2-libs@1.46.0-r0
  • Fixed in: 1.46.0-r1

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › nghttp2/nghttp2-libs@1.46.0-r0

NVD Description

Note: Versions mentioned in the description apply only to the upstream nghttp2 package and not the nghttp2 package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

Envoy is a cloud-native high-performance edge/middle/service proxy. Envoy’s HTTP/2 codec may leak a header map and bookkeeping structures upon receiving RST_STREAM immediately followed by the GOAWAY frames from an upstream server. In nghttp2, cleanup of pending requests due to receipt of the GOAWAY frame skips de-allocation of the bookkeeping structure and pending compressed header. The error return [code path] is taken if connection is already marked for not sending more requests due to GOAWAY frame. The clean-up code is right after the return statement, causing memory leak. Denial of service through memory exhaustion. This vulnerability was patched in versions(s) 1.26.3, 1.25.8, 1.24.9, 1.23.11.

Remediation

Upgrade Alpine:3.15 nghttp2 to version 1.46.0-r1 or higher.

References

Incomplete Cleanup vulnerability report

high severity

Double Free

  • Vulnerable module: openssl/libcrypto1.1
  • Introduced through: openssl/libcrypto1.1@1.1.1n-r0 and openssl/libssl1.1@1.1.1n-r0
  • Fixed in: 1.1.1t-r0

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › openssl/libcrypto1.1@1.1.1n-r0
  • Introduced through: nginx@1.21-alpine-perl › openssl/libssl1.1@1.1.1n-r0

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload data. If the function succeeds then the "name_out", "header" and "data" arguments are populated with pointers to buffers containing the relevant decoded data. The caller is responsible for freeing those buffers. It is possible to construct a PEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex() will return a failure code but will populate the header argument with a pointer to a buffer that has already been freed. If the caller also frees this buffer then a double free will occur. This will most likely lead to a crash. This could be exploited by an attacker who has the ability to supply malicious PEM files for parsing to achieve a denial of service attack.

The functions PEM_read_bio() and PEM_read() are simple wrappers around PEM_read_bio_ex() and therefore these functions are also directly affected.

These functions are also called indirectly by a number of other OpenSSL functions including PEM_X509_INFO_read_bio_ex() and SSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL internal uses of these functions are not vulnerable because the caller does not free the header argument if PEM_read_bio_ex() returns a failure code. These locations include the PEM_read_bio_TYPE() functions as well as the decoders introduced in OpenSSL 3.0.

The OpenSSL asn1parse command line application is also impacted by this issue.

Remediation

Upgrade Alpine:3.15 openssl to version 1.1.1t-r0 or higher.

References

Double Free vulnerability report

high severity

Improper Certificate Validation

  • Vulnerable module: openssl/libcrypto1.1
  • Introduced through: openssl/libcrypto1.1@1.1.1n-r0 and openssl/libssl1.1@1.1.1n-r0
  • Fixed in: 1.1.1t-r2

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › openssl/libcrypto1.1@1.1.1n-r0
  • Introduced through: nginx@1.21-alpine-perl › openssl/libssl1.1@1.1.1n-r0

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

A security vulnerability has been identified in all supported versions

of OpenSSL related to the verification of X.509 certificate chains that include policy constraints. Attackers may be able to exploit this vulnerability by creating a malicious certificate chain that triggers exponential use of computational resources, leading to a denial-of-service (DoS) attack on affected systems.

Policy processing is disabled by default but can be enabled by passing the -policy&#39; argument to the command line utilities or by calling the X509_VERIFY_PARAM_set1_policies()' function.

Remediation

Upgrade Alpine:3.15 openssl to version 1.1.1t-r2 or higher.

References

Improper Certificate Validation vulnerability report

high severity

Use After Free

  • Vulnerable module: openssl/libcrypto1.1
  • Introduced through: openssl/libcrypto1.1@1.1.1n-r0 and openssl/libssl1.1@1.1.1n-r0
  • Fixed in: 1.1.1t-r0

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › openssl/libcrypto1.1@1.1.1n-r0
  • Introduced through: nginx@1.21-alpine-perl › openssl/libssl1.1@1.1.1n-r0

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

The public API function BIO_new_NDEF is a helper function used for streaming ASN.1 data via a BIO. It is primarily used internally to OpenSSL to support the SMIME, CMS and PKCS7 streaming capabilities, but may also be called directly by end user applications.

The function receives a BIO from the caller, prepends a new BIO_f_asn1 filter BIO onto the front of it to form a BIO chain, and then returns the new head of the BIO chain to the caller. Under certain conditions, for example if a CMS recipient public key is invalid, the new filter BIO is freed and the function returns a NULL result indicating a failure. However, in this case, the BIO chain is not properly cleaned up and the BIO passed by the caller still retains internal pointers to the previously freed filter BIO. If the caller then goes on to call BIO_pop() on the BIO then a use-after-free will occur. This will most likely result in a crash.

This scenario occurs directly in the internal function B64_write_ASN1() which may cause BIO_new_NDEF() to be called and will subsequently call BIO_pop() on the BIO. This internal function is in turn called by the public API functions PEM_write_bio_ASN1_stream, PEM_write_bio_CMS_stream, PEM_write_bio_PKCS7_stream, SMIME_write_ASN1, SMIME_write_CMS and SMIME_write_PKCS7.

Other public API functions that may be impacted by this include i2d_ASN1_bio_stream, BIO_new_CMS, BIO_new_PKCS7, i2d_CMS_bio_stream and i2d_PKCS7_bio_stream.

The OpenSSL cms and smime command line applications are similarly affected.

Remediation

Upgrade Alpine:3.15 openssl to version 1.1.1t-r0 or higher.

References

Use After Free vulnerability report

high severity

Integer Overflow or Wraparound

  • Vulnerable module: pcre2/pcre2
  • Introduced through: pcre2/pcre2@10.39-r0
  • Fixed in: 10.42-r0

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › pcre2/pcre2@10.39-r0

NVD Description

Note: Versions mentioned in the description apply only to the upstream pcre2 package and not the pcre2 package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

Integer overflow vulnerability in pcre2test before 10.41 allows attackers to cause a denial of service or other unspecified impacts via negative input.

Remediation

Upgrade Alpine:3.15 pcre2 to version 10.42-r0 or higher.

References

Integer Overflow or Wraparound vulnerability report

high severity

Access of Resource Using Incompatible Type ('Type Confusion')

  • Vulnerable module: openssl/libcrypto1.1
  • Introduced through: openssl/libcrypto1.1@1.1.1n-r0 and openssl/libssl1.1@1.1.1n-r0
  • Fixed in: 1.1.1t-r0

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › openssl/libcrypto1.1@1.1.1n-r0
  • Introduced through: nginx@1.21-alpine-perl › openssl/libssl1.1@1.1.1n-r0

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING.

When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network.

Remediation

Upgrade Alpine:3.15 openssl to version 1.1.1t-r0 or higher.

References

Access of Resource Using Incompatible Type ('Type Confusion') vulnerability report

high severity

Out-of-bounds Read

  • Vulnerable module: ncurses/ncurses-libs
  • Introduced through: ncurses/ncurses-libs@6.3_p20211120-r0 and ncurses/ncurses-terminfo-base@6.3_p20211120-r0
  • Fixed in: 6.3_p20211120-r1

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › ncurses/ncurses-libs@6.3_p20211120-r0
  • Introduced through: nginx@1.21-alpine-perl › ncurses/ncurses-terminfo-base@6.3_p20211120-r0

NVD Description

Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

ncurses 6.3 before patch 20220416 has an out-of-bounds read and segmentation violation in convert_strings in tinfo/read_entry.c in the terminfo library.

Remediation

Upgrade Alpine:3.15 ncurses to version 6.3_p20211120-r1 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.80.0-r1 and curl/libcurl@7.80.0-r1
  • Fixed in: 7.80.0-r2

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › curl/curl@7.80.0-r1
  • Introduced through: nginx@1.21-alpine-perl › curl/libcurl@7.80.0-r1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

curl < 7.84.0 supports "chained" HTTP compression algorithms, meaning that a serverresponse can be compressed multiple times and potentially with different algorithms. The number of acceptable "links" in this "decompression chain" was unbounded, allowing a malicious server to insert a virtually unlimited number of compression steps.The use of such a decompression chain could result in a "malloc bomb", makingcurl end up spending enormous amounts of allocated heap memory, or trying toand returning out of memory errors.

Remediation

Upgrade Alpine:3.15 curl to version 7.80.0-r2 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.80.0-r1 and curl/libcurl@7.80.0-r1
  • Fixed in: 7.80.0-r6

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › curl/curl@7.80.0-r1
  • Introduced through: nginx@1.21-alpine-perl › curl/libcurl@7.80.0-r1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

An allocation of resources without limits or throttling vulnerability exists in curl <v7.88.0 based on the "chained" HTTP compression algorithms, meaning that a server response can be compressed multiple times and potentially with differentalgorithms. The number of acceptable "links" in this "decompression chain" wascapped, but the cap was implemented on a per-header basis allowing a maliciousserver to insert a virtually unlimited number of compression steps simply byusing many headers. The use of such a decompression chain could result in a "malloc bomb", making curl end up spending enormous amounts of allocated heap memory, or trying to and returning out of memory errors.

Remediation

Upgrade Alpine:3.15 curl to version 7.80.0-r6 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

medium severity

Cleartext Transmission of Sensitive Information

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.80.0-r1 and curl/libcurl@7.80.0-r1
  • Fixed in: 7.80.0-r6

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › curl/curl@7.80.0-r1
  • Introduced through: nginx@1.21-alpine-perl › curl/libcurl@7.80.0-r1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

A cleartext transmission of sensitive information vulnerability exists in curl <v7.88.0 that could cause HSTS functionality to behave incorrectly when multiple URLs are requested in parallel. Using its HSTS support, curl can be instructed to use HTTPS instead of using an insecure clear-text HTTP step even when HTTP is provided in the URL. This HSTS mechanism would however surprisingly fail when multiple transfers are done in parallel as the HSTS cache file gets overwritten by the most recentlycompleted transfer. A later HTTP-only transfer to the earlier host name would then not get upgraded properly to HSTS.

Remediation

Upgrade Alpine:3.15 curl to version 7.80.0-r6 or higher.

References

Cleartext Transmission of Sensitive Information vulnerability report

medium severity

CVE-2023-46218

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.80.0-r1 and curl/libcurl@7.80.0-r1
  • Fixed in: 8.5.0-r0

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › curl/curl@7.80.0-r1
  • Introduced through: nginx@1.21-alpine-perl › curl/libcurl@7.80.0-r1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

This flaw allows a malicious HTTP server to set "super cookies" in curl that are then passed back to more origins than what is otherwise allowed or possible. This allows a site to set cookies that then would get sent to different and unrelated sites and domains.

It could do this by exploiting a mixed case flaw in curl's function that verifies a given cookie domain against the Public Suffix List (PSL). For example a cookie could be set with domain=co.UK when the URL used a lower case hostname curl.co.uk, even though co.uk is listed as a PSL domain.

Remediation

Upgrade Alpine:3.15 curl to version 8.5.0-r0 or higher.

References

CVE-2023-46218 vulnerability report

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: openssl/libcrypto1.1
  • Introduced through: openssl/libcrypto1.1@1.1.1n-r0 and openssl/libssl1.1@1.1.1n-r0
  • Fixed in: 1.1.1u-r0

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › openssl/libcrypto1.1@1.1.1n-r0
  • Introduced through: nginx@1.21-alpine-perl › openssl/libssl1.1@1.1.1n-r0

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

Issue summary: Processing some specially crafted ASN.1 object identifiers or data containing them may be very slow.

Impact summary: Applications that use OBJ_obj2txt() directly, or use any of the OpenSSL subsystems OCSP, PKCS7/SMIME, CMS, CMP/CRMF or TS with no message size limit may experience notable to very long delays when processing those messages, which may lead to a Denial of Service.

An OBJECT IDENTIFIER is composed of a series of numbers - sub-identifiers - most of which have no size limit. OBJ_obj2txt() may be used to translate an ASN.1 OBJECT IDENTIFIER given in DER encoding form (using the OpenSSL type ASN1_OBJECT) to its canonical numeric text form, which are the sub-identifiers of the OBJECT IDENTIFIER in decimal form, separated by periods.

When one of the sub-identifiers in the OBJECT IDENTIFIER is very large (these are sizes that are seen as absurdly large, taking up tens or hundreds of KiBs), the translation to a decimal number in text may take a very long time. The time complexity is O(n^2) with 'n' being the size of the sub-identifiers in bytes (*).

With OpenSSL 3.0, support to fetch cryptographic algorithms using names / identifiers in string form was introduced. This includes using OBJECT IDENTIFIERs in canonical numeric text form as identifiers for fetching algorithms.

Such OBJECT IDENTIFIERs may be received through the ASN.1 structure AlgorithmIdentifier, which is commonly used in multiple protocols to specify what cryptographic algorithm should be used to sign or verify, encrypt or decrypt, or digest passed data.

Applications that call OBJ_obj2txt() directly with untrusted data are affected, with any version of OpenSSL. If the use is for the mere purpose of display, the severity is considered low.

In OpenSSL 3.0 and newer, this affects the subsystems OCSP, PKCS7/SMIME, CMS, CMP/CRMF or TS. It also impacts anything that processes X.509 certificates, including simple things like verifying its signature.

The impact on TLS is relatively low, because all versions of OpenSSL have a 100KiB limit on the peer's certificate chain. Additionally, this only impacts clients, or servers that have explicitly enabled client authentication.

In OpenSSL 1.1.1 and 1.0.2, this only affects displaying diverse objects, such as X.509 certificates. This is assumed to not happen in such a way that it would cause a Denial of Service, so these versions are considered not affected by this issue in such a way that it would be cause for concern, and the severity is therefore considered low.

Remediation

Upgrade Alpine:3.15 openssl to version 1.1.1u-r0 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

medium severity

Double Free

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.80.0-r1 and curl/libcurl@7.80.0-r1
  • Fixed in: 8.0.1-r0

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › curl/curl@7.80.0-r1
  • Introduced through: nginx@1.21-alpine-perl › curl/libcurl@7.80.0-r1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

A double free vulnerability exists in libcurl <8.0.0 when sharing HSTS data between separate "handles". This sharing was introduced without considerations for do this sharing across separate threads but there was no indication of this fact in the documentation. Due to missing mutexes or thread locks, two threads sharing the same HSTS data could end up doing a double-free or use-after-free.

Remediation

Upgrade Alpine:3.15 curl to version 8.0.1-r0 or higher.

References

Double Free vulnerability report

medium severity

Improper Authentication

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.80.0-r1 and curl/libcurl@7.80.0-r1
  • Fixed in: 8.0.1-r0

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › curl/curl@7.80.0-r1
  • Introduced through: nginx@1.21-alpine-perl › curl/libcurl@7.80.0-r1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

An authentication bypass vulnerability exists libcurl <8.0.0 in the connection reuse feature which can reuse previously established connections with incorrect user permissions due to a failure to check for changes in the CURLOPT_GSSAPI_DELEGATION option. This vulnerability affects krb5/kerberos/negotiate/GSSAPI transfers and could potentially result in unauthorized access to sensitive information. The safest option is to not reuse connections if the CURLOPT_GSSAPI_DELEGATION option has been changed.

Remediation

Upgrade Alpine:3.15 curl to version 8.0.1-r0 or higher.

References

Improper Authentication vulnerability report

medium severity

Improper Authentication

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.80.0-r1 and curl/libcurl@7.80.0-r1
  • Fixed in: 8.0.1-r0

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › curl/curl@7.80.0-r1
  • Introduced through: nginx@1.21-alpine-perl › curl/libcurl@7.80.0-r1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

An authentication bypass vulnerability exists in libcurl <8.0.0 in the FTP connection reuse feature that can result in wrong credentials being used during subsequent transfers. Previously created connections are kept in a connection pool for reuse if they match the current setup. However, certain FTP settings such as CURLOPT_FTP_ACCOUNT, CURLOPT_FTP_ALTERNATIVE_TO_USER, CURLOPT_FTP_SSL_CCC, and CURLOPT_USE_SSL were not included in the configuration match checks, causing them to match too easily. This could lead to libcurl using the wrong credentials when performing a transfer, potentially allowing unauthorized access to sensitive information.

Remediation

Upgrade Alpine:3.15 curl to version 8.0.1-r0 or higher.

References

Improper Authentication vulnerability report

medium severity

Improper Certificate Validation

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.80.0-r1 and curl/libcurl@7.80.0-r1
  • Fixed in: 8.1.0-r0

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › curl/curl@7.80.0-r1
  • Introduced through: nginx@1.21-alpine-perl › curl/libcurl@7.80.0-r1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

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.

Remediation

Upgrade Alpine:3.15 curl to version 8.1.0-r0 or higher.

References

Improper Certificate Validation vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.80.0-r1 and curl/libcurl@7.80.0-r1
  • Fixed in: 7.80.0-r2

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › curl/curl@7.80.0-r1
  • Introduced through: nginx@1.21-alpine-perl › curl/libcurl@7.80.0-r1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

When curl < 7.84.0 does FTP transfers secured by krb5, it handles message verification failures wrongly. This flaw makes it possible for a Man-In-The-Middle attack to go unnoticed and even allows it to inject data to the client.

Remediation

Upgrade Alpine:3.15 curl to version 7.80.0-r2 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Race Condition

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.80.0-r1 and curl/libcurl@7.80.0-r1
  • Fixed in: 8.1.0-r0

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › curl/curl@7.80.0-r1
  • Introduced through: nginx@1.21-alpine-perl › curl/libcurl@7.80.0-r1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

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.

Remediation

Upgrade Alpine:3.15 curl to version 8.1.0-r0 or higher.

References

Race Condition vulnerability report

medium severity

Use After Free

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.80.0-r1 and curl/libcurl@7.80.0-r1
  • Fixed in: 7.80.0-r5

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › curl/curl@7.80.0-r1
  • Introduced through: nginx@1.21-alpine-perl › curl/libcurl@7.80.0-r1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

A use after free vulnerability exists in curl <7.87.0. Curl can be asked to tunnel virtually all protocols it supports through an HTTP proxy. HTTP proxies can (and often do) deny such tunnel operations. When getting denied to tunnel the specific protocols SMB or TELNET, curl would use a heap-allocated struct after it had been freed, in its transfer shutdown code path.

Remediation

Upgrade Alpine:3.15 curl to version 7.80.0-r5 or higher.

References

Use After Free vulnerability report

medium severity

Information Exposure

  • Vulnerable module: openssl/libcrypto1.1
  • Introduced through: openssl/libcrypto1.1@1.1.1n-r0 and openssl/libssl1.1@1.1.1n-r0
  • Fixed in: 1.1.1t-r0

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › openssl/libcrypto1.1@1.1.1n-r0
  • Introduced through: nginx@1.21-alpine-perl › openssl/libssl1.1@1.1.1n-r0

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

A timing based side channel exists in the OpenSSL RSA Decryption implementation which could be sufficient to recover a plaintext across a network in a Bleichenbacher style attack. To achieve a successful decryption an attacker would have to be able to send a very large number of trial messages for decryption. The vulnerability affects all RSA padding modes: PKCS#1 v1.5, RSA-OEAP and RSASVE.

For example, in a TLS connection, RSA is commonly used by a client to send an encrypted pre-master secret to the server. An attacker that had observed a genuine connection between a client and a server could use this flaw to send trial messages to the server and record the time taken to process them. After a sufficiently large number of messages the attacker could recover the pre-master secret used for the original connection and thus be able to decrypt the application data sent over that connection.

Remediation

Upgrade Alpine:3.15 openssl to version 1.1.1t-r0 or higher.

References

Information Exposure vulnerability report

medium severity

Improper Authentication

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.80.0-r1 and curl/libcurl@7.80.0-r1
  • Fixed in: 8.0.1-r0

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › curl/curl@7.80.0-r1
  • Introduced through: nginx@1.21-alpine-perl › curl/libcurl@7.80.0-r1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

An authentication bypass vulnerability exists in libcurl prior to v8.0.0 where it reuses a previously established SSH connection despite the fact that an SSH option was modified, which should have prevented reuse. libcurl maintains a pool of previously used connections to reuse them for subsequent transfers if the configurations match. However, two SSH settings were omitted from the configuration check, allowing them to match easily, potentially leading to the reuse of an inappropriate connection.

Remediation

Upgrade Alpine:3.15 curl to version 8.0.1-r0 or higher.

References

Improper Authentication vulnerability report

medium severity

Missing Encryption of Sensitive Data

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.80.0-r1 and curl/libcurl@7.80.0-r1
  • Fixed in: 8.5.0-r0

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › curl/curl@7.80.0-r1
  • Introduced through: nginx@1.21-alpine-perl › curl/libcurl@7.80.0-r1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

When saving HSTS data to an excessively long file name, curl could end up removing all contents, making subsequent requests using that file unaware of the HSTS status they should otherwise use.

Remediation

Upgrade Alpine:3.15 curl to version 8.5.0-r0 or higher.

References

Missing Encryption of Sensitive Data vulnerability report

medium severity

Excessive Iteration

  • Vulnerable module: openssl/libcrypto1.1
  • Introduced through: openssl/libcrypto1.1@1.1.1n-r0 and openssl/libssl1.1@1.1.1n-r0
  • Fixed in: 1.1.1v-r0

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › openssl/libcrypto1.1@1.1.1n-r0
  • Introduced through: nginx@1.21-alpine-perl › openssl/libssl1.1@1.1.1n-r0

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

Issue summary: Checking excessively long DH keys or parameters may be very slow.

Impact summary: Applications that use the functions DH_check(), DH_check_ex() or EVP_PKEY_param_check() to check a DH key or DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service.

The function DH_check() performs various checks on DH parameters. After fixing CVE-2023-3446 it was discovered that a large q parameter value can also trigger an overly long computation during some of these checks. A correct q value, if present, cannot be larger than the modulus p parameter, thus it is unnecessary to perform these checks if q is larger than p.

An application that calls DH_check() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack.

The function DH_check() is itself called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_ex() and EVP_PKEY_param_check().

Also vulnerable are the OpenSSL dhparam and pkeyparam command line applications when using the "-check" option.

The OpenSSL SSL/TLS implementation is not affected by this issue.

The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.

Remediation

Upgrade Alpine:3.15 openssl to version 1.1.1v-r0 or higher.

References

Excessive Iteration vulnerability report

medium severity

Improper Certificate Validation

  • Vulnerable module: openssl/libcrypto1.1
  • Introduced through: openssl/libcrypto1.1@1.1.1n-r0 and openssl/libssl1.1@1.1.1n-r0
  • Fixed in: 1.1.1t-r2

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › openssl/libcrypto1.1@1.1.1n-r0
  • Introduced through: nginx@1.21-alpine-perl › openssl/libssl1.1@1.1.1n-r0

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

Applications that use a non-default option when verifying certificates may be vulnerable to an attack from a malicious CA to circumvent certain checks.

Invalid certificate policies in leaf certificates are silently ignored by OpenSSL and other certificate policy checks are skipped for that certificate. A malicious CA could use this to deliberately assert invalid certificate policies in order to circumvent policy checking on the certificate altogether.

Policy processing is disabled by default but can be enabled by passing the -policy&#39; argument to the command line utilities or by calling the X509_VERIFY_PARAM_set1_policies()' function.

Remediation

Upgrade Alpine:3.15 openssl to version 1.1.1t-r2 or higher.

References

Improper Certificate Validation vulnerability report

medium severity

Improper Check for Unusual or Exceptional Conditions

  • Vulnerable module: openssl/libcrypto1.1
  • Introduced through: openssl/libcrypto1.1@1.1.1n-r0 and openssl/libssl1.1@1.1.1n-r0
  • Fixed in: 1.1.1w-r1

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › openssl/libcrypto1.1@1.1.1n-r0
  • Introduced through: nginx@1.21-alpine-perl › openssl/libssl1.1@1.1.1n-r0

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

Issue summary: Generating excessively long X9.42 DH keys or checking excessively long X9.42 DH keys or parameters may be very slow.

Impact summary: Applications that use the functions DH_generate_key() to generate an X9.42 DH key may experience long delays. Likewise, applications that use DH_check_pub_key(), DH_check_pub_key_ex() or EVP_PKEY_public_check() to check an X9.42 DH key or X9.42 DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service.

While DH_check() performs all the necessary checks (as of CVE-2023-3817), DH_check_pub_key() doesn't make any of these checks, and is therefore vulnerable for excessively large P and Q parameters.

Likewise, while DH_generate_key() performs a check for an excessively large P, it doesn't check for an excessively large Q.

An application that calls DH_generate_key() or DH_check_pub_key() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack.

DH_generate_key() and DH_check_pub_key() are also called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_pub_key_ex(), EVP_PKEY_public_check(), and EVP_PKEY_generate().

Also vulnerable are the OpenSSL pkey command line application when using the "-pubcheck" option, as well as the OpenSSL genpkey command line application.

The OpenSSL SSL/TLS implementation is not affected by this issue.

The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.

Remediation

Upgrade Alpine:3.15 openssl to version 1.1.1w-r1 or higher.

References

Improper Check for Unusual or Exceptional Conditions vulnerability report

medium severity

Inefficient Regular Expression Complexity

  • Vulnerable module: openssl/libcrypto1.1
  • Introduced through: openssl/libcrypto1.1@1.1.1n-r0 and openssl/libssl1.1@1.1.1n-r0
  • Fixed in: 1.1.1u-r2

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › openssl/libcrypto1.1@1.1.1n-r0
  • Introduced through: nginx@1.21-alpine-perl › openssl/libssl1.1@1.1.1n-r0

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

Issue summary: Checking excessively long DH keys or parameters may be very slow.

Impact summary: Applications that use the functions DH_check(), DH_check_ex() or EVP_PKEY_param_check() to check a DH key or DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service.

The function DH_check() performs various checks on DH parameters. One of those checks confirms that the modulus ('p' parameter) is not too large. Trying to use a very large modulus is slow and OpenSSL will not normally use a modulus which is over 10,000 bits in length.

However the DH_check() function checks numerous aspects of the key or parameters that have been supplied. Some of those checks use the supplied modulus value even if it has already been found to be too large.

An application that calls DH_check() and supplies a key or parameters obtained from an untrusted source could be vulernable to a Denial of Service attack.

The function DH_check() is itself called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_ex() and EVP_PKEY_param_check().

Also vulnerable are the OpenSSL dhparam and pkeyparam command line applications when using the '-check' option.

The OpenSSL SSL/TLS implementation is not affected by this issue. The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.

Remediation

Upgrade Alpine:3.15 openssl to version 1.1.1u-r2 or higher.

References

Inefficient Regular Expression Complexity vulnerability report

medium severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: openssl/libcrypto1.1
  • Introduced through: openssl/libcrypto1.1@1.1.1n-r0 and openssl/libssl1.1@1.1.1n-r0
  • Fixed in: 1.1.1q-r0

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › openssl/libcrypto1.1@1.1.1n-r0
  • Introduced through: nginx@1.21-alpine-perl › openssl/libssl1.1@1.1.1n-r0

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

AES OCB mode for 32-bit x86 platforms using the AES-NI assembly optimised implementation will not encrypt the entirety of the data under some circumstances. This could reveal sixteen bytes of data that was preexisting in the memory that wasn't written. In the special case of "in place" encryption, sixteen bytes of the plaintext would be revealed. Since OpenSSL does not support OCB based cipher suites for TLS and DTLS, they are both unaffected. Fixed in OpenSSL 3.0.5 (Affected 3.0.0-3.0.4). Fixed in OpenSSL 1.1.1q (Affected 1.1.1-1.1.1p).

Remediation

Upgrade Alpine:3.15 openssl to version 1.1.1q-r0 or higher.

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.80.0-r1 and curl/libcurl@7.80.0-r1
  • Fixed in: 7.80.0-r2

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › curl/curl@7.80.0-r1
  • Introduced through: nginx@1.21-alpine-perl › curl/libcurl@7.80.0-r1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

A malicious server can serve excessive amounts of Set-Cookie: headers in a HTTP response to curl and curl < 7.84.0 stores all of them. A sufficiently large amount of (big) cookies make subsequent HTTP requests to this, or other servers to which the cookies match, create requests that become larger than the threshold that curl uses internally to avoid sending crazy large requests (1048576 bytes) and instead returns an error.This denial state might remain for as long as the same cookies are kept, match and haven't expired. Due to cookie matching rules, a server on foo.example.com can set cookies that also would match for bar.example.com, making it it possible for a "sister server" to effectively cause a denial of service for a sibling site on the same second level domain using this method.

Remediation

Upgrade Alpine:3.15 curl to version 7.80.0-r2 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

low severity

CVE-2022-35252

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.80.0-r1 and curl/libcurl@7.80.0-r1
  • Fixed in: 7.80.0-r3

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › curl/curl@7.80.0-r1
  • Introduced through: nginx@1.21-alpine-perl › curl/libcurl@7.80.0-r1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

When curl is used to retrieve and parse cookies from a HTTP(S) server, itaccepts cookies using control codes that when later are sent back to a HTTPserver might make the server return 400 responses. Effectively allowing a"sister site" to deny service to all siblings.

Remediation

Upgrade Alpine:3.15 curl to version 7.80.0-r3 or higher.

References

CVE-2022-35252 vulnerability report

low severity

CVE-2023-28322

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.80.0-r1 and curl/libcurl@7.80.0-r1
  • Fixed in: 8.1.0-r0

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › curl/curl@7.80.0-r1
  • Introduced through: nginx@1.21-alpine-perl › curl/libcurl@7.80.0-r1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

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.

Remediation

Upgrade Alpine:3.15 curl to version 8.1.0-r0 or higher.

References

CVE-2023-28322 vulnerability report

low severity

CVE-2023-38546

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.80.0-r1 and curl/libcurl@7.80.0-r1
  • Fixed in: 8.4.0-r0

Detailed paths

  • Introduced through: nginx@1.21-alpine-perl › curl/curl@7.80.0-r1
  • Introduced through: nginx@1.21-alpine-perl › curl/libcurl@7.80.0-r1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Alpine. See How to fix? for Alpine:3.15 relevant fixed versions and status.

This flaw allows an attacker to insert cookies at will into a running program using libcurl, if the specific series of conditions are met.

libcurl performs transfers. In its API, an application creates "easy handles" that are the individual handles for single transfers.

libcurl provides a function call that duplicates en easy handle called curl_easy_duphandle.

If a transfer has cookies enabled when the handle is duplicated, the cookie-enable state is also cloned - but without cloning the actual cookies. If the source handle did not read any cookies from a specific file on disk, the cloned version of the handle would instead store the file name as none (using the four ASCII letters, no quotes).

Subsequent use of the cloned handle that does not explicitly set a source to load cookies from would then inadvertently load cookies from a file named none - if such a file exists and is readable in the current directory of the program using libcurl. And if using the correct file format of course.

Remediation

Upgrade Alpine:3.15 curl to version 8.4.0-r0 or higher.

References

CVE-2023-38546 vulnerability report