Vulnerabilities

134 via 270 paths

Dependencies

139

Source

Group 6 Copy Created with Sketch. Docker

Target OS

debian:11
Test your Docker Hub image against our market leading vulnerability database Sign up for free
Severity
  • 5
  • 20
  • 16
  • 93
Status
  • 134
  • 0
  • 0

critical severity

Integer Overflow or Wraparound

  • Vulnerable module: zlib/zlib1g
  • Introduced through: zlib/zlib1g@1:1.2.11.dfsg-2+deb11u1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre zlib/zlib1g@1:1.2.11.dfsg-2+deb11u1

NVD Description

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

MiniZip in zlib through 1.3 has an integer overflow and resultant heap-based buffer overflow in zipOpenNewFileInZip4_64 via a long filename, comment, or extra field. NOTE: MiniZip is not a supported part of the zlib product. NOTE: pyminizip through 0.2.6 is also vulnerable because it bundles an affected zlib version, and exposes the applicable MiniZip code through its compress API.

Remediation

There is no fixed version for Debian:11 zlib.

References

critical severity

Out-of-bounds Write

  • Vulnerable module: zlib/zlib1g
  • Introduced through: zlib/zlib1g@1:1.2.11.dfsg-2+deb11u1
  • Fixed in: 1:1.2.11.dfsg-2+deb11u2

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre zlib/zlib1g@1:1.2.11.dfsg-2+deb11u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream zlib package and not the zlib package as distributed by Debian. See How to fix? for Debian:11 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 Debian:11 zlib to version 1:1.2.11.dfsg-2+deb11u2 or higher.

References

critical severity

Off-by-one Error

  • Vulnerable module: libtasn1-6
  • Introduced through: libtasn1-6@4.16.0-2
  • Fixed in: 4.16.0-2+deb11u1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre libtasn1-6@4.16.0-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream libtasn1-6 package and not the libtasn1-6 package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

GNU Libtasn1 before 4.19.0 has an ETYPE_OK off-by-one array size check that affects asn1_encode_simple_der.

Remediation

Upgrade Debian:11 libtasn1-6 to version 4.16.0-2+deb11u1 or higher.

References

critical severity

Out-of-bounds Read

  • Vulnerable module: pcre2/libpcre2-8-0
  • Introduced through: pcre2/libpcre2-8-0@10.36-2
  • Fixed in: 10.36-2+deb11u1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre pcre2/libpcre2-8-0@10.36-2

NVD Description

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

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

Remediation

Upgrade Debian:11 pcre2 to version 10.36-2+deb11u1 or higher.

References

critical severity

Out-of-bounds Read

  • Vulnerable module: pcre2/libpcre2-8-0
  • Introduced through: pcre2/libpcre2-8-0@10.36-2
  • Fixed in: 10.36-2+deb11u1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre pcre2/libpcre2-8-0@10.36-2

NVD Description

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

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

Remediation

Upgrade Debian:11 pcre2 to version 10.36-2+deb11u1 or higher.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.18.3-6+deb11u1, krb5/libk5crypto3@1.18.3-6+deb11u1 and others
  • Fixed in: 1.18.3-6+deb11u3

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre krb5/libgssapi-krb5-2@1.18.3-6+deb11u1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre krb5/libk5crypto3@1.18.3-6+deb11u1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre krb5/libkrb5-3@1.18.3-6+deb11u1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre krb5/libkrb5support0@1.18.3-6+deb11u1

NVD Description

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

PAC parsing in MIT Kerberos 5 (aka krb5) before 1.19.4 and 1.20.x before 1.20.1 has integer overflows that may lead to remote code execution (in KDC, kadmind, or a GSS or Kerberos application server) on 32-bit platforms (which have a resultant heap-based buffer overflow), and cause a denial of service on other platforms. This occurs in krb5_pac_parse in lib/krb5/krb/pac.c. Heimdal before 7.7.1 has "a similar bug."

Remediation

Upgrade Debian:11 krb5 to version 1.18.3-6+deb11u3 or higher.

References

high severity

Use After Free

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.10-2+deb11u3
  • Fixed in: 2.2.10-2+deb11u4

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre expat/libexpat1@2.2.10-2+deb11u3

NVD Description

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

libexpat before 2.4.9 has a use-after-free in the doContent function in xmlparse.c.

Remediation

Upgrade Debian:11 expat to version 2.2.10-2+deb11u4 or higher.

References

high severity

Off-by-one Error

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.31-13+deb11u3, glibc/libc-l10n@2.31-13+deb11u3 and others
  • Fixed in: 2.31-13+deb11u4

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/libc-bin@2.31-13+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/libc-l10n@2.31-13+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/libc6@2.31-13+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/locales@2.31-13+deb11u3

NVD Description

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

A flaw was found in glibc. An off-by-one buffer overflow and underflow in getcwd() may lead to memory corruption when the size of the buffer is exactly 1. A local attacker who can control the input buffer and size passed to getcwd() in a setuid program could use this flaw to potentially execute arbitrary code and escalate their privileges on the system.

Remediation

Upgrade Debian:11 glibc to version 2.31-13+deb11u4 or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.31-13+deb11u3, glibc/libc-l10n@2.31-13+deb11u3 and others
  • Fixed in: 2.31-13+deb11u7

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/libc-bin@2.31-13+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/libc-l10n@2.31-13+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/libc6@2.31-13+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/locales@2.31-13+deb11u3

NVD Description

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

A buffer overflow was discovered in the GNU C Library's dynamic loader ld.so while processing the GLIBC_TUNABLES environment variable. This issue could allow a local attacker to use maliciously crafted GLIBC_TUNABLES environment variables when launching binaries with SUID permission to execute code with elevated privileges.

Remediation

Upgrade Debian:11 glibc to version 2.31-13+deb11u7 or higher.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: libx11/libx11-6
  • Introduced through: libx11/libx11-6@2:1.7.2-1 and libx11/libx11-data@2:1.7.2-1
  • Fixed in: 2:1.7.2-1+deb11u2

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre libx11/libx11-6@2:1.7.2-1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre libx11/libx11-data@2:1.7.2-1

NVD Description

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

A vulnerability was found in libX11 due to an integer overflow within the XCreateImage() function. This flaw allows a local user to trigger an integer overflow and execute arbitrary code with elevated privileges.

Remediation

Upgrade Debian:11 libx11 to version 2:1.7.2-1+deb11u2 or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: ncurses/libtinfo6
  • Introduced through: ncurses/libtinfo6@6.2+20201114-2, ncurses/ncurses-base@6.2+20201114-2 and others
  • Fixed in: 6.2+20201114-2+deb11u2

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre ncurses/libtinfo6@6.2+20201114-2
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre ncurses/ncurses-base@6.2+20201114-2
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre ncurses/ncurses-bin@6.2+20201114-2

NVD Description

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

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

Remediation

Upgrade Debian:11 ncurses to version 6.2+20201114-2+deb11u2 or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: perl/perl-base
  • Introduced through: perl/perl-base@5.32.1-4+deb11u2
  • Fixed in: 5.32.1-4+deb11u3

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre perl/perl-base@5.32.1-4+deb11u2

NVD Description

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

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

Remediation

Upgrade Debian:11 perl to version 5.32.1-4+deb11u3 or higher.

References

high severity

Resource Exhaustion

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.10-2+deb11u3

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre expat/libexpat1@2.2.10-2+deb11u3

NVD Description

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

libexpat through 2.5.0 allows a denial of service (resource consumption) because many full reparsings are required in the case of a large token for which multiple buffer fills are needed.

Remediation

There is no fixed version for Debian:11 expat.

References

high severity

Use After Free

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.10-2+deb11u3
  • Fixed in: 2.2.10-2+deb11u5

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre expat/libexpat1@2.2.10-2+deb11u3

NVD Description

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

In libexpat through 2.4.9, there is a use-after free caused by overeager destruction of a shared DTD in XML_ExternalEntityParserCreate in out-of-memory situations.

Remediation

Upgrade Debian:11 expat to version 2.2.10-2+deb11u5 or higher.

References

high severity

Resource Exhaustion

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.66.8-1
  • Fixed in: 2.66.8-1+deb11u1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glib2.0/libglib2.0-0@2.66.8-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

A flaw was found in GLib. GVariant deserialization fails to validate that the input conforms to the expected format, leading to denial of service.

Remediation

Upgrade Debian:11 glib2.0 to version 2.66.8-1+deb11u1 or higher.

References

high severity

Double Free

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.7.1-5+deb11u1
  • Fixed in: 3.7.1-5+deb11u2

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre gnutls28/libgnutls30@3.7.1-5+deb11u1

NVD Description

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

A vulnerability found in gnutls. This security flaw happens because of a double free error occurs during verification of pkcs7 signatures in gnutls_pkcs7_verify function.

Remediation

Upgrade Debian:11 gnutls28 to version 3.7.1-5+deb11u2 or higher.

References

high severity

Improper Handling of Exceptional Conditions

  • Vulnerable module: libtirpc/libtirpc-common
  • Introduced through: libtirpc/libtirpc-common@1.3.1-1 and libtirpc/libtirpc3@1.3.1-1
  • Fixed in: 1.3.1-1+deb11u1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre libtirpc/libtirpc-common@1.3.1-1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre libtirpc/libtirpc3@1.3.1-1

NVD Description

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

In libtirpc before 1.3.3rc1, remote attackers could exhaust the file descriptors of a process that uses libtirpc because idle TCP connections are mishandled. This can, in turn, lead to an svc_run infinite loop without accepting new connections.

Remediation

Upgrade Debian:11 libtirpc to version 1.3.1-1+deb11u1 or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: libx11/libx11-6
  • Introduced through: libx11/libx11-6@2:1.7.2-1 and libx11/libx11-data@2:1.7.2-1
  • Fixed in: 2:1.7.2-1+deb11u1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre libx11/libx11-6@2:1.7.2-1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre libx11/libx11-data@2:1.7.2-1

NVD Description

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

