Vulnerabilities

 35 via 60 paths

Dependencies

 18

Source

 Group 6 Copy Created with Sketch. Docker

Target OS

 alpine:3.17.3
Test your Docker Hub image against our market leading vulnerability database Sign up for free
Severity
  • 7
  • 17
  • 11
Status
  • 35
  • 0
  • 0
OS binaries
  • 21
  • 14

high severity

Code Injection

  • Vulnerable module: node
  • Introduced through: node@14.21.3

Detailed paths

  • Introduced through: docker-image|node@14-alpine › node@14.21.3

Overview

node is a JavaScript runtime built on Chrome's V8 JavaScript engine.

Affected versions of this package are vulnerable to Code Injection due to the incorrect handling of environment variables on Linux when the process is running with elevated privileges that the current user lacks (does not apply to CAP_NET_BIND_SERVICE).

Remediation

Upgrade node to version 18.19.1, 20.11.1, 21.6.2 or higher.

References

Code Injection vulnerability report

high severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: node
  • Introduced through: node@14.21.3

Detailed paths

  • Introduced through: docker-image|node@14-alpine › node@14.21.3

Overview

node is a JavaScript runtime built on Chrome's V8 JavaScript engine.

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling due to a lack of safeguards on chunk extension bytes. The server may read an unbounded number of bytes from a single connection, which allows an attacker to cause denial of service via CPU and network bandwidth exhaustion.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

  • High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

  • Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package

Remediation

Upgrade node to version 18.19.1, 20.11.1, 21.6.2 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

high severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: node
  • Introduced through: node@14.21.3

Detailed paths

  • Introduced through: docker-image|node@14-alpine › node@14.21.3

Overview

node is a JavaScript runtime built on Chrome's V8 JavaScript engine.

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling due to a race condition in Http2Session when nghttp2 data is left in memory after a connection is reset while processing HTTP/2 CONTINUATION frames. An attacker can cause denial of service by sending such frames then triggering the Http2Session destructor.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

  • High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

  • Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package

Remediation

Upgrade node to version 18.20.1, 20.12.1, 21.7.2 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

high severity

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

  • Vulnerable module: openssl/libcrypto3
  • Introduced through: openssl/libcrypto3@3.0.8-r3 and openssl/libssl3@3.0.8-r3
  • Fixed in: 3.0.15-r0

Detailed paths

  • Introduced through: node@14-alpine › openssl/libcrypto3@3.0.8-r3
  • Introduced through: node@14-alpine › openssl/libssl3@3.0.8-r3

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.17 relevant fixed versions and status.

Issue summary: Applications performing certificate name checks (e.g., TLS clients checking server certificates) may attempt to read an invalid memory address resulting in abnormal termination of the application process.

Impact summary: Abnormal termination of an application can a cause a denial of service.

Applications performing certificate name checks (e.g., TLS clients checking server certificates) may attempt to read an invalid memory address when comparing the expected name with an otherName subject alternative name of an X.509 certificate. This may result in an exception that terminates the application program.

Note that basic certificate chain validation (signatures, dates, ...) is not affected, the denial of service can occur only when the application also specifies an expected DNS name, Email address or IP address.

TLS servers rarely solicit client certificates, and even when they do, they generally don't perform a name check against a reference identifier (expected identity), but rather extract the presented identity after checking the certificate chain. So TLS servers are generally not affected and the severity of the issue is Moderate.

The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.

Remediation

Upgrade Alpine:3.17 openssl to version 3.0.15-r0 or higher.

References

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

high severity

CVE-2023-5363

  • Vulnerable module: openssl/libcrypto3
  • Introduced through: openssl/libcrypto3@3.0.8-r3 and openssl/libssl3@3.0.8-r3
  • Fixed in: 3.0.12-r0

Detailed paths

  • Introduced through: node@14-alpine › openssl/libcrypto3@3.0.8-r3
  • Introduced through: node@14-alpine › openssl/libssl3@3.0.8-r3

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.17 relevant fixed versions and status.

Issue summary: A bug has been identified in the processing of key and initialisation vector (IV) lengths. This can lead to potential truncation or overruns during the initialisation of some symmetric ciphers.

Impact summary: A truncation in the IV can result in non-uniqueness, which could result in loss of confidentiality for some cipher modes.

When calling EVP_EncryptInit_ex2(), EVP_DecryptInit_ex2() or EVP_CipherInit_ex2() the provided OSSL_PARAM array is processed after the key and IV have been established. Any alterations to the key length, via the "keylen" parameter or the IV length, via the "ivlen" parameter, within the OSSL_PARAM array will not take effect as intended, potentially causing truncation or overreading of these values. The following ciphers and cipher modes are impacted: RC2, RC4, RC5, CCM, GCM and OCB.

