Vulnerabilities

356 via 550 paths

Dependencies

136

Source

Group 6 Copy Created with Sketch. Docker

Target OS

debian:10
Test your Docker Hub image against our market leading vulnerability database Sign up for free
Severity
  • 36
  • 74
  • 97
  • 149
Status
  • 356
  • 0
  • 0

critical severity

Exposure of Resource to Wrong Sphere

  • Vulnerable module: curl
  • Introduced through: curl@7.64.0-4+deb10u2 and curl/libcurl4@7.64.0-4+deb10u2
  • Fixed in: 7.64.0-4+deb10u4

Detailed paths

  • Introduced through: nginx@1.19.10 curl@7.64.0-4+deb10u2
  • Introduced through: nginx@1.19.10 curl/libcurl4@7.64.0-4+deb10u2

NVD Description

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

When doing HTTP(S) transfers, libcurl might erroneously use the read callback (CURLOPT_READFUNCTION) to ask for data to send, even when the CURLOPT_POSTFIELDS option has been set, if the same handle previously was used to issue a PUT request which used that callback. This flaw may surprise the application and cause it to misbehave and either send off the wrong data or use memory after free or similar in the subsequent POST request. The problem exists in the logic for a reused handle when it is changed from a PUT to a POST.

Remediation

Upgrade Debian:10 curl to version 7.64.0-4+deb10u4 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.5

Detailed paths

  • Introduced through: nginx@1.19.10 db5.3/libdb5.3@5.3.28+dfsg1-0.5

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

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

Remediation

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

References

critical severity

Directory Traversal

  • Vulnerable module: dpkg
  • Introduced through: dpkg@1.19.7
  • Fixed in: 1.19.8

Detailed paths

  • Introduced through: nginx@1.19.10 dpkg@1.19.7

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:10 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:10 dpkg to version 1.19.8 or higher.

References

critical severity

Exposure of Resource to Wrong Sphere

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-2+deb10u1
  • Fixed in: 2.2.6-2+deb10u3

Detailed paths

  • Introduced through: nginx@1.19.10 expat/libexpat1@2.2.6-2+deb10u1

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:10 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:10 expat to version 2.2.6-2+deb10u3 or higher.

References

critical severity

Improper Encoding or Escaping of Output

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-2+deb10u1
  • Fixed in: 2.2.6-2+deb10u3

Detailed paths

  • Introduced through: nginx@1.19.10 expat/libexpat1@2.2.6-2+deb10u1

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:10 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:10 expat to version 2.2.6-2+deb10u3 or higher.

References

critical severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-2+deb10u1
  • Fixed in: 2.2.6-2+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 expat/libexpat1@2.2.6-2+deb10u1

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

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

Remediation

Upgrade Debian:10 expat to version 2.2.6-2+deb10u2 or higher.

References

critical severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-2+deb10u1
  • Fixed in: 2.2.6-2+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 expat/libexpat1@2.2.6-2+deb10u1

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

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

Remediation

Upgrade Debian:10 expat to version 2.2.6-2+deb10u2 or higher.

References

critical severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-2+deb10u1
  • Fixed in: 2.2.6-2+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 expat/libexpat1@2.2.6-2+deb10u1

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:10 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:10 expat to version 2.2.6-2+deb10u2 or higher.

References

critical severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-2+deb10u1
  • Fixed in: 2.2.6-2+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 expat/libexpat1@2.2.6-2+deb10u1

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:10 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:10 expat to version 2.2.6-2+deb10u2 or higher.

References

critical severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-2+deb10u1
  • Fixed in: 2.2.6-2+deb10u3

critical severity

Out-of-bounds Write

  • Vulnerable module: freetype/libfreetype6
  • Introduced through: freetype/libfreetype6@2.9.1-3+deb10u2
  • Fixed in: 2.9.1-3+deb10u3

Detailed paths

  • Introduced through: nginx@1.19.10 freetype/libfreetype6@2.9.1-3+deb10u2

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:10 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:10 freetype to version 2.9.1-3+deb10u3 or higher.

References

critical severity

Buffer Overflow

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10
  • Fixed in: 2.28-10+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 glibc/libc-bin@2.28-10
  • Introduced through: nginx@1.19.10 glibc/libc6@2.28-10

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:10 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:10 glibc to version 2.28-10+deb10u2 or higher.

References

critical severity

Buffer Overflow

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10
  • Fixed in: 2.28-10+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 glibc/libc-bin@2.28-10
  • Introduced through: nginx@1.19.10 glibc/libc6@2.28-10

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:10 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:10 glibc to version 2.28-10+deb10u2 or higher.

References

critical severity

Use After Free

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10
  • Fixed in: 2.28-10+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 glibc/libc-bin@2.28-10
  • Introduced through: nginx@1.19.10 glibc/libc6@2.28-10

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:10 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:10 glibc to version 2.28-10+deb10u2 or higher.

References

critical severity

Use After Free

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.6.7-4+deb10u6
  • Fixed in: 3.6.7-4+deb10u7

Detailed paths

  • Introduced through: nginx@1.19.10 gnutls28/libgnutls30@3.6.7-4+deb10u6

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:10 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:10 gnutls28 to version 3.6.7-4+deb10u7 or higher.

References

critical severity

Use After Free

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.6.7-4+deb10u6
  • Fixed in: 3.6.7-4+deb10u7

Detailed paths

  • Introduced through: nginx@1.19.10 gnutls28/libgnutls30@3.6.7-4+deb10u6

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:10 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:10 gnutls28 to version 3.6.7-4+deb10u7 or higher.

References

critical severity

Out-of-bounds Write

  • Vulnerable module: libwebp/libwebp6
  • Introduced through: libwebp/libwebp6@0.6.1-2
  • Fixed in: 0.6.1-2+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 libwebp/libwebp6@0.6.1-2

NVD Description

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

A flaw was found in libwebp in versions before 1.0.1. A heap-based buffer overflow in function WebPDecodeRGBInto is possible due to an invalid check for buffer size. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.

Remediation

Upgrade Debian:10 libwebp to version 0.6.1-2+deb10u1 or higher.

References

critical severity

Out-of-bounds Write

  • Vulnerable module: libwebp/libwebp6
  • Introduced through: libwebp/libwebp6@0.6.1-2
  • Fixed in: 0.6.1-2+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 libwebp/libwebp6@0.6.1-2

NVD Description

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

A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in PutLE16().

Remediation

Upgrade Debian:10 libwebp to version 0.6.1-2+deb10u1 or higher.

References

critical severity

Use After Free

  • Vulnerable module: libwebp/libwebp6
  • Introduced through: libwebp/libwebp6@0.6.1-2
  • Fixed in: 0.6.1-2+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 libwebp/libwebp6@0.6.1-2

NVD Description

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

A flaw was found in libwebp in versions before 1.0.1. A use-after-free was found due to a thread being killed too early. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.

Remediation

Upgrade Debian:10 libwebp to version 0.6.1-2+deb10u1 or higher.

References

critical severity

Use of Uninitialized Resource

  • Vulnerable module: libwebp/libwebp6
  • Introduced through: libwebp/libwebp6@0.6.1-2
  • Fixed in: 0.6.1-2+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 libwebp/libwebp6@0.6.1-2

NVD Description

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

A use of uninitialized value was found in libwebp in versions before 1.0.1 in ReadSymbol().

Remediation

Upgrade Debian:10 libwebp to version 0.6.1-2+deb10u1 or higher.

References

critical severity

Buffer Overflow

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

Detailed paths

  • Introduced through: nginx@1.19.10 libx11/libx11-6@2:1.6.7-1+deb10u1
  • Introduced through: nginx@1.19.10 libx11/libx11-data@2:1.6.7-1+deb10u1

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:10 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:10 libx11 to version 2:1.6.7-1+deb10u2 or higher.

References

critical severity

Out-of-bounds Write

  • Vulnerable module: lz4/liblz4-1
  • Introduced through: lz4/liblz4-1@1.8.3-1
  • Fixed in: 1.8.3-1+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 lz4/liblz4-1@1.8.3-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:10 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:10 lz4 to version 1.8.3-1+deb10u1 or higher.

References

critical severity

SQL Injection

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.47+dfsg-3+deb10u6 and openldap/libldap-common@2.4.47+dfsg-3+deb10u6
  • Fixed in: 2.4.47+dfsg-3+deb10u7

Detailed paths

  • Introduced through: nginx@1.19.10 openldap/libldap-2.4-2@2.4.47+dfsg-3+deb10u6
  • Introduced through: nginx@1.19.10 openldap/libldap-common@2.4.47+dfsg-3+deb10u6

NVD Description

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

In OpenLDAP 2.x before 2.5.12 and 2.6.x before 2.6.2, a SQL injection vulnerability exists in the experimental back-sql backend to slapd, via a SQL statement within an LDAP query. This can occur during an LDAP search operation when the search filter is processed, due to a lack of proper escaping.

Remediation

Upgrade Debian:10 openldap to version 2.4.47+dfsg-3+deb10u7 or higher.

References

critical severity

Buffer Overflow

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1d-0+deb10u6 and openssl/libssl1.1@1.1.1d-0+deb10u6
  • Fixed in: 1.1.1d-0+deb10u7

Detailed paths

  • Introduced through: nginx@1.19.10 openssl@1.1.1d-0+deb10u6
  • Introduced through: nginx@1.19.10 openssl/libssl1.1@1.1.1d-0+deb10u6

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:10 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:10 openssl to version 1.1.1d-0+deb10u7 or higher.

References

critical severity

OS Command Injection

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

Detailed paths

  • Introduced through: nginx@1.19.10 openssl@1.1.1d-0+deb10u6
  • Introduced through: nginx@1.19.10 openssl/libssl1.1@1.1.1d-0+deb10u6

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:10 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:10 openssl to version 1.1.1n-0+deb10u2 or higher.

References

critical severity

OS Command Injection

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

Detailed paths

  • Introduced through: nginx@1.19.10 openssl@1.1.1d-0+deb10u6
  • Introduced through: nginx@1.19.10 openssl/libssl1.1@1.1.1d-0+deb10u6

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:10 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:10 openssl to version 1.1.1n-0+deb10u3 or higher.

References

critical severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: nginx@1.19.10 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:10 relevant fixed versions and status.

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

Remediation

There is no fixed version for Debian:10 zlib.

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-1+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 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:10 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:10 zlib to version 1:1.2.11.dfsg-1+deb10u2 or higher.

References

critical severity

Integer Overflow or Wraparound

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10
  • Fixed in: 2.28-10+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 glibc/libc-bin@2.28-10
  • Introduced through: nginx@1.19.10 glibc/libc6@2.28-10

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:10 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:10 glibc to version 2.28-10+deb10u2 or higher.

References

critical severity

Off-by-one Error

  • Vulnerable module: libtasn1-6
  • Introduced through: libtasn1-6@4.13-3
  • Fixed in: 4.13-3+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 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:10 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:10 libtasn1-6 to version 4.13-3+deb10u1 or higher.

References

critical severity

Out-of-bounds Read

  • Vulnerable module: libwebp/libwebp6
  • Introduced through: libwebp/libwebp6@0.6.1-2
  • Fixed in: 0.6.1-2+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 libwebp/libwebp6@0.6.1-2

NVD Description

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

A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in ApplyFilter().

Remediation

Upgrade Debian:10 libwebp to version 0.6.1-2+deb10u1 or higher.

References

critical severity

Out-of-bounds Read

  • Vulnerable module: libwebp/libwebp6
  • Introduced through: libwebp/libwebp6@0.6.1-2
  • Fixed in: 0.6.1-2+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 libwebp/libwebp6@0.6.1-2

NVD Description

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

A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in ShiftBytes().

Remediation

Upgrade Debian:10 libwebp to version 0.6.1-2+deb10u1 or higher.

References

critical severity

Out-of-bounds Read

  • Vulnerable module: libwebp/libwebp6
  • Introduced through: libwebp/libwebp6@0.6.1-2
  • Fixed in: 0.6.1-2+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 libwebp/libwebp6@0.6.1-2

NVD Description

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

A flaw was found in libwebp in versions before 1.0.1. An out-of-bounds read was found in function ChunkVerifyAndAssign. The highest threat from this vulnerability is to data confidentiality and to the service availability.

Remediation

Upgrade Debian:10 libwebp to version 0.6.1-2+deb10u1 or higher.

References

critical severity

Out-of-bounds Read

  • Vulnerable module: libwebp/libwebp6
  • Introduced through: libwebp/libwebp6@0.6.1-2
  • Fixed in: 0.6.1-2+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 libwebp/libwebp6@0.6.1-2

NVD Description

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

A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in GetLE16().

Remediation

Upgrade Debian:10 libwebp to version 0.6.1-2+deb10u1 or higher.

References

critical severity

Out-of-bounds Read

  • Vulnerable module: libwebp/libwebp6
  • Introduced through: libwebp/libwebp6@0.6.1-2
  • Fixed in: 0.6.1-2+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 libwebp/libwebp6@0.6.1-2

NVD Description

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

A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in GetLE24().

Remediation

Upgrade Debian:10 libwebp to version 0.6.1-2+deb10u1 or higher.

References

critical severity

Out-of-bounds Read

  • Vulnerable module: libwebp/libwebp6
  • Introduced through: libwebp/libwebp6@0.6.1-2
  • Fixed in: 0.6.1-2+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 libwebp/libwebp6@0.6.1-2

NVD Description

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

A flaw was found in libwebp in versions before 1.0.1. An out-of-bounds read was found in function ChunkAssignData. The highest threat from this vulnerability is to data confidentiality and to the service availability.

Remediation

Upgrade Debian:10 libwebp to version 0.6.1-2+deb10u1 or higher.

References

high severity

Arbitrary Code Injection

  • Vulnerable module: curl
  • Introduced through: curl@7.64.0-4+deb10u2 and curl/libcurl4@7.64.0-4+deb10u2
  • Fixed in: 7.64.0-4+deb10u6

Detailed paths

  • Introduced through: nginx@1.19.10 curl@7.64.0-4+deb10u2
  • Introduced through: nginx@1.19.10 curl/libcurl4@7.64.0-4+deb10u2

NVD Description

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

A vulnerability in input validation exists in curl <8.0 during communication using the TELNET protocol may allow an attacker to pass on maliciously crafted user name and "telnet options" during server negotiation. The lack of proper input scrubbing allows an attacker to send content or perform option negotiation without the application's intent. This vulnerability could be exploited if an application allows user input, thereby enabling attackers to execute arbitrary code on the system.

Remediation

Upgrade Debian:10 curl to version 7.64.0-4+deb10u6 or higher.

References

high severity

Directory Traversal

  • Vulnerable module: curl
  • Introduced through: curl@7.64.0-4+deb10u2 and curl/libcurl4@7.64.0-4+deb10u2
  • Fixed in: 7.64.0-4+deb10u9

Detailed paths

  • Introduced through: nginx@1.19.10 curl@7.64.0-4+deb10u2
  • Introduced through: nginx@1.19.10 curl/libcurl4@7.64.0-4+deb10u2

NVD Description

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

A path traversal vulnerability exists in curl <8.0.0 SFTP implementation causes the tilde () character to be wrongly replaced when used as a prefix in the first path element, in addition to its intended use as the first element to indicate a path relative to the user's home directory. Attackers can exploit this flaw to bypass filtering or execute arbitrary code by crafting a path like /2/foo while accessing a server with a specific user.

Remediation

Upgrade Debian:10 curl to version 7.64.0-4+deb10u9 or higher.

References

high severity

SQL Injection

  • Vulnerable module: cyrus-sasl2/libsasl2-2
  • Introduced through: cyrus-sasl2/libsasl2-2@2.1.27+dfsg-1+deb10u1 and cyrus-sasl2/libsasl2-modules-db@2.1.27+dfsg-1+deb10u1
  • Fixed in: 2.1.27+dfsg-1+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 cyrus-sasl2/libsasl2-2@2.1.27+dfsg-1+deb10u1
  • Introduced through: nginx@1.19.10 cyrus-sasl2/libsasl2-modules-db@2.1.27+dfsg-1+deb10u1

NVD Description

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

In Cyrus SASL 2.1.17 through 2.1.27 before 2.1.28, plugins/sql.c does not escape the password for a SQL INSERT or UPDATE statement.

Remediation

Upgrade Debian:10 cyrus-sasl2 to version 2.1.27+dfsg-1+deb10u2 or higher.

References

high severity

Incorrect Calculation

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-2+deb10u1
  • Fixed in: 2.2.6-2+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 expat/libexpat1@2.2.6-2+deb10u1

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:10 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:10 expat to version 2.2.6-2+deb10u2 or higher.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-2+deb10u1
  • Fixed in: 2.2.6-2+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 expat/libexpat1@2.2.6-2+deb10u1

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

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

Remediation

Upgrade Debian:10 expat to version 2.2.6-2+deb10u2 or higher.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-2+deb10u1
  • Fixed in: 2.2.6-2+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 expat/libexpat1@2.2.6-2+deb10u1

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

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

Remediation

Upgrade Debian:10 expat to version 2.2.6-2+deb10u2 or higher.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-2+deb10u1
  • Fixed in: 2.2.6-2+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 expat/libexpat1@2.2.6-2+deb10u1

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

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

Remediation

Upgrade Debian:10 expat to version 2.2.6-2+deb10u2 or higher.

References

high severity

Improper Input Validation

  • Vulnerable module: gzip
  • Introduced through: gzip@1.9-3
  • Fixed in: 1.9-3+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 gzip@1.9-3

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:10 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:10 gzip to version 1.9-3+deb10u1 or higher.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.17-3+deb10u1, krb5/libk5crypto3@1.17-3+deb10u1 and others
  • Fixed in: 1.17-3+deb10u5

Detailed paths

  • Introduced through: nginx@1.19.10 krb5/libgssapi-krb5-2@1.17-3+deb10u1
  • Introduced through: nginx@1.19.10 krb5/libk5crypto3@1.17-3+deb10u1
  • Introduced through: nginx@1.19.10 krb5/libkrb5-3@1.17-3+deb10u1
  • Introduced through: nginx@1.19.10 krb5/libkrb5support0@1.17-3+deb10u1

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:10 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:10 krb5 to version 1.17-3+deb10u5 or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: libwebp/libwebp6
  • Introduced through: libwebp/libwebp6@0.6.1-2
  • Fixed in: 0.6.1-2+deb10u3

