Vulnerabilities

 35 via 49 paths

Dependencies

 29

Source

 Group 6 Copy Created with Sketch. Docker

Target OS

 alpine:3.9.0
Test your Docker Hub image against our market leading vulnerability database Sign up for free
Severity
  • 5
  • 10
  • 18
  • 2
Status
  • 35
  • 0
  • 0

critical severity

Out-of-bounds Write

  • Vulnerable module: bzip2/libbz2
  • Introduced through: bzip2/libbz2@1.0.6-r6
  • Fixed in: 1.0.6-r7

Detailed paths

  • Introduced through: nginx@1.15.8-alpine › bzip2/libbz2@1.0.6-r6

NVD Description

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

BZ2_decompress in decompress.c in bzip2 through 1.0.6 has an out-of-bounds write when there are many selectors.

Remediation

Upgrade Alpine:3.9 bzip2 to version 1.0.6-r7 or higher.

References

Out-of-bounds Write vulnerability report

critical severity

Double Free

  • Vulnerable module: gd/libgd
  • Introduced through: gd/libgd@2.2.5-r1
  • Fixed in: 2.2.5-r2

Detailed paths

  • Introduced through: nginx@1.15.8-alpine › gd/libgd@2.2.5-r1

NVD Description

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

The GD Graphics Library (aka LibGD) 2.2.5 has a double free in the gdImage*Ptr() functions in gd_gif_out.c, gd_jpeg.c, and gd_wbmp.c. NOTE: PHP is unaffected.

Remediation

Upgrade Alpine:3.9 gd to version 2.2.5-r2 or higher.

References

Double Free vulnerability report

critical severity

CVE-2019-11068

  • Vulnerable module: libxslt/libxslt
  • Introduced through: libxslt/libxslt@1.1.32-r0
  • Fixed in: 1.1.33-r1

Detailed paths

  • Introduced through: nginx@1.15.8-alpine › libxslt/libxslt@1.1.32-r0

NVD Description

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

libxslt through 1.1.33 allows bypass of a protection mechanism because callers of xsltCheckRead and xsltCheckWrite permit access even upon receiving a -1 error code. xsltCheckRead can return -1 for a crafted URL that is not actually invalid and is subsequently loaded.

Remediation

Upgrade Alpine:3.9 libxslt to version 1.1.33-r1 or higher.

References

CVE-2019-11068 vulnerability report

critical severity

Out-of-bounds Write

  • Vulnerable module: musl/musl
  • Introduced through: musl/musl@1.1.20-r3 and musl/musl-utils@1.1.20-r3
  • Fixed in: 1.1.20-r5

Detailed paths

  • Introduced through: nginx@1.15.8-alpine › musl/musl@1.1.20-r3
  • Introduced through: nginx@1.15.8-alpine › musl/musl-utils@1.1.20-r3

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

musl libc through 1.1.23 has an x87 floating-point stack adjustment imbalance, related to the math/i386/ directory. In some cases, use of this library could introduce out-of-bounds writes that are not present in an application's source code.

Remediation

Upgrade Alpine:3.9 musl to version 1.1.20-r5 or higher.

References

Out-of-bounds Write vulnerability report

critical severity

Out-of-bounds Write

  • Vulnerable module: freetype/freetype
  • Introduced through: freetype/freetype@2.9.1-r2
  • Fixed in: 2.9.1-r3

Detailed paths

  • Introduced through: nginx@1.15.8-alpine › freetype/freetype@2.9.1-r2

NVD Description

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

Heap buffer overflow in Freetype in Google Chrome prior to 86.0.4240.111 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Remediation

Upgrade Alpine:3.9 freetype to version 2.9.1-r3 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: gd/libgd
  • Introduced through: gd/libgd@2.2.5-r1
  • Fixed in: 2.2.5-r2

Detailed paths

  • Introduced through: nginx@1.15.8-alpine › gd/libgd@2.2.5-r1

NVD Description

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

gdImageColorMatch in gd_color_match.c in the GD Graphics Library (aka LibGD) 2.2.5, as used in the imagecolormatch function in PHP before 5.6.40, 7.x before 7.1.26, 7.2.x before 7.2.14, and 7.3.x before 7.3.1, has a heap-based buffer overflow. This can be exploited by an attacker who is able to trigger imagecolormatch calls with crafted image data.

