Vulnerabilities

27 via 50 paths

Dependencies

16

Source

Group 6 Copy Created with Sketch. Docker

Target OS

alpine:3.12.0
Test your Docker Hub image against our market leading vulnerability database Sign up for free
Severity
  • 3
  • 17
  • 5
  • 2
Status
  • 27
  • 0
  • 0

critical severity

Buffer Overflow

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

Detailed paths

  • Introduced through: caddy@2.2.0-alpine openssl/libcrypto1.1@1.1.1g-r0
  • Introduced through: caddy@2.2.0-alpine openssl/libssl1.1@1.1.1g-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.12 relevant fixed versions and status.

In order to decrypt SM2 encrypted data an application is expected to call the API function EVP_PKEY_decrypt(). Typically an application will call this function twice. The first time, on entry, the "out" parameter can be NULL and, on exit, the "outlen" parameter is populated with the buffer size required to hold the decrypted plaintext. The application can then allocate a sufficiently sized buffer and call EVP_PKEY_decrypt() again, but this time passing a non-NULL value for the "out" parameter. A bug in the implementation of the SM2 decryption code means that the calculation of the buffer size required to hold the plaintext returned by the first call to EVP_PKEY_decrypt() can be smaller than the actual size required by the second call. This can lead to a buffer overflow when EVP_PKEY_decrypt() is called by the application a second time with a buffer that is too small. A malicious attacker who is able present SM2 content for decryption to an application could cause attacker chosen data to overflow the buffer by up to a maximum of 62 bytes altering the contents of other data held after the buffer, possibly changing application behaviour or causing the application to crash. The location of the buffer is application dependent but is typically heap allocated. Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k).

Remediation

Upgrade Alpine:3.12 openssl to version 1.1.1l-r0 or higher.

References

critical severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: caddy@2.2.0-alpine zlib/zlib@1.2.11-r3

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.12 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.12 zlib to version 1.2.12-r2 or higher.

References

critical severity

Out-of-bounds Read

  • Vulnerable module: apk-tools/apk-tools
  • Introduced through: apk-tools/apk-tools@2.10.5-r1
  • Fixed in: 2.10.7-r0

Detailed paths

  • Introduced through: caddy@2.2.0-alpine apk-tools/apk-tools@2.10.5-r1

NVD Description

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

libfetch before 2021-07-26, as used in apk-tools, xbps, and other products, mishandles numeric strings for the FTP and HTTP protocols. The FTP passive mode implementation allows an out-of-bounds read because strtol is used to parse the relevant numbers into address bytes. It does not check if the line ends prematurely. If it does, the for-loop condition checks for the '\0' terminator one byte too late.

Remediation

Upgrade Alpine:3.12 apk-tools to version 2.10.7-r0 or higher.

References

high severity

CVE-2022-28391

  • Vulnerable module: busybox/busybox
  • Introduced through: busybox/busybox@1.31.1-r16 and busybox/ssl_client@1.31.1-r16
  • Fixed in: 1.31.1-r22

Detailed paths

  • Introduced through: caddy@2.2.0-alpine busybox/busybox@1.31.1-r16
  • Introduced through: caddy@2.2.0-alpine busybox/ssl_client@1.31.1-r16

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

BusyBox through 1.35.0 allows remote attackers to execute arbitrary code if netstat is used to print a DNS PTR record's value to a VT compatible terminal. Alternatively, the attacker could choose to change the terminal's colors.

Remediation

Upgrade Alpine:3.12 busybox to version 1.31.1-r22 or higher.

References

high severity

Out-of-bounds Read

  • Vulnerable module: apk-tools/apk-tools
  • Introduced through: apk-tools/apk-tools@2.10.5-r1
  • Fixed in: 2.10.6-r0

Detailed paths

  • Introduced through: caddy@2.2.0-alpine apk-tools/apk-tools@2.10.5-r1

NVD Description

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

In Alpine Linux apk-tools before 2.12.5, the tarball parser allows a buffer overflow and crash.

Remediation

Upgrade Alpine:3.12 apk-tools to version 2.10.6-r0 or higher.

References

high severity

Improper Handling of Exceptional Conditions

  • Vulnerable module: busybox/busybox
  • Introduced through: busybox/busybox@1.31.1-r16 and busybox/ssl_client@1.31.1-r16
  • Fixed in: 1.31.1-r20