Detailed paths

  • Introduced through: nginx@1.19.10 libwebp/libwebp6@0.6.1-2

NVD Description

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

Heap buffer overflow in libwebp in Google Chrome prior to 116.0.5845.187 and libwebp 1.3.2 allowed a remote attacker to perform an out of bounds memory write via a crafted HTML page. (Chromium security severity: Critical)

Remediation

Upgrade Debian:10 libwebp to version 0.6.1-2+deb10u3 or higher.

References

high severity

Use After Free

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-7+deb10u1
  • Fixed in: 2.9.4+dfsg1-7+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 libxml2@2.9.4+dfsg1-7+deb10u1

NVD Description

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

There's a flaw in libxml2 in versions before 2.9.11. An attacker who is able to submit a crafted file to be processed by an application linked with libxml2 could trigger a use-after-free. The greatest impact from this flaw is to confidentiality, integrity, and availability.

Remediation

Upgrade Debian:10 libxml2 to version 2.9.4+dfsg1-7+deb10u2 or higher.

References

high severity

Untrusted Search Path

  • Vulnerable module: libxpm/libxpm4
  • Introduced through: libxpm/libxpm4@1:3.5.12-1
  • Fixed in: 1:3.5.12-1+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 libxpm/libxpm4@1:3.5.12-1

NVD Description

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

A flaw was found in libXpm. When processing files with .Z or .gz extensions, the library calls external programs to compress and uncompress files, relying on the PATH environment variable to find these programs, which could allow a malicious user to execute other programs by manipulating the PATH environment variable.

Remediation

Upgrade Debian:10 libxpm to version 1:3.5.12-1+deb10u1 or higher.

References

high severity

Use After Free

  • Vulnerable module: libxslt/libxslt1.1
  • Introduced through: libxslt/libxslt1.1@1.1.32-2.2~deb10u1
  • Fixed in: 1.1.32-2.2~deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 libxslt/libxslt1.1@1.1.32-2.2~deb10u1

NVD Description

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

Use after free in Blink XSLT in Google Chrome prior to 91.0.4472.164 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Remediation

Upgrade Debian:10 libxslt to version 1.1.32-2.2~deb10u2 or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: ncurses/libncursesw6
  • Introduced through: ncurses/libncursesw6@6.1+20181013-2+deb10u2, ncurses/libtinfo6@6.1+20181013-2+deb10u2 and others
  • Fixed in: 6.1+20181013-2+deb10u5

Detailed paths

  • Introduced through: nginx@1.19.10 ncurses/libncursesw6@6.1+20181013-2+deb10u2
  • Introduced through: nginx@1.19.10 ncurses/libtinfo6@6.1+20181013-2+deb10u2
  • Introduced through: nginx@1.19.10 ncurses/ncurses-base@6.1+20181013-2+deb10u2
  • Introduced through: nginx@1.19.10 ncurses/ncurses-bin@6.1+20181013-2+deb10u2

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:10 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:10 ncurses to version 6.1+20181013-2+deb10u5 or higher.

References

high severity

Buffer Overflow

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u7

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

libtiff 4.5.0 is vulnerable to Buffer Overflow via extractContigSamplesBytes() at /libtiff/tools/tiffcrop.c:3215.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u7 or higher.

References

high severity

Numeric Errors

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u5

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

A vulnerability was found in LibTIFF. It has been classified as critical. This affects the function TIFFReadRGBATileExt of the file libtiff/tif_getimage.c. The manipulation leads to integer overflow. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The name of the patch is 227500897dfb07fb7d27f7aa570050e62617e3be. It is recommended to apply a patch to fix this issue. The identifier VDB-213549 was assigned to this vulnerability.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u5 or higher.

References

high severity

Improper Input Validation

  • Vulnerable module: xz-utils/liblzma5
  • Introduced through: xz-utils/liblzma5@5.2.4-1
  • Fixed in: 5.2.4-1+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 xz-utils/liblzma5@5.2.4-1

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:10 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:10 xz-utils to version 5.2.4-1+deb10u1 or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-7+deb10u1
  • Fixed in: 2.9.4+dfsg1-7+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 libxml2@2.9.4+dfsg1-7+deb10u1

NVD Description

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

There is a flaw in the xml entity encoding functionality of libxml2 in versions before 2.9.11. An attacker who is able to supply a crafted file to be processed by an application linked with the affected functionality of libxml2 could trigger an out-of-bounds read. The most likely impact of this flaw is to application availability, with some potential impact to confidentiality and integrity if an attacker is able to use memory information to further exploit the application.

Remediation

Upgrade Debian:10 libxml2 to version 2.9.4+dfsg1-7+deb10u2 or higher.

References

high severity

Missing Authentication for Critical Function

  • Vulnerable module: curl
  • Introduced through: curl@7.64.0-4+deb10u2 and curl/libcurl4@7.64.0-4+deb10u2
  • Fixed in: 7.64.0-4+deb10u3

Detailed paths

  • Introduced through: nginx@1.19.10 curl@7.64.0-4+deb10u2
  • Introduced through: nginx@1.19.10 curl/libcurl4@7.64.0-4+deb10u2

NVD Description

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

An improper authentication vulnerability exists in curl 7.33.0 to and including 7.82.0 which might allow reuse OAUTH2-authenticated connections without properly making sure that the connection was authenticated with the same credentials as set for this transfer. This affects SASL-enabled protocols: SMPTP(S), IMAP(S), POP3(S) and LDAP(S) (openldap only).

Remediation

Upgrade Debian:10 curl to version 7.64.0-4+deb10u3 or higher.

References

high severity

Use After Free

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-2+deb10u1
  • Fixed in: 2.2.6-2+deb10u5

Detailed paths

  • Introduced through: nginx@1.19.10 expat/libexpat1@2.2.6-2+deb10u1

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:10 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:10 expat to version 2.2.6-2+deb10u5 or higher.

References

high severity

Information Exposure

  • Vulnerable module: gcc-8/gcc-8-base
  • Introduced through: gcc-8/gcc-8-base@8.3.0-6, gcc-8/libgcc1@1:8.3.0-6 and others

Detailed paths

  • Introduced through: nginx@1.19.10 gcc-8/gcc-8-base@8.3.0-6
  • Introduced through: nginx@1.19.10 gcc-8/libgcc1@1:8.3.0-6
  • Introduced through: nginx@1.19.10 gcc-8/libstdc++6@8.3.0-6

NVD Description

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

stack_protect_prologue in cfgexpand.c and stack_protect_epilogue in function.c in GNU Compiler Collection (GCC) 4.1 through 8 (under certain circumstances) generate instruction sequences when targeting ARM targets that spill the address of the stack protector guard, which allows an attacker to bypass the protection of -fstack-protector, -fstack-protector-all, -fstack-protector-strong, and -fstack-protector-explicit against stack overflow by controlling what the stack canary is compared against.

Remediation

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

References

high severity

Integer Underflow

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10
  • Fixed in: 2.28-10+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 glibc/libc-bin@2.28-10
  • Introduced through: nginx@1.19.10 glibc/libc6@2.28-10

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:10 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:10 glibc to version 2.28-10+deb10u2 or higher.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: libssh2/libssh2-1
  • Introduced through: libssh2/libssh2-1@1.8.0-2.1
  • Fixed in: 1.8.0-2.1+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 libssh2/libssh2-1@1.8.0-2.1

NVD Description

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

In libssh2 v1.9.0 and earlier versions, the SSH_MSG_DISCONNECT logic in packet.c has an integer overflow in a bounds check, enabling an attacker to specify an arbitrary (out-of-bounds) offset for a subsequent memory read. A crafted SSH server may be able to disclose sensitive information or cause a denial of service condition on the client system when a user connects to the server.

Remediation

Upgrade Debian:10 libssh2 to version 1.8.0-2.1+deb10u1 or higher.

References

high severity

Out-of-bounds Read

  • Vulnerable module: libssh2/libssh2-1
  • Introduced through: libssh2/libssh2-1@1.8.0-2.1
  • Fixed in: 1.8.0-2.1+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 libssh2/libssh2-1@1.8.0-2.1

NVD Description

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

In libssh2 before 1.9.0, kex_method_diffie_hellman_group_exchange_sha256_key_exchange in kex.c has an integer overflow that could lead to an out-of-bounds read in the way packets are read from the server. A remote attacker who compromises a SSH server may be able to disclose sensitive information or cause a denial of service condition on the client system when a user connects to the server. This is related to an _libssh2_check_length mistake, and is different from the various issues fixed in 1.8.1, such as CVE-2019-3855.

Remediation

Upgrade Debian:10 libssh2 to version 1.8.0-2.1+deb10u1 or higher.

References

high severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: nettle/libhogweed4
  • Introduced through: nettle/libhogweed4@3.4.1-1 and nettle/libnettle6@3.4.1-1
  • Fixed in: 3.4.1-1+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 nettle/libhogweed4@3.4.1-1
  • Introduced through: nginx@1.19.10 nettle/libnettle6@3.4.1-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:10 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:10 nettle to version 3.4.1-1+deb10u1 or higher.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-2+deb10u1
  • Fixed in: 2.2.6-2+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 expat/libexpat1@2.2.6-2+deb10u1

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:10 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:10 expat to version 2.2.6-2+deb10u2 or higher.

References

high severity

Off-by-one Error

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10
  • Fixed in: 2.28-10+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 glibc/libc-bin@2.28-10
  • Introduced through: nginx@1.19.10 glibc/libc6@2.28-10

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:10 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:10 glibc to version 2.28-10+deb10u2 or higher.

References

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: nginx@1.19.10 libx11/libx11-6@2:1.6.7-1+deb10u1
  • Introduced through: nginx@1.19.10 libx11/libx11-data@2:1.6.7-1+deb10u1

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:10 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:10 libx11 to version 2:1.6.7-1+deb10u4 or higher.

References

high severity

Double Free

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-7+deb10u1
  • Fixed in: 2.9.4+dfsg1-7+deb10u5

Detailed paths

  • Introduced through: nginx@1.19.10 libxml2@2.9.4+dfsg1-7+deb10u1

NVD Description

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

An issue was discovered in libxml2 before 2.10.3. Certain invalid XML entity definitions can corrupt a hash table key, potentially leading to subsequent logic errors. In one case, a double-free can be provoked.

Remediation

Upgrade Debian:10 libxml2 to version 2.9.4+dfsg1-7+deb10u5 or higher.

References

high severity

Use After Free

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-7+deb10u1
  • Fixed in: 2.9.4+dfsg1-7+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 libxml2@2.9.4+dfsg1-7+deb10u1

NVD Description

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

There's a flaw in libxml2's xmllint in versions before 2.9.11. An attacker who is able to submit a crafted file to be processed by xmllint could trigger a use-after-free. The greatest impact of this flaw is to confidentiality, integrity, and availability.

Remediation

Upgrade Debian:10 libxml2 to version 2.9.4+dfsg1-7+deb10u2 or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: ncurses/libncursesw6
  • Introduced through: ncurses/libncursesw6@6.1+20181013-2+deb10u2, ncurses/libtinfo6@6.1+20181013-2+deb10u2 and others
  • Fixed in: 6.1+20181013-2+deb10u5

Detailed paths

  • Introduced through: nginx@1.19.10 ncurses/libncursesw6@6.1+20181013-2+deb10u2
  • Introduced through: nginx@1.19.10 ncurses/libtinfo6@6.1+20181013-2+deb10u2
  • Introduced through: nginx@1.19.10 ncurses/ncurses-base@6.1+20181013-2+deb10u2
  • Introduced through: nginx@1.19.10 ncurses/ncurses-bin@6.1+20181013-2+deb10u2

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:10 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:10 ncurses to version 6.1+20181013-2+deb10u5 or higher.

References

high severity

CVE-2023-26604

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@241-7~deb10u7 and systemd/libudev1@241-7~deb10u7
  • Fixed in: 241-7~deb10u9

Detailed paths

  • Introduced through: nginx@1.19.10 systemd/libsystemd0@241-7~deb10u7
  • Introduced through: nginx@1.19.10 systemd/libudev1@241-7~deb10u7

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:10 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:10 systemd to version 241-7~deb10u9 or higher.

References

high severity

Cleartext Transmission of Sensitive Information

  • Vulnerable module: curl
  • Introduced through: curl@7.64.0-4+deb10u2 and curl/libcurl4@7.64.0-4+deb10u2
  • Fixed in: 7.64.0-4+deb10u3

Detailed paths

  • Introduced through: nginx@1.19.10 curl@7.64.0-4+deb10u2
  • Introduced through: nginx@1.19.10 curl/libcurl4@7.64.0-4+deb10u2

NVD Description

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

A user can tell curl >= 7.20.0 and <= 7.78.0 to require a successful upgrade to TLS when speaking to an IMAP, POP3 or FTP server (--ssl-reqd on the command line orCURLOPT_USE_SSL set to CURLUSESSL_CONTROL or CURLUSESSL_ALL withlibcurl). This requirement could be bypassed if the server would return a properly crafted but perfectly legitimate response.This flaw would then make curl silently continue its operations withoutTLS contrary to the instructions and expectations, exposing possibly sensitive data in clear text over the network.

Remediation

Upgrade Debian:10 curl to version 7.64.0-4+deb10u3 or higher.

References

high severity

Improper Certificate Validation

  • Vulnerable module: curl
  • Introduced through: curl@7.64.0-4+deb10u2 and curl/libcurl4@7.64.0-4+deb10u2
  • Fixed in: 7.64.0-4+deb10u3

Detailed paths

  • Introduced through: nginx@1.19.10 curl@7.64.0-4+deb10u2
  • Introduced through: nginx@1.19.10 curl/libcurl4@7.64.0-4+deb10u2

NVD Description

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

libcurl would reuse a previously created connection even when a TLS or SSHrelated option had been changed that should have prohibited reuse.libcurl keeps previously used connections in a connection pool for subsequenttransfers to reuse if one of them matches the setup. However, several TLS andSSH settings were left out from the configuration match checks, making themmatch too easily.

Remediation

Upgrade Debian:10 curl to version 7.64.0-4+deb10u3 or higher.

References

high severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: curl
  • Introduced through: curl@7.64.0-4+deb10u2 and curl/libcurl4@7.64.0-4+deb10u2
  • Fixed in: 7.64.0-4+deb10u3

Detailed paths

  • Introduced through: nginx@1.19.10 curl@7.64.0-4+deb10u2
  • Introduced through: nginx@1.19.10 curl/libcurl4@7.64.0-4+deb10u2

NVD Description

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

libcurl provides the CURLOPT_CERTINFO option to allow applications torequest details to be returned about a server's certificate chain.Due to an erroneous function, a malicious server could make libcurl built withNSS get stuck in a never-ending busy-loop when trying to retrieve thatinformation.

Remediation

Upgrade Debian:10 curl to version 7.64.0-4+deb10u3 or higher.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-2+deb10u1
  • Fixed in: 2.2.6-2+deb10u2

high severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-2+deb10u1
  • Fixed in: 2.2.6-2+deb10u3

high severity

Resource Exhaustion

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-2+deb10u1
  • Fixed in: 2.2.6-2+deb10u7

Detailed paths

  • Introduced through: nginx@1.19.10 expat/libexpat1@2.2.6-2+deb10u1

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:10 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:10 expat to version 2.2.6-2+deb10u7 or higher.

References

high severity

Use After Free

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-2+deb10u1
  • Fixed in: 2.2.6-2+deb10u6

Detailed paths

  • Introduced through: nginx@1.19.10 expat/libexpat1@2.2.6-2+deb10u1

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:10 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:10 expat to version 2.2.6-2+deb10u6 or higher.

References

high severity

Out-of-bounds Read

  • Vulnerable module: freetype/libfreetype6
  • Introduced through: freetype/libfreetype6@2.9.1-3+deb10u2
  • Fixed in: 2.9.1-3+deb10u3

Detailed paths

  • Introduced through: nginx@1.19.10 freetype/libfreetype6@2.9.1-3+deb10u2

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

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

Remediation

Upgrade Debian:10 freetype to version 2.9.1-3+deb10u3 or higher.

References

high severity

Out-of-bounds Read

  • Vulnerable module: freetype/libfreetype6
  • Introduced through: freetype/libfreetype6@2.9.1-3+deb10u2
  • Fixed in: 2.9.1-3+deb10u3

Detailed paths

  • Introduced through: nginx@1.19.10 freetype/libfreetype6@2.9.1-3+deb10u2

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

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

Remediation

Upgrade Debian:10 freetype to version 2.9.1-3+deb10u3 or higher.

References

high severity

Reachable Assertion

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10
  • Fixed in: 2.28-10+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 glibc/libc-bin@2.28-10
  • Introduced through: nginx@1.19.10 glibc/libc6@2.28-10

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:10 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:10 glibc to version 2.28-10+deb10u2 or higher.

References

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: nginx@1.19.10 gmp/libgmp10@2:6.1.2+dfsg-4

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:10 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:10 gmp to version 2:6.1.2+dfsg-4+deb10u1 or higher.

References

high severity

Double Free

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.6.7-4+deb10u6
  • Fixed in: 3.6.7-4+deb10u9

Detailed paths

  • Introduced through: nginx@1.19.10 gnutls28/libgnutls30@3.6.7-4+deb10u6

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:10 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:10 gnutls28 to version 3.6.7-4+deb10u9 or higher.

References

high severity

Information Exposure

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.6.7-4+deb10u6
  • Fixed in: 3.6.7-4+deb10u12

Detailed paths

  • Introduced through: nginx@1.19.10 gnutls28/libgnutls30@3.6.7-4+deb10u6

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:10 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:10 gnutls28 to version 3.6.7-4+deb10u12 or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.6.7-4+deb10u6
  • Fixed in: 3.6.7-4+deb10u7

Detailed paths

  • Introduced through: nginx@1.19.10 gnutls28/libgnutls30@3.6.7-4+deb10u6

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:10 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:10 gnutls28 to version 3.6.7-4+deb10u7 or higher.

References

high severity

NULL Pointer Dereference

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.17-3+deb10u1, krb5/libk5crypto3@1.17-3+deb10u1 and others
  • Fixed in: 1.17-3+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 krb5/libgssapi-krb5-2@1.17-3+deb10u1
  • Introduced through: nginx@1.19.10 krb5/libk5crypto3@1.17-3+deb10u1
  • Introduced through: nginx@1.19.10 krb5/libkrb5-3@1.17-3+deb10u1
  • Introduced through: nginx@1.19.10 krb5/libkrb5support0@1.17-3+deb10u1

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:10 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:10 krb5 to version 1.17-3+deb10u2 or higher.