Remediation

Upgrade Alpine:3.9 gd to version 2.2.5-r2 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: libpng/libpng
  • Introduced through: libpng/libpng@1.6.35-r0
  • Fixed in: 1.6.37-r0

Detailed paths

  • Introduced through: nginx@1.15.8-alpine › libpng/libpng@1.6.35-r0

NVD Description

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

An issue has been found in third-party PNM decoding associated with libpng 1.6.35. It is a stack-based buffer overflow in the function get_token in pnm2png.c in pnm2png.

Remediation

Upgrade Alpine:3.9 libpng to version 1.6.37-r0 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: libjpeg-turbo/libjpeg-turbo
  • Introduced through: libjpeg-turbo/libjpeg-turbo@1.5.3-r4
  • Fixed in: 1.5.3-r6

Detailed paths

  • Introduced through: nginx@1.15.8-alpine › libjpeg-turbo/libjpeg-turbo@1.5.3-r4

NVD Description

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

In generate_jsimd_ycc_rgb_convert_neon of jsimd_arm64_neon.S, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execution in an unprivileged process with no additional execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-8.0 Android-8.1 Android-9 Android-10Android ID: A-120551338

Remediation

Upgrade Alpine:3.9 libjpeg-turbo to version 1.5.3-r6 or higher.

References

Out-of-bounds Write vulnerability report

high severity

NULL Pointer Dereference

  • Vulnerable module: gd/libgd
  • Introduced through: gd/libgd@2.2.5-r1
  • Fixed in: 2.2.5-r3

Detailed paths

  • Introduced through: nginx@1.15.8-alpine › gd/libgd@2.2.5-r1

NVD Description

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

gdImageClone in gd.c in libgd 2.1.0-rc2 through 2.2.5 has a NULL pointer dereference allowing attackers to crash an application via a specific function call sequence. Only affects PHP when linked with an external libgd (not bundled).

Remediation

Upgrade Alpine:3.9 gd to version 2.2.5-r3 or higher.

References

NULL Pointer Dereference vulnerability report

high severity

Missing Release of Resource after Effective Lifetime

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

Detailed paths

  • Introduced through: nginx@1.15.8-alpine › libxml2/libxml2@2.9.9-r0

NVD Description

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

xmlParseBalancedChunkMemoryRecover in parser.c in libxml2 before 2.9.10 has a memory leak related to newDoc->oldNs.

Remediation

Upgrade Alpine:3.9 libxml2 to version 2.9.9-r2 or higher.

References

Missing Release of Resource after Effective Lifetime vulnerability report

high severity

Use After Free

  • Vulnerable module: libxslt/libxslt
  • Introduced through: libxslt/libxslt@1.1.32-r0
  • Fixed in: 1.1.33-r2

Detailed paths

  • Introduced through: nginx@1.15.8-alpine › libxslt/libxslt@1.1.32-r0

NVD Description

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

In xsltCopyText in transform.c in libxslt 1.1.33, a pointer variable isn't reset under certain circumstances. If the relevant memory area happened to be freed and reused in a certain way, a bounds check could fail and memory outside a buffer could be written to, or uninitialized data could be disclosed.

Remediation

Upgrade Alpine:3.9 libxslt to version 1.1.33-r2 or higher.

References

Use After Free vulnerability report

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: nginx@1.15.8-alpine › openssl/libcrypto1.1@1.1.1a-r1
  • Introduced through: nginx@1.15.8-alpine › openssl/libssl1.1@1.1.1a-r1

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.9 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.9 openssl to version 1.1.1j-r0 or higher.

References

Integer Overflow or Wraparound vulnerability report

high severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: nginx@1.15.8-alpine › openssl/libcrypto1.1@1.1.1a-r1
  • Introduced through: nginx@1.15.8-alpine › openssl/libssl1.1@1.1.1a-r1

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

