Vulnerabilities

416 via 706 paths

Dependencies

130

Source

Group 6 Copy Created with Sketch. Docker

Target OS

debian:unstable
Test your Docker Hub image against our market leading vulnerability database Sign up for free
Severity
  • 43
  • 128
  • 125
  • 120
Status
  • 416
  • 0
  • 0

critical severity

Embedded Malicious Code

  • Vulnerable module: xz-utils
  • Introduced through: xz-utils@5.2.2-1.3 and xz-utils/liblzma5@5.2.2-1.3
  • Fixed in: 5.6.1+really5.4.5-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim xz-utils@5.2.2-1.3
  • Introduced through: tomcat@8-jre10-slim xz-utils/liblzma5@5.2.2-1.3

NVD Description

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

Malicious code was discovered in the upstream tarballs of xz, starting with version 5.6.0. Through a series of complex obfuscations, the liblzma build process extracts a prebuilt object file from a disguised test file existing in the source code, which is then used to modify specific functions in the liblzma code. This results in a modified liblzma library that can be used by any software linked against this library, intercepting and modifying the data interaction with this library.

Remediation

Upgrade Debian:unstable xz-utils to version 5.6.1+really5.4.5-1 or higher.

References

critical severity

Integer Overflow or Wraparound

  • Vulnerable module: apr/libapr1
  • Introduced through: apr/libapr1@1.6.3-3
  • Fixed in: 1.7.2-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim apr/libapr1@1.6.3-3

NVD Description

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

Integer Overflow or Wraparound vulnerability in apr_encode functions of Apache Portable Runtime (APR) allows an attacker to write beyond bounds of a buffer. This issue affects Apache Portable Runtime (APR) version 1.7.0.

Remediation

Upgrade Debian:unstable apr to version 1.7.2-1 or higher.

References

critical severity

Out-of-bounds Write

  • Vulnerable module: bzip2
  • Introduced through: bzip2@1.0.6-9 and bzip2/libbz2-1.0@1.0.6-9
  • Fixed in: 1.0.6-9.1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim bzip2@1.0.6-9
  • Introduced through: tomcat@8-jre10-slim bzip2/libbz2-1.0@1.0.6-9

NVD Description

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

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

Remediation

Upgrade Debian:unstable bzip2 to version 1.0.6-9.1 or higher.

References

critical severity

Out-of-bounds Read

  • Vulnerable module: db5.3/libdb5.3
  • Introduced through: db5.3/libdb5.3@5.3.28+dfsg1-0.2
  • Fixed in: 5.3.28+dfsg1-0.9

Detailed paths

  • Introduced through: tomcat@8-jre10-slim db5.3/libdb5.3@5.3.28+dfsg1-0.2

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:unstable 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

Upgrade Debian:unstable db5.3 to version 5.3.28+dfsg1-0.9 or higher.

References

critical severity

Directory Traversal

  • Vulnerable module: dpkg
  • Introduced through: dpkg@1.19.2
  • Fixed in: 1.21.8

Detailed paths

  • Introduced through: tomcat@8-jre10-slim dpkg@1.19.2

NVD Description

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

Dpkg::Source::Archive in dpkg, the Debian package management system, before version 1.21.8, 1.20.10, 1.19.8, 1.18.26 is prone to a directory traversal vulnerability. When extracting untrusted source packages in v2 and v3 source package formats that include a debian.tar, the in-place extraction can lead to directory traversal situations on specially crafted orig.tar and debian.tar tarballs.

Remediation

Upgrade Debian:unstable dpkg to version 1.21.8 or higher.

References

critical severity

Exposure of Resource to Wrong Sphere

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-1
  • Fixed in: 2.4.5-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim expat/libexpat1@2.2.6-1

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

xmlparse.c in Expat (aka libexpat) before 2.4.5 allows attackers to insert namespace-separator characters into namespace URIs.

Remediation

Upgrade Debian:unstable expat to version 2.4.5-1 or higher.

References

critical severity

Improper Encoding or Escaping of Output

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-1
  • Fixed in: 2.4.5-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim expat/libexpat1@2.2.6-1

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

xmltok_impl.c in Expat (aka libexpat) before 2.4.5 lacks certain validation of encoding, such as checks for whether a UTF-8 character is valid in a certain context.

Remediation

Upgrade Debian:unstable expat to version 2.4.5-1 or higher.

References

critical severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-1
  • Fixed in: 2.4.3-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim expat/libexpat1@2.2.6-1

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

addBinding in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow.

Remediation

Upgrade Debian:unstable expat to version 2.4.3-1 or higher.

References

critical severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-1
  • Fixed in: 2.4.3-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim expat/libexpat1@2.2.6-1

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

defineAttribute in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow.

Remediation

Upgrade Debian:unstable expat to version 2.4.3-1 or higher.

References

critical severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-1
  • Fixed in: 2.4.3-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim expat/libexpat1@2.2.6-1

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

build_model in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow.

Remediation

Upgrade Debian:unstable expat to version 2.4.3-1 or higher.

References

critical severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-1
  • Fixed in: 2.4.3-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim expat/libexpat1@2.2.6-1

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

Expat (aka libexpat) before 2.4.4 has a signed integer overflow in XML_GetBuffer, for configurations with a nonzero XML_CONTEXT_BYTES.

Remediation

Upgrade Debian:unstable expat to version 2.4.3-2 or higher.

References

critical severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-1
  • Fixed in: 2.4.5-1

critical severity
new

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-1
  • Fixed in: 2.6.2-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim expat/libexpat1@2.2.6-1

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

An issue was discovered in libexpat before 2.6.3. nextScaffoldPart in xmlparse.c can have an integer overflow for m_groupSize on 32-bit platforms (where UINT_MAX equals SIZE_MAX).

Remediation

Upgrade Debian:unstable expat to version 2.6.2-2 or higher.

References

critical severity
new

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-1
  • Fixed in: 2.6.2-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim expat/libexpat1@2.2.6-1

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

An issue was discovered in libexpat before 2.6.3. dtdCopy in xmlparse.c can have an integer overflow for nDefaultAtts on 32-bit platforms (where UINT_MAX equals SIZE_MAX).

Remediation

Upgrade Debian:unstable expat to version 2.6.2-2 or higher.

References

critical severity
new

XML External Entity (XXE) Injection

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-1
  • Fixed in: 2.6.2-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim expat/libexpat1@2.2.6-1

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

An issue was discovered in libexpat before 2.6.3. xmlparse.c does not reject a negative length for XML_ParseBuffer.

Remediation

Upgrade Debian:unstable expat to version 2.6.2-2 or higher.

References

critical severity

Out-of-bounds Write

  • Vulnerable module: freetype/libfreetype6
  • Introduced through: freetype/libfreetype6@2.8.1-2
  • Fixed in: 2.11.1+dfsg-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim freetype/libfreetype6@2.8.1-2

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

FreeType commit 1e2eb65048f75c64b68708efed6ce904c31f3b2f was discovered to contain a heap buffer overflow via the function sfnt_init_face.

Remediation

Upgrade Debian:unstable freetype to version 2.11.1+dfsg-2 or higher.

References

critical severity

Buffer Overflow

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.33-3

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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

The deprecated compatibility function clnt_create in the sunrpc module of the GNU C Library (aka glibc) through 2.34 copies its hostname argument on the stack without validating its length, which may result in a buffer overflow, potentially resulting in a denial of service or (if an application is not built with a stack protector enabled) arbitrary code execution.

Remediation

Upgrade Debian:unstable glibc to version 2.33-3 or higher.

References

critical severity

Buffer Overflow

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.33-3

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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

The deprecated compatibility function svcunix_create in the sunrpc module of the GNU C Library (aka glibc) through 2.34 copies its path argument on the stack without validating its length, which may result in a buffer overflow, potentially resulting in a denial of service or (if an application is not built with a stack protector enabled) arbitrary code execution.

Remediation

Upgrade Debian:unstable glibc to version 2.33-3 or higher.

References

critical severity

Out-of-bounds Read

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.28-9

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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

In the GNU C Library (aka glibc or libc6) through 2.29, proceed_next_node in posix/regexec.c has a heap-based buffer over-read via an attempted case-insensitive regular-expression match.

Remediation

Upgrade Debian:unstable glibc to version 2.28-9 or higher.

References

critical severity

Use After Free

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.32-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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

The mq_notify function in the GNU C Library (aka glibc) versions 2.32 and 2.33 has a use-after-free. It may use the notification thread attributes object (passed through its struct sigevent parameter) after it has been freed by the caller, leading to a denial of service (application crash) or possibly unspecified other impact.

Remediation

Upgrade Debian:unstable glibc to version 2.32-1 or higher.

References

critical severity

Use After Free

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.19-1+b1
  • Fixed in: 3.7.1-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim gnutls28/libgnutls30@3.5.19-1+b1

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

A flaw was found in gnutls. A use after free issue in client sending key_share extension may lead to memory corruption and other consequences.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.7.1-1 or higher.

References

critical severity

Use After Free

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.19-1+b1
  • Fixed in: 3.7.1-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim gnutls28/libgnutls30@3.5.19-1+b1

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

A flaw was found in gnutls. A use after free issue in client_send_params in lib/ext/pre_shared_key.c may lead to memory corruption and other potential consequences.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.7.1-1 or higher.

References

critical severity

Out-of-bounds Write

  • Vulnerable module: libidn2/libidn2-0
  • Introduced through: libidn2/libidn2-0@2.0.5-1
  • Fixed in: 2.2.0-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libidn2/libidn2-0@2.0.5-1

NVD Description

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

idn2_to_ascii_4i in lib/lookup.c in GNU libidn2 before 2.1.1 has a heap-based buffer overflow via a long domain string.

Remediation

Upgrade Debian:unstable libidn2 to version 2.2.0-1 or higher.

References

critical severity

Buffer Overflow

  • Vulnerable module: libx11/libx11-6
  • Introduced through: libx11/libx11-6@2:1.6.7-1 and libx11/libx11-data@2:1.6.7-1
  • Fixed in: 2:1.7.1-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libx11/libx11-6@2:1.6.7-1
  • Introduced through: tomcat@8-jre10-slim libx11/libx11-data@2:1.6.7-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:unstable relevant fixed versions and status.

LookupCol.c in X.Org X through X11R7.7 and libX11 before 1.7.1 might allow remote attackers to execute arbitrary code. The libX11 XLookupColor request (intended for server-side color lookup) contains a flaw allowing a client to send color-name requests with a name longer than the maximum size allowed by the protocol (and also longer than the maximum packet size for normal-sized packets). The user-controlled data exceeding the maximum size is then interpreted by the server as additional X protocol requests and executed, e.g., to disable X server authorization completely. For example, if the victim encounters malicious terminal control sequences for color codes, then the attacker may be able to take full control of the running graphical session.

Remediation

Upgrade Debian:unstable libx11 to version 2:1.7.1-1 or higher.

References

critical severity

Out-of-bounds Write

  • Vulnerable module: lz4/liblz4-1
  • Introduced through: lz4/liblz4-1@1.8.2-1
  • Fixed in: 1.9.3-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim lz4/liblz4-1@1.8.2-1

NVD Description

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

There's a flaw in lz4. An attacker who submits a crafted file to an application linked with lz4 may be able to trigger an integer overflow, leading to calling of memmove() on a negative size argument, causing an out-of-bounds write and/or a crash. The greatest impact of this flaw is to availability, with some potential impact to confidentiality and integrity as well.

Remediation

Upgrade Debian:unstable lz4 to version 1.9.3-2 or higher.

References

critical severity

Insufficient Verification of Data Authenticity

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.39-1
  • Fixed in: 2:3.47-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim nss/libnss3@2:3.39-1

NVD Description

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

In Network Security Services (NSS) before 3.46, several cryptographic primitives had missing length checks. In cases where the application calling the library did not perform a sanity check on the inputs it could result in a crash due to a buffer overflow.

Remediation

Upgrade Debian:unstable nss to version 2:3.47-1 or higher.

References

critical severity

Out-of-bounds Write

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.39-1
  • Fixed in: 2:3.73-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim nss/libnss3@2:3.39-1

NVD Description

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

NSS (Network Security Services) versions prior to 3.73 or 3.68.1 ESR are vulnerable to a heap overflow when handling DER-encoded DSA or RSA-PSS signatures. Applications using NSS for handling signatures encoded within CMS, S/MIME, PKCS #7, or PKCS #12 are likely to be impacted. Applications using NSS for certificate validation or other TLS, X.509, OCSP or CRL functionality may be impacted, depending on how they configure NSS. Note: This vulnerability does NOT impact Mozilla Firefox. However, email clients and PDF viewers that use NSS for signature verification, such as Thunderbird, LibreOffice, Evolution and Evince are believed to be impacted. This vulnerability affects NSS < 3.73 and NSS < 3.68.1.

Remediation

Upgrade Debian:unstable nss to version 2:3.73-1 or higher.

References

critical severity

Buffer Overflow

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

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

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

Remediation

Upgrade Debian:unstable openssl to version 1.1.1l-1 or higher.

References

critical severity

OS Command Injection

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 1.1.1o-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

The c_rehash script does not properly sanitise shell metacharacters to prevent command injection. This script is distributed by some operating systems in a manner where it is automatically executed. On such operating systems, an attacker could execute arbitrary commands with the privileges of the script. Use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool. Fixed in OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2). Fixed in OpenSSL 1.1.1o (Affected 1.1.1-1.1.1n). Fixed in OpenSSL 1.0.2ze (Affected 1.0.2-1.0.2zd).

Remediation

Upgrade Debian:unstable openssl to version 1.1.1o-1 or higher.

References

critical severity

OS Command Injection

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 3.0.4-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

In addition to the c_rehash shell command injection identified in CVE-2022-1292, further circumstances where the c_rehash script does not properly sanitise shell metacharacters to prevent command injection were found by code review. When the CVE-2022-1292 was fixed it was not discovered that there are other places in the script where the file names of certificates being hashed were possibly passed to a command executed through the shell. This script is distributed by some operating systems in a manner where it is automatically executed. On such operating systems, an attacker could execute arbitrary commands with the privileges of the script. Use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool. Fixed in OpenSSL 3.0.4 (Affected 3.0.0,3.0.1,3.0.2,3.0.3). Fixed in OpenSSL 1.1.1p (Affected 1.1.1-1.1.1o). Fixed in OpenSSL 1.0.2zf (Affected 1.0.2-1.0.2ze).

Remediation

Upgrade Debian:unstable openssl to version 3.0.4-1 or higher.

References

critical severity

Out-of-bounds Write

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 3.0.4-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

The OpenSSL 3.0.4 release introduced a serious bug in the RSA implementation for X86_64 CPUs supporting the AVX512IFMA instructions. This issue makes the RSA implementation with 2048 bit private keys incorrect on such machines and memory corruption will happen during the computation. As a consequence of the memory corruption an attacker may be able to trigger a remote code execution on the machine performing the computation. SSL/TLS servers or other servers using 2048 bit RSA private keys running on machines supporting AVX512IFMA instructions of the X86_64 architecture are affected by this issue.

Remediation

Upgrade Debian:unstable openssl to version 3.0.4-2 or higher.

References

critical severity

Out-of-Bounds

  • Vulnerable module: perl/perl-base
  • Introduced through: perl/perl-base@5.28.0-3
  • Fixed in: 5.28.1-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim perl/perl-base@5.28.0-3

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

Perl before 5.26.3 and 5.28.0 before 5.28.1 has a buffer overflow via a crafted regular expression that triggers invalid write operations.

Remediation

Upgrade Debian:unstable perl to version 5.28.1-1 or higher.

References

critical severity

Out-of-bounds Write

  • Vulnerable module: perl/perl-base
  • Introduced through: perl/perl-base@5.28.0-3
  • Fixed in: 5.28.1-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim perl/perl-base@5.28.0-3

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

Perl before 5.26.3 and 5.28.x before 5.28.1 has a buffer overflow via a crafted regular expression that triggers invalid write operations.

Remediation

Upgrade Debian:unstable perl to version 5.28.1-1 or higher.

References

critical severity

Out-of-Bounds

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1
  • Fixed in: 3.32.0-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim sqlite3/libsqlite3-0@3.25.3-1

NVD Description

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

In SQLite 3.31.1, there is an out of bounds access problem through ALTER TABLE for views that have a nested FROM clause.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.32.0-1 or higher.

References

critical severity

Out-of-bounds Read

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1
  • Fixed in: 3.27.2-3

Detailed paths

  • Introduced through: tomcat@8-jre10-slim sqlite3/libsqlite3-0@3.25.3-1

NVD Description

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

Upgrade Debian:unstable sqlite3 to version 3.27.2-3 or higher.

References

critical severity

Use After Free

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@239-11 and systemd/libudev1@239-11
  • Fixed in: 240-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim systemd/libsystemd0@239-11
  • Introduced through: tomcat@8-jre10-slim systemd/libudev1@239-11

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

A use-after-free vulnerability was found in systemd. This issue occurs due to the on_stream_io() function and dns_stream_complete() function in 'resolved-dns-stream.c' not incrementing the reference counting for the DnsStream object. Therefore, other functions and callbacks called can dereference the DNSStream object, causing the use-after-free when the reference is still used later.

Remediation

Upgrade Debian:unstable systemd to version 240-1 or higher.

References

critical severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: tomcat@8-jre10-slim zlib/zlib1g@1:1.2.11.dfsg-1

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:unstable 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

Upgrade Debian:unstable zlib to version 1:1.3.dfsg-2 or higher.

References

critical severity

Out-of-bounds Write

  • Vulnerable module: zlib/zlib1g
  • Introduced through: zlib/zlib1g@1:1.2.11.dfsg-1
  • Fixed in: 1:1.2.11.dfsg-4.1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim zlib/zlib1g@1:1.2.11.dfsg-1

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:unstable 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:unstable zlib to version 1:1.2.11.dfsg-4.1 or higher.

References

critical severity

Integer Overflow or Wraparound

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.31-13

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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

The wordexp function in the GNU C Library (aka glibc) through 2.33 may crash or read arbitrary memory in parse_param (in posix/wordexp.c) when called with an untrusted, crafted pattern, potentially resulting in a denial of service or disclosure of information. This occurs because atoi was used but strtoul should have been used to ensure correct calculations.

Remediation

Upgrade Debian:unstable glibc to version 2.31-13 or higher.

References

critical severity

CVE-2024-37371

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.16.1-1, krb5/libk5crypto3@1.16.1-1 and others
  • Fixed in: 1.21.3-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim krb5/libgssapi-krb5-2@1.16.1-1
  • Introduced through: tomcat@8-jre10-slim krb5/libk5crypto3@1.16.1-1
  • Introduced through: tomcat@8-jre10-slim krb5/libkrb5-3@1.16.1-1
  • Introduced through: tomcat@8-jre10-slim krb5/libkrb5support0@1.16.1-1

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

In MIT Kerberos 5 (aka krb5) before 1.21.3, an attacker can cause invalid memory reads during GSS message token handling by sending message tokens with invalid length fields.

Remediation

Upgrade Debian:unstable krb5 to version 1.21.3-1 or higher.

References

critical severity

Out-of-bounds Read

  • Vulnerable module: libbsd/libbsd0
  • Introduced through: libbsd/libbsd0@0.9.1-1
  • Fixed in: 0.10.0-1

critical severity

Off-by-one Error

  • Vulnerable module: libtasn1-6
  • Introduced through: libtasn1-6@4.13-3
  • Fixed in: 4.19.0-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libtasn1-6@4.13-3

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:unstable 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:unstable libtasn1-6 to version 4.19.0-2 or higher.

References

critical severity

Out-of-bounds Read

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.39-1
  • Fixed in: 2:3.55-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim nss/libnss3@2:3.39-1

NVD Description

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

A flaw was found in the way CHACHA20-POLY1305 was implemented in NSS in versions before 3.55. When using multi-part Chacha20, it could cause out-of-bounds reads. This issue was fixed by explicitly disabling multi-part ChaCha20 (which was not functioning correctly) and strictly enforcing tag length. The highest threat from this vulnerability is to confidentiality and system availability.

Remediation

Upgrade Debian:unstable nss to version 2:3.55-1 or higher.

References

high severity

Buffer Overflow

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.8-5
  • Fixed in: 2.2.12-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim cups/libcups2@2.2.8-5

NVD Description

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

A buffer overflow issue was addressed with improved memory handling. This issue is fixed in macOS Mojave 10.14.6, Security Update 2019-004 High Sierra, Security Update 2019-004 Sierra. An attacker in a privileged network position may be able to execute arbitrary code.

Remediation

Upgrade Debian:unstable cups to version 2.2.12-1 or higher.

References

high severity

Buffer Overflow

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.8-5
  • Fixed in: 2.2.12-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim cups/libcups2@2.2.8-5

NVD Description

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

A buffer overflow issue was addressed with improved memory handling. This issue is fixed in macOS Mojave 10.14.6, Security Update 2019-004 High Sierra, Security Update 2019-004 Sierra. An attacker in a privileged network position may be able to execute arbitrary code.

Remediation

Upgrade Debian:unstable cups to version 2.2.12-1 or higher.

References

high severity

Incorrect Calculation

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-1
  • Fixed in: 2.4.3-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim expat/libexpat1@2.2.6-1

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

In Expat (aka libexpat) before 2.4.3, a left shift by 29 (or more) places in the storeAtts function in xmlparse.c can lead to realloc misbehavior (e.g., allocating too few bytes, or only freeing memory).

Remediation

Upgrade Debian:unstable expat to version 2.4.3-1 or higher.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-1
  • Fixed in: 2.4.3-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim expat/libexpat1@2.2.6-1

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

lookup in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow.

Remediation

Upgrade Debian:unstable expat to version 2.4.3-1 or higher.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-1
  • Fixed in: 2.4.3-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim expat/libexpat1@2.2.6-1

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

storeAtts in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow.

Remediation

Upgrade Debian:unstable expat to version 2.4.3-1 or higher.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-1
  • Fixed in: 2.4.3-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim expat/libexpat1@2.2.6-1

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

nextScaffoldPart in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow.

Remediation

Upgrade Debian:unstable expat to version 2.4.3-1 or higher.

References

high severity

Cross-site Request Forgery (CSRF)

  • Vulnerable module: gnupg2/gpgv
  • Introduced through: gnupg2/gpgv@2.2.10-3
  • Fixed in: 2.2.12-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim gnupg2/gpgv@2.2.10-3

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

GnuPG version 2.1.12 - 2.2.11 contains a Cross ite Request Forgery (CSRF) vulnerability in dirmngr that can result in Attacker controlled CSRF, Information Disclosure, DoS. This attack appear to be exploitable via Victim must perform a WKD request, e.g. enter an email address in the composer window of Thunderbird/Enigmail. This vulnerability appears to have been fixed in after commit 4a4bb874f63741026bd26264c43bb32b1099f060.

Remediation

Upgrade Debian:unstable gnupg2 to version 2.2.12-1 or higher.

References

high severity

Improper Input Validation

  • Vulnerable module: gzip
  • Introduced through: gzip@1.9-2.1
  • Fixed in: 1.12-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim gzip@1.9-2.1

NVD Description

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

An arbitrary file write vulnerability was found in GNU gzip's zgrep utility. When zgrep is applied on the attacker's chosen file name (for example, a crafted file name), this can overwrite an attacker's content to an arbitrary attacker-selected file. This flaw occurs due to insufficient validation when processing filenames with two or more newlines where selected content and the target file names are embedded in crafted multi-line file names. This flaw allows a remote, low privileged attacker to force zgrep to write arbitrary files on the system.

Remediation