References

high severity

NULL Pointer Dereference

  • Vulnerable module: libgd2/libgd3
  • Introduced through: libgd2/libgd3@2.2.5-5.2
  • Fixed in: 2.2.5-5.2+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 libgd2/libgd3@2.2.5-5.2

NVD Description

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

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

Remediation

Upgrade Debian:10 libgd2 to version 2.2.5-5.2+deb10u1 or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: libssh2/libssh2-1
  • Introduced through: libssh2/libssh2-1@1.8.0-2.1
  • Fixed in: 1.8.0-2.1+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 libssh2/libssh2-1@1.8.0-2.1

NVD Description

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

An issue was discovered in function _libssh2_packet_add in libssh2 1.10.0 allows attackers to access out of bounds memory.

Remediation

Upgrade Debian:10 libssh2 to version 1.8.0-2.1+deb10u1 or higher.

References

high severity

Double Free

  • Vulnerable module: libwebp/libwebp6
  • Introduced through: libwebp/libwebp6@0.6.1-2
  • Fixed in: 0.6.1-2+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 libwebp/libwebp6@0.6.1-2

NVD Description

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

There exists a use after free/double free in libwebp. An attacker can use the ApplyFiltersAndEncode() function and loop through to free best.bw and assign best = trial pointer. The second loop will then return 0 because of an Out of memory error in VP8 encoder, the pointer is still assigned to trial and the AddressSanitizer will attempt a double free. 

Remediation

Upgrade Debian:10 libwebp to version 0.6.1-2+deb10u2 or higher.

References

high severity

Improper Input Validation

  • Vulnerable module: libwebp/libwebp6
  • Introduced through: libwebp/libwebp6@0.6.1-2
  • Fixed in: 0.6.1-2+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 libwebp/libwebp6@0.6.1-2

NVD Description

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

A flaw was found in libwebp in versions before 1.0.1. When reading a file libwebp allocates an excessive amount of memory. The highest threat from this vulnerability is to the service availability.

Remediation

Upgrade Debian:10 libwebp to version 0.6.1-2+deb10u1 or higher.

References

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: nginx@1.19.10 libx11/libx11-6@2:1.6.7-1+deb10u1
  • Introduced through: nginx@1.19.10 libx11/libx11-data@2:1.6.7-1+deb10u1

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:10 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:10 libx11 to version 2:1.6.7-1+deb10u3 or higher.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-7+deb10u1
  • Fixed in: 2.9.4+dfsg1-7+deb10u5

Detailed paths

  • Introduced through: nginx@1.19.10 libxml2@2.9.4+dfsg1-7+deb10u1

NVD Description

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

An issue was discovered in libxml2 before 2.10.3. When parsing a multi-gigabyte XML document with the XML_PARSE_HUGE parser option enabled, several integer counters can overflow. This results in an attempt to access an array at a negative 2GB offset, typically leading to a segmentation fault.

Remediation

Upgrade Debian:10 libxml2 to version 2.9.4+dfsg1-7+deb10u5 or higher.

References

high severity

Use After Free

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-7+deb10u1
  • Fixed in: 2.9.4+dfsg1-7+deb10u3

Detailed paths

  • Introduced through: nginx@1.19.10 libxml2@2.9.4+dfsg1-7+deb10u1

NVD Description

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

valid.c in libxml2 before 2.9.13 has a use-after-free of ID and IDREF attributes.

Remediation

Upgrade Debian:10 libxml2 to version 2.9.4+dfsg1-7+deb10u3 or higher.

References

high severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: libxpm/libxpm4
  • Introduced through: libxpm/libxpm4@1:3.5.12-1
  • Fixed in: 1:3.5.12-1+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 libxpm/libxpm4@1:3.5.12-1

NVD Description

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

A flaw was found in libXpm. This issue occurs when parsing a file with a comment not closed; the end-of-file condition will not be detected, leading to an infinite loop and resulting in a Denial of Service in the application linked to the library.

Remediation

Upgrade Debian:10 libxpm to version 1:3.5.12-1+deb10u1 or higher.

References

high severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: libxpm/libxpm4
  • Introduced through: libxpm/libxpm4@1:3.5.12-1
  • Fixed in: 1:3.5.12-1+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 libxpm/libxpm4@1:3.5.12-1

NVD Description

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

A flaw was found in libXpm. When processing a file with width of 0 and a very large height, some parser functions will be called repeatedly and can lead to an infinite loop, resulting in a Denial of Service in the application linked to the library.

Remediation

Upgrade Debian:10 libxpm to version 1:3.5.12-1+deb10u1 or higher.

References

high severity

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

  • Vulnerable module: libxslt/libxslt1.1
  • Introduced through: libxslt/libxslt1.1@1.1.32-2.2~deb10u1
  • Fixed in: 1.1.32-2.2~deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 libxslt/libxslt1.1@1.1.32-2.2~deb10u1

NVD Description

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

Type confusion in xsltNumberFormatGetMultipleLevel prior to libxslt 1.1.33 could allow attackers to potentially exploit heap corruption via crafted XML data.

Remediation

Upgrade Debian:10 libxslt to version 1.1.32-2.2~deb10u2 or higher.

References

high severity

Improper Input Validation

  • Vulnerable module: nettle/libhogweed4
  • Introduced through: nettle/libhogweed4@3.4.1-1 and nettle/libnettle6@3.4.1-1
  • Fixed in: 3.4.1-1+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 nettle/libhogweed4@3.4.1-1
  • Introduced through: nginx@1.19.10 nettle/libnettle6@3.4.1-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:10 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:10 nettle to version 3.4.1-1+deb10u1 or higher.

References

high severity

Improper Enforcement of Message or Data Structure

  • Vulnerable module: nghttp2/libnghttp2-14
  • Introduced through: nghttp2/libnghttp2-14@1.36.0-2+deb10u1
  • Fixed in: 1.36.0-2+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 nghttp2/libnghttp2-14@1.36.0-2+deb10u1

NVD Description

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

In nghttp2 before version 1.41.0, the overly large HTTP/2 SETTINGS frame payload causes denial of service. The proof of concept attack involves a malicious client constructing a SETTINGS frame with a length of 14,400 bytes (2400 individual settings entries) over and over again. The attack causes the CPU to spike at 100%. nghttp2 v1.41.0 fixes this vulnerability. There is a workaround to this vulnerability. Implement nghttp2_on_frame_recv_callback callback, and if received frame is SETTINGS frame and the number of settings entries are large (e.g., > 32), then drop the connection.

Remediation

Upgrade Debian:10 nghttp2 to version 1.36.0-2+deb10u2 or higher.

References

high severity

Resource Exhaustion

  • Vulnerable module: nghttp2/libnghttp2-14
  • Introduced through: nghttp2/libnghttp2-14@1.36.0-2+deb10u1
  • Fixed in: 1.36.0-2+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 nghttp2/libnghttp2-14@1.36.0-2+deb10u1

NVD Description

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

The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.

Remediation

Upgrade Debian:10 nghttp2 to version 1.36.0-2+deb10u2 or higher.

References

high severity

Double Free

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

Detailed paths

  • Introduced through: nginx@1.19.10 openssl@1.1.1d-0+deb10u6
  • Introduced through: nginx@1.19.10 openssl/libssl1.1@1.1.1d-0+deb10u6

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:10 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:10 openssl to version 1.1.1n-0+deb10u4 or higher.

References

high severity

Improper Certificate Validation

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

Detailed paths

  • Introduced through: nginx@1.19.10 openssl@1.1.1d-0+deb10u6
  • Introduced through: nginx@1.19.10 openssl/libssl1.1@1.1.1d-0+deb10u6

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:10 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:10 openssl to version 1.1.1n-0+deb10u5 or higher.

References

high severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1d-0+deb10u6 and openssl/libssl1.1@1.1.1d-0+deb10u6
  • Fixed in: 1.1.1d-0+deb10u8

Detailed paths

  • Introduced through: nginx@1.19.10 openssl@1.1.1d-0+deb10u6
  • Introduced through: nginx@1.19.10 openssl/libssl1.1@1.1.1d-0+deb10u6

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:10 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:10 openssl to version 1.1.1d-0+deb10u8 or higher.

References

high severity

Use After Free

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

Detailed paths

  • Introduced through: nginx@1.19.10 openssl@1.1.1d-0+deb10u6
  • Introduced through: nginx@1.19.10 openssl/libssl1.1@1.1.1d-0+deb10u6

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:10 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:10 openssl to version 1.1.1n-0+deb10u4 or higher.

References

high severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@241-7~deb10u7 and systemd/libudev1@241-7~deb10u7

Detailed paths

  • Introduced through: nginx@1.19.10 systemd/libsystemd0@241-7~deb10u7
  • Introduced through: nginx@1.19.10 systemd/libudev1@241-7~deb10u7

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

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

Remediation

There is no fixed version for Debian:10 systemd.

References

high severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u9

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

A segment fault (SEGV) flaw was found in libtiff that could be triggered by passing a crafted tiff file to the TIFFReadRGBATileExt() API. This flaw allows a remote attacker to cause a heap-buffer overflow, leading to a denial of service.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u9 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-1+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 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:10 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:10 zlib to version 1:1.2.11.dfsg-1+deb10u1 or higher.

References

high severity

Information Exposure

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.6.7-4+deb10u6
  • Fixed in: 3.6.7-4+deb10u10

Detailed paths

  • Introduced through: nginx@1.19.10 gnutls28/libgnutls30@3.6.7-4+deb10u6

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:10 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:10 gnutls28 to version 3.6.7-4+deb10u10 or higher.

References

high severity

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

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

Detailed paths

  • Introduced through: nginx@1.19.10 openssl@1.1.1d-0+deb10u6
  • Introduced through: nginx@1.19.10 openssl/libssl1.1@1.1.1d-0+deb10u6

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:10 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:10 openssl to version 1.1.1n-0+deb10u4 or higher.

References

high severity

Out-of-bounds Read

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1d-0+deb10u6 and openssl/libssl1.1@1.1.1d-0+deb10u6
  • Fixed in: 1.1.1d-0+deb10u7

Detailed paths

  • Introduced through: nginx@1.19.10 openssl@1.1.1d-0+deb10u6
  • Introduced through: nginx@1.19.10 openssl/libssl1.1@1.1.1d-0+deb10u6

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:10 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:10 openssl to version 1.1.1d-0+deb10u7 or higher.

References

high severity

Out-of-bounds Read

  • Vulnerable module: ncurses/libncursesw6
  • Introduced through: ncurses/libncursesw6@6.1+20181013-2+deb10u2, ncurses/libtinfo6@6.1+20181013-2+deb10u2 and others
  • Fixed in: 6.1+20181013-2+deb10u3

Detailed paths

  • Introduced through: nginx@1.19.10 ncurses/libncursesw6@6.1+20181013-2+deb10u2
  • Introduced through: nginx@1.19.10 ncurses/libtinfo6@6.1+20181013-2+deb10u2
  • Introduced through: nginx@1.19.10 ncurses/ncurses-base@6.1+20181013-2+deb10u2
  • Introduced through: nginx@1.19.10 ncurses/ncurses-bin@6.1+20181013-2+deb10u2

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:10 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:10 ncurses to version 6.1+20181013-2+deb10u3 or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u4

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

A heap buffer overflow in ExtractImageSection function in tiffcrop.c in libtiff library Version 4.3.0 allows attacker to trigger unsafe or out of bounds memory access via crafted TIFF image file which could result into application crash, potential information disclosure or any other context-dependent impact

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u4 or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10

Detailed paths

  • Introduced through: nginx@1.19.10 glibc/libc-bin@2.28-10
  • Introduced through: nginx@1.19.10 glibc/libc6@2.28-10

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

There is no fixed version for Debian:10 glibc.

References

high severity

Use After Free

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10
  • Fixed in: 2.28-10+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 glibc/libc-bin@2.28-10
  • Introduced through: nginx@1.19.10 glibc/libc6@2.28-10

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:10 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:10 glibc to version 2.28-10+deb10u2 or higher.

References

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: curl
  • Introduced through: curl@7.64.0-4+deb10u2 and curl/libcurl4@7.64.0-4+deb10u2
  • Fixed in: 7.64.0-4+deb10u3

Detailed paths

  • Introduced through: nginx@1.19.10 curl@7.64.0-4+deb10u2
  • Introduced through: nginx@1.19.10 curl/libcurl4@7.64.0-4+deb10u2

NVD Description

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

curl < 7.84.0 supports "chained" HTTP compression algorithms, meaning that a serverresponse can be compressed multiple times and potentially with different algorithms. The number of acceptable "links" in this "decompression chain" was unbounded, allowing a malicious server to insert a virtually unlimited number of compression steps.The use of such a decompression chain could result in a "malloc bomb", makingcurl end up spending enormous amounts of allocated heap memory, or trying toand returning out of memory errors.

Remediation

Upgrade Debian:10 curl to version 7.64.0-4+deb10u3 or higher.

References

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: curl
  • Introduced through: curl@7.64.0-4+deb10u2 and curl/libcurl4@7.64.0-4+deb10u2
  • Fixed in: 7.64.0-4+deb10u5

Detailed paths

  • Introduced through: nginx@1.19.10 curl@7.64.0-4+deb10u2
  • Introduced through: nginx@1.19.10 curl/libcurl4@7.64.0-4+deb10u2

NVD Description

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

An allocation of resources without limits or throttling vulnerability exists in curl <v7.88.0 based on the "chained" HTTP compression algorithms, meaning that a server response can be compressed multiple times and potentially with differentalgorithms. The number of acceptable "links" in this "decompression chain" wascapped, but the cap was implemented on a per-header basis allowing a maliciousserver to insert a virtually unlimited number of compression steps simply byusing many headers. The use of such a decompression chain could result in a "malloc bomb", making curl end up spending enormous amounts of allocated heap memory, or trying to and returning out of memory errors.

Remediation

Upgrade Debian:10 curl to version 7.64.0-4+deb10u5 or higher.

References

medium severity

CVE-2023-46218

  • Vulnerable module: curl
  • Introduced through: curl@7.64.0-4+deb10u2 and curl/libcurl4@7.64.0-4+deb10u2
  • Fixed in: 7.64.0-4+deb10u8

Detailed paths

  • Introduced through: nginx@1.19.10 curl@7.64.0-4+deb10u2
  • Introduced through: nginx@1.19.10 curl/libcurl4@7.64.0-4+deb10u2

NVD Description

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

This flaw allows a malicious HTTP server to set "super cookies" in curl that are then passed back to more origins than what is otherwise allowed or possible. This allows a site to set cookies that then would get sent to different and unrelated sites and domains.

It could do this by exploiting a mixed case flaw in curl's function that verifies a given cookie domain against the Public Suffix List (PSL). For example a cookie could be set with domain=co.UK when the URL used a lower case hostname curl.co.uk, even though co.uk is listed as a PSL domain.

Remediation

Upgrade Debian:10 curl to version 7.64.0-4+deb10u8 or higher.

References

medium severity

Insufficiently Protected Credentials

  • Vulnerable module: curl
  • Introduced through: curl@7.64.0-4+deb10u2 and curl/libcurl4@7.64.0-4+deb10u2
  • Fixed in: 7.64.0-4+deb10u3

Detailed paths

  • Introduced through: nginx@1.19.10 curl@7.64.0-4+deb10u2
  • Introduced through: nginx@1.19.10 curl/libcurl4@7.64.0-4+deb10u2

NVD Description

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

A insufficiently protected credentials vulnerability in fixed in curl 7.83.0 might leak authentication or cookie header data on HTTP redirects to the same host but another port number.

Remediation

Upgrade Debian:10 curl to version 7.64.0-4+deb10u3 or higher.

References

medium severity

Uncontrolled Recursion

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-2+deb10u1
  • Fixed in: 2.2.6-2+deb10u3

Detailed paths

  • Introduced through: nginx@1.19.10 expat/libexpat1@2.2.6-2+deb10u1

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:10 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:10 expat to version 2.2.6-2+deb10u3 or higher.

References

medium severity

Arbitrary Code Injection

  • Vulnerable module: gnupg2/gpgv
  • Introduced through: gnupg2/gpgv@2.2.12-1+deb10u1
  • Fixed in: 2.2.12-1+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 gnupg2/gpgv@2.2.12-1+deb10u1

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:10 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:10 gnupg2 to version 2.2.12-1+deb10u2 or higher.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.6.7-4+deb10u6
  • Fixed in: 3.6.7-4+deb10u9

Detailed paths

  • Introduced through: nginx@1.19.10 gnutls28/libgnutls30@3.6.7-4+deb10u6

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:10 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:10 gnutls28 to version 3.6.7-4+deb10u9 or higher.

References

medium severity

Access of Uninitialized Pointer

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.17-3+deb10u1, krb5/libk5crypto3@1.17-3+deb10u1 and others
  • Fixed in: 1.17-3+deb10u6

Detailed paths

  • Introduced through: nginx@1.19.10 krb5/libgssapi-krb5-2@1.17-3+deb10u1
  • Introduced through: nginx@1.19.10 krb5/libk5crypto3@1.17-3+deb10u1
  • Introduced through: nginx@1.19.10 krb5/libkrb5-3@1.17-3+deb10u1
  • Introduced through: nginx@1.19.10 krb5/libkrb5support0@1.17-3+deb10u1

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:10 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:10 krb5 to version 1.17-3+deb10u6 or higher.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.17-3+deb10u1, krb5/libk5crypto3@1.17-3+deb10u1 and others
  • Fixed in: 1.17-3+deb10u3

Detailed paths

  • Introduced through: nginx@1.19.10 krb5/libgssapi-krb5-2@1.17-3+deb10u1
  • Introduced through: nginx@1.19.10 krb5/libk5crypto3@1.17-3+deb10u1
  • Introduced through: nginx@1.19.10 krb5/libkrb5-3@1.17-3+deb10u1
  • Introduced through: nginx@1.19.10 krb5/libkrb5support0@1.17-3+deb10u1

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:10 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:10 krb5 to version 1.17-3+deb10u3 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: libgd2/libgd3
  • Introduced through: libgd2/libgd3@2.2.5-5.2
  • Fixed in: 2.2.5-5.2+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 libgd2/libgd3@2.2.5-5.2