A vulnerability was found in libX11. The security flaw occurs because the functions in src/InitExt.c in libX11 do not check that the values provided for the Request, Event, or Error IDs are within the bounds of the arrays that those functions write to, using those IDs as array indexes. They trust that they were called with values provided by an Xserver adhering to the bounds specified in the X11 protocol, as all X servers provided by X.Org do. As the protocol only specifies a single byte for these values, an out-of-bounds value provided by a malicious server (or a malicious proxy-in-the-middle) can only overwrite other portions of the Display structure and not write outside the bounds of the Display structure itself, possibly causing the client to crash with this memory corruption.

Remediation

Upgrade Debian:11 libx11 to version 2:1.7.2-1+deb11u1 or higher.

References

high severity

Double Free

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1n-0+deb11u3 and openssl/libssl1.1@1.1.1n-0+deb11u3
  • Fixed in: 1.1.1n-0+deb11u4

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre openssl@1.1.1n-0+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre openssl/libssl1.1@1.1.1n-0+deb11u3

NVD Description

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

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

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

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

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

Remediation

Upgrade Debian:11 openssl to version 1.1.1n-0+deb11u4 or higher.

References

high severity

Improper Certificate Validation

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1n-0+deb11u3 and openssl/libssl1.1@1.1.1n-0+deb11u3
  • Fixed in: 1.1.1n-0+deb11u5

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre openssl@1.1.1n-0+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre openssl/libssl1.1@1.1.1n-0+deb11u3

NVD Description

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

A security vulnerability has been identified in all supported versions

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

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

Remediation

Upgrade Debian:11 openssl to version 1.1.1n-0+deb11u5 or higher.

References

high severity

Use After Free

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1n-0+deb11u3 and openssl/libssl1.1@1.1.1n-0+deb11u3
  • Fixed in: 1.1.1n-0+deb11u4

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre openssl@1.1.1n-0+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre openssl/libssl1.1@1.1.1n-0+deb11u3

NVD Description

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

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

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

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

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

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

Remediation

Upgrade Debian:11 openssl to version 1.1.1n-0+deb11u4 or higher.

References

high severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@247.3-7 and systemd/libudev1@247.3-7

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre systemd/libsystemd0@247.3-7
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre systemd/libudev1@247.3-7

NVD Description

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

Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of service (CPU consumption) via one or more DNSSEC responses, aka the "KeyTrap" issue. One of the concerns is that, when there is a zone with many DNSKEY and RRSIG records, the protocol specification implies that an algorithm must evaluate all combinations of DNSKEY and RRSIG records.

Remediation

There is no fixed version for Debian:11 systemd.

References

high severity

Information Exposure

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.7.1-5+deb11u1
  • Fixed in: 3.7.1-5+deb11u3

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre gnutls28/libgnutls30@3.7.1-5+deb11u1

NVD Description

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

A timing side-channel in the handling of RSA ClientKeyExchange messages was discovered in GnuTLS. This side-channel can be sufficient to recover the key encrypted in the RSA ciphertext across a network in a Bleichenbacher style attack. To achieve a successful decryption the attacker would need to send a large amount of specially crafted messages to the vulnerable server. By recovering the secret from the ClientKeyExchange message, the attacker would be able to decrypt the application data exchanged over that connection.

Remediation

Upgrade Debian:11 gnutls28 to version 3.7.1-5+deb11u3 or higher.

References

high severity

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

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1n-0+deb11u3 and openssl/libssl1.1@1.1.1n-0+deb11u3
  • Fixed in: 1.1.1n-0+deb11u4

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre openssl@1.1.1n-0+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre openssl/libssl1.1@1.1.1n-0+deb11u3

NVD Description

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

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

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

Remediation

Upgrade Debian:11 openssl to version 1.1.1n-0+deb11u4 or higher.

References

high severity

Out-of-bounds Read

  • Vulnerable module: ncurses/libtinfo6
  • Introduced through: ncurses/libtinfo6@6.2+20201114-2, ncurses/ncurses-base@6.2+20201114-2 and others
  • Fixed in: 6.2+20201114-2+deb11u1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre ncurses/libtinfo6@6.2+20201114-2
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre ncurses/ncurses-base@6.2+20201114-2
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre ncurses/ncurses-bin@6.2+20201114-2

NVD Description

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

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

Remediation

Upgrade Debian:11 ncurses to version 6.2+20201114-2+deb11u1 or higher.

References

medium severity

Access of Uninitialized Pointer

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.18.3-6+deb11u1, krb5/libk5crypto3@1.18.3-6+deb11u1 and others
  • Fixed in: 1.18.3-6+deb11u4

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre krb5/libgssapi-krb5-2@1.18.3-6+deb11u1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre krb5/libk5crypto3@1.18.3-6+deb11u1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre krb5/libkrb5-3@1.18.3-6+deb11u1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre krb5/libkrb5support0@1.18.3-6+deb11u1

NVD Description

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

lib/kadm5/kadm_rpc_xdr.c in MIT Kerberos 5 (aka krb5) before 1.20.2 and 1.21.x before 1.21.1 frees an uninitialized pointer. A remote authenticated user can trigger a kadmind crash. This occurs because _xdr_kadm5_principal_ent_rec does not validate the relationship between n_key_data and the key_data array count.

Remediation

Upgrade Debian:11 krb5 to version 1.18.3-6+deb11u4 or higher.

References

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1n-0+deb11u3 and openssl/libssl1.1@1.1.1n-0+deb11u3
  • Fixed in: 1.1.1n-0+deb11u5

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre openssl@1.1.1n-0+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre openssl/libssl1.1@1.1.1n-0+deb11u3

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:11 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 Debian:11 openssl to version 1.1.1n-0+deb11u5 or higher.

References

medium severity

Information Exposure

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.7.1-5+deb11u1
  • Fixed in: 3.7.1-5+deb11u4

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre gnutls28/libgnutls30@3.7.1-5+deb11u1

NVD Description

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

A vulnerability was found that the response times to malformed ciphertexts in RSA-PSK ClientKeyExchange differ from response times of ciphertexts with correct PKCS#1 v1.5 padding.

Remediation

Upgrade Debian:11 gnutls28 to version 3.7.1-5+deb11u4 or higher.

References

medium severity

Information Exposure

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1n-0+deb11u3 and openssl/libssl1.1@1.1.1n-0+deb11u3
  • Fixed in: 1.1.1n-0+deb11u4

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre openssl@1.1.1n-0+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre openssl/libssl1.1@1.1.1n-0+deb11u3

NVD Description

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

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

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

Remediation

Upgrade Debian:11 openssl to version 1.1.1n-0+deb11u4 or higher.

References

medium severity

Deserialization of Untrusted Data

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.66.8-1
  • Fixed in: 2.66.8-1+deb11u1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glib2.0/libglib2.0-0@2.66.8-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

A flaw was found in GLib. GVariant deserialization is vulnerable to an exponential blowup issue where a crafted GVariant can cause excessive processing, leading to denial of service.

Remediation

Upgrade Debian:11 glib2.0 to version 2.66.8-1+deb11u1 or higher.

References

medium severity

Resource Exhaustion

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.66.8-1
  • Fixed in: 2.66.8-1+deb11u1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glib2.0/libglib2.0-0@2.66.8-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

A flaw was found in GLib. GVariant deserialization is vulnerable to a slowdown issue where a crafted GVariant can cause excessive processing, leading to denial of service.

Remediation

Upgrade Debian:11 glib2.0 to version 2.66.8-1+deb11u1 or higher.

References

medium severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: libx11/libx11-6
  • Introduced through: libx11/libx11-6@2:1.7.2-1 and libx11/libx11-data@2:1.7.2-1
  • Fixed in: 2:1.7.2-1+deb11u2

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre libx11/libx11-6@2:1.7.2-1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre libx11/libx11-data@2:1.7.2-1

NVD Description

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

A vulnerability was found in libX11 due to an infinite loop within the PutSubImage() function. This flaw allows a local user to consume all available system resources and cause a denial of service condition.

Remediation

Upgrade Debian:11 libx11 to version 2:1.7.2-1+deb11u2 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: libx11/libx11-6
  • Introduced through: libx11/libx11-6@2:1.7.2-1 and libx11/libx11-data@2:1.7.2-1
  • Fixed in: 2:1.7.2-1+deb11u2

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre libx11/libx11-6@2:1.7.2-1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre libx11/libx11-data@2:1.7.2-1

NVD Description

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

A vulnerability was found in libX11 due to a boundary condition within the _XkbReadKeySyms() function. This flaw allows a local user to trigger an out-of-bounds read error and read the contents of memory on the system.

Remediation

Upgrade Debian:11 libx11 to version 2:1.7.2-1+deb11u2 or higher.

References

medium severity

CVE-2022-4415

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@247.3-7 and systemd/libudev1@247.3-7
  • Fixed in: 247.3-7+deb11u2

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre systemd/libsystemd0@247.3-7
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre systemd/libudev1@247.3-7

NVD Description

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

A vulnerability was found in systemd. This security flaw can cause a local information leak due to systemd-coredump not respecting the fs.suid_dumpable kernel setting.

Remediation

Upgrade Debian:11 systemd to version 247.3-7+deb11u2 or higher.

References

medium severity

Off-by-one Error

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@247.3-7 and systemd/libudev1@247.3-7
  • Fixed in: 247.3-7+deb11u2

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre systemd/libsystemd0@247.3-7
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre systemd/libudev1@247.3-7

NVD Description

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

An off-by-one Error issue was discovered in Systemd in format_timespan() function of time-util.c. An attacker could supply specific values for time and accuracy that leads to buffer overrun in format_timespan(), leading to a Denial of Service.

Remediation

Upgrade Debian:11 systemd to version 247.3-7+deb11u2 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: tar
  • Introduced through: tar@1.34+dfsg-1
  • Fixed in: 1.34+dfsg-1+deb11u1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre tar@1.34+dfsg-1

NVD Description

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