Detailed paths

  • Introduced through: caddy@2.2.0-alpine busybox/busybox@1.31.1-r16
  • Introduced through: caddy@2.2.0-alpine busybox/ssl_client@1.31.1-r16

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

decompress_gunzip.c in BusyBox through 1.32.1 mishandles the error bit on the huft_build result pointer, with a resultant invalid free or segmentation fault, via malformed gzip data.

Remediation

Upgrade Alpine:3.12 busybox to version 1.31.1-r20 or higher.

References

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: caddy@2.2.0-alpine openssl/libcrypto1.1@1.1.1g-r0
  • Introduced through: caddy@2.2.0-alpine openssl/libssl1.1@1.1.1g-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.12 relevant fixed versions and status.

Calls to EVP_CipherUpdate, EVP_EncryptUpdate and EVP_DecryptUpdate may overflow the output length argument in some cases where the input length is close to the maximum permissable length for an integer on the platform. In such cases the return value from the function call will be 1 (indicating success), but the output length value will be negative. This could cause applications to behave incorrectly or crash. OpenSSL versions 1.1.1i and below are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1j. OpenSSL versions 1.0.2x and below are affected by this issue. However OpenSSL 1.0.2 is out of support and no longer receiving public updates. Premium support customers of OpenSSL 1.0.2 should upgrade to 1.0.2y. Other users should upgrade to 1.1.1j. Fixed in OpenSSL 1.1.1j (Affected 1.1.1-1.1.1i). Fixed in OpenSSL 1.0.2y (Affected 1.0.2-1.0.2x).

Remediation

Upgrade Alpine:3.12 openssl to version 1.1.1j-r0 or higher.

References

high severity

Loop with Unreachable Exit Condition ('Infinite Loop')

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

Detailed paths

  • Introduced through: caddy@2.2.0-alpine openssl/libcrypto1.1@1.1.1g-r0
  • Introduced through: caddy@2.2.0-alpine openssl/libssl1.1@1.1.1g-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.12 relevant fixed versions and status.

The BN_mod_sqrt() function, which computes a modular square root, contains a bug that can cause it to loop forever for non-prime moduli. Internally this function is used when parsing certificates that contain elliptic curve public keys in compressed form or explicit elliptic curve parameters with a base point encoded in compressed form. It is possible to trigger the infinite loop by crafting a certificate that has invalid explicit curve parameters. Since certificate parsing happens prior to verification of the certificate signature, any process that parses an externally supplied certificate may thus be subject to a denial of service attack. The infinite loop can also be reached when parsing crafted private keys as they can contain explicit elliptic curve parameters. Thus vulnerable situations include: - TLS clients consuming server certificates - TLS servers consuming client certificates - Hosting providers taking certificates or private keys from customers - Certificate authorities parsing certification requests from subscribers - Anything else which parses ASN.1 elliptic curve parameters Also any other applications that use the BN_mod_sqrt() where the attacker can control the parameter values are vulnerable to this DoS issue. In the OpenSSL 1.0.2 version the public key is not parsed during initial parsing of the certificate which makes it slightly harder to trigger the infinite loop. However any operation which requires the public key from the certificate will trigger the infinite loop. In particular the attacker can use a self-signed certificate to trigger the loop during verification of the certificate signature. This issue affects OpenSSL versions 1.0.2, 1.1.1 and 3.0. It was addressed in the releases of 1.1.1n and 3.0.2 on the 15th March 2022. Fixed in OpenSSL 3.0.2 (Affected 3.0.0,3.0.1). Fixed in OpenSSL 1.1.1n (Affected 1.1.1-1.1.1m). Fixed in OpenSSL 1.0.2zd (Affected 1.0.2-1.0.2zc).

Remediation

Upgrade Alpine:3.12 openssl to version 1.1.1n-r0 or higher.

References

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: caddy@2.2.0-alpine zlib/zlib@1.2.11-r3

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

zlib before 1.2.12 allows memory corruption when deflating (i.e., when compressing) if the input has many distant matches.

Remediation

Upgrade Alpine:3.12 zlib to version 1.2.12-r0 or higher.

References

high severity

Improper Certificate Validation

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

Detailed paths

  • Introduced through: caddy@2.2.0-alpine openssl/libcrypto1.1@1.1.1g-r0
  • Introduced through: caddy@2.2.0-alpine openssl/libssl1.1@1.1.1g-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.12 relevant fixed versions and status.