NVD Description

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

read_header_tga in gd_tga.c in the GD Graphics Library (aka LibGD) through 2.3.2 allows remote attackers to cause a denial of service (out-of-bounds read) via a crafted TGA file.

Remediation

Upgrade Debian:10 libgd2 to version 2.2.5-5.2+deb10u1 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: libgd2/libgd3
  • Introduced through: libgd2/libgd3@2.2.5-5.2
  • Fixed in: 2.2.5-5.2+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 libgd2/libgd3@2.2.5-5.2

NVD Description

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

The GD Graphics Library (aka LibGD) through 2.3.2 has an out-of-bounds read because of the lack of certain gdGetBuf and gdPutBuf return value checks.

Remediation

Upgrade Debian:10 libgd2 to version 2.2.5-5.2+deb10u1 or higher.

References

medium severity

Double Free

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-7+deb10u1
  • Fixed in: 2.9.4+dfsg1-7+deb10u6

Detailed paths

  • Introduced through: nginx@1.19.10 libxml2@2.9.4+dfsg1-7+deb10u1

NVD Description

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

An issue was discovered in libxml2 before 2.10.4. When hashing empty dict strings in a crafted XML document, xmlDictComputeFastKey in dict.c can produce non-deterministic values, leading to various logic and memory errors, such as a double free. This behavior occurs because there is an attempt to use the first byte of an empty string, and any value is possible (not solely the '\0' value).

Remediation

Upgrade Debian:10 libxml2 to version 2.9.4+dfsg1-7+deb10u6 or higher.

References

medium severity

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

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-7+deb10u1
  • Fixed in: 2.9.4+dfsg1-7+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 libxml2@2.9.4+dfsg1-7+deb10u1

NVD Description

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

A flaw was found in libxml2. Exponential entity expansion attack its possible bypassing all existing protection mechanisms and leading to denial of service.

Remediation

Upgrade Debian:10 libxml2 to version 2.9.4+dfsg1-7+deb10u2 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-7+deb10u1
  • Fixed in: 2.9.4+dfsg1-7+deb10u4

Detailed paths

  • Introduced through: nginx@1.19.10 libxml2@2.9.4+dfsg1-7+deb10u1

NVD Description

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

In libxml2 before 2.9.14, several buffer handling functions in buf.c (xmlBuf*) and tree.c (xmlBuffer*) don't check for integer overflows. This can result in out-of-bounds memory writes. Exploitation requires a victim to open a crafted, multi-gigabyte XML file. Other software using libxml2's buffer functions, for example libxslt through 1.1.35, is affected as well.

Remediation

Upgrade Debian:10 libxml2 to version 2.9.4+dfsg1-7+deb10u4 or higher.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-7+deb10u1
  • Fixed in: 2.9.4+dfsg1-7+deb10u6

Detailed paths

  • Introduced through: nginx@1.19.10 libxml2@2.9.4+dfsg1-7+deb10u1

NVD Description

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

In libxml2 before 2.10.4, parsing of certain invalid XSD schemas can lead to a NULL pointer dereference and subsequently a segfault. This occurs in xmlSchemaFixupComplexType in xmlschemas.c.

Remediation

Upgrade Debian:10 libxml2 to version 2.9.4+dfsg1-7+deb10u6 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-7+deb10u1
  • Fixed in: 2.9.4+dfsg1-7+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 libxml2@2.9.4+dfsg1-7+deb10u1

NVD Description

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

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

Remediation

Upgrade Debian:10 libxml2 to version 2.9.4+dfsg1-7+deb10u2 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: ncurses/libncursesw6
  • Introduced through: ncurses/libncursesw6@6.1+20181013-2+deb10u2, ncurses/libtinfo6@6.1+20181013-2+deb10u2 and others
  • Fixed in: 6.1+20181013-2+deb10u4

Detailed paths

  • Introduced through: nginx@1.19.10 ncurses/libncursesw6@6.1+20181013-2+deb10u2
  • Introduced through: nginx@1.19.10 ncurses/libtinfo6@6.1+20181013-2+deb10u2
  • Introduced through: nginx@1.19.10 ncurses/ncurses-base@6.1+20181013-2+deb10u2
  • Introduced through: nginx@1.19.10 ncurses/ncurses-bin@6.1+20181013-2+deb10u2

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:10 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:10 ncurses to version 6.1+20181013-2+deb10u4 or higher.

References

medium severity

Allocation of Resources Without Limits or Throttling

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

Detailed paths

  • Introduced through: nginx@1.19.10 openssl@1.1.1d-0+deb10u6
  • Introduced through: nginx@1.19.10 openssl/libssl1.1@1.1.1d-0+deb10u6

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:10 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:10 openssl to version 1.1.1n-0+deb10u5 or higher.

References

medium severity

Buffer Overflow

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u8

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

A flaw was found in libtiff. A specially crafted tiff file can lead to a segmentation fault due to a buffer overflow in the Fax3Encode function in libtiff/tif_fax3.c, resulting in a denial of service.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u8 or higher.

References

medium severity

Divide By Zero

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u5

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

Divide By Zero error in tiffcrop in libtiff 4.4.0 allows attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit f3a5e010.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u5 or higher.

References

medium severity

Divide By Zero

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u5

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

Divide By Zero error in tiffcrop in libtiff 4.4.0 allows attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit f3a5e010.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u5 or higher.

References

medium severity

Divide By Zero

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u5

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

Divide By Zero error in tiffcrop in libtiff 4.4.0 allows attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit f3a5e010.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u5 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u8

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

A vulnerability was found in libtiff due to multiple potential integer overflows in raw2tiff.c. This flaw allows remote attackers to cause a denial of service or possibly execute an arbitrary code via a crafted tiff image, which triggers a heap-based buffer overflow.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u8 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u8

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

LibTIFF is vulnerable to an integer overflow. This flaw allows remote attackers to cause a denial of service (application crash) or possibly execute an arbitrary code via a crafted tiff image, which triggers a heap-based buffer overflow.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u8 or higher.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u8

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

A NULL pointer dereference in TIFFClose() is caused by a failure to open an output file (non-existent path or a path that requires permissions like /dev/null) while specifying zones.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u8 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u5

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

LibTIFF 4.4.0 has an out-of-bounds read in writeSingleSection in tools/tiffcrop.c:7345, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit e8131125.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u5 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u3

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

Buffer Overflow in LibTiff v4.0.10 allows attackers to cause a denial of service via the "TIFFVGetField" funtion in the component 'libtiff/tif_dir.c'.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u3 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u5

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

A stack overflow was discovered in the _TIFFVGetField function of Tiffsplit v4.4.0. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted TIFF file parsed by the "tiffsplit" or "tiffcrop" utilities.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u5 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u5

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

LibTIFF 4.4.0 has an out-of-bounds write in _TIFFmemcpy in libtiff/tif_unix.c:346 when called from extractImageSection, tools/tiffcrop.c:6826, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit 236b7191.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u5 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u5

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

LibTIFF 4.4.0 has an out-of-bounds write in _TIFFmemset in libtiff/tif_unix.c:340 when called from processCropSelections, tools/tiffcrop.c:7619, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit 236b7191.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u5 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u5

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

LibTIFF 4.4.0 has an out-of-bounds write in _TIFFmemcpy in libtiff/tif_unix.c:346 when called from extractImageSection, tools/tiffcrop.c:6860, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit 236b7191.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u5 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u5

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

LibTIFF 4.4.0 has an out-of-bounds write in extractContigSamplesShifted24bits in tools/tiffcrop.c:3604, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit cfbb883b.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u5 or higher.

References

medium severity

Reachable Assertion

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u4

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

Reachable Assertion in tiffcp in libtiff 4.3.0 allows attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit 5e180045.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u4 or higher.

References

medium severity

Stack-based Buffer Overflow

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u5

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

A stack buffer overflow flaw was found in Libtiffs' tiffcp.c in main() function. This flaw allows an attacker to pass a crafted TIFF file to the tiffcp tool, triggering a stack buffer overflow issue, possibly corrupting the memory, and causing a crash that leads to a denial of service.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u5 or higher.

References

medium severity

Improper Authentication

  • Vulnerable module: curl
  • Introduced through: curl@7.64.0-4+deb10u2 and curl/libcurl4@7.64.0-4+deb10u2
  • Fixed in: 7.64.0-4+deb10u6

Detailed paths

  • Introduced through: nginx@1.19.10 curl@7.64.0-4+deb10u2
  • Introduced through: nginx@1.19.10 curl/libcurl4@7.64.0-4+deb10u2

NVD Description

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

An authentication bypass vulnerability exists libcurl <8.0.0 in the connection reuse feature which can reuse previously established connections with incorrect user permissions due to a failure to check for changes in the CURLOPT_GSSAPI_DELEGATION option. This vulnerability affects krb5/kerberos/negotiate/GSSAPI transfers and could potentially result in unauthorized access to sensitive information. The safest option is to not reuse connections if the CURLOPT_GSSAPI_DELEGATION option has been changed.

Remediation

Upgrade Debian:10 curl to version 7.64.0-4+deb10u6 or higher.

References

medium severity

Improper Authentication

  • Vulnerable module: curl
  • Introduced through: curl@7.64.0-4+deb10u2 and curl/libcurl4@7.64.0-4+deb10u2
  • Fixed in: 7.64.0-4+deb10u6

Detailed paths

  • Introduced through: nginx@1.19.10 curl@7.64.0-4+deb10u2
  • Introduced through: nginx@1.19.10 curl/libcurl4@7.64.0-4+deb10u2

NVD Description

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

An authentication bypass vulnerability exists in libcurl <8.0.0 in the FTP connection reuse feature that can result in wrong credentials being used during subsequent transfers. Previously created connections are kept in a connection pool for reuse if they match the current setup. However, certain FTP settings such as CURLOPT_FTP_ACCOUNT, CURLOPT_FTP_ALTERNATIVE_TO_USER, CURLOPT_FTP_SSL_CCC, and CURLOPT_USE_SSL were not included in the configuration match checks, causing them to match too easily. This could lead to libcurl using the wrong credentials when performing a transfer, potentially allowing unauthorized access to sensitive information.

Remediation

Upgrade Debian:10 curl to version 7.64.0-4+deb10u6 or higher.

References

medium severity

Improper Certificate Validation

  • Vulnerable module: curl
  • Introduced through: curl@7.64.0-4+deb10u2 and curl/libcurl4@7.64.0-4+deb10u2
  • Fixed in: 7.64.0-4+deb10u7

Detailed paths

  • Introduced through: nginx@1.19.10 curl@7.64.0-4+deb10u2
  • Introduced through: nginx@1.19.10 curl/libcurl4@7.64.0-4+deb10u2

NVD Description

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

An improper certificate validation vulnerability exists in curl <v8.1.0 in the way it supports matching of wildcard patterns when listed as "Subject Alternative Name" in TLS server certificates. curl can be built to use its own name matching function for TLS rather than one provided by a TLS library. This private wildcard matching function would match IDN (International Domain Name) hosts incorrectly and could as a result accept patterns that otherwise should mismatch. IDN hostnames are converted to puny code before used for certificate checks. Puny coded names always start with xn-- and should not be allowed to pattern match, but the wildcard check in curl could still check for x*, which would match even though the IDN name most likely contained nothing even resembling an x.

Remediation

Upgrade Debian:10 curl to version 7.64.0-4+deb10u7 or higher.

References

medium severity

Insufficient Verification of Data Authenticity

  • Vulnerable module: curl
  • Introduced through: curl@7.64.0-4+deb10u2 and curl/libcurl4@7.64.0-4+deb10u2
  • Fixed in: 7.64.0-4+deb10u3

Detailed paths

  • Introduced through: nginx@1.19.10 curl@7.64.0-4+deb10u2
  • Introduced through: nginx@1.19.10 curl/libcurl4@7.64.0-4+deb10u2

NVD Description

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

When curl >= 7.20.0 and <= 7.78.0 connects to an IMAP or POP3 server to retrieve data using STARTTLS to upgrade to TLS security, the server can respond and send back multiple responses at once that curl caches. curl would then upgrade to TLS but not flush the in-queue of cached responses but instead continue using and trustingthe responses it got before the TLS handshake as if they were authenticated.Using this flaw, it allows a Man-In-The-Middle attacker to first inject the fake responses, then pass-through the TLS traffic from the legitimate server and trick curl into sending data back to the user thinking the attacker's injected data comes from the TLS-protected server.

Remediation

Upgrade Debian:10 curl to version 7.64.0-4+deb10u3 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: curl
  • Introduced through: curl@7.64.0-4+deb10u2 and curl/libcurl4@7.64.0-4+deb10u2
  • Fixed in: 7.64.0-4+deb10u3

Detailed paths

  • Introduced through: nginx@1.19.10 curl@7.64.0-4+deb10u2
  • Introduced through: nginx@1.19.10 curl/libcurl4@7.64.0-4+deb10u2

NVD Description

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

When curl < 7.84.0 does FTP transfers secured by krb5, it handles message verification failures wrongly. This flaw makes it possible for a Man-In-The-Middle attack to go unnoticed and even allows it to inject data to the client.

Remediation

Upgrade Debian:10 curl to version 7.64.0-4+deb10u3 or higher.

References

medium severity

Use After Free

  • Vulnerable module: curl
  • Introduced through: curl@7.64.0-4+deb10u2 and curl/libcurl4@7.64.0-4+deb10u2
  • Fixed in: 7.64.0-4+deb10u4

Detailed paths

  • Introduced through: nginx@1.19.10 curl@7.64.0-4+deb10u2
  • Introduced through: nginx@1.19.10 curl/libcurl4@7.64.0-4+deb10u2

NVD Description

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

A use after free vulnerability exists in curl <7.87.0. Curl can be asked to tunnel virtually all protocols it supports through an HTTP proxy. HTTP proxies can (and often do) deny such tunnel operations. When getting denied to tunnel the specific protocols SMB or TELNET, curl would use a heap-allocated struct after it had been freed, in its transfer shutdown code path.

Remediation

Upgrade Debian:10 curl to version 7.64.0-4+deb10u4 or higher.

References

medium severity

Improper Input Validation

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10
  • Fixed in: 2.28-10+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 glibc/libc-bin@2.28-10
  • Introduced through: nginx@1.19.10 glibc/libc6@2.28-10

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:10 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:10 glibc to version 2.28-10+deb10u2 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10
  • Fixed in: 2.28-10+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 glibc/libc-bin@2.28-10
  • Introduced through: nginx@1.19.10 glibc/libc6@2.28-10

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:10 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:10 glibc to version 2.28-10+deb10u2 or higher.

References

medium severity

Information Exposure

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.6.7-4+deb10u6
  • Fixed in: 3.6.7-4+deb10u11

Detailed paths

  • Introduced through: nginx@1.19.10 gnutls28/libgnutls30@3.6.7-4+deb10u6

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:10 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:10 gnutls28 to version 3.6.7-4+deb10u11 or higher.

References

medium severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: libgcrypt20
  • Introduced through: libgcrypt20@1.8.4-5
  • Fixed in: 1.8.4-5+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 libgcrypt20@1.8.4-5

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:10 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:10 libgcrypt20 to version 1.8.4-5+deb10u1 or higher.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-7+deb10u1
  • Fixed in: 2.9.4+dfsg1-7+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 libxml2@2.9.4+dfsg1-7+deb10u1

NVD Description

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

A vulnerability found in libxml2 in versions before 2.9.11 shows that it did not propagate errors while parsing XML mixed content, causing a NULL dereference. If an untrusted XML document was parsed in recovery mode and post-validated, the flaw could be used to crash the application. The highest threat from this vulnerability is to system availability.

Remediation

Upgrade Debian:10 libxml2 to version 2.9.4+dfsg1-7+deb10u2 or higher.

References

medium severity

CVE-2021-4160

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1d-0+deb10u6 and openssl/libssl1.1@1.1.1d-0+deb10u6
  • Fixed in: 1.1.1d-0+deb10u8

Detailed paths

  • Introduced through: nginx@1.19.10 openssl@1.1.1d-0+deb10u6
  • Introduced through: nginx@1.19.10 openssl/libssl1.1@1.1.1d-0+deb10u6

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:10 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:10 openssl to version 1.1.1d-0+deb10u8 or higher.

References

medium severity

Information Exposure

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

Detailed paths

  • Introduced through: nginx@1.19.10 openssl@1.1.1d-0+deb10u6
  • Introduced through: nginx@1.19.10 openssl/libssl1.1@1.1.1d-0+deb10u6

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:10 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:10 openssl to version 1.1.1n-0+deb10u4 or higher.

References

medium severity

Insufficiently Protected Credentials

  • Vulnerable module: curl
  • Introduced through: curl@7.64.0-4+deb10u2 and curl/libcurl4@7.64.0-4+deb10u2
  • Fixed in: 7.64.0-4+deb10u4

Detailed paths

  • Introduced through: nginx@1.19.10 curl@7.64.0-4+deb10u2
  • Introduced through: nginx@1.19.10 curl/libcurl4@7.64.0-4+deb10u2

NVD Description

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

An insufficiently protected credentials vulnerability exists in curl 4.9 to and include curl 7.82.0 are affected that could allow an attacker to extract credentials when follows HTTP(S) redirects is used with authentication could leak credentials to other services that exist on different protocols or port numbers.

Remediation

Upgrade Debian:10 curl to version 7.64.0-4+deb10u4 or higher.

References

medium severity

Improper Authentication

  • Vulnerable module: curl
  • Introduced through: curl@7.64.0-4+deb10u2 and curl/libcurl4@7.64.0-4+deb10u2
  • Fixed in: 7.64.0-4+deb10u6

Detailed paths

  • Introduced through: nginx@1.19.10 curl@7.64.0-4+deb10u2
  • Introduced through: nginx@1.19.10 curl/libcurl4@7.64.0-4+deb10u2

NVD Description

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

An authentication bypass vulnerability exists in libcurl prior to v8.0.0 where it reuses a previously established SSH connection despite the fact that an SSH option was modified, which should have prevented reuse. libcurl maintains a pool of previously used connections to reuse them for subsequent transfers if the configurations match. However, two SSH settings were omitted from the configuration check, allowing them to match easily, potentially leading to the reuse of an inappropriate connection.