GNU Tar through 1.34 has a one-byte out-of-bounds read that results in use of uninitialized memory for a conditional jump. Exploitation to change the flow of control has not been demonstrated. The issue occurs in from_header in list.c via a V7 archive in which mtime has approximately 11 whitespace characters.

Remediation

Upgrade Debian:11 tar to version 1.34+dfsg-1+deb11u1 or higher.

References

medium severity

Excessive Iteration

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1n-0+deb11u3 and openssl/libssl1.1@1.1.1n-0+deb11u3
  • Fixed in: 1.1.1v-0~deb11u1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre openssl@1.1.1n-0+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre openssl/libssl1.1@1.1.1n-0+deb11u3

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:11 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 Debian:11 openssl to version 1.1.1v-0~deb11u1 or higher.

References

medium severity

Improper Certificate Validation

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1n-0+deb11u3 and openssl/libssl1.1@1.1.1n-0+deb11u3
  • Fixed in: 1.1.1n-0+deb11u5

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre openssl@1.1.1n-0+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre openssl/libssl1.1@1.1.1n-0+deb11u3

NVD Description

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

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

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

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

Remediation

Upgrade Debian:11 openssl to version 1.1.1n-0+deb11u5 or higher.

References

medium severity

Improper Certificate Validation

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1n-0+deb11u3 and openssl/libssl1.1@1.1.1n-0+deb11u3
  • Fixed in: 1.1.1n-0+deb11u5

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre openssl@1.1.1n-0+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre openssl/libssl1.1@1.1.1n-0+deb11u3

NVD Description

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

The function X509_VERIFY_PARAM_add0_policy() is documented to implicitly enable the certificate policy check when doing certificate verification. However the implementation of the function does not enable the check which allows certificates with invalid or incorrect policies to pass the certificate verification.

As suddenly enabling the policy check could break existing deployments it was decided to keep the existing behavior of the X509_VERIFY_PARAM_add0_policy() function.

Instead the applications that require OpenSSL to perform certificate policy check need to use X509_VERIFY_PARAM_set1_policies() or explicitly enable the policy check by calling X509_VERIFY_PARAM_set_flags() with the X509_V_FLAG_POLICY_CHECK flag argument.

Certificate policy checks are disabled by default in OpenSSL and are not commonly used by applications.

Remediation

Upgrade Debian:11 openssl to version 1.1.1n-0+deb11u5 or higher.

References

medium severity

Inefficient Regular Expression Complexity

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1n-0+deb11u3 and openssl/libssl1.1@1.1.1n-0+deb11u3
  • Fixed in: 1.1.1v-0~deb11u1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre openssl@1.1.1n-0+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre openssl/libssl1.1@1.1.1n-0+deb11u3

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:11 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 Debian:11 openssl to version 1.1.1v-0~deb11u1 or higher.

References

medium severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1n-0+deb11u3 and openssl/libssl1.1@1.1.1n-0+deb11u3
  • Fixed in: 1.1.1n-0+deb11u4

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre openssl@1.1.1n-0+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre openssl/libssl1.1@1.1.1n-0+deb11u3

NVD Description

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

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

Remediation

Upgrade Debian:11 openssl to version 1.1.1n-0+deb11u4 or higher.

References

low severity

Out-of-bounds Read

  • Vulnerable module: db5.3/libdb5.3
  • Introduced through: db5.3/libdb5.3@5.3.28+dfsg1-0.8

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre db5.3/libdb5.3@5.3.28+dfsg1-0.8

NVD Description

Note: Versions mentioned in the description apply only to the upstream db5.3 package and not the db5.3 package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

SQLite3 from 3.6.0 to and including 3.27.2 is vulnerable to heap out-of-bound read in the rtreenode() function when handling invalid rtree tables.

Remediation

There is no fixed version for Debian:11 db5.3.

References

low severity

Out-of-Bounds

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.31-13+deb11u3, glibc/libc-l10n@2.31-13+deb11u3 and others

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/libc-bin@2.31-13+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/libc-l10n@2.31-13+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/libc6@2.31-13+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/locales@2.31-13+deb11u3

NVD Description

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

GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may bypass stack guard protection. The component is: nptl. The attack vector is: Exploit stack buffer overflow vulnerability and use this bypass vulnerability to bypass stack guard. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat.

Remediation

There is no fixed version for Debian:11 glibc.

References

low severity

CVE-2020-27619

  • Vulnerable module: python3.9/libpython3.9-minimal
  • Introduced through: python3.9/libpython3.9-minimal@3.9.2-1 and python3.9/python3.9-minimal@3.9.2-1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre python3.9/libpython3.9-minimal@3.9.2-1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre python3.9/python3.9-minimal@3.9.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.9 package and not the python3.9 package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

In Python 3 through 3.9.0, the Lib/test/multibytecodec_support.py CJK codec tests call eval() on content retrieved via HTTP.

Remediation

There is no fixed version for Debian:11 python3.9.

References

low severity

Improper Input Validation

  • Vulnerable module: python3.9/libpython3.9-minimal
  • Introduced through: python3.9/libpython3.9-minimal@3.9.2-1 and python3.9/python3.9-minimal@3.9.2-1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre python3.9/libpython3.9-minimal@3.9.2-1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre python3.9/python3.9-minimal@3.9.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.9 package and not the python3.9 package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

In Python before 3,9,5, the ipaddress library mishandles leading zero characters in the octets of an IP address string. This (in some situations) allows attackers to bypass access control that is based on IP addresses.

Remediation

There is no fixed version for Debian:11 python3.9.

References

low severity

Integer Overflow or Wraparound

  • Vulnerable module: python3.9/libpython3.9-minimal
  • Introduced through: python3.9/libpython3.9-minimal@3.9.2-1 and python3.9/python3.9-minimal@3.9.2-1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre python3.9/libpython3.9-minimal@3.9.2-1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre python3.9/python3.9-minimal@3.9.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.9 package and not the python3.9 package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

The Keccak XKCP SHA-3 reference implementation before fdc6fef has an integer overflow and resultant buffer overflow that allows attackers to execute arbitrary code or eliminate expected cryptographic properties. This occurs in the sponge function interface.

Remediation

There is no fixed version for Debian:11 python3.9.

References

low severity

CVE-2005-2541

  • Vulnerable module: tar
  • Introduced through: tar@1.34+dfsg-1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre tar@1.34+dfsg-1

NVD Description

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

Tar 1.15.1 does not properly warn the user when extracting setuid or setgid files, which may allow local users or remote attackers to gain privileges.

Remediation

There is no fixed version for Debian:11 tar.

References

low severity

CVE-2019-1010023

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.31-13+deb11u3, glibc/libc-l10n@2.31-13+deb11u3 and others

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/libc-bin@2.31-13+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/libc-l10n@2.31-13+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/libc6@2.31-13+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/locales@2.31-13+deb11u3

NVD Description

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

GNU Libc current is affected by: Re-mapping current loaded library with malicious ELF file. The impact is: In worst case attacker may evaluate privileges. The component is: libld. The attack vector is: Attacker sends 2 ELF files to victim and asks to run ldd on it. ldd execute code. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat.

Remediation

There is no fixed version for Debian:11 glibc.

References

low severity

Improper Certificate Validation

  • Vulnerable module: perl/perl-base
  • Introduced through: perl/perl-base@5.32.1-4+deb11u2

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre perl/perl-base@5.32.1-4+deb11u2

NVD Description

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

HTTP::Tiny before 0.083, a Perl core module since 5.13.9 and available standalone on CPAN, has an insecure default TLS configuration where users must opt in to verify certificates.

Remediation

There is no fixed version for Debian:11 perl.

References

low severity

Improper Certificate Validation

  • Vulnerable module: perl/perl-base
  • Introduced through: perl/perl-base@5.32.1-4+deb11u2

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre perl/perl-base@5.32.1-4+deb11u2

NVD Description

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

CPAN.pm before 2.35 does not verify TLS certificates when downloading distributions over HTTPS.

Remediation

There is no fixed version for Debian:11 perl.

References

low severity

Out-of-bounds Write

  • Vulnerable module: bash
  • Introduced through: bash@5.1-2+deb11u1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre bash@5.1-2+deb11u1

NVD Description

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

A flaw was found in the bash package, where a heap-buffer overflow can occur in valid parameter_transform. This issue may lead to memory problems.

Remediation

There is no fixed version for Debian:11 bash.

References

low severity

Out-of-bounds Read

  • Vulnerable module: e2fsprogs
  • Introduced through: e2fsprogs@1.46.2-2, e2fsprogs/libcom-err2@1.46.2-2 and others

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre e2fsprogs@1.46.2-2
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre e2fsprogs/libcom-err2@1.46.2-2
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre e2fsprogs/libext2fs2@1.46.2-2
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre e2fsprogs/libss2@1.46.2-2
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre e2fsprogs/logsave@1.46.2-2

NVD Description

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

An out-of-bounds read/write vulnerability was found in e2fsprogs 1.46.5. This issue leads to a segmentation fault and possibly arbitrary code execution via a specially crafted filesystem.

Remediation

There is no fixed version for Debian:11 e2fsprogs.

References

low severity

Out-of-bounds Write

  • Vulnerable module: freetype/libfreetype6
  • Introduced through: freetype/libfreetype6@2.10.4+dfsg-1+deb11u1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre freetype/libfreetype6@2.10.4+dfsg-1+deb11u1

NVD Description

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

ftbench.c in FreeType Demo Programs through 2.12.1 has a heap-based buffer overflow.

Remediation

There is no fixed version for Debian:11 freetype.

References

low severity

Out-of-Bounds

  • Vulnerable module: pcre3/libpcre3
  • Introduced through: pcre3/libpcre3@2:8.39-13

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre pcre3/libpcre3@2:8.39-13

NVD Description

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

Stack-based buffer overflow in the pcre32_copy_substring function in pcre_get.c in libpcre1 in PCRE 8.40 allows remote attackers to cause a denial of service (WRITE of size 4) or possibly have unspecified other impact via a crafted file.

Remediation

There is no fixed version for Debian:11 pcre3.

References

low severity