For the CCM, GCM and OCB cipher modes, truncation of the IV can result in loss of confidentiality. For example, when following NIST's SP 800-38D section 8.2.1 guidance for constructing a deterministic IV for AES in GCM mode, truncation of the counter portion could lead to IV reuse.

Both truncations and overruns of the key and overruns of the IV will produce incorrect results and could, in some cases, trigger a memory exception. However, these issues are not currently assessed as security critical.

Changing the key and/or IV lengths is not considered to be a common operation and the vulnerable API was recently introduced. Furthermore it is likely that application developers will have spotted this problem during testing since decryption would fail unless both peers in the communication were similarly vulnerable. For these reasons we expect the probability of an application being vulnerable to this to be quite low. However if an application is vulnerable then this issue is considered very serious. For these reasons we have assessed this issue as Moderate severity overall.

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 because the issue lies outside of the FIPS provider boundary.

OpenSSL 3.1 and 3.0 are vulnerable to this issue.

Remediation

Upgrade Alpine:3.17 openssl to version 3.0.12-r0 or higher.

References

CVE-2023-5363 vulnerability report

high severity

Server-Side Request Forgery (SSRF)

  • Vulnerable module: node
  • Introduced through: node@14.21.3

Detailed paths

  • Introduced through: docker-image|node@14-alpine › node@14.21.3

Overview

node is a JavaScript runtime built on Chrome's V8 JavaScript engine.

Affected versions of this package are vulnerable to Server-Side Request Forgery (SSRF) due to the handling of the hostname_ascii variable in the uv_getaddrinfo function. Attackers can exploit the creation of addresses that bypass developer checks and resolve to unintended IP addresses, to access internal APIs or for websites that allow users to have username.example.com pages, potentially exposing internal services to attacks.

Notes:

  1. Depending on the build and runtime environment, it can lead to different exploitation scenarios:

The last byte of the hostname is a random value (0-256) but identical in successive calls, and the subsequent byte is a null byte. This situation can be exploited through brute force, especially in production environments where many Node.js instances run in parallel (pm2, kubernetes, etc).

Since the last byte is random, there are cases where it's one of 0-9a-f, which makes 16 possible cases (out of 256) useful for calling localhost (127.0.0.x) and potentially bypassing security measures on internal APIs. The same is true for calling other IP-ranges.

  1. When deployed in an environment with multiple pods (e.g., Kubernetes), is vulnerable to the attack described above, potentially allowing unauthorized access to internal APIs.

Remediation

Upgrade node to version 18.19.1, 20.11.1, 21.6.2 or higher.

References

Server-Side Request Forgery (SSRF) vulnerability report

high severity

Improper Control of Generation of Code ('Code Injection')

  • Vulnerable module: node
  • Introduced through: node@14.21.3

Detailed paths

  • Introduced through: docker-image|node@14-alpine › node@14.21.3

Overview

node is a JavaScript runtime built on Chrome's V8 JavaScript engine.

Affected versions of this package are vulnerable to Improper Control of Generation of Code ('Code Injection') due to the improper handling of batch files in child_process.spawn or child_process.spawnSync. An attacker can inject arbitrary commands and achieve code execution even if the shell option is not enabled.

Note: This vulnerability only affects Windows machines.

Remediation

Upgrade node to version 18.20.2, 20.12.2, 21.7.3 or higher.

References

Improper Control of Generation of Code ('Code Injection') vulnerability report

medium severity

Access Restriction Bypass

  • Vulnerable module: node
  • Introduced through: node@14.21.3

Detailed paths

  • Introduced through: docker-image|node@14-alpine › node@14.21.3

Overview

node is a JavaScript runtime built on Chrome's V8 JavaScript engine.

Affected versions of this package are vulnerable to Access Restriction Bypass by embedding non-network imports in data URLs. Exploiting this vulnerability allows an attacker to execute arbitrary code, compromising system security.

Remediation

Upgrade node to version 18.20.4, 20.15.1, 22.4.1 or higher.

References

Access Restriction Bypass vulnerability report

medium severity

Improper Control of Generation of Code ('Code Injection')

  • Vulnerable module: node
  • Introduced through: node@14.21.3

Detailed paths

  • Introduced through: docker-image|node@14-alpine › node@14.21.3

Overview

node is a JavaScript runtime built on Chrome's V8 JavaScript engine.

Affected versions of this package are vulnerable to Improper Control of Generation of Code ('Code Injection'). This is due to a bypass of CVE-2024-27980.

A malicious command line argument can inject arbitrary commands and achieve code execution even if the shell option is not enabled.

Note: This vulnerability affects only users of child_process.spawn and child_process.spawnSync on Windows in all active release lines.