Remediation

Upgrade Debian:10 curl to version 7.64.0-4+deb10u6 or higher.

References

medium severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10
  • Fixed in: 2.28-10+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 glibc/libc-bin@2.28-10
  • Introduced through: nginx@1.19.10 glibc/libc6@2.28-10

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:10 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:10 glibc to version 2.28-10+deb10u2 or higher.

References

medium severity

Out-of-Bounds

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10
  • Fixed in: 2.28-10+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 glibc/libc-bin@2.28-10
  • Introduced through: nginx@1.19.10 glibc/libc6@2.28-10

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:10 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:10 glibc to version 2.28-10+deb10u2 or higher.

References

medium severity

Use After Free

  • Vulnerable module: icu/libicu63
  • Introduced through: icu/libicu63@63.1-6+deb10u1
  • Fixed in: 63.1-6+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 icu/libicu63@63.1-6+deb10u1

NVD Description

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

International Components for Unicode (ICU-20850) v66.1 was discovered to contain a use after free bug in the pkg_createWithAssemblyCode function in the file tools/pkgdata/pkgdata.cpp.

Remediation

Upgrade Debian:10 icu to version 63.1-6+deb10u2 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+deb10u1 and libx11/libx11-data@2:1.6.7-1+deb10u1
  • Fixed in: 2:1.6.7-1+deb10u4

Detailed paths

  • Introduced through: nginx@1.19.10 libx11/libx11-6@2:1.6.7-1+deb10u1
  • Introduced through: nginx@1.19.10 libx11/libx11-data@2:1.6.7-1+deb10u1

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:10 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:10 libx11 to version 2:1.6.7-1+deb10u4 or higher.

References

medium severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: nginx@1.19.10 libx11/libx11-6@2:1.6.7-1+deb10u1
  • Introduced through: nginx@1.19.10 libx11/libx11-data@2:1.6.7-1+deb10u1

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:10 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:10 libx11 to version 2:1.6.7-1+deb10u4 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: libxpm/libxpm4
  • Introduced through: libxpm/libxpm4@1:3.5.12-1
  • Fixed in: 1:3.5.12-1+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 libxpm/libxpm4@1:3.5.12-1

NVD Description

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

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

Remediation

Upgrade Debian:10 libxpm to version 1:3.5.12-1+deb10u2 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: libxpm/libxpm4
  • Introduced through: libxpm/libxpm4@1:3.5.12-1
  • Fixed in: 1:3.5.12-1+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 libxpm/libxpm4@1:3.5.12-1

NVD Description

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

A vulnerability was found in libXpm where a vulnerability exists due to a boundary condition, a local user can trigger an out-of-bounds read error and read contents of memory on the system.

Remediation

Upgrade Debian:10 libxpm to version 1:3.5.12-1+deb10u2 or higher.

References

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@241-7~deb10u7 and systemd/libudev1@241-7~deb10u7
  • Fixed in: 241-7~deb10u8

Detailed paths

  • Introduced through: nginx@1.19.10 systemd/libsystemd0@241-7~deb10u7
  • Introduced through: nginx@1.19.10 systemd/libudev1@241-7~deb10u7

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:10 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:10 systemd to version 241-7~deb10u8 or higher.

References

medium severity

CVE-2022-4415

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@241-7~deb10u7 and systemd/libudev1@241-7~deb10u7

Detailed paths

  • Introduced through: nginx@1.19.10 systemd/libsystemd0@241-7~deb10u7
  • Introduced through: nginx@1.19.10 systemd/libudev1@241-7~deb10u7

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

There is no fixed version for Debian:10 systemd.

References

medium severity

Off-by-one Error

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@241-7~deb10u7 and systemd/libudev1@241-7~deb10u7
  • Fixed in: 241-7~deb10u10

Detailed paths

  • Introduced through: nginx@1.19.10 systemd/libsystemd0@241-7~deb10u7
  • Introduced through: nginx@1.19.10 systemd/libudev1@241-7~deb10u7

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:10 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:10 systemd to version 241-7~deb10u10 or higher.

References

medium severity

Buffer Overflow

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u7

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

libtiff 4.5.0 is vulnerable to Buffer Overflow via extractContigSamplesShifted8bits() at /libtiff/tools/tiffcrop.c:3753.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u7 or higher.

References

medium severity

Buffer Overflow

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u8

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

libtiff 4.5.0 is vulnerable to Buffer Overflow in uv_encode() when libtiff reads a corrupted little-endian TIFF file and specifies the output to be big-endian.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u8 or higher.

References

medium severity

Buffer Overflow

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u8

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

libtiff 4.5.0 is vulnerable to Buffer Overflow via /libtiff/tools/tiffcrop.c:8499. Incorrect updating of buffer size after rotateImage() in tiffcrop cause heap-buffer-overflow and SEGV.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u8 or higher.

References

medium severity

Divide By Zero

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u4

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

Divide By Zero error in tiffcrop in libtiff 4.3.0 allows attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit f8d0f9aa.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u4 or higher.

References

medium severity

Improper Validation of Specified Quantity in Input

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u5

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

libtiff's tiffcrop utility has a improper input validation flaw that can lead to out of bounds read and ultimately cause a crash if an attacker is able to supply a crafted file to tiffcrop.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u5 or higher.

References

medium severity

Integer Underflow

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u5

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

libtiff's tiffcrop tool has a uint32_t underflow which leads to out of bounds read and write in the extractContigSamples8bits routine. An attacker who supplies a crafted file to tiffcrop could trigger this flaw, most likely by tricking a user into opening the crafted file with tiffcrop. Triggering this flaw could cause a crash or potentially further exploitation.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u5 or higher.

References

medium severity

Integer Underflow

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u5

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

libtiff's tiffcrop utility has a uint32_t underflow that can lead to out of bounds read and write. An attacker who supplies a crafted file to tiffcrop (likely via tricking a user to run tiffcrop on it with certain parameters) could cause a crash or in some cases, further exploitation.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u5 or higher.

References

medium severity

Memory Leak

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u9

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

A memory leak flaw was found in Libtiff's tiffcrop utility. This issue occurs when tiffcrop operates on a TIFF image file, allowing an attacker to pass a crafted TIFF image file to tiffcrop utility, which causes this memory leak issue, resulting an application crash, eventually leading to a denial of service.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u9 or higher.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u4

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

Null source pointer passed as an argument to memcpy() function within TIFFReadDirectory() in tif_dirread.c in libtiff versions from 4.0 to 4.3.0 could lead to Denial of Service via crafted TIFF file. For users that compile libtiff from sources, a fix is available with commit 561599c.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u4 or higher.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u4

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

Null source pointer passed as an argument to memcpy() function within TIFFFetchStripThing() in tif_dirread.c in libtiff versions from 3.9.0 to 4.3.0 could lead to Denial of Service via crafted TIFF file. For users that compile libtiff from sources, the fix is available with commit eecb0712.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u4 or higher.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u4

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

Null source pointer passed as an argument to memcpy() function within TIFFFetchNormalTag () in tif_dirread.c in libtiff versions up to 4.3.0 could lead to Denial of Service via crafted TIFF file.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u4 or higher.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u8

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

A null pointer dereference issue was found in Libtiff's tif_dir.c file. This issue may allow an attacker to pass a crafted TIFF image file to the tiffcp utility which triggers a runtime error that causes undefined behavior. This will result in an application crash, eventually leading to a denial of service.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u8 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u4

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

LibTIFF 4.3.0 has an out-of-bounds read in _TIFFmemcpy in tif_unix.c in certain situations involving a custom tag and 0x0200 as the second word of the DE field.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u4 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u4

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

Out-of-bounds Read error in tiffcp in libtiff 4.3.0 allows attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit 408976c4.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u4 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u5

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

A heap buffer overflow flaw was found in Libtiffs' tiffinfo.c in TIFFReadRawDataStriped() function. This flaw allows an attacker to pass a crafted TIFF file to the tiffinfo tool, triggering a heap buffer overflow issue and causing a crash that leads to a denial of service.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u5 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u7

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

LibTIFF 4.4.0 has an out-of-bounds read in tiffcrop in libtiff/tif_unix.c:368, invoked by tools/tiffcrop.c:2903 and tools/tiffcrop.c:6921, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit afaabc3e.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u7 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u7

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

LibTIFF 4.4.0 has an out-of-bounds read in tiffcrop in tools/tiffcrop.c:3400, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit afaabc3e.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u7 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u7

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

LibTIFF 4.4.0 has an out-of-bounds read in tiffcrop in tools/tiffcrop.c:3488, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit afaabc3e.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u7 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u7

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

LibTIFF 4.4.0 has an out-of-bounds read in tiffcrop in tools/tiffcrop.c:3592, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit afaabc3e.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u7 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u5

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

LibTIFF 4.4.0 has an out-of-bounds read in tiffcp in tools/tiffcp.c:948, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit e8131125.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u5 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u5

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

Multiple heap buffer overflows in tiffcrop.c utility in libtiff library Version 4.4.0 allows attacker to trigger unsafe or out of bounds memory access via crafted TIFF image file which could result into application crash, potential information disclosure or any other context-dependent impact

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u5 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u6

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

processCropSelections in tools/tiffcrop.c in LibTIFF through 4.5.0 has a heap-based buffer overflow (e.g., "WRITE of size 307203") via a crafted TIFF image.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u6 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u7

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

LibTIFF 4.4.0 has an out-of-bounds write in tiffcrop in tools/tiffcrop.c:3502, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit 33aee127.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u7 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u7

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

LibTIFF 4.4.0 has an out-of-bounds write in tiffcrop in tools/tiffcrop.c:3516, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit 33aee127.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u7 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u7

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

LibTIFF 4.4.0 has an out-of-bounds write in tiffcrop in tools/tiffcrop.c:3609, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit 33aee127.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u7 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u7

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

LibTIFF 4.4.0 has an out-of-bounds write in tiffcrop in tools/tiffcrop.c:3724, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit 33aee127.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u7 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u7

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

LibTIFF 4.4.0 has an out-of-bounds write in tiffcrop in libtiff/tif_unix.c:368, invoked by tools/tiffcrop.c:2903 and tools/tiffcrop.c:6778, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit 33aee127.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u7 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u5

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

A vulnerability was found in the libtiff library. This flaw causes a heap buffer overflow issue via the TIFFTAG_INKNAMES and TIFFTAG_NUMBEROFINKS values.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u5 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u5

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

Buffer Overflow vulnerability found in Libtiff V.4.0.7 allows a local attacker to cause a denial of service via the tiffcp function in tiffcp.c.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u5 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u8

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

loadImage() in tools/tiffcrop.c in LibTIFF through 4.5.0 has a heap-based use after free via a crafted TIFF image.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u8 or higher.

References

medium severity

Unchecked Return Value

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u4

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

Unchecked Return Value to NULL Pointer Dereference in tiffcrop in libtiff 4.3.0 allows attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit f2b656e2.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u4 or higher.

References

medium severity

Use After Free

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2
  • Fixed in: 4.1.0+git191117-2~deb10u7

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

LibTIFF 4.4.0 has an out-of-bounds read in tiffcrop in tools/tiffcrop.c:3701, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit afaabc3e.

Remediation

Upgrade Debian:10 tiff to version 4.1.0+git191117-2~deb10u7 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.33.1-0.1, util-linux/fdisk@2.33.1-0.1 and others
  • Fixed in: 2.33.1-0.1+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 util-linux@2.33.1-0.1
  • Introduced through: nginx@1.19.10 util-linux/fdisk@2.33.1-0.1
  • Introduced through: nginx@1.19.10 util-linux/libblkid1@2.33.1-0.1
  • Introduced through: nginx@1.19.10 util-linux/libfdisk1@2.33.1-0.1
  • Introduced through: nginx@1.19.10 util-linux/libmount1@2.33.1-0.1
  • Introduced through: nginx@1.19.10 util-linux/libsmartcols1@2.33.1-0.1
  • Introduced through: nginx@1.19.10 util-linux/libuuid1@2.33.1-0.1
  • Introduced through: nginx@1.19.10 util-linux/mount@2.33.1-0.1

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:10 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:10 util-linux to version 2.33.1-0.1+deb10u1 or higher.

References

medium severity

Excessive Iteration

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

Detailed paths

  • Introduced through: nginx@1.19.10 openssl@1.1.1d-0+deb10u6
  • Introduced through: nginx@1.19.10 openssl/libssl1.1@1.1.1d-0+deb10u6

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:10 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:10 openssl to version 1.1.1n-0+deb10u6 or higher.

References

medium severity

Improper Certificate Validation

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

Detailed paths

  • Introduced through: nginx@1.19.10 openssl@1.1.1d-0+deb10u6
  • Introduced through: nginx@1.19.10 openssl/libssl1.1@1.1.1d-0+deb10u6

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:10 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:10 openssl to version 1.1.1n-0+deb10u5 or higher.

References

medium severity

Improper Certificate Validation

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

Detailed paths

  • Introduced through: nginx@1.19.10 openssl@1.1.1d-0+deb10u6
  • Introduced through: nginx@1.19.10 openssl/libssl1.1@1.1.1d-0+deb10u6

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:10 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:10 openssl to version 1.1.1n-0+deb10u5 or higher.

References

medium severity

Inefficient Regular Expression Complexity

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

Detailed paths

  • Introduced through: nginx@1.19.10 openssl@1.1.1d-0+deb10u6
  • Introduced through: nginx@1.19.10 openssl/libssl1.1@1.1.1d-0+deb10u6

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:10 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:10 openssl to version 1.1.1n-0+deb10u6 or higher.

References

medium severity

Use of a Broken or Risky Cryptographic Algorithm

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

Detailed paths

  • Introduced through: nginx@1.19.10 openssl@1.1.1d-0+deb10u6
  • Introduced through: nginx@1.19.10 openssl/libssl1.1@1.1.1d-0+deb10u6

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:10 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:10 openssl to version 1.1.1n-0+deb10u4 or higher.

References

low severity

Out-of-Bounds

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10

Detailed paths

  • Introduced through: nginx@1.19.10 glibc/libc-bin@2.28-10
  • Introduced through: nginx@1.19.10 glibc/libc6@2.28-10

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:10 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:10 glibc.

References

low severity

CVE-2019-9893

  • Vulnerable module: libseccomp/libseccomp2
  • Introduced through: libseccomp/libseccomp2@2.3.3-4

Detailed paths

  • Introduced through: nginx@1.19.10 libseccomp/libseccomp2@2.3.3-4

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

There is no fixed version for Debian:10 libseccomp.

References

low severity

CVE-2005-2541

  • Vulnerable module: tar
  • Introduced through: tar@1.30+dfsg-6

Detailed paths

  • Introduced through: nginx@1.19.10 tar@1.30+dfsg-6

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:10 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:10 tar.

References

low severity

Out-of-bounds Read

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

In LibTIFF 4.0.7, the program processes BMP images without verifying that biWidth and biHeight in the bitmap-information header match the actual input, leading to a heap-based buffer over-read in bmp2tiff.

Remediation

There is no fixed version for Debian:10 tiff.

References

low severity

CVE-2019-1010023

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10

Detailed paths

  • Introduced through: nginx@1.19.10 glibc/libc-bin@2.28-10
  • Introduced through: nginx@1.19.10 glibc/libc6@2.28-10

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:10 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:10 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+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+deb10u1

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

There is no fixed version for Debian:10 libjpeg-turbo.

References

low severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: nginx@1.19.10 libpng1.6/libpng16-16@1.6.36-6

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

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

References

low severity

Out-of-bounds Read

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

LibTIFF version 4.0.7 is vulnerable to a heap-based buffer over-read in tif_lzw.c resulting in DoS or code execution via a crafted bmp image to tools/bmp2tiff.

Remediation

There is no fixed version for Debian:10 tiff.

References

low severity

Use After Free

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

In LibTIFF 4.0.8, there is a heap-based use-after-free in the t2p_writeproc function in tiff2pdf.c. NOTE: there is a third-party report of inability to reproduce this issue

Remediation

There is no fixed version for Debian:10 tiff.

References

low severity

Out-of-bounds Read

  • Vulnerable module: libgd2/libgd3
  • Introduced through: libgd2/libgd3@2.2.5-5.2

Detailed paths

  • Introduced through: nginx@1.19.10 libgd2/libgd3@2.2.5-5.2

NVD Description

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

In the GD Graphics Library (aka LibGD) through 2.2.5, there is a heap-based buffer over-read in tiffWriter in gd_tiff.c. NOTE: the vendor says "In my opinion this issue should not have a CVE, since the GD and GD2 formats are documented to be 'obsolete, and should only be used for development and testing purposes.'

Remediation

There is no fixed version for Debian:10 libgd2.

References

low severity

Out-of-bounds Write

  • Vulnerable module: lz4/liblz4-1
  • Introduced through: lz4/liblz4-1@1.8.3-1

Detailed paths

  • Introduced through: nginx@1.19.10 lz4/liblz4-1@1.8.3-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:10 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

There is no fixed version for Debian:10 lz4.

References

low severity

Improper Certificate Validation

  • Vulnerable module: perl/perl-base
  • Introduced through: perl/perl-base@5.28.1-6+deb10u1

low severity

Improper Certificate Validation

  • Vulnerable module: perl/perl-base
  • Introduced through: perl/perl-base@5.28.1-6+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 perl/perl-base@5.28.1-6+deb10u1

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

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

Remediation

There is no fixed version for Debian:10 perl.

References

low severity

Improper Check for Dropped Privileges

  • Vulnerable module: bash
  • Introduced through: bash@5.0-4

Detailed paths

  • Introduced through: nginx@1.19.10 bash@5.0-4

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

There is no fixed version for Debian:10 bash.

References

low severity

Out-of-bounds Read

  • Vulnerable module: e2fsprogs
  • Introduced through: e2fsprogs@1.44.5-1+deb10u3, e2fsprogs/libcom-err2@1.44.5-1+deb10u3 and others

Detailed paths

  • Introduced through: nginx@1.19.10 e2fsprogs@1.44.5-1+deb10u3
  • Introduced through: nginx@1.19.10 e2fsprogs/libcom-err2@1.44.5-1+deb10u3
  • Introduced through: nginx@1.19.10 e2fsprogs/libext2fs2@1.44.5-1+deb10u3
  • Introduced through: nginx@1.19.10 e2fsprogs/libss2@1.44.5-1+deb10u3

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

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