Out-of-Bounds

  • Vulnerable module: pcre3/libpcre3
  • Introduced through: pcre3/libpcre3@2:8.39-13

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre pcre3/libpcre3@2:8.39-13

NVD Description

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

Stack-based buffer overflow in the pcre32_copy_substring function in pcre_get.c in libpcre1 in PCRE 8.40 allows remote attackers to cause a denial of service (WRITE of size 268) or possibly have unspecified other impact via a crafted file.

Remediation

There is no fixed version for Debian:11 pcre3.

References

low severity

Improper Verification of Cryptographic Signature

  • Vulnerable module: perl/perl-base
  • Introduced through: perl/perl-base@5.32.1-4+deb11u2

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre perl/perl-base@5.32.1-4+deb11u2

NVD Description

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

CPAN 2.28 allows Signature Verification Bypass.

Remediation

There is no fixed version for Debian:11 perl.

References

low severity

CVE-2022-42919

  • Vulnerable module: python3.9/libpython3.9-minimal
  • Introduced through: python3.9/libpython3.9-minimal@3.9.2-1 and python3.9/python3.9-minimal@3.9.2-1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre python3.9/libpython3.9-minimal@3.9.2-1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre python3.9/python3.9-minimal@3.9.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.9 package and not the python3.9 package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

Python 3.9.x before 3.9.16 and 3.10.x before 3.10.9 on Linux allows local privilege escalation in a non-default configuration. The Python multiprocessing library, when used with the forkserver start method on Linux, allows pickles to be deserialized from any user in the same machine local network namespace, which in many system configurations means any user on the same machine. Pickles can execute arbitrary code. Thus, this allows for local user privilege escalation to the user that any forkserver process is running as. Setting multiprocessing.util.abstract_sockets_supported to False is a workaround. The forkserver start method for multiprocessing is not the default start method. This issue is Linux specific because only Linux supports abstract namespace sockets. CPython before 3.9 does not make use of Linux abstract namespace sockets by default. Support for users manually specifying an abstract namespace socket was added as a bugfix in 3.7.8 and 3.8.3, but users would need to make specific uncommon API calls in order to do that in CPython before 3.9.

Remediation

There is no fixed version for Debian:11 python3.9.

References

low severity

Incorrect Permission Assignment for Critical Resource

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.8.1-1 and shadow/passwd@1:4.8.1-1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre shadow/login@1:4.8.1-1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre shadow/passwd@1:4.8.1-1

NVD Description

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

shadow 4.8, in certain circumstances affecting at least Gentoo, Arch Linux, and Void Linux, allows local users to obtain root access because setuid programs are misconfigured. Specifically, this affects shadow 4.8 when compiled using --with-libpam but without explicitly passing --disable-account-tools-setuid, and without a PAM configuration suitable for use with setuid account management tools. This combination leads to account management tools (groupadd, groupdel, groupmod, useradd, userdel, usermod) that can easily be used by unprivileged local users to escalate privileges to root in multiple ways. This issue became much more relevant in approximately December 2019 when an unrelated bug was fixed (i.e., the chmod calls to suidusbins were fixed in the upstream Makefile which is now included in the release version 4.8).

Remediation

There is no fixed version for Debian:11 shadow.

References

low severity

Arbitrary Command Injection

  • Vulnerable module: python3.9/libpython3.9-minimal
  • Introduced through: python3.9/libpython3.9-minimal@3.9.2-1 and python3.9/python3.9-minimal@3.9.2-1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre python3.9/libpython3.9-minimal@3.9.2-1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre python3.9/python3.9-minimal@3.9.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.9 package and not the python3.9 package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

In Python (aka CPython) up to 3.10.8, the mailcap module does not add escape characters into commands discovered in the system mailcap file. This may allow attackers to inject shell commands into applications that call mailcap.findmatch with untrusted input (if they lack validation of user-provided filenames or arguments). The fix is also back-ported to 3.7, 3.8, 3.9

Remediation

There is no fixed version for Debian:11 python3.9.

References

low severity

Uncontrolled Recursion

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.31-13+deb11u3, glibc/libc-l10n@2.31-13+deb11u3 and others

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/libc-bin@2.31-13+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/libc-l10n@2.31-13+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/libc6@2.31-13+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/locales@2.31-13+deb11u3

NVD Description

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

In the GNU C Library (aka glibc or libc6) through 2.29, check_dst_limits_calc_pos_1 in posix/regexec.c has Uncontrolled Recursion, as demonstrated by '(|)(\1\1)*' in grep, a different issue than CVE-2018-20796. NOTE: the software maintainer disputes that this is a vulnerability because the behavior occurs only with a crafted pattern

Remediation

There is no fixed version for Debian:11 glibc.

References

low severity

Uncontrolled Recursion

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.31-13+deb11u3, glibc/libc-l10n@2.31-13+deb11u3 and others

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/libc-bin@2.31-13+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/libc-l10n@2.31-13+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/libc6@2.31-13+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/locales@2.31-13+deb11u3

NVD Description

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

In the GNU C Library (aka glibc or libc6) through 2.29, check_dst_limits_calc_pos_1 in posix/regexec.c has Uncontrolled Recursion, as demonstrated by '(\227|)(\1\1|t1|\\2537)+' in grep.

Remediation

There is no fixed version for Debian:11 glibc.

References

low severity

Improper Verification of Cryptographic Signature

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.7.1-5+deb11u1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre gnutls28/libgnutls30@3.7.1-5+deb11u1

NVD Description

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

A vulnerability was found in GnuTLS, where a cockpit (which uses gnuTLS) rejects a certificate chain with distributed trust. This issue occurs when validating a certificate chain with cockpit-certificate-ensure. This flaw allows an unauthenticated, remote client or attacker to initiate a denial of service attack.

Remediation

There is no fixed version for Debian:11 gnutls28.

References

low severity

Information Exposure

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.7.1-5+deb11u1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre gnutls28/libgnutls30@3.7.1-5+deb11u1

NVD Description

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

A vulnerability was found in GnuTLS. The response times to malformed ciphertexts in RSA-PSK ClientKeyExchange differ from the response times of ciphertexts with correct PKCS#1 v1.5 padding. This issue may allow a remote attacker to perform a timing side-channel attack in the RSA-PSK key exchange, potentially leading to the leakage of sensitive data. CVE-2024-0553 is designated as an incomplete resolution for CVE-2023-5981.

Remediation

There is no fixed version for Debian:11 gnutls28.

References

low severity

Integer Overflow or Wraparound

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.18.3-6+deb11u1, krb5/libk5crypto3@1.18.3-6+deb11u1 and others

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre krb5/libgssapi-krb5-2@1.18.3-6+deb11u1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre krb5/libk5crypto3@1.18.3-6+deb11u1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre krb5/libkrb5-3@1.18.3-6+deb11u1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre krb5/libkrb5support0@1.18.3-6+deb11u1

NVD Description

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

An issue was discovered in MIT Kerberos 5 (aka krb5) through 1.16. There is a variable "dbentry->n_key_data" in kadmin/dbutil/dump.c that can store 16-bit data but unknowingly the developer has assigned a "u4" variable to it, which is for 32-bit data. An attacker can use this vulnerability to affect other artifacts of the database as we know that a Kerberos database dump file contains trusted data.

Remediation

There is no fixed version for Debian:11 krb5.

References

low severity

Information Exposure

  • Vulnerable module: libgcrypt20
  • Introduced through: libgcrypt20@1.8.7-6

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre libgcrypt20@1.8.7-6

NVD Description

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

Libgcrypt before 1.8.8 and 1.9.x before 1.9.3 mishandles ElGamal encryption because it lacks exponent blinding to address a side-channel attack against mpi_powm, and the window size is not chosen appropriately. This, for example, affects use of ElGamal in OpenPGP.

Remediation

There is no fixed version for Debian:11 libgcrypt20.

References

low severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: libgcrypt20
  • Introduced through: libgcrypt20@1.8.7-6

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre libgcrypt20@1.8.7-6

NVD Description

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

cipher/elgamal.c in Libgcrypt through 1.8.2, when used to encrypt messages directly, improperly encodes plaintexts, which allows attackers to obtain sensitive information by reading ciphertext data (i.e., it does not have semantic security in face of a ciphertext-only attack). The Decisional Diffie-Hellman (DDH) assumption does not hold for Libgcrypt's ElGamal implementation.

Remediation

There is no fixed version for Debian:11 libgcrypt20.

References

low severity

Resource Exhaustion

  • Vulnerable module: libzstd/libzstd1
  • Introduced through: libzstd/libzstd1@1.4.8+dfsg-2.1

low severity

Integer Overflow or Wraparound

  • Vulnerable module: pcre2/libpcre2-8-0
  • Introduced through: pcre2/libpcre2-8-0@10.36-2

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre pcre2/libpcre2-8-0@10.36-2

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 pcre2.

References

low severity

Out-of-bounds Read

  • Vulnerable module: pcre3/libpcre3
  • Introduced through: pcre3/libpcre3@2:8.39-13

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre pcre3/libpcre3@2:8.39-13

NVD Description

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

libpcre in PCRE before 8.43 allows a subject buffer over-read in JIT when UTF is disabled, and \X or \R has more than one fixed quantifier, a related issue to CVE-2019-20454.

Remediation

There is no fixed version for Debian:11 pcre3.

References

low severity

Uncontrolled Recursion

  • Vulnerable module: pcre3/libpcre3
  • Introduced through: pcre3/libpcre3@2:8.39-13

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre pcre3/libpcre3@2:8.39-13

NVD Description

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

In PCRE 8.41, the OP_KETRMAX feature in the match function in pcre_exec.c allows stack exhaustion (uncontrolled recursion) when processing a crafted regular expression.

Remediation

There is no fixed version for Debian:11 pcre3.

References

low severity

Link Following

  • Vulnerable module: perl/perl-base
  • Introduced through: perl/perl-base@5.32.1-4+deb11u2

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre perl/perl-base@5.32.1-4+deb11u2

NVD Description

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