Upgrade Debian:unstable gzip to version 1.12-1 or higher.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.16.1-1, krb5/libk5crypto3@1.16.1-1 and others
  • Fixed in: 1.20.1-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim krb5/libgssapi-krb5-2@1.16.1-1
  • Introduced through: tomcat@8-jre10-slim krb5/libk5crypto3@1.16.1-1
  • Introduced through: tomcat@8-jre10-slim krb5/libkrb5-3@1.16.1-1
  • Introduced through: tomcat@8-jre10-slim krb5/libkrb5support0@1.16.1-1

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:unstable 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:unstable krb5 to version 1.20.1-1 or higher.

References

high severity

CVE-2023-0767

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.39-1
  • Fixed in: 2:3.87.1-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim nss/libnss3@2:3.39-1

NVD Description

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

An attacker could construct a PKCS 12 cert bundle in such a way that could allow for arbitrary memory writes via PKCS 12 Safe Bag attributes being mishandled. This vulnerability affects Firefox < 110, Thunderbird < 102.8, and Firefox ESR < 102.8.

Remediation

Upgrade Debian:unstable nss to version 2:3.87.1-1 or higher.

References

high severity

CVE-2024-6609

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.39-1
  • Fixed in: 2:3.101-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim nss/libnss3@2:3.39-1

NVD Description

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

When almost out-of-memory an elliptic curve key which was never allocated could have been freed again. This vulnerability affects Firefox < 128 and Thunderbird < 128.

Remediation

Upgrade Debian:unstable nss to version 2:3.101-1 or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.39-1
  • Fixed in: 2:3.47.1-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim nss/libnss3@2:3.39-1

NVD Description

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

When encrypting with a block cipher, if a call to NSC_EncryptUpdate was made with data smaller than the block size, a small out of bounds write could occur. This could have caused heap corruption and a potentially exploitable crash. This vulnerability affects Thunderbird < 68.3, Firefox ESR < 68.3, and Firefox < 71.

Remediation

Upgrade Debian:unstable nss to version 2:3.47.1-1 or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1
  • Fixed in: 3.27.2-3

Detailed paths

  • Introduced through: tomcat@8-jre10-slim sqlite3/libsqlite3-0@3.25.3-1

NVD Description

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

Integer overflow in SQLite via WebSQL in Google Chrome prior to 74.0.3729.131 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.27.2-3 or higher.

References

high severity

Improper Input Validation

  • Vulnerable module: xz-utils
  • Introduced through: xz-utils@5.2.2-1.3 and xz-utils/liblzma5@5.2.2-1.3
  • Fixed in: 5.2.5-2.1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim xz-utils@5.2.2-1.3
  • Introduced through: tomcat@8-jre10-slim xz-utils/liblzma5@5.2.2-1.3

NVD Description

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

An arbitrary file write vulnerability was found in GNU gzip's zgrep utility. When zgrep is applied on the attacker's chosen file name (for example, a crafted file name), this can overwrite an attacker's content to an arbitrary attacker-selected file. This flaw occurs due to insufficient validation when processing filenames with two or more newlines where selected content and the target file names are embedded in crafted multi-line file names. This flaw allows a remote, low privileged attacker to force zgrep to write arbitrary files on the system.

Remediation

Upgrade Debian:unstable xz-utils to version 5.2.5-2.1 or higher.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: perl/perl-base
  • Introduced through: perl/perl-base@5.28.0-3
  • Fixed in: 5.30.3-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim perl/perl-base@5.28.0-3

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

Perl before 5.30.3 has an integer overflow related to mishandling of a "PL_regkind[OP(n)] == NOTHING" situation. A crafted regular expression could lead to malformed bytecode with a possibility of instruction injection.

Remediation

Upgrade Debian:unstable perl to version 5.30.3-1 or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: perl/perl-base
  • Introduced through: perl/perl-base@5.28.0-3
  • Fixed in: 5.30.3-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim perl/perl-base@5.28.0-3

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

Perl before 5.30.3 on 32-bit platforms allows a heap-based buffer overflow because nested regular expression quantifiers have an integer overflow.

Remediation

Upgrade Debian:unstable perl to version 5.30.3-1 or higher.

References

high severity

CVE-2019-3462

  • Vulnerable module: apt
  • Introduced through: apt@1.7.0 and apt/libapt-pkg5.0@1.7.0
  • Fixed in: 1.8.0~alpha3.1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim apt@1.7.0
  • Introduced through: tomcat@8-jre10-slim apt/libapt-pkg5.0@1.7.0

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

Incorrect sanitation of the 302 redirect field in HTTP transport method of apt versions 1.4.8 and earlier can lead to content injection by a MITM attacker, potentially leading to remote code execution on the target machine.

Remediation

Upgrade Debian:unstable apt to version 1.8.0~alpha3.1 or higher.

References

high severity

Use After Free

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-1
  • Fixed in: 2.4.8-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim expat/libexpat1@2.2.6-1

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:unstable 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:unstable expat to version 2.4.8-2 or higher.

References

high severity

Out-of-bounds Read

  • Vulnerable module: libjpeg-turbo/libjpeg62-turbo
  • Introduced through: libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+b1
  • Fixed in: 1:2.0.5-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+b1

NVD Description

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

libjpeg-turbo 2.0.4, and mozjpeg 4.0.0, has a heap-based buffer over-read in get_rgb_row() in rdppm.c via a malformed PPM input file.

Remediation

Upgrade Debian:unstable libjpeg-turbo to version 1:2.0.5-1 or higher.

References

high severity

Race Condition

  • Vulnerable module: libzstd/libzstd1
  • Introduced through: libzstd/libzstd1@1.3.5+dfsg-1
  • Fixed in: 1.3.8+dfsg-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libzstd/libzstd1@1.3.5+dfsg-1

NVD Description

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

A race condition in the one-pass compression functions of Zstandard prior to version 1.3.8 could allow an attacker to write bytes out of bounds if an output buffer smaller than the recommended size was used.

Remediation

Upgrade Debian:unstable libzstd to version 1.3.8+dfsg-2 or higher.

References

high severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: nettle/libhogweed4
  • Introduced through: nettle/libhogweed4@3.4-1 and nettle/libnettle6@3.4-1
  • Fixed in: 3.7.2-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim nettle/libhogweed4@3.4-1
  • Introduced through: tomcat@8-jre10-slim nettle/libnettle6@3.4-1

NVD Description

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

A flaw was found in Nettle in versions before 3.7.2, where several Nettle signature verification functions (GOST DSA, EDDSA & ECDSA) result in the Elliptic Curve Cryptography point (ECC) multiply function being called with out-of-range scalers, possibly resulting in incorrect results. This flaw allows an attacker to force an invalid signature, causing an assertion failure or possible validation. The highest threat to this vulnerability is to confidentiality, integrity, as well as system availability.

Remediation

Upgrade Debian:unstable nettle to version 3.7.2-1 or higher.

References

high severity

Improper Certificate Validation

  • Vulnerable module: perl/perl-base
  • Introduced through: perl/perl-base@5.28.0-3
  • Fixed in: 5.38.2-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim perl/perl-base@5.28.0-3

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

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

Remediation

Upgrade Debian:unstable perl to version 5.38.2-2 or higher.

References

high severity

Use After Free

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1
  • Fixed in: 3.27.2-3

Detailed paths

  • Introduced through: tomcat@8-jre10-slim sqlite3/libsqlite3-0@3.25.3-1

NVD Description

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

An exploitable use after free vulnerability exists in the window function functionality of Sqlite3 3.26.0. A specially crafted SQL command can cause a use after free vulnerability, potentially resulting in remote code execution. An attacker can send a malicious SQL command to trigger this vulnerability.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.27.2-3 or higher.

References

high severity

Link Following

  • Vulnerable module: avahi/libavahi-client3
  • Introduced through: avahi/libavahi-client3@0.7-4+b1, avahi/libavahi-common-data@0.7-4+b1 and others
  • Fixed in: 0.8-4

Detailed paths

  • Introduced through: tomcat@8-jre10-slim avahi/libavahi-client3@0.7-4+b1
  • Introduced through: tomcat@8-jre10-slim avahi/libavahi-common-data@0.7-4+b1
  • Introduced through: tomcat@8-jre10-slim avahi/libavahi-common3@0.7-4+b1

NVD Description

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

avahi-daemon-check-dns.sh in the Debian avahi package through 0.8-4 is executed as root via /etc/network/if-up.d/avahi-daemon, and allows a local attacker to cause a denial of service or create arbitrary empty files via a symlink attack on files under /run/avahi-daemon. NOTE: this only affects the packaging for Debian GNU/Linux (used indirectly by SUSE), not the upstream Avahi product.

Remediation

Upgrade Debian:unstable avahi to version 0.8-4 or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: bash
  • Introduced through: bash@4.4.18-3.1
  • Fixed in: 5.2-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim bash@4.4.18-3.1

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:unstable 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

Upgrade Debian:unstable bash to version 5.2-1 or higher.

References

high severity

Out-of-Bounds

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.8-5
  • Fixed in: 2.3.1-12

Detailed paths

  • Introduced through: tomcat@8-jre10-slim cups/libcups2@2.2.8-5

NVD Description

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

A memory corruption issue was addressed with improved validation. This issue is fixed in macOS Catalina 10.15.4. An application may be able to gain elevated privileges.

Remediation

Upgrade Debian:unstable cups to version 2.3.1-12 or higher.

References

high severity

Use After Free

  • Vulnerable module: dbus/libdbus-1-3
  • Introduced through: dbus/libdbus-1-3@1.12.10-1
  • Fixed in: 1.12.20-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim dbus/libdbus-1-3@1.12.10-1

NVD Description

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

A use-after-free flaw was found in D-Bus Development branch <= 1.13.16, dbus-1.12.x stable branch <= 1.12.18, and dbus-1.10.x and older branches <= 1.10.30 when a system has multiple usernames sharing the same UID. When a set of policy rules references these usernames, D-Bus may free some memory in the heap, which is still used by data structures necessary for the other usernames sharing the UID, possibly leading to a crash or other undefined behaviors

Remediation

Upgrade Debian:unstable dbus to version 1.12.20-1 or higher.

References

high severity

Out-of-bounds Read

  • Vulnerable module: e2fsprogs
  • Introduced through: e2fsprogs@1.44.4-2, e2fsprogs/libcom-err2@1.44.4-2 and others
  • Fixed in: 1.46.6~rc1-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim e2fsprogs@1.44.4-2
  • Introduced through: tomcat@8-jre10-slim e2fsprogs/libcom-err2@1.44.4-2
  • Introduced through: tomcat@8-jre10-slim e2fsprogs/libext2fs2@1.44.4-2
  • Introduced through: tomcat@8-jre10-slim e2fsprogs/libss2@1.44.4-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:unstable 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

Upgrade Debian:unstable e2fsprogs to version 1.46.6~rc1-1 or higher.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-1
  • Fixed in: 2.4.3-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim expat/libexpat1@2.2.6-1

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

In doProlog in xmlparse.c in Expat (aka libexpat) before 2.4.3, an integer overflow exists for m_groupSize.

Remediation

Upgrade Debian:unstable expat to version 2.4.3-1 or higher.

References

high severity

Off-by-one Error

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.33-4

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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:unstable 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:unstable glibc to version 2.33-4 or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.37-12

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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:unstable 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:unstable glibc to version 2.37-12 or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.37-15

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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

A heap-based buffer overflow was found in the __vsyslog_internal function of the glibc library. This function is called by the syslog and vsyslog functions. This issue occurs when the openlog function was not called, or called with the ident argument set to NULL, and the program name (the basename of argv[0]) is bigger than 1024 bytes, resulting in an application crash or local privilege escalation. This issue affects glibc 2.36 and newer.

Remediation

Upgrade Debian:unstable glibc to version 2.37-15 or higher.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: libx11/libx11-6
  • Introduced through: libx11/libx11-6@2:1.6.7-1 and libx11/libx11-data@2:1.6.7-1
  • Fixed in: 2:1.8.7-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libx11/libx11-6@2:1.6.7-1
  • Introduced through: tomcat@8-jre10-slim libx11/libx11-data@2:1.6.7-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:unstable 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:unstable libx11 to version 2:1.8.7-1 or higher.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: libx11/libx11-6
  • Introduced through: libx11/libx11-6@2:1.6.7-1 and libx11/libx11-data@2:1.6.7-1
  • Fixed in: 2:1.6.12-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libx11/libx11-6@2:1.6.7-1
  • Introduced through: tomcat@8-jre10-slim libx11/libx11-data@2:1.6.7-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:unstable relevant fixed versions and status.

An integer overflow vulnerability leading to a double-free was found in libX11. This flaw allows a local privileged attacker to cause an application compiled with libX11 to crash, or in some cases, result in arbitrary code execution. The highest threat from this flaw is to confidentiality, integrity as well as system availability.

Remediation

Upgrade Debian:unstable libx11 to version 2:1.6.12-1 or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: ncurses/libncursesw6
  • Introduced through: ncurses/libncursesw6@6.1+20181013-1, ncurses/libtinfo6@6.1+20181013-1 and others
  • Fixed in: 6.4-3

Detailed paths

  • Introduced through: tomcat@8-jre10-slim ncurses/libncursesw6@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/libtinfo6@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/ncurses-base@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/ncurses-bin@6.1+20181013-1

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:unstable 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:unstable ncurses to version 6.4-3 or higher.

References

high severity

Improper Verification of Cryptographic Signature

high severity

Out-of-bounds Write

  • Vulnerable module: perl/perl-base
  • Introduced through: perl/perl-base@5.28.0-3
  • Fixed in: 5.36.0-10

Detailed paths

  • Introduced through: tomcat@8-jre10-slim perl/perl-base@5.28.0-3

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

A vulnerability was found in perl 5.30.0 through 5.38.0. 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:unstable perl to version 5.36.0-10 or higher.

References

high severity

Untrusted Search Path

  • Vulnerable module: perl/perl-base
  • Introduced through: perl/perl-base@5.28.0-3
  • Fixed in: 5.32.1-5

Detailed paths

  • Introduced through: tomcat@8-jre10-slim perl/perl-base@5.28.0-3

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

Encode.pm, as distributed in Perl through 5.34.0, allows local users to gain privileges via a Trojan horse Encode::ConfigLocal library (in the current working directory) that preempts dynamic module loading. Exploitation requires an unusual configuration, and certain 2021 versions of Encode.pm (3.05 through 3.11). This issue occurs because the || operator evaluates @INC in a scalar context, and thus @INC has only an integer value.

Remediation

Upgrade Debian:unstable perl to version 5.32.1-5 or higher.

References

high severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@239-11 and systemd/libudev1@239-11
  • Fixed in: 240-4

Detailed paths

  • Introduced through: tomcat@8-jre10-slim systemd/libsystemd0@239-11
  • Introduced through: tomcat@8-jre10-slim systemd/libudev1@239-11

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

An allocation of memory without limits, that could result in the stack clashing with another memory region, was discovered in systemd-journald when a program with long command line arguments calls syslog. A local attacker may use this flaw to crash systemd-journald or escalate his privileges. Versions through v240 are vulnerable.

Remediation

Upgrade Debian:unstable systemd to version 240-4 or higher.

References

high severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@239-11 and systemd/libudev1@239-11
  • Fixed in: 240-4

Detailed paths

  • Introduced through: tomcat@8-jre10-slim systemd/libsystemd0@239-11
  • Introduced through: tomcat@8-jre10-slim systemd/libudev1@239-11

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

An allocation of memory without limits, that could result in the stack clashing with another memory region, was discovered in systemd-journald when many entries are sent to the journal socket. A local attacker, or a remote one if systemd-journal-remote is used, may use this flaw to crash systemd-journald or execute code with journald privileges. Versions through v240 are vulnerable.

Remediation

Upgrade Debian:unstable systemd to version 240-4 or higher.

References

high severity

CVE-2023-26604

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@239-11 and systemd/libudev1@239-11
  • Fixed in: 247.1-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim systemd/libsystemd0@239-11
  • Introduced through: tomcat@8-jre10-slim systemd/libudev1@239-11

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

systemd before 247 does not adequately block local privilege escalation for some Sudo configurations, e.g., plausible sudoers files in which the "systemctl status" command may be executed. Specifically, systemd does not set LESSSECURE to 1, and thus other programs may be launched from the less program. This presents a substantial security risk when running systemctl from Sudo, because less executes as root when the terminal size is too small to show the complete systemctl output.

Remediation

Upgrade Debian:unstable systemd to version 247.1-2 or higher.

References

high severity

Deserialization of Untrusted Data

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@239-11 and systemd/libudev1@239-11
  • Fixed in: 239-12

Detailed paths

  • Introduced through: tomcat@8-jre10-slim systemd/libsystemd0@239-11
  • Introduced through: tomcat@8-jre10-slim systemd/libudev1@239-11

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

A vulnerability in unit_deserialize of systemd allows an attacker to supply arbitrary state across systemd re-execution via NotifyAccess. This can be used to improperly influence systemd execution and possibly lead to root privilege escalation. Affected releases are systemd versions up to and including 239.

Remediation

Upgrade Debian:unstable systemd to version 239-12 or higher.

References

high severity

Incorrect Privilege Assignment

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@239-11 and systemd/libudev1@239-11
  • Fixed in: 242-4

Detailed paths

  • Introduced through: tomcat@8-jre10-slim systemd/libsystemd0@239-11
  • Introduced through: tomcat@8-jre10-slim systemd/libudev1@239-11

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

It was discovered that a systemd service that uses DynamicUser property can create a SUID/SGID binary that would be allowed to run as the transient service UID/GID even after the service is terminated. A local attacker may use this flaw to access resources that will be owned by a potentially different service in the future, when the UID/GID will be recycled.

Remediation

Upgrade Debian:unstable systemd to version 242-4 or higher.

References

high severity

Privilege Chaining

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@239-11 and systemd/libudev1@239-11
  • Fixed in: 242-4

Detailed paths

  • Introduced through: tomcat@8-jre10-slim systemd/libsystemd0@239-11
  • Introduced through: tomcat@8-jre10-slim systemd/libudev1@239-11

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

It was discovered that a systemd service that uses DynamicUser property can get new privileges through the execution of SUID binaries, which would allow to create binaries owned by the service transient group with the setgid bit set. A local attacker may use this flaw to access resources that will be owned by a potentially different service in the future, when the GID will be recycled.

Remediation

Upgrade Debian:unstable systemd to version 242-4 or higher.

References

high severity

Use After Free

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@239-11 and systemd/libudev1@239-11
  • Fixed in: 244.2-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim systemd/libsystemd0@239-11
  • Introduced through: tomcat@8-jre10-slim systemd/libudev1@239-11

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

A heap use-after-free vulnerability was found in systemd before version v245-rc1, where asynchronous Polkit queries are performed while handling dbus messages. A local unprivileged attacker can abuse this flaw to crash systemd services or potentially execute code and elevate their privileges, by sending specially crafted dbus messages.

Remediation

Upgrade Debian:unstable systemd to version 244.2-1 or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: unzip
  • Introduced through: unzip@6.0-21
  • Fixed in: 6.0-22

Detailed paths

  • Introduced through: tomcat@8-jre10-slim unzip@6.0-21

NVD Description

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

A heap-based buffer overflow exists in Info-Zip UnZip version <= 6.00 in the processing of password-protected archives that allows an attacker to perform a denial of service or to possibly achieve code execution.

Remediation

Upgrade Debian:unstable unzip to version 6.0-22 or higher.

References

high severity

Buffer Overflow

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 3.0.7-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed the malicious certificate or for the application to continue certificate verification despite failure to construct a path to a trusted issuer. An attacker can craft a malicious email address to overflow four attacker-controlled bytes on the stack. This buffer overflow could result in a crash (causing a denial of service) or potentially remote code execution.

In a TLS client, this can be triggered by connecting to a malicious server.

In a TLS server, this can be triggered if the server requests client authentication and a malicious client connects.

Note: Pre-announcements of CVE-2022-3602 described this issue as CRITICAL. Further analysis based on some of the mitigating factors described above have led this to be downgraded to HIGH. Users are still encouraged to upgrade to a new version as soon as possible.

Remediation

Upgrade Debian:unstable openssl to version 3.0.7-1 or higher.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-1
  • Fixed in: 2.4.3-3

high severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-1
  • Fixed in: 2.4.5-1

high severity

Out-of-bounds Read

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-1
  • Fixed in: 2.2.7-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim expat/libexpat1@2.2.6-1

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

In libexpat before 2.2.8, crafted XML input could fool the parser into changing from DTD parsing to document parsing too early; a consecutive call to XML_GetCurrentLineNumber (or XML_GetCurrentColumnNumber) then resulted in a heap-based buffer over-read.

Remediation

Upgrade Debian:unstable expat to version 2.2.7-2 or higher.

References

high severity

Resource Exhaustion

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-1
  • Fixed in: 2.6.0-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim expat/libexpat1@2.2.6-1

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:unstable 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

Upgrade Debian:unstable expat to version 2.6.0-1 or higher.

References

high severity

Use After Free

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-1
  • Fixed in: 2.5.0-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim expat/libexpat1@2.2.6-1

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:unstable 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:unstable expat to version 2.5.0-1 or higher.

References

high severity

XML External Entity (XXE) Injection

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-1
  • Fixed in: 2.2.6-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim expat/libexpat1@2.2.6-1

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

In libexpat in Expat before 2.2.7, XML input including XML names that contain a large number of colons could make the XML parser consume a high amount of RAM and CPU resources while processing (enough to be usable for denial-of-service attacks).

Remediation

Upgrade Debian:unstable expat to version 2.2.6-2 or higher.

References

high severity

Out-of-bounds Read

  • Vulnerable module: freetype/libfreetype6
  • Introduced through: freetype/libfreetype6@2.8.1-2
  • Fixed in: 2.11.1+dfsg-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim freetype/libfreetype6@2.8.1-2

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

FreeType commit 53dfdcd8198d2b3201a23c4bad9190519ba918db was discovered to contain a segmentation violation via the function FNT_Size_Request.

Remediation

Upgrade Debian:unstable freetype to version 2.11.1+dfsg-2 or higher.

References

high severity

Out-of-bounds Read

  • Vulnerable module: freetype/libfreetype6
  • Introduced through: freetype/libfreetype6@2.8.1-2
  • Fixed in: 2.11.1+dfsg-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim freetype/libfreetype6@2.8.1-2

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

FreeType commit 22a0cccb4d9d002f33c1ba7a4b36812c7d4f46b5 was discovered to contain a segmentation violation via the function FT_Request_Size.

Remediation

Upgrade Debian:unstable freetype to version 2.11.1+dfsg-2 or higher.

References

high severity

Improper Data Handling

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.28-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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

In the GNU C Library (aka glibc or libc6) before 2.28, parse_reg_exp in posix/regcomp.c misparses alternatives, which allows attackers to cause a denial of service (assertion failure and application exit) or trigger an incorrect result by attempting a regular-expression match.

Remediation

Upgrade Debian:unstable glibc to version 2.28-1 or higher.

References

high severity

Improper Input Validation

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.28-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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

In the GNU C Library (aka glibc or libc6) through 2.28, attempting to resolve a crafted hostname via getaddrinfo() leads to the allocation of a socket descriptor that is not closed. This is related to the if_nametoindex() function.

Remediation

Upgrade Debian:unstable glibc to version 2.28-1 or higher.

References

high severity

Memory Leak

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.37-11

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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

A flaw was found in the GNU C Library. A recent fix for CVE-2023-4806 introduced the potential for a memory leak, which may result in an application crash.

Remediation

Upgrade Debian:unstable glibc to version 2.37-11 or higher.

References

high severity

Out-of-bounds Read

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.33-4

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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

A flaw was found in glibc. The realpath() function can mistakenly return an unexpected value, potentially leading to information leakage and disclosure of sensitive data.

Remediation

Upgrade Debian:unstable glibc to version 2.33-4 or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.37-15

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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