The X509_V_FLAG_X509_STRICT flag enables additional security checks of the certificates present in a certificate chain. It is not set by default. Starting from OpenSSL version 1.1.1h a check to disallow certificates in the chain that have explicitly encoded elliptic curve parameters was added as an additional strict check. An error in the implementation of this check meant that the result of a previous check to confirm that certificates in the chain are valid CA certificates was overwritten. This effectively bypasses the check that non-CA certificates must not be able to issue other certificates. If a "purpose" has been configured then there is a subsequent opportunity for checks that the certificate is a valid CA. All of the named "purpose" values implemented in libcrypto perform this check. Therefore, where a purpose is set the certificate chain will still be rejected even when the strict flag has been used. A purpose is set by default in libssl client and server certificate verification routines, but it can be overridden or removed by an application. In order to be affected, an application must explicitly set the X509_V_FLAG_X509_STRICT verification flag and either not set a purpose for the certificate verification or, in the case of TLS client or server applications, override the default purpose. OpenSSL versions 1.1.1h and newer are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1h-1.1.1j).

Remediation

Upgrade Alpine:3.12 openssl to version 1.1.1k-r0 or higher.

References

high severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: caddy@2.2.0-alpine openssl/libcrypto1.1@1.1.1g-r0
  • Introduced through: caddy@2.2.0-alpine openssl/libssl1.1@1.1.1g-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.12 relevant fixed versions and status.

ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not a strict requirement, ASN.1 strings that are parsed using OpenSSL's own "d2i" functions (and other similar parsing functions) as well as any string whose value has been set with the ASN1_STRING_set() function will additionally NUL terminate the byte array in the ASN1_STRING structure. However, it is possible for applications to directly construct valid ASN1_STRING structures which do not NUL terminate the byte array by directly setting the "data" and "length" fields in the ASN1_STRING array. This can also happen by using the ASN1_STRING_set0() function. Numerous OpenSSL functions that print ASN.1 data have been found to assume that the ASN1_STRING byte array will be NUL terminated, even though this is not guaranteed for strings that have been directly constructed. Where an application requests an ASN.1 structure to be printed, and where that ASN.1 structure contains ASN1_STRINGs that have been directly constructed by the application without NUL terminating the "data" field, then a read buffer overrun can occur. The same thing can also occur during name constraints processing of certificates (for example if a certificate has been directly constructed by the application instead of loading it via the OpenSSL parsing functions, and the certificate contains non NUL terminated ASN1_STRING structures). It can also occur in the X509_get1_email(), X509_REQ_get1_email() and X509_get1_ocsp() functions. If a malicious actor can cause an application to directly construct an ASN1_STRING and then process it through one of the affected OpenSSL functions then this issue could be hit. This might result in a crash (causing a Denial of Service attack). It could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext). Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k). Fixed in OpenSSL 1.0.2za (Affected 1.0.2-1.0.2y).

Remediation

Upgrade Alpine:3.12 openssl to version 1.1.1l-r0 or higher.

References

high severity

Use After Free

  • Vulnerable module: busybox/busybox
  • Introduced through: busybox/busybox@1.31.1-r16 and busybox/ssl_client@1.31.1-r16
  • Fixed in: 1.31.1-r21

Detailed paths

  • Introduced through: caddy@2.2.0-alpine busybox/busybox@1.31.1-r16
  • Introduced through: caddy@2.2.0-alpine busybox/ssl_client@1.31.1-r16

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

A use-after-free in Busybox's awk applet leads to denial of service and possibly code execution when processing a crafted awk pattern in the hash_init function

Remediation

Upgrade Alpine:3.12 busybox to version 1.31.1-r21 or higher.

References

high severity

Use After Free

  • Vulnerable module: busybox/busybox
  • Introduced through: busybox/busybox@1.31.1-r16 and busybox/ssl_client@1.31.1-r16
  • Fixed in: 1.31.1-r21

Detailed paths

  • Introduced through: caddy@2.2.0-alpine busybox/busybox@1.31.1-r16
  • Introduced through: caddy@2.2.0-alpine busybox/ssl_client@1.31.1-r16

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

A use-after-free in Busybox's awk applet leads to denial of service and possibly code execution when processing a crafted awk pattern in the next_input_file function

Remediation

Upgrade Alpine:3.12 busybox to version 1.31.1-r21 or higher.

References

high severity

Use After Free

  • Vulnerable module: busybox/busybox
  • Introduced through: busybox/busybox@1.31.1-r16 and busybox/ssl_client@1.31.1-r16
  • Fixed in: 1.31.1-r21