Server or client applications that call the SSL_check_chain() function during or after a TLS 1.3 handshake may crash due to a NULL pointer dereference as a result of incorrect handling of the "signature_algorithms_cert" TLS extension. The crash occurs if an invalid or unrecognised signature algorithm is received from the peer. This could be exploited by a malicious peer in a Denial of Service attack. OpenSSL version 1.1.1d, 1.1.1e, and 1.1.1f are affected by this issue. This issue did not affect OpenSSL versions prior to 1.1.1d. Fixed in OpenSSL 1.1.1g (Affected 1.1.1d-1.1.1f).

Remediation

Upgrade Alpine:3.9 openssl to version 1.1.1g-r0 or higher.

References

NULL Pointer Dereference vulnerability report

high severity

Improper Certificate Validation

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

Detailed paths

  • Introduced through: nginx@1.15.8-alpine › openssl/libcrypto1.1@1.1.1a-r1
  • Introduced through: nginx@1.15.8-alpine › openssl/libssl1.1@1.1.1a-r1

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.9 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.9 openssl to version 1.1.1k-r0 or higher.

References

Improper Certificate Validation vulnerability report

high severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: openssl/libcrypto1.1
  • Introduced through: openssl/libcrypto1.1@1.1.1a-r1 and openssl/libssl1.1@1.1.1a-r1
  • Fixed in: 1.1.1b-r1

Detailed paths

  • Introduced through: nginx@1.15.8-alpine › openssl/libcrypto1.1@1.1.1a-r1
  • Introduced through: nginx@1.15.8-alpine › openssl/libssl1.1@1.1.1a-r1

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

ChaCha20-Poly1305 is an AEAD cipher, and requires a unique nonce input for every encryption operation. RFC 7539 specifies that the nonce value (IV) should be 96 bits (12 bytes). OpenSSL allows a variable nonce length and front pads the nonce with 0 bytes if it is less than 12 bytes. However it also incorrectly allows a nonce to be set of up to 16 bytes. In this case only the last 12 bytes are significant and any additional leading bytes are ignored. It is a requirement of using this cipher that nonce values are unique. Messages encrypted using a reused nonce value are susceptible to serious confidentiality and integrity attacks. If an application changes the default nonce length to be longer than 12 bytes and then makes a change to the leading bytes of the nonce expecting the new value to be a new unique nonce then such an application could inadvertently encrypt messages with a reused nonce. Additionally the ignored bytes in a long nonce are not covered by the integrity guarantee of this cipher. Any application that relies on the integrity of these ignored leading bytes of a long nonce may be further affected. Any OpenSSL internal use of this cipher, including in SSL/TLS, is safe because no such use sets such a long nonce value. However user applications that use this cipher directly and set a non-default nonce length to be longer than 12 bytes may be vulnerable. OpenSSL versions 1.1.1 and 1.1.0 are affected by this issue. Due to the limited scope of affected deployments this has been assessed as low severity and therefore we are not creating new releases at this time. Fixed in OpenSSL 1.1.1c (Affected 1.1.1-1.1.1b). Fixed in OpenSSL 1.1.0k (Affected 1.1.0-1.1.0j).

Remediation

Upgrade Alpine:3.9 openssl to version 1.1.1b-r1 or higher.

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

medium severity

Out-of-bounds Read

  • Vulnerable module: libjpeg-turbo/libjpeg-turbo
  • Introduced through: libjpeg-turbo/libjpeg-turbo@1.5.3-r4
  • Fixed in: 1.5.3-r5

Detailed paths

  • Introduced through: nginx@1.15.8-alpine › libjpeg-turbo/libjpeg-turbo@1.5.3-r4

NVD Description

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

get_8bit_row in rdbmp.c in libjpeg-turbo through 1.5.90 and MozJPEG through 3.3.1 allows attackers to cause a denial of service (heap-based buffer over-read and application crash) via a crafted 8-bit BMP in which one or more of the color indices is out of range for the number of palette entries.

Remediation

Upgrade Alpine:3.9 libjpeg-turbo to version 1.5.3-r5 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

CVE-2018-14048

  • Vulnerable module: libpng/libpng
  • Introduced through: libpng/libpng@1.6.35-r0
  • Fixed in: 1.6.37-r0

Detailed paths

  • Introduced through: nginx@1.15.8-alpine › libpng/libpng@1.6.35-r0

NVD Description

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

An issue has been found in libpng 1.6.34. It is a SEGV in the function png_free_data in png.c, related to the recommended error handling for png_read_image.