An off-by-one heap-based buffer overflow was found in the __vsyslog_internal function of the glibc library. This function is called by the syslog and vsyslog functions. This issue occurs when these functions are called with a message bigger than INT_MAX bytes, leading to an incorrect calculation of the buffer size to store the message, resulting in an application crash. This issue affects glibc 2.37 and newer.

Remediation

Upgrade Debian:unstable glibc to version 2.37-15 or higher.

References

high severity

Reachable Assertion

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.31-10

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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

The iconv function in the GNU C Library (aka glibc or libc6) 2.32 and earlier, when processing invalid input sequences in the ISO-2022-JP-3 encoding, fails an assertion in the code path and aborts the program, potentially resulting in a denial of service.

Remediation

Upgrade Debian:unstable glibc to version 2.31-10 or higher.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: gmp/libgmp10
  • Introduced through: gmp/libgmp10@2:6.1.2+dfsg-3
  • Fixed in: 2:6.2.1+dfsg-3

Detailed paths

  • Introduced through: tomcat@8-jre10-slim gmp/libgmp10@2:6.1.2+dfsg-3

NVD Description

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

GNU Multiple Precision Arithmetic Library (GMP) through 6.2.1 has an mpz/inp_raw.c integer overflow and resultant buffer overflow via crafted input, leading to a segmentation fault on 32-bit platforms.

Remediation

Upgrade Debian:unstable gmp to version 2:6.2.1+dfsg-3 or higher.

References

high severity

Access of Uninitialized Pointer

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.19-1+b1
  • Fixed in: 3.6.7-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim gnutls28/libgnutls30@3.5.19-1+b1

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

It was discovered in gnutls before version 3.6.7 upstream that there is an uninitialized pointer access in gnutls versions 3.6.3 or later which can be triggered by certain post-handshake messages.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.6.7-2 or higher.

References

high severity

Double Free

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.19-1+b1
  • Fixed in: 3.7.7-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim gnutls28/libgnutls30@3.5.19-1+b1

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:unstable 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:unstable gnutls28 to version 3.7.7-1 or higher.

References

high severity

Double Free

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.19-1+b1
  • Fixed in: 3.6.7-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim gnutls28/libgnutls30@3.5.19-1+b1

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

A vulnerability was found in gnutls versions from 3.5.8 before 3.6.7. A memory corruption (double free) vulnerability in the certificate verification API. Any client or server application that verifies X.509 certificates with GnuTLS 3.5.8 or later is affected.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.6.7-2 or higher.

References

high severity

Improper Verification of Cryptographic Signature

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.19-1+b1
  • Fixed in: 3.8.3-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim gnutls28/libgnutls30@3.5.19-1+b1

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:unstable 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

Upgrade Debian:unstable gnutls28 to version 3.8.3-1 or higher.

References

high severity

Information Exposure

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.19-1+b1
  • Fixed in: 3.8.3-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim gnutls28/libgnutls30@3.5.19-1+b1

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:unstable 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

Upgrade Debian:unstable gnutls28 to version 3.8.3-1 or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.19-1+b1
  • Fixed in: 3.6.15-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim gnutls28/libgnutls30@3.5.19-1+b1

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

An issue was discovered in GnuTLS before 3.6.15. A server can trigger a NULL pointer dereference in a TLS 1.3 client if a no_renegotiation alert is sent with unexpected timing, and then an invalid second handshake occurs. The crash happens in the application's error handling path, where the gnutls_deinit function is called after detecting a handshake failure.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.6.15-1 or higher.

References

high severity

CVE-2024-37370

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.16.1-1, krb5/libk5crypto3@1.16.1-1 and others
  • Fixed in: 1.21.3-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim krb5/libgssapi-krb5-2@1.16.1-1
  • Introduced through: tomcat@8-jre10-slim krb5/libk5crypto3@1.16.1-1
  • Introduced through: tomcat@8-jre10-slim krb5/libkrb5-3@1.16.1-1
  • Introduced through: tomcat@8-jre10-slim krb5/libkrb5support0@1.16.1-1

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

In MIT Kerberos 5 (aka krb5) before 1.21.3, an attacker can modify the plaintext Extra Count field of a confidential GSS krb5 wrap token, causing the unwrapped token to appear truncated to the application.

Remediation

Upgrade Debian:unstable krb5 to version 1.21.3-1 or higher.

References

high severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: tomcat@8-jre10-slim krb5/libgssapi-krb5-2@1.16.1-1
  • Introduced through: tomcat@8-jre10-slim krb5/libk5crypto3@1.16.1-1
  • Introduced through: tomcat@8-jre10-slim krb5/libkrb5-3@1.16.1-1
  • Introduced through: tomcat@8-jre10-slim krb5/libkrb5support0@1.16.1-1

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

ec_verify in kdc/kdc_preauth_ec.c in the Key Distribution Center (KDC) in MIT Kerberos 5 (aka krb5) before 1.18.4 and 1.19.x before 1.19.2 allows remote attackers to cause a NULL pointer dereference and daemon crash. This occurs because a return value is not properly managed in a certain situation.

Remediation

Upgrade Debian:unstable krb5 to version 1.18.3-6 or higher.

References

high severity

Uncontrolled Recursion

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.16.1-1, krb5/libk5crypto3@1.16.1-1 and others
  • Fixed in: 1.18.3-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim krb5/libgssapi-krb5-2@1.16.1-1
  • Introduced through: tomcat@8-jre10-slim krb5/libk5crypto3@1.16.1-1
  • Introduced through: tomcat@8-jre10-slim krb5/libkrb5-3@1.16.1-1
  • Introduced through: tomcat@8-jre10-slim krb5/libkrb5support0@1.16.1-1

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

MIT Kerberos 5 (aka krb5) before 1.17.2 and 1.18.x before 1.18.3 allows unbounded recursion via an ASN.1-encoded Kerberos message because the lib/krb5/asn.1/asn1_encode.c support for BER indefinite lengths lacks a recursion limit.

Remediation

Upgrade Debian:unstable krb5 to version 1.18.3-1 or higher.

References

high severity

Information Exposure

  • Vulnerable module: libgcrypt20
  • Introduced through: libgcrypt20@1.8.4-3
  • Fixed in: 1.9.4-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libgcrypt20@1.8.4-3

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:unstable 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

Upgrade Debian:unstable libgcrypt20 to version 1.9.4-2 or higher.

References

high severity

Improper Input Validation

  • Vulnerable module: libidn2/libidn2-0
  • Introduced through: libidn2/libidn2-0@2.0.5-1
  • Fixed in: 2.2.0-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libidn2/libidn2-0@2.0.5-1

NVD Description

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

GNU libidn2 before 2.2.0 fails to perform the roundtrip checks specified in RFC3490 Section 4.2 when converting A-labels to U-labels. This makes it possible in some circumstances for one domain to impersonate another. By creating a malicious domain that matches a target domain except for the inclusion of certain punycoded Unicode characters (that would be discarded when converted first to a Unicode label and then back to an ASCII label), arbitrary domains can be impersonated.

Remediation

Upgrade Debian:unstable libidn2 to version 2.2.0-1 or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: libx11/libx11-6
  • Introduced through: libx11/libx11-6@2:1.6.7-1 and libx11/libx11-data@2:1.6.7-1
  • Fixed in: 2:1.8.6-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libx11/libx11-6@2:1.6.7-1
  • Introduced through: tomcat@8-jre10-slim libx11/libx11-data@2:1.6.7-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:unstable 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:unstable libx11 to version 2:1.8.6-1 or higher.

References

high severity

Resource Exhaustion

  • Vulnerable module: libzstd/libzstd1
  • Introduced through: libzstd/libzstd1@1.3.5+dfsg-1
  • Fixed in: 1.5.4+dfsg2-1

high severity

Improper Input Validation

  • Vulnerable module: nettle/libhogweed4
  • Introduced through: nettle/libhogweed4@3.4-1 and nettle/libnettle6@3.4-1
  • Fixed in: 3.7.3-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim nettle/libhogweed4@3.4-1
  • Introduced through: tomcat@8-jre10-slim nettle/libnettle6@3.4-1

NVD Description

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

A flaw was found in the way nettle's RSA decryption functions handled specially crafted ciphertext. An attacker could use this flaw to provide a manipulated ciphertext leading to application crash and denial of service.

Remediation

Upgrade Debian:unstable nettle to version 3.7.3-1 or higher.

References

high severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.39-1
  • Fixed in: 2:3.58-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim nss/libnss3@2:3.39-1

NVD Description

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

A flaw was found in the way NSS handled CCS (ChangeCipherSpec) messages in TLS 1.3. This flaw allows a remote attacker to send multiple CCS messages, causing a denial of service for servers compiled with the NSS library. The highest threat from this vulnerability is to system availability. This flaw affects NSS versions before 3.58.

Remediation

Upgrade Debian:unstable nss to version 2:3.58-1 or higher.

References

high severity

CVE-2022-3479

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.39-1
  • Fixed in: 2:3.87-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim nss/libnss3@2:3.39-1

NVD Description

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

A vulnerability found in nss. By this security vulnerability, nss client auth crash without a user certificate in the database and this can lead us to a segmentation fault or crash.

Remediation

Upgrade Debian:unstable nss to version 2:3.87-1 or higher.

References

high severity

Improper Certificate Validation

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.39-1
  • Fixed in: 2:3.45-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim nss/libnss3@2:3.39-1

NVD Description

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

In Network Security Services before 3.44, a malformed Netscape Certificate Sequence can cause NSS to crash, resulting in a denial of service.

Remediation

Upgrade Debian:unstable nss to version 2:3.45-1 or higher.

References

high severity

Out-of-Bounds

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.39-1
  • Fixed in: 2:3.45-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim nss/libnss3@2:3.39-1

NVD Description

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

Empty or malformed p256-ECDH public keys may trigger a segmentation fault due values being improperly sanitized before being copied into memory and used. This vulnerability affects Firefox ESR < 60.8, Firefox < 68, and Thunderbird < 60.8.

Remediation

Upgrade Debian:unstable nss to version 2:3.45-1 or higher.

References

high severity

Out-of-bounds Read

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.39-1
  • Fixed in: 2:3.45-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim nss/libnss3@2:3.39-1

NVD Description

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

When importing a curve25519 private key in PKCS#8format with leading 0x00 bytes, it is possible to trigger an out-of-bounds read in the Network Security Services (NSS) library. This could lead to information disclosure. This vulnerability affects Firefox ESR < 60.8, Firefox < 68, and Thunderbird < 60.8.

Remediation

Upgrade Debian:unstable nss to version 2:3.45-1 or higher.

References

high severity

Unchecked Return Value

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.39-1
  • Fixed in: 2:3.96.1-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim nss/libnss3@2:3.39-1

NVD Description

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

An unchecked return value in TLS handshake code could have caused a potentially exploitable crash. This vulnerability affects Firefox < 122, Firefox ESR < 115.9, and Thunderbird < 115.9.

Remediation

Upgrade Debian:unstable nss to version 2:3.96.1-1 or higher.

References

high severity

CVE-2023-5363

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 3.0.12-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

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

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

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

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

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

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

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

The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this because the issue lies outside of the FIPS provider boundary.

OpenSSL 3.1 and 3.0 are vulnerable to this issue.

Remediation

Upgrade Debian:unstable openssl to version 3.0.12-1 or higher.

References

high severity

Double Free

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 3.0.8-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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:unstable 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:unstable openssl to version 3.0.8-1 or higher.

References

high severity

Improper Certificate Validation

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 3.0.9-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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:unstable 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&#39; argument to the command line utilities or by calling the X509_VERIFY_PARAM_set1_policies()' function.

Remediation

Upgrade Debian:unstable openssl to version 3.0.9-1 or higher.

References

high severity

Improper Locking

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 3.0.7-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

If an X.509 certificate contains a malformed policy constraint and policy processing is enabled, then a write lock will be taken twice recursively. On some operating systems (most widely: Windows) this results in a denial of service when the affected process hangs. Policy processing being enabled on a publicly facing server is not considered to be a common setup.

Policy processing is enabled by passing the -policy&#39; argument to the command line utilities or by calling the X509_VERIFY_PARAM_set1_policies()' function.

Update (31 March 2023): The description of the policy processing enablement was corrected based on CVE-2023-0466.

Remediation

Upgrade Debian:unstable openssl to version 3.0.7-2 or higher.

References

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

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

Remediation

Upgrade Debian:unstable openssl to version 1.1.1j-1 or higher.

References

high severity

Loop with Unreachable Exit Condition ('Infinite Loop')

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

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

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

Remediation

Upgrade Debian:unstable openssl to version 1.1.1n-1 or higher.

References

high severity

NULL Pointer Dereference

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 3.0.7-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

OpenSSL supports creating a custom cipher via the legacy EVP_CIPHER_meth_new() function and associated function calls. This function was deprecated in OpenSSL 3.0 and application authors are instead encouraged to use the new provider mechanism in order to implement custom ciphers. OpenSSL versions 3.0.0 to 3.0.5 incorrectly handle legacy custom ciphers passed to the EVP_EncryptInit_ex2(), EVP_DecryptInit_ex2() and EVP_CipherInit_ex2() functions (as well as other similarly named encryption and decryption initialisation functions). Instead of using the custom cipher directly it incorrectly tries to fetch an equivalent cipher from the available providers. An equivalent cipher is found based on the NID passed to EVP_CIPHER_meth_new(). This NID is supposed to represent the unique NID for a given cipher. However it is possible for an application to incorrectly pass NID_undef as this value in the call to EVP_CIPHER_meth_new(). When NID_undef is used in this way the OpenSSL encryption/decryption initialisation function will match the NULL cipher as being equivalent and will fetch this from the available providers. This will succeed if the default provider has been loaded (or if a third party provider has been loaded that offers this cipher). Using the NULL cipher means that the plaintext is emitted as the ciphertext. Applications are only affected by this issue if they call EVP_CIPHER_meth_new() using NID_undef and subsequently use it in a call to an encryption/decryption initialisation function. Applications that only use SSL/TLS are not impacted by this issue. Fixed in OpenSSL 3.0.6 (Affected 3.0.0-3.0.5).

Remediation

Upgrade Debian:unstable openssl to version 3.0.7-1 or higher.

References

high severity

NULL Pointer Dereference

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 3.0.8-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

An invalid pointer dereference on read can be triggered when an application tries to load malformed PKCS7 data with the d2i_PKCS7(), d2i_PKCS7_bio() or d2i_PKCS7_fp() functions.

The result of the dereference is an application crash which could lead to a denial of service attack. The TLS implementation in OpenSSL does not call this function however third party applications might call these functions on untrusted data.

Remediation

Upgrade Debian:unstable openssl to version 3.0.8-1 or higher.

References

high severity

NULL Pointer Dereference

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 3.0.8-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

An invalid pointer dereference on read can be triggered when an application tries to check a malformed DSA public key by the EVP_PKEY_public_check() function. This will most likely lead to an application crash. This function can be called on public keys supplied from untrusted sources which could allow an attacker to cause a denial of service attack.

The TLS implementation in OpenSSL does not call this function but applications might call the function if there are additional security requirements imposed by standards such as FIPS 140-3.

Remediation

Upgrade Debian:unstable openssl to version 3.0.8-1 or higher.

References

high severity

NULL Pointer Dereference

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 3.0.8-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

A NULL pointer can be dereferenced when signatures are being verified on PKCS7 signed or signedAndEnveloped data. In case the hash algorithm used for the signature is known to the OpenSSL library but the implementation of the hash algorithm is not available the digest initialization will fail. There is a missing check for the return value from the initialization function which later leads to invalid usage of the digest API most likely leading to a crash.

The unavailability of an algorithm can be caused by using FIPS enabled configuration of providers or more commonly by not loading the legacy provider.

PKCS7 data is processed by the SMIME library calls and also by the time stamp (TS) library calls. The TLS implementation in OpenSSL does not call these functions however third party applications would be affected if they call these functions to verify signatures on untrusted data.

Remediation

Upgrade Debian:unstable openssl to version 3.0.8-1 or higher.

References

high severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

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

Remediation

Upgrade Debian:unstable openssl to version 1.1.1g-1 or higher.

References

high severity

Use After Free

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 3.0.8-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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:unstable 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:unstable openssl to version 3.0.8-1 or higher.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: p11-kit/libp11-kit0
  • Introduced through: p11-kit/libp11-kit0@0.23.14-2
  • Fixed in: 0.23.22-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim p11-kit/libp11-kit0@0.23.14-2

NVD Description

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

An issue was discovered in p11-kit 0.21.1 through 0.23.21. Multiple integer overflows have been discovered in the array allocations in the p11-kit library and the p11-kit list command, where overflow checks are missing before calling realloc or calloc.

Remediation

Upgrade Debian:unstable p11-kit to version 0.23.22-1 or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: p11-kit/libp11-kit0
  • Introduced through: p11-kit/libp11-kit0@0.23.14-2
  • Fixed in: 0.23.22-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim p11-kit/libp11-kit0@0.23.14-2

NVD Description

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

An issue was discovered in p11-kit 0.23.6 through 0.23.21. A heap-based buffer overflow has been discovered in the RPC protocol used by p11-kit server/remote commands and the client library. When the remote entity supplies a serialized byte array in a CK_ATTRIBUTE, the receiving entity may not allocate sufficient length for the buffer to store the deserialized value.

Remediation

Upgrade Debian:unstable p11-kit to version 0.23.22-1 or higher.

References

high severity

Buffer Overflow

  • Vulnerable module: perl/perl-base
  • Introduced through: perl/perl-base@5.28.0-3
  • Fixed in: 5.30.3-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim perl/perl-base@5.28.0-3

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

regcomp.c in Perl before 5.30.3 allows a buffer overflow via a crafted regular expression because of recursive S_study_chunk calls.

Remediation

Upgrade Debian:unstable perl to version 5.30.3-1 or higher.

References

high severity

CVE-2019-19603

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1
  • Fixed in: 3.30.1+fossil191229-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim sqlite3/libsqlite3-0@3.25.3-1

NVD Description

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

SQLite 3.30.1 mishandles certain SELECT statements with a nonexistent VIEW, leading to an application crash.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.30.1+fossil191229-1 or higher.

References

high severity

CVE-2019-19959

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1
  • Fixed in: 3.30.1+fossil191229-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim sqlite3/libsqlite3-0@3.25.3-1

NVD Description

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

ext/misc/zipfile.c in SQLite 3.30.1 mishandles certain uses of INSERT INTO in situations involving embedded '\0' characters in filenames, leading to a memory-management error that can be detected by (for example) valgrind.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.30.1+fossil191229-1 or higher.

References

high severity

Improper Handling of Exceptional Conditions

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1
  • Fixed in: 3.30.1+fossil191229-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim sqlite3/libsqlite3-0@3.25.3-1

NVD Description

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

selectExpander in select.c in SQLite 3.30.1 proceeds with WITH stack unwinding even after a parsing error.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.30.1+fossil191229-1 or higher.

References

high severity

Improper Initialization

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1
  • Fixed in: 3.31.1-5

Detailed paths

  • Introduced through: tomcat@8-jre10-slim sqlite3/libsqlite3-0@3.25.3-1

NVD Description

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

SQLite through 3.31.1 allows attackers to cause a denial of service (segmentation fault) via a malformed window-function query because the AggInfo object's initialization is mishandled.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.31.1-5 or higher.

References

high severity

NULL Pointer Dereference

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1
  • Fixed in: 3.32.0-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim sqlite3/libsqlite3-0@3.25.3-1

NVD Description

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

In SQlite 3.31.1, a potential null pointer derreference was found in the INTERSEC query processing.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.32.0-1 or higher.

References

high severity

NULL Pointer Dereference

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1
  • Fixed in: 3.30.1+fossil191229-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim sqlite3/libsqlite3-0@3.25.3-1

NVD Description

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

exprListAppendList in window.c in SQLite 3.30.1 allows attackers to trigger an invalid pointer dereference because constant integer values in ORDER BY clauses of window definitions are mishandled.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.30.1+fossil191229-1 or higher.

References

high severity

NULL Pointer Dereference

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1
  • Fixed in: 3.30.1+fossil191229-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim sqlite3/libsqlite3-0@3.25.3-1

NVD Description

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

flattenSubquery in select.c in SQLite 3.30.1 mishandles certain uses of SELECT DISTINCT involving a LEFT JOIN in which the right-hand side is a view. This can cause a NULL pointer dereference (or incorrect results).

Remediation

Upgrade Debian:unstable sqlite3 to version 3.30.1+fossil191229-1 or higher.

References

high severity

NULL Pointer Dereference

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1
  • Fixed in: 3.31.1-3

Detailed paths

  • Introduced through: tomcat@8-jre10-slim sqlite3/libsqlite3-0@3.25.3-1

NVD Description

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

In SQLite 3.31.1, isAuxiliaryVtabOperator allows attackers to trigger a NULL pointer dereference and segmentation fault because of generated column optimizations.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.31.1-3 or higher.

References

high severity

Out-of-bounds Read

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1
  • Fixed in: 3.36.0-2

high severity

Unrestricted Upload of File with Dangerous Type

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1
  • Fixed in: 3.30.1+fossil191229-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim sqlite3/libsqlite3-0@3.25.3-1

NVD Description

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

zipfileUpdate in ext/misc/zipfile.c in SQLite 3.30.1 mishandles a NULL pathname during an update of a ZIP archive.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.30.1+fossil191229-1 or higher.

References

high severity

Use After Free

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1
  • Fixed in: 3.32.2-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim sqlite3/libsqlite3-0@3.25.3-1

NVD Description

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

SQLite 3.32.2 has a use-after-free in resetAccumulator in select.c because the parse tree rewrite for window functions is too late.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.32.2-2 or higher.

References

high severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@239-11 and systemd/libudev1@239-11
  • Fixed in: 255.4-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim systemd/libsystemd0@239-11
  • Introduced through: tomcat@8-jre10-slim systemd/libudev1@239-11

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:unstable 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

Upgrade Debian:unstable systemd to version 255.4-1 or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: zlib/zlib1g
  • Introduced through: zlib/zlib1g@1:1.2.11.dfsg-1
  • Fixed in: 1:1.2.11.dfsg-4

Detailed paths

  • Introduced through: tomcat@8-jre10-slim zlib/zlib1g@1:1.2.11.dfsg-1

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

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

Remediation

Upgrade Debian:unstable zlib to version 1:1.2.11.dfsg-4 or higher.

References

high severity

Information Exposure

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.19-1+b1
  • Fixed in: 3.7.8-5

Detailed paths

  • Introduced through: tomcat@8-jre10-slim gnutls28/libgnutls30@3.5.19-1+b1

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:unstable 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:unstable gnutls28 to version 3.7.8-5 or higher.

References

high severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.19-1+b1
  • Fixed in: 3.6.13-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim gnutls28/libgnutls30@3.5.19-1+b1

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

GnuTLS 3.6.x before 3.6.13 uses incorrect cryptography for DTLS. The earliest affected version is 3.6.3 (2018-07-16) because of an error in a 2017-10-06 commit. The DTLS client always uses 32 '\0' bytes instead of a random value, and thus contributes no randomness to a DTLS negotiation. This breaks the security guarantees of the DTLS protocol.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.6.13-2 or higher.

References

high severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.19-1+b1
  • Fixed in: 3.6.14-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim gnutls28/libgnutls30@3.5.19-1+b1

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

GnuTLS 3.6.x before 3.6.14 uses incorrect cryptography for encrypting a session ticket (a loss of confidentiality in TLS 1.2, and an authentication bypass in TLS 1.3). The earliest affected version is 3.6.4 (2018-09-24) because of an error in a 2018-09-18 commit. Until the first key rotation, the TLS server always uses wrong data in place of an encryption key derived from an application.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.6.14-1 or higher.

References