Remediation

Upgrade node to version 18.20.4, 20.15.1, 22.4.1 or higher.

References

Improper Control of Generation of Code ('Code Injection') vulnerability report

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: openssl/libcrypto3
  • Introduced through: openssl/libcrypto3@3.0.8-r3 and openssl/libssl3@3.0.8-r3
  • Fixed in: 3.0.9-r0

Detailed paths

  • Introduced through: node@14-alpine › openssl/libcrypto3@3.0.8-r3
  • Introduced through: node@14-alpine › openssl/libssl3@3.0.8-r3

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.17 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.17 openssl to version 3.0.9-r0 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: openssl/libcrypto3
  • Introduced through: openssl/libcrypto3@3.0.8-r3 and openssl/libssl3@3.0.8-r3
  • Fixed in: 3.0.12-r2

Detailed paths

  • Introduced through: node@14-alpine › openssl/libcrypto3@3.0.8-r3
  • Introduced through: node@14-alpine › openssl/libssl3@3.0.8-r3

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.17 relevant fixed versions and status.

Issue summary: The POLY1305 MAC (message authentication code) implementation contains a bug that might corrupt the internal state of applications running on PowerPC CPU based platforms if the CPU provides vector instructions.

Impact summary: If an attacker can influence whether the POLY1305 MAC algorithm is used, the application state might be corrupted with various application dependent consequences.

The POLY1305 MAC (message authentication code) implementation in OpenSSL for PowerPC CPUs restores the contents of vector registers in a different order than they are saved. Thus the contents of some of these vector registers are corrupted when returning to the caller. The vulnerable code is used only on newer PowerPC processors supporting the PowerISA 2.07 instructions.

The consequences of this kind of internal application state corruption can be various - from no consequences, if the calling application does not depend on the contents of non-volatile XMM registers at all, to the worst consequences, where the attacker could get complete control of the application process. However unless the compiler uses the vector registers for storing pointers, the most likely consequence, if any, would be an incorrect result of some application dependent calculations or a crash leading to a denial of service.

The POLY1305 MAC algorithm is most frequently used as part of the CHACHA20-POLY1305 AEAD (authenticated encryption with associated data) algorithm. The most common usage of this AEAD cipher is with TLS protocol versions 1.2 and 1.3. If this cipher is enabled on the server a malicious client can influence whether this AEAD cipher is used. This implies that TLS server applications using OpenSSL can be potentially impacted. However we are currently not aware of any concrete application that would be affected by this issue therefore we consider this a Low severity security issue.

Remediation

Upgrade Alpine:3.17 openssl to version 3.0.12-r2 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Observable Timing Discrepancy

  • Vulnerable module: node
  • Introduced through: node@14.21.3

Detailed paths

  • Introduced through: docker-image|node@14-alpine › node@14.21.3

Overview

node is a JavaScript runtime built on Chrome's V8 JavaScript engine.

Affected versions of this package are vulnerable to Observable Timing Discrepancy due to the implementation of PKCS#1 v1.5 padding. An attacker can infer the private key used in the cryptographic operation by observing the time taken to execute cryptographic operations (Marvin).

Remediation

Upgrade node to version 18.19.1, 20.11.1, 21.6.2 or higher.

References

Observable Timing Discrepancy vulnerability report

medium severity

Out-of-bounds Read

  • Vulnerable module: openssl/libcrypto3
  • Introduced through: openssl/libcrypto3@3.0.8-r3 and openssl/libssl3@3.0.8-r3
  • Fixed in: 3.0.8-r4

Detailed paths

  • Introduced through: node@14-alpine › openssl/libcrypto3@3.0.8-r3
  • Introduced through: node@14-alpine › openssl/libssl3@3.0.8-r3

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.17 relevant fixed versions and status.

Issue summary: The AES-XTS cipher decryption implementation for 64 bit ARM platform contains a bug that could cause it to read past the input buffer, leading to a crash.

Impact summary: Applications that use the AES-XTS algorithm on the 64 bit ARM platform can crash in rare circumstances. The AES-XTS algorithm is usually used for disk encryption.

The AES-XTS cipher decryption implementation for 64 bit ARM platform will read past the end of the ciphertext buffer if the ciphertext size is 4 mod 5 in 16 byte blocks, e.g. 144 bytes or 1024 bytes. If the memory after the ciphertext buffer is unmapped, this will trigger a crash which results in a denial of service.

If an attacker can control the size and location of the ciphertext buffer being decrypted by an application using AES-XTS on 64 bit ARM, the application is affected. This is fairly unlikely making this issue a Low severity one.

Remediation