Remediation

Upgrade Alpine:3.9 libpng to version 1.6.37-r0 or higher.

References

CVE-2018-14048 vulnerability report

medium severity

Out-of-bounds Read

  • Vulnerable module: libxml2/libxml2
  • Introduced through: libxml2/libxml2@2.9.9-r0
  • Fixed in: 2.9.9-r3

Detailed paths

  • Introduced through: nginx@1.15.8-alpine › libxml2/libxml2@2.9.9-r0

NVD Description

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

GNOME project libxml2 v2.9.10 has a global buffer over-read vulnerability in xmlEncodeEntitiesInternal at libxml2/entities.c. The issue has been fixed in commit 50f06b3e.

Remediation

Upgrade Alpine:3.9 libxml2 to version 2.9.9-r3 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Race Condition

  • Vulnerable module: libgcrypt/libgcrypt
  • Introduced through: libgcrypt/libgcrypt@1.8.4-r0
  • Fixed in: 1.8.5-r0

Detailed paths

  • Introduced through: nginx@1.15.8-alpine › libgcrypt/libgcrypt@1.8.4-r0

NVD Description

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

It was discovered that there was a ECDSA timing attack in the libgcrypt20 cryptographic library. Version affected: 1.8.4-5, 1.7.6-2+deb9u3, and 1.6.3-2+deb8u4. Versions fixed: 1.8.5-2 and 1.6.3-2+deb8u7.

Remediation

Upgrade Alpine:3.9 libgcrypt to version 1.8.5-r0 or higher.

References

Race Condition vulnerability report

medium severity

Cryptographic Issues

  • Vulnerable module: libgcrypt/libgcrypt
  • Introduced through: libgcrypt/libgcrypt@1.8.4-r0
  • Fixed in: 1.8.4-r1

Detailed paths

  • Introduced through: nginx@1.15.8-alpine › libgcrypt/libgcrypt@1.8.4-r0

NVD Description

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

In Libgcrypt 1.8.4, the C implementation of AES is vulnerable to a flush-and-reload side-channel attack because physical addresses are available to other processes. (The C implementation is used on platforms where an assembly-language implementation is unavailable.) NOTE: the vendor's position is that the issue report cannot be validated because there is no description of an attack

Remediation

Upgrade Alpine:3.9 libgcrypt to version 1.8.4-r1 or higher.

References

Cryptographic Issues vulnerability report

medium severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: nginx@1.15.8-alpine › openssl/libcrypto1.1@1.1.1a-r1
  • Introduced through: nginx@1.15.8-alpine › openssl/libssl1.1@1.1.1a-r1

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.9 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.9 openssl to version 1.1.1j-r0 or higher.

References

Integer Overflow or Wraparound vulnerability report

medium severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: nginx@1.15.8-alpine › openssl/libcrypto1.1@1.1.1a-r1
  • Introduced through: nginx@1.15.8-alpine › openssl/libssl1.1@1.1.1a-r1

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.9 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.9 openssl to version 1.1.1k-r0 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: nginx@1.15.8-alpine › openssl/libcrypto1.1@1.1.1a-r1
  • Introduced through: nginx@1.15.8-alpine › openssl/libssl1.1@1.1.1a-r1

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.9 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.9 openssl to version 1.1.1i-r0 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

Incorrect Conversion between Numeric Types

  • Vulnerable module: gd/libgd
  • Introduced through: gd/libgd@2.2.5-r1
  • Fixed in: 2.2.5-r2

Detailed paths

  • Introduced through: nginx@1.15.8-alpine › gd/libgd@2.2.5-r1

NVD Description

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

gd_gif_in.c in the GD Graphics Library (aka libgd), as used in PHP before 5.6.33, 7.0.x before 7.0.27, 7.1.x before 7.1.13, and 7.2.x before 7.2.1, has an integer signedness error that leads to an infinite loop via a crafted GIF file, as demonstrated by a call to the imagecreatefromgif or imagecreatefromstring PHP function. This is related to GetCode_ and gdImageCreateFromGifCtx.

Remediation

Upgrade Alpine:3.9 gd to version 2.2.5-r2 or higher.

References