high severity

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

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 3.0.8-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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:unstable 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:unstable openssl to version 3.0.8-1 or higher.

References

high severity

Improper Certificate Validation

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

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

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

Remediation

Upgrade Debian:unstable openssl to version 1.1.1k-1 or higher.

References

high severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

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

Remediation

Upgrade Debian:unstable openssl to version 1.1.1l-1 or higher.

References

high severity

CVE-2022-46908

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1
  • Fixed in: 3.40.0-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim sqlite3/libsqlite3-0@3.25.3-1

NVD Description

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

SQLite through 3.40.0, when relying on --safe for execution of an untrusted CLI script, does not properly implement the azProhibitedFunctions protection mechanism, and instead allows UDF functions such as WRITEFILE.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.40.0-2 or higher.

References

high severity

Out-of-Bounds

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1
  • Fixed in: 3.43.1-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim sqlite3/libsqlite3-0@3.25.3-1

NVD Description

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

A vulnerability was found in SQLite SQLite3 up to 3.43.0 and classified as critical. This issue affects the function sessionReadRecord of the file ext/session/sqlite3session.c of the component make alltest Handler. The manipulation leads to heap-based buffer overflow. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-248999.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.43.1-1 or higher.

References

high severity

Out-of-bounds Read

  • Vulnerable module: apr/libapr1
  • Introduced through: apr/libapr1@1.6.3-3
  • Fixed in: 1.7.0-7

Detailed paths

  • Introduced through: tomcat@8-jre10-slim apr/libapr1@1.6.3-3

NVD Description

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

An out-of-bounds array read in the apr_time_exp*() functions was fixed in the Apache Portable Runtime 1.6.3 release (CVE-2017-12613). The fix for this issue was not carried forward to the APR 1.7.x branch, and hence version 1.7.0 regressed compared to 1.6.3 and is vulnerable to the same issue.

Remediation

Upgrade Debian:unstable apr to version 1.7.0-7 or higher.

References

high severity

Use After Free

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.8-5
  • Fixed in: 2.4.2-5

Detailed paths

  • Introduced through: tomcat@8-jre10-slim cups/libcups2@2.2.8-5

NVD Description

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

OpenPrinting CUPS is a standards-based, open source printing system for Linux and other Unix-like operating systems. Starting in version 2.0.0 and prior to version 2.4.6, CUPS logs data of free memory to the logging service AFTER the connection has been closed, when it should have logged the data right before. This is a use-after-free bug that impacts the entire cupsd process.

The exact cause of this issue is the function httpClose(con-&gt;http) being called in scheduler/client.c. The problem is that httpClose always, provided its argument is not null, frees the pointer at the end of the call, only for cupsdLogClient to pass the pointer to httpGetHostname. This issue happens in function cupsdAcceptClient if LogLevel is warn or higher and in two scenarios: there is a double-lookup for the IP Address (HostNameLookups Double is set in cupsd.conf) which fails to resolve, or if CUPS is compiled with TCP wrappers and the connection is refused by rules from /etc/hosts.allow and /etc/hosts.deny.

Version 2.4.6 has a patch for this issue.

Remediation

Upgrade Debian:unstable cups to version 2.4.2-5 or higher.

References

high severity

Link Following

  • Vulnerable module: dbus/libdbus-1-3
  • Introduced through: dbus/libdbus-1-3@1.12.10-1
  • Fixed in: 1.12.16-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim dbus/libdbus-1-3@1.12.10-1

NVD Description

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

dbus before 1.10.28, 1.12.x before 1.12.16, and 1.13.x before 1.13.12, as used in DBusServer in Canonical Upstart in Ubuntu 14.04 (and in some, less common, uses of dbus-daemon), allows cookie spoofing because of symlink mishandling in the reference implementation of DBUS_COOKIE_SHA1 in the libdbus library. (This only affects the DBUS_COOKIE_SHA1 authentication mechanism.) A malicious client with write access to its own home directory could manipulate a ~/.dbus-keyrings symlink to cause a DBusServer with a different uid to read and write in unintended locations. In the worst case, this could result in the DBusServer reusing a cookie that is known to the malicious client, and treating that cookie as evidence that a subsequent client connection came from an attacker-chosen uid, allowing authentication bypass.

Remediation

Upgrade Debian:unstable dbus to version 1.12.16-1 or higher.

References

high severity

Out-of-bounds Read

  • Vulnerable module: ncurses/libncursesw6
  • Introduced through: ncurses/libncursesw6@6.1+20181013-1, ncurses/libtinfo6@6.1+20181013-1 and others
  • Fixed in: 6.3+20220423-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim ncurses/libncursesw6@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/libtinfo6@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/ncurses-base@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/ncurses-bin@6.1+20181013-1

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:unstable 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:unstable ncurses to version 6.3+20220423-1 or higher.

References

high severity

Buffer Overflow

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 3.0.7-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed the malicious certificate or for the application to continue certificate verification despite failure to construct a path to a trusted issuer.

An attacker can craft a malicious email address to overflow an arbitrary number of bytes containing the . character (decimal 46) on the stack. This buffer overflow could result in a crash (causing a denial of service).

Remediation

Upgrade Debian:unstable openssl to version 3.0.7-1 or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.8-5
  • Fixed in: 2.4.2-6

Detailed paths

  • Introduced through: tomcat@8-jre10-slim cups/libcups2@2.2.8-5

NVD Description

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

Due to failure in validating the length provided by an attacker-crafted PPD PostScript document, CUPS and libppd are susceptible to a heap-based buffer overflow and possibly code execution. This issue has been fixed in CUPS version 2.4.7, released in September of 2023.

Remediation

Upgrade Debian:unstable cups to version 2.4.2-6 or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.30-3

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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

An out-of-bounds write vulnerability was found in glibc before 2.31 when handling signal trampolines on PowerPC. Specifically, the backtrace function did not properly check the array bounds when storing the frame address, resulting in a denial of service or potential code execution. The highest threat from this vulnerability is to system availability.

Remediation

Upgrade Debian:unstable glibc to version 2.30-3 or higher.

References

high severity

Use After Free

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.30-3

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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

A use-after-free vulnerability introduced in glibc upstream version 2.14 was found in the way the tilde expansion was carried out. Directory paths containing an initial tilde followed by a valid username were affected by this issue. A local attacker could exploit this flaw by creating a specially crafted path that, when processed by the glob function, would potentially lead to arbitrary code execution. This was fixed in version 2.32.

Remediation

Upgrade Debian:unstable glibc to version 2.30-3 or higher.

References

high severity

Use After Free

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1
  • Fixed in: 3.32.0-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim sqlite3/libsqlite3-0@3.25.3-1

NVD Description

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

ext/fts3/fts3.c in SQLite before 3.32.0 has a use-after-free in fts3EvalNextRow, related to the snippet feature.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.32.0-1 or higher.

References

high severity

Improper Authorization

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@239-11 and systemd/libudev1@239-11
  • Fixed in: 241-3

Detailed paths

  • Introduced through: tomcat@8-jre10-slim systemd/libsystemd0@239-11
  • Introduced through: tomcat@8-jre10-slim systemd/libudev1@239-11

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

In systemd before v242-rc4, it was discovered that pam_systemd does not properly sanitize the environment before using the XDG_SEAT variable. It is possible for an attacker, in some particular configurations, to set a XDG_SEAT environment variable which allows for commands to be checked against polkit policies using the "allow_active" element rather than "allow_any".

Remediation

Upgrade Debian:unstable systemd to version 241-3 or higher.

References

medium severity

Insufficient Comparison

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.8-5
  • Fixed in: 2.4.2-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim cups/libcups2@2.2.8-5

NVD Description

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

A logic issue was addressed with improved state management. This issue is fixed in Security Update 2022-003 Catalina, macOS Monterey 12.3, macOS Big Sur 11.6.5. An application may be able to gain elevated privileges.

Remediation

Upgrade Debian:unstable cups to version 2.4.2-1 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: e2fsprogs
  • Introduced through: e2fsprogs@1.44.4-2, e2fsprogs/libcom-err2@1.44.4-2 and others
  • Fixed in: 1.45.4-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim e2fsprogs@1.44.4-2
  • Introduced through: tomcat@8-jre10-slim e2fsprogs/libcom-err2@1.44.4-2
  • Introduced through: tomcat@8-jre10-slim e2fsprogs/libext2fs2@1.44.4-2
  • Introduced through: tomcat@8-jre10-slim e2fsprogs/libss2@1.44.4-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:unstable relevant fixed versions and status.

An exploitable code execution vulnerability exists in the quota file functionality of E2fsprogs 1.45.3. A specially crafted ext4 partition can cause an out-of-bounds write on the heap, resulting in code execution. An attacker can corrupt a partition to trigger this vulnerability.

Remediation

Upgrade Debian:unstable e2fsprogs to version 1.45.4-1 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: e2fsprogs
  • Introduced through: e2fsprogs@1.44.4-2, e2fsprogs/libcom-err2@1.44.4-2 and others
  • Fixed in: 1.45.5-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim e2fsprogs@1.44.4-2
  • Introduced through: tomcat@8-jre10-slim e2fsprogs/libcom-err2@1.44.4-2
  • Introduced through: tomcat@8-jre10-slim e2fsprogs/libext2fs2@1.44.4-2
  • Introduced through: tomcat@8-jre10-slim e2fsprogs/libss2@1.44.4-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:unstable relevant fixed versions and status.

A code execution vulnerability exists in the directory rehashing functionality of E2fsprogs e2fsck 1.45.4. A specially crafted ext4 directory can cause an out-of-bounds write on the stack, resulting in code execution. An attacker can corrupt a partition to trigger this vulnerability.

Remediation

Upgrade Debian:unstable e2fsprogs to version 1.45.5-1 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: libx11/libx11-6
  • Introduced through: libx11/libx11-6@2:1.6.7-1 and libx11/libx11-data@2:1.6.7-1
  • Fixed in: 2:1.6.10-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libx11/libx11-6@2:1.6.7-1
  • Introduced through: tomcat@8-jre10-slim libx11/libx11-data@2:1.6.7-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:unstable relevant fixed versions and status.

An integer overflow leading to a heap-buffer overflow was found in The X Input Method (XIM) client was implemented in libX11 before version 1.6.10. As per upstream this is security relevant when setuid programs call XIM client functions while running with elevated privileges. No such programs are shipped with Red Hat Enterprise Linux.

Remediation

Upgrade Debian:unstable libx11 to version 2:1.6.10-1 or higher.

References

medium severity

CVE-2022-42012

  • Vulnerable module: dbus/libdbus-1-3
  • Introduced through: dbus/libdbus-1-3@1.12.10-1
  • Fixed in: 1.14.4-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim dbus/libdbus-1-3@1.12.10-1

NVD Description

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

An issue was discovered in D-Bus before 1.12.24, 1.13.x and 1.14.x before 1.14.4, and 1.15.x before 1.15.2. An authenticated attacker can cause dbus-daemon and other programs that use libdbus to crash by sending a message with attached file descriptors in an unexpected format.

Remediation

Upgrade Debian:unstable dbus to version 1.14.4-1 or higher.

References

medium severity

CVE-2023-34969

  • Vulnerable module: dbus/libdbus-1-3
  • Introduced through: dbus/libdbus-1-3@1.12.10-1
  • Fixed in: 1.14.8-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim dbus/libdbus-1-3@1.12.10-1

NVD Description

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

D-Bus before 1.15.6 sometimes allows unprivileged users to crash dbus-daemon. If a privileged user with control over the dbus-daemon is using the org.freedesktop.DBus.Monitoring interface to monitor message bus traffic, then an unprivileged user with the ability to connect to the same dbus-daemon can cause a dbus-daemon crash under some circumstances via an unreplyable message. When done on the well-known system bus, this is a denial-of-service vulnerability. The fixed versions are 1.12.28, 1.14.8, and 1.15.6.

Remediation

Upgrade Debian:unstable dbus to version 1.14.8-1 or higher.

References

medium severity

Improper Validation of Array Index

  • Vulnerable module: dbus/libdbus-1-3
  • Introduced through: dbus/libdbus-1-3@1.12.10-1
  • Fixed in: 1.14.4-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim dbus/libdbus-1-3@1.12.10-1

NVD Description

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

An issue was discovered in D-Bus before 1.12.24, 1.13.x and 1.14.x before 1.14.4, and 1.15.x before 1.15.2. An authenticated attacker can cause dbus-daemon and other programs that use libdbus to crash when receiving a message where an array length is inconsistent with the size of the element type.

Remediation

Upgrade Debian:unstable dbus to version 1.14.4-1 or higher.

References

medium severity

Improper Verification of Cryptographic Signature

  • Vulnerable module: dbus/libdbus-1-3
  • Introduced through: dbus/libdbus-1-3@1.12.10-1
  • Fixed in: 1.14.4-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim dbus/libdbus-1-3@1.12.10-1

NVD Description

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

An issue was discovered in D-Bus before 1.12.24, 1.13.x and 1.14.x before 1.14.4, and 1.15.x before 1.15.2. An authenticated attacker can cause dbus-daemon and other programs that use libdbus to crash when receiving a message with certain invalid type signatures.

Remediation

Upgrade Debian:unstable dbus to version 1.14.4-1 or higher.

References

medium severity

Uncontrolled Recursion

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-1
  • Fixed in: 2.4.5-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim expat/libexpat1@2.2.6-1

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

In Expat (aka libexpat) before 2.4.5, an attacker can trigger stack exhaustion in build_model via a large nesting depth in the DTD element.

Remediation

Upgrade Debian:unstable expat to version 2.4.5-1 or higher.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: freetype/libfreetype6
  • Introduced through: freetype/libfreetype6@2.8.1-2
  • Fixed in: 2.9.1-3

Detailed paths

  • Introduced through: tomcat@8-jre10-slim freetype/libfreetype6@2.8.1-2

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

An issue was discovered in FreeType 2 through 2.9. A NULL pointer dereference in the Ins_GETVARIATION() function within ttinterp.c could lead to DoS via a crafted font file.

Remediation

Upgrade Debian:unstable freetype to version 2.9.1-3 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: freetype/libfreetype6
  • Introduced through: freetype/libfreetype6@2.8.1-2
  • Fixed in: 2.10.2+dfsg-4

Detailed paths

  • Introduced through: tomcat@8-jre10-slim freetype/libfreetype6@2.8.1-2

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

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

Remediation

Upgrade Debian:unstable freetype to version 2.10.2+dfsg-4 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.37-9

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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

A flaw was found in glibc. When the getaddrinfo function is called with the AF_UNSPEC address family and the system is configured with no-aaaa mode via /etc/resolv.conf, a DNS response via TCP larger than 2048 bytes can potentially disclose stack contents through the function returned address data, and may cause a crash.

Remediation

Upgrade Debian:unstable glibc to version 2.37-9 or higher.

References

medium severity

Arbitrary Code Injection

  • Vulnerable module: gnupg2/gpgv
  • Introduced through: gnupg2/gpgv@2.2.10-3
  • Fixed in: 2.2.35-3

Detailed paths

  • Introduced through: tomcat@8-jre10-slim gnupg2/gpgv@2.2.10-3

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

GnuPG through 2.3.6, in unusual situations where an attacker possesses any secret-key information from a victim's keyring and other constraints (e.g., use of GPGME) are met, allows signature forgery via injection into the status line.

Remediation

Upgrade Debian:unstable gnupg2 to version 2.2.35-3 or higher.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.19-1+b1
  • Fixed in: 3.7.3-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim gnutls28/libgnutls30@3.5.19-1+b1

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

A NULL pointer dereference flaw was found in GnuTLS. As Nettle's hash update functions internally call memcpy, providing zero-length input may cause undefined behavior. This flaw leads to a denial of service after authentication in rare circumstances.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.7.3-2 or higher.

References

medium severity

Access of Uninitialized Pointer

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.16.1-1, krb5/libk5crypto3@1.16.1-1 and others
  • Fixed in: 1.20.1-3

Detailed paths

  • Introduced through: tomcat@8-jre10-slim krb5/libgssapi-krb5-2@1.16.1-1
  • Introduced through: tomcat@8-jre10-slim krb5/libk5crypto3@1.16.1-1
  • Introduced through: tomcat@8-jre10-slim krb5/libkrb5-3@1.16.1-1
  • Introduced through: tomcat@8-jre10-slim krb5/libkrb5support0@1.16.1-1

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:unstable 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:unstable krb5 to version 1.20.1-3 or higher.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.16.1-1, krb5/libk5crypto3@1.16.1-1 and others
  • Fixed in: 1.18.3-7

Detailed paths

  • Introduced through: tomcat@8-jre10-slim krb5/libgssapi-krb5-2@1.16.1-1
  • Introduced through: tomcat@8-jre10-slim krb5/libk5crypto3@1.16.1-1
  • Introduced through: tomcat@8-jre10-slim krb5/libkrb5-3@1.16.1-1
  • Introduced through: tomcat@8-jre10-slim krb5/libkrb5support0@1.16.1-1

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

The Key Distribution Center (KDC) in MIT Kerberos 5 (aka krb5) before 1.18.5 and 1.19.x before 1.19.3 has a NULL pointer dereference in kdc/do_tgs_req.c via a FAST inner body that lacks a server field.

Remediation

Upgrade Debian:unstable krb5 to version 1.18.3-7 or higher.

References

medium severity

CVE-2023-50495

  • Vulnerable module: ncurses/libncursesw6
  • Introduced through: ncurses/libncursesw6@6.1+20181013-1, ncurses/libtinfo6@6.1+20181013-1 and others
  • Fixed in: 6.4+20230625-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim ncurses/libncursesw6@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/libtinfo6@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/ncurses-base@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/ncurses-bin@6.1+20181013-1

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

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

Remediation

Upgrade Debian:unstable ncurses to version 6.4+20230625-1 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: ncurses/libncursesw6
  • Introduced through: ncurses/libncursesw6@6.1+20181013-1, ncurses/libtinfo6@6.1+20181013-1 and others
  • Fixed in: 6.1+20191019-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim ncurses/libncursesw6@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/libtinfo6@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/ncurses-base@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/ncurses-bin@6.1+20181013-1

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

Buffer Overflow vulnerability in one_one_mapping function in progs/dump_entry.c:1373 in ncurses 6.1 allows remote attackers to cause a denial of service via crafted command.

Remediation

Upgrade Debian:unstable ncurses to version 6.1+20191019-1 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: ncurses/libncursesw6
  • Introduced through: ncurses/libncursesw6@6.1+20181013-1, ncurses/libtinfo6@6.1+20181013-1 and others
  • Fixed in: 6.1+20191019-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim ncurses/libncursesw6@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/libtinfo6@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/ncurses-base@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/ncurses-bin@6.1+20181013-1

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

Buffer Overflow vulnerability in fmt_entry function in progs/dump_entry.c:1116 in ncurses 6.1 allows remote attackers to cause a denial of service via crafted command.

Remediation

Upgrade Debian:unstable ncurses to version 6.1+20191019-1 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: ncurses/libncursesw6
  • Introduced through: ncurses/libncursesw6@6.1+20181013-1, ncurses/libtinfo6@6.1+20181013-1 and others
  • Fixed in: 6.1+20191019-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim ncurses/libncursesw6@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/libtinfo6@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/ncurses-base@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/ncurses-bin@6.1+20181013-1

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

Buffer Overflow vulnerability in _nc_find_entry in tinfo/comp_hash.c:70 in ncurses 6.1 allows remote attackers to cause a denial of service via crafted command.

Remediation

Upgrade Debian:unstable ncurses to version 6.1+20191019-1 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: ncurses/libncursesw6
  • Introduced through: ncurses/libncursesw6@6.1+20181013-1, ncurses/libtinfo6@6.1+20181013-1 and others
  • Fixed in: 6.1+20191019-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim ncurses/libncursesw6@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/libtinfo6@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/ncurses-base@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/ncurses-bin@6.1+20181013-1

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

Buffer Overflow vulnerability in _nc_find_entry function in tinfo/comp_hash.c:66 in ncurses 6.1 allows remote attackers to cause a denial of service via crafted command.

Remediation

Upgrade Debian:unstable ncurses to version 6.1+20191019-1 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: ncurses/libncursesw6
  • Introduced through: ncurses/libncursesw6@6.1+20181013-1, ncurses/libtinfo6@6.1+20181013-1 and others
  • Fixed in: 6.1+20191019-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim ncurses/libncursesw6@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/libtinfo6@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/ncurses-base@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/ncurses-bin@6.1+20181013-1

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

Buffer Overflow vulnerability in fmt_entry function in progs/dump_entry.c:1100 in ncurses 6.1 allows remote attackers to cause a denial of service via crafted command.

Remediation

Upgrade Debian:unstable ncurses to version 6.1+20191019-1 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: ncurses/libncursesw6
  • Introduced through: ncurses/libncursesw6@6.1+20181013-1, ncurses/libtinfo6@6.1+20181013-1 and others
  • Fixed in: 6.1+20191019-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim ncurses/libncursesw6@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/libtinfo6@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/ncurses-base@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/ncurses-bin@6.1+20181013-1

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

Buffer Overflow vulnerability in postprocess_terminfo function in tinfo/parse_entry.c:997 in ncurses 6.1 allows remote attackers to cause a denial of service via crafted command.

Remediation

Upgrade Debian:unstable ncurses to version 6.1+20191019-1 or higher.

References

medium severity
new

CVE-2024-7531

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.39-1
  • Fixed in: 2:3.103-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim nss/libnss3@2:3.39-1

NVD Description

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

Calling PK11_Encrypt() in NSS using CKM_CHACHA20 and the same buffer for input and output can result in plaintext on an Intel Sandy Bridge processor. In Firefox this only affects the QUIC header protection feature when the connection is using the ChaCha20-Poly1305 cipher suite. The most likely outcome is connection failure, but if the connection persists despite the high packet loss it could be possible for a network observer to identify packets as coming from the same source despite a network path change. This vulnerability affects Firefox < 129, Firefox ESR < 115.14, and Firefox ESR < 128.1.

Remediation

Upgrade Debian:unstable nss to version 2:3.103-1 or higher.

References

medium severity

Improper Authentication

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.39-1
  • Fixed in: 2:3.49-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim nss/libnss3@2:3.39-1

NVD Description

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

After a HelloRetryRequest has been sent, the client may negotiate a lower protocol that TLS 1.3, resulting in an invalid state transition in the TLS State Machine. If the client gets into this state, incoming Application Data records will be ignored. This vulnerability affects Firefox < 72.

Remediation

Upgrade Debian:unstable nss to version 2:3.49-1 or higher.

References

medium severity

Improper Certificate Validation

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.39-1
  • Fixed in: 2:3.73-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim nss/libnss3@2:3.39-1

NVD Description

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

After accepting an untrusted certificate, handling an empty pkcs7 sequence as part of the certificate data could have lead to a crash. This crash is believed to be unexploitable. This vulnerability affects Firefox ESR < 91.5, Firefox < 96, and Thunderbird < 91.5.

Remediation

Upgrade Debian:unstable nss to version 2:3.73-1 or higher.

References

medium severity

Information Exposure

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.39-1
  • Fixed in: 2:3.61-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim nss/libnss3@2:3.39-1

NVD Description

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

The NSS code used for checking PKCS#1 v1.5 was leaking information useful in mounting Bleichenbacher-like attacks. Both the overall correctness of the padding as well as the length of the encrypted message was leaking through timing side-channel. By sending large number of attacker-selected ciphertexts, the attacker would be able to decrypt a previously intercepted PKCS#1 v1.5 ciphertext (for example, to decrypt a TLS session that used RSA key exchange), or forge a signature using the victim's key. The issue was fixed by implementing the implicit rejection algorithm, in which the NSS returns a deterministic random message in case invalid padding is detected, as proposed in the Marvin Attack paper. This vulnerability affects NSS < 3.61.