Remediation

There is no fixed version for Debian:10 e2fsprogs.

References

low severity

Out-of-bounds Write

  • Vulnerable module: freetype/libfreetype6
  • Introduced through: freetype/libfreetype6@2.9.1-3+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 freetype/libfreetype6@2.9.1-3+deb10u2

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

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

Remediation

There is no fixed version for Debian:10 freetype.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: nginx@1.19.10 pcre3/libpcre3@2:8.39-12

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:10 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:10 pcre3.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: nginx@1.19.10 pcre3/libpcre3@2:8.39-12

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:10 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:10 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: nginx@1.19.10 shadow/login@1:4.5-1.1
  • Introduced through: nginx@1.19.10 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:10 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:10 shadow.

References

low severity

Incorrect Privilege Assignment

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@241-7~deb10u7 and systemd/libudev1@241-7~deb10u7

Detailed paths

  • Introduced through: nginx@1.19.10 systemd/libsystemd0@241-7~deb10u7
  • Introduced through: nginx@1.19.10 systemd/libudev1@241-7~deb10u7

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

There is no fixed version for Debian:10 systemd.

References

low severity

Privilege Chaining

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@241-7~deb10u7 and systemd/libudev1@241-7~deb10u7

Detailed paths

  • Introduced through: nginx@1.19.10 systemd/libsystemd0@241-7~deb10u7
  • Introduced through: nginx@1.19.10 systemd/libudev1@241-7~deb10u7

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

There is no fixed version for Debian:10 systemd.

References

low severity

Insufficient Entropy

  • Vulnerable module: gcc-8/gcc-8-base
  • Introduced through: gcc-8/gcc-8-base@8.3.0-6, gcc-8/libgcc1@1:8.3.0-6 and others

Detailed paths

  • Introduced through: nginx@1.19.10 gcc-8/gcc-8-base@8.3.0-6
  • Introduced through: nginx@1.19.10 gcc-8/libgcc1@1:8.3.0-6
  • Introduced through: nginx@1.19.10 gcc-8/libstdc++6@8.3.0-6

NVD Description

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

The POWER9 backend in GNU Compiler Collection (GCC) before version 10 could optimize multiple calls of the __builtin_darn intrinsic into a single call, thus reducing the entropy of the random number generator. This occurred because a volatile operation was not specified. For example, within a single execution of a program, the output of every __builtin_darn() call may be the same.

Remediation

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

References

low severity

Uncontrolled Recursion

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10

Detailed paths

  • Introduced through: nginx@1.19.10 glibc/libc-bin@2.28-10
  • Introduced through: nginx@1.19.10 glibc/libc6@2.28-10

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:10 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:10 glibc.

References

low severity

Uncontrolled Recursion

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10

Detailed paths

  • Introduced through: nginx@1.19.10 glibc/libc-bin@2.28-10
  • Introduced through: nginx@1.19.10 glibc/libc6@2.28-10

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:10 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:10 glibc.

References

low severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: gnupg2/gpgv
  • Introduced through: gnupg2/gpgv@2.2.12-1+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 gnupg2/gpgv@2.2.12-1+deb10u1

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

There is no fixed version for Debian:10 gnupg2.

References

low severity

Integer Overflow or Wraparound

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.17-3+deb10u1, krb5/libk5crypto3@1.17-3+deb10u1 and others

Detailed paths

  • Introduced through: nginx@1.19.10 krb5/libgssapi-krb5-2@1.17-3+deb10u1
  • Introduced through: nginx@1.19.10 krb5/libk5crypto3@1.17-3+deb10u1
  • Introduced through: nginx@1.19.10 krb5/libkrb5-3@1.17-3+deb10u1
  • Introduced through: nginx@1.19.10 krb5/libkrb5support0@1.17-3+deb10u1

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:10 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:10 krb5.

References

low severity

Information Exposure

  • Vulnerable module: libgcrypt20
  • Introduced through: libgcrypt20@1.8.4-5

Detailed paths

  • Introduced through: nginx@1.19.10 libgcrypt20@1.8.4-5

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

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

Remediation

There is no fixed version for Debian:10 libgcrypt20.

References

low severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: libgcrypt20
  • Introduced through: libgcrypt20@1.8.4-5

Detailed paths

  • Introduced through: nginx@1.19.10 libgcrypt20@1.8.4-5

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:10 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:10 libgcrypt20.

References

low severity

Double Free

  • Vulnerable module: libgd2/libgd3
  • Introduced through: libgd2/libgd3@2.2.5-5.2

Detailed paths

  • Introduced through: nginx@1.19.10 libgd2/libgd3@2.2.5-5.2

NVD Description

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

gdImageGd2Ptr in gd_gd2.c in the GD Graphics Library (aka LibGD) through 2.3.2 has a double free. NOTE: the vendor's position is "The GD2 image format is a proprietary image format of libgd. It has to be regarded as being obsolete, and should only be used for development and testing purposes.

Remediation

There is no fixed version for Debian:10 libgd2.

References

low severity

Improper Input Validation

  • Vulnerable module: libidn2/libidn2-0
  • Introduced through: libidn2/libidn2-0@2.0.5-1+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 libidn2/libidn2-0@2.0.5-1+deb10u1

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

There is no fixed version for Debian:10 libidn2.

References

low severity

Excessive Iteration

  • Vulnerable module: libjpeg-turbo/libjpeg62-turbo
  • Introduced through: libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+deb10u1

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

libjpeg 9c has a large loop because read_pixel in rdtarga.c mishandles EOF.

Remediation

There is no fixed version for Debian:10 libjpeg-turbo.

References

low severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-7+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 libxml2@2.9.4+dfsg1-7+deb10u1

NVD Description

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

parser.c in libxml2 before 2.9.5 does not prevent infinite recursion in parameter entities.

Remediation

There is no fixed version for Debian:10 libxml2.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-7+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 libxml2@2.9.4+dfsg1-7+deb10u1

NVD Description

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

NULL Pointer Dereference allows attackers to cause a denial of service (or application crash). This only applies when lxml is used together with libxml2 2.9.10 through 2.9.14. libxml2 2.9.9 and earlier are not affected. It allows triggering crashes through forged input data, given a vulnerable code sequence in the application. The vulnerability is caused by the iterwalk function (also used by the canonicalize function). Such code shouldn't be in wide-spread use, given that parsing + iterwalk would usually be replaced with the more efficient iterparse function. However, an XML converter that serialises to C14N would also be vulnerable, for example, and there are legitimate use cases for this code sequence. If untrusted input is received (also remotely) and processed via iterwalk function, a crash can be triggered.

Remediation

There is no fixed version for Debian:10 libxml2.

References

low severity

Use After Free

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-7+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 libxml2@2.9.4+dfsg1-7+deb10u1

NVD Description

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

An issue was discovered in libxml2 before 2.11.7 and 2.12.x before 2.12.5. When using the XML Reader interface with DTD validation and XInclude expansion enabled, processing crafted XML documents can lead to an xmlValidatePopElement use-after-free.

Remediation

There is no fixed version for Debian:10 libxml2.

References

low severity

Resource Exhaustion

  • Vulnerable module: nginx
  • Introduced through: nginx@1.19.10-1~buster

Detailed paths

  • Introduced through: nginx@1.19.10 nginx@1.19.10-1~buster

NVD Description

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

The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.

Remediation

There is no fixed version for Debian:10 nginx.

References

low severity

Cryptographic Issues

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.47+dfsg-3+deb10u6 and openldap/libldap-common@2.4.47+dfsg-3+deb10u6

Detailed paths

  • Introduced through: nginx@1.19.10 openldap/libldap-2.4-2@2.4.47+dfsg-3+deb10u6
  • Introduced through: nginx@1.19.10 openldap/libldap-common@2.4.47+dfsg-3+deb10u6

NVD Description

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

The nss_parse_ciphers function in libraries/libldap/tls_m.c in OpenLDAP does not properly parse OpenSSL-style multi-keyword mode cipher strings, which might cause a weaker than intended cipher to be used and allow remote attackers to have unspecified impact via unknown vectors.

Remediation

There is no fixed version for Debian:10 openldap.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.47+dfsg-3+deb10u6 and openldap/libldap-common@2.4.47+dfsg-3+deb10u6

Detailed paths

  • Introduced through: nginx@1.19.10 openldap/libldap-2.4-2@2.4.47+dfsg-3+deb10u6
  • Introduced through: nginx@1.19.10 openldap/libldap-common@2.4.47+dfsg-3+deb10u6

NVD Description

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

A vulnerability was found in openldap. This security flaw causes a null pointer dereference in ber_memalloc_x() function.

Remediation

There is no fixed version for Debian:10 openldap.

References

low severity

Out-of-Bounds

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.47+dfsg-3+deb10u6 and openldap/libldap-common@2.4.47+dfsg-3+deb10u6

Detailed paths

  • Introduced through: nginx@1.19.10 openldap/libldap-2.4-2@2.4.47+dfsg-3+deb10u6
  • Introduced through: nginx@1.19.10 openldap/libldap-common@2.4.47+dfsg-3+deb10u6

NVD Description

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

contrib/slapd-modules/nops/nops.c in OpenLDAP through 2.4.45, when both the nops module and the memberof overlay are enabled, attempts to free a buffer that was allocated on the stack, which allows remote attackers to cause a denial of service (slapd crash) via a member MODDN operation.

Remediation

There is no fixed version for Debian:10 openldap.

References

low severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: nginx@1.19.10 pcre3/libpcre3@2:8.39-12

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:10 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:10 pcre3.

References

low severity

Uncontrolled Recursion

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

Detailed paths

  • Introduced through: nginx@1.19.10 pcre3/libpcre3@2:8.39-12

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:10 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:10 pcre3.

References

low severity

Link Following

  • Vulnerable module: perl/perl-base
  • Introduced through: perl/perl-base@5.28.1-6+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 perl/perl-base@5.28.1-6+deb10u1

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:10 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:10 perl.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: tar
  • Introduced through: tar@1.30+dfsg-6

low severity

Missing Release of Resource after Effective Lifetime

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

LibTIFF 4.0.8 has multiple memory leak vulnerabilities, which allow attackers to cause a denial of service (memory consumption), as demonstrated by tif_open.c, tif_lzw.c, and tif_aux.c. NOTE: Third parties were unable to reproduce the issue

Remediation

There is no fixed version for Debian:10 tiff.

References

low severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

An out-of-memory flaw was found in libtiff that could be triggered by passing a crafted tiff file to the TIFFRasterScanlineSize64() API. This flaw allows a remote attacker to cause a denial of service via a crafted input with a size smaller than 379 KB.

Remediation

There is no fixed version for Debian:10 tiff.

References

low severity

Access Restriction Bypass

  • Vulnerable module: nginx
  • Introduced through: nginx@1.19.10-1~buster

Detailed paths

  • Introduced through: nginx@1.19.10 nginx@1.19.10-1~buster

NVD Description

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

The default configuration of nginx, possibly 1.3.13 and earlier, uses world-readable permissions for the (1) access.log and (2) error.log files, which allows local users to obtain sensitive information by reading the files.

Remediation

There is no fixed version for Debian:10 nginx.

References

low severity

Improper Input Validation

  • Vulnerable module: coreutils
  • Introduced through: coreutils@8.30-3

Detailed paths

  • Introduced through: nginx@1.19.10 coreutils@8.30-3

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:10 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:10 coreutils.

References

low severity

Improper Validation of Integrity Check Value

  • Vulnerable module: curl
  • Introduced through: curl@7.64.0-4+deb10u2 and curl/libcurl4@7.64.0-4+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 curl@7.64.0-4+deb10u2
  • Introduced through: nginx@1.19.10 curl/libcurl4@7.64.0-4+deb10u2

NVD Description

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

When curl is instructed to download content using the metalink feature, thecontents is verified against a hash provided in the metalink XML file.The metalink XML file points out to the client how to get the same contentfrom a set of different URLs, potentially hosted by different servers and theclient can then download the file from one or several of them. In a serial orparallel manner.If one of the servers hosting the contents has been breached and the contentsof the specific file on that server is replaced with a modified payload, curlshould detect this when the hash of the file mismatches after a completeddownload. It should remove the contents and instead try getting the contentsfrom another URL. This is not done, and instead such a hash mismatch is onlymentioned in text and the potentially malicious content is kept in the file ondisk.

Remediation

There is no fixed version for Debian:10 curl.

References

low severity

Out-of-Bounds

  • Vulnerable module: jbigkit/libjbig0
  • Introduced through: jbigkit/libjbig0@2.1-3.1+b2

Detailed paths

  • Introduced through: nginx@1.19.10 jbigkit/libjbig0@2.1-3.1+b2

NVD Description

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

In LibTIFF 4.0.8, there is a memory malloc failure in tif_jbig.c. A crafted TIFF document can lead to an abort resulting in a remote denial of service attack.

Remediation

There is no fixed version for Debian:10 jbigkit.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: libjpeg-turbo/libjpeg62-turbo
  • Introduced through: libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+deb10u1

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

There is no fixed version for Debian:10 libjpeg-turbo.

References

low severity

CVE-2018-14048

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

Detailed paths

  • Introduced through: nginx@1.19.10 libpng1.6/libpng16-16@1.6.36-6

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

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

References

low severity

Memory Leak

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

Detailed paths

  • Introduced through: nginx@1.19.10 libpng1.6/libpng16-16@1.6.36-6

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

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

Remediation

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

References

low severity

Out-of-Bounds

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-7+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 libxml2@2.9.4+dfsg1-7+deb10u1

NVD Description

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

Xmlsoft Libxml2 v2.11.0 was discovered to contain an out-of-bounds read via the xmlSAX2StartElement() function at /libxml2/SAX2.c. This vulnerability allows attackers to cause a Denial of Service (DoS) via supplying a crafted XML file. NOTE: the vendor's position is that the product does not support the legacy SAX1 interface with custom callbacks; there is a crash even without crafted input.

Remediation

There is no fixed version for Debian:10 libxml2.

References

low severity

Use After Free

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-7+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 libxml2@2.9.4+dfsg1-7+deb10u1

NVD Description

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

libxml2 through 2.11.5 has a use-after-free that can only occur after a certain memory allocation fails. This occurs in xmlUnlinkNode in tree.c. NOTE: the vendor's position is "I don't think these issues are critical enough to warrant a CVE ID ... because an attacker typically can't control when memory allocations fail."

Remediation

There is no fixed version for Debian:10 libxml2.

References

low severity

CVE-2023-50495

  • Vulnerable module: ncurses/libncursesw6
  • Introduced through: ncurses/libncursesw6@6.1+20181013-2+deb10u2, ncurses/libtinfo6@6.1+20181013-2+deb10u2 and others

Detailed paths

  • Introduced through: nginx@1.19.10 ncurses/libncursesw6@6.1+20181013-2+deb10u2
  • Introduced through: nginx@1.19.10 ncurses/libtinfo6@6.1+20181013-2+deb10u2
  • Introduced through: nginx@1.19.10 ncurses/ncurses-base@6.1+20181013-2+deb10u2
  • Introduced through: nginx@1.19.10 ncurses/ncurses-bin@6.1+20181013-2+deb10u2

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

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

Remediation

There is no fixed version for Debian:10 ncurses.

References

low severity

Double Free

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

There is a double free or corruption in rotateImage() at tiffcrop.c:8839 found in libtiff 4.4.0rc1

Remediation

There is no fixed version for Debian:10 tiff.

References

low severity

Improper Resource Shutdown or Release

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

A vulnerability classified as problematic was found in LibTIFF 4.3.0. Affected by this vulnerability is the TIFF File Handler of tiff2ps. Opening a malicious file leads to a denial of service. The attack can be launched remotely but requires user interaction. The exploit has been disclosed to the public and may be used.

Remediation

There is no fixed version for Debian:10 tiff.

References

low severity

Incorrect Calculation of Buffer Size

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

A flaw was found in libtiff 4.4.0rc1. There is a sysmalloc assertion fail in rotateImage() at tiffcrop.c:8621 that can cause program crash when reading a crafted input.

Remediation

There is no fixed version for Debian:10 tiff.

References

low severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

An issue was discovered in function TIFFReadDirectory libtiff before 4.4.0 allows attackers to cause a denial of service via crafted TIFF file.

Remediation

There is no fixed version for Debian:10 tiff.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

LibTIFF 4.0.9 has a NULL pointer dereference in the jpeg_fdct_16x16 function in jfdctint.c.

Remediation

There is no fixed version for Debian:10 tiff.

References

low severity

Release of Invalid Pointer or Reference

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

It was found in libtiff 4.4.0rc1 that there is an invalid pointer free operation in TIFFClose() at tif_close.c:131 called by tiffcrop.c:2522 that can cause a program crash and denial of service while processing crafted input.

Remediation

There is no fixed version for Debian:10 tiff.

References

low severity

Resource Exhaustion

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

An out-of-memory flaw was found in libtiff. Passing a crafted tiff file to TIFFOpen() API may allow a remote attacker to cause a denial of service via a craft input with size smaller than 379 KB.

Remediation

There is no fixed version for Debian:10 tiff.

References

low severity

XML External Entity (XXE) Injection

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-2+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 expat/libexpat1@2.2.6-2+deb10u1

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

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

Remediation

There is no fixed version for Debian:10 expat.

References

low severity

Race Condition

  • Vulnerable module: libgcrypt20
  • Introduced through: libgcrypt20@1.8.4-5

Detailed paths

  • Introduced through: nginx@1.19.10 libgcrypt20@1.8.4-5

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

There is no fixed version for Debian:10 libgcrypt20.

References

low severity

CVE-2009-4487

  • Vulnerable module: nginx
  • Introduced through: nginx@1.19.10-1~buster

Detailed paths

  • Introduced through: nginx@1.19.10 nginx@1.19.10-1~buster

NVD Description

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

nginx 0.7.64 writes data to a log file without sanitizing non-printable characters, which might allow remote attackers to modify a window's title, or possibly execute arbitrary commands or overwrite files, via an HTTP request containing an escape sequence for a terminal emulator.

Remediation

There is no fixed version for Debian:10 nginx.

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: nginx@1.19.10 shadow/login@1:4.5-1.1
  • Introduced through: nginx@1.19.10 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:10 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:10 shadow.

References

low severity