Detailed paths

  • Introduced through: caddy@2.2.0-alpine busybox/busybox@1.31.1-r16
  • Introduced through: caddy@2.2.0-alpine busybox/ssl_client@1.31.1-r16

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

A use-after-free in Busybox's awk applet leads to denial of service and possibly code execution when processing a crafted awk pattern in the clrvar function

Remediation

Upgrade Alpine:3.12 busybox to version 1.31.1-r21 or higher.

References

high severity

Use After Free

  • Vulnerable module: busybox/busybox
  • Introduced through: busybox/busybox@1.31.1-r16 and busybox/ssl_client@1.31.1-r16
  • Fixed in: 1.31.1-r21

Detailed paths

  • Introduced through: caddy@2.2.0-alpine busybox/busybox@1.31.1-r16
  • Introduced through: caddy@2.2.0-alpine busybox/ssl_client@1.31.1-r16

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

A use-after-free in Busybox's awk applet leads to denial of service and possibly code execution when processing a crafted awk pattern in the handle_special function

Remediation

Upgrade Alpine:3.12 busybox to version 1.31.1-r21 or higher.

References

high severity

Use After Free

  • Vulnerable module: busybox/busybox
  • Introduced through: busybox/busybox@1.31.1-r16 and busybox/ssl_client@1.31.1-r16
  • Fixed in: 1.31.1-r21

Detailed paths

  • Introduced through: caddy@2.2.0-alpine busybox/busybox@1.31.1-r16
  • Introduced through: caddy@2.2.0-alpine busybox/ssl_client@1.31.1-r16

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

A use-after-free in Busybox's awk applet leads to denial of service and possibly code execution when processing a crafted awk pattern in the evaluate function

Remediation

Upgrade Alpine:3.12 busybox to version 1.31.1-r21 or higher.

References

high severity

Use After Free

  • Vulnerable module: busybox/busybox
  • Introduced through: busybox/busybox@1.31.1-r16 and busybox/ssl_client@1.31.1-r16
  • Fixed in: 1.31.1-r21

Detailed paths

  • Introduced through: caddy@2.2.0-alpine busybox/busybox@1.31.1-r16
  • Introduced through: caddy@2.2.0-alpine busybox/ssl_client@1.31.1-r16

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

A use-after-free in Busybox's awk applet leads to denial of service and possibly code execution when processing a crafted awk pattern in the getvar_i function

Remediation

Upgrade Alpine:3.12 busybox to version 1.31.1-r21 or higher.

References

high severity

Use After Free

  • Vulnerable module: busybox/busybox
  • Introduced through: busybox/busybox@1.31.1-r16 and busybox/ssl_client@1.31.1-r16
  • Fixed in: 1.31.1-r21

Detailed paths

  • Introduced through: caddy@2.2.0-alpine busybox/busybox@1.31.1-r16
  • Introduced through: caddy@2.2.0-alpine busybox/ssl_client@1.31.1-r16

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

A use-after-free in Busybox's awk applet leads to denial of service and possibly code execution when processing a crafted awk pattern in the nvalloc function

Remediation

Upgrade Alpine:3.12 busybox to version 1.31.1-r21 or higher.

References

high severity

Use After Free

  • Vulnerable module: busybox/busybox
  • Introduced through: busybox/busybox@1.31.1-r16 and busybox/ssl_client@1.31.1-r16
  • Fixed in: 1.31.1-r21

Detailed paths

  • Introduced through: caddy@2.2.0-alpine busybox/busybox@1.31.1-r16
  • Introduced through: caddy@2.2.0-alpine busybox/ssl_client@1.31.1-r16

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

A use-after-free in Busybox's awk applet leads to denial of service and possibly code execution when processing a crafted awk pattern in the getvar_s function

Remediation

Upgrade Alpine:3.12 busybox to version 1.31.1-r21 or higher.

References

high severity

Use After Free

  • Vulnerable module: busybox/busybox
  • Introduced through: busybox/busybox@1.31.1-r16 and busybox/ssl_client@1.31.1-r16
  • Fixed in: 1.31.1-r21

Detailed paths

  • Introduced through: caddy@2.2.0-alpine busybox/busybox@1.31.1-r16
  • Introduced through: caddy@2.2.0-alpine busybox/ssl_client@1.31.1-r16

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

A use-after-free in Busybox's awk applet leads to denial of service and possibly code execution when processing a crafted awk pattern in the evaluate function