Remediation

Upgrade Debian:unstable nss to version 2:3.61-1 or higher.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.39-1
  • Fixed in: 2:3.42.1-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim nss/libnss3@2:3.39-1

NVD Description

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

In Network Security Services (NSS) before 3.36.7 and before 3.41.1, a malformed signature can cause a crash due to a null dereference, resulting in a Denial of Service.

Remediation

Upgrade Debian:unstable nss to version 2:3.42.1-1 or higher.

References

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 3.0.9-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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:unstable 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:unstable openssl to version 3.0.9-1 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 3.1.5-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

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

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

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

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

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

Remediation

Upgrade Debian:unstable openssl to version 3.1.5-1 or higher.

References

medium severity

Divide By Zero

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1
  • Fixed in: 3.29.0-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim sqlite3/libsqlite3-0@3.25.3-1

NVD Description

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

In SQLite through 3.29.0, whereLoopAddBtreeIndex in sqlite3.c can crash a browser or other application because of missing validation of a sqlite_stat1 sz field, aka a "severe division by zero in the query planner."

Remediation

Upgrade Debian:unstable sqlite3 to version 3.29.0-2 or higher.

References

medium severity

Race Condition

  • Vulnerable module: libgcrypt20
  • Introduced through: libgcrypt20@1.8.4-3
  • Fixed in: 1.8.5-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libgcrypt20@1.8.4-3

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

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

Remediation

Upgrade Debian:unstable libgcrypt20 to version 1.8.5-1 or higher.

References

medium severity

Information Exposure

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.8-5
  • Fixed in: 2.2.10-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim cups/libcups2@2.2.8-5

NVD Description

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

The session cookie generated by the CUPS web interface was easy to guess on Linux, allowing unauthorized scripted access to the web interface when the web interface is enabled. This issue affected versions prior to v2.2.10.

Remediation

Upgrade Debian:unstable cups to version 2.2.10-1 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.31-9

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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

The iconv feature in the GNU C Library (aka glibc or libc6) through 2.32, when processing invalid multi-byte input sequences in the EUC-KR encoding, may have a buffer over-read.

Remediation

Upgrade Debian:unstable glibc to version 2.31-9 or higher.

References

medium severity

Use After Free

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.36-3

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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:unstable 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

Upgrade Debian:unstable glibc to version 2.36-3 or higher.

References

medium severity

Use After Free

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.37-10

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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:unstable 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

Upgrade Debian:unstable glibc to version 2.37-10 or higher.

References

medium severity

Information Exposure

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.19-1+b1
  • Fixed in: 3.8.2-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim gnutls28/libgnutls30@3.5.19-1+b1

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:unstable 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:unstable gnutls28 to version 3.8.2-1 or higher.

References

medium severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: libgcrypt20
  • Introduced through: libgcrypt20@1.8.4-3
  • Fixed in: 1.8.7-6

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libgcrypt20@1.8.4-3

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

The ElGamal implementation in Libgcrypt before 1.9.4 allows plaintext recovery because, during interaction between two cryptographic libraries, a certain dangerous combination of the prime defined by the receiver's public key, the generator defined by the receiver's public key, and the sender's ephemeral exponents can lead to a cross-configuration attack against OpenPGP.

Remediation

Upgrade Debian:unstable libgcrypt20 to version 1.8.7-6 or higher.

References

medium severity

CVE-2018-12404

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.39-1
  • Fixed in: 2:3.41-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim nss/libnss3@2:3.39-1

NVD Description

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

A cached side channel attack during handshakes using RSA encryption could allow for the decryption of encrypted content. This is a variant of the Adaptive Chosen Ciphertext attack (AKA Bleichenbacher attack) and affects all NSS versions prior to NSS 3.41.

Remediation

Upgrade Debian:unstable nss to version 2:3.41-1 or higher.

References

medium severity

CVE-2021-4160

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 1.1.1m-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

There is a carry propagation bug in the MIPS32 and MIPS64 squaring procedure. Many EC algorithms are affected, including some of the TLS 1.3 default curves. Impact was not analyzed in detail, because the pre-requisites for attack are considered unlikely and include reusing private keys. Analysis suggests that attacks against RSA and DSA as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH are considered just feasible (although very difficult) because most of the work necessary to deduce information about a private key may be performed offline. The amount of resources required for such an attack would be significant. However, for an attack on TLS to be meaningful, the server would have to share the DH private key among multiple clients, which is no longer an option since CVE-2016-0701. This issue affects OpenSSL versions 1.0.2, 1.1.1 and 3.0.0. It was addressed in the releases of 1.1.1m and 3.0.1 on the 15th of December 2021. For the 1.0.2 release it is addressed in git commit 6fc1aaaf3 that is available to premium support customers only. It will be made available in 1.0.2zc when it is released. The issue only affects OpenSSL on MIPS platforms. Fixed in OpenSSL 3.0.1 (Affected 3.0.0). Fixed in OpenSSL 1.1.1m (Affected 1.1.1-1.1.1l). Fixed in OpenSSL 1.0.2zc-dev (Affected 1.0.2-1.0.2zb).

Remediation

Upgrade Debian:unstable openssl to version 1.1.1m-1 or higher.

References

medium severity

Information Exposure

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 3.0.8-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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:unstable 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:unstable openssl to version 3.0.8-1 or higher.

References

medium severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

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

Remediation

Upgrade Debian:unstable openssl to version 1.1.1j-1 or higher.

References

medium severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

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

Remediation

Upgrade Debian:unstable openssl to version 1.1.1i-1 or higher.

References

medium severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

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

Remediation

Upgrade Debian:unstable openssl to version 1.1.1k-1 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 3.0.9-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

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

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

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

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

Remediation

Upgrade Debian:unstable openssl to version 3.0.9-1 or higher.

References

medium severity

Use of a Broken or Risky Cryptographic Algorithm

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

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

The OpenSSL DSA signature algorithm has been shown to be vulnerable to a timing side channel attack. An attacker could use variations in the signing algorithm to recover the private key. Fixed in OpenSSL 1.1.1a (Affected 1.1.1). Fixed in OpenSSL 1.1.0j (Affected 1.1.0-1.1.0i). Fixed in OpenSSL 1.0.2q (Affected 1.0.2-1.0.2p).

Remediation

Upgrade Debian:unstable openssl to version 1.1.1a-1 or higher.

References

medium severity

Use of a Broken or Risky Cryptographic Algorithm

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

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

The OpenSSL ECDSA signature algorithm has been shown to be vulnerable to a timing side channel attack. An attacker could use variations in the signing algorithm to recover the private key. Fixed in OpenSSL 1.1.0j (Affected 1.1.0-1.1.0i). Fixed in OpenSSL 1.1.1a (Affected 1.1.1).

Remediation

Upgrade Debian:unstable openssl to version 1.1.1a-1 or higher.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1
  • Fixed in: 3.30.1+fossil191229-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim sqlite3/libsqlite3-0@3.25.3-1

NVD Description

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

SQLite 3.30.1 mishandles pExpr->y.pTab, as demonstrated by the TK_COLUMN case in sqlite3ExprCodeTarget in expr.c.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.30.1+fossil191229-1 or higher.

References

medium severity

CVE-2023-7008

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@239-11 and systemd/libudev1@239-11
  • Fixed in: 255.1-3

Detailed paths

  • Introduced through: tomcat@8-jre10-slim systemd/libsystemd0@239-11
  • Introduced through: tomcat@8-jre10-slim systemd/libudev1@239-11

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:unstable 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

Upgrade Debian:unstable systemd to version 255.1-3 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: apt
  • Introduced through: apt@1.7.0 and apt/libapt-pkg5.0@1.7.0
  • Fixed in: 2.1.13

Detailed paths

  • Introduced through: tomcat@8-jre10-slim apt@1.7.0
  • Introduced through: tomcat@8-jre10-slim apt/libapt-pkg5.0@1.7.0

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

APT had several integer overflows and underflows while parsing .deb packages, aka GHSL-2020-168 GHSL-2020-169, in files apt-pkg/contrib/extracttar.cc, apt-pkg/deb/debfile.cc, and apt-pkg/contrib/arfile.cc. This issue affects: apt 1.2.32ubuntu0 versions prior to 1.2.32ubuntu0.2; 1.6.12ubuntu0 versions prior to 1.6.12ubuntu0.2; 2.0.2ubuntu0 versions prior to 2.0.2ubuntu0.2; 2.1.10ubuntu0 versions prior to 2.1.10ubuntu0.1;

Remediation

Upgrade Debian:unstable apt to version 2.1.13 or higher.

References

medium severity

Information Exposure

  • Vulnerable module: nettle/libhogweed4
  • Introduced through: nettle/libhogweed4@3.4-1 and nettle/libnettle6@3.4-1
  • Fixed in: 3.4.1~rc1-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim nettle/libhogweed4@3.4-1
  • Introduced through: tomcat@8-jre10-slim nettle/libnettle6@3.4-1

NVD Description

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

A Bleichenbacher type side-channel based padding oracle attack was found in the way nettle handles endian conversion of RSA decrypted PKCS#1 v1.5 data. An attacker who is able to run a process on the same physical core as the victim process, could use this flaw extract plaintext or in some cases downgrade any TLS connections to a vulnerable server.

Remediation

Upgrade Debian:unstable nettle to version 3.4.1~rc1-1 or higher.

References

medium severity

Information Exposure

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.19-1+b1
  • Fixed in: 3.6.5-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim gnutls28/libgnutls30@3.5.19-1+b1

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

A Bleichenbacher type side-channel based padding oracle attack was found in the way gnutls handles verification of RSA decrypted PKCS#1 v1.5 data. An attacker who is able to run process on the same physical core as the victim process, could use this to extract plaintext or in some cases downgrade any TLS connections to a vulnerable server.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.6.5-2 or higher.

References

medium severity
new

Incorrect Permission Assignment for Critical Resource

  • Vulnerable module: apr/libapr1
  • Introduced through: apr/libapr1@1.6.3-3
  • Fixed in: 1.7.5-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim apr/libapr1@1.6.3-3

NVD Description

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

Lax permissions set by the Apache Portable Runtime library on Unix platforms would allow local users read access to named shared memory segments, potentially revealing sensitive application data.

This issue does not affect non-Unix platforms, or builds with APR_USE_SHMEM_SHMGET=1 (apr.h)

Users are recommended to upgrade to APR version 1.7.5, which fixes this issue.

Remediation

Upgrade Debian:unstable apr to version 1.7.5-1 or higher.

References

medium severity

Improper Input Validation

  • Vulnerable module: apt
  • Introduced through: apt@1.7.0 and apt/libapt-pkg5.0@1.7.0
  • Fixed in: 2.1.2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim apt@1.7.0
  • Introduced through: tomcat@8-jre10-slim apt/libapt-pkg5.0@1.7.0

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

Missing input validation in the ar/tar implementations of APT before version 2.1.2 could result in denial of service when processing specially crafted deb files.

Remediation

Upgrade Debian:unstable apt to version 2.1.2 or higher.

References

medium severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: avahi/libavahi-client3
  • Introduced through: avahi/libavahi-client3@0.7-4+b1, avahi/libavahi-common-data@0.7-4+b1 and others
  • Fixed in: 0.8-7

Detailed paths

  • Introduced through: tomcat@8-jre10-slim avahi/libavahi-client3@0.7-4+b1
  • Introduced through: tomcat@8-jre10-slim avahi/libavahi-common-data@0.7-4+b1
  • Introduced through: tomcat@8-jre10-slim avahi/libavahi-common3@0.7-4+b1

NVD Description

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

A flaw was found in avahi in versions 0.6 up to 0.8. The event used to signal the termination of the client connection on the avahi Unix socket is not correctly handled in the client_work function, allowing a local attacker to trigger an infinite loop. The highest threat from this vulnerability is to the availability of the avahi service, which becomes unresponsive after this flaw is triggered.

Remediation

Upgrade Debian:unstable avahi to version 0.8-7 or higher.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: avahi/libavahi-client3
  • Introduced through: avahi/libavahi-client3@0.7-4+b1, avahi/libavahi-common-data@0.7-4+b1 and others
  • Fixed in: 0.8-6

Detailed paths

  • Introduced through: tomcat@8-jre10-slim avahi/libavahi-client3@0.7-4+b1
  • Introduced through: tomcat@8-jre10-slim avahi/libavahi-common-data@0.7-4+b1
  • Introduced through: tomcat@8-jre10-slim avahi/libavahi-common3@0.7-4+b1

NVD Description

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

A flaw was found in avahi 0.8-5. A reachable assertion is present in avahi_s_host_name_resolver_start function allowing a local attacker to crash the avahi service by requesting hostname resolutions through the avahi socket or dbus methods for invalid hostnames. The highest threat from this vulnerability is to the service availability.

Remediation

Upgrade Debian:unstable avahi to version 0.8-6 or higher.

References

medium severity

Reachable Assertion

  • Vulnerable module: avahi/libavahi-client3
  • Introduced through: avahi/libavahi-client3@0.7-4+b1, avahi/libavahi-common-data@0.7-4+b1 and others

Detailed paths

  • Introduced through: tomcat@8-jre10-slim avahi/libavahi-client3@0.7-4+b1
  • Introduced through: tomcat@8-jre10-slim avahi/libavahi-common-data@0.7-4+b1
  • Introduced through: tomcat@8-jre10-slim avahi/libavahi-common3@0.7-4+b1

NVD Description

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

A vulnerability was found in Avahi, where a reachable assertion exists in avahi_dns_packet_append_record.

Remediation

There is no fixed version for Debian:unstable avahi.

References

medium severity

Reachable Assertion

  • Vulnerable module: avahi/libavahi-client3
  • Introduced through: avahi/libavahi-client3@0.7-4+b1, avahi/libavahi-common-data@0.7-4+b1 and others

Detailed paths

  • Introduced through: tomcat@8-jre10-slim avahi/libavahi-client3@0.7-4+b1
  • Introduced through: tomcat@8-jre10-slim avahi/libavahi-common-data@0.7-4+b1
  • Introduced through: tomcat@8-jre10-slim avahi/libavahi-common3@0.7-4+b1

NVD Description

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

A vulnerability was found in Avahi. A reachable assertion exists in the avahi_escape_label() function.

Remediation

There is no fixed version for Debian:unstable avahi.

References

medium severity

Reachable Assertion

  • Vulnerable module: avahi/libavahi-client3
  • Introduced through: avahi/libavahi-client3@0.7-4+b1, avahi/libavahi-common-data@0.7-4+b1 and others

Detailed paths

  • Introduced through: tomcat@8-jre10-slim avahi/libavahi-client3@0.7-4+b1
  • Introduced through: tomcat@8-jre10-slim avahi/libavahi-common-data@0.7-4+b1
  • Introduced through: tomcat@8-jre10-slim avahi/libavahi-common3@0.7-4+b1

NVD Description

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

A vulnerability was found in Avahi. A reachable assertion exists in the avahi_rdata_parse() function.

Remediation

There is no fixed version for Debian:unstable avahi.

References

medium severity

Reachable Assertion

  • Vulnerable module: avahi/libavahi-client3
  • Introduced through: avahi/libavahi-client3@0.7-4+b1, avahi/libavahi-common-data@0.7-4+b1 and others

Detailed paths

  • Introduced through: tomcat@8-jre10-slim avahi/libavahi-client3@0.7-4+b1
  • Introduced through: tomcat@8-jre10-slim avahi/libavahi-common-data@0.7-4+b1
  • Introduced through: tomcat@8-jre10-slim avahi/libavahi-common3@0.7-4+b1

NVD Description

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

A vulnerability was found in Avahi. A reachable assertion exists in the dbus_set_host_name function.

Remediation

There is no fixed version for Debian:unstable avahi.

References

medium severity

Reachable Assertion

  • Vulnerable module: avahi/libavahi-client3
  • Introduced through: avahi/libavahi-client3@0.7-4+b1, avahi/libavahi-common-data@0.7-4+b1 and others

Detailed paths

  • Introduced through: tomcat@8-jre10-slim avahi/libavahi-client3@0.7-4+b1
  • Introduced through: tomcat@8-jre10-slim avahi/libavahi-common-data@0.7-4+b1
  • Introduced through: tomcat@8-jre10-slim avahi/libavahi-common3@0.7-4+b1

NVD Description

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

A vulnerability was found in Avahi. A reachable assertion exists in the avahi_alternative_host_name() function.

Remediation

There is no fixed version for Debian:unstable avahi.

References

medium severity

Resource Exhaustion

  • Vulnerable module: avahi/libavahi-client3
  • Introduced through: avahi/libavahi-client3@0.7-4+b1, avahi/libavahi-common-data@0.7-4+b1 and others
  • Fixed in: 0.8-10

Detailed paths

  • Introduced through: tomcat@8-jre10-slim avahi/libavahi-client3@0.7-4+b1
  • Introduced through: tomcat@8-jre10-slim avahi/libavahi-common-data@0.7-4+b1
  • Introduced through: tomcat@8-jre10-slim avahi/libavahi-common3@0.7-4+b1

NVD Description

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

A vulnerability was found in the avahi library. This flaw allows an unprivileged user to make a dbus call, causing the avahi daemon to crash.

Remediation

Upgrade Debian:unstable avahi to version 0.8-10 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: coreutils
  • Introduced through: coreutils@8.30-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim coreutils@8.30-1

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

A flaw was found in the GNU coreutils "split" program. A heap overflow with user-controlled data of multiple hundred bytes in length could occur in the line_bytes_split() function, potentially leading to an application crash and denial of service.

Remediation

There is no fixed version for Debian:unstable coreutils.

References

medium severity

CVE-2023-32360

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.8-5
  • Fixed in: 2.4.2-6

Detailed paths

  • Introduced through: tomcat@8-jre10-slim cups/libcups2@2.2.8-5

NVD Description

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

An authentication issue was addressed with improved state management. This issue is fixed in macOS Big Sur 11.7.7, macOS Monterey 12.6.6, macOS Ventura 13.4. An unauthenticated user may be able to access recently printed documents.

Remediation

Upgrade Debian:unstable cups to version 2.4.2-6 or higher.

References

medium severity

Improper Input Validation

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.8-5
  • Fixed in: 2.3.3op2-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim cups/libcups2@2.2.8-5

NVD Description

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

An input validation issue was addressed with improved memory handling. This issue is fixed in macOS Big Sur 11.1, Security Update 2020-001 Catalina, Security Update 2020-007 Mojave. A malicious application may be able to read restricted memory.

Remediation

Upgrade Debian:unstable cups to version 2.3.3op2-1 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.8-5
  • Fixed in: 2.2.12-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim cups/libcups2@2.2.8-5

NVD Description

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

In ippSetValueTag of ipp.c in Android 8.0, 8.1 and 9, there is a possible out of bounds read due to improper input validation. This could lead to local information disclosure from the printer service with no additional execution privileges needed. User interaction is not needed for exploitation.

Remediation

Upgrade Debian:unstable cups to version 2.2.12-1 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.8-5
  • Fixed in: 2.3.1-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim cups/libcups2@2.2.8-5

NVD Description

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

In array_find of array.c, there is a possible out-of-bounds read due to an incorrect bounds check. This could lead to local information disclosure in the printer spooler with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-8.0 Android-8.1 Android-9 Android-10Android ID: A-111210196

Remediation

Upgrade Debian:unstable cups to version 2.3.1-1 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.8-5
  • Fixed in: 2.4.2-4

Detailed paths

  • Introduced through: tomcat@8-jre10-slim cups/libcups2@2.2.8-5

NVD Description

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

OpenPrinting CUPS is an open source printing system. In versions 2.4.2 and prior, a heap buffer overflow vulnerability would allow a remote attacker to launch a denial of service (DoS) attack. A buffer overflow vulnerability in the function format_log_line could allow remote attackers to cause a DoS on the affected system. Exploitation of the vulnerability can be triggered when the configuration file cupsd.conf sets the value of loglevel to DEBUG. No known patches or workarounds exist at time of publication.

Remediation

Upgrade Debian:unstable cups to version 2.4.2-4 or higher.

References

medium severity

Improper Resource Shutdown or Release

  • Vulnerable module: dbus/libdbus-1-3
  • Introduced through: dbus/libdbus-1-3@1.12.10-1
  • Fixed in: 1.12.18-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim dbus/libdbus-1-3@1.12.10-1

NVD Description

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

An issue was discovered in dbus >= 1.3.0 before 1.12.18. The DBusServer in libdbus, as used in dbus-daemon, leaks file descriptors when a message exceeds the per-message file descriptor limit. A local attacker with access to the D-Bus system bus or another system service's private AF_UNIX socket could use this to make the system service reach its file descriptor limit, denying service to subsequent D-Bus clients.

Remediation

Upgrade Debian:unstable dbus to version 1.12.18-1 or higher.

References

medium severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.31-5

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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

The iconv function in the GNU C Library (aka glibc or libc6) 2.32 and earlier, when processing invalid multi-byte input sequences in IBM1364, IBM1371, IBM1388, IBM1390, and IBM1399 encodings, fails to advance the input state, which could lead to an infinite loop in applications, resulting in a denial of service, a different vulnerability from CVE-2016-10228.

Remediation

Upgrade Debian:unstable glibc to version 2.31-5 or higher.

References

medium severity

Out-of-Bounds

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.30-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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

The GNU C Library (aka glibc or libc6) before 2.32 could overflow an on-stack buffer during range reduction if an input to an 80-bit long double function contains a non-canonical bit pattern, a seen when passing a 0x5d414141414141410000 value to sinl on x86 targets. This is related to sysdeps/ieee754/ldbl-96/e_rem_pio2l.c.

Remediation

Upgrade Debian:unstable glibc to version 2.30-1 or higher.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: libjpeg-turbo/libjpeg62-turbo
  • Introduced through: libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+b1
  • Fixed in: 1:2.0.6-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+b1

NVD Description

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

A crafted input file could cause a null pointer dereference in jcopy_sample_rows() when processed by libjpeg-turbo.

Remediation

Upgrade Debian:unstable libjpeg-turbo to version 1:2.0.6-1 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: libjpeg-turbo/libjpeg62-turbo
  • Introduced through: libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+b1
  • Fixed in: 1:2.1.1-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+b1

NVD Description

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

The PPM reader in libjpeg-turbo through 2.0.90 mishandles use of tjLoadImage for loading a 16-bit binary PPM file into a grayscale buffer and loading a 16-bit binary PGM file into an RGB buffer. This is related to a heap-based buffer overflow in the get_word_rgb_row function in rdppm.c.

Remediation

Upgrade Debian:unstable libjpeg-turbo to version 1:2.1.1-1 or higher.

References

medium severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: libx11/libx11-6
  • Introduced through: libx11/libx11-6@2:1.6.7-1 and libx11/libx11-data@2:1.6.7-1
  • Fixed in: 2:1.8.7-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libx11/libx11-6@2:1.6.7-1
  • Introduced through: tomcat@8-jre10-slim libx11/libx11-data@2:1.6.7-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:unstable 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:unstable libx11 to version 2:1.8.7-1 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: libx11/libx11-6
  • Introduced through: libx11/libx11-6@2:1.6.7-1 and libx11/libx11-data@2:1.6.7-1
  • Fixed in: 2:1.8.7-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libx11/libx11-6@2:1.6.7-1
  • Introduced through: tomcat@8-jre10-slim libx11/libx11-data@2:1.6.7-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:unstable 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:unstable libx11 to version 2:1.8.7-1 or higher.

References

medium severity

Incorrect Default Permissions

  • Vulnerable module: libzstd/libzstd1
  • Introduced through: libzstd/libzstd1@1.3.5+dfsg-1
  • Fixed in: 1.4.8+dfsg-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libzstd/libzstd1@1.3.5+dfsg-1