Upgrade Alpine:3.17 openssl to version 3.0.8-r4 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: busybox/busybox
  • Introduced through: busybox/busybox@1.35.0-r29, busybox/busybox-binsh@1.35.0-r29 and others
  • Fixed in: 1.35.0-r30

Detailed paths

  • Introduced through: node@14-alpine › busybox/busybox@1.35.0-r29
  • Introduced through: node@14-alpine › busybox/busybox-binsh@1.35.0-r29
  • Introduced through: node@14-alpine › busybox/ssl_client@1.35.0-r29

NVD Description

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

A heap-buffer-overflow was discovered in BusyBox v.1.36.1 in the next_token function at awk.c:1159.

Remediation

Upgrade Alpine:3.17 busybox to version 1.35.0-r30 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Use After Free

  • Vulnerable module: busybox/busybox
  • Introduced through: busybox/busybox@1.35.0-r29, busybox/busybox-binsh@1.35.0-r29 and others
  • Fixed in: 1.35.0-r31

Detailed paths

  • Introduced through: node@14-alpine › busybox/busybox@1.35.0-r29
  • Introduced through: node@14-alpine › busybox/busybox-binsh@1.35.0-r29
  • Introduced through: node@14-alpine › busybox/ssl_client@1.35.0-r29

NVD Description

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

A use-after-free vulnerability was discovered in BusyBox v.1.36.1 via a crafted awk pattern in the awk.c copyvar function.

Remediation

Upgrade Alpine:3.17 busybox to version 1.35.0-r31 or higher.

References

Use After Free vulnerability report

medium severity

Use After Free

  • Vulnerable module: busybox/busybox
  • Introduced through: busybox/busybox@1.35.0-r29, busybox/busybox-binsh@1.35.0-r29 and others
  • Fixed in: 1.35.0-r31

Detailed paths

  • Introduced through: node@14-alpine › busybox/busybox@1.35.0-r29
  • Introduced through: node@14-alpine › busybox/busybox-binsh@1.35.0-r29
  • Introduced through: node@14-alpine › busybox/ssl_client@1.35.0-r29

NVD Description

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

A use-after-free vulnerability in BusyBox v.1.36.1 allows attackers to cause a denial of service via a crafted awk pattern in the awk.c evaluate function.

Remediation

Upgrade Alpine:3.17 busybox to version 1.35.0-r31 or higher.

References

Use After Free vulnerability report

medium severity

Use After Free

  • Vulnerable module: busybox/busybox
  • Introduced through: busybox/busybox@1.35.0-r29, busybox/busybox-binsh@1.35.0-r29 and others
  • Fixed in: 1.35.0-r31

Detailed paths

  • Introduced through: node@14-alpine › busybox/busybox@1.35.0-r29
  • Introduced through: node@14-alpine › busybox/busybox-binsh@1.35.0-r29
  • Introduced through: node@14-alpine › busybox/ssl_client@1.35.0-r29

NVD Description

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

A use-after-free vulnerability was discovered in xasprintf function in xfuncs_printf.c:344 in BusyBox v.1.36.1.

Remediation

Upgrade Alpine:3.17 busybox to version 1.35.0-r31 or higher.

References

Use After Free vulnerability report

medium severity

CVE-2024-0727

  • Vulnerable module: openssl/libcrypto3
  • Introduced through: openssl/libcrypto3@3.0.8-r3 and openssl/libssl3@3.0.8-r3
  • Fixed in: 3.0.12-r4

Detailed paths

  • Introduced through: node@14-alpine › openssl/libcrypto3@3.0.8-r3
  • Introduced through: node@14-alpine › openssl/libssl3@3.0.8-r3

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.17 relevant fixed versions and status.

Issue summary: Processing a maliciously formatted PKCS12 file may lead OpenSSL to crash leading to a potential Denial of Service attack

Impact summary: Applications loading files in the PKCS12 format from untrusted sources might terminate abruptly.

A file in PKCS12 format can contain certificates and keys and may come from an untrusted source. The PKCS12 specification allows certain fields to be NULL, but OpenSSL does not correctly check for this case. This can lead to a NULL pointer dereference that results in OpenSSL crashing. If an application processes PKCS12 files from an untrusted source using the OpenSSL APIs then that application will be vulnerable to this issue.

OpenSSL APIs that are vulnerable to this are: PKCS12_parse(), PKCS12_unpack_p7data(), PKCS12_unpack_p7encdata(), PKCS12_unpack_authsafes() and PKCS12_newpass().

We have also fixed a similar issue in SMIME_write_PKCS7(). However since this function is related to writing data we do not consider it security significant.

The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue.

Remediation

Upgrade Alpine:3.17 openssl to version 3.0.12-r4 or higher.

References

CVE-2024-0727 vulnerability report