Cross-site Scripting (XSS)

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-7+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 libxml2@2.9.4+dfsg1-7+deb10u1

NVD Description

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

Possible cross-site scripting vulnerability in libxml after commit 960f0e2.

Remediation

There is no fixed version for Debian:10 libxml2.

References

low severity

Authentication Bypass

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@241-7~deb10u7 and systemd/libudev1@241-7~deb10u7

Detailed paths

  • Introduced through: nginx@1.19.10 systemd/libsystemd0@241-7~deb10u7
  • Introduced through: nginx@1.19.10 systemd/libudev1@241-7~deb10u7

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

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

Remediation

There is no fixed version for Debian:10 systemd.

References

low severity

Out-of-bounds Read

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

A flaw was found in tiffcrop, a program distributed by the libtiff package. A specially crafted tiff file can lead to an out-of-bounds read in the extractImageSection function in tools/tiffcrop.c, resulting in a denial of service and limited information disclosure. This issue affects libtiff versions 4.x.

Remediation

There is no fixed version for Debian:10 tiff.

References

low severity

Race Condition

  • Vulnerable module: curl
  • Introduced through: curl@7.64.0-4+deb10u2 and curl/libcurl4@7.64.0-4+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 curl@7.64.0-4+deb10u2
  • Introduced through: nginx@1.19.10 curl/libcurl4@7.64.0-4+deb10u2

NVD Description

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

A denial of service vulnerability exists in curl <v8.1.0 in the way libcurl provides several different backends for resolving host names, selected at build time. If it is built to use the synchronous resolver, it allows name resolves to time-out slow operations using alarm() and siglongjmp(). When doing this, libcurl used a global buffer that was not mutex protected and a multi-threaded application might therefore crash or otherwise misbehave.

Remediation

There is no fixed version for Debian:10 curl.

References

low severity

Use After Free

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10

Detailed paths

  • Introduced through: nginx@1.19.10 glibc/libc-bin@2.28-10
  • Introduced through: nginx@1.19.10 glibc/libc6@2.28-10

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

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

Remediation

There is no fixed version for Debian:10 glibc.

References

low severity

Use After Free

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10

Detailed paths

  • Introduced through: nginx@1.19.10 glibc/libc-bin@2.28-10
  • Introduced through: nginx@1.19.10 glibc/libc6@2.28-10

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

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

Remediation

There is no fixed version for Debian:10 glibc.

References

low severity

CVE-2023-7008

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@241-7~deb10u7 and systemd/libudev1@241-7~deb10u7

Detailed paths

  • Introduced through: nginx@1.19.10 systemd/libsystemd0@241-7~deb10u7
  • Introduced through: nginx@1.19.10 systemd/libudev1@241-7~deb10u7

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

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

Remediation

There is no fixed version for Debian:10 systemd.

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-2+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 expat/libexpat1@2.2.6-2+deb10u1

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

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

Remediation

There is no fixed version for Debian:10 expat.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: libjpeg-turbo/libjpeg62-turbo
  • Introduced through: libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+deb10u1

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

There is no fixed version for Debian:10 libjpeg-turbo.

References

low severity

Out-of-bounds Write

  • Vulnerable module: libjpeg-turbo/libjpeg62-turbo
  • Introduced through: libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+deb10u1

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

There is no fixed version for Debian:10 libjpeg-turbo.

References

low severity

Buffer Overflow

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

Detailed paths

  • Introduced through: nginx@1.19.10 libpng1.6/libpng16-16@1.6.36-6

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:10 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:10 libpng1.6.

References

low severity

CVE-2018-1000654

  • Vulnerable module: libtasn1-6
  • Introduced through: libtasn1-6@4.13-3

Detailed paths

  • Introduced through: nginx@1.19.10 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:10 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

There is no fixed version for Debian:10 libtasn1-6.

References

low severity

XML External Entity (XXE) Injection

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-7+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 libxml2@2.9.4+dfsg1-7+deb10u1

NVD Description

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

libxml2 2.9.4 and earlier, as used in XMLSec 1.2.23 and earlier and other products, does not offer a flag directly indicating that the current document may be read but other files may not be opened, which makes it easier for remote attackers to conduct XML External Entity (XXE) attacks via a crafted document.

Remediation

There is no fixed version for Debian:10 libxml2.

References

low severity

CVE-2024-0727

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

Detailed paths

  • Introduced through: nginx@1.19.10 openssl@1.1.1d-0+deb10u6
  • Introduced through: nginx@1.19.10 openssl/libssl1.1@1.1.1d-0+deb10u6

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

Issue summary: Processing a maliciously formatted PKCS12 file may lead OpenSSL to crash leading to a potential Denial of Service attack

Impact summary: Applications loading files in the PKCS12 format from untrusted sources might terminate abruptly.

A file in PKCS12 format can contain certificates and keys and may come from an untrusted source. The PKCS12 specification allows certain fields to be NULL, but OpenSSL does not correctly check for this case. This can lead to a NULL pointer dereference that results in OpenSSL crashing. If an application processes PKCS12 files from an untrusted source using the OpenSSL APIs then that application will be vulnerable to this issue.

OpenSSL APIs that are vulnerable to this are: PKCS12_parse(), PKCS12_unpack_p7data(), PKCS12_unpack_p7encdata(), PKCS12_unpack_authsafes() and PKCS12_newpass().

We have also fixed a similar issue in SMIME_write_PKCS7(). However since this function is related to writing data we do not consider it security significant.

The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue.

Remediation

There is no fixed version for Debian:10 openssl.

References

low severity

CVE-2024-22365

  • Vulnerable module: pam/libpam-modules
  • Introduced through: pam/libpam-modules@1.3.1-5, pam/libpam-modules-bin@1.3.1-5 and others

Detailed paths

  • Introduced through: nginx@1.19.10 pam/libpam-modules@1.3.1-5
  • Introduced through: nginx@1.19.10 pam/libpam-modules-bin@1.3.1-5
  • Introduced through: nginx@1.19.10 pam/libpam-runtime@1.3.1-5
  • Introduced through: nginx@1.19.10 pam/libpam0g@1.3.1-5

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

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

Remediation

There is no fixed version for Debian:10 pam.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: nginx@1.19.10 pcre3/libpcre3@2:8.39-12

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:10 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:10 pcre3.

References

low severity

Improper Authentication

  • 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: nginx@1.19.10 shadow/login@1:4.5-1.1
  • Introduced through: nginx@1.19.10 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:10 relevant fixed versions and status.

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

Remediation

There is no fixed version for Debian:10 shadow.

References

low severity

Uncontrolled Recursion

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@241-7~deb10u7 and systemd/libudev1@241-7~deb10u7

Detailed paths

  • Introduced through: nginx@1.19.10 systemd/libsystemd0@241-7~deb10u7
  • Introduced through: nginx@1.19.10 systemd/libudev1@241-7~deb10u7

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

There is no fixed version for Debian:10 systemd.

References

low severity

Out-of-bounds Read

  • Vulnerable module: tar
  • Introduced through: tar@1.30+dfsg-6

Detailed paths

  • Introduced through: nginx@1.19.10 tar@1.30+dfsg-6

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

There is no fixed version for Debian:10 tar.

References

low severity

Out-of-bounds Read

  • Vulnerable module: tar
  • Introduced through: tar@1.30+dfsg-6

Detailed paths

  • Introduced through: nginx@1.19.10 tar@1.30+dfsg-6

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

There is no fixed version for Debian:10 tar.

References

low severity

Out-of-Bounds

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

A flaw was found in libtiff. Due to a memory allocation failure in tif_read.c, a crafted TIFF file can lead to an abort, resulting in denial of service.

Remediation

There is no fixed version for Debian:10 tiff.

References

low severity

Out-of-Bounds

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

In LibTIFF, there is a memory malloc failure in tif_pixarlog.c. A crafted TIFF document can lead to an abort, resulting in a remote denial of service attack.

Remediation

There is no fixed version for Debian:10 tiff.

References

low severity

Out-of-bounds Read

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

Out-of-bounds Read error in tiffcrop in libtiff 4.3.0 allows attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit 46dc8fcd.

Remediation

There is no fixed version for Debian:10 tiff.

References

low severity

Out-of-bounds Read

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

LibTIFF 4.4.0 has an out-of-bounds read in extractImageSection in tools/tiffcrop.c:6905, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit 48d6ece8.

Remediation

There is no fixed version for Debian:10 tiff.

References

low severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

A vulnerability was found in the libtiff library. This security flaw causes a heap buffer overflow in extractContigSamples32bits, tiffcrop.c.

Remediation

There is no fixed version for Debian:10 tiff.

References

low severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

A heap-buffer-overflow vulnerability was found in LibTIFF, in extractImageSection() at tools/tiffcrop.c:7916 and tools/tiffcrop.c:7801. This flaw allows attackers to cause a denial of service via a crafted tiff file.

Remediation

There is no fixed version for Debian:10 tiff.

References

low severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.1.0+git191117-2~deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 tiff/libtiff5@4.1.0+git191117-2~deb10u2

NVD Description

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

An issue was found in the tiffcp utility distributed by the libtiff package where a crafted TIFF file on processing may cause a heap-based buffer overflow leads to an application crash.

Remediation

There is no fixed version for Debian:10 tiff.

References

low severity

Information Exposure

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.33.1-0.1, util-linux/fdisk@2.33.1-0.1 and others

Detailed paths

  • Introduced through: nginx@1.19.10 util-linux@2.33.1-0.1
  • Introduced through: nginx@1.19.10 util-linux/fdisk@2.33.1-0.1
  • Introduced through: nginx@1.19.10 util-linux/libblkid1@2.33.1-0.1
  • Introduced through: nginx@1.19.10 util-linux/libfdisk1@2.33.1-0.1
  • Introduced through: nginx@1.19.10 util-linux/libmount1@2.33.1-0.1
  • Introduced through: nginx@1.19.10 util-linux/libsmartcols1@2.33.1-0.1
  • Introduced through: nginx@1.19.10 util-linux/libuuid1@2.33.1-0.1
  • Introduced through: nginx@1.19.10 util-linux/mount@2.33.1-0.1
  • Introduced through: nginx@1.19.10 util-linux/bsdutils@1:2.33.1-0.1

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:10 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:10 util-linux.

References

low severity

Cryptographic Issues

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

Detailed paths

  • Introduced through: nginx@1.19.10 openssl@1.1.1d-0+deb10u6
  • Introduced through: nginx@1.19.10 openssl/libssl1.1@1.1.1d-0+deb10u6

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

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

Remediation

There is no fixed version for Debian:10 openssl.

References

low severity

Insufficiently Protected Credentials

  • Vulnerable module: curl
  • Introduced through: curl@7.64.0-4+deb10u2 and curl/libcurl4@7.64.0-4+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 curl@7.64.0-4+deb10u2
  • Introduced through: nginx@1.19.10 curl/libcurl4@7.64.0-4+deb10u2

NVD Description

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

When curl is instructed to get content using the metalink feature, and a user name and password are used to download the metalink XML file, those same credentials are then subsequently passed on to each of the servers from which curl will download or try to download the contents from. Often contrary to the user's expectations and intentions and without telling the user it happened.

Remediation

There is no fixed version for Debian:10 curl.

References

low severity

Information Exposure

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10

Detailed paths

  • Introduced through: nginx@1.19.10 glibc/libc-bin@2.28-10
  • Introduced through: nginx@1.19.10 glibc/libc6@2.28-10

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:10 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:10 glibc.

References

low severity

Use of Insufficiently Random Values

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10

Detailed paths

  • Introduced through: nginx@1.19.10 glibc/libc-bin@2.28-10
  • Introduced through: nginx@1.19.10 glibc/libc6@2.28-10

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:10 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:10 glibc.

References

low severity

Use of Insufficiently Random Values

  • Vulnerable module: libxslt/libxslt1.1
  • Introduced through: libxslt/libxslt1.1@1.1.32-2.2~deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 libxslt/libxslt1.1@1.1.32-2.2~deb10u1

NVD Description

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

In libxslt 1.1.29 and earlier, the EXSLT math.random function was not initialized with a random seed during startup, which could cause usage of this function to produce predictable outputs.

Remediation

There is no fixed version for Debian:10 libxslt.

References

low severity

CVE-2020-36309

  • Vulnerable module: nginx
  • Introduced through: nginx@1.19.10-1~buster

Detailed paths

  • Introduced through: nginx@1.19.10 nginx@1.19.10-1~buster

NVD Description

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

ngx_http_lua_module (aka lua-nginx-module) before 0.10.16 in OpenResty allows unsafe characters in an argument when using the API to mutate a URI, or a request or response header.

Remediation

There is no fixed version for Debian:10 nginx.

References

low severity

Improper Check for Unusual or Exceptional Conditions

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

Detailed paths

  • Introduced through: nginx@1.19.10 openssl@1.1.1d-0+deb10u6
  • Introduced through: nginx@1.19.10 openssl/libssl1.1@1.1.1d-0+deb10u6

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

Issue summary: Generating excessively long X9.42 DH keys or checking excessively long X9.42 DH keys or parameters may be very slow.

Impact summary: Applications that use the functions DH_generate_key() to generate an X9.42 DH key may experience long delays. Likewise, applications that use DH_check_pub_key(), DH_check_pub_key_ex() or EVP_PKEY_public_check() to check an X9.42 DH key or X9.42 DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service.

While DH_check() performs all the necessary checks (as of CVE-2023-3817), DH_check_pub_key() doesn't make any of these checks, and is therefore vulnerable for excessively large P and Q parameters.

Likewise, while DH_generate_key() performs a check for an excessively large P, it doesn't check for an excessively large Q.

An application that calls DH_generate_key() or DH_check_pub_key() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack.

DH_generate_key() and DH_check_pub_key() are also called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_pub_key_ex(), EVP_PKEY_public_check(), and EVP_PKEY_generate().

Also vulnerable are the OpenSSL pkey command line application when using the "-pubcheck" option, as well as the OpenSSL genpkey command line application.

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

The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.

Remediation

There is no fixed version for Debian:10 openssl.

References

low severity

Integer Overflow or Wraparound

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

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: nginx@1.19.10 shadow/login@1:4.5-1.1
  • Introduced through: nginx@1.19.10 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:10 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

There is no fixed version for Debian:10 shadow.

References

low severity

Improper Validation of Integrity Check Value

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@241-7~deb10u7 and systemd/libudev1@241-7~deb10u7

Detailed paths

  • Introduced through: nginx@1.19.10 systemd/libsystemd0@241-7~deb10u7
  • Introduced through: nginx@1.19.10 systemd/libudev1@241-7~deb10u7

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:10 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:10 systemd.

References

low severity

Improper Validation of Integrity Check Value

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@241-7~deb10u7 and systemd/libudev1@241-7~deb10u7

Detailed paths

  • Introduced through: nginx@1.19.10 systemd/libsystemd0@241-7~deb10u7
  • Introduced through: nginx@1.19.10 systemd/libudev1@241-7~deb10u7

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:10 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:10 systemd.

References

low severity

Improper Validation of Integrity Check Value

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@241-7~deb10u7 and systemd/libudev1@241-7~deb10u7

Detailed paths

  • Introduced through: nginx@1.19.10 systemd/libsystemd0@241-7~deb10u7
  • Introduced through: nginx@1.19.10 systemd/libudev1@241-7~deb10u7

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:10 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:10 systemd.

References

low severity

Cryptographic Issues

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

Detailed paths

  • Introduced through: nginx@1.19.10 openssl@1.1.1d-0+deb10u6
  • Introduced through: nginx@1.19.10 openssl/libssl1.1@1.1.1d-0+deb10u6

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

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

Remediation

There is no fixed version for Debian:10 openssl.

References

low severity

CVE-2023-4039

  • Vulnerable module: gcc-8/gcc-8-base
  • Introduced through: gcc-8/gcc-8-base@8.3.0-6, gcc-8/libgcc1@1:8.3.0-6 and others

Detailed paths

  • Introduced through: nginx@1.19.10 gcc-8/gcc-8-base@8.3.0-6
  • Introduced through: nginx@1.19.10 gcc-8/libgcc1@1:8.3.0-6
  • Introduced through: nginx@1.19.10 gcc-8/libstdc++6@8.3.0-6

NVD Description

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

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

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

Remediation

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

References

low severity

Race Condition

  • Vulnerable module: coreutils
  • Introduced through: coreutils@8.30-3

Detailed paths

  • Introduced through: nginx@1.19.10 coreutils@8.30-3

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:10 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:10 coreutils.

References

low severity

Improper Initialization

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.47+dfsg-3+deb10u6 and openldap/libldap-common@2.4.47+dfsg-3+deb10u6

Detailed paths

  • Introduced through: nginx@1.19.10 openldap/libldap-2.4-2@2.4.47+dfsg-3+deb10u6
  • Introduced through: nginx@1.19.10 openldap/libldap-common@2.4.47+dfsg-3+deb10u6

NVD Description

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

slapd in OpenLDAP 2.4.45 and earlier creates a PID file after dropping privileges to a non-root account, which might allow local users to kill arbitrary processes by leveraging access to this non-root account for PID file modification before a root script executes a "kill cat /pathname" command, as demonstrated by openldap-initscript.

Remediation

There is no fixed version for Debian:10 openldap.

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

Detailed paths

  • Introduced through: nginx@1.19.10 shadow/login@1:4.5-1.1
  • Introduced through: nginx@1.19.10 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:10 relevant fixed versions and status.

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

Remediation

There is no fixed version for Debian:10 shadow.

References

low severity

Link Following

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@241-7~deb10u7 and systemd/libudev1@241-7~deb10u7

Detailed paths

  • Introduced through: nginx@1.19.10 systemd/libsystemd0@241-7~deb10u7
  • Introduced through: nginx@1.19.10 systemd/libudev1@241-7~deb10u7

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:10 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:10 systemd.

References

low severity

Resource Management Errors

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10

Detailed paths

  • Introduced through: nginx@1.19.10 glibc/libc-bin@2.28-10
  • Introduced through: nginx@1.19.10 glibc/libc6@2.28-10

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:10 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:10 glibc.

References

low severity

Improper Input Validation

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.6.7-4+deb10u6

Detailed paths

  • Introduced through: nginx@1.19.10 gnutls28/libgnutls30@3.6.7-4+deb10u6

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:10 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:10 gnutls28.

References