_is_safe in the File::Temp module for Perl does not properly handle symlinks.

Remediation

There is no fixed version for Debian:11 perl.

References

low severity

Algorithmic Complexity

  • Vulnerable module: python3.9/libpython3.9-minimal
  • Introduced through: python3.9/libpython3.9-minimal@3.9.2-1 and python3.9/python3.9-minimal@3.9.2-1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre python3.9/libpython3.9-minimal@3.9.2-1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre python3.9/python3.9-minimal@3.9.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.9 package and not the python3.9 package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

An issue was discovered in Python before 3.11.1. An unnecessary quadratic algorithm exists in one path when processing some inputs to the IDNA (RFC 3490) decoder, such that a crafted, unreasonably long name being presented to the decoder could lead to a CPU denial of service. Hostnames are often supplied by remote servers that could be controlled by a malicious actor; in such a scenario, they could trigger excessive CPU consumption on the client attempting to make use of an attacker-supplied supposed hostname. For example, the attack payload could be placed in the Location header of an HTTP response with status code 302. A fix is planned in 3.11.1, 3.10.9, 3.9.16, 3.8.16, and 3.7.16.

Remediation

There is no fixed version for Debian:11 python3.9.

References

low severity

Arbitrary Code Injection

  • Vulnerable module: python3.9/libpython3.9-minimal
  • Introduced through: python3.9/libpython3.9-minimal@3.9.2-1 and python3.9/python3.9-minimal@3.9.2-1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre python3.9/libpython3.9-minimal@3.9.2-1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre python3.9/python3.9-minimal@3.9.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.9 package and not the python3.9 package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

A flaw was found in Python, specifically within the urllib.parse module. This module helps break Uniform Resource Locator (URL) strings into components. The issue involves how the urlparse method does not sanitize input and allows characters like '\r' and '\n' in the URL path. This flaw allows an attacker to input a crafted URL, leading to injection attacks. This flaw affects Python versions prior to 3.10.0b1, 3.9.5, 3.8.11, 3.7.11 and 3.6.14.

Remediation

There is no fixed version for Debian:11 python3.9.

References

low severity

Improper Input Validation

  • Vulnerable module: python3.9/libpython3.9-minimal
  • Introduced through: python3.9/libpython3.9-minimal@3.9.2-1 and python3.9/python3.9-minimal@3.9.2-1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre python3.9/libpython3.9-minimal@3.9.2-1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre python3.9/python3.9-minimal@3.9.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.9 package and not the python3.9 package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

An issue in the urllib.parse component of Python before 3.11.4 allows attackers to bypass blocklisting methods by supplying a URL that starts with blank characters.

Remediation

There is no fixed version for Debian:11 python3.9.

References

low severity

Incorrect Type Conversion or Cast

  • Vulnerable module: python3.9/libpython3.9-minimal
  • Introduced through: python3.9/libpython3.9-minimal@3.9.2-1 and python3.9/python3.9-minimal@3.9.2-1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre python3.9/libpython3.9-minimal@3.9.2-1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre python3.9/python3.9-minimal@3.9.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.9 package and not the python3.9 package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

A flaw was found in python. In algorithms with quadratic time complexity using non-binary bases, when using int("text"), a system could take 50ms to parse an int string with 100,000 digits and 5s for 1,000,000 digits (float, decimal, int.from_bytes(), and int() for binary bases 2, 4, 8, 16, and 32 are not affected). The highest threat from this vulnerability is to system availability.

Remediation

There is no fixed version for Debian:11 python3.9.

References

low severity

Resource Exhaustion

  • Vulnerable module: python3.9/libpython3.9-minimal
  • Introduced through: python3.9/libpython3.9-minimal@3.9.2-1 and python3.9/python3.9-minimal@3.9.2-1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre python3.9/libpython3.9-minimal@3.9.2-1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre python3.9/python3.9-minimal@3.9.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.9 package and not the python3.9 package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

A flaw was found in python. An improperly handled HTTP response in the HTTP client code of python may allow a remote attacker, who controls the HTTP server, to make the client script enter an infinite loop, consuming CPU time. The highest threat from this vulnerability is to system availability.

Remediation

There is no fixed version for Debian:11 python3.9.

References

low severity

Open Redirect

  • Vulnerable module: python3.9/libpython3.9-minimal
  • Introduced through: python3.9/libpython3.9-minimal@3.9.2-1 and python3.9/python3.9-minimal@3.9.2-1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre python3.9/libpython3.9-minimal@3.9.2-1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre python3.9/python3.9-minimal@3.9.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.9 package and not the python3.9 package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

Python 3.x through 3.10 has an open redirection vulnerability in lib/http/server.py due to no protection against multiple (/) at the beginning of URI path which may leads to information disclosure. NOTE: this is disputed by a third party because the http.server.html documentation page states "Warning: http.server is not recommended for production. It only implements basic security checks."

Remediation

There is no fixed version for Debian:11 python3.9.

References

low severity

Improper Input Validation

  • Vulnerable module: coreutils/coreutils
  • Introduced through: coreutils/coreutils@8.32-4+b1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre coreutils/coreutils@8.32-4+b1

NVD Description

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

chroot in GNU coreutils, when used with --userspec, allows local users to escape to the parent session via a crafted TIOCSTI ioctl call, which pushes characters to the terminal's input buffer.

Remediation

There is no fixed version for Debian:11 coreutils.

References

low severity

Memory Leak

  • Vulnerable module: libpng1.6/libpng16-16
  • Introduced through: libpng1.6/libpng16-16@1.6.37-3

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre libpng1.6/libpng16-16@1.6.37-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

png_create_info_struct in png.c in libpng 1.6.36 has a memory leak, as demonstrated by pngcp. NOTE: a third party has stated "I don't think it is libpng's job to free this buffer.

Remediation

There is no fixed version for Debian:11 libpng1.6.

References

low severity

CVE-2023-50495

  • Vulnerable module: ncurses/libtinfo6
  • Introduced through: ncurses/libtinfo6@6.2+20201114-2, ncurses/ncurses-base@6.2+20201114-2 and others

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre ncurses/libtinfo6@6.2+20201114-2
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre ncurses/ncurses-base@6.2+20201114-2
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre ncurses/ncurses-bin@6.2+20201114-2

NVD Description

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

NCurse v6.4-20230418 was discovered to contain a segmentation fault via the component _nc_wrap_entry().

Remediation

There is no fixed version for Debian:11 ncurses.

References

low severity

Resource Exhaustion

  • Vulnerable module: python3.9/libpython3.9-minimal
  • Introduced through: python3.9/libpython3.9-minimal@3.9.2-1 and python3.9/python3.9-minimal@3.9.2-1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre python3.9/libpython3.9-minimal@3.9.2-1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre python3.9/python3.9-minimal@3.9.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.9 package and not the python3.9 package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

There's a flaw in urllib's AbstractBasicAuthHandler class. An attacker who controls a malicious HTTP server that an HTTP client (such as web browser) connects to, could trigger a Regular Expression Denial of Service (ReDOS) during an authentication request with a specially crafted payload that is sent by the server to the client. The greatest threat that this flaw poses is to application availability.

Remediation

There is no fixed version for Debian:11 python3.9.

References

low severity

XML External Entity (XXE) Injection

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.10-2+deb11u3

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre expat/libexpat1@2.2.10-2+deb11u3

NVD Description

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

expat 2.1.0 and earlier does not properly handle entities expansion unless an application developer uses the XML_SetEntityDeclHandler function, which allows remote attackers to cause a denial of service (resource consumption), send HTTP requests to intranet servers, or read arbitrary files via a crafted XML document, aka an XML External Entity (XXE) issue. NOTE: it could be argued that because expat already provides the ability to disable external entity expansion, the responsibility for resolving this issue lies with application developers; according to this argument, this entry should be REJECTed, and each affected application would need its own CVE.

Remediation

There is no fixed version for Debian:11 expat.

References

low severity

Access Restriction Bypass

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.8.1-1 and shadow/passwd@1:4.8.1-1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre shadow/login@1:4.8.1-1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre shadow/passwd@1:4.8.1-1

NVD Description

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

initscripts in rPath Linux 1 sets insecure permissions for the /var/log/btmp file, which allows local users to obtain sensitive information regarding authentication attempts. NOTE: because sshd detects the insecure permissions and does not log certain events, this also prevents sshd from logging failed authentication attempts by remote attackers.

Remediation

There is no fixed version for Debian:11 shadow.

References

low severity

Authentication Bypass

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@247.3-7 and systemd/libudev1@247.3-7

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre systemd/libsystemd0@247.3-7
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre systemd/libudev1@247.3-7

NVD Description

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

An exploitable denial-of-service vulnerability exists in Systemd 245. A specially crafted DHCP FORCERENEW packet can cause a server running the DHCP client to be vulnerable to a DHCP ACK spoofing attack. An attacker can forge a pair of FORCERENEW and DCHP ACK packets to reconfigure the server.

Remediation

There is no fixed version for Debian:11 systemd.

References

low severity

Use After Free

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.31-13+deb11u3, glibc/libc-l10n@2.31-13+deb11u3 and others

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/libc-bin@2.31-13+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/libc-l10n@2.31-13+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/libc6@2.31-13+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/locales@2.31-13+deb11u3

NVD Description

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

A flaw was found in glibc. In an extremely rare situation, the getaddrinfo function may access memory that has been freed, resulting in an application crash. This issue is only exploitable when a NSS module implements only the nss_gethostbyname2_r and nss_getcanonname_r hooks without implementing the nss*_gethostbyname3_r hook. The resolved name should return a large number of IPv6 and IPv4, and the call to the getaddrinfo function should have the AF_INET6 address family with AI_CANONNAME, AI_ALL and AI_V4MAPPED as flags.

Remediation

There is no fixed version for Debian:11 glibc.

References

low severity

Use After Free

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.31-13+deb11u3, glibc/libc-l10n@2.31-13+deb11u3 and others

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/libc-bin@2.31-13+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/libc-l10n@2.31-13+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/libc6@2.31-13+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/locales@2.31-13+deb11u3