Incorrect Conversion between Numeric Types vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: musl/musl
  • Introduced through: musl/musl@1.1.20-r3 and musl/musl-utils@1.1.20-r3
  • Fixed in: 1.1.20-r6

Detailed paths

  • Introduced through: nginx@1.15.8-alpine › musl/musl@1.1.20-r3
  • Introduced through: nginx@1.15.8-alpine › musl/musl-utils@1.1.20-r3

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.9 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.9 musl to version 1.1.20-r6 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Use of Uninitialized Resource

  • Vulnerable module: gd/libgd
  • Introduced through: gd/libgd@2.2.5-r1
  • Fixed in: 2.2.5-r3

Detailed paths

  • Introduced through: nginx@1.15.8-alpine › gd/libgd@2.2.5-r1

NVD Description

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

When using the gdImageCreateFromXbm() function in the GD Graphics Library (aka LibGD) 2.2.5, as used in the PHP GD extension in PHP versions 7.1.x below 7.1.30, 7.2.x below 7.2.19 and 7.3.x below 7.3.6, it is possible to supply data that will cause the function to use the value of uninitialized variable. This may lead to disclosing contents of the stack that has been left there by previous code.

Remediation

Upgrade Alpine:3.9 gd to version 2.2.5-r3 or higher.

References

Use of Uninitialized Resource vulnerability report

medium severity

Use After Free

  • Vulnerable module: libpng/libpng
  • Introduced through: libpng/libpng@1.6.35-r0
  • Fixed in: 1.6.37-r0

Detailed paths

  • Introduced through: nginx@1.15.8-alpine › libpng/libpng@1.6.35-r0

NVD Description

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

png_image_free in png.c in libpng 1.6.x before 1.6.37 has a use-after-free because png_image_free_function is called under png_safe_execute.

Remediation

Upgrade Alpine:3.9 libpng to version 1.6.37-r0 or higher.

References

Use After Free vulnerability report

medium severity

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

  • Vulnerable module: libxslt/libxslt
  • Introduced through: libxslt/libxslt@1.1.32-r0
  • Fixed in: 1.1.33-r3

Detailed paths

  • Introduced through: nginx@1.15.8-alpine › libxslt/libxslt@1.1.32-r0

NVD Description

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

In numbers.c in libxslt 1.1.33, a type holding grouping characters of an xsl:number instruction was too narrow and an invalid character/length combination could be passed to xsltNumberFormatDecimal, leading to a read of uninitialized stack data.

Remediation

Upgrade Alpine:3.9 libxslt to version 1.1.33-r3 or higher.

References

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

medium severity

Use of Uninitialized Resource

  • Vulnerable module: libxslt/libxslt
  • Introduced through: libxslt/libxslt@1.1.32-r0
  • Fixed in: 1.1.33-r3

Detailed paths

  • Introduced through: nginx@1.15.8-alpine › libxslt/libxslt@1.1.32-r0

NVD Description

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

In numbers.c in libxslt 1.1.33, an xsl:number with certain format strings could lead to a uninitialized read in xsltNumberFormatInsertNumbers. This could allow an attacker to discern whether a byte on the stack contains the characters A, a, I, i, or 0, or any other character.

Remediation

Upgrade Alpine:3.9 libxslt to version 1.1.33-r3 or higher.

References

Use of Uninitialized Resource vulnerability report

medium severity

Information Exposure

  • Vulnerable module: openssl/libcrypto1.1
  • Introduced through: openssl/libcrypto1.1@1.1.1a-r1 and openssl/libssl1.1@1.1.1a-r1
  • Fixed in: 1.1.1d-r2

Detailed paths

  • Introduced through: nginx@1.15.8-alpine › openssl/libcrypto1.1@1.1.1a-r1
  • Introduced through: nginx@1.15.8-alpine › openssl/libssl1.1@1.1.1a-r1

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

There is an overflow bug in the x64_64 Montgomery squaring procedure used in exponentiation with 512-bit moduli. No EC algorithms are affected. Analysis suggests that attacks against 2-prime RSA1024, 3-prime RSA1536, and DSA1024 as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH512 are considered just feasible. However, for an attack the target would have to re-use the DH512 private key, which is not recommended anyway. Also applications directly using the low level API BN_mod_exp may be affected if they use BN_FLG_CONSTTIME. Fixed in OpenSSL 1.1.1e (Affected 1.1.1-1.1.1d). Fixed in OpenSSL 1.0.2u (Affected 1.0.2-1.0.2t).