low severity

Improper Certificate Validation

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.47+dfsg-3+deb10u6 and openldap/libldap-common@2.4.47+dfsg-3+deb10u6

Detailed paths

  • Introduced through: nginx@1.19.10 openldap/libldap-2.4-2@2.4.47+dfsg-3+deb10u6
  • Introduced through: nginx@1.19.10 openldap/libldap-common@2.4.47+dfsg-3+deb10u6

NVD Description

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

libldap in certain third-party OpenLDAP packages has a certificate-validation flaw when the third-party package is asserting RFC6125 support. It considers CN even when there is a non-matching subjectAltName (SAN). This is fixed in, for example, openldap-2.4.46-10.el8 in Red Hat Enterprise Linux.

Remediation

There is no fixed version for Debian:10 openldap.

References

low severity

Improper Verification of Cryptographic Signature

  • Vulnerable module: apt
  • Introduced through: apt@1.8.2.3 and apt/libapt-pkg5.0@1.8.2.3

Detailed paths

  • Introduced through: nginx@1.19.10 apt@1.8.2.3
  • Introduced through: nginx@1.19.10 apt/libapt-pkg5.0@1.8.2.3

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:10 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:10 apt.

References

low severity

CVE-2022-35252

  • Vulnerable module: curl
  • Introduced through: curl@7.64.0-4+deb10u2 and curl/libcurl4@7.64.0-4+deb10u2
  • Fixed in: 7.64.0-4+deb10u4

Detailed paths

  • Introduced through: nginx@1.19.10 curl@7.64.0-4+deb10u2
  • Introduced through: nginx@1.19.10 curl/libcurl4@7.64.0-4+deb10u2

NVD Description

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

When curl is used to retrieve and parse cookies from a HTTP(S) server, itaccepts cookies using control codes that when later are sent back to a HTTPserver might make the server return 400 responses. Effectively allowing a"sister site" to deny service to all siblings.

Remediation

Upgrade Debian:10 curl to version 7.64.0-4+deb10u4 or higher.

References

low severity

CVE-2023-28322

  • Vulnerable module: curl
  • Introduced through: curl@7.64.0-4+deb10u2 and curl/libcurl4@7.64.0-4+deb10u2
  • Fixed in: 7.64.0-4+deb10u8

Detailed paths

  • Introduced through: nginx@1.19.10 curl@7.64.0-4+deb10u2
  • Introduced through: nginx@1.19.10 curl/libcurl4@7.64.0-4+deb10u2

NVD Description

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

An information disclosure vulnerability exists in curl <v8.1.0 when doing HTTP(S) transfers, libcurl might erroneously use the read callback (CURLOPT_READFUNCTION) to ask for data to send, even when the CURLOPT_POSTFIELDS option has been set, if the same handle previously wasused to issue a PUT request which used that callback. This flaw may surprise the application and cause it to misbehave and either send off the wrong data or use memory after free or similar in the second transfer. The problem exists in the logic for a reused handle when it is (expected to be) changed from a PUT to a POST.

Remediation

Upgrade Debian:10 curl to version 7.64.0-4+deb10u8 or higher.

References

low severity

CVE-2023-38546

  • Vulnerable module: curl
  • Introduced through: curl@7.64.0-4+deb10u2 and curl/libcurl4@7.64.0-4+deb10u2
  • Fixed in: 7.64.0-4+deb10u7

Detailed paths

  • Introduced through: nginx@1.19.10 curl@7.64.0-4+deb10u2
  • Introduced through: nginx@1.19.10 curl/libcurl4@7.64.0-4+deb10u2

NVD Description

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

This flaw allows an attacker to insert cookies at will into a running program using libcurl, if the specific series of conditions are met.

libcurl performs transfers. In its API, an application creates "easy handles" that are the individual handles for single transfers.

libcurl provides a function call that duplicates en easy handle called curl_easy_duphandle.

If a transfer has cookies enabled when the handle is duplicated, the cookie-enable state is also cloned - but without cloning the actual cookies. If the source handle did not read any cookies from a specific file on disk, the cloned version of the handle would instead store the file name as none (using the four ASCII letters, no quotes).

Subsequent use of the cloned handle that does not explicitly set a source to load cookies from would then inadvertently load cookies from a file named none - if such a file exists and is readable in the current directory of the program using libcurl. And if using the correct file format of course.

Remediation

Upgrade Debian:10 curl to version 7.64.0-4+deb10u7 or higher.

References

low severity

Use of Incorrectly-Resolved Name or Reference

  • Vulnerable module: curl
  • Introduced through: curl@7.64.0-4+deb10u2 and curl/libcurl4@7.64.0-4+deb10u2
  • Fixed in: 7.64.0-4+deb10u3

Detailed paths

  • Introduced through: nginx@1.19.10 curl@7.64.0-4+deb10u2
  • Introduced through: nginx@1.19.10 curl/libcurl4@7.64.0-4+deb10u2

NVD Description

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

libcurl keeps previously used connections in a connection pool for subsequenttransfers to reuse, if one of them matches the setup.Due to errors in the logic, the config matching function did not take 'issuercert' into account and it compared the involved paths case insensitively,which could lead to libcurl reusing wrong connections.File paths are, or can be, case sensitive on many systems but not all, and caneven vary depending on used file systems.The comparison also didn't include the 'issuer cert' which a transfer can setto qualify how to verify the server certificate.

Remediation

Upgrade Debian:10 curl to version 7.64.0-4+deb10u3 or higher.

References

low severity

Integer Overflow or Wraparound

  • Vulnerable module: curl
  • Introduced through: curl@7.64.0-4+deb10u2 and curl/libcurl4@7.64.0-4+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 curl@7.64.0-4+deb10u2
  • Introduced through: nginx@1.19.10 curl/libcurl4@7.64.0-4+deb10u2

NVD Description

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

Integer overflow vulnerability in tool_operate.c in curl 7.65.2 via a large value as the retry delay. NOTE: many parties report that this has no direct security impact on the curl user; however, it may (in theory) cause a denial of service to associated systems or networks if, for example, --retry-delay is misinterpreted as a value much smaller than what was intended. This is not especially plausible because the overflow only happens if the user was trying to specify that curl should wait weeks (or longer) before trying to recover from a transient error.

Remediation

There is no fixed version for Debian:10 curl.

References

low severity

Information Exposure

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10
  • Fixed in: 2.28-10+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 glibc/libc-bin@2.28-10
  • Introduced through: nginx@1.19.10 glibc/libc6@2.28-10

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:10 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:10 glibc to version 2.28-10+deb10u2 or higher.

References

low severity

Out-of-bounds Write

  • Vulnerable module: gnupg2/gpgv
  • Introduced through: gnupg2/gpgv@2.2.12-1+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 gnupg2/gpgv@2.2.12-1+deb10u1

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:10 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:10 gnupg2.

References

low severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: nginx@1.19.10 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:10 relevant fixed versions and status.

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

Remediation

There is no fixed version for Debian:10 libsepol.

References

low severity

Use After Free

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

Detailed paths

  • Introduced through: nginx@1.19.10 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:10 relevant fixed versions and status.

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

Remediation

There is no fixed version for Debian:10 libsepol.

References

low severity

Use After Free

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

Detailed paths

  • Introduced through: nginx@1.19.10 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:10 relevant fixed versions and status.

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

Remediation

There is no fixed version for Debian:10 libsepol.

References

low severity

Use After Free

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

Detailed paths

  • Introduced through: nginx@1.19.10 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:10 relevant fixed versions and status.

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

Remediation

There is no fixed version for Debian:10 libsepol.

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

Detailed paths

  • Introduced through: nginx@1.19.10 shadow/login@1:4.5-1.1
  • Introduced through: nginx@1.19.10 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:10 relevant fixed versions and status.

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

Remediation

There is no fixed version for Debian:10 shadow.

References

low severity

Missing Initialization of Resource

  • Vulnerable module: curl
  • Introduced through: curl@7.64.0-4+deb10u2 and curl/libcurl4@7.64.0-4+deb10u2
  • Fixed in: 7.64.0-4+deb10u3

Detailed paths

  • Introduced through: nginx@1.19.10 curl@7.64.0-4+deb10u2
  • Introduced through: nginx@1.19.10 curl/libcurl4@7.64.0-4+deb10u2

NVD Description

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

curl 7.7 through 7.76.1 suffers from an information disclosure when the -t command line option, known as CURLOPT_TELNETOPTIONS in libcurl, is used to send variable=content pairs to TELNET servers. Due to a flaw in the option parser for sending NEW_ENV variables, libcurl could be made to pass on uninitialized data from a stack based buffer to the server, resulting in potentially revealing sensitive internal information to the server using a clear-text network protocol.

Remediation

Upgrade Debian:10 curl to version 7.64.0-4+deb10u3 or higher.

References

low severity

Double Free

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10
  • Fixed in: 2.28-10+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 glibc/libc-bin@2.28-10
  • Introduced through: nginx@1.19.10 glibc/libc6@2.28-10

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:10 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:10 glibc to version 2.28-10+deb10u2 or higher.

References

low severity

Missing Release of Resource after Effective Lifetime

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@241-7~deb10u7 and systemd/libudev1@241-7~deb10u7

Detailed paths

  • Introduced through: nginx@1.19.10 systemd/libsystemd0@241-7~deb10u7
  • Introduced through: nginx@1.19.10 systemd/libudev1@241-7~deb10u7

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

There is no fixed version for Debian:10 systemd.

References

low severity

CVE-2024-2379

  • Vulnerable module: curl
  • Introduced through: curl@7.64.0-4+deb10u2 and curl/libcurl4@7.64.0-4+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 curl@7.64.0-4+deb10u2
  • Introduced through: nginx@1.19.10 curl/libcurl4@7.64.0-4+deb10u2

NVD Description

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

libcurl skips the certificate verification for a QUIC connection under certain conditions, when built to use wolfSSL. If told to use an unknown/bad cipher or curve, the error path accidentally skips the verification and returns OK, thus ignoring any certificate problems.

Remediation

There is no fixed version for Debian:10 curl.

References

low severity

CVE-2024-2398

  • Vulnerable module: curl
  • Introduced through: curl@7.64.0-4+deb10u2 and curl/libcurl4@7.64.0-4+deb10u2

Detailed paths

  • Introduced through: nginx@1.19.10 curl@7.64.0-4+deb10u2
  • Introduced through: nginx@1.19.10 curl/libcurl4@7.64.0-4+deb10u2

NVD Description

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

When an application tells libcurl it wants to allow HTTP/2 server push, and the amount of received headers for the push surpasses the maximum allowed limit (1000), libcurl aborts the server push. When aborting, libcurl inadvertently does not free all the previously allocated headers and instead leaks the memory. Further, this error condition fails silently and is therefore not easily detected by an application.

Remediation

There is no fixed version for Debian:10 curl.

References

low severity

CVE-2024-28757

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.6-2+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 expat/libexpat1@2.2.6-2+deb10u1

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

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

Remediation

There is no fixed version for Debian:10 expat.

References

low severity
new

CVE-2024-2961

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10

Detailed paths

  • Introduced through: nginx@1.19.10 glibc/libc-bin@2.28-10
  • Introduced through: nginx@1.19.10 glibc/libc6@2.28-10

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

There is no fixed version for Debian:10 glibc.

References

low severity
new

CVE-2024-33599

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10

Detailed paths

  • Introduced through: nginx@1.19.10 glibc/libc-bin@2.28-10
  • Introduced through: nginx@1.19.10 glibc/libc6@2.28-10

NVD Description

This vulnerability has not been analyzed by NVD yet.

Remediation

There is no fixed version for Debian:10 glibc.

References

low severity
new

CVE-2024-33600

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10

Detailed paths

  • Introduced through: nginx@1.19.10 glibc/libc-bin@2.28-10
  • Introduced through: nginx@1.19.10 glibc/libc6@2.28-10

NVD Description

This vulnerability has not been analyzed by NVD yet.

Remediation

There is no fixed version for Debian:10 glibc.

References

low severity
new

CVE-2024-33601

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10

Detailed paths

  • Introduced through: nginx@1.19.10 glibc/libc-bin@2.28-10
  • Introduced through: nginx@1.19.10 glibc/libc6@2.28-10

NVD Description

This vulnerability has not been analyzed by NVD yet.

Remediation

There is no fixed version for Debian:10 glibc.

References

low severity
new

CVE-2024-33602

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10

Detailed paths

  • Introduced through: nginx@1.19.10 glibc/libc-bin@2.28-10
  • Introduced through: nginx@1.19.10 glibc/libc6@2.28-10

NVD Description

This vulnerability has not been analyzed by NVD yet.

Remediation

There is no fixed version for Debian:10 glibc.

References

low severity

CVE-2024-26458

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.17-3+deb10u1, krb5/libk5crypto3@1.17-3+deb10u1 and others

Detailed paths

  • Introduced through: nginx@1.19.10 krb5/libgssapi-krb5-2@1.17-3+deb10u1
  • Introduced through: nginx@1.19.10 krb5/libk5crypto3@1.17-3+deb10u1
  • Introduced through: nginx@1.19.10 krb5/libkrb5-3@1.17-3+deb10u1
  • Introduced through: nginx@1.19.10 krb5/libkrb5support0@1.17-3+deb10u1

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:10 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:10 krb5.

References

low severity

CVE-2024-26461

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.17-3+deb10u1, krb5/libk5crypto3@1.17-3+deb10u1 and others

Detailed paths

  • Introduced through: nginx@1.19.10 krb5/libgssapi-krb5-2@1.17-3+deb10u1
  • Introduced through: nginx@1.19.10 krb5/libk5crypto3@1.17-3+deb10u1
  • Introduced through: nginx@1.19.10 krb5/libkrb5-3@1.17-3+deb10u1
  • Introduced through: nginx@1.19.10 krb5/libkrb5support0@1.17-3+deb10u1

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:10 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:10 krb5.

References

low severity

CVE-2024-26462

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.17-3+deb10u1, krb5/libk5crypto3@1.17-3+deb10u1 and others

Detailed paths

  • Introduced through: nginx@1.19.10 krb5/libgssapi-krb5-2@1.17-3+deb10u1
  • Introduced through: nginx@1.19.10 krb5/libk5crypto3@1.17-3+deb10u1
  • Introduced through: nginx@1.19.10 krb5/libkrb5-3@1.17-3+deb10u1
  • Introduced through: nginx@1.19.10 krb5/libkrb5support0@1.17-3+deb10u1

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:10 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:10 krb5.

References

low severity

Information Exposure

  • Vulnerable module: libgcrypt20
  • Introduced through: libgcrypt20@1.8.4-5

Detailed paths

  • Introduced through: nginx@1.19.10 libgcrypt20@1.8.4-5

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:10 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:10 libgcrypt20.

References

low severity

CVE-2023-45918

  • Vulnerable module: ncurses/libncursesw6
  • Introduced through: ncurses/libncursesw6@6.1+20181013-2+deb10u2, ncurses/libtinfo6@6.1+20181013-2+deb10u2 and others

Detailed paths

  • Introduced through: nginx@1.19.10 ncurses/libncursesw6@6.1+20181013-2+deb10u2
  • Introduced through: nginx@1.19.10 ncurses/libtinfo6@6.1+20181013-2+deb10u2
  • Introduced through: nginx@1.19.10 ncurses/ncurses-base@6.1+20181013-2+deb10u2
  • Introduced through: nginx@1.19.10 ncurses/ncurses-bin@6.1+20181013-2+deb10u2

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

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

Remediation

There is no fixed version for Debian:10 ncurses.

References

low severity
new

CVE-2024-28182

  • Vulnerable module: nghttp2/libnghttp2-14
  • Introduced through: nghttp2/libnghttp2-14@1.36.0-2+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 nghttp2/libnghttp2-14@1.36.0-2+deb10u1

NVD Description

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

nghttp2 is an implementation of the Hypertext Transfer Protocol version 2 in C. The nghttp2 library prior to version 1.61.0 keeps reading the unbounded number of HTTP/2 CONTINUATION frames even after a stream is reset to keep HPACK context in sync. This causes excessive CPU usage to decode HPACK stream. nghttp2 v1.61.0 mitigates this vulnerability by limiting the number of CONTINUATION frames it accepts per stream. There is no workaround for this vulnerability.

Remediation

There is no fixed version for Debian:10 nghttp2.

References

low severity
new

CVE-2024-2511

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

Detailed paths

  • Introduced through: nginx@1.19.10 openssl@1.1.1d-0+deb10u6
  • Introduced through: nginx@1.19.10 openssl/libssl1.1@1.1.1d-0+deb10u6

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

There is no fixed version for Debian:10 openssl.

References

low severity

CVE-2023-50868

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@241-7~deb10u7 and systemd/libudev1@241-7~deb10u7

Detailed paths

  • Introduced through: nginx@1.19.10 systemd/libsystemd0@241-7~deb10u7
  • Introduced through: nginx@1.19.10 systemd/libudev1@241-7~deb10u7

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

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

Remediation

There is no fixed version for Debian:10 systemd.

References

low severity

CVE-2023-39804

  • Vulnerable module: tar
  • Introduced through: tar@1.30+dfsg-6
  • Fixed in: 1.30+dfsg-6+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 tar@1.30+dfsg-6

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:10 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:10 tar to version 1.30+dfsg-6+deb10u1 or higher.

References

low severity
new

CVE-2024-28085

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.33.1-0.1, util-linux/fdisk@2.33.1-0.1 and others
  • Fixed in: 2.33.1-0.1+deb10u1

Detailed paths

  • Introduced through: nginx@1.19.10 util-linux@2.33.1-0.1
  • Introduced through: nginx@1.19.10 util-linux/fdisk@2.33.1-0.1
  • Introduced through: nginx@1.19.10 util-linux/libblkid1@2.33.1-0.1
  • Introduced through: nginx@1.19.10 util-linux/libfdisk1@2.33.1-0.1
  • Introduced through: nginx@1.19.10 util-linux/libmount1@2.33.1-0.1
  • Introduced through: nginx@1.19.10 util-linux/libsmartcols1@2.33.1-0.1
  • Introduced through: nginx@1.19.10 util-linux/libuuid1@2.33.1-0.1
  • Introduced through: nginx@1.19.10 util-linux/mount@2.33.1-0.1

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:10 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:10 util-linux to version 2.33.1-0.1+deb10u1 or higher.

References