Remediation

Upgrade Alpine:3.12 busybox to version 1.31.1-r21 or higher.

References

medium severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: caddy@2.2.0-alpine openssl/libcrypto1.1@1.1.1g-r0
  • Introduced through: caddy@2.2.0-alpine openssl/libssl1.1@1.1.1g-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.12 relevant fixed versions and status.

The OpenSSL public API function X509_issuer_and_serial_hash() attempts to create a unique hash value based on the issuer and serial number data contained within an X509 certificate. However it fails to correctly handle any errors that may occur while parsing the issuer field (which might occur if the issuer field is maliciously constructed). This may subsequently result in a NULL pointer deref and a crash leading to a potential denial of service attack. The function X509_issuer_and_serial_hash() is never directly called by OpenSSL itself so applications are only vulnerable if they use this function directly and they use it on certificates that may have been obtained from untrusted sources. OpenSSL versions 1.1.1i and below are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1j. OpenSSL versions 1.0.2x and below are affected by this issue. However OpenSSL 1.0.2 is out of support and no longer receiving public updates. Premium support customers of OpenSSL 1.0.2 should upgrade to 1.0.2y. Other users should upgrade to 1.1.1j. Fixed in OpenSSL 1.1.1j (Affected 1.1.1-1.1.1i). Fixed in OpenSSL 1.0.2y (Affected 1.0.2-1.0.2x).

Remediation

Upgrade Alpine:3.12 openssl to version 1.1.1j-r0 or higher.

References

medium severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: caddy@2.2.0-alpine openssl/libcrypto1.1@1.1.1g-r0
  • Introduced through: caddy@2.2.0-alpine openssl/libssl1.1@1.1.1g-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.12 relevant fixed versions and status.

The X.509 GeneralName type is a generic type for representing different types of names. One of those name types is known as EDIPartyName. OpenSSL provides a function GENERAL_NAME_cmp which compares different instances of a GENERAL_NAME to see if they are equal or not. This function behaves incorrectly when both GENERAL_NAMEs contain an EDIPARTYNAME. A NULL pointer dereference and a crash may occur leading to a possible denial of service attack. OpenSSL itself uses the GENERAL_NAME_cmp function for two purposes: 1) Comparing CRL distribution point names between an available CRL and a CRL distribution point embedded in an X509 certificate 2) When verifying that a timestamp response token signer matches the timestamp authority name (exposed via the API functions TS_RESP_verify_response and TS_RESP_verify_token) If an attacker can control both items being compared then that attacker could trigger a crash. For example if the attacker can trick a client or server into checking a malicious certificate against a malicious CRL then this may occur. Note that some applications automatically download CRLs based on a URL embedded in a certificate. This checking happens prior to the signatures on the certificate and CRL being verified. OpenSSL's s_server, s_client and verify tools have support for the "-crl_download" option which implements automatic CRL downloading and this attack has been demonstrated to work against those tools. Note that an unrelated bug means that affected versions of OpenSSL cannot parse or construct correct encodings of EDIPARTYNAME. However it is possible to construct a malformed EDIPARTYNAME that OpenSSL's parser will accept and hence trigger this attack. All OpenSSL 1.1.1 and 1.0.2 versions are affected by this issue. Other OpenSSL releases are out of support and have not been checked. Fixed in OpenSSL 1.1.1i (Affected 1.1.1-1.1.1h). Fixed in OpenSSL 1.0.2x (Affected 1.0.2-1.0.2w).

Remediation

Upgrade Alpine:3.12 openssl to version 1.1.1i-r0 or higher.

References

medium severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: caddy@2.2.0-alpine openssl/libcrypto1.1@1.1.1g-r0
  • Introduced through: caddy@2.2.0-alpine openssl/libssl1.1@1.1.1g-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.12 relevant fixed versions and status.

An OpenSSL TLS server may crash if sent a maliciously crafted renegotiation ClientHello message from a client. If a TLSv1.2 renegotiation ClientHello omits the signature_algorithms extension (where it was present in the initial ClientHello), but includes a signature_algorithms_cert extension then a NULL pointer dereference will result, leading to a crash and a denial of service attack. A server is only vulnerable if it has TLSv1.2 and renegotiation enabled (which is the default configuration). OpenSSL TLS clients are not impacted by this issue. All OpenSSL 1.1.1 versions are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1-1.1.1j).

Remediation