NVD Description

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

A flaw was found in glibc. In an uncommon situation, the gaih_inet function may use memory that has been freed, resulting in an application crash. This issue is only exploitable when the getaddrinfo function is called and the hosts database in /etc/nsswitch.conf is configured with SUCCESS=continue or SUCCESS=merge.

Remediation

There is no fixed version for Debian:11 glibc.

References

low severity

CVE-2023-7008

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@247.3-7 and systemd/libudev1@247.3-7

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre systemd/libsystemd0@247.3-7
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre systemd/libudev1@247.3-7

NVD Description

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

A vulnerability was found in systemd-resolved. This issue may allow systemd-resolved to accept records of DNSSEC-signed domains even when they have no signature, allowing man-in-the-middles (or the upstream DNS resolver) to manipulate records.

Remediation

There is no fixed version for Debian:11 systemd.

References

low severity

Information Exposure

  • Vulnerable module: python3.9/libpython3.9-minimal
  • Introduced through: python3.9/libpython3.9-minimal@3.9.2-1 and python3.9/python3.9-minimal@3.9.2-1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre python3.9/libpython3.9-minimal@3.9.2-1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre python3.9/python3.9-minimal@3.9.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.9 package and not the python3.9 package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

There's a flaw in Python 3's pydoc. A local or adjacent attacker who discovers or is able to convince another local or adjacent user to start a pydoc server could access the server and use it to disclose sensitive information belonging to the other user that they would not normally be able to access. The highest risk of this flaw is to data confidentiality. This flaw affects Python versions before 3.8.9, Python versions before 3.9.3 and Python versions before 3.10.0a7.

Remediation

There is no fixed version for Debian:11 python3.9.

References

low severity

Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion')

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.10-2+deb11u3

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre expat/libexpat1@2.2.10-2+deb11u3

NVD Description

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

libexpat through 2.5.0 allows recursive XML Entity Expansion if XML_DTD is undefined at compile time.

Remediation

There is no fixed version for Debian:11 expat.

References

low severity

Buffer Overflow

  • Vulnerable module: libpng1.6/libpng16-16
  • Introduced through: libpng1.6/libpng16-16@1.6.37-3

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre libpng1.6/libpng16-16@1.6.37-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

A heap overflow flaw was found in libpngs' pngimage.c program. This flaw allows an attacker with local network access to pass a specially crafted PNG file to the pngimage utility, causing an application to crash, leading to a denial of service.

Remediation

There is no fixed version for Debian:11 libpng1.6.

References

low severity

CVE-2024-0727

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1n-0+deb11u3 and openssl/libssl1.1@1.1.1n-0+deb11u3

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre openssl@1.1.1n-0+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre openssl/libssl1.1@1.1.1n-0+deb11u3

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:11 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

There is no fixed version for Debian:11 openssl.

References

low severity

CVE-2024-22365

  • Vulnerable module: pam/libpam-modules
  • Introduced through: pam/libpam-modules@1.4.0-9+deb11u1, pam/libpam-modules-bin@1.4.0-9+deb11u1 and others

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre pam/libpam-modules@1.4.0-9+deb11u1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre pam/libpam-modules-bin@1.4.0-9+deb11u1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre pam/libpam-runtime@1.4.0-9+deb11u1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre pam/libpam0g@1.4.0-9+deb11u1

NVD Description

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

linux-pam (aka Linux PAM) before 1.6.0 allows attackers to cause a denial of service (blocked login process) via mkfifo because the openat call (for protect_dir) lacks O_DIRECTORY.

Remediation

There is no fixed version for Debian:11 pam.

References

low severity

Out-of-Bounds

  • Vulnerable module: pcre3/libpcre3
  • Introduced through: pcre3/libpcre3@2:8.39-13

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre pcre3/libpcre3@2:8.39-13

NVD Description

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

In PCRE 8.41, after compiling, a pcretest load test PoC produces a crash overflow in the function match() in pcre_exec.c because of a self-recursive call. NOTE: third parties dispute the relevance of this report, noting that there are options that can be used to limit the amount of stack that is used

Remediation

There is no fixed version for Debian:11 pcre3.

References

low severity

Improper Authentication

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.8.1-1 and shadow/passwd@1:4.8.1-1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre shadow/login@1:4.8.1-1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre shadow/passwd@1:4.8.1-1

NVD Description

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

A flaw was found in shadow-utils. When asking for a new password, shadow-utils asks the password twice. If the password fails on the second attempt, shadow-utils fails in cleaning the buffer used to store the first entry. This may allow an attacker with enough access to retrieve the password from the memory.

Remediation

There is no fixed version for Debian:11 shadow.

References

low severity

Information Exposure

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.36.1-8+deb11u1, util-linux/bsdutils@1:2.36.1-8+deb11u1 and others

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre util-linux@2.36.1-8+deb11u1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre util-linux/bsdutils@1:2.36.1-8+deb11u1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre util-linux/libblkid1@2.36.1-8+deb11u1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre util-linux/libmount1@2.36.1-8+deb11u1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre util-linux/libsmartcols1@2.36.1-8+deb11u1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre util-linux/libuuid1@2.36.1-8+deb11u1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre util-linux/mount@2.36.1-8+deb11u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream util-linux package and not the util-linux package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

A flaw was found in the util-linux chfn and chsh utilities when compiled with Readline support. The Readline library uses an "INPUTRC" environment variable to get a path to the library config file. When the library cannot parse the specified file, it prints an error message containing data from the file. This flaw allows an unprivileged user to read root-owned files, potentially leading to privilege escalation. This flaw affects util-linux versions prior to 2.37.4.

Remediation

There is no fixed version for Debian:11 util-linux.

References

low severity

Cryptographic Issues

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1n-0+deb11u3 and openssl/libssl1.1@1.1.1n-0+deb11u3

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre openssl@1.1.1n-0+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre openssl/libssl1.1@1.1.1n-0+deb11u3

NVD Description

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

The NIST SP 800-90A default statement of the Dual Elliptic Curve Deterministic Random Bit Generation (Dual_EC_DRBG) algorithm contains point Q constants with a possible relationship to certain "skeleton key" values, which might allow context-dependent attackers to defeat cryptographic protection mechanisms by leveraging knowledge of those values. NOTE: this is a preliminary CVE for Dual_EC_DRBG; future research may provide additional details about point Q and associated attacks, and could potentially lead to a RECAST or REJECT of this CVE.

Remediation

There is no fixed version for Debian:11 openssl.

References

low severity

Cryptographic Issues

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.66.8-1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glib2.0/libglib2.0-0@2.66.8-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

GLib 2.31.8 and earlier, when the g_str_hash function is used, computes hash values without restricting the ability to trigger hash collisions predictably, which allows context-dependent attackers to cause a denial of service (CPU consumption) via crafted input to an application that maintains a hash table. NOTE: this issue may be disputed by the vendor; the existence of the g_str_hash function is not a vulnerability in the library, because callers of g_hash_table_new and g_hash_table_new_full can specify an arbitrary hash function that is appropriate for the application.

Remediation

There is no fixed version for Debian:11 glib2.0.

References

low severity

Information Exposure

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.31-13+deb11u3, glibc/libc-l10n@2.31-13+deb11u3 and others

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/libc-bin@2.31-13+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/libc-l10n@2.31-13+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/libc6@2.31-13+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/locales@2.31-13+deb11u3

NVD Description

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

GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may bypass ASLR using cache of thread stack and heap. The component is: glibc. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat.

Remediation

There is no fixed version for Debian:11 glibc.

References

low severity

Use of Insufficiently Random Values

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.31-13+deb11u3, glibc/libc-l10n@2.31-13+deb11u3 and others

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/libc-bin@2.31-13+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/libc-l10n@2.31-13+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/libc6@2.31-13+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/locales@2.31-13+deb11u3

NVD Description

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

GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may guess the heap addresses of pthread_created thread. The component is: glibc. NOTE: the vendor's position is "ASLR bypass itself is not a vulnerability.

Remediation

There is no fixed version for Debian:11 glibc.

References

low severity

Improper Check for Unusual or Exceptional Conditions

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1n-0+deb11u3 and openssl/libssl1.1@1.1.1n-0+deb11u3

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre openssl@1.1.1n-0+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre openssl/libssl1.1@1.1.1n-0+deb11u3

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:11 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

There is no fixed version for Debian:11 openssl.

References

low severity

CVE-2023-40217

  • Vulnerable module: python3.9/libpython3.9-minimal
  • Introduced through: python3.9/libpython3.9-minimal@3.9.2-1 and python3.9/python3.9-minimal@3.9.2-1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre python3.9/libpython3.9-minimal@3.9.2-1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre python3.9/python3.9-minimal@3.9.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.9 package and not the python3.9 package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

An issue was discovered in Python before 3.8.18, 3.9.x before 3.9.18, 3.10.x before 3.10.13, and 3.11.x before 3.11.5. It primarily affects servers (such as HTTP servers) that use TLS client authentication. If a TLS server-side socket is created, receives data into the socket buffer, and then is closed quickly, there is a brief window where the SSLSocket instance will detect the socket as "not connected" and won't initiate a handshake, but buffered data will still be readable from the socket buffer. This data will not be authenticated if the server-side TLS peer is expecting client certificate authentication, and is indistinguishable from valid TLS stream data. Data is limited in size to the amount that will fit in the buffer. (The TLS connection cannot directly be used for data exfiltration because the vulnerable code path requires that the connection be closed on initialization of the SSLSocket.)

Remediation

There is no fixed version for Debian:11 python3.9.

References

low severity

Improper Input Validation

  • Vulnerable module: python3.9/libpython3.9-minimal
  • Introduced through: python3.9/libpython3.9-minimal@3.9.2-1 and python3.9/python3.9-minimal@3.9.2-1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre python3.9/libpython3.9-minimal@3.9.2-1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre python3.9/python3.9-minimal@3.9.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.9 package and not the python3.9 package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

