Vulnerabilities

 5 via 8 paths

Dependencies

 14

Source

 Group 6 Copy Created with Sketch. Docker

Target OS

 alpine:3.10.6
Test your Docker Hub image against our market leading vulnerability database Sign up for free
Severity
  • 1
  • 3
  • 1
Status
  • 5
  • 0
  • 0

critical severity

Out-of-bounds Read

  • Vulnerable module: apk-tools/apk-tools
  • Introduced through: apk-tools/apk-tools@2.10.4-r2
  • Fixed in: 2.10.7-r0

Detailed paths

  • Introduced through: alpine@3.10.6 › apk-tools/apk-tools@2.10.4-r2

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.10 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.10 apk-tools to version 2.10.7-r0 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Out-of-bounds Read

  • Vulnerable module: apk-tools/apk-tools
  • Introduced through: apk-tools/apk-tools@2.10.4-r2
  • Fixed in: 2.10.6-r0

Detailed paths

  • Introduced through: alpine@3.10.6 › apk-tools/apk-tools@2.10.4-r2

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.10 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.10 apk-tools to version 2.10.6-r0 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Improper Handling of Exceptional Conditions

  • Vulnerable module: busybox/busybox
  • Introduced through: busybox/busybox@1.30.1-r4 and busybox/ssl_client@1.30.1-r4
  • Fixed in: 1.30.1-r5

Detailed paths

  • Introduced through: alpine@3.10.6 › busybox/busybox@1.30.1-r4
  • Introduced through: alpine@3.10.6 › busybox/ssl_client@1.30.1-r4

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.10 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.10 busybox to version 1.30.1-r5 or higher.

References

Improper Handling of Exceptional Conditions vulnerability report

high severity

Improper Certificate Validation

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

Detailed paths

  • Introduced through: alpine@3.10.6 › openssl/libcrypto1.1@1.1.1j-r0
  • Introduced through: alpine@3.10.6 › openssl/libssl1.1@1.1.1j-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.10 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.10 openssl to version 1.1.1k-r0 or higher.

References

Improper Certificate Validation vulnerability report

medium severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: alpine@3.10.6 › openssl/libcrypto1.1@1.1.1j-r0
  • Introduced through: alpine@3.10.6 › openssl/libssl1.1@1.1.1j-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.10 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.10 openssl to version 1.1.1k-r0 or higher.

References

NULL Pointer Dereference vulnerability report