NVD Description

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

In the Zstandard command-line utility prior to v1.4.1, output files were created with default permissions. Correct file permissions (matching the input) would only be set at completion time. Output files could therefore be readable or writable to unintended parties.

Remediation

Upgrade Debian:unstable libzstd to version 1.4.8+dfsg-1 or higher.

References

medium severity

CVE-2024-0727

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 3.1.5-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

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

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

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

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

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

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

Remediation

Upgrade Debian:unstable openssl to version 3.1.5-1 or higher.

References

medium severity

CVE-2024-22365

  • Vulnerable module: pam/libpam-modules
  • Introduced through: pam/libpam-modules@1.1.8-3.8, pam/libpam-modules-bin@1.1.8-3.8 and others
  • Fixed in: 1.5.3-4

Detailed paths

  • Introduced through: tomcat@8-jre10-slim pam/libpam-modules@1.1.8-3.8
  • Introduced through: tomcat@8-jre10-slim pam/libpam-modules-bin@1.1.8-3.8
  • Introduced through: tomcat@8-jre10-slim pam/libpam-runtime@1.1.8-3.8
  • Introduced through: tomcat@8-jre10-slim pam/libpam0g@1.1.8-3.8

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:unstable 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

Upgrade Debian:unstable pam to version 1.5.3-4 or higher.

References

medium severity

Improper Authentication

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.5-1.1 and shadow/passwd@1:4.5-1.1
  • Fixed in: 1:4.13+dfsg1-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim shadow/login@1:4.5-1.1
  • Introduced through: tomcat@8-jre10-slim shadow/passwd@1:4.5-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:unstable 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

Upgrade Debian:unstable shadow to version 1:4.13+dfsg1-2 or higher.

References

medium severity

Buffer Overflow

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1
  • Fixed in: 3.27.2-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim sqlite3/libsqlite3-0@3.25.3-1

NVD Description

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

Buffer Overflow vulnerability found in SQLite3 v.3.27.1 and before allows a local attacker to cause a denial of service via a crafted script.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.27.2-1 or higher.

References

medium severity

CVE-2020-13631

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1
  • Fixed in: 3.32.0-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim sqlite3/libsqlite3-0@3.25.3-1

NVD Description

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

SQLite before 3.32.0 allows a virtual table to be renamed to the name of one of its shadow tables, related to alter.c and build.c.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.32.0-1 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1
  • Fixed in: 3.32.1-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim sqlite3/libsqlite3-0@3.25.3-1

NVD Description

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

SQLite through 3.32.0 has an integer overflow in sqlite3_str_vappendf in printf.c.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.32.1-1 or higher.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1
  • Fixed in: 3.32.1-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim sqlite3/libsqlite3-0@3.25.3-1

NVD Description

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

SQLite through 3.32.0 has a segmentation fault in sqlite3ExprCodeTarget in expr.c.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.32.1-1 or higher.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1
  • Fixed in: 3.32.0-1

medium severity

Out-of-bounds Write

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1
  • Fixed in: 3.32.3-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim sqlite3/libsqlite3-0@3.25.3-1

NVD Description

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

In SQLite before 3.32.3, select.c mishandles query-flattener optimization, leading to a multiSelectOrderBy heap overflow because of misuse of transitive properties for constant propagation.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.32.3-1 or higher.

References

medium severity

Uncontrolled Recursion

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1
  • Fixed in: 3.30.1+fossil191229-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim sqlite3/libsqlite3-0@3.25.3-1

NVD Description

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

alter.c in SQLite through 3.30.1 allows attackers to trigger infinite recursion via certain types of self-referential views in conjunction with ALTER TABLE statements.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.30.1+fossil191229-1 or higher.

References

medium severity

Use After Free

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1
  • Fixed in: 3.34.1-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim sqlite3/libsqlite3-0@3.25.3-1

NVD Description

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

A flaw was found in SQLite's SELECT query functionality (src/select.c). This flaw allows an attacker who is capable of running SQL queries locally on the SQLite database to cause a denial of service or possible code execution by triggering a use-after-free. The highest threat from this vulnerability is to system availability.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.34.1-1 or higher.

References

medium severity

Use After Free

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1
  • Fixed in: 3.43.2-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim sqlite3/libsqlite3-0@3.25.3-1

NVD Description

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

A heap use-after-free issue has been identified in SQLite in the jsonParseAddNodeArray() function in sqlite3.c. This flaw allows a local attacker to leverage a victim to pass specially crafted malicious input to the application, potentially causing a crash and leading to a denial of service.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.43.2-1 or higher.

References

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@239-11 and systemd/libudev1@239-11
  • Fixed in: 247.3-6

Detailed paths

  • Introduced through: tomcat@8-jre10-slim systemd/libsystemd0@239-11
  • Introduced through: tomcat@8-jre10-slim systemd/libudev1@239-11

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

basic/unit-name.c in systemd prior to 246.15, 247.8, 248.5, and 249.1 has a Memory Allocation with an Excessive Size Value (involving strdupa and alloca for a pathname controlled by a local attacker) that results in an operating system crash.

Remediation

Upgrade Debian:unstable systemd to version 247.3-6 or higher.

References

medium severity

CVE-2022-4415

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@239-11 and systemd/libudev1@239-11
  • Fixed in: 252.4-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim systemd/libsystemd0@239-11
  • Introduced through: tomcat@8-jre10-slim systemd/libudev1@239-11

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:unstable 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:unstable systemd to version 252.4-1 or higher.

References

medium severity

Off-by-one Error

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@239-11 and systemd/libudev1@239-11
  • Fixed in: 251.3-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim systemd/libsystemd0@239-11
  • Introduced through: tomcat@8-jre10-slim systemd/libudev1@239-11

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:unstable 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:unstable systemd to version 251.3-1 or higher.

References

medium severity

Out-of-Bounds

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@239-11 and systemd/libudev1@239-11
  • Fixed in: 240-6

Detailed paths

  • Introduced through: tomcat@8-jre10-slim systemd/libsystemd0@239-11
  • Introduced through: tomcat@8-jre10-slim systemd/libudev1@239-11

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

An issue was discovered in sd-bus in systemd 239. bus_process_object() in libsystemd/sd-bus/bus-objects.c allocates a variable-length stack buffer for temporarily storing the object path of incoming D-Bus messages. An unprivileged local user can exploit this by sending a specially crafted message to PID1, causing the stack pointer to jump over the stack guard pages into an unmapped memory region and trigger a denial of service (systemd PID1 crash and kernel panic).

Remediation

Upgrade Debian:unstable systemd to version 240-6 or higher.

References

medium severity

Resource Exhaustion

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@239-11 and systemd/libudev1@239-11
  • Fixed in: 252-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim systemd/libsystemd0@239-11
  • Introduced through: tomcat@8-jre10-slim systemd/libudev1@239-11

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

systemd 250 and 251 allows local users to achieve a systemd-coredump deadlock by triggering a crash that has a long backtrace. This occurs in parse_elf_object in shared/elf-util.c. The exploitation methodology is to crash a binary calling the same function recursively, and put it in a deeply nested directory to make its backtrace large enough to cause the deadlock. This must be done 16 times when MaxConnections=16 is set for the systemd/units/systemd-coredump.socket file.

Remediation

Upgrade Debian:unstable systemd to version 252-1 or higher.

References

medium severity

Uncontrolled Recursion

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@239-11 and systemd/libudev1@239-11
  • Fixed in: 250.2-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim systemd/libsystemd0@239-11
  • Introduced through: tomcat@8-jre10-slim systemd/libudev1@239-11

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

A flaw was found in systemd. An uncontrolled recursion in systemd-tmpfiles may lead to a denial of service at boot time when too many nested directories are created in /tmp.

Remediation

Upgrade Debian:unstable systemd to version 250.2-1 or higher.

References

medium severity

CVE-2022-0530

  • Vulnerable module: unzip
  • Introduced through: unzip@6.0-21
  • Fixed in: 6.0-27

Detailed paths

  • Introduced through: tomcat@8-jre10-slim unzip@6.0-21

NVD Description

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

A flaw was found in Unzip. The vulnerability occurs during the conversion of a wide string to a local string that leads to a heap of out-of-bound write. This flaw allows an attacker to input a specially crafted zip file, leading to a crash or code execution.

Remediation

Upgrade Debian:unstable unzip to version 6.0-27 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: unzip
  • Introduced through: unzip@6.0-21
  • Fixed in: 6.0-27

Detailed paths

  • Introduced through: tomcat@8-jre10-slim unzip@6.0-21

NVD Description

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

A flaw was found in Unzip. The vulnerability occurs during the conversion of a wide string to a local string that leads to a heap of out-of-bound write. This flaw allows an attacker to input a specially crafted zip file, leading to a crash or code execution.

Remediation

Upgrade Debian:unstable unzip to version 6.0-27 or higher.

References

medium severity

Files or Directories Accessible to External Parties

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.32.1-0.2, util-linux/fdisk@2.32.1-0.2 and others
  • Fixed in: 2.37.3-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim util-linux@2.32.1-0.2
  • Introduced through: tomcat@8-jre10-slim util-linux/fdisk@2.32.1-0.2
  • Introduced through: tomcat@8-jre10-slim util-linux/libblkid1@2.32.1-0.2
  • Introduced through: tomcat@8-jre10-slim util-linux/libfdisk1@2.32.1-0.2
  • Introduced through: tomcat@8-jre10-slim util-linux/libmount1@2.32.1-0.2
  • Introduced through: tomcat@8-jre10-slim util-linux/libsmartcols1@2.32.1-0.2
  • Introduced through: tomcat@8-jre10-slim util-linux/libuuid1@2.32.1-0.2
  • Introduced through: tomcat@8-jre10-slim util-linux/mount@2.32.1-0.2

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

A logic error was found in the libmount library of util-linux in the function that allows an unprivileged user to unmount a FUSE filesystem. This flaw allows a local user on a vulnerable system to unmount other users' filesystems that are either world-writable themselves (like /tmp) or mounted in a world-writable directory. An attacker may use this flaw to cause a denial of service to applications that use the affected filesystems.

Remediation

Upgrade Debian:unstable util-linux to version 2.37.3-1 or higher.

References

medium severity

Files or Directories Accessible to External Parties

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.32.1-0.2, util-linux/fdisk@2.32.1-0.2 and others
  • Fixed in: 2.37.3-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim util-linux@2.32.1-0.2
  • Introduced through: tomcat@8-jre10-slim util-linux/fdisk@2.32.1-0.2
  • Introduced through: tomcat@8-jre10-slim util-linux/libblkid1@2.32.1-0.2
  • Introduced through: tomcat@8-jre10-slim util-linux/libfdisk1@2.32.1-0.2
  • Introduced through: tomcat@8-jre10-slim util-linux/libmount1@2.32.1-0.2
  • Introduced through: tomcat@8-jre10-slim util-linux/libsmartcols1@2.32.1-0.2
  • Introduced through: tomcat@8-jre10-slim util-linux/libuuid1@2.32.1-0.2
  • Introduced through: tomcat@8-jre10-slim util-linux/mount@2.32.1-0.2

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

A logic error was found in the libmount library of util-linux in the function that allows an unprivileged user to unmount a FUSE filesystem. This flaw allows an unprivileged local attacker to unmount FUSE filesystems that belong to certain other users who have a UID that is a prefix of the UID of the attacker in its string form. An attacker may use this flaw to cause a denial of service to applications that use the affected filesystems.

Remediation

Upgrade Debian:unstable util-linux to version 2.37.3-1 or higher.

References

medium severity

Improper Input Validation

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.28-6

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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

In the GNU C Library (aka glibc or libc6) through 2.28, the getaddrinfo function would successfully parse a string that contained an IPv4 address followed by whitespace and arbitrary characters, which could lead applications to incorrectly assume that it had parsed a valid string, without the possibility of embedded HTTP headers or other potentially dangerous substrings.

Remediation

Upgrade Debian:unstable glibc to version 2.28-6 or higher.

References

medium severity

Incorrect Calculation of Buffer Size

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.37-15

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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

An integer overflow was found in the __vsyslog_internal function of the glibc library. This function is called by the syslog and vsyslog functions. This issue occurs when these functions are called with a very long message, leading to an incorrect calculation of the buffer size to store the message, resulting in undefined behavior. This issue affects glibc 2.37 and newer.

Remediation

Upgrade Debian:unstable glibc to version 2.37-15 or higher.

References

medium severity

Use After Free

  • Vulnerable module: libpng1.6/libpng16-16
  • Introduced through: libpng1.6/libpng16-16@1.6.34-2
  • Fixed in: 1.6.36-4

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libpng1.6/libpng16-16@1.6.34-2

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

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

Remediation

Upgrade Debian:unstable libpng1.6 to version 1.6.36-4 or higher.

References

medium severity

CVE-2020-6829

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.39-1
  • Fixed in: 2:3.55-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim nss/libnss3@2:3.39-1

NVD Description

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

When performing EC scalar point multiplication, the wNAF point multiplication algorithm was used; which leaked partial information about the nonce used during signature generation. Given an electro-magnetic trace of a few signature generations, the private key could have been computed. This vulnerability affects Firefox < 80 and Firefox for Android < 80.

Remediation

Upgrade Debian:unstable nss to version 2:3.55-1 or higher.

References

medium severity

Improper Certificate Validation

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.39-1
  • Fixed in: 2:3.45-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim nss/libnss3@2:3.39-1

NVD Description

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

A vulnerability exists where it possible to force Network Security Services (NSS) to sign CertificateVerify with PKCS#1 v1.5 signatures when those are the only ones advertised by server in CertificateRequest in TLS 1.3. PKCS#1 v1.5 signatures should not be used for TLS 1.3 messages. This vulnerability affects Firefox < 68.

Remediation

Upgrade Debian:unstable nss to version 2:3.45-1 or higher.

References

medium severity

Excessive Iteration

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 3.0.10-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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:unstable 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:unstable openssl to version 3.0.10-1 or higher.

References

medium severity

Improper Authentication

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 3.0.10-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

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

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

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

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

Remediation

Upgrade Debian:unstable openssl to version 3.0.10-1 or higher.

References

medium severity

Improper Certificate Validation

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 3.0.9-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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:unstable 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:unstable openssl to version 3.0.9-1 or higher.

References

medium severity

Improper Certificate Validation

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 3.0.9-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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:unstable 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&#39; argument to the command line utilities or by calling the X509_VERIFY_PARAM_set1_policies()' function.

Remediation

Upgrade Debian:unstable openssl to version 3.0.9-1 or higher.

References

medium severity

Improper Check for Unusual or Exceptional Conditions

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 3.0.12-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

Issue summary: Generating excessively long X9.42 DH keys or checking excessively long X9.42 DH keys or parameters may be very slow.

Impact summary: Applications that use the functions DH_generate_key() to generate an X9.42 DH key may experience long delays. Likewise, applications that use DH_check_pub_key(), DH_check_pub_key_ex() or EVP_PKEY_public_check() to check an X9.42 DH key or X9.42 DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service.

While DH_check() performs all the necessary checks (as of CVE-2023-3817), DH_check_pub_key() doesn't make any of these checks, and is therefore vulnerable for excessively large P and Q parameters.

Likewise, while DH_generate_key() performs a check for an excessively large P, it doesn't check for an excessively large Q.

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

DH_generate_key() and DH_check_pub_key() are also called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_pub_key_ex(), EVP_PKEY_public_check(), and EVP_PKEY_generate().

Also vulnerable are the OpenSSL pkey command line application when using the "-pubcheck" option, as well as the OpenSSL genpkey command line application.

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

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

Remediation

Upgrade Debian:unstable openssl to version 3.0.12-2 or higher.

References

medium severity

Inefficient Regular Expression Complexity

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 3.0.10-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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:unstable 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:unstable openssl to version 3.0.10-1 or higher.

References

medium severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 3.0.5-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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:unstable 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:unstable openssl to version 3.0.5-1 or higher.

References

medium severity

Use of Insufficiently Random Values

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 1.1.1d-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

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

Remediation

Upgrade Debian:unstable openssl to version 1.1.1d-1 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: p11-kit/libp11-kit0
  • Introduced through: p11-kit/libp11-kit0@0.23.14-2
  • Fixed in: 0.23.22-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim p11-kit/libp11-kit0@0.23.14-2

NVD Description

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

An issue was discovered in p11-kit 0.21.1 through 0.23.21. A heap-based buffer over-read has been discovered in the RPC protocol used by thep11-kit server/remote commands and the client library. When the remote entity supplies a byte array through a serialized PKCS#11 function call, the receiving entity may allow the reading of up to 4 bytes of memory past the heap allocation.

Remediation

Upgrade Debian:unstable p11-kit to version 0.23.22-1 or higher.

References

medium severity

Integer Overflow or Wraparound

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

medium severity

Improper Handling of Exceptional Conditions

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1
  • Fixed in: 3.30.1+fossil191229-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim sqlite3/libsqlite3-0@3.25.3-1

NVD Description

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

SQLite 3.30.1 mishandles certain parser-tree rewriting, related to expr.c, vdbeaux.c, and window.c. This is caused by incorrect sqlite3WindowRewrite() error handling.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.30.1+fossil191229-1 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 3.0.8-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

A read buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed the malicious certificate or for the application to continue certificate verification despite failure to construct a path to a trusted issuer.

The read buffer overrun might result in a crash which could lead to a denial of service attack. In theory it could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext) although we are not aware of any working exploit leading to memory contents disclosure as of the time of release of this advisory.

In a TLS client, this can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server requests client authentication and a malicious client connects.

Remediation

Upgrade Debian:unstable openssl to version 3.0.8-1 or higher.

References

medium severity

Reachable Assertion

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.31-7

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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

The iconv function in the GNU C Library (aka glibc or libc6) 2.30 to 2.32, when converting UCS4 text containing an irreversible character, fails an assertion in the code path and aborts the program, potentially resulting in a denial of service.

Remediation

Upgrade Debian:unstable glibc to version 2.31-7 or higher.

References

medium severity

Incorrect Default Permissions

  • Vulnerable module: libzstd/libzstd1
  • Introduced through: libzstd/libzstd1@1.3.5+dfsg-1
  • Fixed in: 1.4.8+dfsg-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libzstd/libzstd1@1.3.5+dfsg-1

NVD Description

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

Beginning in v1.4.1 and prior to v1.4.9, due to an incomplete fix for CVE-2021-24031, the Zstandard command-line utility created output files with default permissions and restricted those permissions immediately afterwards. Output files could therefore momentarily be readable or writable to unintended parties.

Remediation

Upgrade Debian:unstable libzstd to version 1.4.8+dfsg-2 or higher.

References

medium severity

Information Exposure

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.39-1
  • Fixed in: 2:3.55-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim nss/libnss3@2:3.39-1

NVD Description

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

When converting coordinates from projective to affine, the modular inversion was not performed in constant time, resulting in a possible timing-based side channel attack. This vulnerability affects Firefox < 80 and Firefox for Android < 80.

Remediation

Upgrade Debian:unstable nss to version 2:3.55-1 or higher.

References

medium severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.39-1
  • Fixed in: 2:3.55-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim nss/libnss3@2:3.39-1

NVD Description

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

During ECDSA signature generation, padding applied in the nonce designed to ensure constant-time scalar multiplication was removed, resulting in variable-time execution dependent on secret data. This vulnerability affects Firefox < 80 and Firefox for Android < 80.

Remediation

Upgrade Debian:unstable nss to version 2:3.55-1 or higher.

References

medium severity

CVE-2019-1547

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 1.1.1d-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

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

Remediation

Upgrade Debian:unstable openssl to version 1.1.1d-1 or higher.

References

medium severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: tar
  • Introduced through: tar@1.30+dfsg-2
  • Fixed in: 1.30+dfsg-3.1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim tar@1.30+dfsg-2

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

GNU Tar through 1.30, when --sparse is used, mishandles file shrinkage during read access, which allows local users to cause a denial of service (infinite read loop in sparse_dump_region in sparse.c) by modifying a file that is supposed to be archived by a different user's process (e.g., a system backup running as root).

Remediation

Upgrade Debian:unstable tar to version 1.30+dfsg-3.1 or higher.

References

medium severity

Information Exposure

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.39-1
  • Fixed in: 2:3.53-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim nss/libnss3@2:3.39-1

NVD Description

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

NSS has shown timing differences when performing DSA signatures, which was exploitable and could eventually leak private keys. This vulnerability affects Thunderbird < 68.9.0, Firefox < 77, and Firefox ESR < 68.9.

Remediation

Upgrade Debian:unstable nss to version 2:3.53-1 or higher.

References

medium severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.39-1
  • Fixed in: 2:3.53.1-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim nss/libnss3@2:3.39-1

NVD Description

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

During RSA key generation, bignum implementations used a variation of the Binary Extended Euclidean Algorithm which entailed significantly input-dependent flow. This allowed an attacker able to perform electromagnetic-based side channel attacks to record traces leading to the recovery of the secret primes. Note: An unmodified Firefox browser does not generate RSA keys in normal operation and is not affected, but products built on top of it might. This vulnerability affects Firefox < 78.

Remediation

Upgrade Debian:unstable nss to version 2:3.53.1-1 or higher.

References

medium severity

CVE-2019-15718

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@239-11 and systemd/libudev1@239-11
  • Fixed in: 242-7

Detailed paths

  • Introduced through: tomcat@8-jre10-slim systemd/libsystemd0@239-11
  • Introduced through: tomcat@8-jre10-slim systemd/libudev1@239-11

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

In systemd 240, bus_open_system_watch_bind_with_description in shared/bus-util.c (as used by systemd-resolved to connect to the system D-Bus instance), calls sd_bus_set_trusted, which disables access controls for incoming D-Bus messages. An unprivileged user can exploit this by executing D-Bus methods that should be restricted to privileged users, in order to change the system's DNS resolver settings.

Remediation

Upgrade Debian:unstable systemd to version 242-7 or higher.

References

medium severity

Information Exposure

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.39-1
  • Fixed in: 2:3.95-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim nss/libnss3@2:3.39-1

NVD Description

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

Multiple NSS NIST curves were susceptible to a side-channel attack known as "Minerva". This attack could potentially allow an attacker to recover the private key. This vulnerability affects Firefox < 121.

Remediation

Upgrade Debian:unstable nss to version 2:3.95-1 or higher.

References

low severity

Out-of-Bounds

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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:unstable 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:unstable glibc.

References

low severity

CVE-2019-9893

  • Vulnerable module: libseccomp/libseccomp2
  • Introduced through: libseccomp/libseccomp2@2.3.3-3
  • Fixed in: 2.4.1-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libseccomp/libseccomp2@2.3.3-3

NVD Description

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

libseccomp before 2.4.0 did not correctly generate 64-bit syscall argument comparisons using the arithmetic operators (LT, GT, LE, GE), which might able to lead to bypassing seccomp filters and potential privilege escalations.

Remediation

Upgrade Debian:unstable libseccomp to version 2.4.1-1 or higher.

References

low severity

Out-of-bounds Write

  • Vulnerable module: perl/perl-base
  • Introduced through: perl/perl-base@5.28.0-3
  • Fixed in: 5.36.0-4

Detailed paths

  • Introduced through: tomcat@8-jre10-slim perl/perl-base@5.28.0-3

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

In Perl 5.34.0, function S_find_uninit_var in sv.c has a stack-based crash that can lead to remote code execution or local privilege escalation.

Remediation

Upgrade Debian:unstable perl to version 5.36.0-4 or higher.

References

low severity

Use After Free

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1
  • Fixed in: 3.32.0-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim sqlite3/libsqlite3-0@3.25.3-1

NVD Description

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

In SQLite through 3.31.1, the ALTER TABLE implementation has a use-after-free, as demonstrated by an ORDER BY clause that belongs to a compound SELECT statement.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.32.0-1 or higher.