medium severity

HTTP Request Smuggling

  • Vulnerable module: node
  • Introduced through: node@14.21.3

Detailed paths

  • Introduced through: docker-image|node@14-alpine › node@14.21.3

Overview

node is a JavaScript runtime built on Chrome's V8 JavaScript engine.

Affected versions of this package are vulnerable to HTTP Request Smuggling via content length ofuscation. An attacker can smuggle an HTTP request by including a space before a Content-Length header.

Remediation

Upgrade node to version 18.20.1, 20.12.1, 21.7.2 or higher.

References

HTTP Request Smuggling vulnerability report

medium severity

Inconsistency Between Implementation and Documented Design

  • Vulnerable module: node
  • Introduced through: node@14.21.3

Detailed paths

  • Introduced through: docker-image|node@14-alpine › node@14.21.3

Overview

node is a JavaScript runtime built on Chrome's V8 JavaScript engine.

Affected versions of this package are vulnerable to Inconsistency Between Implementation and Documented Design where the generateKeys() API function returned from crypto.createDiffieHellman() do not generate keys after setting a private key.

Remediation

Upgrade node to version 16.20.1, 18.16.1, 20.3.1 or higher.

References

Inconsistency Between Implementation and Documented Design vulnerability report

medium severity

Excessive Iteration

  • Vulnerable module: openssl/libcrypto3
  • Introduced through: openssl/libcrypto3@3.0.8-r3 and openssl/libssl3@3.0.8-r3
  • Fixed in: 3.0.10-r0

Detailed paths

  • Introduced through: node@14-alpine › openssl/libcrypto3@3.0.8-r3
  • Introduced through: node@14-alpine › openssl/libssl3@3.0.8-r3

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.17 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.17 openssl to version 3.0.10-r0 or higher.

References

Excessive Iteration vulnerability report

medium severity

Improper Authentication

  • Vulnerable module: openssl/libcrypto3
  • Introduced through: openssl/libcrypto3@3.0.8-r3 and openssl/libssl3@3.0.8-r3
  • Fixed in: 3.0.9-r2

Detailed paths

  • Introduced through: node@14-alpine › openssl/libcrypto3@3.0.8-r3
  • Introduced through: node@14-alpine › openssl/libssl3@3.0.8-r3

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.17 relevant fixed versions and status.

Issue summary: The AES-SIV cipher implementation contains a bug that causes it to ignore empty associated data entries which are unauthenticated as a consequence.

Impact summary: Applications that use the AES-SIV algorithm and want to authenticate empty data entries as associated data can be misled by removing, adding or reordering such empty entries as these are ignored by the OpenSSL implementation. We are currently unaware of any such applications.

The AES-SIV algorithm allows for authentication of multiple associated data entries along with the encryption. To authenticate empty data the application has to call EVP_EncryptUpdate() (or EVP_CipherUpdate()) with NULL pointer as the output buffer and 0 as the input buffer length. The AES-SIV implementation in OpenSSL just returns success for such a call instead of performing the associated data authentication operation. The empty data thus will not be authenticated.

As this issue does not affect non-empty associated data authentication and we expect it to be rare for an application to use empty associated data entries this is qualified as Low severity issue.

Remediation

Upgrade Alpine:3.17 openssl to version 3.0.9-r2 or higher.

References

Improper Authentication vulnerability report

medium severity

Improper Check for Unusual or Exceptional Conditions

  • Vulnerable module: openssl/libcrypto3
  • Introduced through: openssl/libcrypto3@3.0.8-r3 and openssl/libssl3@3.0.8-r3
  • Fixed in: 3.0.12-r1

Detailed paths

  • Introduced through: node@14-alpine › openssl/libcrypto3@3.0.8-r3
  • Introduced through: node@14-alpine › openssl/libssl3@3.0.8-r3

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.17 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.17 openssl to version 3.0.12-r1 or higher.

References

Improper Check for Unusual or Exceptional Conditions vulnerability report

medium severity

Inefficient Regular Expression Complexity

  • Vulnerable module: openssl/libcrypto3
  • Introduced through: openssl/libcrypto3@3.0.8-r3 and openssl/libssl3@3.0.8-r3
  • Fixed in: 3.0.9-r3

Detailed paths

  • Introduced through: node@14-alpine › openssl/libcrypto3@3.0.8-r3
  • Introduced through: node@14-alpine › openssl/libssl3@3.0.8-r3

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.17 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.17 openssl to version 3.0.9-r3 or higher.

References

Inefficient Regular Expression Complexity vulnerability report

low severity

Permissive Cross-domain Policy with Untrusted Domains

  • Vulnerable module: node
  • Introduced through: node@14.21.3