Remediation

Upgrade Alpine:3.9 openssl to version 1.1.1d-r2 or higher.

References

Information Exposure vulnerability report

medium severity

Use of Insufficiently Random Values

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

Detailed paths

  • Introduced through: nginx@1.15.8-alpine › openssl/libcrypto1.1@1.1.1a-r1
  • Introduced through: nginx@1.15.8-alpine › openssl/libssl1.1@1.1.1a-r1

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

OpenSSL 1.1.1 introduced a rewritten random number generator (RNG). This was intended to include protection in the event of a fork() system call in order to ensure that the parent and child processes did not share the same RNG state. However this protection was not being used in the default case. A partial mitigation for this issue is that the output from a high precision timer is mixed into the RNG state so the likelihood of a parent and child process sharing state is significantly reduced. If an application already calls OPENSSL_init_crypto() explicitly using OPENSSL_INIT_ATFORK then this problem does not occur at all. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c).

Remediation

Upgrade Alpine:3.9 openssl to version 1.1.1d-r0 or higher.

References

Use of Insufficiently Random Values vulnerability report

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: pcre/pcre
  • Introduced through: pcre/pcre@8.42-r1
  • Fixed in: 8.42-r2

Detailed paths

  • Introduced through: nginx@1.15.8-alpine › pcre/pcre@8.42-r1

NVD Description

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

libpcre in PCRE before 8.44 allows an integer overflow via a large number after a (?C substring.

Remediation

Upgrade Alpine:3.9 pcre to version 8.42-r2 or higher.

References

Integer Overflow or Wraparound vulnerability report

medium severity

CVE-2019-1547

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

Detailed paths

  • Introduced through: nginx@1.15.8-alpine › openssl/libcrypto1.1@1.1.1a-r1
  • Introduced through: nginx@1.15.8-alpine › openssl/libssl1.1@1.1.1a-r1

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

Normally in OpenSSL EC groups always have a co-factor present and this is used in side channel resistant code paths. However, in some cases, it is possible to construct a group using explicit parameters (instead of using a named curve). In those cases it is possible that such a group does not have the cofactor present. This can occur even where all the parameters match a known named curve. If such a curve is used then OpenSSL falls back to non-side channel resistant code paths which may result in full key recovery during an ECDSA signature operation. In order to be vulnerable an attacker would have to have the ability to time the creation of a large number of signatures where explicit parameters with no co-factor present are in use by an application using libcrypto. For the avoidance of doubt libssl is not vulnerable because explicit parameters are never used. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s).

Remediation

Upgrade Alpine:3.9 openssl to version 1.1.1d-r0 or higher.

References

CVE-2019-1547 vulnerability report

low severity

Inadequate Encryption Strength

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

Detailed paths

  • Introduced through: nginx@1.15.8-alpine › openssl/libcrypto1.1@1.1.1a-r1
  • Introduced through: nginx@1.15.8-alpine › openssl/libssl1.1@1.1.1a-r1

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.9 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.9 openssl to version 1.1.1j-r0 or higher.

References

Inadequate Encryption Strength vulnerability report

low severity

Use of a Broken or Risky Cryptographic Algorithm

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

Detailed paths

  • Introduced through: nginx@1.15.8-alpine › openssl/libcrypto1.1@1.1.1a-r1
  • Introduced through: nginx@1.15.8-alpine › openssl/libssl1.1@1.1.1a-r1

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

In situations where an attacker receives automated notification of the success or failure of a decryption attempt an attacker, after sending a very large number of messages to be decrypted, can recover a CMS/PKCS7 transported encryption key or decrypt any RSA encrypted message that was encrypted with the public RSA key, using a Bleichenbacher padding oracle attack. Applications are not affected if they use a certificate together with the private RSA key to the CMS_decrypt or PKCS7_decrypt functions to select the correct recipient info to decrypt. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s).

Remediation

Upgrade Alpine:3.9 openssl to version 1.1.1d-r0 or higher.

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report