References

low severity

Improper Certificate Validation

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@239-11 and systemd/libudev1@239-11
  • Fixed in: 244-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim systemd/libsystemd0@239-11
  • Introduced through: tomcat@8-jre10-slim systemd/libudev1@239-11

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

systemd 239 through 245 accepts any certificate signed by a trusted certificate authority for DNS Over TLS. Server Name Indication (SNI) is not sent, and there is no hostname validation with the GnuTLS backend. NOTE: This has been disputed by the developer as not a vulnerability since hostname validation does not have anything to do with this issue (i.e. there is no hostname to be sent)

Remediation

Upgrade Debian:unstable systemd to version 244-1 or higher.

References

low severity

CVE-2005-2541

  • Vulnerable module: tar
  • Introduced through: tar@1.30+dfsg-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim tar@1.30+dfsg-2

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:unstable 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:unstable tar.

References

low severity

Origin Validation Error

  • Vulnerable module: avahi/libavahi-client3
  • Introduced through: avahi/libavahi-client3@0.7-4+b1, avahi/libavahi-common-data@0.7-4+b1 and others
  • Fixed in: 0.7-5

Detailed paths

  • Introduced through: tomcat@8-jre10-slim avahi/libavahi-client3@0.7-4+b1
  • Introduced through: tomcat@8-jre10-slim avahi/libavahi-common-data@0.7-4+b1
  • Introduced through: tomcat@8-jre10-slim avahi/libavahi-common3@0.7-4+b1

NVD Description

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

avahi-daemon in Avahi through 0.6.32 and 0.7 inadvertently responds to IPv6 unicast queries with source addresses that are not on-link, which allows remote attackers to cause a denial of service (traffic amplification) and may cause information leakage by obtaining potentially sensitive information from the responding device via port-5353 UDP packets. NOTE: this may overlap CVE-2015-2809.

Remediation

Upgrade Debian:unstable avahi to version 0.7-5 or higher.

References

low severity

Improper Input Validation

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.8-5

Detailed paths

  • Introduced through: tomcat@8-jre10-slim cups/libcups2@2.2.8-5

NVD Description

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

The browsing feature in the server in CUPS does not filter ANSI escape sequences from shared printer names, which might allow remote attackers to execute arbitrary code via a crafted printer name.

Remediation

There is no fixed version for Debian:unstable cups.

References

low severity

CVE-2019-1010023

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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:unstable 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:unstable glibc.

References

low severity

Out-of-bounds Write

  • Vulnerable module: libjpeg-turbo/libjpeg62-turbo
  • Introduced through: libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+b1
  • Fixed in: 1:2.0.5-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+b1

NVD Description

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

Libjpeg-turbo all version have a stack-based buffer overflow in the "transform" component. A remote attacker can send a malformed jpeg file to the service and cause arbitrary code execution or denial of service of the target service.

Remediation

Upgrade Debian:unstable libjpeg-turbo to version 1:2.0.5-1 or higher.

References

low severity

Out-of-bounds Write

  • Vulnerable module: libpng1.6/libpng16-16
  • Introduced through: libpng1.6/libpng16-16@1.6.34-2
  • Fixed in: 1.6.37-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libpng1.6/libpng16-16@1.6.34-2

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

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

Remediation

Upgrade Debian:unstable libpng1.6 to version 1.6.37-1 or higher.

References

low severity

Out-of-bounds Write

  • Vulnerable module: ncurses/libncursesw6
  • Introduced through: ncurses/libncursesw6@6.1+20181013-1, ncurses/libtinfo6@6.1+20181013-1 and others
  • Fixed in: 6.2+20200912-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim ncurses/libncursesw6@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/libtinfo6@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/ncurses-base@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/ncurses-bin@6.1+20181013-1

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

An issue was discovered in ncurses through v6.2-1. _nc_captoinfo in captoinfo.c has a heap-based buffer overflow.

Remediation

Upgrade Debian:unstable ncurses to version 6.2+20200912-1 or higher.

References

low severity

Integer Underflow

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.31-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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

An exploitable signed comparison vulnerability exists in the ARMv7 memcpy() implementation of GNU glibc 2.30.9000. Calling memcpy() (on ARMv7 targets that utilize the GNU glibc implementation) with a negative value for the 'num' parameter results in a signed comparison vulnerability. If an attacker underflows the 'num' parameter to memcpy(), this vulnerability could lead to undefined behavior such as writing to out-of-bounds memory and potentially remote code execution. Furthermore, this memcpy() implementation allows for program execution to continue in scenarios where a segmentation fault or crash should have occurred. The dangers occur in that subsequent execution and iterations of this code will be executed with this corrupted data.

Remediation

Upgrade Debian:unstable glibc to version 2.31-2 or higher.

References

low severity

Out-of-bounds Write

  • Vulnerable module: lz4/liblz4-1
  • Introduced through: lz4/liblz4-1@1.8.2-1
  • Fixed in: 1.9.2-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim lz4/liblz4-1@1.8.2-1

NVD Description

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

LZ4 before 1.9.2 has a heap-based buffer overflow in LZ4_write32 (related to LZ4_compress_destSize), affecting applications that call LZ4_compress_fast with a large input. (This issue can also lead to data corruption.) NOTE: the vendor states "only a few specific / uncommon usages of the API are at risk."

Remediation

Upgrade Debian:unstable lz4 to version 1.9.2-1 or higher.

References

low severity

Improper Certificate Validation

  • Vulnerable module: perl/perl-base
  • Introduced through: perl/perl-base@5.28.0-3
  • Fixed in: 5.38.2-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim perl/perl-base@5.28.0-3

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:unstable 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

Upgrade Debian:unstable perl to version 5.38.2-2 or higher.

References

low severity

Improper Check for Dropped Privileges

  • Vulnerable module: bash
  • Introduced through: bash@4.4.18-3.1
  • Fixed in: 5.1~rc1-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim bash@4.4.18-3.1

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

An issue was discovered in disable_priv_mode in shell.c in GNU Bash through 5.0 patch 11. By default, if Bash is run with its effective UID not equal to its real UID, it will drop privileges by setting its effective UID to its real UID. However, it does so incorrectly. On Linux and other systems that support "saved UID" functionality, the saved UID is not dropped. An attacker with command execution in the shell can use "enable -f" for runtime loading of a new builtin, which can be a shared object that calls setuid() and therefore regains privileges. However, binaries running with an effective UID of 0 are unaffected.

Remediation

Upgrade Debian:unstable bash to version 5.1~rc1-2 or higher.

References

low severity

Out-of-bounds Write

  • Vulnerable module: freetype/libfreetype6
  • Introduced through: freetype/libfreetype6@2.8.1-2
  • Fixed in: 2.12.1+dfsg-3

Detailed paths

  • Introduced through: tomcat@8-jre10-slim freetype/libfreetype6@2.8.1-2

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

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

Remediation

Upgrade Debian:unstable freetype to version 2.12.1+dfsg-3 or higher.

References

low severity

Improper Resource Shutdown or Release

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.28-6

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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

The string component in the GNU C Library (aka glibc or libc6) through 2.28, when running on the x32 architecture, incorrectly attempts to use a 64-bit register for size_t in assembly codes, which can lead to a segmentation fault or possibly unspecified other impact, as demonstrated by a crash in __memmove_avx_unaligned_erms in sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S during a memcpy.

Remediation

Upgrade Debian:unstable glibc to version 2.28-6 or higher.

References

low severity

Out-of-bounds Write

  • Vulnerable module: libjpeg-turbo/libjpeg62-turbo
  • Introduced through: libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+b1
  • Fixed in: 1:2.0.5-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+b1

NVD Description

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

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

Remediation

Upgrade Debian:unstable libjpeg-turbo to version 1:2.0.5-1 or higher.

References

low severity

Out-of-Bounds

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.39-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim nss/libnss3@2:3.39-1

NVD Description

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

Heap-based buffer overflow in the __get_page function in lib/dbm/src/h_page.c in Mozilla Network Security Services (NSS) allows context-dependent attackers to have unspecified impact using a crafted cert8.db file.

Remediation

There is no fixed version for Debian:unstable nss.

References

low severity

Out-of-Bounds

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.39-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim nss/libnss3@2:3.39-1

NVD Description

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

The __hash_open function in hash.c:229 in Mozilla Network Security Services (NSS) allows context-dependent attackers to cause a denial of service (floating point exception and crash) via a crafted cert8.db file.

Remediation

There is no fixed version for Debian:unstable nss.

References

low severity

Out-of-Bounds

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.39-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim nss/libnss3@2:3.39-1

NVD Description

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

Heap-based buffer overflow in the __hash_open function in lib/dbm/src/hash.c in Mozilla Network Security Services (NSS) allows context-dependent attackers to have unspecified impact using a crafted cert8.db file.

Remediation

There is no fixed version for Debian:unstable nss.

References

low severity

Out-of-Bounds

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.39-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim nss/libnss3@2:3.39-1

NVD Description

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

Heap-based buffer overflow in the alloc_segs function in lib/dbm/src/hash.c in Mozilla Network Security Services (NSS) allows context-dependent attackers to have unspecified impact using a crafted cert8.db file.

Remediation

There is no fixed version for Debian:unstable nss.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: tomcat@8-jre10-slim pcre3/libpcre3@2:8.39-11

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:unstable 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:unstable pcre3.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: tomcat@8-jre10-slim pcre3/libpcre3@2:8.39-11

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:unstable 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:unstable pcre3.

References

low severity

Incorrect Permission Assignment for Critical Resource

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

Detailed paths

  • Introduced through: tomcat@8-jre10-slim shadow/login@1:4.5-1.1
  • Introduced through: tomcat@8-jre10-slim shadow/passwd@1:4.5-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:unstable 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:unstable shadow.

References

low severity

CVE-2021-43396

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.32-5

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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

In iconvdata/iso-2022-jp-3.c in the GNU C Library (aka glibc) 2.34, remote attackers can force iconv() to emit a spurious '\0' character via crafted ISO-2022-JP-3 data that is accompanied by an internal state reset. This may affect data integrity in certain iconv() use cases. NOTE: the vendor states "the bug cannot be invoked through user input and requires iconv to be invoked with a NULL inbuf, which ought to require a separate application bug to do so unintentionally. Hence there's no security impact to the bug.

Remediation

Upgrade Debian:unstable glibc to version 2.32-5 or higher.

References

low severity

Uncontrolled Recursion

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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:unstable 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:unstable glibc.

References

low severity

Uncontrolled Recursion

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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:unstable 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:unstable glibc.

References

low severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: gnupg2/gpgv
  • Introduced through: gnupg2/gpgv@2.2.10-3
  • Fixed in: 2.2.19-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim gnupg2/gpgv@2.2.10-3

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

A flaw was found in the way certificate signatures could be forged using collisions found in the SHA-1 algorithm. An attacker could use this weakness to create forged certificate signatures. This issue affects GnuPG versions before 2.2.18.

Remediation

Upgrade Debian:unstable gnupg2 to version 2.2.19-1 or higher.

References

low severity

Integer Overflow or Wraparound

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.16.1-1, krb5/libk5crypto3@1.16.1-1 and others

Detailed paths

  • Introduced through: tomcat@8-jre10-slim krb5/libgssapi-krb5-2@1.16.1-1
  • Introduced through: tomcat@8-jre10-slim krb5/libk5crypto3@1.16.1-1
  • Introduced through: tomcat@8-jre10-slim krb5/libkrb5-3@1.16.1-1
  • Introduced through: tomcat@8-jre10-slim krb5/libkrb5support0@1.16.1-1

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:unstable 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:unstable krb5.

References

low severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: libgcrypt20
  • Introduced through: libgcrypt20@1.8.4-3

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libgcrypt20@1.8.4-3

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:unstable 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:unstable libgcrypt20.

References

low severity

Excessive Iteration

  • Vulnerable module: libjpeg-turbo/libjpeg62-turbo
  • Introduced through: libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+b1
  • Fixed in: 1:2.0.5-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+b1

NVD Description

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

libjpeg 9c has a large loop because read_pixel in rdtarga.c mishandles EOF.

Remediation

Upgrade Debian:unstable libjpeg-turbo to version 1:2.0.5-1 or higher.

References

low severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: tomcat@8-jre10-slim pcre3/libpcre3@2:8.39-11

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:unstable 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:unstable pcre3.

References

low severity

Uncontrolled Recursion

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

Detailed paths

  • Introduced through: tomcat@8-jre10-slim pcre3/libpcre3@2:8.39-11

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:unstable 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:unstable pcre3.

References

low severity

Link Following

  • Vulnerable module: perl/perl-base
  • Introduced through: perl/perl-base@5.28.0-3

Detailed paths

  • Introduced through: tomcat@8-jre10-slim perl/perl-base@5.28.0-3

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:unstable 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:unstable perl.

References

low severity

CVE-2019-19244

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1
  • Fixed in: 3.30.1+fossil191229-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim sqlite3/libsqlite3-0@3.25.3-1

NVD Description

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

sqlite3Select in select.c in SQLite 3.30.1 allows a crash if a sub-select uses both DISTINCT and window functions, and also has certain ORDER BY usage.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.30.1+fossil191229-1 or higher.

References

low severity

Improper Validation of Array Index

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1
  • Fixed in: 3.39.2-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim sqlite3/libsqlite3-0@3.25.3-1

NVD Description

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

SQLite 1.0.12 through 3.39.x before 3.39.2 sometimes allows an array-bounds overflow if billions of bytes are used in a string argument to a C API.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.39.2-1 or higher.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1
  • Fixed in: 3.27.2-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim sqlite3/libsqlite3-0@3.25.3-1

NVD Description

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

In SQLite 3.27.2, interleaving reads and writes in a single transaction with an fts5 virtual table will lead to a NULL Pointer Dereference in fts5ChunkIterate in sqlite3.c. This is related to ext/fts5/fts5_hash.c and ext/fts5/fts5_index.c.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.27.2-2 or higher.

References

low severity

Out-of-bounds Read

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1
  • Fixed in: 3.36.0-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim sqlite3/libsqlite3-0@3.25.3-1

NVD Description

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

A segmentation fault can occur in the sqlite3.exe command-line component of SQLite 3.36.0 via the idxGetTableInfo function when there is a crafted SQL query. NOTE: the vendor disputes the relevance of this report because a sqlite3.exe user already has full privileges (e.g., is intentionally allowed to execute commands). This report does NOT imply any problem in the SQLite library.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.36.0-2 or higher.

References

low severity

Out-of-bounds Read

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1
  • Fixed in: 3.27.2-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim sqlite3/libsqlite3-0@3.25.3-1

NVD Description

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

In SQLite 3.27.2, running fts5 prefix queries inside a transaction could trigger a heap-based buffer over-read in fts5HashEntrySort in sqlite3.c, which may lead to an information leak. This is related to ext/fts5/fts5_hash.c.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.27.2-2 or higher.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: tar
  • Introduced through: tar@1.30+dfsg-2
  • Fixed in: 1.32+dfsg-1

low severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 1.1.1c-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

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

Remediation

Upgrade Debian:unstable openssl to version 1.1.1c-1 or higher.

References

low severity

Improper Input Validation

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@239-11 and systemd/libudev1@239-11
  • Fixed in: 246-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim systemd/libsystemd0@239-11
  • Introduced through: tomcat@8-jre10-slim systemd/libudev1@239-11

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

systemd through v245 mishandles numerical usernames such as ones composed of decimal digits or 0x followed by hex digits, as demonstrated by use of root privileges when privileges of the 0x0 user account were intended. NOTE: this issue exists because of an incomplete fix for CVE-2017-1000082.

Remediation

Upgrade Debian:unstable systemd to version 246-2 or higher.

References

low severity

Improper Input Validation

  • Vulnerable module: coreutils
  • Introduced through: coreutils@8.30-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim coreutils@8.30-1

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:unstable 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:unstable coreutils.

References

low severity

Divide By Zero

  • Vulnerable module: libjpeg-turbo/libjpeg62-turbo
  • Introduced through: libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+b1
  • Fixed in: 1:2.0.5-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+b1

NVD Description

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

libjpeg-turbo 1.5.90 is vulnerable to a denial of service vulnerability caused by a divide by zero when processing a crafted BMP image.

Remediation

Upgrade Debian:unstable libjpeg-turbo to version 1:2.0.5-1 or higher.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: libjpeg-turbo/libjpeg62-turbo
  • Introduced through: libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+b1
  • Fixed in: 1:2.0.5-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+b1

NVD Description

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

libjpeg-turbo 1.5.2 has a NULL Pointer Dereference in jdpostct.c and jquant1.c via a crafted JPEG file.

Remediation

Upgrade Debian:unstable libjpeg-turbo to version 1:2.0.5-1 or higher.

References

low severity

Out-of-bounds Read

  • Vulnerable module: libjpeg-turbo/libjpeg62-turbo
  • Introduced through: libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+b1
  • Fixed in: 1:2.0.5-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+b1

NVD Description

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

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

Remediation

Upgrade Debian:unstable libjpeg-turbo to version 1:2.0.5-1 or higher.

References

low severity

CVE-2018-14048

  • Vulnerable module: libpng1.6/libpng16-16
  • Introduced through: libpng1.6/libpng16-16@1.6.34-2
  • Fixed in: 1.6.37-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libpng1.6/libpng16-16@1.6.34-2

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

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

Remediation

Upgrade Debian:unstable libpng1.6 to version 1.6.37-1 or higher.

References

low severity

Memory Leak

  • Vulnerable module: libpng1.6/libpng16-16
  • Introduced through: libpng1.6/libpng16-16@1.6.34-2
  • Fixed in: 1.6.39-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libpng1.6/libpng16-16@1.6.34-2

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:unstable 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

Upgrade Debian:unstable libpng1.6 to version 1.6.39-1 or higher.

References

low severity

XML External Entity (XXE) Injection

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-1
  • Fixed in: 2.4.1-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim expat/libexpat1@2.2.6-1

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:unstable 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

Upgrade Debian:unstable expat to version 2.4.1-2 or higher.

References

low severity

Access Restriction Bypass

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

Detailed paths

  • Introduced through: tomcat@8-jre10-slim shadow/login@1:4.5-1.1
  • Introduced through: tomcat@8-jre10-slim shadow/passwd@1:4.5-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:unstable 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:unstable shadow.

References

low severity

Authentication Bypass

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@239-11 and systemd/libudev1@239-11
  • Fixed in: 249.4-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim systemd/libsystemd0@239-11
  • Introduced through: tomcat@8-jre10-slim systemd/libudev1@239-11

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:unstable 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

Upgrade Debian:unstable systemd to version 249.4-2 or higher.

References

low severity

Improper Data Handling

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.28-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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

The pop_fail_stack function in the GNU C Library (aka glibc or libc6) allows context-dependent attackers to cause a denial of service (assertion failure and application crash) via vectors related to extended regular expression processing.

Remediation

Upgrade Debian:unstable glibc to version 2.28-1 or higher.

References

low severity

Improper Input Validation

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.31-3

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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

The iconv program in the GNU C Library (aka glibc or libc6) 2.31 and earlier, when invoked with multiple suffixes in the destination encoding (TRANSLATE or IGNORE) along with the -c option, enters an infinite loop when processing invalid multi-byte input sequences, leading to a denial of service.

Remediation

Upgrade Debian:unstable glibc to version 2.31-3 or higher.

References

low severity

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

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-1
  • Fixed in: 2.6.0-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim expat/libexpat1@2.2.6-1

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

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

Remediation

Upgrade Debian:unstable expat to version 2.6.0-1 or higher.

References

low severity

CVE-2019-7309

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.28-6

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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

In the GNU C Library (aka glibc or libc6) through 2.29, the memcmp function for the x32 architecture can incorrectly return zero (indicating that the inputs are equal) because the RDX most significant bit is mishandled.

Remediation

Upgrade Debian:unstable glibc to version 2.28-6 or higher.

References

low severity

Buffer Overflow

  • Vulnerable module: libpng1.6/libpng16-16
  • Introduced through: libpng1.6/libpng16-16@1.6.34-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libpng1.6/libpng16-16@1.6.34-2

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:unstable 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:unstable libpng1.6.

References

low severity

CVE-2018-1000654

  • Vulnerable module: libtasn1-6
  • Introduced through: libtasn1-6@4.13-3
  • Fixed in: 4.14-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libtasn1-6@4.13-3

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

GNU Libtasn1-4.13 libtasn1-4.13 version libtasn1-4.13, libtasn1-4.12 contains a DoS, specifically CPU usage will reach 100% when running asn1Paser against the POC due to an issue in _asn1_expand_object_id(p_tree), after a long time, the program will be killed. This attack appears to be exploitable via parsing a crafted file.

Remediation

Upgrade Debian:unstable libtasn1-6 to version 4.14-2 or higher.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: tomcat@8-jre10-slim pcre3/libpcre3@2:8.39-11

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:unstable 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:unstable pcre3.

References

low severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: tomcat@8-jre10-slim tar@1.30+dfsg-2

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

A flaw was found in the src/list.c of tar 1.33 and earlier. This flaw allows an attacker who can submit a crafted input file to tar to cause uncontrolled consumption of memory. The highest threat from this vulnerability is to system availability.

Remediation

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

References

low severity

Out-of-bounds Read

  • Vulnerable module: tar
  • Introduced through: tar@1.30+dfsg-2
  • Fixed in: 1.34+dfsg-1.4

Detailed paths

  • Introduced through: tomcat@8-jre10-slim tar@1.30+dfsg-2

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:unstable 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:unstable tar to version 1.34+dfsg-1.4 or higher.

References

low severity

Information Exposure

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.32.1-0.2, util-linux/fdisk@2.32.1-0.2 and others

Detailed paths

  • Introduced through: tomcat@8-jre10-slim util-linux@2.32.1-0.2
  • Introduced through: tomcat@8-jre10-slim util-linux/fdisk@2.32.1-0.2
  • Introduced through: tomcat@8-jre10-slim util-linux/libblkid1@2.32.1-0.2
  • Introduced through: tomcat@8-jre10-slim util-linux/libfdisk1@2.32.1-0.2
  • Introduced through: tomcat@8-jre10-slim util-linux/libmount1@2.32.1-0.2
  • Introduced through: tomcat@8-jre10-slim util-linux/libsmartcols1@2.32.1-0.2
  • Introduced through: tomcat@8-jre10-slim util-linux/libuuid1@2.32.1-0.2
  • Introduced through: tomcat@8-jre10-slim util-linux/mount@2.32.1-0.2
  • Introduced through: tomcat@8-jre10-slim util-linux/bsdutils@1:2.32.1-0.2

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:unstable 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:unstable util-linux.

References

low severity

Integer Overflow or Wraparound

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.32.1-0.2, util-linux/fdisk@2.32.1-0.2 and others
  • Fixed in: 2.36.1-8

Detailed paths

  • Introduced through: tomcat@8-jre10-slim util-linux@2.32.1-0.2
  • Introduced through: tomcat@8-jre10-slim util-linux/fdisk@2.32.1-0.2
  • Introduced through: tomcat@8-jre10-slim util-linux/libblkid1@2.32.1-0.2
  • Introduced through: tomcat@8-jre10-slim util-linux/libfdisk1@2.32.1-0.2
  • Introduced through: tomcat@8-jre10-slim util-linux/libmount1@2.32.1-0.2
  • Introduced through: tomcat@8-jre10-slim util-linux/libsmartcols1@2.32.1-0.2
  • Introduced through: tomcat@8-jre10-slim util-linux/libuuid1@2.32.1-0.2
  • Introduced through: tomcat@8-jre10-slim util-linux/mount@2.32.1-0.2

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

An integer overflow in util-linux through 2.37.1 can potentially cause a buffer overflow if an attacker were able to use system resources in a way that leads to a large number in the /proc/sysvipc/sem file. NOTE: this is unexploitable in GNU C Library environments, and possibly in all realistic environments.