The email module of Python through 3.11.3 incorrectly parses e-mail addresses that contain a special character. The wrong portion of an RFC2822 header is identified as the value of the addr-spec. In some applications, an attacker can bypass a protection mechanism in which application access is granted only after verifying receipt of e-mail to a specific domain (e.g., only @company.example.com addresses may be used for signup). This occurs in email/_parseaddr.py in recent versions of Python.

Remediation

There is no fixed version for Debian:11 python3.9.

References

low severity

Unchecked Return Value

  • Vulnerable module: python3.9/libpython3.9-minimal
  • Introduced through: python3.9/libpython3.9-minimal@3.9.2-1 and python3.9/python3.9-minimal@3.9.2-1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre python3.9/libpython3.9-minimal@3.9.2-1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre python3.9/python3.9-minimal@3.9.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.9 package and not the python3.9 package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

A flaw was found in Python, specifically in the FTP (File Transfer Protocol) client library in PASV (passive) mode. The issue is how the FTP client trusts the host from the PASV response by default. This flaw allows an attacker to set up a malicious FTP server that can trick FTP clients into connecting back to a given IP address and port. This vulnerability could lead to FTP client scanning ports, which otherwise would not have been possible.

Remediation

There is no fixed version for Debian:11 python3.9.

References

low severity

Improper Validation of Integrity Check Value

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@247.3-7 and systemd/libudev1@247.3-7

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre systemd/libsystemd0@247.3-7
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre systemd/libudev1@247.3-7

NVD Description

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

An issue was discovered in systemd 253. An attacker can modify a sealed log file such that, in some views, not all existing and sealed log messages are displayed. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability."

Remediation

There is no fixed version for Debian:11 systemd.

References

low severity

Improper Validation of Integrity Check Value

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@247.3-7 and systemd/libudev1@247.3-7

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre systemd/libsystemd0@247.3-7
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre systemd/libudev1@247.3-7

NVD Description

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

An issue was discovered in systemd 253. An attacker can truncate a sealed log file and then resume log sealing such that checking the integrity shows no error, despite modifications. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability."

Remediation

There is no fixed version for Debian:11 systemd.

References

low severity

Improper Validation of Integrity Check Value

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@247.3-7 and systemd/libudev1@247.3-7

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre systemd/libsystemd0@247.3-7
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre systemd/libudev1@247.3-7

NVD Description

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

An issue was discovered in systemd 253. An attacker can modify the contents of past events in a sealed log file and then adjust the file such that checking the integrity shows no error, despite modifications. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability."

Remediation

There is no fixed version for Debian:11 systemd.

References

low severity

Cryptographic Issues

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1n-0+deb11u3 and openssl/libssl1.1@1.1.1n-0+deb11u3

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre openssl@1.1.1n-0+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre openssl/libssl1.1@1.1.1n-0+deb11u3

NVD Description

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

OpenSSL 0.9.8i on the Gaisler Research LEON3 SoC on the Xilinx Virtex-II Pro FPGA uses a Fixed Width Exponentiation (FWE) algorithm for certain signature calculations, and does not verify the signature before providing it to a caller, which makes it easier for physically proximate attackers to determine the private key via a modified supply voltage for the microprocessor, related to a "fault-based attack."

Remediation

There is no fixed version for Debian:11 openssl.

References

low severity

CVE-2023-4039

  • Vulnerable module: gcc-10/gcc-10-base
  • Introduced through: gcc-10/gcc-10-base@10.2.1-6, gcc-10/libgcc-s1@10.2.1-6 and others

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre gcc-10/gcc-10-base@10.2.1-6
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre gcc-10/libgcc-s1@10.2.1-6
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre gcc-10/libstdc++6@10.2.1-6

NVD Description

Note: Versions mentioned in the description apply only to the upstream gcc-10 package and not the gcc-10 package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

DISPUTEDA failure in the -fstack-protector feature in GCC-based toolchains that target AArch64 allows an attacker to exploit an existing buffer overflow in dynamically-sized local variables in your application without this being detected. This stack-protector failure only applies to C99-style dynamically-sized local variables or those created using alloca(). The stack-protector operates as intended for statically-sized local variables.

The default behavior when the stack-protector detects an overflow is to terminate your application, resulting in controlled loss of availability. An attacker who can exploit a buffer overflow without triggering the stack-protector might be able to change program flow control to cause an uncontrolled loss of availability or to go further and affect confidentiality or integrity. NOTE: The GCC project argues that this is a missed hardening bug and not a vulnerability by itself.

Remediation

There is no fixed version for Debian:11 gcc-10.

References

low severity

CVE-2023-4039

  • Vulnerable module: gcc-9/gcc-9-base
  • Introduced through: gcc-9/gcc-9-base@9.3.0-22

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre gcc-9/gcc-9-base@9.3.0-22

NVD Description

Note: Versions mentioned in the description apply only to the upstream gcc-9 package and not the gcc-9 package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

DISPUTEDA failure in the -fstack-protector feature in GCC-based toolchains that target AArch64 allows an attacker to exploit an existing buffer overflow in dynamically-sized local variables in your application without this being detected. This stack-protector failure only applies to C99-style dynamically-sized local variables or those created using alloca(). The stack-protector operates as intended for statically-sized local variables.

The default behavior when the stack-protector detects an overflow is to terminate your application, resulting in controlled loss of availability. An attacker who can exploit a buffer overflow without triggering the stack-protector might be able to change program flow control to cause an uncontrolled loss of availability or to go further and affect confidentiality or integrity. NOTE: The GCC project argues that this is a missed hardening bug and not a vulnerability by itself.

Remediation

There is no fixed version for Debian:11 gcc-9.

References

low severity

Race Condition

  • Vulnerable module: coreutils/coreutils
  • Introduced through: coreutils/coreutils@8.32-4+b1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre coreutils/coreutils@8.32-4+b1

NVD Description

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

In GNU Coreutils through 8.29, chown-core.c in chown and chgrp does not prevent replacement of a plain file with a symlink during use of the POSIX "-R -L" options, which allows local users to modify the ownership of arbitrary files by leveraging a race condition.

Remediation

There is no fixed version for Debian:11 coreutils.

References

low severity

Time-of-check Time-of-use (TOCTOU)

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.8.1-1 and shadow/passwd@1:4.8.1-1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre shadow/login@1:4.8.1-1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre shadow/passwd@1:4.8.1-1

NVD Description

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

shadow: TOCTOU (time-of-check time-of-use) race condition when copying and removing directory trees

Remediation

There is no fixed version for Debian:11 shadow.

References

low severity

Link Following

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@247.3-7 and systemd/libudev1@247.3-7

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre systemd/libsystemd0@247.3-7
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre systemd/libudev1@247.3-7

NVD Description

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

systemd, when updating file permissions, allows local users to change the permissions and SELinux security contexts for arbitrary files via a symlink attack on unspecified files.

Remediation

There is no fixed version for Debian:11 systemd.

References

low severity

Resource Management Errors

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.31-13+deb11u3, glibc/libc-l10n@2.31-13+deb11u3 and others

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/libc-bin@2.31-13+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/libc-l10n@2.31-13+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/libc6@2.31-13+deb11u3
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre glibc/locales@2.31-13+deb11u3

NVD Description

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

The glob implementation in the GNU C Library (aka glibc or libc6) allows remote authenticated users to cause a denial of service (CPU and memory consumption) via crafted glob expressions that do not match any pathnames, as demonstrated by glob expressions in STAT commands to an FTP daemon, a different vulnerability than CVE-2010-2632.

Remediation

There is no fixed version for Debian:11 glibc.

References

low severity

Improper Input Validation

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.7.1-5+deb11u1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre gnutls28/libgnutls30@3.7.1-5+deb11u1

NVD Description

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

The SSL protocol, as used in certain configurations in Microsoft Windows and Microsoft Internet Explorer, Mozilla Firefox, Google Chrome, Opera, and other products, encrypts data by using CBC mode with chained initialization vectors, which allows man-in-the-middle attackers to obtain plaintext HTTP headers via a blockwise chosen-boundary attack (BCBA) on an HTTPS session, in conjunction with JavaScript code that uses (1) the HTML5 WebSocket API, (2) the Java URLConnection API, or (3) the Silverlight WebClient API, aka a "BEAST" attack.

Remediation

There is no fixed version for Debian:11 gnutls28.

References

low severity

Improper Verification of Cryptographic Signature

  • Vulnerable module: apt
  • Introduced through: apt@2.2.4 and apt/libapt-pkg6.0@2.2.4

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre apt@2.2.4
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre apt/libapt-pkg6.0@2.2.4

NVD Description

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

It was found that apt-key in apt, all versions, do not correctly validate gpg keys with the master keyring, leading to a potential man-in-the-middle attack.

Remediation

There is no fixed version for Debian:11 apt.

References

low severity

Out-of-bounds Write

  • Vulnerable module: gnupg2/dirmngr
  • Introduced through: gnupg2/dirmngr@2.2.27-2+deb11u2, gnupg2/gpg-agent@2.2.27-2+deb11u2 and others

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre gnupg2/dirmngr@2.2.27-2+deb11u2
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre gnupg2/gpg-agent@2.2.27-2+deb11u2
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre gnupg2/gpgv@2.2.27-2+deb11u2

NVD Description

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

GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB.

Remediation

There is no fixed version for Debian:11 gnupg2.

References

low severity

Out-of-bounds Read

  • Vulnerable module: libsepol/libsepol1
  • Introduced through: libsepol/libsepol1@3.1-1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre libsepol/libsepol1@3.1-1

NVD Description

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

The CIL compiler in SELinux 3.2 has a heap-based buffer over-read in ebitmap_match_any (called indirectly from cil_check_neverallow). This occurs because there is sometimes a lack of checks for invalid statements in an optional block.

Remediation

There is no fixed version for Debian:11 libsepol.

References

low severity

Use After Free

  • Vulnerable module: libsepol/libsepol1
  • Introduced through: libsepol/libsepol1@3.1-1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre libsepol/libsepol1@3.1-1

NVD Description

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