Upgrade Alpine:3.12 openssl to version 1.1.1k-r0 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: musl/musl
  • Introduced through: musl/musl@1.1.24-r8 and musl/musl-utils@1.1.24-r8
  • Fixed in: 1.1.24-r10

Detailed paths

  • Introduced through: caddy@2.2.0-alpine musl/musl@1.1.24-r8
  • Introduced through: caddy@2.2.0-alpine musl/musl-utils@1.1.24-r8

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

In musl libc through 1.2.1, wcsnrtombs mishandles particular combinations of destination buffer size and source character limit, as demonstrated by an invalid write access (buffer overflow).

Remediation

Upgrade Alpine:3.12 musl to version 1.1.24-r10 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: busybox/busybox
  • Introduced through: busybox/busybox@1.31.1-r16 and busybox/ssl_client@1.31.1-r16
  • Fixed in: 1.31.1-r21

Detailed paths

  • Introduced through: caddy@2.2.0-alpine busybox/busybox@1.31.1-r16
  • Introduced through: caddy@2.2.0-alpine busybox/ssl_client@1.31.1-r16

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

An out-of-bounds heap read in Busybox's unlzma applet leads to information leak and denial of service when crafted LZMA-compressed input is decompressed. This can be triggered by any applet/format that

Remediation

Upgrade Alpine:3.12 busybox to version 1.31.1-r21 or higher.

References

low severity

Inadequate Encryption Strength

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

Detailed paths

  • Introduced through: caddy@2.2.0-alpine openssl/libcrypto1.1@1.1.1g-r0
  • Introduced through: caddy@2.2.0-alpine openssl/libssl1.1@1.1.1g-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.12 relevant fixed versions and status.

OpenSSL 1.0.2 supports SSLv2. If a client attempts to negotiate SSLv2 with a server that is configured to support both SSLv2 and more recent SSL and TLS versions then a check is made for a version rollback attack when unpadding an RSA signature. Clients that support SSL or TLS versions greater than SSLv2 are supposed to use a special form of padding. A server that supports greater than SSLv2 is supposed to reject connection attempts from a client where this special form of padding is present, because this indicates that a version rollback has occurred (i.e. both client and server support greater than SSLv2, and yet this is the version that is being requested). The implementation of this padding check inverted the logic so that the connection attempt is accepted if the padding is present, and rejected if it is absent. This means that such as server will accept a connection if a version rollback attack has occurred. Further the server will erroneously reject a connection if a normal SSLv2 connection attempt is made. Only OpenSSL 1.0.2 servers from version 1.0.2s to 1.0.2x are affected by this issue. In order to be vulnerable a 1.0.2 server must: 1) have configured SSLv2 support at compile time (this is off by default), 2) have configured SSLv2 support at runtime (this is off by default), 3) have configured SSLv2 ciphersuites (these are not in the default ciphersuite list) OpenSSL 1.1.1 does not have SSLv2 support and therefore is not vulnerable to this issue. The underlying error is in the implementation of the RSA_padding_check_SSLv23() function. This also affects the RSA_SSLV23_PADDING padding mode used by various other functions. Although 1.1.1 does not support SSLv2 the RSA_padding_check_SSLv23() function still exists, as does the RSA_SSLV23_PADDING padding mode. Applications that directly call that function or use that padding mode will encounter this issue. However since there is no support for the SSLv2 protocol in 1.1.1 this is considered a bug and not a security issue in that version. OpenSSL 1.0.2 is out of support and no longer receiving public updates. Premium support customers of OpenSSL 1.0.2 should upgrade to 1.0.2y. Other users should upgrade to 1.1.1j. Fixed in OpenSSL 1.0.2y (Affected 1.0.2s-1.0.2x).

Remediation

Upgrade Alpine:3.12 openssl to version 1.1.1j-r0 or higher.

References

low severity

ALPINE-13661

  • Vulnerable module: busybox/busybox
  • Introduced through: busybox/busybox@1.31.1-r16 and busybox/ssl_client@1.31.1-r16
  • Fixed in: 1.31.1-r22

Detailed paths

  • Introduced through: caddy@2.2.0-alpine busybox/busybox@1.31.1-r16
  • Introduced through: caddy@2.2.0-alpine busybox/ssl_client@1.31.1-r16

NVD Description

This vulnerability has not been analyzed by NVD yet.

Remediation

Upgrade Alpine:3.12 busybox to version 1.31.1-r22 or higher.