Remediation

Upgrade Debian:unstable util-linux to version 2.36.1-8 or higher.

References

low severity

Out-of-bounds Read

  • Vulnerable module: ncurses/libncursesw6
  • Introduced through: ncurses/libncursesw6@6.1+20181013-1, ncurses/libtinfo6@6.1+20181013-1 and others
  • Fixed in: 6.1+20191019-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim ncurses/libncursesw6@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/libtinfo6@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/ncurses-base@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/ncurses-bin@6.1+20181013-1

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

There is a heap-based buffer over-read in the fmt_entry function in tinfo/comp_hash.c in the terminfo library in ncurses before 6.1-20191012.

Remediation

Upgrade Debian:unstable ncurses to version 6.1+20191019-1 or higher.

References

low severity

Information Exposure

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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:unstable 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:unstable glibc.

References

low severity

Use of Insufficiently Random Values

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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:unstable 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:unstable glibc.

References

low severity

Reachable Assertion

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.16.1-1, krb5/libk5crypto3@1.16.1-1 and others
  • Fixed in: 1.16.2-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim krb5/libgssapi-krb5-2@1.16.1-1
  • Introduced through: tomcat@8-jre10-slim krb5/libk5crypto3@1.16.1-1
  • Introduced through: tomcat@8-jre10-slim krb5/libkrb5-3@1.16.1-1
  • Introduced through: tomcat@8-jre10-slim krb5/libkrb5support0@1.16.1-1

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

A Reachable Assertion issue was discovered in the KDC in MIT Kerberos 5 (aka krb5) before 1.17. If an attacker can obtain a krbtgt ticket using an older encryption type (single-DES, triple-DES, or RC4), the attacker can crash the KDC by making an S4U2Self request.

Remediation

Upgrade Debian:unstable krb5 to version 1.16.2-1 or higher.

References

low severity

Out-of-bounds Read

  • Vulnerable module: ncurses/libncursesw6
  • Introduced through: ncurses/libncursesw6@6.1+20181013-1, ncurses/libtinfo6@6.1+20181013-1 and others
  • Fixed in: 6.1+20191019-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim ncurses/libncursesw6@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/libtinfo6@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/ncurses-base@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/ncurses-bin@6.1+20181013-1

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

There is a heap-based buffer over-read in the _nc_find_entry function in tinfo/comp_hash.c in the terminfo library in ncurses before 6.1-20191012.

Remediation

Upgrade Debian:unstable ncurses to version 6.1+20191019-1 or higher.

References

low severity

Information Exposure

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 1.1.1e-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

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

Remediation

Upgrade Debian:unstable openssl to version 1.1.1e-1 or higher.

References

low severity

Incorrect Permission Assignment for Critical Resource

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.5-1.1 and shadow/passwd@1:4.5-1.1
  • Fixed in: 1:4.7-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim shadow/login@1:4.5-1.1
  • Introduced through: tomcat@8-jre10-slim shadow/passwd@1:4.5-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:unstable relevant fixed versions and status.

An issue was discovered in shadow 4.5. newgidmap (in shadow-utils) is setuid and allows an unprivileged user to be placed in a user namespace where setgroups(2) is permitted. This allows an attacker to remove themselves from a supplementary group, which may allow access to certain filesystem paths if the administrator has used "group blacklisting" (e.g., chmod g-rwx) to restrict access to paths. This flaw effectively reverts a security feature in the kernel (in particular, the /proc/self/setgroups knob) to prevent this sort of privilege escalation.

Remediation

Upgrade Debian:unstable shadow to version 1:4.7-1 or higher.

References

low severity

Improper Validation of Integrity Check Value

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@239-11 and systemd/libudev1@239-11

Detailed paths

  • Introduced through: tomcat@8-jre10-slim systemd/libsystemd0@239-11
  • Introduced through: tomcat@8-jre10-slim systemd/libudev1@239-11

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:unstable 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:unstable systemd.

References

low severity

Improper Validation of Integrity Check Value

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@239-11 and systemd/libudev1@239-11

Detailed paths

  • Introduced through: tomcat@8-jre10-slim systemd/libsystemd0@239-11
  • Introduced through: tomcat@8-jre10-slim systemd/libudev1@239-11

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:unstable 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:unstable systemd.

References

low severity

Improper Validation of Integrity Check Value

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@239-11 and systemd/libudev1@239-11

Detailed paths

  • Introduced through: tomcat@8-jre10-slim systemd/libsystemd0@239-11
  • Introduced through: tomcat@8-jre10-slim systemd/libudev1@239-11

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:unstable 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:unstable systemd.

References

low severity

Race Condition

  • Vulnerable module: coreutils
  • Introduced through: coreutils@8.30-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim coreutils@8.30-1

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:unstable 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:unstable coreutils.

References

low severity

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

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.5-1.1 and shadow/passwd@1:4.5-1.1
  • Fixed in: 1:4.12.3+dfsg1-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim shadow/login@1:4.5-1.1
  • Introduced through: tomcat@8-jre10-slim shadow/passwd@1:4.5-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:unstable relevant fixed versions and status.

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

Remediation

Upgrade Debian:unstable shadow to version 1:4.12.3+dfsg1-1 or higher.

References

low severity

Link Following

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@239-11 and systemd/libudev1@239-11

Detailed paths

  • Introduced through: tomcat@8-jre10-slim systemd/libsystemd0@239-11
  • Introduced through: tomcat@8-jre10-slim systemd/libudev1@239-11

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:unstable 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:unstable systemd.

References

low severity

Resource Management Errors

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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:unstable 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:unstable glibc.

References

low severity

Improper Input Validation

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.19-1+b1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim gnutls28/libgnutls30@3.5.19-1+b1

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:unstable 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:unstable gnutls28.

References

low severity

Memory Leak

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.25.3-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim sqlite3/libsqlite3-0@3.25.3-1

NVD Description

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

A Memory Leak vulnerability exists in SQLite Project SQLite3 3.35.1 and 3.37.0 via maliciously crafted SQL Queries (made via editing the Database File), it is possible to query a record, and leak subsequent bytes of memory that extend beyond the record, which could let a malicious user obtain sensitive information. NOTE: The developer disputes this as a vulnerability stating that If you give SQLite a corrupted database file and submit a query against the database, it might read parts of the database that you did not intend or expect.

Remediation

There is no fixed version for Debian:unstable sqlite3.

References

low severity

Improper Verification of Cryptographic Signature

  • Vulnerable module: apt
  • Introduced through: apt@1.7.0 and apt/libapt-pkg5.0@1.7.0

Detailed paths

  • Introduced through: tomcat@8-jre10-slim apt@1.7.0
  • Introduced through: tomcat@8-jre10-slim apt/libapt-pkg5.0@1.7.0

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:unstable 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:unstable apt.

References

low severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 1.1.1d-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

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

Remediation

Upgrade Debian:unstable openssl to version 1.1.1d-1 or higher.

References

low severity

Buffer Overflow

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.8-5
  • Fixed in: 2.3.1-12

Detailed paths

  • Introduced through: tomcat@8-jre10-slim cups/libcups2@2.2.8-5

NVD Description

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

A buffer overflow was addressed with improved bounds checking. This issue is fixed in macOS Catalina 10.15.2, Security Update 2019-002 Mojave, and Security Update 2019-007 High Sierra. In certain configurations, a remote attacker may be able to submit arbitrary print jobs.

Remediation

Upgrade Debian:unstable cups to version 2.3.1-12 or higher.

References

low severity

Information Exposure

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.29-8

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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

On the x86-64 architecture, the GNU C Library (aka glibc) before 2.31 fails to ignore the LD_PREFER_MAP_32BIT_EXEC environment variable during program execution after a security transition, allowing local attackers to restrict the possible mapping addresses for loaded libraries and thus bypass ASLR for a setuid program.

Remediation

Upgrade Debian:unstable glibc to version 2.29-8 or higher.

References

low severity

Out-of-bounds Write

  • Vulnerable module: gnupg2/gpgv
  • Introduced through: gnupg2/gpgv@2.2.10-3

Detailed paths

  • Introduced through: tomcat@8-jre10-slim gnupg2/gpgv@2.2.10-3

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:unstable 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:unstable gnupg2.

References

low severity

Out-of-bounds Read

  • Vulnerable module: libsepol/libsepol1
  • Introduced through: libsepol/libsepol1@2.8-1
  • Fixed in: 3.3-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libsepol/libsepol1@2.8-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:unstable 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

Upgrade Debian:unstable libsepol to version 3.3-1 or higher.

References

low severity

Use After Free

  • Vulnerable module: libsepol/libsepol1
  • Introduced through: libsepol/libsepol1@2.8-1
  • Fixed in: 3.3-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libsepol/libsepol1@2.8-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:unstable 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

Upgrade Debian:unstable libsepol to version 3.3-1 or higher.

References

low severity

Use After Free

  • Vulnerable module: libsepol/libsepol1
  • Introduced through: libsepol/libsepol1@2.8-1
  • Fixed in: 3.3-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libsepol/libsepol1@2.8-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:unstable 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

Upgrade Debian:unstable libsepol to version 3.3-1 or higher.

References

low severity

Use After Free

  • Vulnerable module: libsepol/libsepol1
  • Introduced through: libsepol/libsepol1@2.8-1
  • Fixed in: 3.3-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libsepol/libsepol1@2.8-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:unstable 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

Upgrade Debian:unstable libsepol to version 3.3-1 or higher.

References

low severity

Arbitrary Code Injection

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.5-1.1 and shadow/passwd@1:4.5-1.1
  • Fixed in: 1:4.13+dfsg1-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim shadow/login@1:4.5-1.1
  • Introduced through: tomcat@8-jre10-slim shadow/passwd@1:4.5-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:unstable 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

Upgrade Debian:unstable shadow to version 1:4.13+dfsg1-2 or higher.

References

low severity

Out-of-bounds Read

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@239-11 and systemd/libudev1@239-11
  • Fixed in: 240-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim systemd/libsystemd0@239-11
  • Introduced through: tomcat@8-jre10-slim systemd/libudev1@239-11

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

An out of bounds read was discovered in systemd-journald in the way it parses log messages that terminate with a colon ':'. A local attacker can use this flaw to disclose process memory data. Versions from v221 to v239 are vulnerable.

Remediation

Upgrade Debian:unstable systemd to version 240-1 or higher.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: unzip
  • Introduced through: unzip@6.0-21

Detailed paths

  • Introduced through: tomcat@8-jre10-slim unzip@6.0-21

NVD Description

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

A flaw was found in unzip. The vulnerability occurs due to improper handling of Unicode strings, which can lead to a null pointer dereference. This flaw allows an attacker to input a specially crafted zip file, leading to a crash or code execution.

Remediation

There is no fixed version for Debian:unstable unzip.

References

low severity

Resource Exhaustion

  • Vulnerable module: unzip
  • Introduced through: unzip@6.0-21
  • Fixed in: 6.0-24

Detailed paths

  • Introduced through: tomcat@8-jre10-slim unzip@6.0-21

NVD Description

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

Info-ZIP UnZip 6.0 mishandles the overlapping of files inside a ZIP container, leading to denial of service (resource consumption), aka a "better zip bomb" issue.

Remediation

Upgrade Debian:unstable unzip to version 6.0-24 or higher.

References

low severity

Double Free

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.31-10

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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

The nameserver caching daemon (nscd) in the GNU C Library (aka glibc or libc6) 2.29 through 2.33, when processing a request for netgroup lookup, may crash due to a double-free, potentially resulting in degraded service or Denial of Service on the local system. This is related to netgroupcache.c.

Remediation

Upgrade Debian:unstable glibc to version 2.31-10 or higher.

References

low severity

Missing Release of Resource after Effective Lifetime

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@239-11 and systemd/libudev1@239-11
  • Fixed in: 243-5

Detailed paths

  • Introduced through: tomcat@8-jre10-slim systemd/libsystemd0@239-11
  • Introduced through: tomcat@8-jre10-slim systemd/libudev1@239-11

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

An issue was discovered in button_open in login/logind-button.c in systemd before 243. When executing the udevadm trigger command, a memory leak may occur.

Remediation

Upgrade Debian:unstable systemd to version 243-5 or higher.

References

low severity

CVE-2024-35235

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.8-5
  • Fixed in: 2.4.7-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim cups/libcups2@2.2.8-5

NVD Description

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

OpenPrinting CUPS is an open source printing system for Linux and other Unix-like operating systems. In versions 2.4.8 and earlier, when starting the cupsd server with a Listen configuration item pointing to a symbolic link, the cupsd process can be caused to perform an arbitrary chmod of the provided argument, providing world-writable access to the target. Given that cupsd is often running as root, this can result in the change of permission of any user or system files to be world writable. Given the aforementioned Ubuntu AppArmor context, on such systems this vulnerability is limited to those files modifiable by the cupsd process. In that specific case it was found to be possible to turn the configuration of the Listen argument into full control over the cupsd.conf and cups-files.conf configuration files. By later setting the User and Group arguments in cups-files.conf, and printing with a printer configured by PPD with a FoomaticRIPCommandLine argument, arbitrary user and group (not root) command execution could be achieved, which can further be used on Ubuntu systems to achieve full root command execution. Commit ff1f8a623e090dee8a8aadf12a6a4b25efac143d contains a patch for the issue.

Remediation

Upgrade Debian:unstable cups to version 2.4.7-2 or higher.

References

low severity

CVE-2024-28757

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-1
  • Fixed in: 2.6.1-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim expat/libexpat1@2.2.6-1

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:unstable 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

Upgrade Debian:unstable expat to version 2.6.1-2 or higher.

References

low severity

CVE-2024-2961

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.37-18

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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

The iconv() function in the GNU C Library versions 2.39 and older may overflow the output buffer passed to it by up to 4 bytes when converting strings to the ISO-2022-CN-EXT character set, which may be used to crash an application or overwrite a neighbouring variable.

Remediation

Upgrade Debian:unstable glibc to version 2.37-18 or higher.

References

low severity

CVE-2024-33599

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.37-19

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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

nscd: Stack-based buffer overflow in netgroup cache

If the Name Service Cache Daemon's (nscd) fixed size cache is exhausted by client requests then a subsequent client request for netgroup data may result in a stack-based buffer overflow. This flaw was introduced in glibc 2.15 when the cache was added to nscd.

This vulnerability is only present in the nscd binary.

Remediation

Upgrade Debian:unstable glibc to version 2.37-19 or higher.

References

low severity

CVE-2024-33600

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.37-19

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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

nscd: Null pointer crashes after notfound response

If the Name Service Cache Daemon's (nscd) cache fails to add a not-found netgroup response to the cache, the client request can result in a null pointer dereference. This flaw was introduced in glibc 2.15 when the cache was added to nscd.

This vulnerability is only present in the nscd binary.

Remediation

Upgrade Debian:unstable glibc to version 2.37-19 or higher.

References

low severity

CVE-2024-33601

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.37-19

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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

nscd: netgroup cache may terminate daemon on memory allocation failure

The Name Service Cache Daemon's (nscd) netgroup cache uses xmalloc or xrealloc and these functions may terminate the process due to a memory allocation failure resulting in a denial of service to the clients. The flaw was introduced in glibc 2.15 when the cache was added to nscd.

This vulnerability is only present in the nscd binary.

Remediation

Upgrade Debian:unstable glibc to version 2.37-19 or higher.

References

low severity

CVE-2024-33602

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-8 and glibc/libc6@2.27-8
  • Fixed in: 2.37-19

Detailed paths

  • Introduced through: tomcat@8-jre10-slim glibc/libc-bin@2.27-8
  • Introduced through: tomcat@8-jre10-slim glibc/libc6@2.27-8

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

nscd: netgroup cache assumes NSS callback uses in-buffer strings

The Name Service Cache Daemon's (nscd) netgroup cache can corrupt memory when the NSS callback does not store all strings in the provided buffer. The flaw was introduced in glibc 2.15 when the cache was added to nscd.

This vulnerability is only present in the nscd binary.

Remediation

Upgrade Debian:unstable glibc to version 2.37-19 or higher.

References

low severity

Information Exposure

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.19-1+b1
  • Fixed in: 3.8.4-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim gnutls28/libgnutls30@3.5.19-1+b1

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:unstable 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

Upgrade Debian:unstable gnutls28 to version 3.8.4-2 or higher.

References

low severity

Uncaught Exception

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.19-1+b1
  • Fixed in: 3.8.4-2

Detailed paths

  • Introduced through: tomcat@8-jre10-slim gnutls28/libgnutls30@3.5.19-1+b1

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:unstable 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

Upgrade Debian:unstable gnutls28 to version 3.8.4-2 or higher.

References

low severity

CVE-2024-26458

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.16.1-1, krb5/libk5crypto3@1.16.1-1 and others

Detailed paths

  • Introduced through: tomcat@8-jre10-slim krb5/libgssapi-krb5-2@1.16.1-1
  • Introduced through: tomcat@8-jre10-slim krb5/libk5crypto3@1.16.1-1
  • Introduced through: tomcat@8-jre10-slim krb5/libkrb5-3@1.16.1-1
  • Introduced through: tomcat@8-jre10-slim krb5/libkrb5support0@1.16.1-1

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:unstable 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:unstable krb5.

References

low severity

CVE-2024-26461

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.16.1-1, krb5/libk5crypto3@1.16.1-1 and others

Detailed paths

  • Introduced through: tomcat@8-jre10-slim krb5/libgssapi-krb5-2@1.16.1-1
  • Introduced through: tomcat@8-jre10-slim krb5/libk5crypto3@1.16.1-1
  • Introduced through: tomcat@8-jre10-slim krb5/libkrb5-3@1.16.1-1
  • Introduced through: tomcat@8-jre10-slim krb5/libkrb5support0@1.16.1-1

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:unstable 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:unstable krb5.

References

low severity

CVE-2024-26462

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.16.1-1, krb5/libk5crypto3@1.16.1-1 and others

Detailed paths

  • Introduced through: tomcat@8-jre10-slim krb5/libgssapi-krb5-2@1.16.1-1
  • Introduced through: tomcat@8-jre10-slim krb5/libk5crypto3@1.16.1-1
  • Introduced through: tomcat@8-jre10-slim krb5/libkrb5-3@1.16.1-1
  • Introduced through: tomcat@8-jre10-slim krb5/libkrb5support0@1.16.1-1

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:unstable 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:unstable krb5.

References

low severity

Information Exposure

  • Vulnerable module: libgcrypt20
  • Introduced through: libgcrypt20@1.8.4-3

Detailed paths

  • Introduced through: tomcat@8-jre10-slim libgcrypt20@1.8.4-3

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:unstable 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:unstable libgcrypt20.

References

low severity

CVE-2023-45918

  • Vulnerable module: ncurses/libncursesw6
  • Introduced through: ncurses/libncursesw6@6.1+20181013-1, ncurses/libtinfo6@6.1+20181013-1 and others
  • Fixed in: 6.4+20230625-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim ncurses/libncursesw6@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/libtinfo6@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/ncurses-base@6.1+20181013-1
  • Introduced through: tomcat@8-jre10-slim ncurses/ncurses-bin@6.1+20181013-1

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

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

Remediation

Upgrade Debian:unstable ncurses to version 6.4+20230625-1 or higher.

References

low severity

CVE-2023-5388

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.39-1
  • Fixed in: 2:3.98-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim nss/libnss3@2:3.39-1

NVD Description

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

NSS was susceptible to a timing side-channel attack when performing RSA decryption. This attack could potentially allow an attacker to recover the private data. This vulnerability affects Firefox < 124, Firefox ESR < 115.9, and Thunderbird < 115.9.

Remediation

Upgrade Debian:unstable nss to version 2:3.98-1 or higher.

References

low severity

CVE-2024-6602

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.39-1
  • Fixed in: 2:3.101-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim nss/libnss3@2:3.39-1

NVD Description

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

A mismatch between allocator and deallocator could have lead to memory corruption. This vulnerability affects Firefox < 128, Firefox ESR < 115.13, Thunderbird < 115.13, and Thunderbird < 128.

Remediation

Upgrade Debian:unstable nss to version 2:3.101-1 or higher.

References

low severity

CVE-2023-6237

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 3.1.5-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

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

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

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

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

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

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

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

Remediation

Upgrade Debian:unstable openssl to version 3.1.5-1 or higher.

References

low severity

CVE-2024-2511

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 3.2.2-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

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

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

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

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

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

Remediation

Upgrade Debian:unstable openssl to version 3.2.2-1 or higher.

References

low severity

CVE-2024-4603

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 3.2.2-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

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

Impact summary: Applications that use the functions EVP_PKEY_param_check() or EVP_PKEY_public_check() to check a DSA public key or DSA parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service.

The functions EVP_PKEY_param_check() or EVP_PKEY_public_check() perform various checks on DSA parameters. Some of those computations take a long time if the modulus (p parameter) is too large.

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

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

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

Also vulnerable are the OpenSSL pkey and pkeyparam command line applications when using the -check option.

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

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

Remediation

Upgrade Debian:unstable openssl to version 3.2.2-1 or higher.

References

low severity

CVE-2024-4741

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 3.2.2-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

NVD Description

This vulnerability has not been analyzed by NVD yet.

Remediation

Upgrade Debian:unstable openssl to version 3.2.2-1 or higher.

References

low severity

CVE-2024-5535

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 3.3.2-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

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

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

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

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

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

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

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

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

Remediation

Upgrade Debian:unstable openssl to version 3.3.2-1 or higher.

References

low severity
new

CVE-2024-6119

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-2 and openssl/libssl1.1@1.1.1-2
  • Fixed in: 3.3.2-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim openssl@1.1.1-2
  • Introduced through: tomcat@8-jre10-slim openssl/libssl1.1@1.1.1-2

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

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

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

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

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

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

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

Remediation

Upgrade Debian:unstable openssl to version 3.3.2-1 or higher.

References

low severity

CVE-2023-50868

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@239-11 and systemd/libudev1@239-11
  • Fixed in: 255.4-1

Detailed paths

  • Introduced through: tomcat@8-jre10-slim systemd/libsystemd0@239-11
  • Introduced through: tomcat@8-jre10-slim systemd/libudev1@239-11

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:unstable 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

Upgrade Debian:unstable systemd to version 255.4-1 or higher.

References

low severity

CVE-2023-39804

  • Vulnerable module: tar
  • Introduced through: tar@1.30+dfsg-2
  • Fixed in: 1.34+dfsg-1.3

Detailed paths

  • Introduced through: tomcat@8-jre10-slim tar@1.30+dfsg-2

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:unstable 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:unstable tar to version 1.34+dfsg-1.3 or higher.

References

low severity

CVE-2024-28085

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.32.1-0.2, util-linux/fdisk@2.32.1-0.2 and others
  • Fixed in: 2.39.3-11

Detailed paths

  • Introduced through: tomcat@8-jre10-slim util-linux@2.32.1-0.2
  • Introduced through: tomcat@8-jre10-slim util-linux/fdisk@2.32.1-0.2
  • Introduced through: tomcat@8-jre10-slim util-linux/libblkid1@2.32.1-0.2
  • Introduced through: tomcat@8-jre10-slim util-linux/libfdisk1@2.32.1-0.2
  • Introduced through: tomcat@8-jre10-slim util-linux/libmount1@2.32.1-0.2
  • Introduced through: tomcat@8-jre10-slim util-linux/libsmartcols1@2.32.1-0.2
  • Introduced through: tomcat@8-jre10-slim util-linux/libuuid1@2.32.1-0.2
  • Introduced through: tomcat@8-jre10-slim util-linux/mount@2.32.1-0.2

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:unstable 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

Upgrade Debian:unstable util-linux to version 2.39.3-11 or higher.

References