Detailed paths

  • Introduced through: docker-image|node@14-alpine › node@14.21.3

Overview

node is a JavaScript runtime built on Chrome's V8 JavaScript engine.

Affected versions of this package are vulnerable to Permissive Cross-domain Policy with Untrusted Domains due to not clearing Proxy-Authentication headers on cross-origin redirects. An attacker can intercept the improperly cleared headers.

Remediation

Upgrade node to version 18.19.1, 20.11.1, 21.6.2 or higher.

References

Permissive Cross-domain Policy with Untrusted Domains vulnerability report

low severity

Authorization Bypass

  • Vulnerable module: node
  • Introduced through: node@14.21.3

Detailed paths

  • Introduced through: docker-image|node@14-alpine › node@14.21.3

Overview

node is a JavaScript runtime built on Chrome's V8 JavaScript engine.

Affected versions of this package are vulnerable to Authorization Bypass via fs.fchown or fs.fchmod operations which can use a "read-only" file descriptor to change the owner and permissions of a file.

Note: This is only exploitable for users using the experimental permission when the --allow-fs-write flag is used

Remediation

Upgrade node to version 20.15.1, 22.4.1 or higher.

References

Authorization Bypass vulnerability report

low severity

Authorization Bypass

  • Vulnerable module: node
  • Introduced through: node@14.21.3

Detailed paths

  • Introduced through: docker-image|node@14-alpine › node@14.21.3

Overview

node is a JavaScript runtime built on Chrome's V8 JavaScript engine.

Affected versions of this package are vulnerable to Authorization Bypass due to a failure to restrict file stats through the fs.lstat API that allows attackers to retrieve stats from files to which they do not have explicit read access.

Note: This is exploitable only for users of the experimental permission model when the --allow-fs-read flag is used.

Remediation

Upgrade node to version 20.15.1, 22.4.1 or higher.

References

Authorization Bypass vulnerability report

low severity

Improper Handling of Values

  • Vulnerable module: node
  • Introduced through: node@14.21.3

Detailed paths

  • Introduced through: docker-image|node@14-alpine › node@14.21.3

Overview

node is a JavaScript runtime built on Chrome's V8 JavaScript engine.

Affected versions of this package are vulnerable to Improper Handling of Values. This is because the Permission Model assumes wrongly that any path starting with two backslashes \ has a four-character prefix that can be ignored.

Note: This vulnerability affects only Windows users of the Node.js Permission Model

Remediation

Upgrade node to version 20.15.1, 22.4.1 or higher.

References

Improper Handling of Values vulnerability report

low severity

CVE-2025-26519

  • Vulnerable module: musl/musl
  • Introduced through: musl/musl@1.2.3-r4 and musl/musl-utils@1.2.3-r4
  • Fixed in: 1.2.3-r6

Detailed paths

  • Introduced through: node@14-alpine › musl/musl@1.2.3-r4
  • Introduced through: node@14-alpine › musl/musl-utils@1.2.3-r4

NVD Description

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

musl libc 0.9.13 through 1.2.5 before 1.2.6 has an out-of-bounds write vulnerability when an attacker can trigger iconv conversion of untrusted EUC-KR text to UTF-8.

Remediation

Upgrade Alpine:3.17 musl to version 1.2.3-r6 or higher.

References

CVE-2025-26519 vulnerability report

low severity

CVE-2023-6237

  • Vulnerable module: openssl/libcrypto3
  • Introduced through: openssl/libcrypto3@3.0.8-r3 and openssl/libssl3@3.0.8-r3
  • Fixed in: 3.0.12-r3

Detailed paths

  • Introduced through: node@14-alpine › openssl/libcrypto3@3.0.8-r3
  • Introduced through: node@14-alpine › openssl/libssl3@3.0.8-r3

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.17 relevant fixed versions and status.

Issue summary: Checking excessively long invalid RSA public keys may take a long time.

Impact summary: Applications that use the function EVP_PKEY_public_check() to check RSA public keys may experience long delays. Where the key that is being checked has been obtained from an untrusted source this may lead to a Denial of Service.

When function EVP_PKEY_public_check() is called on RSA public keys, a computation is done to confirm that the RSA modulus, n, is composite. For valid RSA keys, n is a product of two or more large primes and this computation completes quickly. However, if n is an overly large prime, then this computation would take a long time.

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

The function EVP_PKEY_public_check() is not called from other OpenSSL functions however it is called from the OpenSSL pkey command line application. For that reason that application is also vulnerable if used with the '-pubin' and '-check' options on untrusted data.

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

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

Remediation

Upgrade Alpine:3.17 openssl to version 3.0.12-r3 or higher.

References

CVE-2023-6237 vulnerability report

low severity