The CIL compiler in SELinux 3.2 has a use-after-free in __cil_verify_classperms (called from __verify_map_perm_classperms and hashtab_map).

Remediation

There is no fixed version for Debian:11 libsepol.

References

low severity

Use After Free

  • Vulnerable module: libsepol/libsepol1
  • Introduced through: libsepol/libsepol1@3.1-1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre libsepol/libsepol1@3.1-1

NVD Description

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

The CIL compiler in SELinux 3.2 has a use-after-free in __cil_verify_classperms (called from __cil_verify_classpermission and __cil_pre_verify_helper).

Remediation

There is no fixed version for Debian:11 libsepol.

References

low severity

Use After Free

  • Vulnerable module: libsepol/libsepol1
  • Introduced through: libsepol/libsepol1@3.1-1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre libsepol/libsepol1@3.1-1

NVD Description

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

The CIL compiler in SELinux 3.2 has a use-after-free in cil_reset_classpermission (called from cil_reset_classperms_set and cil_reset_classperms_list).

Remediation

There is no fixed version for Debian:11 libsepol.

References

low severity

Arbitrary Code Injection

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.8.1-1 and shadow/passwd@1:4.8.1-1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre shadow/login@1:4.8.1-1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre shadow/passwd@1:4.8.1-1

NVD Description

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

In Shadow 4.13, it is possible to inject control characters into fields provided to the SUID program chfn (change finger). Although it is not possible to exploit this directly (e.g., adding a new user fails because \n is in the block list), it is possible to misrepresent the /etc/passwd file when viewed. Use of \r manipulations and Unicode characters to work around blocking of the : character make it possible to give the impression that a new user has been added. In other words, an adversary may be able to convince a system administrator to take the system offline (an indirect, social-engineered denial of service) by demonstrating that "cat /etc/passwd" shows a rogue user account.

Remediation

There is no fixed version for Debian:11 shadow.

References

low severity
new

CVE-2024-28757

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.10-2+deb11u3

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre expat/libexpat1@2.2.10-2+deb11u3

NVD Description

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

libexpat through 2.6.1 allows an XML Entity Expansion attack when there is isolated use of external parsers (created via XML_ExternalEntityParserCreate).

Remediation

There is no fixed version for Debian:11 expat.

References

low severity
new

Information Exposure

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.7.1-5+deb11u1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre gnutls28/libgnutls30@3.7.1-5+deb11u1

NVD Description

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

A flaw was found in GnuTLS. The Minerva attack is a cryptographic vulnerability that exploits deterministic behavior in systems like GnuTLS, leading to side-channel leaks. In specific scenarios, such as when using the GNUTLS_PRIVKEY_FLAG_REPRODUCIBLE flag, it can result in a noticeable step in nonce size from 513 to 512 bits, exposing a potential timing side-channel.

Remediation

There is no fixed version for Debian:11 gnutls28.

References

low severity
new

Uncaught Exception

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.7.1-5+deb11u1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre gnutls28/libgnutls30@3.7.1-5+deb11u1

NVD Description

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

A flaw has been discovered in GnuTLS where an application crash can be induced when attempting to verify a specially crafted .pem bundle using the "certtool --verify-chain" command.

Remediation

There is no fixed version for Debian:11 gnutls28.

References

low severity

CVE-2024-26458

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.18.3-6+deb11u1, krb5/libk5crypto3@1.18.3-6+deb11u1 and others

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre krb5/libgssapi-krb5-2@1.18.3-6+deb11u1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre krb5/libk5crypto3@1.18.3-6+deb11u1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre krb5/libkrb5-3@1.18.3-6+deb11u1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre krb5/libkrb5support0@1.18.3-6+deb11u1

NVD Description

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

Kerberos 5 (aka krb5) 1.21.2 contains a memory leak in /krb5/src/lib/rpc/pmap_rmt.c.

Remediation

There is no fixed version for Debian:11 krb5.

References

low severity

CVE-2024-26461

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.18.3-6+deb11u1, krb5/libk5crypto3@1.18.3-6+deb11u1 and others

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre krb5/libgssapi-krb5-2@1.18.3-6+deb11u1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre krb5/libk5crypto3@1.18.3-6+deb11u1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre krb5/libkrb5-3@1.18.3-6+deb11u1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre krb5/libkrb5support0@1.18.3-6+deb11u1

NVD Description

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

Kerberos 5 (aka krb5) 1.21.2 contains a memory leak vulnerability in /krb5/src/lib/gssapi/krb5/k5sealv3.c.

Remediation

There is no fixed version for Debian:11 krb5.

References

low severity

CVE-2024-26462

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.18.3-6+deb11u1, krb5/libk5crypto3@1.18.3-6+deb11u1 and others

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre krb5/libgssapi-krb5-2@1.18.3-6+deb11u1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre krb5/libk5crypto3@1.18.3-6+deb11u1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre krb5/libkrb5-3@1.18.3-6+deb11u1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre krb5/libkrb5support0@1.18.3-6+deb11u1

NVD Description

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

Kerberos 5 (aka krb5) 1.21.2 contains a memory leak vulnerability in /krb5/src/kdc/ndr.c.

Remediation

There is no fixed version for Debian:11 krb5.

References

low severity
new

Information Exposure

  • Vulnerable module: libgcrypt20
  • Introduced through: libgcrypt20@1.8.7-6

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre libgcrypt20@1.8.7-6

NVD Description

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

A timing-based side-channel flaw was found in libgcrypt's RSA implementation. This issue may allow a remote attacker to initiate a Bleichenbacher-style attack, which can lead to the decryption of RSA ciphertexts.

Remediation

There is no fixed version for Debian:11 libgcrypt20.

References

low severity

CVE-2023-45918

  • Vulnerable module: ncurses/libtinfo6
  • Introduced through: ncurses/libtinfo6@6.2+20201114-2, ncurses/ncurses-base@6.2+20201114-2 and others

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre ncurses/libtinfo6@6.2+20201114-2
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre ncurses/ncurses-base@6.2+20201114-2
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre ncurses/ncurses-bin@6.2+20201114-2

NVD Description

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

ncurses 6.4-20230610 has a NULL pointer dereference in tgetstr in tinfo/lib_termcap.c.

Remediation

There is no fixed version for Debian:11 ncurses.

References

low severity
new

CVE-2023-6597

  • Vulnerable module: python3.9/libpython3.9-minimal
  • Introduced through: python3.9/libpython3.9-minimal@3.9.2-1 and python3.9/python3.9-minimal@3.9.2-1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre python3.9/libpython3.9-minimal@3.9.2-1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre python3.9/python3.9-minimal@3.9.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.9 package and not the python3.9 package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

An issue was found in the CPython tempfile.TemporaryDirectory class affecting versions 3.12.2, 3.11.8, 3.10.13, 3.9.18, and 3.8.18 and prior.

The tempfile.TemporaryDirectory class would dereference symlinks during cleanup of permissions-related errors. This means users which can run privileged programs are potentially able to modify permissions of files referenced by symlinks in some circumstances.

Remediation

There is no fixed version for Debian:11 python3.9.

References

low severity
new

CVE-2024-0450

  • Vulnerable module: python3.9/libpython3.9-minimal
  • Introduced through: python3.9/libpython3.9-minimal@3.9.2-1 and python3.9/python3.9-minimal@3.9.2-1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre python3.9/libpython3.9-minimal@3.9.2-1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre python3.9/python3.9-minimal@3.9.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.9 package and not the python3.9 package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

An issue was found in the CPython zipfile module affecting versions 3.12.2, 3.11.8, 3.10.13, 3.9.18, and 3.8.18 and prior.

The zipfile module is vulnerable to “quoted-overlap” zip-bombs which exploit the zip format to create a zip-bomb with a high compression ratio. The fixed versions of CPython makes the zipfile module reject zip archives which overlap entries in the archive.

Remediation

There is no fixed version for Debian:11 python3.9.

References

low severity

CVE-2023-50868

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@247.3-7 and systemd/libudev1@247.3-7

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre systemd/libsystemd0@247.3-7
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre systemd/libudev1@247.3-7

NVD Description

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

The Closest Encloser Proof aspect of the DNS protocol (in RFC 5155 when RFC 9276 guidance is skipped) allows remote attackers to cause a denial of service (CPU consumption for SHA-1 computations) via DNSSEC responses in a random subdomain attack, aka the "NSEC3" issue. The RFC 5155 specification implies that an algorithm must perform thousands of iterations of a hash function in certain situations.

Remediation

There is no fixed version for Debian:11 systemd.

References

low severity

CVE-2023-39804

  • Vulnerable module: tar
  • Introduced through: tar@1.34+dfsg-1
  • Fixed in: 1.34+dfsg-1+deb11u1

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre tar@1.34+dfsg-1

NVD Description

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

In GNU tar before 1.35, mishandled extension attributes in a PAX archive can lead to an application crash in xheader.c.

Remediation

Upgrade Debian:11 tar to version 1.34+dfsg-1+deb11u1 or higher.

References

low severity
new

CVE-2024-28085

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.36.1-8+deb11u1, util-linux/bsdutils@1:2.36.1-8+deb11u1 and others

Detailed paths

  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre util-linux@2.36.1-8+deb11u1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre util-linux/bsdutils@1:2.36.1-8+deb11u1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre util-linux/libblkid1@2.36.1-8+deb11u1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre util-linux/libmount1@2.36.1-8+deb11u1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre util-linux/libsmartcols1@2.36.1-8+deb11u1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre util-linux/libuuid1@2.36.1-8+deb11u1
  • Introduced through: azul/zulu-openjdk-debian@17.0.1-jre util-linux/mount@2.36.1-8+deb11u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream util-linux package and not the util-linux package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

wall in util-linux through 2.40, often installed with setgid tty permissions, allows escape sequences to be sent to other users' terminals through argv. (Specifically, escape sequences received from stdin are blocked, but escape sequences received from argv are not blocked.) There may be plausible scenarios where this leads to account takeover.

Remediation

There is no fixed version for Debian:11 util-linux.

References