CVE-2024-2511

  • Vulnerable module: openssl/libcrypto3
  • Introduced through: openssl/libcrypto3@3.0.8-r3 and openssl/libssl3@3.0.8-r3
  • Fixed in: 3.0.12-r5

Detailed paths

  • Introduced through: node@14-alpine › openssl/libcrypto3@3.0.8-r3
  • Introduced through: node@14-alpine › openssl/libssl3@3.0.8-r3

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.17 relevant fixed versions and status.

Issue summary: Some non-default TLS server configurations can cause unbounded memory growth when processing TLSv1.3 sessions

Impact summary: An attacker may exploit certain server configurations to trigger unbounded memory growth that would lead to a Denial of Service

This problem can occur in TLSv1.3 if the non-default SSL_OP_NO_TICKET option is being used (but not if early_data support is also configured and the default anti-replay protection is in use). In this case, under certain conditions, the session cache can get into an incorrect state and it will fail to flush properly as it fills. The session cache will continue to grow in an unbounded manner. A malicious client could deliberately create the scenario for this failure to force a Denial of Service. It may also happen by accident in normal operation.

This issue only affects TLS servers supporting TLSv1.3. It does not affect TLS clients.

The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue. OpenSSL 1.0.2 is also not affected by this issue.

Remediation

Upgrade Alpine:3.17 openssl to version 3.0.12-r5 or higher.

References

CVE-2024-2511 vulnerability report

low severity

CVE-2024-4603

  • Vulnerable module: openssl/libcrypto3
  • Introduced through: openssl/libcrypto3@3.0.8-r3 and openssl/libssl3@3.0.8-r3
  • Fixed in: 3.0.13-r0

Detailed paths

  • Introduced through: node@14-alpine › openssl/libcrypto3@3.0.8-r3
  • Introduced through: node@14-alpine › openssl/libssl3@3.0.8-r3

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.17 relevant fixed versions and status.

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

Impact summary: Applications that use the functions EVP_PKEY_param_check() or EVP_PKEY_public_check() to check a DSA public key or DSA 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 functions EVP_PKEY_param_check() or EVP_PKEY_public_check() perform various checks on DSA parameters. Some of those computations take a long time if the modulus (p parameter) is too large.

Trying to use a very large modulus is slow and OpenSSL will not allow using public keys with a modulus which is over 10,000 bits in length for signature verification. However the key and parameter check functions do not limit the modulus size when performing the checks.

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

These functions are not called by OpenSSL itself on untrusted DSA keys so only applications that directly call these functions may be vulnerable.

Also vulnerable are the OpenSSL pkey 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 affected by this issue.

Remediation

Upgrade Alpine:3.17 openssl to version 3.0.13-r0 or higher.

References

CVE-2024-4603 vulnerability report

low severity

CVE-2024-4741

  • Vulnerable module: openssl/libcrypto3
  • Introduced through: openssl/libcrypto3@3.0.8-r3 and openssl/libssl3@3.0.8-r3
  • Fixed in: 3.0.14-r0

Detailed paths

  • Introduced through: node@14-alpine › openssl/libcrypto3@3.0.8-r3
  • Introduced through: node@14-alpine › openssl/libssl3@3.0.8-r3

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.17 relevant fixed versions and status.

Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause memory to be accessed that was previously freed in some situations

Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, only applications that directly call the SSL_free_buffers function are affected by this issue. Applications that do not call this function are not vulnerable. Our investigations indicate that this function is rarely used by applications.

The SSL_free_buffers function is used to free the internal OpenSSL buffer used when processing an incoming record from the network. The call is only expected to succeed if the buffer is not currently in use. However, two scenarios have been identified where the buffer is freed even when still in use.

The first scenario occurs where a record header has been received from the network and processed by OpenSSL, but the full record body has not yet arrived. In this case calling SSL_free_buffers will succeed even though a record has only been partially processed and the buffer is still in use.

The second scenario occurs where a full record containing application data has been received and processed by OpenSSL but the application has only read part of this data. Again a call to SSL_free_buffers will succeed even though the buffer is still in use.

While these scenarios could occur accidentally during normal operation a malicious attacker could attempt to engineer a stituation where this occurs. We are not aware of this issue being actively exploited.

The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.

Remediation

Upgrade Alpine:3.17 openssl to version 3.0.14-r0 or higher.

References

CVE-2024-4741 vulnerability report

low severity

CVE-2024-5535

  • Vulnerable module: openssl/libcrypto3
  • Introduced through: openssl/libcrypto3@3.0.8-r3 and openssl/libssl3@3.0.8-r3
  • Fixed in: 3.0.14-r0

Detailed paths

  • Introduced through: node@14-alpine › openssl/libcrypto3@3.0.8-r3
  • Introduced through: node@14-alpine › openssl/libssl3@3.0.8-r3

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.17 relevant fixed versions and status.

Issue summary: Calling the OpenSSL API function SSL_select_next_proto with an empty supported client protocols buffer may cause a crash or memory contents to be sent to the peer.

Impact summary: A buffer overread can have a range of potential consequences such as unexpected application beahviour or a crash. In particular this issue could result in up to 255 bytes of arbitrary private data from memory being sent to the peer leading to a loss of confidentiality. However, only applications that directly call the SSL_select_next_proto function with a 0 length list of supported client protocols are affected by this issue. This would normally never be a valid scenario and is typically not under attacker control but may occur by accident in the case of a configuration or programming error in the calling application.

The OpenSSL API function SSL_select_next_proto is typically used by TLS applications that support ALPN (Application Layer Protocol Negotiation) or NPN (Next Protocol Negotiation). NPN is older, was never standardised and is deprecated in favour of ALPN. We believe that ALPN is significantly more widely deployed than NPN. The SSL_select_next_proto function accepts a list of protocols from the server and a list of protocols from the client and returns the first protocol that appears in the server list that also appears in the client list. In the case of no overlap between the two lists it returns the first item in the client list. In either case it will signal whether an overlap between the two lists was found. In the case where SSL_select_next_proto is called with a zero length client list it fails to notice this condition and returns the memory immediately following the client list pointer (and reports that there was no overlap in the lists).

This function is typically called from a server side application callback for ALPN or a client side application callback for NPN. In the case of ALPN the list of protocols supplied by the client is guaranteed by libssl to never be zero in length. The list of server protocols comes from the application and should never normally be expected to be of zero length. In this case if the SSL_select_next_proto function has been called as expected (with the list supplied by the client passed in the client/client_len parameters), then the application will not be vulnerable to this issue. If the application has accidentally been configured with a zero length server list, and has accidentally passed that zero length server list in the client/client_len parameters, and has additionally failed to correctly handle a "no overlap" response (which would normally result in a handshake failure in ALPN) then it will be vulnerable to this problem.

In the case of NPN, the protocol permits the client to opportunistically select a protocol when there is no overlap. OpenSSL returns the first client protocol in the no overlap case in support of this. The list of client protocols comes from the application and should never normally be expected to be of zero length. However if the SSL_select_next_proto function is accidentally called with a client_len of 0 then an invalid memory pointer will be returned instead. If the application uses this output as the opportunistic protocol then the loss of confidentiality will occur.

This issue has been assessed as Low severity because applications are most likely to be vulnerable if they are using NPN instead of ALPN - but NPN is not widely used. It also requires an application configuration or programming error. Finally, this issue would not typically be under attacker control making active exploitation unlikely.

The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.

Due to the low severity of this issue we are not issuing new releases of OpenSSL at this time. The fix will be included in the next releases when they become available.

Remediation

Upgrade Alpine:3.17 openssl to version 3.0.14-r0 or higher.

References

CVE-2024-5535 vulnerability report

low severity

CVE-2024-9143

  • Vulnerable module: openssl/libcrypto3
  • Introduced through: openssl/libcrypto3@3.0.8-r3 and openssl/libssl3@3.0.8-r3
  • Fixed in: 3.0.15-r1

Detailed paths

  • Introduced through: node@14-alpine › openssl/libcrypto3@3.0.8-r3
  • Introduced through: node@14-alpine › openssl/libssl3@3.0.8-r3

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.17 relevant fixed versions and status.

Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted explicit values for the field polynomial can lead to out-of-bounds memory reads or writes.

Impact summary: Out of bound memory writes can lead to an application crash or even a possibility of a remote code execution, however, in all the protocols involving Elliptic Curve Cryptography that we're aware of, either only "named curves" are supported, or, if explicit curve parameters are supported, they specify an X9.62 encoding of binary (GF(2^m)) curves that can't represent problematic input values. Thus the likelihood of existence of a vulnerable application is low.

In particular, the X9.62 encoding is used for ECC keys in X.509 certificates, so problematic inputs cannot occur in the context of processing X.509 certificates. Any problematic use-cases would have to be using an "exotic" curve encoding.

The affected APIs include: EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(), and various supporting BN_GF2m_*() functions.

Applications working with "exotic" explicit binary (GF(2^m)) curve parameters, that make it possible to represent invalid field polynomials with a zero constant term, via the above or similar APIs, may terminate abruptly as a result of reading or writing outside of array bounds. Remote code execution cannot easily be ruled out.

The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.

Remediation

Upgrade Alpine:3.17 openssl to version 3.0.15-r1 or higher.

References

CVE-2024-9143 vulnerability report