Vulnerabilities

 1047 via 2137 paths

Dependencies

 342

Source

 Group 6 Copy Created with Sketch. Docker

Target OS

 debian:unstable
Test your Docker Hub image against our market leading vulnerability database Sign up for free
Severity
  • 100
  • 299
  • 295
  • 353
Status
  • 1047
  • 0
  • 0

critical severity

Embedded Malicious Code

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › xz-utils@5.2.2-1.3
  • Introduced through: openjdk@10-ea-jdk › xz-utils/liblzma5@5.2.2-1.3

NVD Description

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

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

Remediation

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

References

Embedded Malicious Code vulnerability report

critical severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › apr/libapr1@1.6.3-2

NVD Description

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

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

Remediation

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

References

Integer Overflow or Wraparound vulnerability report

critical severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › bzip2@1.0.6-8.1
  • Introduced through: openjdk@10-ea-jdk › bzip2/libbz2-1.0@1.0.6-8.1

NVD Description

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

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

Remediation

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

References

Out-of-bounds Write vulnerability report

critical severity

Buffer Overflow

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.66.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

Heap buffer overflow in the TFTP protocol handler in cURL 7.19.4 to 7.65.3.

Remediation

Upgrade Debian:unstable curl to version 7.66.0-1 or higher.

References

Buffer Overflow vulnerability report

critical severity

Double Free

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.66.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

Double-free vulnerability in the FTP-kerberos code in cURL 7.52.0 to 7.65.3.

Remediation

Upgrade Debian:unstable curl to version 7.66.0-1 or higher.

References

Double Free vulnerability report

critical severity

Exposure of Resource to Wrong Sphere

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.86.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

References

Exposure of Resource to Wrong Sphere vulnerability report

critical severity

Incorrect Default Permissions

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.84.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

When curl < 7.84.0 saves cookies, alt-svc and hsts data to local files, it makes the operation atomic by finalizing the operation with a rename from a temporary name to the final target file name.In that rename operation, it might accidentally widen the permissions for the target file, leaving the updated file accessible to more users than intended.

Remediation

Upgrade Debian:unstable curl to version 7.84.0-1 or higher.

References

Incorrect Default Permissions vulnerability report

critical severity

Integer Overflow or Wraparound

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.62.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

curl before version 7.61.1 is vulnerable to a buffer overrun in the NTLM authentication code. The internal function Curl_ntlm_core_mk_nt_hash multiplies the length of the password by two (SUM) to figure out how large temporary storage area to allocate from the heap. The length value is then subsequently used to iterate over the password and generate output into the allocated storage buffer. On systems with a 32 bit size_t, the math to calculate SUM triggers an integer overflow when the password length exceeds 2GB (2^31 bytes). This integer overflow usually causes a very small buffer to actually get allocated instead of the intended very huge one, making the use of that buffer end up in a heap buffer overflow. (This bug is almost identical to CVE-2017-8816.)

Remediation

Upgrade Debian:unstable curl to version 7.62.0-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

critical severity

Out-of-Bounds

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.62.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

Curl versions 7.33.0 through 7.61.1 are vulnerable to a buffer overrun in the SASL authentication code that may lead to denial of service.

Remediation

Upgrade Debian:unstable curl to version 7.62.0-1 or higher.

References

Out-of-Bounds vulnerability report

critical severity

Out-of-bounds Write

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.64.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

libcurl versions from 7.36.0 to before 7.64.0 are vulnerable to a stack-based buffer overflow. The function creating an outgoing NTLM type-3 header (lib/vauth/ntlm.c:Curl_auth_create_ntlm_type3_message()), generates the request HTTP header contents based on previously received data. The check that exists to prevent the local buffer from getting overflowed is implemented wrongly (using unsigned math) and as such it does not prevent the overflow from happening. This output data can grow larger than the local buffer if very large 'nt response' data is extracted from a previous NTLMv2 header provided by the malicious or broken HTTP server. Such a 'large value' needs to be around 1000 bytes or more. The actual payload data copied to the target buffer comes from the NTLMv2 type-2 response header.

Remediation

Upgrade Debian:unstable curl to version 7.64.0-1 or higher.

References

Out-of-bounds Write vulnerability report

critical severity

Out-of-bounds Write

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.60.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

A buffer overflow exists in curl 7.12.3 to and including curl 7.58.0 in the FTP URL handling that allows an attacker to cause a denial of service or worse.

Remediation

Upgrade Debian:unstable curl to version 7.60.0-1 or higher.

References

Out-of-bounds Write vulnerability report

critical severity

Out-of-bounds Write

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.60.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

curl version curl 7.54.1 to and including curl 7.59.0 contains a CWE-122: Heap-based Buffer Overflow vulnerability in denial of service and more that can result in curl might overflow a heap based memory buffer when closing down an FTP connection with very long server command replies.. This vulnerability appears to have been fixed in curl < 7.54.1 and curl >= 7.60.0.

Remediation

Upgrade Debian:unstable curl to version 7.60.0-1 or higher.

References

Out-of-bounds Write vulnerability report

critical severity

Out-of-bounds Write

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.61.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

Curl_smtp_escape_eob in lib/smtp.c in curl 7.54.1 to and including curl 7.60.0 has a heap-based buffer overflow that might be exploitable by an attacker who can control the data that curl transmits over SMTP with certain settings (i.e., use of a nonstandard --limit-rate argument or CURLOPT_BUFFERSIZE value).

Remediation

Upgrade Debian:unstable curl to version 7.61.0-1 or higher.

References

Out-of-bounds Write vulnerability report

critical severity

Out-of-bounds Write

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 8.3.0-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

This flaw makes curl overflow a heap based buffer in the SOCKS5 proxy handshake.

When curl is asked to pass along the host name to the SOCKS5 proxy to allow that to resolve the address instead of it getting done by curl itself, the maximum length that host name can be is 255 bytes.

If the host name is detected to be longer, curl switches to local name resolving and instead passes on the resolved address only. Due to this bug, the local variable that means "let the host resolve the name" could get the wrong value during a slow SOCKS5 handshake, and contrary to the intention, copy the too long host name to the target buffer instead of copying just the resolved address there.

The target buffer being a heap based buffer, and the host name coming from the URL that curl has been told to operate with.

Remediation

Upgrade Debian:unstable curl to version 8.3.0-3 or higher.

References

Out-of-bounds Write vulnerability report

critical severity

Use After Free

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.62.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

A heap use-after-free flaw was found in curl versions from 7.59.0 through 7.61.1 in the code related to closing an easy handle. When closing and cleaning up an 'easy' handle in the Curl_close() function, the library code first frees a struct (without nulling the pointer) and might then subsequently erroneously write to a struct field within that already freed struct.

Remediation

Upgrade Debian:unstable curl to version 7.62.0-1 or higher.

References

Use After Free vulnerability report

critical severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › db5.3/libdb5.3@5.3.28-13.1+b1

NVD Description

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

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

Remediation

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

References

Out-of-bounds Read vulnerability report

critical severity

Directory Traversal

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › dpkg@1.19.0.5

NVD Description

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

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

Remediation

Upgrade Debian:unstable dpkg to version 1.21.8 or higher.

References

Directory Traversal vulnerability report

critical severity

Exposure of Resource to Wrong Sphere

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › expat/libexpat1@2.2.5-3

NVD Description

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

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

Remediation

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

References

Exposure of Resource to Wrong Sphere vulnerability report

critical severity

Improper Encoding or Escaping of Output

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › expat/libexpat1@2.2.5-3

NVD Description

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

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

Remediation

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

References

Improper Encoding or Escaping of Output vulnerability report

critical severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › expat/libexpat1@2.2.5-3

NVD Description

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

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

Remediation

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

References

Integer Overflow or Wraparound vulnerability report

critical severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › expat/libexpat1@2.2.5-3

NVD Description

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

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

Remediation

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

References

Integer Overflow or Wraparound vulnerability report

critical severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › expat/libexpat1@2.2.5-3

NVD Description

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

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

Remediation

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

References

Integer Overflow or Wraparound vulnerability report

critical severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.5-3
  • Fixed in: 2.4.3-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › expat/libexpat1@2.2.5-3

NVD Description

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

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

Remediation

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

References

Integer Overflow or Wraparound vulnerability report

critical severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › expat/libexpat1@2.2.5-3

NVD Description

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

In Expat (aka libexpat) before 2.4.5, there is an integer overflow in storeRawNames.

Remediation

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

References

Integer Overflow or Wraparound vulnerability report

critical severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.5-3
  • Fixed in: 2.6.2-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › expat/libexpat1@2.2.5-3

NVD Description

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

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

Remediation

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

References

Integer Overflow or Wraparound vulnerability report

critical severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.5-3
  • Fixed in: 2.6.2-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › expat/libexpat1@2.2.5-3

NVD Description

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

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

Remediation

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

References

Integer Overflow or Wraparound vulnerability report

critical severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › freetype/libfreetype6@2.8.1-2

NVD Description

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

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

Remediation

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

References

Out-of-bounds Write vulnerability report

critical severity

Arbitrary Argument Injection

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.19.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

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

Git before 2.14.5, 2.15.x before 2.15.3, 2.16.x before 2.16.5, 2.17.x before 2.17.2, 2.18.x before 2.18.1, and 2.19.x before 2.19.1 allows remote code execution during processing of a recursive "git clone" of a superproject if a .gitmodules file has a URL field beginning with a '-' character.

Remediation

Upgrade Debian:unstable git to version 1:2.19.1-1 or higher.

References

Arbitrary Argument Injection vulnerability report

critical severity

CVE-2019-1353

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.24.0-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

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

An issue was found in Git before v2.24.1, v2.23.1, v2.22.2, v2.21.1, v2.20.2, v2.19.3, v2.18.2, v2.17.3, v2.16.6, v2.15.4, and v2.14.6. When running Git in the Windows Subsystem for Linux (also known as "WSL") while accessing a working directory on a regular Windows drive, none of the NTFS protections were active.

Remediation

Upgrade Debian:unstable git to version 1:2.24.0-2 or higher.

References

CVE-2019-1353 vulnerability report

critical severity

Integer Overflow or Wraparound

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.39.1-0.1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

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

Git is distributed revision control system. gitattributes are a mechanism to allow defining attributes for paths. These attributes can be defined by adding a .gitattributes file to the repository, which contains a set of file patterns and the attributes that should be set for paths matching this pattern. When parsing gitattributes, multiple integer overflows can occur when there is a huge number of path patterns, a huge number of attributes for a single pattern, or when the declared attribute names are huge. These overflows can be triggered via a crafted .gitattributes file that may be part of the commit history. Git silently splits lines longer than 2KB when parsing gitattributes from a file, but not when parsing them from the index. Consequentially, the failure mode depends on whether the file exists in the working tree, the index or both. This integer overflow can result in arbitrary heap reads and writes, which may result in remote code execution. The problem has been patched in the versions published on 2023-01-17, going back to v2.30.7. Users are advised to upgrade. There are no known workarounds for this issue.

Remediation

Upgrade Debian:unstable git to version 1:2.39.1-0.1 or higher.

References

Integer Overflow or Wraparound vulnerability report

critical severity

Integer Overflow or Wraparound

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.39.1-0.1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

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

Git is distributed revision control system. git log can display commits in an arbitrary format using its --format specifiers. This functionality is also exposed to git archive via the export-subst gitattribute. When processing the padding operators, there is a integer overflow in pretty.c::format_and_pad_commit() where a size_t is stored improperly as an int, and then added as an offset to a memcpy(). This overflow can be triggered directly by a user running a command which invokes the commit formatting machinery (e.g., git log --format=...). It may also be triggered indirectly through git archive via the export-subst mechanism, which expands format specifiers inside of files within the repository during a git archive. This integer overflow can result in arbitrary heap writes, which may result in arbitrary code execution. The problem has been patched in the versions published on 2023-01-17, going back to v2.30.7. Users are advised to upgrade. Users who are unable to upgrade should disable git archive in untrusted repositories. If you expose git archive via git daemon, disable it by running git config --global daemon.uploadArch false.

Remediation

Upgrade Debian:unstable git to version 1:2.39.1-0.1 or higher.

References

Integer Overflow or Wraparound vulnerability report

critical severity

Untrusted Search Path

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.19.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

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

Git before 2.19.2 on Linux and UNIX executes commands from the current working directory (as if '.' were at the end of $PATH) in certain cases involving the run_command() API and run-command.c, because there was a dangerous change from execvp to execv during 2017.

Remediation

Upgrade Debian:unstable git to version 1:2.19.2-1 or higher.

References

Untrusted Search Path vulnerability report

critical severity

Race Condition

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.56.1-2 and glib2.0/libglib2.0-data@2.56.1-2
  • Fixed in: 2.58.3-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-0@2.56.1-2
  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-data@2.56.1-2

NVD Description

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

file_copy_fallback in gio/gfile.c in GNOME GLib 2.15.0 through 2.61.1 does not properly restrict file permissions while a copy operation is in progress. Instead, default permissions are used.

Remediation

Upgrade Debian:unstable glib2.0 to version 2.58.3-2 or higher.

References

Race Condition vulnerability report

critical severity

Buffer Overflow

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

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

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

Remediation

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

References

Buffer Overflow vulnerability report

critical severity

Buffer Overflow

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

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

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

Remediation

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

References

Buffer Overflow vulnerability report

critical severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

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

An SSE2-optimized memmove implementation for i386 in sysdeps/i386/i686/multiarch/memcpy-sse2-unaligned.S in the GNU C Library (aka glibc or libc6) 2.21 through 2.27 does not correctly perform the overlapping memory check if the source memory range spans the middle of the address space, resulting in corrupt data being produced by the copy operation. This may disclose information to context-dependent attackers, or result in a denial of service, or, possibly, code execution.

Remediation

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

References

Out-of-Bounds vulnerability report

critical severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

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

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

Remediation

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

References

Out-of-bounds Read vulnerability report

critical severity

Use After Free

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

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

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

Remediation

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

References

Use After Free vulnerability report

critical severity

Use After Free

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.18-1
  • Fixed in: 3.7.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gnutls28/libgnutls30@3.5.18-1

NVD Description

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

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

Remediation

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

References

Use After Free vulnerability report

critical severity

Use After Free

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.18-1
  • Fixed in: 3.7.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gnutls28/libgnutls30@3.5.18-1

NVD Description

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

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

Remediation

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

References

Use After Free vulnerability report

critical severity

Integer Overflow or Wraparound

  • Vulnerable module: icu/libicu57
  • Introduced through: icu/libicu57@57.1-9
  • Fixed in: 63.1-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › icu/libicu57@57.1-9

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

International Components for Unicode (ICU) for C/C++ 63.1 has an integer overflow in number::impl::DecimalQuantity::toScientificString() in i18n/number_decimalquantity.cpp.

Remediation

Upgrade Debian:unstable icu to version 63.1-3 or higher.

References

Integer Overflow or Wraparound vulnerability report

critical severity

Buffer Overflow

  • Vulnerable module: inetutils/inetutils-ping
  • Introduced through: inetutils/inetutils-ping@2:1.9.4-3
  • Fixed in: 2:1.9.4-12

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › inetutils/inetutils-ping@2:1.9.4-3

NVD Description

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

utility.c in telnetd in netkit telnet through 0.17 allows remote attackers to execute arbitrary code via short writes or urgent data, because of a buffer overflow involving the netclear and nextitem functions.

Remediation

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

References

Buffer Overflow vulnerability report

critical severity

Out-of-bounds Write

  • Vulnerable module: json-c/libjson-c3
  • Introduced through: json-c/libjson-c3@0.12.1-1.3
  • Fixed in: 0.16-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › json-c/libjson-c3@0.12.1-1.3

NVD Description

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

An issue was discovered in json-c from 20200420 (post 0.14 unreleased code) through 0.15-20200726. A stack-buffer-overflow exists in the auxiliary sample program json_parse which is located in the function parseit.

Remediation

Upgrade Debian:unstable json-c to version 0.16-1 or higher.

References

Out-of-bounds Write vulnerability report

critical severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libidn2/libidn2-0@2.0.4-1.1

NVD Description

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

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

Remediation

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

References

Out-of-bounds Write vulnerability report

critical severity

Integer Overflow or Wraparound

  • Vulnerable module: libksba/libksba8
  • Introduced through: libksba/libksba8@1.3.5-2
  • Fixed in: 1.6.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libksba/libksba8@1.3.5-2

NVD Description

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

A vulnerability was found in the Libksba library due to an integer overflow within the CRL parser. The vulnerability can be exploited remotely for code execution on the target system by passing specially crafted data to the application, for example, a malicious S/MIME attachment.

Remediation

Upgrade Debian:unstable libksba to version 1.6.2-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

critical severity

Integer Overflow or Wraparound

  • Vulnerable module: libksba/libksba8
  • Introduced through: libksba/libksba8@1.3.5-2
  • Fixed in: 1.6.3-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libksba/libksba8@1.3.5-2

NVD Description

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

Libksba before 1.6.3 is prone to an integer overflow vulnerability in the CRL signature parser.

Remediation

Upgrade Debian:unstable libksba to version 1.6.3-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

critical severity

Buffer Overflow

  • Vulnerable module: libproxy/libproxy1v5
  • Introduced through: libproxy/libproxy1v5@0.4.15-1
  • Fixed in: 0.4.15-15

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libproxy/libproxy1v5@0.4.15-1

NVD Description

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

url.cpp in libproxy through 0.4.15 is prone to a buffer overflow when PAC is enabled, as demonstrated by a large PAC file that is delivered without a Content-length header.

Remediation

Upgrade Debian:unstable libproxy to version 0.4.15-15 or higher.

References

Buffer Overflow vulnerability report

critical severity

Buffer Overflow

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-6@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-data@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-dev@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-doc@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-xcb1@2:1.6.5-1

NVD Description

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

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

Remediation

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

References

Buffer Overflow vulnerability report

critical severity

CVE-2024-56171

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.12.7+dfsg+really2.9.14-0.4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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

libxml2 before 2.12.10 and 2.13.x before 2.13.6 has a use-after-free in xmlSchemaIDCFillNodeTables and xmlSchemaBubbleIDCNodeTables in xmlschemas.c. To exploit this, a crafted XML document must be validated against an XML schema with certain identity constraints, or a crafted XML schema must be used.

Remediation

Upgrade Debian:unstable libxml2 to version 2.12.7+dfsg+really2.9.14-0.4 or higher.

References

CVE-2024-56171 vulnerability report

critical severity

Out-of-bounds Write

  • Vulnerable module: lz4/liblz4-1
  • Introduced through: lz4/liblz4-1@0.0~r131-2+b1
  • Fixed in: 1.9.3-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › lz4/liblz4-1@0.0~r131-2+b1

NVD Description

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

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

Remediation

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

References

Out-of-bounds Write vulnerability report

critical severity

Integer Overflow or Wraparound

  • Vulnerable module: mercurial
  • Introduced through: mercurial@4.5-1 and mercurial/mercurial-common@4.5-1
  • Fixed in: 4.6.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › mercurial@4.5-1
  • Introduced through: openjdk@10-ea-jdk › mercurial/mercurial-common@4.5-1

NVD Description

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

mpatch.c in Mercurial before 4.6.1 mishandles integer addition and subtraction, aka OVE-20180430-0002.

Remediation

Upgrade Debian:unstable mercurial to version 4.6.1-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

critical severity

Insufficient Verification of Data Authenticity

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nss/libnss3@2:3.36.1-1

NVD Description

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

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

Remediation

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

References

Insufficient Verification of Data Authenticity vulnerability report

critical severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nss/libnss3@2:3.36.1-1

NVD Description

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

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

Remediation

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

References

Out-of-bounds Write vulnerability report

critical severity

SQL Injection

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1 and openldap/libldap-common@2.4.45+dfsg-1
  • Fixed in: 2.5.12+dfsg-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-2.4-2@2.4.45+dfsg-1
  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-common@2.4.45+dfsg-1

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:unstable 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:unstable openldap to version 2.5.12+dfsg-1 or higher.

References

SQL Injection vulnerability report

critical severity

CVE-2023-28531

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:7.6p1-4
  • Fixed in: 1:9.3p1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssh/openssh-client@1:7.6p1-4

NVD Description

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

ssh-add in OpenSSH before 9.3 adds smartcard keys to ssh-agent without the intended per-hop destination constraints. The earliest affected version is 8.9.

Remediation

Upgrade Debian:unstable openssh to version 1:9.3p1-1 or higher.

References

CVE-2023-28531 vulnerability report

critical severity

Unquoted Search Path or Element

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:7.6p1-4
  • Fixed in: 1:9.3p2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssh/openssh-client@1:7.6p1-4

NVD Description

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

The PKCS#11 feature in ssh-agent in OpenSSH before 9.3p2 has an insufficiently trustworthy search path, leading to remote code execution if an agent is forwarded to an attacker-controlled system. (Code in /usr/lib is not necessarily safe for loading into ssh-agent.) NOTE: this issue exists because of an incomplete fix for CVE-2016-10009.

Remediation

Upgrade Debian:unstable openssh to version 1:9.3p2-1 or higher.

References

Unquoted Search Path or Element vulnerability report

critical severity

Buffer Overflow

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

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

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

Remediation

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

References

Buffer Overflow vulnerability report

critical severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

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

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

Remediation

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

References

Out-of-bounds Write vulnerability report

critical severity

Out-of-bounds Write

  • Vulnerable module: pango1.0/libpango-1.0-0
  • Introduced through: pango1.0/libpango-1.0-0@1.42.1-1, pango1.0/libpangocairo-1.0-0@1.42.1-1 and others
  • Fixed in: 1.42.4-7

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › pango1.0/libpango-1.0-0@1.42.1-1
  • Introduced through: openjdk@10-ea-jdk › pango1.0/libpangocairo-1.0-0@1.42.1-1
  • Introduced through: openjdk@10-ea-jdk › pango1.0/libpangoft2-1.0-0@1.42.1-1

NVD Description

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

Gnome Pango 1.42 and later is affected by: Buffer Overflow. The impact is: The heap based buffer overflow can be used to get code execution. The component is: function name: pango_log2vis_get_embedding_levels, assignment of nchars and the loop condition. The attack vector is: Bug can be used when application pass invalid utf-8 strings to functions like pango_itemize.

Remediation

Upgrade Debian:unstable pango1.0 to version 1.42.4-7 or higher.

References

Out-of-bounds Write vulnerability report

critical severity

Out-of-Bounds

  • Vulnerable module: perl
  • Introduced through: perl@5.26.1-5, perl/libperl5.26@5.26.1-5 and others
  • Fixed in: 5.28.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › perl@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/libperl5.26@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-base@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-modules-5.26@5.26.1-5

NVD Description

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

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

Remediation

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

References

Out-of-Bounds vulnerability report

critical severity

Out-of-Bounds

  • Vulnerable module: perl
  • Introduced through: perl@5.26.1-5, perl/libperl5.26@5.26.1-5 and others
  • Fixed in: 5.28.0-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › perl@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/libperl5.26@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-base@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-modules-5.26@5.26.1-5

NVD Description

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

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

Remediation

Upgrade Debian:unstable perl to version 5.28.0-3 or higher.

References

Out-of-Bounds vulnerability report

critical severity

Out-of-bounds Write

  • Vulnerable module: perl
  • Introduced through: perl@5.26.1-5, perl/libperl5.26@5.26.1-5 and others
  • Fixed in: 5.28.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › perl@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/libperl5.26@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-base@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-modules-5.26@5.26.1-5

NVD Description

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

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

Remediation

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

References

Out-of-bounds Write vulnerability report

critical severity

Out-of-bounds Write

  • Vulnerable module: perl
  • Introduced through: perl@5.26.1-5, perl/libperl5.26@5.26.1-5 and others
  • Fixed in: 5.26.1-6

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › perl@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/libperl5.26@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-base@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-modules-5.26@5.26.1-5

NVD Description

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

Heap-based buffer overflow in the pack function in Perl before 5.26.2 allows context-dependent attackers to execute arbitrary code via a large item count.

Remediation

Upgrade Debian:unstable perl to version 5.26.1-6 or higher.

References

Out-of-bounds Write vulnerability report

critical severity

Out-of-bounds Write

  • Vulnerable module: perl
  • Introduced through: perl@5.26.1-5, perl/libperl5.26@5.26.1-5 and others
  • Fixed in: 5.26.1-6

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › perl@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/libperl5.26@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-base@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-modules-5.26@5.26.1-5

NVD Description

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

An issue was discovered in Perl 5.18 through 5.26. A crafted regular expression can cause a heap-based buffer overflow, with control over the bytes written.

Remediation

Upgrade Debian:unstable perl to version 5.26.1-6 or higher.

References

Out-of-bounds Write vulnerability report

critical severity

Integer Overflow or Wraparound

  • Vulnerable module: procps
  • Introduced through: procps@2:3.3.12-4 and procps/libprocps6@2:3.3.12-4
  • Fixed in: 2:3.3.15-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › procps@2:3.3.12-4
  • Introduced through: openjdk@10-ea-jdk › procps/libprocps6@2:3.3.12-4

NVD Description

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

procps-ng before version 3.3.15 is vulnerable to an incorrect integer size in proc/alloc.* leading to truncation/integer overflow issues. This flaw is related to CVE-2018-1124.

Remediation

Upgrade Debian:unstable procps to version 2:3.3.15-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

critical severity

CVE-2025-6965

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1
  • Fixed in: 3.46.1-7

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

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

There exists a vulnerability in SQLite versions before 3.50.2 where the number of aggregate terms could exceed the number of columns available. This could lead to a memory corruption issue. We recommend upgrading to version 3.50.2 or above.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.46.1-7 or higher.

References

CVE-2025-6965 vulnerability report

critical severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

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

An integer overflow can be triggered in SQLite’s concat_ws() function. The resulting, truncated integer is then used to allocate a buffer. When SQLite then writes the resulting string to the buffer, it uses the original, untruncated size and thus a wild Heap Buffer overflow of size ~4GB can be triggered. This can result in arbitrary code execution.

Remediation

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

References

Integer Overflow or Wraparound vulnerability report

critical severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

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

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

Remediation

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

References

Out-of-Bounds vulnerability report

critical severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

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

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

Remediation

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

References

Out-of-bounds Read vulnerability report

critical severity

Use After Free

  • Vulnerable module: systemd
  • Introduced through: systemd@238-4, systemd/libnss-systemd@238-4 and others
  • Fixed in: 240-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libnss-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libpam-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libsystemd0@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libudev1@238-2
  • Introduced through: openjdk@10-ea-jdk › systemd/systemd-sysv@238-4

NVD Description

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

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

Remediation

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

References

Use After Free vulnerability report

critical severity

Out-of-bounds Write

  • Vulnerable module: wget
  • Introduced through: wget@1.19.4-1
  • Fixed in: 1.20.1-1.1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › wget@1.19.4-1

NVD Description

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

Buffer overflow in GNU Wget 1.20.1 and earlier allows remote attackers to cause a denial-of-service (DoS) or may execute an arbitrary code via unspecified vectors.

Remediation

Upgrade Debian:unstable wget to version 1.20.1-1.1 or higher.

References

Out-of-bounds Write vulnerability report

critical severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › zlib/zlib1g@1:1.2.8.dfsg-5

NVD Description

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

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

Remediation

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

References

Integer Overflow or Wraparound vulnerability report

critical severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › zlib/zlib1g@1:1.2.8.dfsg-5

NVD Description

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

zlib through 1.2.12 has a heap-based buffer over-read or buffer overflow in inflate in inflate.c via a large gzip header extra field. NOTE: only applications that call inflateGetHeader are affected. Some common applications bundle the affected zlib source code but may be unable to call inflateGetHeader (e.g., see the nodejs/node reference).

Remediation

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

References

Out-of-bounds Write vulnerability report

critical severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › freetype/libfreetype6@2.8.1-2

NVD Description

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

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

Remediation

Upgrade Debian:unstable freetype to version 2.10.2+dfsg-4 or higher.

References

Out-of-bounds Write vulnerability report

critical severity

CVE-2024-47175

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.7-3
  • Fixed in: 2.4.10-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › cups/libcups2@2.2.7-3

NVD Description

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

CUPS is a standards-based, open-source printing system, and libppd can be used for legacy PPD file support. The libppd function ppdCreatePPDFromIPP2 does not sanitize IPP attributes when creating the PPD buffer. When used in combination with other functions such as cfGetPrinterAttributes5, can result in user controlled input and ultimately code execution via Foomatic. This vulnerability can be part of an exploit chain leading to remote code execution (RCE), as described in CVE-2024-47176.

Remediation

Upgrade Debian:unstable cups to version 2.4.10-2 or higher.

References

CVE-2024-47175 vulnerability report

critical severity

Cleartext Transmission of Sensitive Information

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.88.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

A cleartext transmission of sensitive information vulnerability exists in curl <v7.88.0 that could cause HSTS functionality fail when multiple URLs are requested serially. Using its HSTS support, curl can be instructed to use HTTPS instead of usingan insecure clear-text HTTP step even when HTTP is provided in the URL. ThisHSTS mechanism would however surprisingly be ignored by subsequent transferswhen done on the same command line because the state would not be properlycarried on.

Remediation

Upgrade Debian:unstable curl to version 7.88.1-1 or higher.

References

Cleartext Transmission of Sensitive Information vulnerability report

critical severity

Double Free

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.79.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

When sending data to an MQTT server, libcurl <= 7.73.0 and 7.78.0 could in some circumstances erroneously keep a pointer to an already freed memory area and both use that again in a subsequent call to send data and also free it again.

Remediation

Upgrade Debian:unstable curl to version 7.79.1-1 or higher.

References

Double Free vulnerability report

critical severity

Out-of-bounds Read

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.60.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

curl version curl 7.20.0 to and including curl 7.59.0 contains a CWE-126: Buffer Over-read vulnerability in denial of service that can result in curl can be tricked into reading data beyond the end of a heap based buffer used to store downloaded RTSP content.. This vulnerability appears to have been fixed in curl < 7.20.0 and curl >= 7.60.0.

Remediation

Upgrade Debian:unstable curl to version 7.60.0-1 or higher.

References

Out-of-bounds Read vulnerability report

critical severity

Out-of-bounds Read

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.62.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

Curl versions 7.14.1 through 7.61.1 are vulnerable to a heap-based buffer over-read in the tool_msgs.c:voutf() function that may result in information exposure and denial of service.

Remediation

Upgrade Debian:unstable curl to version 7.62.0-1 or higher.

References

Out-of-bounds Read vulnerability report

critical severity

Out-of-bounds Read

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.60.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

A buffer over-read exists in curl 7.20.0 to and including curl 7.58.0 in the RTSP+RTP handling code that allows an attacker to cause a denial of service or information leakage

Remediation

Upgrade Debian:unstable curl to version 7.60.0-1 or higher.

References

Out-of-bounds Read vulnerability report

critical severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

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

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

Remediation

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

References

Integer Overflow or Wraparound vulnerability report

critical severity

CVE-2024-37371

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › krb5/libgssapi-krb5-2@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libk5crypto3@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libkrb5-3@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libkrb5support0@1.16-2

NVD Description

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

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

Remediation

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

References

CVE-2024-37371 vulnerability report

critical severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libbsd/libbsd0@0.8.7-1

NVD Description

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

nlist.c in libbsd before 0.10.0 has an out-of-bounds read during a comparison for a symbol name from the string table (strtab).

Remediation

Upgrade Debian:unstable libbsd to version 0.10.0-1 or higher.

References

Out-of-bounds Read vulnerability report

critical severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libssh2/libssh2-1@1.8.0-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:unstable relevant fixed versions and status.

An out of bounds read flaw was discovered in libssh2 before 1.8.1 when a specially crafted SFTP packet is received from the server. A remote attacker who compromises a SSH server may be able to cause a Denial of Service or read data in the client memory.

Remediation

Upgrade Debian:unstable libssh2 to version 1.8.0-2.1 or higher.

References

Out-of-bounds Read vulnerability report

critical severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libssh2/libssh2-1@1.8.0-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:unstable relevant fixed versions and status.

An out of bounds read flaw was discovered in libssh2 before 1.8.1 in the _libssh2_packet_require and _libssh2_packet_requirev functions. A remote attacker who compromises a SSH server may be able to cause a Denial of Service or read data in the client memory.

Remediation

Upgrade Debian:unstable libssh2 to version 1.8.0-2.1 or higher.

References

Out-of-bounds Read vulnerability report

critical severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libssh2/libssh2-1@1.8.0-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:unstable relevant fixed versions and status.

An out of bounds read flaw was discovered in libssh2 before 1.8.1 in the way SSH packets with a padding length value greater than the packet length are parsed. A remote attacker who compromises a SSH server may be able to cause a Denial of Service or read data in the client memory.

Remediation

Upgrade Debian:unstable libssh2 to version 1.8.0-2.1 or higher.

References

Out-of-bounds Read vulnerability report

critical severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libssh2/libssh2-1@1.8.0-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:unstable relevant fixed versions and status.

An out of bounds read flaw was discovered in libssh2 before 1.8.1 in the way SFTP packets with empty payloads are parsed. A remote attacker who compromises a SSH server may be able to cause a Denial of Service or read data in the client memory.

Remediation

Upgrade Debian:unstable libssh2 to version 1.8.0-2.1 or higher.

References

Out-of-bounds Read vulnerability report

critical severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libssh2/libssh2-1@1.8.0-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:unstable relevant fixed versions and status.

An out of bounds read flaw was discovered in libssh2 before 1.8.1 in the way SSH_MSG_CHANNEL_REQUEST packets with an exit status message and no payload are parsed. A remote attacker who compromises a SSH server may be able to cause a Denial of Service or read data in the client memory.

Remediation

Upgrade Debian:unstable libssh2 to version 1.8.0-2.1 or higher.

References

Out-of-bounds Read vulnerability report

critical severity

Off-by-one Error

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libtasn1-6@4.13-2

NVD Description

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

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

Remediation

Upgrade Debian:unstable libtasn1-6 to version 4.19.0-2 or higher.

References

Off-by-one Error vulnerability report

critical severity

Expired Pointer Dereference

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.12.7+dfsg+really2.9.14-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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

A use-after-free vulnerability was found in libxml2. This issue occurs when parsing XPath elements under certain circumstances when the XML schematron has the <sch:name path="..."/> schema elements. This flaw allows a malicious actor to craft a malicious XML document used as input for libxml, resulting in the program's crash using libxml or other possible undefined behaviors.

Remediation

Upgrade Debian:unstable libxml2 to version 2.12.7+dfsg+really2.9.14-2 or higher.

References

Expired Pointer Dereference vulnerability report

critical severity

Out-of-bounds Read

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.12.7+dfsg+really2.9.14-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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

A vulnerability was found in libxml2. Processing certain sch:name elements from the input XML file can trigger a memory corruption issue. This flaw allows an attacker to craft a malicious XML input file that can lead libxml to crash, resulting in a denial of service or other possible undefined behavior due to sensitive data being corrupted in memory.

Remediation

Upgrade Debian:unstable libxml2 to version 2.12.7+dfsg+really2.9.14-2 or higher.

References

Out-of-bounds Read vulnerability report

critical severity

Incorrect Permission Assignment for Critical Resource

  • Vulnerable module: mercurial
  • Introduced through: mercurial@4.5-1 and mercurial/mercurial-common@4.5-1
  • Fixed in: 4.5.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › mercurial@4.5-1
  • Introduced through: openjdk@10-ea-jdk › mercurial/mercurial-common@4.5-1

NVD Description

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

Mercurial version 4.5 and earlier contains a Incorrect Access Control (CWE-285) vulnerability in Protocol server that can result in Unauthorized data access. This attack appear to be exploitable via network connectivity. This vulnerability appears to have been fixed in 4.5.1.

Remediation

Upgrade Debian:unstable mercurial to version 4.5.2-1 or higher.

References

Incorrect Permission Assignment for Critical Resource vulnerability report

critical severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nss/libnss3@2:3.36.1-1

NVD Description

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

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

Remediation

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

References

Out-of-bounds Read vulnerability report

critical severity

Out-of-bounds Read

  • Vulnerable module: pcre2/libpcre2-8-0
  • Introduced through: pcre2/libpcre2-8-0@10.31-3
  • Fixed in: 10.40-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › pcre2/libpcre2-8-0@10.31-3

NVD Description

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

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

Remediation

Upgrade Debian:unstable pcre2 to version 10.40-1 or higher.

References

Out-of-bounds Read vulnerability report

critical severity

Out-of-bounds Read

  • Vulnerable module: pcre2/libpcre2-8-0
  • Introduced through: pcre2/libpcre2-8-0@10.31-3
  • Fixed in: 10.40-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › pcre2/libpcre2-8-0@10.31-3

NVD Description

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

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

Remediation

Upgrade Debian:unstable pcre2 to version 10.40-1 or higher.

References

Out-of-bounds Read vulnerability report

critical severity

Out-of-bounds Write

  • Vulnerable module: pcre2/libpcre2-8-0
  • Introduced through: pcre2/libpcre2-8-0@10.31-3
  • Fixed in: 10.46-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › pcre2/libpcre2-8-0@10.31-3

NVD Description

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

The PCRE2 library is a set of C functions that implement regular expression pattern matching. In version 10.45, a heap-buffer-overflow read vulnerability exists in the PCRE2 regular expression matching engine, specifically within the handling of the (*scs:...) (Scan SubString) verb when combined with (*ACCEPT) in src/pcre2_match.c. This vulnerability may potentially lead to information disclosure if the out-of-bounds data read during the memcmp affects the final match result in a way observable by the attacker. This issue has been resolved in version 10.46.

Remediation

Upgrade Debian:unstable pcre2 to version 10.46-1 or higher.

References

Out-of-bounds Write vulnerability report

critical severity

Out-of-bounds Read

  • Vulnerable module: perl
  • Introduced through: perl@5.26.1-5, perl/libperl5.26@5.26.1-5 and others
  • Fixed in: 5.28.0-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › perl@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/libperl5.26@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-base@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-modules-5.26@5.26.1-5

NVD Description

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

Perl before 5.26.3 has a buffer over-read via a crafted regular expression that triggers disclosure of sensitive information from process memory.

Remediation

Upgrade Debian:unstable perl to version 5.28.0-3 or higher.

References

Out-of-bounds Read vulnerability report

critical severity

CVE-2025-7458

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1
  • Fixed in: 3.42.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

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

An integer overflow in the sqlite3KeyInfoFromExprList function in SQLite versions 3.39.2 through 3.41.1 allows an attacker with the ability to execute arbitrary SQL statements to cause a denial of service or disclose sensitive information from process memory via a crafted SELECT statement with a large number of expressions in the ORDER BY clause.

Remediation

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

References

CVE-2025-7458 vulnerability report

critical severity

Interpretation Conflict

  • Vulnerable module: wget
  • Introduced through: wget@1.19.4-1
  • Fixed in: 1.24.5-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › wget@1.19.4-1

NVD Description

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

url.c in GNU Wget through 1.24.5 mishandles semicolons in the userinfo subcomponent of a URI, and thus there may be insecure behavior in which data that was supposed to be in the userinfo subcomponent is misinterpreted to be part of the host subcomponent.

Remediation

Upgrade Debian:unstable wget to version 1.24.5-2 or higher.

References

Interpretation Conflict vulnerability report

critical severity

Link Following

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.45.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

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

Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, repositories with submodules can be crafted in a way that exploits a bug in Git whereby it can be fooled into writing files not into the submodule's worktree but into a .git/ directory. This allows writing a hook that will be executed while the clone operation is still running, giving the user no opportunity to inspect the code that is being executed. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4. If symbolic link support is disabled in Git (e.g. via git config --global core.symlinks false), the described attack won't work. As always, it is best to avoid cloning repositories from untrusted sources.

Remediation

Upgrade Debian:unstable git to version 1:2.45.1-1 or higher.

References

Link Following vulnerability report

high severity

Buffer Overflow

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.7-3
  • Fixed in: 2.2.12-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › cups/libcups2@2.2.7-3

NVD Description

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

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

Remediation

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

References

Buffer Overflow vulnerability report

high severity

Buffer Overflow

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.7-3
  • Fixed in: 2.2.12-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › cups/libcups2@2.2.7-3

NVD Description

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

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

Remediation

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

References

Buffer Overflow vulnerability report

high severity

CVE-2018-6553

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › cups/libcups2@2.2.7-3

NVD Description

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

The CUPS AppArmor profile incorrectly confined the dnssd backend due to use of hard links. A local attacker could possibly use this issue to escape confinement. This flaw affects versions prior to 2.2.7-1ubuntu2.1 in Ubuntu 18.04 LTS, prior to 2.2.4-7ubuntu3.1 in Ubuntu 17.10, prior to 2.1.3-4ubuntu0.5 in Ubuntu 16.04 LTS, and prior to 1.7.2-0ubuntu1.10 in Ubuntu 14.04 LTS.

Remediation

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

References

CVE-2018-6553 vulnerability report

high severity

Arbitrary Code Injection

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.88.1-7

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable 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:unstable curl to version 7.88.1-7 or higher.

References

Arbitrary Code Injection vulnerability report

high severity

Directory Traversal

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.88.1-7

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable 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:unstable curl to version 7.88.1-7 or higher.

References

Directory Traversal vulnerability report

high severity

SQL Injection

  • Vulnerable module: cyrus-sasl2/libsasl2-2
  • Introduced through: cyrus-sasl2/libsasl2-2@2.1.27~101-g0780600+dfsg-3 and cyrus-sasl2/libsasl2-modules-db@2.1.27~101-g0780600+dfsg-3
  • Fixed in: 2.1.28+dfsg-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › cyrus-sasl2/libsasl2-2@2.1.27~101-g0780600+dfsg-3
  • Introduced through: openjdk@10-ea-jdk › cyrus-sasl2/libsasl2-modules-db@2.1.27~101-g0780600+dfsg-3

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:unstable 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:unstable cyrus-sasl2 to version 2.1.28+dfsg-2 or higher.

References

SQL Injection vulnerability report

high severity

Incorrect Calculation

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › expat/libexpat1@2.2.5-3

NVD Description

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

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

Remediation

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

References

Incorrect Calculation vulnerability report

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › expat/libexpat1@2.2.5-3

NVD Description

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

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

Remediation

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

References

Integer Overflow or Wraparound vulnerability report

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › expat/libexpat1@2.2.5-3

NVD Description

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

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

Remediation

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

References

Integer Overflow or Wraparound vulnerability report

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › expat/libexpat1@2.2.5-3

NVD Description

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

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

Remediation

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

References

Integer Overflow or Wraparound vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: gdk-pixbuf/libgdk-pixbuf2.0-0
  • Introduced through: gdk-pixbuf/libgdk-pixbuf2.0-0@2.36.11-2, gdk-pixbuf/libgdk-pixbuf2.0-bin@2.36.11-2 and others
  • Fixed in: 2.42.2+dfsg-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gdk-pixbuf/libgdk-pixbuf2.0-0@2.36.11-2
  • Introduced through: openjdk@10-ea-jdk › gdk-pixbuf/libgdk-pixbuf2.0-bin@2.36.11-2
  • Introduced through: openjdk@10-ea-jdk › gdk-pixbuf/libgdk-pixbuf2.0-common@2.36.11-2

NVD Description

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

A flaw was found in gdk-pixbuf in versions before 2.42.0. An integer wraparound leading to an out of bounds write can occur when a crafted GIF image is loaded. An attacker may cause applications to crash or could potentially execute code on the victim system. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.

Remediation

Upgrade Debian:unstable gdk-pixbuf to version 2.42.2+dfsg-1 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: gdk-pixbuf/libgdk-pixbuf2.0-0
  • Introduced through: gdk-pixbuf/libgdk-pixbuf2.0-0@2.36.11-2, gdk-pixbuf/libgdk-pixbuf2.0-bin@2.36.11-2 and others
  • Fixed in: 2.42.9+dfsg-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gdk-pixbuf/libgdk-pixbuf2.0-0@2.36.11-2
  • Introduced through: openjdk@10-ea-jdk › gdk-pixbuf/libgdk-pixbuf2.0-bin@2.36.11-2
  • Introduced through: openjdk@10-ea-jdk › gdk-pixbuf/libgdk-pixbuf2.0-common@2.36.11-2

NVD Description

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

GNOME gdk-pixbuf 2.42.6 is vulnerable to a heap-buffer overflow vulnerability when decoding the lzw compressed stream of image data in GIF files with lzw minimum code size equals to 12.

Remediation

Upgrade Debian:unstable gdk-pixbuf to version 2.42.9+dfsg-1 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: giflib/libgif7
  • Introduced through: giflib/libgif7@5.1.4-2
  • Fixed in: 5.1.9-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › giflib/libgif7@5.1.4-2

NVD Description

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

The DGifDecompressLine function in dgif_lib.c in GIFLIB (possibly version 3.0.x), as later shipped in cgif.c in sam2p 0.49.4, has a heap-based buffer overflow because a certain "Private->RunningCode - 2" array index is not checked. This will lead to a denial of service or possibly unspecified other impact.

Remediation

Upgrade Debian:unstable giflib to version 5.1.9-1 or higher.

References

Out-of-bounds Write vulnerability report

high severity

CVE-2019-1387

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.24.0-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

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

An issue was found in Git before v2.24.1, v2.23.1, v2.22.2, v2.21.1, v2.20.2, v2.19.3, v2.18.2, v2.17.3, v2.16.6, v2.15.4, and v2.14.6. Recursive clones are currently affected by a vulnerability that is caused by too-lax validation of submodule names, allowing very targeted attacks via remote code execution in recursive clones.

Remediation

Upgrade Debian:unstable git to version 1:2.24.0-2 or higher.

References

CVE-2019-1387 vulnerability report

high severity

Heap-based Buffer Overflow

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.38.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

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

Git is an open source, scalable, distributed revision control system. git shell is a restricted login shell that can be used to implement Git's push/pull functionality via SSH. In versions prior to 2.30.6, 2.31.5, 2.32.4, 2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4, the function that splits the command arguments into an array improperly uses an int to represent the number of entries in the array, allowing a malicious actor to intentionally overflow the return value, leading to arbitrary heap writes. Because the resulting array is then passed to execv(), it is possible to leverage this attack to gain remote code execution on a victim machine. Note that a victim must first allow access to git shell as a login shell in order to be vulnerable to this attack. This problem is patched in versions 2.30.6, 2.31.5, 2.32.4, 2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4 and users are advised to upgrade to the latest version. Disabling git shell access via remote logins is a viable short-term workaround.

Remediation

Upgrade Debian:unstable git to version 1:2.38.1-1 or higher.

References

Heap-based Buffer Overflow vulnerability report

high severity

Improper Input Validation

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.24.0-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

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

A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-1349, CVE-2019-1350, CVE-2019-1354, CVE-2019-1387.

Remediation

Upgrade Debian:unstable git to version 1:2.24.0-2 or higher.

References

Improper Input Validation vulnerability report

high severity

Improper Input Validation

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.24.0-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

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

A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-1350, CVE-2019-1352, CVE-2019-1354, CVE-2019-1387.

Remediation

Upgrade Debian:unstable git to version 1:2.24.0-2 or higher.

References

Improper Input Validation vulnerability report

high severity

Use After Free

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.56.1-2 and glib2.0/libglib2.0-data@2.56.1-2
  • Fixed in: 2.66.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-0@2.56.1-2
  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-data@2.56.1-2

NVD Description

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

A vulnerability was found in GNOME gvdb. It has been classified as critical. This affects the function gvdb_table_write_contents_async of the file gvdb-builder.c. The manipulation leads to use after free. It is possible to initiate the attack remotely. The name of the patch is d83587b2a364eb9a9a53be7e6a708074e252de14. It is recommended to apply a patch to fix this issue. The identifier VDB-216789 was assigned to this vulnerability.

Remediation

Upgrade Debian:unstable glib2.0 to version 2.66.0-1 or higher.

References

Use After Free vulnerability report

high severity

Cross-site Request Forgery (CSRF)

  • Vulnerable module: gnupg2/dirmngr
  • Introduced through: gnupg2/dirmngr@2.2.5-1, gnupg2/gnupg@2.2.5-1 and others
  • Fixed in: 2.2.12-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gnupg2/dirmngr@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gnupg@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gnupg-l10n@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gnupg-utils@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpg@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpg-agent@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpg-wks-client@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpg-wks-server@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpgconf@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpgsm@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpgv@2.2.5-1

NVD Description

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

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

Remediation

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

References

Cross-site Request Forgery (CSRF) vulnerability report

high severity

Improper Input Validation

  • Vulnerable module: gzip/gzip
  • Introduced through: gzip/gzip@1.6-5+b1
  • Fixed in: 1.12-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gzip/gzip@1.6-5+b1

NVD Description

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

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

Remediation

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

References

Improper Input Validation vulnerability report

high severity

Double Free

  • Vulnerable module: icu/libicu57
  • Introduced through: icu/libicu57@57.1-9
  • Fixed in: 67.1-7

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › icu/libicu57@57.1-9

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

Double free in ICU in Google Chrome prior to 91.0.4472.77 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Remediation

Upgrade Debian:unstable icu to version 67.1-7 or higher.

References

Double Free vulnerability report

high severity

Integer Overflow or Wraparound

  • Vulnerable module: icu/libicu57
  • Introduced through: icu/libicu57@57.1-9
  • Fixed in: 63.2-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › icu/libicu57@57.1-9

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

An issue was discovered in International Components for Unicode (ICU) for C/C++ through 66.1. An integer overflow, leading to a heap-based buffer overflow, exists in the UnicodeString::doAppend() function in common/unistr.cpp.

Remediation

Upgrade Debian:unstable icu to version 63.2-3 or higher.

References

Integer Overflow or Wraparound vulnerability report

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › krb5/libgssapi-krb5-2@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libk5crypto3@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libkrb5-3@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libkrb5support0@1.16-2

NVD Description

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

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

Remediation

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

References

Integer Overflow or Wraparound vulnerability report

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libssh2/libssh2-1@1.8.0-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:unstable relevant fixed versions and status.

An integer overflow flaw, which could lead to an out of bounds write, was discovered in libssh2 before 1.8.1 in the way keyboard prompt requests are parsed. A remote attacker who compromises a SSH server may be able to execute code on the client system when a user connects to the server.

Remediation

Upgrade Debian:unstable libssh2 to version 1.8.0-2.1 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libssh2/libssh2-1@1.8.0-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:unstable relevant fixed versions and status.

An integer overflow flaw which could lead to an out of bounds write was discovered in libssh2 before 1.8.1 in the way SSH_MSG_CHANNEL_REQUEST packets with an exit signal are parsed. A remote attacker who compromises a SSH server may be able to execute code on the client system when a user connects to the server.

Remediation

Upgrade Debian:unstable libssh2 to version 1.8.0-2.1 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libssh2/libssh2-1@1.8.0-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:unstable relevant fixed versions and status.

A flaw was found in libssh2 before 1.8.1 creating a vulnerability on the SSH client side. A server could send a multiple keyboard interactive response messages whose total length are greater than unsigned char max characters. This value is used by the SSH client as an index to copy memory causing in an out of bounds memory write error.

Remediation

Upgrade Debian:unstable libssh2 to version 1.8.0-2.1 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libssh2/libssh2-1@1.8.0-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:unstable relevant fixed versions and status.

An integer overflow flaw which could lead to an out of bounds write was discovered in libssh2 before 1.8.1 in the way packets are read from the server. A remote attacker who compromises a SSH server may be able to execute code on the client system when a user connects to the server.

Remediation

Upgrade Debian:unstable libssh2 to version 1.8.0-2.1 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Use After Free

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.9.10+dfsg-6.6

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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:unstable 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:unstable libxml2 to version 2.9.10+dfsg-6.6 or higher.

References

Use After Free vulnerability report

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.1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › 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:unstable 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:unstable libxpm to version 1:3.5.12-1.1 or higher.

References

Untrusted Search Path vulnerability report

high severity

CVE-2023-0767

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nss/libnss3@2:3.36.1-1

NVD Description

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

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

Remediation

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

References

CVE-2023-0767 vulnerability report

high severity

CVE-2024-6609

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nss/libnss3@2:3.36.1-1

NVD Description

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

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

Remediation

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

References

CVE-2024-6609 vulnerability report

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nss/libnss3@2:3.36.1-1

NVD Description

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

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

Remediation

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

References

Out-of-bounds Write vulnerability report

high severity

Integer Overflow or Wraparound

  • Vulnerable module: pixman/libpixman-1-0
  • Introduced through: pixman/libpixman-1-0@0.34.0-2
  • Fixed in: 0.40.0-1.1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › pixman/libpixman-1-0@0.34.0-2

NVD Description

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

In libpixman in Pixman before 0.42.2, there is an out-of-bounds write (aka heap-based buffer overflow) in rasterize_edges_8 due to an integer overflow in pixman_sample_floor_y.

Remediation

Upgrade Debian:unstable pixman to version 0.40.0-1.1 or higher.

References

Integer Overflow or Wraparound vulnerability report

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

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

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

Remediation

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

References

Out-of-bounds Write vulnerability report

high severity

Out-of-Bounds

  • Vulnerable module: systemd
  • Introduced through: systemd@238-4, systemd/libnss-systemd@238-4 and others
  • Fixed in: 239-11

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libnss-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libpam-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libsystemd0@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libudev1@238-2
  • Introduced through: openjdk@10-ea-jdk › systemd/systemd-sysv@238-4

NVD Description

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

A buffer overflow vulnerability in the dhcp6 client of systemd allows a malicious dhcp6 server to overwrite heap memory in systemd-networkd. Affected releases are systemd: versions up to and including 239.

Remediation

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

References

Out-of-Bounds vulnerability report

high severity

Buffer Overflow

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.5.0-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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

References

Buffer Overflow vulnerability report

high severity

Numeric Errors

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.4.0-6

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.4.0-6 or higher.

References

Numeric Errors vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.0.10-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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

Heap-based buffer overflow in the cpSeparateBufToContigBuf function in tiffcp.c in LibTIFF 3.9.3, 3.9.4, 3.9.5, 3.9.6, 3.9.7, 4.0.0beta7, 4.0.0alpha4, 4.0.0alpha5, 4.0.0alpha6, 4.0.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.4beta, 4.0.5, 4.0.6, 4.0.7, 4.0.8 and 4.0.9 allows remote attackers to cause a denial of service (crash) or possibly have unspecified other impact via a crafted TIFF file.

Remediation

Upgrade Debian:unstable tiff to version 4.0.10-4 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.0.9-6

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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

In LibTIFF 4.0.9, a heap-based buffer overflow occurs in the function LZWDecodeCompat in tif_lzw.c via a crafted TIFF file, as demonstrated by tiff2ps.

Remediation

Upgrade Debian:unstable tiff to version 4.0.9-6 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.0.9+git181026-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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

LibTIFF 3.9.3, 3.9.4, 3.9.5, 3.9.6, 3.9.7, 4.0.0alpha4, 4.0.0alpha5, 4.0.0alpha6, 4.0.0beta7, 4.0.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.4beta, 4.0.5, 4.0.6, 4.0.7, 4.0.8 and 4.0.9 (with JBIG enabled) decodes arbitrarily-sized JBIG into a buffer, ignoring the buffer size, which leads to a tif_jbig.c JBIGDecode out-of-bounds write.

Remediation

Upgrade Debian:unstable tiff to version 4.0.9+git181026-1 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.0.9+git181026-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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

An issue was discovered in LibTIFF 4.0.9. There are two out-of-bounds writes in cpTags in tools/tiff2bw.c and tools/pal2rgb.c, which can cause a denial of service (application crash) or possibly have unspecified other impact via a crafted image file.

Remediation

Upgrade Debian:unstable tiff to version 4.0.9+git181026-1 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.0.10+git190818-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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

tif_getimage.c in LibTIFF through 4.0.10, as used in GDAL through 3.0.1 and other products, has an integer overflow that potentially causes a heap-based buffer overflow via a crafted RGBA image, related to a "Negative-size-param" condition.

Remediation

Upgrade Debian:unstable tiff to version 4.0.10+git190818-1 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Write-what-where Condition

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.7.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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

A flaw was found in Libtiff. This vulnerability is a "write-what-where" condition, triggered when the library processes a specially crafted TIFF image file.

By providing an abnormally large image height value in the file's metadata, an attacker can trick the library into writing attacker-controlled color data to an arbitrary memory location. This memory corruption can be exploited to cause a denial of service (application crash) or to achieve arbitrary code execution with the permissions of the user.

Remediation

Upgrade Debian:unstable tiff to version 4.7.1-1 or higher.

References

Write-what-where Condition vulnerability report

high severity

Improper Input Validation

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › xz-utils@5.2.2-1.3
  • Introduced through: openjdk@10-ea-jdk › xz-utils/liblzma5@5.2.2-1.3

NVD Description

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

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

Remediation

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

References

Improper Input Validation vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.9.10+dfsg-6.6

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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:unstable 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:unstable libxml2 to version 2.9.10+dfsg-6.6 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Integer Overflow or Wraparound

  • Vulnerable module: perl
  • Introduced through: perl@5.26.1-5, perl/libperl5.26@5.26.1-5 and others
  • Fixed in: 5.30.3-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › perl@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/libperl5.26@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-base@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-modules-5.26@5.26.1-5

NVD Description

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

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

Remediation

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

References

Integer Overflow or Wraparound vulnerability report

high severity

Double Free

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.18-1
  • Fixed in: 3.8.9-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gnutls28/libgnutls30@3.5.18-1

NVD Description

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

A flaw was found in GnuTLS. A double-free vulnerability exists in GnuTLS due to incorrect ownership handling in the export logic of Subject Alternative Name (SAN) entries containing an otherName. If the type-id OID is invalid or malformed, GnuTLS will call asn1_delete_structure() on an ASN.1 node it does not own, leading to a double-free condition when the parent function or caller later attempts to free the same structure.

This vulnerability can be triggered using only public GnuTLS APIs and may result in denial of service or memory corruption, depending on allocator behavior.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.8.9-3 or higher.

References

Double Free vulnerability report

high severity

Heap-based Buffer Overflow

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.18-1
  • Fixed in: 3.8.9-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gnutls28/libgnutls30@3.5.18-1

NVD Description

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

A heap-buffer-overflow (off-by-one) flaw was found in the GnuTLS software in the template parsing logic within the certtool utility. When it reads certain settings from a template file, it allows an attacker to cause an out-of-bounds (OOB) NULL pointer write, resulting in memory corruption and a denial-of-service (DoS) that could potentially crash the system.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.8.9-3 or higher.

References

Heap-based Buffer Overflow vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: perl
  • Introduced through: perl@5.26.1-5, perl/libperl5.26@5.26.1-5 and others
  • Fixed in: 5.30.3-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › perl@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/libperl5.26@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-base@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-modules-5.26@5.26.1-5

NVD Description

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

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

Remediation

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

References

Out-of-bounds Write vulnerability report

high severity

CVE-2019-3462

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › apt@1.6~beta1
  • Introduced through: openjdk@10-ea-jdk › apt/libapt-pkg5.0@1.6~beta1

NVD Description

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

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

Remediation

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

References

CVE-2019-3462 vulnerability report

high severity

Double Free

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.86.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

curl before 7.86.0 has a double free. If curl is told to use an HTTP proxy for a transfer with a non-HTTP(S) URL, it sets up the connection to the remote server by issuing a CONNECT request to the proxy, and then tunnels the rest of the protocol through. An HTTP proxy might refuse this request (HTTP proxies often only allow outgoing connections to specific port numbers, like 443 for HTTPS) and instead return a non-200 status code to the client. Due to flaws in the error/cleanup handling, this could trigger a double free in curl if one of the following schemes were used in the URL for the transfer: dict, gopher, gophers, ldap, ldaps, rtmp, rtmps, or telnet. The earliest affected version is 7.77.0.

Remediation

Upgrade Debian:unstable curl to version 7.86.0-1 or higher.

References

Double Free vulnerability report

high severity

Missing Authentication for Critical Function

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.83.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

References

Missing Authentication for Critical Function vulnerability report

high severity

Use of Incorrectly-Resolved Name or Reference

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.83.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

A use of incorrectly resolved name vulnerability fixed in 7.83.1 might remove the wrong file when --no-clobber is used together with --remove-on-error.

Remediation

Upgrade Debian:unstable curl to version 7.83.1-1 or higher.

References

Use of Incorrectly-Resolved Name or Reference vulnerability report

high severity

Use After Free

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.5-3
  • Fixed in: 2.4.8-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › expat/libexpat1@2.2.5-3

NVD Description

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

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

Remediation

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

References

Use After Free vulnerability report

high severity

CVE-2025-27363

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › freetype/libfreetype6@2.8.1-2

NVD Description

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

An out of bounds write exists in FreeType versions 2.13.0 and below (newer versions of FreeType are not vulnerable) when attempting to parse font subglyph structures related to TrueType GX and variable font files. The vulnerable code assigns a signed short value to an unsigned long and then adds a static value causing it to wrap around and allocate too small of a heap buffer. The code then writes up to 6 signed long integers out of bounds relative to this buffer. This may result in arbitrary code execution. This vulnerability may have been exploited in the wild.

Remediation

Upgrade Debian:unstable freetype to version 2.13.1+dfsg-1 or higher.

References

CVE-2025-27363 vulnerability report

high severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+b1

NVD Description

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

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

Remediation

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

References

Out-of-bounds Read vulnerability report

high severity

Out-of-bounds Read

  • Vulnerable module: libssh2/libssh2-1
  • Introduced through: libssh2/libssh2-1@1.8.0-1
  • Fixed in: 1.9.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libssh2/libssh2-1@1.8.0-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:unstable 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:unstable libssh2 to version 1.9.0-1 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Use of a Broken or Risky Cryptographic Algorithm

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nettle/libhogweed4@3.4-1
  • Introduced through: openjdk@10-ea-jdk › nettle/libnettle6@3.4-1

NVD Description

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

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

Remediation

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

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

high severity

Race Condition

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:7.6p1-4
  • Fixed in: 1:9.7p1-7

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssh/openssh-client@1:7.6p1-4

NVD Description

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

A security regression (CVE-2006-5051) was discovered in OpenSSH's server (sshd). There is a race condition which can lead sshd to handle some signals in an unsafe manner. An unauthenticated, remote attacker may be able to trigger it by failing to authenticate within a set time period.

Remediation

Upgrade Debian:unstable openssh to version 1:9.7p1-7 or higher.

References

Race Condition vulnerability report

high severity

Improper Certificate Validation

  • Vulnerable module: perl
  • Introduced through: perl@5.26.1-5, perl/libperl5.26@5.26.1-5 and others
  • Fixed in: 5.38.2-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › perl@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/libperl5.26@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-base@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-modules-5.26@5.26.1-5

NVD Description

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

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

Remediation

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

References

Improper Certificate Validation vulnerability report

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

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

SQLite before 3.25.3, when the FTS3 extension is enabled, encounters an integer overflow (and resultant buffer overflow) for FTS3 queries that occur after crafted changes to FTS3 shadow tables, allowing remote attackers to execute arbitrary code by leveraging the ability to run arbitrary SQL statements (such as in certain WebSQL use cases), aka Magellan.

Remediation

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

References

Integer Overflow or Wraparound vulnerability report

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

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

SQLite before 3.25.3, when the FTS3 extension is enabled, encounters an integer overflow (and resultant buffer overflow) for FTS3 queries in a "merge" operation that occurs after crafted changes to FTS3 shadow tables, allowing remote attackers to execute arbitrary code by leveraging the ability to run arbitrary SQL statements (such as in certain WebSQL use cases). This is a different vulnerability than CVE-2018-20346.

Remediation

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

References

Integer Overflow or Wraparound vulnerability report

high severity

Use After Free

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

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

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

Remediation

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

References

Use After Free vulnerability report

high severity

Link Following

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-client3@0.7-3.1
  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-common-data@0.7-3.1
  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-common3@0.7-3.1

NVD Description

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

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

Remediation

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

References

Link Following vulnerability report

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › bash@4.4.18-1.1

NVD Description

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

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

Remediation

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

References

Out-of-bounds Write vulnerability report

high severity

Stack-based Buffer Overflow

  • Vulnerable module: cairo/libcairo-gobject2
  • Introduced through: cairo/libcairo-gobject2@1.15.10-3 and cairo/libcairo2@1.15.10-3
  • Fixed in: 1.16.0-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › cairo/libcairo-gobject2@1.15.10-3
  • Introduced through: openjdk@10-ea-jdk › cairo/libcairo2@1.15.10-3

NVD Description

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

A flaw was found in cairo's image-compositor.c in all versions prior to 1.17.4. This flaw allows an attacker who can provide a crafted input file to cairo's image-compositor (for example, by convincing a user to open a file in an application using cairo, or if an application uses cairo on untrusted input) to cause a stack buffer overflow -> out-of-bounds WRITE. The highest impact from this vulnerability is to confidentiality, integrity, as well as system availability.

Remediation

Upgrade Debian:unstable cairo to version 1.16.0-5 or higher.

References

Stack-based Buffer Overflow vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: cryptsetup/libcryptsetup12
  • Introduced through: cryptsetup/libcryptsetup12@2:2.0.2-1
  • Fixed in: 2:2.3.4-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › cryptsetup/libcryptsetup12@2:2.0.2-1

NVD Description

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

A vulnerability was found in upstream release cryptsetup-2.2.0 where, there's a bug in LUKS2 format validation code, that is effectively invoked on every device/image presenting itself as LUKS2 container. The bug is in segments validation code in file 'lib/luks2/luks2_json_metadata.c' in function hdr_validate_segments(struct crypt_device *cd, json_object *hdr_jobj) where the code does not check for possible overflow on memory allocation used for intervals array (see statement "intervals = malloc(first_backup * sizeof(*intervals));"). Due to the bug, library can be tricked to expect such allocation was successful but for far less memory then originally expected. Later it may read data FROM image crafted by an attacker and actually write such data BEYOND allocated memory.

Remediation

Upgrade Debian:unstable cryptsetup to version 2:2.3.4-1 or higher.

References

Out-of-bounds Write vulnerability report

high severity

CVE-2018-4180

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.7-3
  • Fixed in: 2.2.8-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › cups/libcups2@2.2.7-3

NVD Description

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

In macOS High Sierra before 10.13.5, an issue existed in CUPS. This issue was addressed with improved access restrictions.

Remediation

Upgrade Debian:unstable cups to version 2.2.8-2 or higher.

References

CVE-2018-4180 vulnerability report

high severity

Out-of-Bounds

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.7-3
  • Fixed in: 2.3.1-12

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › cups/libcups2@2.2.7-3

NVD Description

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

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

Remediation

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

References

Out-of-Bounds vulnerability report

high severity

Arbitrary Code Injection

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.72.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

curl 7.20.0 through 7.70.0 is vulnerable to improper restriction of names for files and other resources that can lead too overwriting a local file when the -J flag is used.

Remediation

Upgrade Debian:unstable curl to version 7.72.0-1 or higher.

References

Arbitrary Code Injection vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.64.0-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

A heap buffer overflow in the TFTP receiving code allows for DoS or arbitrary code execution in libcurl versions 7.19.4 through 7.64.1.

Remediation

Upgrade Debian:unstable curl to version 7.64.0-4 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Use After Free

  • Vulnerable module: dbus
  • Introduced through: dbus@1.12.6-2, dbus/dbus-user-session@1.12.6-2 and others
  • Fixed in: 1.12.20-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › dbus@1.12.6-2
  • Introduced through: openjdk@10-ea-jdk › dbus/dbus-user-session@1.12.6-2
  • Introduced through: openjdk@10-ea-jdk › dbus/libdbus-1-3@1.12.6-2

NVD Description

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

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

Remediation

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

References

Use After Free vulnerability report

high severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › e2fsprogs@1.44.0-1
  • Introduced through: openjdk@10-ea-jdk › e2fsprogs/libcom-err2@1.44.0-1
  • Introduced through: openjdk@10-ea-jdk › e2fsprogs/libext2fs2@1.44.0-1
  • Introduced through: openjdk@10-ea-jdk › e2fsprogs/libss2@1.44.0-1

NVD Description

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

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

Remediation

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

References

Out-of-bounds Read vulnerability report

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › expat/libexpat1@2.2.5-3

NVD Description

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

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

Remediation

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

References

Integer Overflow or Wraparound vulnerability report

high severity

Buffer Overflow

  • Vulnerable module: fribidi/libfribidi0
  • Introduced through: fribidi/libfribidi0@0.19.7-2
  • Fixed in: 1.0.7-1.1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › fribidi/libfribidi0@0.19.7-2

NVD Description

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

A buffer overflow in the fribidi_get_par_embedding_levels_ex() function in lib/fribidi-bidi.c of GNU FriBidi through 1.0.7 allows an attacker to cause a denial of service or possibly execute arbitrary code by delivering crafted text content to a user, when this content is then rendered by an application that uses FriBidi for text layout calculations. Examples include any GNOME or GTK+ based application that uses Pango for text layout, as this internally uses FriBidi for bidirectional text layout. For example, the attacker can construct a crafted text file to be opened in GEdit, or a crafted IRC message to be viewed in HexChat.

Remediation

Upgrade Debian:unstable fribidi to version 1.0.7-1.1 or higher.

References

Buffer Overflow vulnerability report

high severity

Stack-based Buffer Overflow

  • Vulnerable module: fribidi/libfribidi0
  • Introduced through: fribidi/libfribidi0@0.19.7-2
  • Fixed in: 1.0.8-2.1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › fribidi/libfribidi0@0.19.7-2

NVD Description

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

A stack-based buffer overflow flaw was found in the Fribidi package. This flaw allows an attacker to pass a specially crafted file to the Fribidi application, which leads to a possible memory leak or a denial of service.

Remediation

Upgrade Debian:unstable fribidi to version 1.0.8-2.1 or higher.

References

Stack-based Buffer Overflow vulnerability report

high severity

Integer Overflow or Wraparound

  • Vulnerable module: gdk-pixbuf/libgdk-pixbuf2.0-0
  • Introduced through: gdk-pixbuf/libgdk-pixbuf2.0-0@2.36.11-2, gdk-pixbuf/libgdk-pixbuf2.0-bin@2.36.11-2 and others
  • Fixed in: 2.42.8+dfsg-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gdk-pixbuf/libgdk-pixbuf2.0-0@2.36.11-2
  • Introduced through: openjdk@10-ea-jdk › gdk-pixbuf/libgdk-pixbuf2.0-bin@2.36.11-2
  • Introduced through: openjdk@10-ea-jdk › gdk-pixbuf/libgdk-pixbuf2.0-common@2.36.11-2

NVD Description

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

GNOME GdkPixbuf (aka GDK-PixBuf) before 2.42.8 allows a heap-based buffer overflow when compositing or clearing frames in GIF files, as demonstrated by io-gif-animation.c composite_frame. This overflow is controllable and could be abused for code execution, especially on 32-bit systems.

Remediation

Upgrade Debian:unstable gdk-pixbuf to version 2.42.8+dfsg-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: gdk-pixbuf/libgdk-pixbuf2.0-0
  • Introduced through: gdk-pixbuf/libgdk-pixbuf2.0-0@2.36.11-2, gdk-pixbuf/libgdk-pixbuf2.0-bin@2.36.11-2 and others
  • Fixed in: 2.42.12+dfsg-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gdk-pixbuf/libgdk-pixbuf2.0-0@2.36.11-2
  • Introduced through: openjdk@10-ea-jdk › gdk-pixbuf/libgdk-pixbuf2.0-bin@2.36.11-2
  • Introduced through: openjdk@10-ea-jdk › gdk-pixbuf/libgdk-pixbuf2.0-common@2.36.11-2

NVD Description

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

In GNOME GdkPixbuf (aka gdk-pixbuf) through 2.42.10, the ANI (Windows animated cursor) decoder encounters heap memory corruption (in ani_load_chunk in io-ani.c) when parsing chunks in a crafted .ani file. A crafted file could allow an attacker to overwrite heap metadata, leading to a denial of service or code execution attack. This occurs in gdk_pixbuf_set_option() in gdk-pixbuf.c.

Remediation

Upgrade Debian:unstable gdk-pixbuf to version 2.42.12+dfsg-1 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Arbitrary Code Injection

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.40.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

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

Git is a revision control system. Prior to versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1, a specially crafted .gitmodules file with submodule URLs that are longer than 1024 characters can used to exploit a bug in config.c::git_config_copy_or_rename_section_in_file(). This bug can be used to inject arbitrary configuration into a user's $GIT_DIR/config when attempting to remove the configuration section associated with that submodule. When the attacker injects configuration values which specify executables to run (such as core.pager, core.editor, core.sshCommand, etc.) this can lead to a remote code execution. A fix A fix is available in versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1. As a workaround, avoid running git submodule deinit on untrusted repositories or without prior inspection of any submodule sections in $GIT_DIR/config.

Remediation

Upgrade Debian:unstable git to version 1:2.40.1-1 or higher.

References

Arbitrary Code Injection vulnerability report

high severity

CVE-2024-32004

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.45.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

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

Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, an attacker can prepare a local repository in such a way that, when cloned, will execute arbitrary code during the operation. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4. As a workaround, avoid cloning repositories from untrusted sources.

Remediation

Upgrade Debian:unstable git to version 1:2.45.1-1 or higher.

References

CVE-2024-32004 vulnerability report

high severity

CVE-2024-32465

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.45.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

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

Git is a revision control system. The Git project recommends to avoid working in untrusted repositories, and instead to clone it first with git clone --no-local to obtain a clean copy. Git has specific protections to make that a safe operation even with an untrusted source repository, but vulnerabilities allow those protections to be bypassed. In the context of cloning local repositories owned by other users, this vulnerability has been covered in CVE-2024-32004. But there are circumstances where the fixes for CVE-2024-32004 are not enough: For example, when obtaining a .zip file containing a full copy of a Git repository, it should not be trusted by default to be safe, as e.g. hooks could be configured to run within the context of that repository. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4. As a workaround, avoid using Git in repositories that have been obtained via archives from untrusted sources.

Remediation

Upgrade Debian:unstable git to version 1:2.45.1-1 or higher.

References

CVE-2024-32465 vulnerability report

high severity

Directory Traversal

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.17.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

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

In Git before 2.13.7, 2.14.x before 2.14.4, 2.15.x before 2.15.2, 2.16.x before 2.16.4, and 2.17.x before 2.17.1, remote code execution can occur. With a crafted .gitmodules file, a malicious project can execute an arbitrary script on a machine that runs "git clone --recurse-submodules" because submodule "names" are obtained from this file, and then appended to $GIT_DIR/modules, leading to directory traversal with "../" in a name. Finally, post-checkout hooks from a submodule are executed, bypassing the intended design in which hooks are not obtained from a remote server.

Remediation

Upgrade Debian:unstable git to version 1:2.17.1-1 or higher.

References

Directory Traversal vulnerability report

high severity

Improper Input Validation

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.24.0-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

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

Arbitrary command execution is possible in Git before 2.20.2, 2.21.x before 2.21.1, 2.22.x before 2.22.2, 2.23.x before 2.23.1, and 2.24.x before 2.24.1 because a "git submodule update" operation can run commands found in the .gitmodules file of a malicious repository.

Remediation

Upgrade Debian:unstable git to version 1:2.24.0-2 or higher.

References

Improper Input Validation vulnerability report

high severity

Improper Ownership Management

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.37.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

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

Git is a distributed revision control system. Git prior to versions 2.37.1, 2.36.2, 2.35.4, 2.34.4, 2.33.4, 2.32.3, 2.31.4, and 2.30.5, is vulnerable to privilege escalation in all platforms. An unsuspecting user could still be affected by the issue reported in CVE-2022-24765, for example when navigating as root into a shared tmp directory that is owned by them, but where an attacker could create a git repository. Versions 2.37.1, 2.36.2, 2.35.4, 2.34.4, 2.33.4, 2.32.3, 2.31.4, and 2.30.5 contain a patch for this issue. The simplest way to avoid being affected by the exploit described in the example is to avoid running git as root (or an Administrator in Windows), and if needed to reduce its use to a minimum. While a generic workaround is not possible, a system could be hardened from the exploit described in the example by removing any such repository if it exists already and creating one as root to block any future attacks.

Remediation

Upgrade Debian:unstable git to version 1:2.37.2-1 or higher.

References

Improper Ownership Management vulnerability report

high severity

Uncontrolled Search Path Element

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.35.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

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

Git for Windows is a fork of Git containing Windows-specific patches. This vulnerability affects users working on multi-user machines, where untrusted parties have write access to the same hard disk. Those untrusted parties could create the folder C:\.git, which would be picked up by Git operations run supposedly outside a repository while searching for a Git directory. Git would then respect any config in said Git directory. Git Bash users who set GIT_PS1_SHOWDIRTYSTATE are vulnerable as well. Users who installed posh-gitare vulnerable simply by starting a PowerShell. Users of IDEs such as Visual Studio are vulnerable: simply creating a new project would already read and respect the config specified in C:\.git\config. Users of the Microsoft fork of Git are vulnerable simply by starting a Git Bash. The problem has been patched in Git for Windows v2.35.2. Users unable to upgrade may create the folder .git on all drives where Git commands are run, and remove read/write access from those folders as a workaround. Alternatively, define or extend GIT_CEILING_DIRECTORIES to cover the parent directory of the user profile, e.g. C:\Users if the user profile is located in C:\Users\my-user-name.

Remediation

Upgrade Debian:unstable git to version 1:2.35.2-1 or higher.

References

Uncontrolled Search Path Element vulnerability report

high severity

Off-by-one Error

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

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

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

Remediation

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

References

Off-by-one Error vulnerability report

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

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

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

Remediation

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

References

Out-of-bounds Write vulnerability report

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

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

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

Remediation

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

References

Out-of-bounds Write vulnerability report

high severity

Unchecked Return Value

  • Vulnerable module: inetutils/inetutils-ping
  • Introduced through: inetutils/inetutils-ping@2:1.9.4-3
  • Fixed in: 2:2.4-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › inetutils/inetutils-ping@2:1.9.4-3

NVD Description

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

GNU inetutils before 2.5 may allow privilege escalation because of unchecked return values of set*id() family functions in ftpd, rcp, rlogin, rsh, rshd, and uucpd. This is, for example, relevant if the setuid system call fails when a process is trying to drop privileges before letting an ordinary user control the activities of the process.

Remediation

Upgrade Debian:unstable inetutils to version 2:2.4-3 or higher.

References

Unchecked Return Value vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: json-c/libjson-c3
  • Introduced through: json-c/libjson-c3@0.12.1-1.3
  • Fixed in: 0.13.1+dfsg-8

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › json-c/libjson-c3@0.12.1-1.3

NVD Description

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

json-c through 0.14 has an integer overflow and out-of-bounds write via a large JSON file, as demonstrated by printbuf_memappend.

Remediation

Upgrade Debian:unstable json-c to version 0.13.1+dfsg-8 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Integer Overflow or Wraparound

  • Vulnerable module: libcap2
  • Introduced through: libcap2@1:2.25-1.2
  • Fixed in: 1:2.66-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libcap2@1:2.25-1.2

NVD Description

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

A vulnerability was found in libcap. This issue occurs in the _libcap_strdup() function and can lead to an integer overflow if the input string is close to 4GiB.

Remediation

Upgrade Debian:unstable libcap2 to version 1:2.66-4 or higher.

References

Integer Overflow or Wraparound vulnerability report

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-6@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-data@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-dev@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-doc@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-xcb1@2:1.6.5-1

NVD Description

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

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

Remediation

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

References

Integer Overflow or Wraparound vulnerability report

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-6@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-data@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-dev@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-doc@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-xcb1@2:1.6.5-1

NVD Description

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

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

Remediation

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

References

Integer Overflow or Wraparound vulnerability report

high severity

CVE-2022-49043

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.12.7+dfsg+really2.9.14-0.4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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

xmlXIncludeAddNode in xinclude.c in libxml2 before 2.11.0 has a use-after-free.

Remediation

Upgrade Debian:unstable libxml2 to version 2.12.7+dfsg+really2.9.14-0.4 or higher.

References

CVE-2022-49043 vulnerability report

high severity

Double Free

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.9.14+dfsg-1.1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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:unstable 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:unstable libxml2 to version 2.9.14+dfsg-1.1 or higher.

References

Double Free vulnerability report

high severity

Use After Free

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.9.10+dfsg-6.6

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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:unstable 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:unstable libxml2 to version 2.9.10+dfsg-6.6 or higher.

References

Use After Free vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: ncurses/libncurses5
  • Introduced through: ncurses/libncurses5@6.1-1, ncurses/libncursesw5@6.1-1 and others
  • Fixed in: 6.4-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › ncurses/libncurses5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/libncursesw5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/libtinfo5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/ncurses-base@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/ncurses-bin@6.1-1

NVD Description

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

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

Remediation

Upgrade Debian:unstable ncurses to version 6.4-3 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Directory Traversal

  • Vulnerable module: pam/libpam-modules
  • Introduced through: pam/libpam-modules@1.1.8-3.7, pam/libpam-modules-bin@1.1.8-3.7 and others
  • Fixed in: 1.7.0-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › pam/libpam-modules@1.1.8-3.7
  • Introduced through: openjdk@10-ea-jdk › pam/libpam-modules-bin@1.1.8-3.7
  • Introduced through: openjdk@10-ea-jdk › pam/libpam-runtime@1.1.8-3.7
  • Introduced through: openjdk@10-ea-jdk › pam/libpam0g@1.1.8-3.7

NVD Description

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

A flaw was found in linux-pam. The module pam_namespace may use access user-controlled paths without proper protection, allowing local users to elevate their privileges to root via multiple symlink attacks and race conditions.

Remediation

Upgrade Debian:unstable pam to version 1.7.0-5 or higher.

References

Directory Traversal vulnerability report

high severity

Improper Verification of Cryptographic Signature

  • Vulnerable module: perl
  • Introduced through: perl@5.26.1-5, perl/libperl5.26@5.26.1-5 and others
  • Fixed in: 5.36.0-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › perl@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/libperl5.26@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-base@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-modules-5.26@5.26.1-5

NVD Description

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

CPAN 2.28 allows Signature Verification Bypass.

Remediation

Upgrade Debian:unstable perl to version 5.36.0-4 or higher.

References

Improper Verification of Cryptographic Signature vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: perl
  • Introduced through: perl@5.26.1-5, perl/libperl5.26@5.26.1-5 and others
  • Fixed in: 5.36.0-10

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › perl@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/libperl5.26@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-base@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-modules-5.26@5.26.1-5

NVD Description

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

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

Remediation

Upgrade Debian:unstable perl to version 5.36.0-10 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Untrusted Search Path

  • Vulnerable module: perl
  • Introduced through: perl@5.26.1-5, perl/libperl5.26@5.26.1-5 and others
  • Fixed in: 5.32.1-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › perl@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/libperl5.26@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-base@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-modules-5.26@5.26.1-5

NVD Description

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

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

Remediation

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

References

Untrusted Search Path vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: procps
  • Introduced through: procps@2:3.3.12-4 and procps/libprocps6@2:3.3.12-4
  • Fixed in: 2:3.3.15-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › procps@2:3.3.12-4
  • Introduced through: openjdk@10-ea-jdk › procps/libprocps6@2:3.3.12-4

NVD Description

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

procps-ng before version 3.3.15 is vulnerable to multiple integer overflows leading to a heap corruption in file2strvec function. This allows a privilege escalation for a local attacker who can create entries in procfs by starting processes, which could result in crashes or arbitrary code execution in proc utilities run by other users.

Remediation

Upgrade Debian:unstable procps to version 2:3.3.15-1 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: systemd
  • Introduced through: systemd@238-4, systemd/libnss-systemd@238-4 and others
  • Fixed in: 240-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libnss-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libpam-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libsystemd0@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libudev1@238-2
  • Introduced through: openjdk@10-ea-jdk › systemd/systemd-sysv@238-4

NVD Description

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

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

Remediation

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

References

Allocation of Resources Without Limits or Throttling vulnerability report

high severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: systemd
  • Introduced through: systemd@238-4, systemd/libnss-systemd@238-4 and others
  • Fixed in: 240-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libnss-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libpam-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libsystemd0@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libudev1@238-2
  • Introduced through: openjdk@10-ea-jdk › systemd/systemd-sysv@238-4

NVD Description

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

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

Remediation

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

References

Allocation of Resources Without Limits or Throttling vulnerability report

high severity

CVE-2023-26604

  • Vulnerable module: systemd
  • Introduced through: systemd@238-4, systemd/libnss-systemd@238-4 and others
  • Fixed in: 247.1-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libnss-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libpam-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libsystemd0@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libudev1@238-2
  • Introduced through: openjdk@10-ea-jdk › systemd/systemd-sysv@238-4

NVD Description

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

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

Remediation

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

References

CVE-2023-26604 vulnerability report

high severity

Deserialization of Untrusted Data

  • Vulnerable module: systemd
  • Introduced through: systemd@238-4, systemd/libnss-systemd@238-4 and others
  • Fixed in: 239-12

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libnss-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libpam-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libsystemd0@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libudev1@238-2
  • Introduced through: openjdk@10-ea-jdk › systemd/systemd-sysv@238-4

NVD Description

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

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

Remediation

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

References

Deserialization of Untrusted Data vulnerability report

high severity

Incorrect Privilege Assignment

  • Vulnerable module: systemd
  • Introduced through: systemd@238-4, systemd/libnss-systemd@238-4 and others
  • Fixed in: 242-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libnss-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libpam-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libsystemd0@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libudev1@238-2
  • Introduced through: openjdk@10-ea-jdk › systemd/systemd-sysv@238-4

NVD Description

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

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

Remediation

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

References

Incorrect Privilege Assignment vulnerability report

high severity

Privilege Chaining

  • Vulnerable module: systemd
  • Introduced through: systemd@238-4, systemd/libnss-systemd@238-4 and others
  • Fixed in: 242-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libnss-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libpam-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libsystemd0@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libudev1@238-2
  • Introduced through: openjdk@10-ea-jdk › systemd/systemd-sysv@238-4

NVD Description

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

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

Remediation

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

References

Privilege Chaining vulnerability report

high severity

Use After Free

  • Vulnerable module: systemd
  • Introduced through: systemd@238-4, systemd/libnss-systemd@238-4 and others
  • Fixed in: 244.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libnss-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libpam-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libsystemd0@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libudev1@238-2
  • Introduced through: openjdk@10-ea-jdk › systemd/systemd-sysv@238-4

NVD Description

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

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

Remediation

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

References

Use After Free vulnerability report

high severity

Integer Overflow or Wraparound

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.1.0+git201212-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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

An integer overflow flaw was found in libtiff that exists in the tif_getimage.c file. This flaw allows an attacker to inject and execute arbitrary code when a user opens a crafted TIFF file. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability.

Remediation

Upgrade Debian:unstable tiff to version 4.1.0+git201212-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

high severity

Out-of-Bounds

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.1.0+git201212-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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

A heap-based buffer overflow flaw was found in libtiff in the handling of TIFF images in libtiff's TIFF2PDF tool. A specially crafted TIFF file can lead to arbitrary code execution. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability.

Remediation

Upgrade Debian:unstable tiff to version 4.1.0+git201212-1 or higher.

References

Out-of-Bounds vulnerability report

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › unzip@6.0-21

NVD Description

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

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

Remediation

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

References

Out-of-bounds Write vulnerability report

high severity

Information Exposure

  • Vulnerable module: wget
  • Introduced through: wget@1.19.4-1
  • Fixed in: 1.20.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › wget@1.19.4-1

NVD Description

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

set_file_metadata in xattr.c in GNU Wget before 1.20.1 stores a file's origin URL in the user.xdg.origin.url metadata attribute of the extended attributes of the downloaded file, which allows local users to obtain sensitive information (e.g., credentials contained in the URL) by reading this attribute, as demonstrated by getfattr. This also applies to Referer information in the user.xdg.referrer.url metadata attribute. According to 2016-07-22 in the Wget ChangeLog, user.xdg.origin.url was partially based on the behavior of fwrite_xattr in tool_xattr.c in curl.

Remediation

Upgrade Debian:unstable wget to version 1.20.1-1 or higher.

References

Information Exposure vulnerability report

high severity

Integer Overflow or Wraparound

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.56.1-2 and glib2.0/libglib2.0-data@2.56.1-2
  • Fixed in: 2.86.3-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-0@2.56.1-2
  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-data@2.56.1-2

NVD Description

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

A heap-based buffer overflow problem was found in glib through an incorrect calculation of buffer size in the g_escape_uri_string() function. If the string to escape contains a very large number of unacceptable characters (which would need escaping), the calculation of the length of the escaped string could overflow, leading to a potential write off the end of the newly allocated string.

Remediation

Upgrade Debian:unstable glib2.0 to version 2.86.3-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

high severity

CVE-2025-24928

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.12.7+dfsg+really2.9.14-0.4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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

libxml2 before 2.12.10 and 2.13.x before 2.13.6 has a stack-based buffer overflow in xmlSnprintfElements in valid.c. To exploit this, DTD validation must occur for an untrusted document or untrusted DTD. NOTE: this is similar to CVE-2017-9047.

Remediation

Upgrade Debian:unstable libxml2 to version 2.12.7+dfsg+really2.9.14-0.4 or higher.

References

CVE-2025-24928 vulnerability report

high severity

Buffer Overflow

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

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

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

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

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

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

Remediation

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

References

Buffer Overflow vulnerability report

high severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 8.3.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

When curl retrieves an HTTP response, it stores the incoming headers so that they can be accessed later via the libcurl headers API.

However, curl did not have a limit in how many or how large headers it would accept in a response, allowing a malicious server to stream an endless series of headers and eventually cause curl to run out of heap memory.

Remediation

Upgrade Debian:unstable curl to version 8.3.0-1 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

high severity

Cleartext Transmission of Sensitive Information

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.79.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

References

Cleartext Transmission of Sensitive Information vulnerability report

high severity

Cleartext Transmission of Sensitive Information

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.86.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

In curl before 7.86.0, the HSTS check could be bypassed to trick it into staying with HTTP. Using its HSTS support, curl can be instructed to use HTTPS directly (instead of using an insecure cleartext HTTP step) even when HTTP is provided in the URL. This mechanism could be bypassed if the host name in the given URL uses IDN characters that get replaced with ASCII counterparts as part of the IDN conversion, e.g., using the character UTF-8 U+3002 (IDEOGRAPHIC FULL STOP) instead of the common ASCII full stop of U+002E (.). The earliest affected version is 7.77.0 2021-05-26.

Remediation

Upgrade Debian:unstable curl to version 7.86.0-1 or higher.

References

Cleartext Transmission of Sensitive Information vulnerability report

high severity

Cleartext Transmission of Sensitive Information

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.86.0-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

A vulnerability exists in curl <7.87.0 HSTS check that could be bypassed to trick it to keep using HTTP. Using its HSTS support, curl can be instructed to use HTTPS instead of using an insecure clear-text HTTP step even when HTTP is provided in the URL. However, the HSTS mechanism could be bypassed if the host name in the given URL first uses IDN characters that get replaced to ASCII counterparts as part of the IDN conversion. Like using the character UTF-8 U+3002 (IDEOGRAPHIC FULL STOP) instead of the common ASCII full stop (U+002E) .. Then in a subsequent request, it does not detect the HSTS state and makes a clear text transfer. Because it would store the info IDN encoded but look for it IDN decoded.

Remediation

Upgrade Debian:unstable curl to version 7.86.0-3 or higher.

References

Cleartext Transmission of Sensitive Information vulnerability report

high severity

CVE-2022-27775

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.83.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

An information disclosure vulnerability exists in curl 7.65.0 to 7.82.0 are vulnerable that by using an IPv6 address that was in the connection pool but with a different zone id it could reuse a connection instead.

Remediation

Upgrade Debian:unstable curl to version 7.83.0-1 or higher.

References

CVE-2022-27775 vulnerability report

high severity

CVE-2024-6197

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 8.9.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

libcurl's ASN1 parser has this utf8asn1str() function used for parsing an ASN.1 UTF-8 string. Itcan detect an invalid field and return error. Unfortunately, when doing so it also invokes free() on a 4 byte localstack buffer. Most modern malloc implementations detect this error and immediately abort. Some however accept the input pointer and add that memory to its list of available chunks. This leads to the overwriting of nearby stack memory. The content of the overwrite is decided by the free() implementation; likely to be memory pointers and a set of flags. The most likely outcome of exploting this flaw is a crash, although it cannot be ruled out that more serious results can be had in special circumstances.

Remediation

Upgrade Debian:unstable curl to version 8.9.0-1 or higher.

References

CVE-2024-6197 vulnerability report

high severity

Improper Certificate Validation

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.74.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

curl 7.41.0 through 7.73.0 is vulnerable to an improper check for certificate revocation due to insufficient verification of the OCSP response.

Remediation

Upgrade Debian:unstable curl to version 7.74.0-1 or higher.

References

Improper Certificate Validation vulnerability report

high severity

Improper Certificate Validation

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.83.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

References

Improper Certificate Validation vulnerability report

high severity

Information Exposure

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.72.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

curl 7.62.0 through 7.70.0 is vulnerable to an information disclosure vulnerability that can lead to a partial password being leaked over the network and to the DNS server(s).

Remediation

Upgrade Debian:unstable curl to version 7.72.0-1 or higher.

References

Information Exposure vulnerability report

high severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.83.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

References

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability report

high severity

NULL Pointer Dereference

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.60.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

A NULL pointer dereference exists in curl 7.21.0 to and including curl 7.58.0 in the LDAP code that allows an attacker to cause a denial of service

Remediation

Upgrade Debian:unstable curl to version 7.60.0-1 or higher.

References

NULL Pointer Dereference vulnerability report

high severity

Out-of-bounds Read

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.64.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

libcurl versions from 7.34.0 to before 7.64.0 are vulnerable to a heap out-of-bounds read in the code handling the end-of-response for SMTP. If the buffer passed to smtp_endofresp() isn't NUL terminated and contains no character ending the parsed number, and len is set to 5, then the strtol() call reads beyond the allocated buffer. The read contents will not be returned to the caller.

Remediation

Upgrade Debian:unstable curl to version 7.64.0-1 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Out-of-bounds Read

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.64.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

libcurl versions from 7.36.0 to before 7.64.0 is vulnerable to a heap buffer out-of-bounds read. The function handling incoming NTLM type-2 messages (lib/vauth/ntlm.c:ntlm_decode_type2_target) does not validate incoming data correctly and is subject to an integer overflow vulnerability. Using that overflow, a malicious or broken NTLM server could trick libcurl to accept a bad length + offset combination that would lead to a buffer read out-of-bounds.

Remediation

Upgrade Debian:unstable curl to version 7.64.0-1 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.74.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

curl 7.21.0 to and including 7.73.0 is vulnerable to uncontrolled recursion due to a stack overflow issue in FTP wildcard match parsing.

Remediation

Upgrade Debian:unstable curl to version 7.74.0-1 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Server-Side Request Forgery (SSRF)

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.83.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

The curl URL parser wrongly accepts percent-encoded URL separators like '/'when decoding the host name part of a URL, making it a different URL usingthe wrong host name when it is later retrieved.For example, a URL like http://example.com%2F127.0.0.1/, would be allowed bythe parser and get transposed into http://example.com/127.0.0.1/. This flawcan be used to circumvent filters, checks and more.

Remediation

Upgrade Debian:unstable curl to version 7.83.1-1 or higher.

References

Server-Side Request Forgery (SSRF) vulnerability report

high severity

Use After Free

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.88.1-10

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

A use after free vulnerability exists in curl <v8.1.0 in the way libcurl offers a feature to verify an SSH server's public key using a SHA 256 hash. When this check fails, libcurl would free the memory for the fingerprint before it returns an error message containing the (now freed) hash. This flaw risks inserting sensitive heap-based data into the error message that might be shown to users or otherwise get leaked and revealed.

Remediation

Upgrade Debian:unstable curl to version 7.88.1-10 or higher.

References

Use After Free vulnerability report

high severity

Use After Free

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.72.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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

Due to use of a dangling pointer, libcurl 7.29.0 through 7.71.1 can use the wrong connection when sending data.

Remediation

Upgrade Debian:unstable curl to version 7.72.0-1 or higher.

References

Use After Free vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: cyrus-sasl2/libsasl2-2
  • Introduced through: cyrus-sasl2/libsasl2-2@2.1.27~101-g0780600+dfsg-3 and cyrus-sasl2/libsasl2-modules-db@2.1.27~101-g0780600+dfsg-3
  • Fixed in: 2.1.27+dfsg-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › cyrus-sasl2/libsasl2-2@2.1.27~101-g0780600+dfsg-3
  • Introduced through: openjdk@10-ea-jdk › cyrus-sasl2/libsasl2-modules-db@2.1.27~101-g0780600+dfsg-3

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

cyrus-sasl (aka Cyrus SASL) 2.1.27 has an out-of-bounds write leading to unauthenticated remote denial-of-service in OpenLDAP via a malformed LDAP packet. The OpenLDAP crash is ultimately caused by an off-by-one error in _sasl_add_string in common.c in cyrus-sasl.

Remediation

Upgrade Debian:unstable cyrus-sasl2 to version 2.1.27+dfsg-2 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: e2fsprogs
  • Introduced through: e2fsprogs@1.44.0-1, e2fsprogs/libcom-err2@1.44.0-1 and others
  • Fixed in: 1.45.4-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › e2fsprogs@1.44.0-1
  • Introduced through: openjdk@10-ea-jdk › e2fsprogs/libcom-err2@1.44.0-1
  • Introduced through: openjdk@10-ea-jdk › e2fsprogs/libext2fs2@1.44.0-1
  • Introduced through: openjdk@10-ea-jdk › e2fsprogs/libss2@1.44.0-1

NVD Description

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

An exploitable code execution vulnerability exists in the quota file functionality of E2fsprogs 1.45.3. A specially crafted ext4 partition can cause an out-of-bounds write on the heap, resulting in code execution. An attacker can corrupt a partition to trigger this vulnerability.

Remediation

Upgrade Debian:unstable e2fsprogs to version 1.45.4-1 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › expat/libexpat1@2.2.5-3

NVD Description

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

Expat (aka libexpat) before 2.4.4 has an integer overflow in the doProlog function.

Remediation

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

References

Integer Overflow or Wraparound vulnerability report

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › expat/libexpat1@2.2.5-3

NVD Description

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

In Expat (aka libexpat) before 2.4.5, there is an integer overflow in copyString.

Remediation

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

References

Integer Overflow or Wraparound vulnerability report

high severity

Out-of-bounds Read

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.5-3
  • Fixed in: 2.2.7-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › expat/libexpat1@2.2.5-3

NVD Description

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

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

Remediation

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

References

Out-of-bounds Read vulnerability report

high severity

Resource Exhaustion

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › expat/libexpat1@2.2.5-3

NVD Description

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

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

Remediation

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

References

Resource Exhaustion vulnerability report

high severity

Uncontrolled Recursion

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.5-3
  • Fixed in: 2.7.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › expat/libexpat1@2.2.5-3

NVD Description

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

A stack overflow vulnerability exists in the libexpat library due to the way it handles recursive entity expansion in XML documents. When parsing an XML document with deeply nested entity references, libexpat can be forced to recurse indefinitely, exhausting the stack space and causing a crash. This issue could lead to denial of service (DoS) or, in some cases, exploitable memory corruption, depending on the environment and library usage.

Remediation

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

References

Uncontrolled Recursion vulnerability report

high severity

Use After Free

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › expat/libexpat1@2.2.5-3

NVD Description

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

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

Remediation

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

References

Use After Free vulnerability report

high severity

XML External Entity (XXE) Injection

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › expat/libexpat1@2.2.5-3

NVD Description

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

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

Remediation

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

References

XML External Entity (XXE) Injection vulnerability report

high severity

XML External Entity (XXE) Injection

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.5-3
  • Fixed in: 2.6.2-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › expat/libexpat1@2.2.5-3

NVD Description

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

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

Remediation

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

References

XML External Entity (XXE) Injection vulnerability report

high severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › freetype/libfreetype6@2.8.1-2

NVD Description

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

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

Remediation

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

References

Out-of-bounds Read vulnerability report

high severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › freetype/libfreetype6@2.8.1-2

NVD Description

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

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

Remediation

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

References

Out-of-bounds Read vulnerability report

high severity

Buffer Overflow

  • Vulnerable module: gdk-pixbuf/libgdk-pixbuf2.0-0
  • Introduced through: gdk-pixbuf/libgdk-pixbuf2.0-0@2.36.11-2, gdk-pixbuf/libgdk-pixbuf2.0-bin@2.36.11-2 and others
  • Fixed in: 2.42.12+dfsg-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gdk-pixbuf/libgdk-pixbuf2.0-0@2.36.11-2
  • Introduced through: openjdk@10-ea-jdk › gdk-pixbuf/libgdk-pixbuf2.0-bin@2.36.11-2
  • Introduced through: openjdk@10-ea-jdk › gdk-pixbuf/libgdk-pixbuf2.0-common@2.36.11-2

NVD Description

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

A flaw exists in gdk‑pixbuf within the gdk_pixbuf__jpeg_image_load_increment function (io-jpeg.c) and in glib’s g_base64_encode_step (glib/gbase64.c). When processing maliciously crafted JPEG images, a heap buffer overflow can occur during Base64 encoding, allowing out-of-bounds reads from heap memory, potentially causing application crashes or arbitrary code execution.

Remediation

Upgrade Debian:unstable gdk-pixbuf to version 2.42.12+dfsg-4 or higher.

References

Buffer Overflow vulnerability report

high severity

CVE-2021-40330

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.30.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

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

git_connect_git in connect.c in Git before 2.30.1 allows a repository path to contain a newline character, which may result in unexpected cross-protocol requests, as demonstrated by the git://localhost:1234/%0d%0a%0d%0aGET%20/%20HTTP/1.1 substring.

Remediation

Upgrade Debian:unstable git to version 1:2.30.1-1 or higher.

References

CVE-2021-40330 vulnerability report

high severity

CVE-2023-25652

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.40.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

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

Git is a revision control system. Prior to versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1, by feeding specially crafted input to git apply --reject, a path outside the working tree can be overwritten with partially controlled contents (corresponding to the rejected hunk(s) from the given patch). A fix is available in versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1. As a workaround, avoid using git apply with --reject when applying patches from an untrusted source. Use git apply --stat to inspect a patch before applying; avoid applying one that create a conflict where a link corresponding to the *.rej file exists.

Remediation

Upgrade Debian:unstable git to version 1:2.40.1-1 or higher.

References

CVE-2023-25652 vulnerability report

high severity

Directory Traversal

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.39.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

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

Git, a revision control system, is vulnerable to path traversal prior to versions 2.39.2, 2.38.4, 2.37.6, 2.36.5, 2.35.7, 2.34.7, 2.33.7, 2.32.6, 2.31.7, and 2.30.8. By feeding a crafted input to git apply, a path outside the working tree can be overwritten as the user who is running git apply. A fix has been prepared and will appear in v2.39.2, v2.38.4, v2.37.6, v2.36.5, v2.35.7, v2.34.7, v2.33.7, v2.32.6, v2.31.7, and v2.30.8. As a workaround, use git apply --stat to inspect a patch before applying; avoid applying one that creates a symbolic link and then creates a file beyond the symbolic link.

Remediation

Upgrade Debian:unstable git to version 1:2.39.2-1 or higher.

References

Directory Traversal vulnerability report

high severity

Improper Encoding or Escaping of Output

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.47.2-0.1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

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

Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals. Git defines a line-based protocol that is used to exchange information between Git and Git credential helpers. Some ecosystems (most notably, .NET and node.js) interpret single Carriage Return characters as newlines, which renders the protections against CVE-2020-5260 incomplete for credential helpers that treat Carriage Returns in this way. This issue has been addressed in commit b01b9b8 which is included in release versions v2.48.1, v2.47.2, v2.46.3, v2.45.3, v2.44.3, v2.43.6, v2.42.4, v2.41.3, and v2.40.4. Users are advised to upgrade. Users unable to upgrade should avoid cloning from untrusted URLs, especially recursive clones.

Remediation

Upgrade Debian:unstable git to version 1:2.47.2-0.1 or higher.

References

Improper Encoding or Escaping of Output vulnerability report

high severity

Insufficiently Protected Credentials

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.26.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

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

Affected versions of Git have a vulnerability whereby Git can be tricked into sending private credentials to a host controlled by an attacker. Git uses external "credential helper" programs to store and retrieve passwords or other credentials from secure storage provided by the operating system. Specially-crafted URLs that contain an encoded newline can inject unintended values into the credential helper protocol stream, causing the credential helper to retrieve the password for one server (e.g., good.example.com) for an HTTP request being made to another server (e.g., evil.example.com), resulting in credentials for the former being sent to the latter. There are no restrictions on the relationship between the two, meaning that an attacker can craft a URL that will present stored credentials for any host to a host of their choosing. The vulnerability can be triggered by feeding a malicious URL to git clone. However, the affected URLs look rather suspicious; the likely vector would be through systems which automatically clone URLs not visible to the user, such as Git submodules, or package systems built around Git. The problem has been patched in the versions published on April 14th, 2020, going back to v2.17.x. Anyone wishing to backport the change further can do so by applying commit 9a6bbee (the full release includes extra checks for git fsck, but that commit is sufficient to protect clients against the vulnerability). The patched versions are: 2.17.4, 2.18.3, 2.19.4, 2.20.3, 2.21.2, 2.22.3, 2.23.2, 2.24.2, 2.25.3, 2.26.1.

Remediation

Upgrade Debian:unstable git to version 1:2.26.1-1 or higher.

References

Insufficiently Protected Credentials vulnerability report

high severity

Insufficiently Protected Credentials

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.26.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

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

Affected versions of Git have a vulnerability whereby Git can be tricked into sending private credentials to a host controlled by an attacker. This bug is similar to CVE-2020-5260(GHSA-qm7j-c969-7j4q). The fix for that bug still left the door open for an exploit where some credential is leaked (but the attacker cannot control which one). Git uses external "credential helper" programs to store and retrieve passwords or other credentials from secure storage provided by the operating system. Specially-crafted URLs that are considered illegal as of the recently published Git versions can cause Git to send a "blank" pattern to helpers, missing hostname and protocol fields. Many helpers will interpret this as matching any URL, and will return some unspecified stored password, leaking the password to an attacker's server. The vulnerability can be triggered by feeding a malicious URL to git clone. However, the affected URLs look rather suspicious; the likely vector would be through systems which automatically clone URLs not visible to the user, such as Git submodules, or package systems built around Git. The root of the problem is in Git itself, which should not be feeding blank input to helpers. However, the ability to exploit the vulnerability in practice depends on which helpers are in use. Credential helpers which are known to trigger the vulnerability: - Git's "store" helper - Git's "cache" helper - the "osxkeychain" helper that ships in Git's "contrib" directory Credential helpers which are known to be safe even with vulnerable versions of Git: - Git Credential Manager for Windows Any helper not in this list should be assumed to trigger the vulnerability.

Remediation

Upgrade Debian:unstable git to version 1:2.26.2-1 or higher.

References

Insufficiently Protected Credentials vulnerability report

high severity

Link Following

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.30.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

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

Git is an open-source distributed revision control system. In affected versions of Git a specially crafted repository that contains symbolic links as well as files using a clean/smudge filter such as Git LFS, may cause just-checked out script to be executed while cloning onto a case-insensitive file system such as NTFS, HFS+ or APFS (i.e. the default file systems on Windows and macOS). Note that clean/smudge filters have to be configured for that. Git for Windows configures Git LFS by default, and is therefore vulnerable. The problem has been patched in the versions published on Tuesday, March 9th, 2021. As a workaound, if symbolic link support is disabled in Git (e.g. via git config --global core.symlinks false), the described attack won't work. Likewise, if no clean/smudge filters such as Git LFS are configured globally (i.e. before cloning), the attack is foiled. As always, it is best to avoid cloning repositories from untrusted sources. The earliest impacted version is 2.14.2. The fix versions are: 2.30.1, 2.29.3, 2.28.1, 2.27.1, 2.26.3, 2.25.5, 2.24.4, 2.23.4, 2.22.5, 2.21.4, 2.20.5, 2.19.6, 2.18.5, 2.17.62.17.6.

Remediation

Upgrade Debian:unstable git to version 1:2.30.2-1 or higher.

References

Link Following vulnerability report

high severity

Incorrect Conversion between Numeric Types

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.56.1-2 and glib2.0/libglib2.0-data@2.56.1-2
  • Fixed in: 2.66.7-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-0@2.56.1-2
  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-data@2.56.1-2

NVD Description

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

An issue was discovered in GNOME GLib before 2.66.7 and 2.67.x before 2.67.4. If g_byte_array_new_take() was called with a buffer of 4GB or more on a 64-bit platform, the length would be truncated modulo 2**32, causing unintended length truncation.

Remediation

Upgrade Debian:unstable glib2.0 to version 2.66.7-1 or higher.

References

Incorrect Conversion between Numeric Types vulnerability report

high severity

Incorrect Conversion between Numeric Types

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.56.1-2 and glib2.0/libglib2.0-data@2.56.1-2
  • Fixed in: 2.66.6-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-0@2.56.1-2
  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-data@2.56.1-2

NVD Description

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

An issue was discovered in GNOME GLib before 2.66.6 and 2.67.x before 2.67.3. The function g_bytes_new has an integer overflow on 64-bit platforms due to an implicit cast from 64 bits to 32 bits. The overflow could potentially lead to memory corruption.

Remediation

Upgrade Debian:unstable glib2.0 to version 2.66.6-1 or higher.

References

Incorrect Conversion between Numeric Types vulnerability report

high severity

Incorrect Permission Assignment for Critical Resource

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.56.1-2 and glib2.0/libglib2.0-data@2.56.1-2
  • Fixed in: 2.60.5-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-0@2.56.1-2
  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-data@2.56.1-2

NVD Description

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

The keyfile settings backend in GNOME GLib (aka glib2.0) before 2.60.0 creates directories using g_file_make_directory_with_parents (kfsb->dir, NULL, NULL) and files using g_file_replace_contents (kfsb->file, contents, length, NULL, FALSE, G_FILE_CREATE_REPLACE_DESTINATION, NULL, NULL, NULL). Consequently, it does not properly restrict directory (and file) permissions. Instead, for directories, 0777 permissions are used; for files, default file permissions are used. This is similar to CVE-2019-12450.

Remediation

Upgrade Debian:unstable glib2.0 to version 2.60.5-1 or higher.

References

Incorrect Permission Assignment for Critical Resource vulnerability report

high severity

Resource Exhaustion

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.56.1-2 and glib2.0/libglib2.0-data@2.56.1-2
  • Fixed in: 2.74.4-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-0@2.56.1-2
  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-data@2.56.1-2

NVD Description

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

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

Remediation

Upgrade Debian:unstable glib2.0 to version 2.74.4-1 or higher.

References

Resource Exhaustion vulnerability report

high severity

Improper Data Handling

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

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

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

Remediation

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

References

Improper Data Handling vulnerability report

high severity

Improper Input Validation

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

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

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

Remediation

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

References

Improper Input Validation vulnerability report

high severity

Memory Leak

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

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

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

Remediation

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

References

Memory Leak vulnerability report

high severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

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

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

Remediation

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

References

Out-of-bounds Read vulnerability report

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

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

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

Remediation

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

References

Out-of-bounds Write vulnerability report

high severity

Reachable Assertion

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

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

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

Remediation

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

References

Reachable Assertion vulnerability report

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gmp/libgmp10@2:6.1.2+dfsg-3

NVD Description

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

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

Remediation

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

References

Integer Overflow or Wraparound vulnerability report

high severity

Use of Incorrectly-Resolved Name or Reference

  • Vulnerable module: gnupg2/dirmngr
  • Introduced through: gnupg2/dirmngr@2.2.5-1, gnupg2/gnupg@2.2.5-1 and others
  • Fixed in: 2.2.8-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gnupg2/dirmngr@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gnupg@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gnupg-l10n@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gnupg-utils@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpg@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpg-agent@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpg-wks-client@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpg-wks-server@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpgconf@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpgsm@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpgv@2.2.5-1

NVD Description

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

mainproc.c in GnuPG before 2.2.8 mishandles the original filename during decryption and verification actions, which allows remote attackers to spoof the output that GnuPG sends on file descriptor 2 to other programs that use the "--status-fd 2" option. For example, the OpenPGP data might represent an original filename that contains line feed characters in conjunction with GOODSIG or VALIDSIG status codes.

Remediation

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

References

Use of Incorrectly-Resolved Name or Reference vulnerability report

high severity

Access of Uninitialized Pointer

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gnutls28/libgnutls30@3.5.18-1

NVD Description

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

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

Remediation

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

References

Access of Uninitialized Pointer vulnerability report

high severity

Double Free

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.18-1
  • Fixed in: 3.7.7-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gnutls28/libgnutls30@3.5.18-1

NVD Description

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

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

Remediation

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

References

Double Free vulnerability report

high severity

Double Free

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gnutls28/libgnutls30@3.5.18-1

NVD Description

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

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

Remediation

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

References

Double Free vulnerability report

high severity

Improper Verification of Cryptographic Signature

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.18-1
  • Fixed in: 3.8.3-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gnutls28/libgnutls30@3.5.18-1

NVD Description

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

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

Remediation

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

References

Improper Verification of Cryptographic Signature vulnerability report

high severity

Information Exposure

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.18-1
  • Fixed in: 3.8.3-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gnutls28/libgnutls30@3.5.18-1

NVD Description

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

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

Remediation

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

References

Information Exposure vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.18-1
  • Fixed in: 3.6.15-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gnutls28/libgnutls30@3.5.18-1

NVD Description

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

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

Remediation

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

References

Out-of-bounds Write vulnerability report

high severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: harfbuzz/libharfbuzz0b
  • Introduced through: harfbuzz/libharfbuzz0b@1.7.6-1
  • Fixed in: 8.0.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › harfbuzz/libharfbuzz0b@1.7.6-1

NVD Description

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

hb-ot-layout-gsubgpos.hh in HarfBuzz through 6.0.0 allows attackers to trigger O(n^2) growth via consecutive marks during the process of looking back for base glyphs when attaching marks.

Remediation

Upgrade Debian:unstable harfbuzz to version 8.0.0-1 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

high severity

NULL Pointer Dereference

  • Vulnerable module: inetutils/inetutils-ping
  • Introduced through: inetutils/inetutils-ping@2:1.9.4-3
  • Fixed in: 2:2.3-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › inetutils/inetutils-ping@2:1.9.4-3

NVD Description

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

telnetd in GNU Inetutils through 2.3, MIT krb5-appl through 1.0.3, and derivative works has a NULL pointer dereference via 0xff 0xf7 or 0xff 0xf8. In a typical installation, the telnetd application would crash but the telnet service would remain available through inetd. However, if the telnetd application has many crashes within a short time interval, the telnet service would become unavailable after inetd logs a "telnet/tcp server failing (looping), service terminated" error. NOTE: MIT krb5-appl is not supported upstream but is shipped by a few Linux distributions. The affected code was removed from the supported MIT Kerberos 5 (aka krb5) product many years ago, at version 1.8.

Remediation

Upgrade Debian:unstable inetutils to version 2:2.3-5 or higher.

References

NULL Pointer Dereference vulnerability report

high severity

CVE-2024-37370

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › krb5/libgssapi-krb5-2@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libk5crypto3@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libkrb5-3@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libkrb5support0@1.16-2

NVD Description

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

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

Remediation

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

References

CVE-2024-37370 vulnerability report

high severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › krb5/libgssapi-krb5-2@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libk5crypto3@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libkrb5-3@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libkrb5support0@1.16-2

NVD Description

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

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

Remediation

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

References

NULL Pointer Dereference vulnerability report

high severity

Uncontrolled Recursion

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › krb5/libgssapi-krb5-2@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libk5crypto3@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libkrb5-3@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libkrb5support0@1.16-2

NVD Description

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

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

Remediation

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

References

Uncontrolled Recursion vulnerability report

high severity

Information Exposure

  • Vulnerable module: libgcrypt20
  • Introduced through: libgcrypt20@1.8.1-4
  • Fixed in: 1.9.4-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libgcrypt20@1.8.1-4

NVD Description

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

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

Remediation

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

References

Information Exposure vulnerability report

high severity

Improper Input Validation

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libidn2/libidn2-0@2.0.4-1.1

NVD Description

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

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

Remediation

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

References

Improper Input Validation vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: libproxy/libproxy1v5
  • Introduced through: libproxy/libproxy1v5@0.4.15-1
  • Fixed in: 0.4.15-15

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libproxy/libproxy1v5@0.4.15-1

NVD Description

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

url::recvline in url.cpp in libproxy 0.4.x through 0.4.15 allows a remote HTTP server to trigger uncontrolled recursion via a response composed of an infinite stream that lacks a newline character. This leads to stack exhaustion.

Remediation

Upgrade Debian:unstable libproxy to version 0.4.15-15 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: libssh2/libssh2-1
  • Introduced through: libssh2/libssh2-1@1.8.0-1
  • Fixed in: 1.10.0-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libssh2/libssh2-1@1.8.0-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:unstable 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:unstable libssh2 to version 1.10.0-2 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-6@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-data@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-dev@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-doc@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-xcb1@2:1.6.5-1

NVD Description

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

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

Remediation

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

References

Out-of-bounds Write vulnerability report

high severity

Integer Overflow or Wraparound

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.9.14+dfsg-1.1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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:unstable 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:unstable libxml2 to version 2.9.14+dfsg-1.1 or higher.

References

Integer Overflow or Wraparound vulnerability report

high severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.9.10+dfsg-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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

parser.c in libxml2 before 2.9.5 does not prevent infinite recursion in parameter entities.

Remediation

Upgrade Debian:unstable libxml2 to version 2.9.10+dfsg-2 or higher.

References

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability report

high severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.9.10+dfsg-2.1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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

xmlStringLenDecodeEntities in parser.c in libxml2 2.9.10 has an infinite loop in a certain end-of-file situation.

Remediation

Upgrade Debian:unstable libxml2 to version 2.9.10+dfsg-2.1 or higher.

References

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability report

high severity

Memory Leak

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.9.10+dfsg-2.1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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

xmlSchemaPreRun in xmlschemas.c in libxml2 2.9.10 allows an xmlSchemaValidateStream memory leak.

Remediation

Upgrade Debian:unstable libxml2 to version 2.9.10+dfsg-2.1 or higher.

References

Memory Leak vulnerability report

high severity

Missing Release of Resource after Effective Lifetime

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.9.10+dfsg-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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

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

Remediation

Upgrade Debian:unstable libxml2 to version 2.9.10+dfsg-2 or higher.

References

Missing Release of Resource after Effective Lifetime vulnerability report

high severity

NULL Pointer Dereference

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.9.14+dfsg-1.3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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

Upgrade Debian:unstable libxml2 to version 2.9.14+dfsg-1.3 or higher.

References

NULL Pointer Dereference vulnerability report

high severity

NULL Pointer Dereference

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.12.7+dfsg+really2.9.14-0.4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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

libxml2 before 2.12.10 and 2.13.x before 2.13.6 has a NULL pointer dereference in xmlPatMatch in pattern.c.

Remediation

Upgrade Debian:unstable libxml2 to version 2.12.7+dfsg+really2.9.14-0.4 or higher.

References

NULL Pointer Dereference vulnerability report

high severity

Out-of-bounds Read

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.12.7+dfsg+really2.9.14-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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

In libxml2 before 2.13.8 and 2.14.x before 2.14.2, xmlSchemaIDCFillNodeTables in xmlschemas.c has a heap-based buffer under-read. To exploit this, a crafted XML document must be validated against an XML schema with certain identity constraints, or a crafted XML schema must be used.

Remediation

Upgrade Debian:unstable libxml2 to version 2.12.7+dfsg+really2.9.14-1 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.12.7+dfsg+really2.9.14-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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

A flaw was found in libxml2's xmlBuildQName function, where integer overflows in buffer size calculations can lead to a stack-based buffer overflow. This issue can result in memory corruption or a denial of service when processing crafted input.

Remediation

Upgrade Debian:unstable libxml2 to version 2.12.7+dfsg+really2.9.14-2 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Unchecked Return Value

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.12.7+dfsg+really2.9.14-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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

In libxml2 before 2.13.8 and 2.14.x before 2.14.2, out-of-bounds memory access can occur in the Python API (Python bindings) because of an incorrect return value. This occurs in xmlPythonFileRead and xmlPythonFileReadRaw because of a difference between bytes and characters.

Remediation

Upgrade Debian:unstable libxml2 to version 2.12.7+dfsg+really2.9.14-1 or higher.

References

Unchecked Return Value vulnerability report

high severity

Use After Free

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.9.13+dfsg-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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:unstable 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:unstable libxml2 to version 2.9.13+dfsg-1 or higher.

References

Use After Free vulnerability report

high severity

Use After Free

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.12.7+dfsg+really2.9.14-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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

Upgrade Debian:unstable libxml2 to version 2.12.7+dfsg+really2.9.14-1 or higher.

References

Use After Free vulnerability report

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.1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › 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:unstable 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:unstable libxpm to version 1:3.5.12-1.1 or higher.

References

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability report

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.1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › 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:unstable 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:unstable libxpm to version 1:3.5.12-1.1 or higher.

References

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability report

high severity

Improper Input Validation

  • Vulnerable module: mercurial
  • Introduced through: mercurial@4.5-1 and mercurial/mercurial-common@4.5-1
  • Fixed in: 4.6.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › mercurial@4.5-1
  • Introduced through: openjdk@10-ea-jdk › mercurial/mercurial-common@4.5-1

NVD Description

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

The mpatch_apply function in mpatch.c in Mercurial before 4.6.1 incorrectly proceeds in cases where the fragment start is past the end of the original data, aka OVE-20180430-0004.

Remediation

Upgrade Debian:unstable mercurial to version 4.6.1-1 or higher.

References

Improper Input Validation vulnerability report

high severity

Improper Input Validation

  • Vulnerable module: mercurial
  • Introduced through: mercurial@4.5-1 and mercurial/mercurial-common@4.5-1
  • Fixed in: 4.6.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › mercurial@4.5-1
  • Introduced through: openjdk@10-ea-jdk › mercurial/mercurial-common@4.5-1

NVD Description

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

The mpatch_decode function in mpatch.c in Mercurial before 4.6.1 mishandles certain situations where there should be at least 12 bytes remaining after the current position in the patch data, but actually are not, aka OVE-20180430-0001.

Remediation

Upgrade Debian:unstable mercurial to version 4.6.1-1 or higher.

References

Improper Input Validation vulnerability report

high severity

Improper Input Validation

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nettle/libhogweed4@3.4-1
  • Introduced through: openjdk@10-ea-jdk › nettle/libnettle6@3.4-1

NVD Description

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

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

Remediation

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

References

Improper Input Validation vulnerability report

high severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: nghttp2/libnghttp2-14
  • Introduced through: nghttp2/libnghttp2-14@1.31.0-1
  • Fixed in: 1.39.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nghttp2/libnghttp2-14@1.31.0-1

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

Some HTTP/2 implementations are vulnerable to window size manipulation and stream prioritization manipulation, potentially leading to a denial of service. The attacker requests a large amount of data from a specified resource over multiple streams. They manipulate window size and stream priority to force the server to queue the data in 1-byte chunks. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both.

Remediation

Upgrade Debian:unstable nghttp2 to version 1.39.2-1 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

high severity

CVE-2019-9513

  • Vulnerable module: nghttp2/libnghttp2-14
  • Introduced through: nghttp2/libnghttp2-14@1.31.0-1
  • Fixed in: 1.39.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nghttp2/libnghttp2-14@1.31.0-1

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

Some HTTP/2 implementations are vulnerable to resource loops, potentially leading to a denial of service. The attacker creates multiple request streams and continually shuffles the priority of the streams in a way that causes substantial churn to the priority tree. This can consume excess CPU.

Remediation

Upgrade Debian:unstable nghttp2 to version 1.39.2-1 or higher.

References

CVE-2019-9513 vulnerability report

high severity

CVE-2023-44487

  • Vulnerable module: nghttp2/libnghttp2-14
  • Introduced through: nghttp2/libnghttp2-14@1.31.0-1
  • Fixed in: 1.57.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nghttp2/libnghttp2-14@1.31.0-1

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

References

CVE-2023-44487 vulnerability report

high severity

Improper Enforcement of Message or Data Structure

  • Vulnerable module: nghttp2/libnghttp2-14
  • Introduced through: nghttp2/libnghttp2-14@1.31.0-1
  • Fixed in: 1.41.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nghttp2/libnghttp2-14@1.31.0-1

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

References

Improper Enforcement of Message or Data Structure vulnerability report

high severity

Allocation of Resources Without Limits or Throttling

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nss/libnss3@2:3.36.1-1

NVD Description

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

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

Remediation

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

References

Allocation of Resources Without Limits or Throttling vulnerability report

high severity

CVE-2022-3479

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nss/libnss3@2:3.36.1-1

NVD Description

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

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

Remediation

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

References

CVE-2022-3479 vulnerability report

high severity

Improper Certificate Validation

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nss/libnss3@2:3.36.1-1

NVD Description

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

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

Remediation

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

References

Improper Certificate Validation vulnerability report

high severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nss/libnss3@2:3.36.1-1

NVD Description

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

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

Remediation

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

References

Out-of-Bounds vulnerability report

high severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nss/libnss3@2:3.36.1-1

NVD Description

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

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

Remediation

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

References

Out-of-bounds Read vulnerability report

high severity

Unchecked Return Value

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nss/libnss3@2:3.36.1-1

NVD Description

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

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

Remediation

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

References

Unchecked Return Value vulnerability report

high severity

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

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1 and openldap/libldap-common@2.4.45+dfsg-1
  • Fixed in: 2.4.57+dfsg-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-2.4-2@2.4.45+dfsg-1
  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-common@2.4.45+dfsg-1

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

A flaw was discovered in ldap_X509dn2bv in OpenLDAP before 2.4.57 leading to a slapd crash in the X.509 DN parsing in ad_keystring, resulting in denial of service.

Remediation

Upgrade Debian:unstable openldap to version 2.4.57+dfsg-1 or higher.

References

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

high severity

CVE-2020-36226

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1 and openldap/libldap-common@2.4.45+dfsg-1
  • Fixed in: 2.4.57+dfsg-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-2.4-2@2.4.45+dfsg-1
  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-common@2.4.45+dfsg-1

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

A flaw was discovered in OpenLDAP before 2.4.57 leading to a memch->bv_len miscalculation and slapd crash in the saslAuthzTo processing, resulting in denial of service.

Remediation

Upgrade Debian:unstable openldap to version 2.4.57+dfsg-1 or higher.

References

CVE-2020-36226 vulnerability report

high severity

Double Free

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1 and openldap/libldap-common@2.4.45+dfsg-1
  • Fixed in: 2.4.57+dfsg-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-2.4-2@2.4.45+dfsg-1
  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-common@2.4.45+dfsg-1

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

A flaw was discovered in OpenLDAP before 2.4.57 leading to a double free and slapd crash in the saslAuthzTo processing, resulting in denial of service.

Remediation

Upgrade Debian:unstable openldap to version 2.4.57+dfsg-1 or higher.

References

Double Free vulnerability report

high severity

Integer Underflow

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1 and openldap/libldap-common@2.4.45+dfsg-1
  • Fixed in: 2.4.57+dfsg-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-2.4-2@2.4.45+dfsg-1
  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-common@2.4.45+dfsg-1

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

An integer underflow was discovered in OpenLDAP before 2.4.57 leading to slapd crashes in the Certificate Exact Assertion processing, resulting in denial of service (schema_init.c serialNumberAndIssuerCheck).

Remediation

Upgrade Debian:unstable openldap to version 2.4.57+dfsg-1 or higher.

References

Integer Underflow vulnerability report

high severity

Integer Underflow

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1 and openldap/libldap-common@2.4.45+dfsg-1
  • Fixed in: 2.4.57+dfsg-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-2.4-2@2.4.45+dfsg-1
  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-common@2.4.45+dfsg-1

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

An integer underflow was discovered in OpenLDAP before 2.4.57 leading to a slapd crash in the Certificate List Exact Assertion processing, resulting in denial of service.

Remediation

Upgrade Debian:unstable openldap to version 2.4.57+dfsg-1 or higher.

References

Integer Underflow vulnerability report

high severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1 and openldap/libldap-common@2.4.45+dfsg-1
  • Fixed in: 2.4.57+dfsg-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-2.4-2@2.4.45+dfsg-1
  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-common@2.4.45+dfsg-1

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

A flaw was discovered in OpenLDAP before 2.4.57 leading to an infinite loop in slapd with the cancel_extop Cancel operation, resulting in denial of service.

Remediation

Upgrade Debian:unstable openldap to version 2.4.57+dfsg-1 or higher.

References

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability report

high severity

NULL Pointer Dereference

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1 and openldap/libldap-common@2.4.45+dfsg-1
  • Fixed in: 2.4.55+dfsg-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-2.4-2@2.4.45+dfsg-1
  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-common@2.4.45+dfsg-1

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

A NULL pointer dereference was found in OpenLDAP server and was fixed in openldap 2.4.55, during a request for renaming RDNs. An unauthenticated attacker could remotely crash the slapd process by sending a specially crafted request, causing a Denial of Service.

Remediation

Upgrade Debian:unstable openldap to version 2.4.55+dfsg-1 or higher.

References

NULL Pointer Dereference vulnerability report

high severity

NULL Pointer Dereference

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1 and openldap/libldap-common@2.4.45+dfsg-1
  • Fixed in: 2.5.16+dfsg-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-2.4-2@2.4.45+dfsg-1
  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-common@2.4.45+dfsg-1

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

Upgrade Debian:unstable openldap to version 2.5.16+dfsg-1 or higher.

References

NULL Pointer Dereference vulnerability report

high severity

Out-of-bounds Read

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1 and openldap/libldap-common@2.4.45+dfsg-1
  • Fixed in: 2.4.57+dfsg-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-2.4-2@2.4.45+dfsg-1
  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-common@2.4.45+dfsg-1

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

A flaw was discovered in OpenLDAP before 2.4.57 leading to a slapd crash in the Values Return Filter control handling, resulting in denial of service (double free and out-of-bounds read).

Remediation

Upgrade Debian:unstable openldap to version 2.4.57+dfsg-1 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Reachable Assertion

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1 and openldap/libldap-common@2.4.45+dfsg-1
  • Fixed in: 2.4.56+dfsg-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-2.4-2@2.4.45+dfsg-1
  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-common@2.4.45+dfsg-1

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

A flaw was found in OpenLDAP. This flaw allows an attacker who can send a malicious packet to be processed by OpenLDAP’s slapd server, to trigger an assertion failure. The highest threat from this vulnerability is to system availability.

Remediation

Upgrade Debian:unstable openldap to version 2.4.56+dfsg-1 or higher.

References

Reachable Assertion vulnerability report

high severity

Reachable Assertion

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1 and openldap/libldap-common@2.4.45+dfsg-1
  • Fixed in: 2.4.56+dfsg-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-2.4-2@2.4.45+dfsg-1
  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-common@2.4.45+dfsg-1

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

A flaw was found in OpenLDAP in versions before 2.4.56. This flaw allows an attacker who sends a malicious packet processed by OpenLDAP to force a failed assertion in csnNormalize23(). The highest threat from this vulnerability is to system availability.

Remediation

Upgrade Debian:unstable openldap to version 2.4.56+dfsg-1 or higher.

References

Reachable Assertion vulnerability report

high severity

Reachable Assertion

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1 and openldap/libldap-common@2.4.45+dfsg-1
  • Fixed in: 2.4.57+dfsg-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-2.4-2@2.4.45+dfsg-1
  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-common@2.4.45+dfsg-1

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

A flaw was discovered in OpenLDAP before 2.4.57 leading to an assertion failure in slapd in the saslAuthzTo validation, resulting in denial of service.

Remediation

Upgrade Debian:unstable openldap to version 2.4.57+dfsg-1 or higher.

References

Reachable Assertion vulnerability report

high severity

Reachable Assertion

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1 and openldap/libldap-common@2.4.45+dfsg-1
  • Fixed in: 2.4.57+dfsg-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-2.4-2@2.4.45+dfsg-1
  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-common@2.4.45+dfsg-1

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

A flaw was discovered in OpenLDAP before 2.4.57 leading in an assertion failure in slapd in the X.509 DN parsing in decode.c ber_next_element, resulting in denial of service.

Remediation

Upgrade Debian:unstable openldap to version 2.4.57+dfsg-1 or higher.

References

Reachable Assertion vulnerability report

high severity

Reachable Assertion

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1 and openldap/libldap-common@2.4.45+dfsg-1
  • Fixed in: 2.4.57+dfsg-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-2.4-2@2.4.45+dfsg-1
  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-common@2.4.45+dfsg-1

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

In OpenLDAP through 2.4.57 and 2.5.x through 2.5.1alpha, an assertion failure in slapd can occur in the issuerAndThisUpdateCheck function via a crafted packet, resulting in a denial of service (daemon exit) via a short timestamp. This is related to schema_init.c and checkTime.

Remediation

Upgrade Debian:unstable openldap to version 2.4.57+dfsg-2 or higher.

References

Reachable Assertion vulnerability report

high severity

Release of Invalid Pointer or Reference

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1 and openldap/libldap-common@2.4.45+dfsg-1
  • Fixed in: 2.4.57+dfsg-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-2.4-2@2.4.45+dfsg-1
  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-common@2.4.45+dfsg-1

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

A flaw was discovered in OpenLDAP before 2.4.57 leading to an invalid pointer free and slapd crash in the saslAuthzTo processing, resulting in denial of service.

Remediation

Upgrade Debian:unstable openldap to version 2.4.57+dfsg-1 or higher.

References

Release of Invalid Pointer or Reference vulnerability report

high severity

Resource Exhaustion

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1 and openldap/libldap-common@2.4.45+dfsg-1
  • Fixed in: 2.4.50+dfsg-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-2.4-2@2.4.45+dfsg-1
  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-common@2.4.45+dfsg-1

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

In filter.c in slapd in OpenLDAP before 2.4.50, LDAP search filters with nested boolean expressions can result in denial of service (daemon crash).

Remediation

Upgrade Debian:unstable openldap to version 2.4.50+dfsg-1 or higher.

References

Resource Exhaustion vulnerability report

high severity

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

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

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

Issue summary: Applications performing certificate name checks (e.g., TLS clients checking server certificates) may attempt to read an invalid memory address resulting in abnormal termination of the application process.

Impact summary: Abnormal termination of an application can a cause a denial of service.

Applications performing certificate name checks (e.g., TLS clients checking server certificates) may attempt to read an invalid memory address when comparing the expected name with an otherName subject alternative name of an X.509 certificate. This may result in an exception that terminates the application program.

Note that basic certificate chain validation (signatures, dates, ...) is not affected, the denial of service can occur only when the application also specifies an expected DNS name, Email address or IP address.

TLS servers rarely solicit client certificates, and even when they do, they generally don't perform a name check against a reference identifier (expected identity), but rather extract the presented identity after checking the certificate chain. So TLS servers are generally not affected and the severity of the issue is Moderate.

The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.

Remediation

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

References

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

high severity

CVE-2023-5363

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

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

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

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

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

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

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

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

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

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

OpenSSL 3.1 and 3.0 are vulnerable to this issue.

Remediation

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

References

CVE-2023-5363 vulnerability report

high severity

Double Free

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

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

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

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

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

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

Remediation

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

References

Double Free vulnerability report

high severity

Improper Certificate Validation

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

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

A security vulnerability has been identified in all supported versions

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

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

Remediation

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

References

Improper Certificate Validation vulnerability report

high severity

Improper Locking

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

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

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

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

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

Remediation

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

References

Improper Locking vulnerability report

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

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

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

Remediation

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

References

Integer Overflow or Wraparound vulnerability report

high severity

Loop with Unreachable Exit Condition ('Infinite Loop')

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

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

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

Remediation

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

References

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability report

high severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

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

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

Remediation

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

References

NULL Pointer Dereference vulnerability report

high severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

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

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

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

Remediation

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

References

NULL Pointer Dereference vulnerability report

high severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

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

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

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

Remediation

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

References

NULL Pointer Dereference vulnerability report

high severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

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

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

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

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

Remediation

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

References

NULL Pointer Dereference vulnerability report

high severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

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

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

Remediation

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

References

NULL Pointer Dereference vulnerability report

high severity

Use After Free

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

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

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

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

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

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

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

Remediation

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

References

Use After Free vulnerability report

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › p11-kit/libp11-kit0@0.23.9-2

NVD Description

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

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

Remediation

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

References

Integer Overflow or Wraparound vulnerability report

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › p11-kit/libp11-kit0@0.23.9-2

NVD Description

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

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

Remediation

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

References

Out-of-bounds Write vulnerability report

high severity

Out-of-bounds Read

  • Vulnerable module: pcre2/libpcre2-8-0
  • Introduced through: pcre2/libpcre2-8-0@10.31-3
  • Fixed in: 10.34-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › pcre2/libpcre2-8-0@10.31-3

NVD Description

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

An out-of-bounds read was discovered in PCRE before 10.34 when the pattern \X is JIT compiled and used to match specially crafted subjects in non-UTF mode. Applications that use PCRE to parse untrusted input may be vulnerable to this flaw, which would allow an attacker to crash the application. The flaw occurs in do_extuni_no_utf in pcre2_jit_compile.c.

Remediation

Upgrade Debian:unstable pcre2 to version 10.34-1 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Buffer Overflow

  • Vulnerable module: perl
  • Introduced through: perl@5.26.1-5, perl/libperl5.26@5.26.1-5 and others
  • Fixed in: 5.30.3-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › perl@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/libperl5.26@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-base@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-modules-5.26@5.26.1-5

NVD Description

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

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

Remediation

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

References

Buffer Overflow vulnerability report

high severity

Link Following

  • Vulnerable module: perl
  • Introduced through: perl@5.26.1-5, perl/libperl5.26@5.26.1-5 and others
  • Fixed in: 5.26.2-6

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › perl@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/libperl5.26@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-base@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-modules-5.26@5.26.1-5

NVD Description

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

In Perl through 5.26.2, the Archive::Tar module allows remote attackers to bypass a directory-traversal protection mechanism, and overwrite arbitrary files, via an archive file containing a symlink and a regular file with the same name.

Remediation

Upgrade Debian:unstable perl to version 5.26.2-6 or higher.

References

Link Following vulnerability report

high severity

Out-of-bounds Read

  • Vulnerable module: perl
  • Introduced through: perl@5.26.1-5, perl/libperl5.26@5.26.1-5 and others
  • Fixed in: 5.26.1-6

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › perl@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/libperl5.26@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-base@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-modules-5.26@5.26.1-5

NVD Description

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

An issue was discovered in Perl 5.22 through 5.26. Matching a crafted locale dependent regular expression can cause a heap-based buffer over-read and potentially information disclosure.

Remediation

Upgrade Debian:unstable perl to version 5.26.1-6 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Heap-based Buffer Overflow

  • Vulnerable module: procps
  • Introduced through: procps@2:3.3.12-4 and procps/libprocps6@2:3.3.12-4
  • Fixed in: 2:3.3.15-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › procps@2:3.3.12-4
  • Introduced through: openjdk@10-ea-jdk › procps/libprocps6@2:3.3.12-4

NVD Description

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

procps-ng before version 3.3.15 is vulnerable to a denial of service in ps via mmap buffer overflow. Inbuilt protection in ps maps a guard page at the end of the overflowed buffer, ensuring that the impact of this flaw is limited to a crash (temporary denial of service).

Remediation

Upgrade Debian:unstable procps to version 2:3.3.15-1 or higher.

References

Heap-based Buffer Overflow vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: procps
  • Introduced through: procps@2:3.3.12-4 and procps/libprocps6@2:3.3.12-4
  • Fixed in: 2:3.3.15-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › procps@2:3.3.12-4
  • Introduced through: openjdk@10-ea-jdk › procps/libprocps6@2:3.3.12-4

NVD Description

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

procps-ng before version 3.3.15 is vulnerable to a stack buffer overflow in pgrep. This vulnerability is mitigated by FORTIFY, as it involves strncat() to a stack-allocated string. When pgrep is compiled with FORTIFY (as on Red Hat Enterprise Linux and Fedora), the impact is limited to a crash.

Remediation

Upgrade Debian:unstable procps to version 2:3.3.15-1 or higher.

References

Out-of-bounds Write vulnerability report

high severity

CVE-2019-19603

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

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

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

Remediation

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

References

CVE-2019-19603 vulnerability report

high severity

CVE-2019-19959

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

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

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

Remediation

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

References

CVE-2019-19959 vulnerability report

high severity

Improper Handling of Exceptional Conditions

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

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

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

Remediation

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

References

Improper Handling of Exceptional Conditions vulnerability report

high severity

Improper Initialization

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

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

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

Remediation

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

References

Improper Initialization vulnerability report

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

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

In SQLite 3.44.0 through 3.49.0 before 3.49.1, the concat_ws() SQL function can cause memory to be written beyond the end of a malloc-allocated buffer. If the separator argument is attacker-controlled and has a large string (e.g., 2MB or more), an integer overflow occurs in calculating the size of the result buffer, and thus malloc may not allocate enough memory.

Remediation

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

References

Integer Overflow or Wraparound vulnerability report

high severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

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

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

Remediation

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

References

NULL Pointer Dereference vulnerability report

high severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

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

In SQLite through 3.22.0, databases whose schema is corrupted using a CREATE TABLE AS statement could cause a NULL pointer dereference, related to build.c and prepare.c.

Remediation

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

References

NULL Pointer Dereference vulnerability report

high severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

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

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

Remediation

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

References

NULL Pointer Dereference vulnerability report

high severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

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

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

Remediation

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

References

NULL Pointer Dereference vulnerability report

high severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

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

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

Remediation

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

References

NULL Pointer Dereference vulnerability report

high severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

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

An issue found in SQLite SQLite3 v.3.35.4 that allows a remote attacker to cause a denial of service via the appendvfs.c function.

Remediation

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

References

Out-of-bounds Read vulnerability report

high severity

SQL Injection

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

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

SQLite 3.25.2, when queries are run on a table with a malformed PRIMARY KEY, allows remote attackers to cause a denial of service (application crash) by leveraging the ability to run arbitrary SQL statements (such as in certain WebSQL use cases).

Remediation

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

References

SQL Injection vulnerability report

high severity

Unrestricted Upload of File with Dangerous Type

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

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

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

Remediation

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

References

Unrestricted Upload of File with Dangerous Type vulnerability report

high severity

Use After Free

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

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

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

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

Remediation

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

References

Use After Free vulnerability report

high severity

Access of Uninitialized Pointer

  • Vulnerable module: subversion
  • Introduced through: subversion@1.9.7-4 and subversion/libsvn1@1.9.7-4
  • Fixed in: 1.10.4-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › subversion@1.9.7-4
  • Introduced through: openjdk@10-ea-jdk › subversion/libsvn1@1.9.7-4

NVD Description

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

Subversion's mod_dav_svn Apache HTTPD module versions 1.11.0 and 1.10.0 to 1.10.3 will crash after dereferencing an uninitialized pointer if the client omits the root path in a recursive directory listing operation.

Remediation

Upgrade Debian:unstable subversion to version 1.10.4-1 or higher.

References

Access of Uninitialized Pointer vulnerability report

high severity

Improper Input Validation

  • Vulnerable module: subversion
  • Introduced through: subversion@1.9.7-4 and subversion/libsvn1@1.9.7-4
  • Fixed in: 1.10.6-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › subversion@1.9.7-4
  • Introduced through: openjdk@10-ea-jdk › subversion/libsvn1@1.9.7-4

NVD Description

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

In Apache Subversion versions up to and including 1.9.10, 1.10.4, 1.12.0, Subversion's svnserve server process may exit when a client sends certain sequences of protocol commands. This can lead to disruption for users of the server.

Remediation

Upgrade Debian:unstable subversion to version 1.10.6-1 or higher.

References

Improper Input Validation vulnerability report

high severity

NULL Pointer Dereference

  • Vulnerable module: subversion
  • Introduced through: subversion@1.9.7-4 and subversion/libsvn1@1.9.7-4
  • Fixed in: 1.14.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › subversion@1.9.7-4
  • Introduced through: openjdk@10-ea-jdk › subversion/libsvn1@1.9.7-4

NVD Description

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

Subversion's mod_authz_svn module will crash if the server is using in-repository authz rules with the AuthzSVNReposRelativeAccessFile option and a client sends a request for a non-existing repository URL. This can lead to disruption for users of the service. This issue was fixed in mod_dav_svn+mod_authz_svn servers 1.14.1 and mod_dav_svn+mod_authz_svn servers 1.10.7

Remediation

Upgrade Debian:unstable subversion to version 1.14.1-1 or higher.

References

NULL Pointer Dereference vulnerability report

high severity

Use After Free

  • Vulnerable module: subversion
  • Introduced through: subversion@1.9.7-4 and subversion/libsvn1@1.9.7-4
  • Fixed in: 1.14.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › subversion@1.9.7-4
  • Introduced through: openjdk@10-ea-jdk › subversion/libsvn1@1.9.7-4

NVD Description

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

Subversion's mod_dav_svn is vulnerable to memory corruption. While looking up path-based authorization rules, mod_dav_svn servers may attempt to use memory which has already been freed. Affected Subversion mod_dav_svn servers 1.10.0 through 1.14.1 (inclusive). Servers that do not use mod_dav_svn are not affected.

Remediation

Upgrade Debian:unstable subversion to version 1.14.2-1 or higher.

References

Use After Free vulnerability report

high severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: systemd
  • Introduced through: systemd@238-4, systemd/libnss-systemd@238-4 and others
  • Fixed in: 255.4-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libnss-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libpam-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libsystemd0@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libudev1@238-2
  • Introduced through: openjdk@10-ea-jdk › systemd/systemd-sysv@238-4

NVD Description

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

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

Remediation

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

References

Allocation of Resources Without Limits or Throttling vulnerability report

high severity

CVE-2023-50868

  • Vulnerable module: systemd
  • Introduced through: systemd@238-4, systemd/libnss-systemd@238-4 and others
  • Fixed in: 255.4-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libnss-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libpam-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libsystemd0@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libudev1@238-2
  • Introduced through: openjdk@10-ea-jdk › systemd/systemd-sysv@238-4

NVD Description

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

The Closest Encloser Proof aspect of the DNS protocol (in RFC 5155 when RFC 9276 guidance is skipped) allows remote attackers to cause a denial of service (CPU consumption for SHA-1 computations) via DNSSEC responses in a random subdomain attack, aka the "NSEC3" issue. The RFC 5155 specification implies that an algorithm must perform thousands of iterations of a hash function in certain situations.

Remediation

Upgrade Debian:unstable systemd to version 255.4-1 or higher.

References

CVE-2023-50868 vulnerability report

high severity

NULL Pointer Dereference

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.5.1+git230720-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable relevant fixed versions and status.

A null pointer dereference flaw was found in Libtiff via tif_dirinfo.c. This issue may allow an attacker to trigger memory allocation failures through certain means, such as restricting the heap space size or injecting faults, causing a segmentation fault. This can cause an application crash, eventually leading to a denial of service.

Remediation

Upgrade Debian:unstable tiff to version 4.5.1+git230720-5 or higher.

References

NULL Pointer Dereference vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.0.10+git190814-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable relevant fixed versions and status.

Buffer Overflow in LibTiff v4.0.10 allows attackers to cause a denial of service via the "invertImage()" function in the component "tiffcrop".

Remediation

Upgrade Debian:unstable tiff to version 4.0.10+git190814-1 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.5.1+git230720-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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

Upgrade Debian:unstable tiff to version 4.5.1+git230720-4 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.5.1+git230720-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.5.1+git230720-4 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: zlib/zlib1g
  • Introduced through: zlib/zlib1g@1:1.2.8.dfsg-5
  • Fixed in: 1:1.2.11.dfsg-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › zlib/zlib1g@1:1.2.8.dfsg-5

NVD Description

Note: Versions mentioned in the description apply only to the upstream zlib package and not the zlib package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

zlib before 1.2.12 allows memory corruption when deflating (i.e., when compressing) if the input has many distant matches.

Remediation

Upgrade Debian:unstable zlib to version 1:1.2.11.dfsg-4 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Information Exposure

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.18-1
  • Fixed in: 3.7.8-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gnutls28/libgnutls30@3.5.18-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A timing side-channel in the handling of RSA ClientKeyExchange messages was discovered in GnuTLS. This side-channel can be sufficient to recover the key encrypted in the RSA ciphertext across a network in a Bleichenbacher style attack. To achieve a successful decryption the attacker would need to send a large amount of specially crafted messages to the vulnerable server. By recovering the secret from the ClientKeyExchange message, the attacker would be able to decrypt the application data exchanged over that connection.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.7.8-5 or higher.

References

Information Exposure vulnerability report

high severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.18-1
  • Fixed in: 3.6.13-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gnutls28/libgnutls30@3.5.18-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

GnuTLS 3.6.x before 3.6.13 uses incorrect cryptography for DTLS. The earliest affected version is 3.6.3 (2018-07-16) because of an error in a 2017-10-06 commit. The DTLS client always uses 32 '\0' bytes instead of a random value, and thus contributes no randomness to a DTLS negotiation. This breaks the security guarantees of the DTLS protocol.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.6.13-2 or higher.

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

high severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.18-1
  • Fixed in: 3.6.14-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gnutls28/libgnutls30@3.5.18-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

GnuTLS 3.6.x before 3.6.14 uses incorrect cryptography for encrypting a session ticket (a loss of confidentiality in TLS 1.2, and an authentication bypass in TLS 1.3). The earliest affected version is 3.6.4 (2018-09-24) because of an error in a 2018-09-18 commit. Until the first key rotation, the TLS server always uses wrong data in place of an encryption key derived from an application.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.6.14-1 or higher.

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

high severity

Access of Resource Using Incompatible Type ('Type Confusion')

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 3.0.8-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING.

When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network.

Remediation

Upgrade Debian:unstable openssl to version 3.0.8-1 or higher.

References

Access of Resource Using Incompatible Type ('Type Confusion') vulnerability report

high severity

Improper Certificate Validation

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 1.1.1k-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The X509_V_FLAG_X509_STRICT flag enables additional security checks of the certificates present in a certificate chain. It is not set by default. Starting from OpenSSL version 1.1.1h a check to disallow certificates in the chain that have explicitly encoded elliptic curve parameters was added as an additional strict check. An error in the implementation of this check meant that the result of a previous check to confirm that certificates in the chain are valid CA certificates was overwritten. This effectively bypasses the check that non-CA certificates must not be able to issue other certificates. If a "purpose" has been configured then there is a subsequent opportunity for checks that the certificate is a valid CA. All of the named "purpose" values implemented in libcrypto perform this check. Therefore, where a purpose is set the certificate chain will still be rejected even when the strict flag has been used. A purpose is set by default in libssl client and server certificate verification routines, but it can be overridden or removed by an application. In order to be affected, an application must explicitly set the X509_V_FLAG_X509_STRICT verification flag and either not set a purpose for the certificate verification or, in the case of TLS client or server applications, override the default purpose. OpenSSL versions 1.1.1h and newer are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1h-1.1.1j).

Remediation

Upgrade Debian:unstable openssl to version 1.1.1k-1 or higher.

References

Improper Certificate Validation vulnerability report

high severity

Out-of-bounds Read

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 1.1.1l-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not a strict requirement, ASN.1 strings that are parsed using OpenSSL's own "d2i" functions (and other similar parsing functions) as well as any string whose value has been set with the ASN1_STRING_set() function will additionally NUL terminate the byte array in the ASN1_STRING structure. However, it is possible for applications to directly construct valid ASN1_STRING structures which do not NUL terminate the byte array by directly setting the "data" and "length" fields in the ASN1_STRING array. This can also happen by using the ASN1_STRING_set0() function. Numerous OpenSSL functions that print ASN.1 data have been found to assume that the ASN1_STRING byte array will be NUL terminated, even though this is not guaranteed for strings that have been directly constructed. Where an application requests an ASN.1 structure to be printed, and where that ASN.1 structure contains ASN1_STRINGs that have been directly constructed by the application without NUL terminating the "data" field, then a read buffer overrun can occur. The same thing can also occur during name constraints processing of certificates (for example if a certificate has been directly constructed by the application instead of loading it via the OpenSSL parsing functions, and the certificate contains non NUL terminated ASN1_STRING structures). It can also occur in the X509_get1_email(), X509_REQ_get1_email() and X509_get1_ocsp() functions. If a malicious actor can cause an application to directly construct an ASN1_STRING and then process it through one of the affected OpenSSL functions then this issue could be hit. This might result in a crash (causing a Denial of Service attack). It could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext). Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k). Fixed in OpenSSL 1.0.2za (Affected 1.0.2-1.0.2y).

Remediation

Upgrade Debian:unstable openssl to version 1.1.1l-1 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Improper Authentication

  • Vulnerable module: pam/libpam-modules
  • Introduced through: pam/libpam-modules@1.1.8-3.7, pam/libpam-modules-bin@1.1.8-3.7 and others
  • Fixed in: 1.7.0-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › pam/libpam-modules@1.1.8-3.7
  • Introduced through: openjdk@10-ea-jdk › pam/libpam-modules-bin@1.1.8-3.7
  • Introduced through: openjdk@10-ea-jdk › pam/libpam-runtime@1.1.8-3.7
  • Introduced through: openjdk@10-ea-jdk › pam/libpam0g@1.1.8-3.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream pam package and not the pam package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw was found in pam_access, where certain rules in its configuration file are mistakenly treated as hostnames. This vulnerability allows attackers to trick the system by pretending to be a trusted hostname, gaining unauthorized access. This issue poses a risk for systems that rely on this feature to control who can access certain services or terminals.

Remediation

Upgrade Debian:unstable pam to version 1.7.0-5 or higher.

References

Improper Authentication vulnerability report

high severity

OS Command Injection

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 1.1.1o-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The c_rehash script does not properly sanitise shell metacharacters to prevent command injection. This script is distributed by some operating systems in a manner where it is automatically executed. On such operating systems, an attacker could execute arbitrary commands with the privileges of the script. Use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool. Fixed in OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2). Fixed in OpenSSL 1.1.1o (Affected 1.1.1-1.1.1n). Fixed in OpenSSL 1.0.2ze (Affected 1.0.2-1.0.2zd).

Remediation

Upgrade Debian:unstable openssl to version 1.1.1o-1 or higher.

References

OS Command Injection vulnerability report

high severity

OS Command Injection

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 3.0.4-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In addition to the c_rehash shell command injection identified in CVE-2022-1292, further circumstances where the c_rehash script does not properly sanitise shell metacharacters to prevent command injection were found by code review. When the CVE-2022-1292 was fixed it was not discovered that there are other places in the script where the file names of certificates being hashed were possibly passed to a command executed through the shell. This script is distributed by some operating systems in a manner where it is automatically executed. On such operating systems, an attacker could execute arbitrary commands with the privileges of the script. Use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool. Fixed in OpenSSL 3.0.4 (Affected 3.0.0,3.0.1,3.0.2,3.0.3). Fixed in OpenSSL 1.1.1p (Affected 1.1.1-1.1.1o). Fixed in OpenSSL 1.0.2zf (Affected 1.0.2-1.0.2ze).

Remediation

Upgrade Debian:unstable openssl to version 3.0.4-1 or higher.

References

OS Command Injection vulnerability report

high severity

CVE-2022-46908

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1
  • Fixed in: 3.40.0-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

SQLite through 3.40.0, when relying on --safe for execution of an untrusted CLI script, does not properly implement the azProhibitedFunctions protection mechanism, and instead allows UDF functions such as WRITEFILE.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.40.0-2 or higher.

References

CVE-2022-46908 vulnerability report

high severity

Out-of-Bounds

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1
  • Fixed in: 3.43.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A vulnerability was found in SQLite SQLite3 up to 3.43.0 and classified as critical. This issue affects the function sessionReadRecord of the file ext/session/sqlite3session.c of the component make alltest Handler. The manipulation leads to heap-based buffer overflow. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-248999.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.43.1-1 or higher.

References

Out-of-Bounds vulnerability report

high severity

Out-of-bounds Read

  • Vulnerable module: apr/libapr1
  • Introduced through: apr/libapr1@1.6.3-2
  • Fixed in: 1.7.0-7

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › apr/libapr1@1.6.3-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream apr package and not the apr package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An out-of-bounds array read in the apr_time_exp*() functions was fixed in the Apache Portable Runtime 1.6.3 release (CVE-2017-12613). The fix for this issue was not carried forward to the APR 1.7.x branch, and hence version 1.7.0 regressed compared to 1.6.3 and is vulnerable to the same issue.

Remediation

Upgrade Debian:unstable apr to version 1.7.0-7 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Use After Free

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.7-3
  • Fixed in: 2.4.2-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › cups/libcups2@2.2.7-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream cups package and not the cups package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

OpenPrinting CUPS is a standards-based, open source printing system for Linux and other Unix-like operating systems. Starting in version 2.0.0 and prior to version 2.4.6, CUPS logs data of free memory to the logging service AFTER the connection has been closed, when it should have logged the data right before. This is a use-after-free bug that impacts the entire cupsd process.

The exact cause of this issue is the function httpClose(con-&gt;http) being called in scheduler/client.c. The problem is that httpClose always, provided its argument is not null, frees the pointer at the end of the call, only for cupsdLogClient to pass the pointer to httpGetHostname. This issue happens in function cupsdAcceptClient if LogLevel is warn or higher and in two scenarios: there is a double-lookup for the IP Address (HostNameLookups Double is set in cupsd.conf) which fails to resolve, or if CUPS is compiled with TCP wrappers and the connection is refused by rules from /etc/hosts.allow and /etc/hosts.deny.

Version 2.4.6 has a patch for this issue.

Remediation

Upgrade Debian:unstable cups to version 2.4.2-5 or higher.

References

Use After Free vulnerability report

high severity

Link Following

  • Vulnerable module: dbus
  • Introduced through: dbus@1.12.6-2, dbus/dbus-user-session@1.12.6-2 and others
  • Fixed in: 1.12.16-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › dbus@1.12.6-2
  • Introduced through: openjdk@10-ea-jdk › dbus/dbus-user-session@1.12.6-2
  • Introduced through: openjdk@10-ea-jdk › dbus/libdbus-1-3@1.12.6-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream dbus package and not the dbus package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

dbus before 1.10.28, 1.12.x before 1.12.16, and 1.13.x before 1.13.12, as used in DBusServer in Canonical Upstart in Ubuntu 14.04 (and in some, less common, uses of dbus-daemon), allows cookie spoofing because of symlink mishandling in the reference implementation of DBUS_COOKIE_SHA1 in the libdbus library. (This only affects the DBUS_COOKIE_SHA1 authentication mechanism.) A malicious client with write access to its own home directory could manipulate a ~/.dbus-keyrings symlink to cause a DBusServer with a different uid to read and write in unintended locations. In the worst case, this could result in the DBusServer reusing a cookie that is known to the malicious client, and treating that cookie as evidence that a subsequent client connection came from an attacker-chosen uid, allowing authentication bypass.

Remediation

Upgrade Debian:unstable dbus to version 1.12.16-1 or higher.

References

Link Following vulnerability report

high severity

CVE-2024-32021

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.45.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, when cloning a local source repository that contains symlinks via the filesystem, Git may create hardlinks to arbitrary user-readable files on the same filesystem as the target repository in the objects/ directory. Cloning a local repository over the filesystem may creating hardlinks to arbitrary user-owned files on the same filesystem in the target Git repository's objects/ directory. When cloning a repository over the filesystem (without explicitly specifying the file:// protocol or --no-local), the optimizations for local cloning will be used, which include attempting to hard link the object files instead of copying them. While the code includes checks against symbolic links in the source repository, which were added during the fix for CVE-2022-39253, these checks can still be raced because the hard link operation ultimately follows symlinks. If the object on the filesystem appears as a file during the check, and then a symlink during the operation, this will allow the adversary to bypass the check and create hardlinks in the destination objects directory to arbitrary, user-readable files. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4.

Remediation

Upgrade Debian:unstable git to version 1:2.45.1-1 or higher.

References

CVE-2024-32021 vulnerability report

high severity

Out-of-bounds Read

  • Vulnerable module: ncurses/libncurses5
  • Introduced through: ncurses/libncurses5@6.1-1, ncurses/libncursesw5@6.1-1 and others
  • Fixed in: 6.3+20220423-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › ncurses/libncurses5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/libncursesw5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/libtinfo5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/ncurses-base@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/ncurses-bin@6.1-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

ncurses 6.3 before patch 20220416 has an out-of-bounds read and segmentation violation in convert_strings in tinfo/read_entry.c in the terminfo library.

Remediation

Upgrade Debian:unstable ncurses to version 6.3+20220423-1 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Double Free

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:7.6p1-4
  • Fixed in: 1:8.4p1-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssh/openssh-client@1:7.6p1-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

ssh-agent in OpenSSH before 8.5 has a double free that may be relevant in a few less-common scenarios, such as unconstrained agent-socket access on a legacy operating system, or the forwarding of an agent to an attacker-controlled host.

Remediation

Upgrade Debian:unstable openssh to version 1:8.4p1-5 or higher.

References

Double Free vulnerability report

high severity

Buffer Overflow

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 3.0.7-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed the malicious certificate or for the application to continue certificate verification despite failure to construct a path to a trusted issuer.

An attacker can craft a malicious email address to overflow an arbitrary number of bytes containing the . character (decimal 46) on the stack. This buffer overflow could result in a crash (causing a denial of service).

Remediation

Upgrade Debian:unstable openssl to version 3.0.7-1 or higher.

References

Buffer Overflow vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.3.0-6

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.3.0-6 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.7-3
  • Fixed in: 2.4.2-6

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › cups/libcups2@2.2.7-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream cups package and not the cups package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Due to failure in validating the length provided by an attacker-crafted PPD PostScript document, CUPS and libppd are susceptible to a heap-based buffer overflow and possibly code execution. This issue has been fixed in CUPS version 2.4.7, released in September of 2023.

Remediation

Upgrade Debian:unstable cups to version 2.4.2-6 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2
  • Fixed in: 2.30-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An out-of-bounds write vulnerability was found in glibc before 2.31 when handling signal trampolines on PowerPC. Specifically, the backtrace function did not properly check the array bounds when storing the frame address, resulting in a denial of service or potential code execution. The highest threat from this vulnerability is to system availability.

Remediation

Upgrade Debian:unstable glibc to version 2.30-3 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Use After Free

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2
  • Fixed in: 2.30-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A use-after-free vulnerability introduced in glibc upstream version 2.14 was found in the way the tilde expansion was carried out. Directory paths containing an initial tilde followed by a valid username were affected by this issue. A local attacker could exploit this flaw by creating a specially crafted path that, when processed by the glob function, would potentially lead to arbitrary code execution. This was fixed in version 2.32.

Remediation

Upgrade Debian:unstable glibc to version 2.30-3 or higher.

References

Use After Free vulnerability report

high severity
new

Out-of-bounds Write

  • Vulnerable module: gnupg2/dirmngr
  • Introduced through: gnupg2/dirmngr@2.2.5-1, gnupg2/gnupg@2.2.5-1 and others
  • Fixed in: 2.4.8-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gnupg2/dirmngr@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gnupg@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gnupg-l10n@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gnupg-utils@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpg@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpg-agent@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpg-wks-client@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpg-wks-server@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpgconf@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpgsm@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpgv@2.2.5-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream gnupg2 package and not the gnupg2 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In GnuPG before 2.4.9, armor_filter in g10/armor.c has two increments of an index variable where one is intended, leading to an out-of-bounds write for crafted input. (For ExtendedLTS, 2.2.51 and later are fixed versions.)

Remediation

Upgrade Debian:unstable gnupg2 to version 2.4.8-5 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Buffer Overflow

  • Vulnerable module: icu/libicu57
  • Introduced through: icu/libicu57@57.1-9
  • Fixed in: 76.1-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › icu/libicu57@57.1-9

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:unstable relevant fixed versions and status.

A stack buffer overflow was found in Internationl components for unicode (ICU ). While running the genrb binary, the 'subtag' struct overflowed at the SRBRoot::addTag function. This issue may lead to memory corruption and local arbitrary code execution.

Remediation

Upgrade Debian:unstable icu to version 76.1-4 or higher.

References

Buffer Overflow vulnerability report

high severity

Improper Privilege Management

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:7.6p1-4
  • Fixed in: 1:8.7p1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssh/openssh-client@1:7.6p1-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

sshd in OpenSSH 6.2 through 8.x before 8.8, when certain non-default configurations are used, allows privilege escalation because supplemental groups are not initialized as expected. Helper programs for AuthorizedKeysCommand and AuthorizedPrincipalsCommand may run with privileges associated with group memberships of the sshd process, if the configuration specifies running the command as a different user.

Remediation

Upgrade Debian:unstable openssh to version 1:8.7p1-1 or higher.

References

Improper Privilege Management vulnerability report

high severity

Inclusion of Functionality from Untrusted Control Sphere

  • Vulnerable module: procps
  • Introduced through: procps@2:3.3.12-4 and procps/libprocps6@2:3.3.12-4
  • Fixed in: 2:3.3.15-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › procps@2:3.3.12-4
  • Introduced through: openjdk@10-ea-jdk › procps/libprocps6@2:3.3.12-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream procps package and not the procps package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

procps-ng before version 3.3.15 is vulnerable to a local privilege escalation in top. If a user runs top with HOME unset in an attacker-controlled directory, the attacker could achieve privilege escalation by exploiting one of several vulnerabilities in the config_file() function.

Remediation

Upgrade Debian:unstable procps to version 2:3.3.15-1 or higher.

References

Inclusion of Functionality from Untrusted Control Sphere vulnerability report

high severity

Use After Free

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1
  • Fixed in: 3.32.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

ext/fts3/fts3.c in SQLite before 3.32.0 has a use-after-free in fts3EvalNextRow, related to the snippet feature.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.32.0-1 or higher.

References

Use After Free vulnerability report

high severity

Improper Authorization

  • Vulnerable module: systemd
  • Introduced through: systemd@238-4, systemd/libnss-systemd@238-4 and others
  • Fixed in: 241-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libnss-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libpam-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libsystemd0@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libudev1@238-2
  • Introduced through: openjdk@10-ea-jdk › systemd/systemd-sysv@238-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In systemd before v242-rc4, it was discovered that pam_systemd does not properly sanitize the environment before using the XDG_SEAT variable. It is possible for an attacker, in some particular configurations, to set a XDG_SEAT environment variable which allows for commands to be checked against polkit policies using the "allow_active" element rather than "allow_any".

Remediation

Upgrade Debian:unstable systemd to version 241-3 or higher.

References

Improper Authorization vulnerability report

high severity

Race Condition

  • Vulnerable module: systemd
  • Introduced through: systemd@238-4, systemd/libnss-systemd@238-4 and others
  • Fixed in: 239-11

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libnss-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libpam-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libsystemd0@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libudev1@238-2
  • Introduced through: openjdk@10-ea-jdk › systemd/systemd-sysv@238-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A race condition in chown_one() of systemd allows an attacker to cause systemd to set arbitrary permissions on arbitrary files. Affected releases are systemd versions up to and including 239.

Remediation

Upgrade Debian:unstable systemd to version 239-11 or higher.

References

Race Condition vulnerability report

medium severity

Detection of Error Condition Without Action

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:7.6p1-4
  • Fixed in: 1:9.9p2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssh/openssh-client@1:7.6p1-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A vulnerability was found in OpenSSH when the VerifyHostKeyDNS option is enabled. A machine-in-the-middle attack can be performed by a malicious machine impersonating a legit server. This issue occurs due to how OpenSSH mishandles error codes in specific conditions when verifying the host key. For an attack to be considered successful, the attacker needs to manage to exhaust the client's memory resource first, turning the attack complexity high.

Remediation

Upgrade Debian:unstable openssh to version 1:9.9p2-1 or higher.

References

Detection of Error Condition Without Action vulnerability report

medium severity

Improper Encoding or Escaping of Output

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:7.6p1-4
  • Fixed in: 1:7.9p1-6

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssh/openssh-client@1:7.6p1-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An issue was discovered in OpenSSH 7.9. Due to missing character encoding in the progress display, a malicious server (or Man-in-The-Middle attacker) can employ crafted object names to manipulate the client output, e.g., by using ANSI control codes to hide additional files being transferred. This affects refresh_progress_meter() in progressmeter.c.

Remediation

Upgrade Debian:unstable openssh to version 1:7.9p1-6 or higher.

References

Improper Encoding or Escaping of Output vulnerability report

medium severity

Buffer Underflow

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.7-3
  • Fixed in: 2.4.15-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › cups/libcups2@2.2.7-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream cups package and not the cups package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

OpenPrinting CUPS is an open source printing system for Linux and other Unix-like operating systems. Prior to version 2.4.15, a user in the lpadmin group can use the cups web ui to change the config and insert a malicious line. Then the cupsd process which runs as root will parse the new config and cause an out-of-bound write. This issue has been patched in version 2.4.15.

Remediation

Upgrade Debian:unstable cups to version 2.4.15-1 or higher.

References

Buffer Underflow vulnerability report

medium severity

CVE-2024-35235

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.7-3
  • Fixed in: 2.4.7-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › cups/libcups2@2.2.7-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream cups package and not the cups package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

OpenPrinting CUPS is an open source printing system for Linux and other Unix-like operating systems. In versions 2.4.8 and earlier, when starting the cupsd server with a Listen configuration item pointing to a symbolic link, the cupsd process can be caused to perform an arbitrary chmod of the provided argument, providing world-writable access to the target. Given that cupsd is often running as root, this can result in the change of permission of any user or system files to be world writable. Given the aforementioned Ubuntu AppArmor context, on such systems this vulnerability is limited to those files modifiable by the cupsd process. In that specific case it was found to be possible to turn the configuration of the Listen argument into full control over the cupsd.conf and cups-files.conf configuration files. By later setting the User and Group arguments in cups-files.conf, and printing with a printer configured by PPD with a FoomaticRIPCommandLine argument, arbitrary user and group (not root) command execution could be achieved, which can further be used on Ubuntu systems to achieve full root command execution. Commit ff1f8a623e090dee8a8aadf12a6a4b25efac143d contains a patch for the issue.

Remediation

Upgrade Debian:unstable cups to version 2.4.7-2 or higher.

References

CVE-2024-35235 vulnerability report

medium severity

Insufficient Comparison

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.7-3
  • Fixed in: 2.4.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › cups/libcups2@2.2.7-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream cups package and not the cups package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A logic issue was addressed with improved state management. This issue is fixed in Security Update 2022-003 Catalina, macOS Monterey 12.3, macOS Big Sur 11.6.5. An application may be able to gain elevated privileges.

Remediation

Upgrade Debian:unstable cups to version 2.4.2-1 or higher.

References

Insufficient Comparison vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: e2fsprogs
  • Introduced through: e2fsprogs@1.44.0-1, e2fsprogs/libcom-err2@1.44.0-1 and others
  • Fixed in: 1.45.5-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › e2fsprogs@1.44.0-1
  • Introduced through: openjdk@10-ea-jdk › e2fsprogs/libcom-err2@1.44.0-1
  • Introduced through: openjdk@10-ea-jdk › e2fsprogs/libext2fs2@1.44.0-1
  • Introduced through: openjdk@10-ea-jdk › e2fsprogs/libss2@1.44.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream e2fsprogs package and not the e2fsprogs package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A code execution vulnerability exists in the directory rehashing functionality of E2fsprogs e2fsck 1.45.4. A specially crafted ext4 directory can cause an out-of-bounds write on the stack, resulting in code execution. An attacker can corrupt a partition to trigger this vulnerability.

Remediation

Upgrade Debian:unstable e2fsprogs to version 1.45.5-1 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: libx11/libx11-6
  • Introduced through: libx11/libx11-6@2:1.6.5-1, libx11/libx11-data@2:1.6.5-1 and others
  • Fixed in: 2:1.6.10-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-6@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-data@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-dev@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-doc@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-xcb1@2:1.6.5-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libx11 package and not the libx11 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An integer overflow leading to a heap-buffer overflow was found in The X Input Method (XIM) client was implemented in libX11 before version 1.6.10. As per upstream this is security relevant when setuid programs call XIM client functions while running with elevated privileges. No such programs are shipped with Red Hat Enterprise Linux.

Remediation

Upgrade Debian:unstable libx11 to version 2:1.6.10-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: wayland/libwayland-client0
  • Introduced through: wayland/libwayland-client0@1.14.0-2, wayland/libwayland-cursor0@1.14.0-2 and others
  • Fixed in: 1.21.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › wayland/libwayland-client0@1.14.0-2
  • Introduced through: openjdk@10-ea-jdk › wayland/libwayland-cursor0@1.14.0-2
  • Introduced through: openjdk@10-ea-jdk › wayland/libwayland-server0@1.14.0-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream wayland package and not the wayland package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An internal reference count is held on the buffer pool, incremented every time a new buffer is created from the pool. The reference count is maintained as an int; on LP64 systems this can cause the reference count to overflow if the client creates a large number of wl_shm buffer objects, or if it can coerce the server to create a large number of external references to the buffer storage. With the reference count overflowing, a use-after-free can be constructed on the wl_shm_pool tracking structure, where values may be incremented or decremented; it may also be possible to construct a limited oracle to leak 4 bytes of server-side memory to the attacking client at a time.

Remediation

Upgrade Debian:unstable wayland to version 1.21.0-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: apr-util/libaprutil1
  • Introduced through: apr-util/libaprutil1@1.6.1-2
  • Fixed in: 1.6.3-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › apr-util/libaprutil1@1.6.1-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream apr-util package and not the apr-util package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Integer Overflow or Wraparound vulnerability in apr_base64 functions of Apache Portable Runtime Utility (APR-util) allows an attacker to write beyond bounds of a buffer.

This issue affects Apache Portable Runtime Utility (APR-util) 1.6.1 and prior versions.

Remediation

Upgrade Debian:unstable apr-util to version 1.6.3-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

medium severity

Use After Free

  • Vulnerable module: cairo/libcairo-gobject2
  • Introduced through: cairo/libcairo-gobject2@1.15.10-3 and cairo/libcairo2@1.15.10-3
  • Fixed in: 1.16.0-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › cairo/libcairo-gobject2@1.15.10-3
  • Introduced through: openjdk@10-ea-jdk › cairo/libcairo2@1.15.10-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream cairo package and not the cairo package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

cairo 1.16.0, in cairo_ft_apply_variations() in cairo-ft-font.c, would free memory using a free function incompatible with WebKit's fastMalloc, leading to an application crash with a "free(): invalid pointer" error.

Remediation

Upgrade Debian:unstable cairo to version 1.16.0-4 or higher.

References

Use After Free vulnerability report

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.84.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable 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:unstable curl to version 7.84.0-1 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.88.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable 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:unstable curl to version 7.88.1-1 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

medium severity

Cleartext Transmission of Sensitive Information

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.88.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable relevant fixed versions and status.

A cleartext transmission of sensitive information vulnerability exists in curl <v7.88.0 that could cause HSTS functionality to behave incorrectly when multiple URLs are requested in parallel. Using its HSTS support, curl can be instructed to use HTTPS instead of using an insecure clear-text HTTP step even when HTTP is provided in the URL. This HSTS mechanism would however surprisingly fail when multiple transfers are done in parallel as the HSTS cache file gets overwritten by the most recentlycompleted transfer. A later HTTP-only transfer to the earlier host name would then not get upgraded properly to HSTS.

Remediation

Upgrade Debian:unstable curl to version 7.88.1-1 or higher.

References

Cleartext Transmission of Sensitive Information vulnerability report

medium severity

CVE-2023-46218

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 8.5.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable 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:unstable curl to version 8.5.0-1 or higher.

References

CVE-2023-46218 vulnerability report

medium severity

Insufficient Comparison

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 8.11.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable relevant fixed versions and status.

When curl is asked to use HSTS, the expiry time for a subdomain might overwrite a parent domain's cache entry, making it end sooner or later than otherwise intended.

This affects curl using applications that enable HSTS and use URLs with the insecure HTTP:// scheme and perform transfers with hosts like x.example.com as well as example.com where the first host is a subdomain of the second host.

(The HSTS cache either needs to have been populated manually or there needs to have been previous HTTPS accesses done as the cache needs to have entries for the domains involved to trigger this problem.)

When x.example.com responds with Strict-Transport-Security: headers, this bug can make the subdomain's expiry timeout bleed over and get set for the parent domain example.com in curl's HSTS cache.

The result of a triggered bug is that HTTP accesses to example.com get converted to HTTPS for a different period of time than what was asked for by the origin server. If example.com for example stops supporting HTTPS at its expiry time, curl might then fail to access http://example.com until the (wrongly set) timeout expires. This bug can also expire the parent's entry earlier, thus making curl inadvertently switch back to insecure HTTP earlier than otherwise intended.

Remediation

Upgrade Debian:unstable curl to version 8.11.0-1 or higher.

References

Insufficient Comparison vulnerability report

medium severity

Insufficiently Protected Credentials

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.83.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable 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:unstable curl to version 7.83.0-1 or higher.

References

Insufficiently Protected Credentials vulnerability report

medium severity

Out-of-bounds Read

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 8.9.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable relevant fixed versions and status.

libcurl's ASN1 parser code has the GTime2str() function, used for parsing an ASN.1 Generalized Time field. If given an syntactically incorrect field, the parser might end up using -1 for the length of the time fraction, leading to a strlen() getting performed on a pointer to a heap buffer area that is not (purposely) null terminated.

This flaw most likely leads to a crash, but can also lead to heap contents getting returned to the application when CURLINFO_CERTINFO is used.

Remediation

Upgrade Debian:unstable curl to version 8.9.1-1 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.86.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable relevant fixed versions and status.

curl can be told to parse a .netrc file for credentials. If that file endsin a line with 4095 consecutive non-white space letters and no newline, curlwould first read past the end of the stack-based buffer, and if the readworks, write a zero byte beyond its boundary.This will in most cases cause a segfault or similar, but circumstances might also cause different outcomes.If a malicious user can provide a custom netrc file to an application or otherwise affect its contents, this flaw could be used as denial-of-service.

Remediation

Upgrade Debian:unstable curl to version 7.86.0-1 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

CVE-2022-42012

  • Vulnerable module: dbus
  • Introduced through: dbus@1.12.6-2, dbus/dbus-user-session@1.12.6-2 and others
  • Fixed in: 1.14.4-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › dbus@1.12.6-2
  • Introduced through: openjdk@10-ea-jdk › dbus/dbus-user-session@1.12.6-2
  • Introduced through: openjdk@10-ea-jdk › dbus/libdbus-1-3@1.12.6-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream dbus package and not the dbus package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An issue was discovered in D-Bus before 1.12.24, 1.13.x and 1.14.x before 1.14.4, and 1.15.x before 1.15.2. An authenticated attacker can cause dbus-daemon and other programs that use libdbus to crash by sending a message with attached file descriptors in an unexpected format.

Remediation

Upgrade Debian:unstable dbus to version 1.14.4-1 or higher.

References

CVE-2022-42012 vulnerability report

medium severity

CVE-2023-34969

  • Vulnerable module: dbus
  • Introduced through: dbus@1.12.6-2, dbus/dbus-user-session@1.12.6-2 and others
  • Fixed in: 1.14.8-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › dbus@1.12.6-2
  • Introduced through: openjdk@10-ea-jdk › dbus/dbus-user-session@1.12.6-2
  • Introduced through: openjdk@10-ea-jdk › dbus/libdbus-1-3@1.12.6-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream dbus package and not the dbus package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

D-Bus before 1.15.6 sometimes allows unprivileged users to crash dbus-daemon. If a privileged user with control over the dbus-daemon is using the org.freedesktop.DBus.Monitoring interface to monitor message bus traffic, then an unprivileged user with the ability to connect to the same dbus-daemon can cause a dbus-daemon crash under some circumstances via an unreplyable message. When done on the well-known system bus, this is a denial-of-service vulnerability. The fixed versions are 1.12.28, 1.14.8, and 1.15.6.

Remediation

Upgrade Debian:unstable dbus to version 1.14.8-1 or higher.

References

CVE-2023-34969 vulnerability report

medium severity

Improper Validation of Array Index

  • Vulnerable module: dbus
  • Introduced through: dbus@1.12.6-2, dbus/dbus-user-session@1.12.6-2 and others
  • Fixed in: 1.14.4-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › dbus@1.12.6-2
  • Introduced through: openjdk@10-ea-jdk › dbus/dbus-user-session@1.12.6-2
  • Introduced through: openjdk@10-ea-jdk › dbus/libdbus-1-3@1.12.6-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream dbus package and not the dbus package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An issue was discovered in D-Bus before 1.12.24, 1.13.x and 1.14.x before 1.14.4, and 1.15.x before 1.15.2. An authenticated attacker can cause dbus-daemon and other programs that use libdbus to crash when receiving a message where an array length is inconsistent with the size of the element type.

Remediation

Upgrade Debian:unstable dbus to version 1.14.4-1 or higher.

References

Improper Validation of Array Index vulnerability report

medium severity

Improper Verification of Cryptographic Signature

  • Vulnerable module: dbus
  • Introduced through: dbus@1.12.6-2, dbus/dbus-user-session@1.12.6-2 and others
  • Fixed in: 1.14.4-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › dbus@1.12.6-2
  • Introduced through: openjdk@10-ea-jdk › dbus/dbus-user-session@1.12.6-2
  • Introduced through: openjdk@10-ea-jdk › dbus/libdbus-1-3@1.12.6-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream dbus package and not the dbus package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An issue was discovered in D-Bus before 1.12.24, 1.13.x and 1.14.x before 1.14.4, and 1.15.x before 1.15.2. An authenticated attacker can cause dbus-daemon and other programs that use libdbus to crash when receiving a message with certain invalid type signatures.

Remediation

Upgrade Debian:unstable dbus to version 1.14.4-1 or higher.

References

Improper Verification of Cryptographic Signature vulnerability report

medium severity

Uncontrolled Recursion

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.5-3
  • Fixed in: 2.4.5-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › expat/libexpat1@2.2.5-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In Expat (aka libexpat) before 2.4.5, an attacker can trigger stack exhaustion in build_model via a large nesting depth in the DTD element.

Remediation

Upgrade Debian:unstable expat to version 2.4.5-1 or higher.

References

Uncontrolled Recursion vulnerability report

medium severity

NULL Pointer Dereference

  • Vulnerable module: freetype/libfreetype6
  • Introduced through: freetype/libfreetype6@2.8.1-2
  • Fixed in: 2.9.1-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › freetype/libfreetype6@2.8.1-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream freetype package and not the freetype package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An issue was discovered in FreeType 2 through 2.9. A NULL pointer dereference in the Ins_GETVARIATION() function within ttinterp.c could lead to DoS via a crafted font file.

Remediation

Upgrade Debian:unstable freetype to version 2.9.1-3 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

Divide By Zero

  • Vulnerable module: giflib/libgif7
  • Introduced through: giflib/libgif7@5.1.4-2
  • Fixed in: 5.1.9-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › giflib/libgif7@5.1.4-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream giflib package and not the giflib package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In GIFLIB before 2019-02-16, a malformed GIF file triggers a divide-by-zero exception in the decoder function DGifSlurp in dgif_lib.c if the height field of the ImageSize data structure is equal to zero.

Remediation

Upgrade Debian:unstable giflib to version 5.1.9-1 or higher.

References

Divide By Zero vulnerability report

medium severity

Improper Certificate Validation

  • Vulnerable module: glib-networking
  • Introduced through: glib-networking@2.56.0-1, glib-networking/glib-networking-common@2.56.0-1 and others
  • Fixed in: 2.64.3-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glib-networking@2.56.0-1
  • Introduced through: openjdk@10-ea-jdk › glib-networking/glib-networking-common@2.56.0-1
  • Introduced through: openjdk@10-ea-jdk › glib-networking/glib-networking-services@2.56.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib-networking package and not the glib-networking package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In GNOME glib-networking through 2.64.2, the implementation of GTlsClientConnection skips hostname verification of the server's TLS certificate if the application fails to specify the expected server identity. This is in contrast to its intended documented behavior, to fail the certificate verification. Applications that fail to provide the server identity, including Balsa before 2.5.11 and 2.6.x before 2.6.1, accept a TLS certificate if the certificate is valid for any host.

Remediation

Upgrade Debian:unstable glib-networking to version 2.64.3-2 or higher.

References

Improper Certificate Validation vulnerability report

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.56.1-2 and glib2.0/libglib2.0-data@2.56.1-2
  • Fixed in: 2.86.3-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-0@2.56.1-2
  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-data@2.56.1-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw was found in glib. This vulnerability allows a heap buffer overflow and denial-of-service (DoS) via an integer overflow in GLib's GIO (GLib Input/Output) escape_byte_string() function when processing malicious file or remote filesystem attribute values.

Remediation

Upgrade Debian:unstable glib2.0 to version 2.86.3-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

medium severity

Out-of-bounds Read

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2
  • Fixed in: 2.37-9

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw was found in glibc. When the getaddrinfo function is called with the AF_UNSPEC address family and the system is configured with no-aaaa mode via /etc/resolv.conf, a DNS response via TCP larger than 2048 bytes can potentially disclose stack contents through the function returned address data, and may cause a crash.

Remediation

Upgrade Debian:unstable glibc to version 2.37-9 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Arbitrary Code Injection

  • Vulnerable module: gnupg2/dirmngr
  • Introduced through: gnupg2/dirmngr@2.2.5-1, gnupg2/gnupg@2.2.5-1 and others
  • Fixed in: 2.2.35-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gnupg2/dirmngr@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gnupg@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gnupg-l10n@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gnupg-utils@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpg@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpg-agent@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpg-wks-client@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpg-wks-server@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpgconf@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpgsm@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpgv@2.2.5-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream gnupg2 package and not the gnupg2 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

GnuPG through 2.3.6, in unusual situations where an attacker possesses any secret-key information from a victim's keyring and other constraints (e.g., use of GPGME) are met, allows signature forgery via injection into the status line.

Remediation

Upgrade Debian:unstable gnupg2 to version 2.2.35-3 or higher.

References

Arbitrary Code Injection vulnerability report

medium severity

NULL Pointer Dereference

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.18-1
  • Fixed in: 3.8.9-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gnutls28/libgnutls30@3.5.18-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A NULL pointer dereference flaw was found in the GnuTLS software in _gnutls_figure_common_ciphersuite().

Remediation

Upgrade Debian:unstable gnutls28 to version 3.8.9-3 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

NULL Pointer Dereference

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.18-1
  • Fixed in: 3.7.3-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gnutls28/libgnutls30@3.5.18-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A NULL pointer dereference flaw was found in GnuTLS. As Nettle's hash update functions internally call memcpy, providing zero-length input may cause undefined behavior. This flaw leads to a denial of service after authentication in rare circumstances.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.7.3-2 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

Insufficient Verification of Data Authenticity

  • Vulnerable module: inetutils/inetutils-ping
  • Introduced through: inetutils/inetutils-ping@2:1.9.4-3
  • Fixed in: 2:2.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › inetutils/inetutils-ping@2:1.9.4-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream inetutils package and not the inetutils package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The ftp client in GNU Inetutils before 2.2 does not validate addresses returned by PASV/LSPV responses to make sure they match the server address. This is similar to CVE-2020-8284 for curl.

Remediation

Upgrade Debian:unstable inetutils to version 2:2.2-1 or higher.

References

Insufficient Verification of Data Authenticity vulnerability report

medium severity

Access of Uninitialized Pointer

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.16-2, krb5/libk5crypto3@1.16-2 and others
  • Fixed in: 1.20.1-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › krb5/libgssapi-krb5-2@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libk5crypto3@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libkrb5-3@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libkrb5support0@1.16-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

lib/kadm5/kadm_rpc_xdr.c in MIT Kerberos 5 (aka krb5) before 1.20.2 and 1.21.x before 1.21.1 frees an uninitialized pointer. A remote authenticated user can trigger a kadmind crash. This occurs because _xdr_kadm5_principal_ent_rec does not validate the relationship between n_key_data and the key_data array count.

Remediation

Upgrade Debian:unstable krb5 to version 1.20.1-3 or higher.

References

Access of Uninitialized Pointer vulnerability report

medium severity

NULL Pointer Dereference

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.16-2, krb5/libk5crypto3@1.16-2 and others
  • Fixed in: 1.18.3-7

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › krb5/libgssapi-krb5-2@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libk5crypto3@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libkrb5-3@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libkrb5support0@1.16-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The Key Distribution Center (KDC) in MIT Kerberos 5 (aka krb5) before 1.18.5 and 1.19.x before 1.19.3 has a NULL pointer dereference in kdc/do_tgs_req.c via a FAST inner body that lacks a server field.

Remediation

Upgrade Debian:unstable krb5 to version 1.18.3-7 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

NULL Pointer Dereference

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.16-2, krb5/libk5crypto3@1.16-2 and others
  • Fixed in: 1.16.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › krb5/libgssapi-krb5-2@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libk5crypto3@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libkrb5-3@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libkrb5support0@1.16-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An issue was discovered in MIT Kerberos 5 (aka krb5) through 1.16. The pre-defined function "strlen" is getting a "NULL" string as a parameter value in plugins/kdb/ldap/libkdb_ldap/ldap_principal2.c in the Key Distribution Center (KDC), which allows remote authenticated users to cause a denial of service (NULL pointer dereference) via a modified kadmin client.

Remediation

Upgrade Debian:unstable krb5 to version 1.16.1-1 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

Divide By Zero

  • Vulnerable module: libpng1.6/libpng16-16
  • Introduced through: libpng1.6/libpng16-16@1.6.34-1
  • Fixed in: 1.6.34-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libpng1.6/libpng16-16@1.6.34-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In libpng 1.6.34, a wrong calculation of row_factor in the png_check_chunk_length function (pngrutil.c) may trigger an integer overflow and resultant divide-by-zero while processing a crafted PNG file, leading to a denial of service.

Remediation

Upgrade Debian:unstable libpng1.6 to version 1.6.34-2 or higher.

References

Divide By Zero vulnerability report

medium severity

Resource Exhaustion

  • Vulnerable module: librsvg/librsvg2-2
  • Introduced through: librsvg/librsvg2-2@2.40.20-2 and librsvg/librsvg2-common@2.40.20-2
  • Fixed in: 2.46.4-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › librsvg/librsvg2-2@2.40.20-2
  • Introduced through: openjdk@10-ea-jdk › librsvg/librsvg2-common@2.40.20-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream librsvg package and not the librsvg package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In xml.rs in GNOME librsvg before 2.46.2, a crafted SVG file with nested patterns can cause denial of service when passed to the library for processing. The attacker constructs pattern elements so that the number of final rendered objects grows exponentially.

Remediation

Upgrade Debian:unstable librsvg to version 2.46.4-1 or higher.

References

Resource Exhaustion vulnerability report

medium severity

Double Free

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.9.14+dfsg-1.2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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:unstable 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:unstable libxml2 to version 2.9.14+dfsg-1.2 or higher.

References

Double Free vulnerability report

medium severity

Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion')

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.9.10+dfsg-6.7

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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:unstable 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:unstable libxml2 to version 2.9.10+dfsg-6.7 or higher.

References

Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion') vulnerability report

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.9.14+dfsg-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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:unstable 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:unstable libxml2 to version 2.9.14+dfsg-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

medium severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.9.10+dfsg-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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:unstable relevant fixed versions and status.

libxml2 2.9.8, if --with-lzma is used, allows remote attackers to cause a denial of service (infinite loop) via a crafted XML file that triggers LZMA_MEMLIMIT_ERROR, as demonstrated by xmllint, a different vulnerability than CVE-2015-8035 and CVE-2018-9251.

Remediation

Upgrade Debian:unstable libxml2 to version 2.9.10+dfsg-2 or higher.

References

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability report

medium severity

NULL Pointer Dereference

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.9.14+dfsg-1.2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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:unstable 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:unstable libxml2 to version 2.9.14+dfsg-1.2 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

Out-of-Bounds

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.12.7+dfsg+really2.9.14-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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:unstable 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

Upgrade Debian:unstable libxml2 to version 2.12.7+dfsg+really2.9.14-1 or higher.

References

Out-of-Bounds vulnerability report

medium severity

Use After Free

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.12.7+dfsg+really2.9.14-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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:unstable 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

Upgrade Debian:unstable libxml2 to version 2.12.7+dfsg+really2.9.14-1 or higher.

References

Use After Free vulnerability report

medium severity

CVE-2023-50495

  • Vulnerable module: ncurses/libncurses5
  • Introduced through: ncurses/libncurses5@6.1-1, ncurses/libncursesw5@6.1-1 and others
  • Fixed in: 6.4+20230625-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › ncurses/libncurses5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/libncursesw5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/libtinfo5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/ncurses-base@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/ncurses-bin@6.1-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

NCurse v6.4-20230418 was discovered to contain a segmentation fault via the component _nc_wrap_entry().

Remediation

Upgrade Debian:unstable ncurses to version 6.4+20230625-1 or higher.

References

CVE-2023-50495 vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: ncurses/libncurses5
  • Introduced through: ncurses/libncurses5@6.1-1, ncurses/libncursesw5@6.1-1 and others
  • Fixed in: 6.1+20191019-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › ncurses/libncurses5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/libncursesw5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/libtinfo5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/ncurses-base@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/ncurses-bin@6.1-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Buffer Overflow vulnerability in one_one_mapping function in progs/dump_entry.c:1373 in ncurses 6.1 allows remote attackers to cause a denial of service via crafted command.

Remediation

Upgrade Debian:unstable ncurses to version 6.1+20191019-1 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: ncurses/libncurses5
  • Introduced through: ncurses/libncurses5@6.1-1, ncurses/libncursesw5@6.1-1 and others
  • Fixed in: 6.1+20191019-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › ncurses/libncurses5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/libncursesw5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/libtinfo5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/ncurses-base@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/ncurses-bin@6.1-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Buffer Overflow vulnerability in fmt_entry function in progs/dump_entry.c:1116 in ncurses 6.1 allows remote attackers to cause a denial of service via crafted command.

Remediation

Upgrade Debian:unstable ncurses to version 6.1+20191019-1 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: ncurses/libncurses5
  • Introduced through: ncurses/libncurses5@6.1-1, ncurses/libncursesw5@6.1-1 and others
  • Fixed in: 6.1+20191019-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › ncurses/libncurses5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/libncursesw5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/libtinfo5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/ncurses-base@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/ncurses-bin@6.1-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Buffer Overflow vulnerability in _nc_find_entry in tinfo/comp_hash.c:70 in ncurses 6.1 allows remote attackers to cause a denial of service via crafted command.

Remediation

Upgrade Debian:unstable ncurses to version 6.1+20191019-1 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: ncurses/libncurses5
  • Introduced through: ncurses/libncurses5@6.1-1, ncurses/libncursesw5@6.1-1 and others
  • Fixed in: 6.1+20191019-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › ncurses/libncurses5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/libncursesw5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/libtinfo5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/ncurses-base@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/ncurses-bin@6.1-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Buffer Overflow vulnerability in _nc_find_entry function in tinfo/comp_hash.c:66 in ncurses 6.1 allows remote attackers to cause a denial of service via crafted command.

Remediation

Upgrade Debian:unstable ncurses to version 6.1+20191019-1 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: ncurses/libncurses5
  • Introduced through: ncurses/libncurses5@6.1-1, ncurses/libncursesw5@6.1-1 and others
  • Fixed in: 6.1+20191019-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › ncurses/libncurses5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/libncursesw5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/libtinfo5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/ncurses-base@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/ncurses-bin@6.1-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Buffer Overflow vulnerability in fmt_entry function in progs/dump_entry.c:1100 in ncurses 6.1 allows remote attackers to cause a denial of service via crafted command.

Remediation

Upgrade Debian:unstable ncurses to version 6.1+20191019-1 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: ncurses/libncurses5
  • Introduced through: ncurses/libncurses5@6.1-1, ncurses/libncursesw5@6.1-1 and others
  • Fixed in: 6.1+20191019-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › ncurses/libncurses5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/libncursesw5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/libtinfo5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/ncurses-base@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/ncurses-bin@6.1-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Buffer Overflow vulnerability in postprocess_terminfo function in tinfo/parse_entry.c:997 in ncurses 6.1 allows remote attackers to cause a denial of service via crafted command.

Remediation

Upgrade Debian:unstable ncurses to version 6.1+20191019-1 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

CVE-2024-7531

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.36.1-1
  • Fixed in: 2:3.103-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nss/libnss3@2:3.36.1-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nss package and not the nss package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Calling PK11_Encrypt() in NSS using CKM_CHACHA20 and the same buffer for input and output can result in plaintext on an Intel Sandy Bridge processor. In Firefox this only affects the QUIC header protection feature when the connection is using the ChaCha20-Poly1305 cipher suite. The most likely outcome is connection failure, but if the connection persists despite the high packet loss it could be possible for a network observer to identify packets as coming from the same source despite a network path change. This vulnerability affects Firefox < 129, Firefox ESR < 115.14, and Firefox ESR < 128.1.

Remediation

Upgrade Debian:unstable nss to version 2:3.103-1 or higher.

References

CVE-2024-7531 vulnerability report

medium severity

Improper Authentication

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.36.1-1
  • Fixed in: 2:3.49-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nss/libnss3@2:3.36.1-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nss package and not the nss package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

After a HelloRetryRequest has been sent, the client may negotiate a lower protocol that TLS 1.3, resulting in an invalid state transition in the TLS State Machine. If the client gets into this state, incoming Application Data records will be ignored. This vulnerability affects Firefox < 72.

Remediation

Upgrade Debian:unstable nss to version 2:3.49-1 or higher.

References

Improper Authentication vulnerability report

medium severity

Improper Certificate Validation

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.36.1-1
  • Fixed in: 2:3.73-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nss/libnss3@2:3.36.1-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nss package and not the nss package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

After accepting an untrusted certificate, handling an empty pkcs7 sequence as part of the certificate data could have lead to a crash. This crash is believed to be unexploitable. This vulnerability affects Firefox ESR < 91.5, Firefox < 96, and Thunderbird < 91.5.

Remediation

Upgrade Debian:unstable nss to version 2:3.73-1 or higher.

References

Improper Certificate Validation vulnerability report

medium severity

Information Exposure

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.36.1-1
  • Fixed in: 2:3.61-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nss/libnss3@2:3.36.1-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nss package and not the nss package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The NSS code used for checking PKCS#1 v1.5 was leaking information useful in mounting Bleichenbacher-like attacks. Both the overall correctness of the padding as well as the length of the encrypted message was leaking through timing side-channel. By sending large number of attacker-selected ciphertexts, the attacker would be able to decrypt a previously intercepted PKCS#1 v1.5 ciphertext (for example, to decrypt a TLS session that used RSA key exchange), or forge a signature using the victim's key. The issue was fixed by implementing the implicit rejection algorithm, in which the NSS returns a deterministic random message in case invalid padding is detected, as proposed in the Marvin Attack paper. This vulnerability affects NSS < 3.61.

Remediation

Upgrade Debian:unstable nss to version 2:3.61-1 or higher.

References

Information Exposure vulnerability report

medium severity

NULL Pointer Dereference

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.36.1-1
  • Fixed in: 2:3.42.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nss/libnss3@2:3.36.1-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nss package and not the nss package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In Network Security Services (NSS) before 3.36.7 and before 3.41.1, a malformed signature can cause a crash due to a null dereference, resulting in a Denial of Service.

Remediation

Upgrade Debian:unstable nss to version 2:3.42.1-1 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

Double Free

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:7.6p1-4
  • Fixed in: 1:9.2p1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssh/openssh-client@1:7.6p1-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

OpenSSH server (sshd) 9.1 introduced a double-free vulnerability during options.kex_algorithms handling. This is fixed in OpenSSH 9.2. The double free can be leveraged, by an unauthenticated remote attacker in the default configuration, to jump to any location in the sshd address space. One third-party report states "remote code execution is theoretically possible."

Remediation

Upgrade Debian:unstable openssh to version 1:9.2p1-1 or higher.

References

Double Free vulnerability report

medium severity

OS Command Injection

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:7.6p1-4
  • Fixed in: 1:9.6p1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssh/openssh-client@1:7.6p1-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In ssh in OpenSSH before 9.6, OS command injection might occur if a user name or host name has shell metacharacters, and this name is referenced by an expansion token in certain situations. For example, an untrusted Git repository can have a submodule with shell metacharacters in a user name or host name.

Remediation

Upgrade Debian:unstable openssh to version 1:9.6p1-1 or higher.

References

OS Command Injection vulnerability report

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 3.0.9-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Issue summary: Processing some specially crafted ASN.1 object identifiers or data containing them may be very slow.

Impact summary: Applications that use OBJ_obj2txt() directly, or use any of the OpenSSL subsystems OCSP, PKCS7/SMIME, CMS, CMP/CRMF or TS with no message size limit may experience notable to very long delays when processing those messages, which may lead to a Denial of Service.

An OBJECT IDENTIFIER is composed of a series of numbers - sub-identifiers - most of which have no size limit. OBJ_obj2txt() may be used to translate an ASN.1 OBJECT IDENTIFIER given in DER encoding form (using the OpenSSL type ASN1_OBJECT) to its canonical numeric text form, which are the sub-identifiers of the OBJECT IDENTIFIER in decimal form, separated by periods.

When one of the sub-identifiers in the OBJECT IDENTIFIER is very large (these are sizes that are seen as absurdly large, taking up tens or hundreds of KiBs), the translation to a decimal number in text may take a very long time. The time complexity is O(n^2) with 'n' being the size of the sub-identifiers in bytes (*).

With OpenSSL 3.0, support to fetch cryptographic algorithms using names / identifiers in string form was introduced. This includes using OBJECT IDENTIFIERs in canonical numeric text form as identifiers for fetching algorithms.

Such OBJECT IDENTIFIERs may be received through the ASN.1 structure AlgorithmIdentifier, which is commonly used in multiple protocols to specify what cryptographic algorithm should be used to sign or verify, encrypt or decrypt, or digest passed data.

Applications that call OBJ_obj2txt() directly with untrusted data are affected, with any version of OpenSSL. If the use is for the mere purpose of display, the severity is considered low.

In OpenSSL 3.0 and newer, this affects the subsystems OCSP, PKCS7/SMIME, CMS, CMP/CRMF or TS. It also impacts anything that processes X.509 certificates, including simple things like verifying its signature.

The impact on TLS is relatively low, because all versions of OpenSSL have a 100KiB limit on the peer's certificate chain. Additionally, this only impacts clients, or servers that have explicitly enabled client authentication.

In OpenSSL 1.1.1 and 1.0.2, this only affects displaying diverse objects, such as X.509 certificates. This is assumed to not happen in such a way that it would cause a Denial of Service, so these versions are considered not affected by this issue in such a way that it would be cause for concern, and the severity is therefore considered low.

Remediation

Upgrade Debian:unstable openssl to version 3.0.9-1 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 3.1.5-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Issue summary: The POLY1305 MAC (message authentication code) implementation contains a bug that might corrupt the internal state of applications running on PowerPC CPU based platforms if the CPU provides vector instructions.

Impact summary: If an attacker can influence whether the POLY1305 MAC algorithm is used, the application state might be corrupted with various application dependent consequences.

The POLY1305 MAC (message authentication code) implementation in OpenSSL for PowerPC CPUs restores the contents of vector registers in a different order than they are saved. Thus the contents of some of these vector registers are corrupted when returning to the caller. The vulnerable code is used only on newer PowerPC processors supporting the PowerISA 2.07 instructions.

The consequences of this kind of internal application state corruption can be various - from no consequences, if the calling application does not depend on the contents of non-volatile XMM registers at all, to the worst consequences, where the attacker could get complete control of the application process. However unless the compiler uses the vector registers for storing pointers, the most likely consequence, if any, would be an incorrect result of some application dependent calculations or a crash leading to a denial of service.

The POLY1305 MAC algorithm is most frequently used as part of the CHACHA20-POLY1305 AEAD (authenticated encryption with associated data) algorithm. The most common usage of this AEAD cipher is with TLS protocol versions 1.2 and 1.3. If this cipher is enabled on the server a malicious client can influence whether this AEAD cipher is used. This implies that TLS server applications using OpenSSL can be potentially impacted. However we are currently not aware of any concrete application that would be affected by this issue therefore we consider this a Low severity security issue.

Remediation

Upgrade Debian:unstable openssl to version 3.1.5-1 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Uncontrolled Recursion

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 1.1.0h-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Constructed ASN.1 types with a recursive definition (such as can be found in PKCS7) could eventually exceed the stack given malicious input with excessive recursion. This could result in a Denial Of Service attack. There are no such structures used within SSL/TLS that come from untrusted sources so this is considered safe. Fixed in OpenSSL 1.1.0h (Affected 1.1.0-1.1.0g). Fixed in OpenSSL 1.0.2o (Affected 1.0.2b-1.0.2n).

Remediation

Upgrade Debian:unstable openssl to version 1.1.0h-1 or higher.

References

Uncontrolled Recursion vulnerability report

medium severity

Divide By Zero

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1
  • Fixed in: 3.29.0-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In SQLite through 3.29.0, whereLoopAddBtreeIndex in sqlite3.c can crash a browser or other application because of missing validation of a sqlite_stat1 sz field, aka a "severe division by zero in the query planner."

Remediation

Upgrade Debian:unstable sqlite3 to version 3.29.0-2 or higher.

References

Divide By Zero vulnerability report

medium severity

Improper Input Validation

  • Vulnerable module: subversion
  • Introduced through: subversion@1.9.7-4 and subversion/libsvn1@1.9.7-4
  • Fixed in: 1.10.6-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › subversion@1.9.7-4
  • Introduced through: openjdk@10-ea-jdk › subversion/libsvn1@1.9.7-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream subversion package and not the subversion package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In Apache Subversion versions up to and including 1.9.10, 1.10.4, 1.12.0, Subversion's svnserve server process may exit when a well-formed read-only request produces a particular answer. This can lead to disruption for users of the server.

Remediation

Upgrade Debian:unstable subversion to version 1.10.6-1 or higher.

References

Improper Input Validation vulnerability report

medium severity

Buffer Overflow

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.5.1~rc3-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.5.1~rc3-1 or higher.

References

Buffer Overflow vulnerability report

medium severity

CVE-2019-7663

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.0.10-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable relevant fixed versions and status.

An Invalid Address dereference was discovered in TIFFWriteDirectoryTagTransferfunction in libtiff/tif_dirwrite.c in LibTIFF 4.0.10, affecting the cpSeparateBufToContigBuf function in tiffcp.c. Remote attackers could leverage this vulnerability to cause a denial-of-service via a crafted tiff file. This is different from CVE-2018-12900.

Remediation

Upgrade Debian:unstable tiff to version 4.0.10-4 or higher.

References

CVE-2019-7663 vulnerability report

medium severity

Divide By Zero

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.4.0-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.4.0-3 or higher.

References

Divide By Zero vulnerability report

medium severity

Divide By Zero

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.4.0-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.4.0-3 or higher.

References

Divide By Zero vulnerability report

medium severity

Divide By Zero

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.4.0-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.4.0-3 or higher.

References

Divide By Zero vulnerability report

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.5.1+git230720-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.5.1+git230720-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.5.1+git230720-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.5.1+git230720-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

medium severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.5.0-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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

Upgrade Debian:unstable tiff to version 4.5.0-2 or higher.

References

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability report

medium severity

NULL Pointer Dereference

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.0.10-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable relevant fixed versions and status.

In LibTIFF 4.0.9, there is a NULL pointer dereference in the TIFFWriteDirectorySec function in tif_dirwrite.c that will lead to a denial of service attack, as demonstrated by tiffset.

Remediation

Upgrade Debian:unstable tiff to version 4.0.10-4 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

NULL Pointer Dereference

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.0.10-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable relevant fixed versions and status.

A NULL pointer dereference in the function _TIFFmemcmp at tif_unix.c (called from TIFFWriteDirectoryTagTransferfunction) in LibTIFF 4.0.9 allows an attacker to cause a denial-of-service through a crafted tiff file. This vulnerability can be triggered by the executable tiffcp.

Remediation

Upgrade Debian:unstable tiff to version 4.0.10-4 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

NULL Pointer Dereference

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.5.0-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.5.0-5 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

Out-of-bounds Read

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.4.0-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.4.0-5 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.1.0+git201212-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.1.0+git201212-1 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.0.10+git190814-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable relevant fixed versions and status.

Buffer Overflow in LibTiff v4.0.10 allows attackers to cause a denial of service via the 'in _TIFFmemcpy' funtion in the component 'tif_unix.c'.

Remediation

Upgrade Debian:unstable tiff to version 4.0.10+git190814-1 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.4.0-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.4.0-4 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.4.0-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.4.0-5 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.4.0-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.4.0-5 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.4.0-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.4.0-5 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.4.0-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.4.0-5 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Reachable Assertion

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.3.0-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.3.0-5 or higher.

References

Reachable Assertion vulnerability report

medium severity

Reachable Assertion

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.0.9-6

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable relevant fixed versions and status.

The TIFFWriteDirectorySec() function in tif_dirwrite.c in LibTIFF through 4.0.9 allows remote attackers to cause a denial of service (assertion failure and application crash) via a crafted file, a different vulnerability than CVE-2017-13726.

Remediation

Upgrade Debian:unstable tiff to version 4.0.9-6 or higher.

References

Reachable Assertion vulnerability report

medium severity

Resource Exhaustion

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.5.1+git230720-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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

Upgrade Debian:unstable tiff to version 4.5.1+git230720-2 or higher.

References

Resource Exhaustion vulnerability report

medium severity

Improper Input Validation

  • Vulnerable module: wget
  • Introduced through: wget@1.19.4-1
  • Fixed in: 1.19.5-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › wget@1.19.4-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream wget package and not the wget package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

GNU Wget before 1.19.5 is prone to a cookie injection vulnerability in the resp_new function in http.c via a \r\n sequence in a continuation line.

Remediation

Upgrade Debian:unstable wget to version 1.19.5-1 or higher.

References

Improper Input Validation vulnerability report

medium severity

Race Condition

  • Vulnerable module: libgcrypt20
  • Introduced through: libgcrypt20@1.8.1-4
  • Fixed in: 1.8.5-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libgcrypt20@1.8.1-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream libgcrypt20 package and not the libgcrypt20 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

It was discovered that there was a ECDSA timing attack in the libgcrypt20 cryptographic library. Version affected: 1.8.4-5, 1.7.6-2+deb9u3, and 1.6.3-2+deb8u4. Versions fixed: 1.8.5-2 and 1.6.3-2+deb8u7.

Remediation

Upgrade Debian:unstable libgcrypt20 to version 1.8.5-1 or higher.

References

Race Condition vulnerability report

medium severity

Cross-site Scripting (XSS)

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.9.12+dfsg-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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:unstable relevant fixed versions and status.

Possible cross-site scripting vulnerability in libxml after commit 960f0e2.

Remediation

Upgrade Debian:unstable libxml2 to version 2.9.12+dfsg-3 or higher.

References

Cross-site Scripting (XSS) vulnerability report

medium severity

Stack-based Buffer Overflow

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.3.0-8

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.3.0-8 or higher.

References

Stack-based Buffer Overflow vulnerability report

medium severity

Out-of-bounds Read

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.31.1-0.5, util-linux/fdisk@2.31.1-0.5 and others
  • Fixed in: 2.41.3-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › util-linux@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/fdisk@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/libblkid1@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/libfdisk1@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/libmount1@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/libsmartcols1@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/libuuid1@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/mount@2.31.1-0.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream util-linux package and not the util-linux package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw was found in util-linux. This vulnerability allows a heap buffer overread when processing 256-byte usernames, specifically within the setpwnam() function, affecting SUID (Set User ID) login-utils utilities writing to the password database.

Remediation

Upgrade Debian:unstable util-linux to version 2.41.3-1 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Open Redirect

  • Vulnerable module: wget
  • Introduced through: wget@1.19.4-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › wget@1.19.4-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream wget package and not the wget package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

GNU Wget through 1.21.1 does not omit the Authorization header upon a redirect to a different origin, a related issue to CVE-2018-1000007.

Remediation

There is no fixed version for Debian:unstable wget.

References

Open Redirect vulnerability report

medium severity

Improper Verification of Cryptographic Signature

  • Vulnerable module: apt
  • Introduced through: apt@1.6~beta1 and apt/libapt-pkg5.0@1.6~beta1
  • Fixed in: 1.6.4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › apt@1.6~beta1
  • Introduced through: openjdk@10-ea-jdk › apt/libapt-pkg5.0@1.6~beta1

NVD Description

Note: Versions mentioned in the description apply only to the upstream apt package and not the apt package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The mirror:// method implementation in Advanced Package Tool (APT) 1.6.x before 1.6.4 and 1.7.x before 1.7.0~alpha3 mishandles gpg signature verification for the InRelease file of a fallback mirror, aka mirrorfail.

Remediation

Upgrade Debian:unstable apt to version 1.6.4 or higher.

References

Improper Verification of Cryptographic Signature vulnerability report

medium severity

Information Exposure

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.7-3
  • Fixed in: 2.2.10-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › cups/libcups2@2.2.7-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream cups package and not the cups package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The session cookie generated by the CUPS web interface was easy to guess on Linux, allowing unauthorized scripted access to the web interface when the web interface is enabled. This issue affected versions prior to v2.2.10.

Remediation

Upgrade Debian:unstable cups to version 2.2.10-1 or higher.

References

Information Exposure vulnerability report

medium severity

Double Free

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.88.1-7

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable relevant fixed versions and status.

A double free vulnerability exists in libcurl <8.0.0 when sharing HSTS data between separate "handles". This sharing was introduced without considerations for do this sharing across separate threads but there was no indication of this fact in the documentation. Due to missing mutexes or thread locks, two threads sharing the same HSTS data could end up doing a double-free or use-after-free.

Remediation

Upgrade Debian:unstable curl to version 7.88.1-7 or higher.

References

Double Free vulnerability report

medium severity

Improper Authentication

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.88.1-7

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable 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:unstable curl to version 7.88.1-7 or higher.

References

Improper Authentication vulnerability report

medium severity

Improper Authentication

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.88.1-7

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable 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:unstable curl to version 7.88.1-7 or higher.

References

Improper Authentication vulnerability report

medium severity

Improper Certificate Validation

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.88.1-10

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable 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:unstable curl to version 7.88.1-10 or higher.

References

Improper Certificate Validation vulnerability report

medium severity

Insufficient Verification of Data Authenticity

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.79.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable 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:unstable curl to version 7.79.1-1 or higher.

References

Insufficient Verification of Data Authenticity vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.84.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable 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:unstable curl to version 7.84.0-1 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Use After Free

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.86.0-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable 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:unstable curl to version 7.86.0-3 or higher.

References

Use After Free vulnerability report

medium severity

Information Exposure

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.56.1-2 and glib2.0/libglib2.0-data@2.56.1-2
  • Fixed in: 2.62.5-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-0@2.56.1-2
  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-data@2.56.1-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

GSocketClient in GNOME GLib through 2.62.4 may occasionally connect directly to a target address instead of connecting via a proxy server when configured to do so, because the proxy_addr field is mishandled. This bug is timing-dependent and may occur only sporadically depending on network delays. The greatest security relevance is in use cases where a proxy is used to help with privacy/anonymity, even though there is no technical barrier to a direct connection. NOTE: versions before 2.60 are unaffected.

Remediation

Upgrade Debian:unstable glib2.0 to version 2.62.5-1 or higher.

References

Information Exposure vulnerability report

medium severity

Out-of-bounds Read

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2
  • Fixed in: 2.31-9

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The iconv feature in the GNU C Library (aka glibc or libc6) through 2.32, when processing invalid multi-byte input sequences in the EUC-KR encoding, may have a buffer over-read.

Remediation

Upgrade Debian:unstable glibc to version 2.31-9 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Use After Free

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2
  • Fixed in: 2.36-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw has been identified in glibc. In an uncommon situation, the gaih_inet function may use memory that has been freed, resulting in an application crash. This issue is only exploitable when the getaddrinfo function is called and the hosts database in /etc/nsswitch.conf is configured with SUCCESS=continue or SUCCESS=merge.

Remediation

Upgrade Debian:unstable glibc to version 2.36-3 or higher.

References

Use After Free vulnerability report

medium severity

Use After Free

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2
  • Fixed in: 2.37-10

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw has been identified in glibc. In an extremely rare situation, the getaddrinfo function may access memory that has been freed, resulting in an application crash. This issue is only exploitable when a NSS module implements only the nss_gethostbyname2_r and nss_getcanonname_r hooks without implementing the nss*_gethostbyname3_r hook. The resolved name should return a large number of IPv6 and IPv4, and the call to the getaddrinfo function should have the AF_INET6 address family with AI_CANONNAME, AI_ALL and AI_V4MAPPED as flags.

Remediation

Upgrade Debian:unstable glibc to version 2.37-10 or higher.

References

Use After Free vulnerability report

medium severity

Information Exposure

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.18-1
  • Fixed in: 3.8.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gnutls28/libgnutls30@3.5.18-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A vulnerability was found that the response times to malformed ciphertexts in RSA-PSK ClientKeyExchange differ from response times of ciphertexts with correct PKCS#1 v1.5 padding.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.8.2-1 or higher.

References

Information Exposure vulnerability report

medium severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.18-1
  • Fixed in: 3.5.19-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gnutls28/libgnutls30@3.5.18-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

It was found that the GnuTLS implementation of HMAC-SHA-384 was vulnerable to a Lucky thirteen style attack. Remote attackers could use this flaw to conduct distinguishing attacks and plain text recovery attacks via statistical analysis of timing data using crafted packets.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.5.19-1 or higher.

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

medium severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.18-1
  • Fixed in: 3.5.19-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gnutls28/libgnutls30@3.5.18-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

It was found that the GnuTLS implementation of HMAC-SHA-256 was vulnerable to a Lucky thirteen style attack. Remote attackers could use this flaw to conduct distinguishing attacks and plaintext-recovery attacks via statistical analysis of timing data using crafted packets.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.5.19-1 or higher.

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

medium severity

Reversible One-Way Hash

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.16-2, krb5/libk5crypto3@1.16-2 and others
  • Fixed in: 1.21.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › krb5/libgssapi-krb5-2@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libk5crypto3@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libkrb5-3@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libkrb5support0@1.16-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A vulnerability in the MIT Kerberos implementation allows GSSAPI-protected messages using RC4-HMAC-MD5 to be spoofed due to weaknesses in the MD5 checksum design. If RC4 is preferred over stronger encryption types, an attacker could exploit MD5 collisions to forge message integrity codes. This may lead to unauthorized message tampering.

Remediation

Upgrade Debian:unstable krb5 to version 1.21.2-1 or higher.

References

Reversible One-Way Hash vulnerability report

medium severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: libgcrypt20
  • Introduced through: libgcrypt20@1.8.1-4
  • Fixed in: 1.8.7-6

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libgcrypt20@1.8.1-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream libgcrypt20 package and not the libgcrypt20 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The ElGamal implementation in Libgcrypt before 1.9.4 allows plaintext recovery because, during interaction between two cryptographic libraries, a certain dangerous combination of the prime defined by the receiver's public key, the generator defined by the receiver's public key, and the sender's ephemeral exponents can lead to a cross-configuration attack against OpenPGP.

Remediation

Upgrade Debian:unstable libgcrypt20 to version 1.8.7-6 or higher.

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

medium severity

Improper Validation of Integrity Check Value

  • Vulnerable module: libssh2/libssh2-1
  • Introduced through: libssh2/libssh2-1@1.8.0-1
  • Fixed in: 1.11.0-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libssh2/libssh2-1@1.8.0-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:unstable relevant fixed versions and status.

The SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 and other products, allows remote attackers to bypass integrity checks such that some packets are omitted (from the extension negotiation message), and a client and server may consequently end up with a connection for which some security features have been downgraded or disabled, aka a Terrapin attack. This occurs because the SSH Binary Packet Protocol (BPP), implemented by these extensions, mishandles the handshake phase and mishandles use of sequence numbers. For example, there is an effective attack against SSH's use of ChaCha20-Poly1305 (and CBC with Encrypt-then-MAC). The bypass occurs in chacha20-poly1305@openssh.com and (if CBC is used) the -etm@openssh.com MAC algorithms. This also affects Maverick Synergy Java SSH API before 3.1.0-SNAPSHOT, Dropbear through 2022.83, Ssh before 5.1.1 in Erlang/OTP, PuTTY before 0.80, AsyncSSH before 2.14.2, golang.org/x/crypto before 0.17.0, libssh before 0.10.6, libssh2 through 1.11.0, Thorn Tech SFTP Gateway before 3.4.6, Tera Term before 5.1, Paramiko before 3.4.0, jsch before 0.2.15, SFTPGo before 2.5.6, Netgate pfSense Plus through 23.09.1, Netgate pfSense CE through 2.7.2, HPN-SSH through 18.2.0, ProFTPD before 1.3.8b (and before 1.3.9rc2), ORYX CycloneSSH before 2.3.4, NetSarang XShell 7 before Build 0144, CrushFTP before 10.6.0, ConnectBot SSH library before 2.2.22, Apache MINA sshd through 2.11.0, sshj through 0.37.0, TinySSH through 20230101, trilead-ssh2 6401, LANCOM LCOS and LANconfig, FileZilla before 3.66.4, Nova before 11.8, PKIX-SSH before 14.4, SecureCRT before 9.4.3, Transmit5 before 5.10.4, Win32-OpenSSH before 9.5.0.0p1-Beta, WinSCP before 6.2.2, Bitvise SSH Server before 9.32, Bitvise SSH Client before 9.33, KiTTY through 0.76.1.13, the net-ssh gem 7.2.0 for Ruby, the mscdex ssh2 module before 1.15.0 for Node.js, the thrussh library before 0.35.1 for Rust, and the Russh crate before 0.40.2 for Rust.

Remediation

Upgrade Debian:unstable libssh2 to version 1.11.0-4 or higher.

References

Improper Validation of Integrity Check Value vulnerability report

medium severity

NULL Pointer Dereference

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.9.10+dfsg-6.6

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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:unstable 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:unstable libxml2 to version 2.9.10+dfsg-6.6 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity
new

Uncontrolled Recursion

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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:unstable relevant fixed versions and status.

A flaw was found in libxml2, an XML parsing library. This uncontrolled recursion vulnerability occurs in the xmlCatalogXMLResolveURI function when an XML catalog contains a delegate URI entry that references itself. A remote attacker could exploit this configuration-dependent issue by providing a specially crafted XML catalog, leading to infinite recursion and call stack exhaustion. This ultimately results in a segmentation fault, causing a Denial of Service (DoS) by crashing affected applications.

Remediation

There is no fixed version for Debian:unstable libxml2.

References

Uncontrolled Recursion vulnerability report

medium severity

Link Following

  • Vulnerable module: mercurial
  • Introduced through: mercurial@4.5-1 and mercurial/mercurial-common@4.5-1
  • Fixed in: 4.9-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › mercurial@4.5-1
  • Introduced through: openjdk@10-ea-jdk › mercurial/mercurial-common@4.5-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream mercurial package and not the mercurial package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw was found in Mercurial before 4.9. It was possible to use symlinks and subrepositories to defeat Mercurial's path-checking logic and write files outside a repository.

Remediation

Upgrade Debian:unstable mercurial to version 4.9-1 or higher.

References

Link Following vulnerability report

medium severity

CVE-2018-12404

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.36.1-1
  • Fixed in: 2:3.41-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nss/libnss3@2:3.36.1-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nss package and not the nss package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A cached side channel attack during handshakes using RSA encryption could allow for the decryption of encrypted content. This is a variant of the Adaptive Chosen Ciphertext attack (AKA Bleichenbacher attack) and affects all NSS versions prior to NSS 3.41.

Remediation

Upgrade Debian:unstable nss to version 2:3.41-1 or higher.

References

CVE-2018-12404 vulnerability report

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:7.6p1-4
  • Fixed in: 1:9.9p2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssh/openssh-client@1:7.6p1-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw was found in the OpenSSH package. For each ping packet the SSH server receives, a pong packet is allocated in a memory buffer and stored in a queue of packages. It is only freed when the server/client key exchange has finished. A malicious client may keep sending such packages, leading to an uncontrolled increase in memory consumption on the server side. Consequently, the server may become unavailable, resulting in a denial of service attack.

Remediation

Upgrade Debian:unstable openssh to version 1:9.9p2-1 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

medium severity

Directory Traversal

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:7.6p1-4
  • Fixed in: 1:7.9p1-9

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssh/openssh-client@1:7.6p1-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An issue was discovered in OpenSSH 7.9. Due to the scp implementation being derived from 1983 rcp, the server chooses which files/directories are sent to the client. However, the scp client only performs cursory validation of the object name returned (only directory traversal attacks are prevented). A malicious scp server (or Man-in-The-Middle attacker) can overwrite arbitrary files in the scp client target directory. If recursive operation (-r) is performed, the server can manipulate subdirectories as well (for example, to overwrite the .ssh/authorized_keys file).

Remediation

Upgrade Debian:unstable openssh to version 1:7.9p1-9 or higher.

References

Directory Traversal vulnerability report

medium severity

Improper Validation of Integrity Check Value

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:7.6p1-4
  • Fixed in: 1:9.6p1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssh/openssh-client@1:7.6p1-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 and other products, allows remote attackers to bypass integrity checks such that some packets are omitted (from the extension negotiation message), and a client and server may consequently end up with a connection for which some security features have been downgraded or disabled, aka a Terrapin attack. This occurs because the SSH Binary Packet Protocol (BPP), implemented by these extensions, mishandles the handshake phase and mishandles use of sequence numbers. For example, there is an effective attack against SSH's use of ChaCha20-Poly1305 (and CBC with Encrypt-then-MAC). The bypass occurs in chacha20-poly1305@openssh.com and (if CBC is used) the -etm@openssh.com MAC algorithms. This also affects Maverick Synergy Java SSH API before 3.1.0-SNAPSHOT, Dropbear through 2022.83, Ssh before 5.1.1 in Erlang/OTP, PuTTY before 0.80, AsyncSSH before 2.14.2, golang.org/x/crypto before 0.17.0, libssh before 0.10.6, libssh2 through 1.11.0, Thorn Tech SFTP Gateway before 3.4.6, Tera Term before 5.1, Paramiko before 3.4.0, jsch before 0.2.15, SFTPGo before 2.5.6, Netgate pfSense Plus through 23.09.1, Netgate pfSense CE through 2.7.2, HPN-SSH through 18.2.0, ProFTPD before 1.3.8b (and before 1.3.9rc2), ORYX CycloneSSH before 2.3.4, NetSarang XShell 7 before Build 0144, CrushFTP before 10.6.0, ConnectBot SSH library before 2.2.22, Apache MINA sshd through 2.11.0, sshj through 0.37.0, TinySSH through 20230101, trilead-ssh2 6401, LANCOM LCOS and LANconfig, FileZilla before 3.66.4, Nova before 11.8, PKIX-SSH before 14.4, SecureCRT before 9.4.3, Transmit5 before 5.10.4, Win32-OpenSSH before 9.5.0.0p1-Beta, WinSCP before 6.2.2, Bitvise SSH Server before 9.32, Bitvise SSH Client before 9.33, KiTTY through 0.76.1.13, the net-ssh gem 7.2.0 for Ruby, the mscdex ssh2 module before 1.15.0 for Node.js, the thrussh library before 0.35.1 for Rust, and the Russh crate before 0.40.2 for Rust.

Remediation

Upgrade Debian:unstable openssh to version 1:9.6p1-1 or higher.

References

Improper Validation of Integrity Check Value vulnerability report

medium severity

CVE-2021-4160

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 1.1.1m-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

There is a carry propagation bug in the MIPS32 and MIPS64 squaring procedure. Many EC algorithms are affected, including some of the TLS 1.3 default curves. Impact was not analyzed in detail, because the pre-requisites for attack are considered unlikely and include reusing private keys. Analysis suggests that attacks against RSA and DSA as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH are considered just feasible (although very difficult) because most of the work necessary to deduce information about a private key may be performed offline. The amount of resources required for such an attack would be significant. However, for an attack on TLS to be meaningful, the server would have to share the DH private key among multiple clients, which is no longer an option since CVE-2016-0701. This issue affects OpenSSL versions 1.0.2, 1.1.1 and 3.0.0. It was addressed in the releases of 1.1.1m and 3.0.1 on the 15th of December 2021. For the 1.0.2 release it is addressed in git commit 6fc1aaaf3 that is available to premium support customers only. It will be made available in 1.0.2zc when it is released. The issue only affects OpenSSL on MIPS platforms. Fixed in OpenSSL 3.0.1 (Affected 3.0.0). Fixed in OpenSSL 1.1.1m (Affected 1.1.1-1.1.1l). Fixed in OpenSSL 1.0.2zc-dev (Affected 1.0.2-1.0.2zb).

Remediation

Upgrade Debian:unstable openssl to version 1.1.1m-1 or higher.

References

CVE-2021-4160 vulnerability report

medium severity

Information Exposure

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 3.0.8-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A timing based side channel exists in the OpenSSL RSA Decryption implementation which could be sufficient to recover a plaintext across a network in a Bleichenbacher style attack. To achieve a successful decryption an attacker would have to be able to send a very large number of trial messages for decryption. The vulnerability affects all RSA padding modes: PKCS#1 v1.5, RSA-OEAP and RSASVE.

For example, in a TLS connection, RSA is commonly used by a client to send an encrypted pre-master secret to the server. An attacker that had observed a genuine connection between a client and a server could use this flaw to send trial messages to the server and record the time taken to process them. After a sufficiently large number of messages the attacker could recover the pre-master secret used for the original connection and thus be able to decrypt the application data sent over that connection.

Remediation

Upgrade Debian:unstable openssl to version 3.0.8-1 or higher.

References

Information Exposure vulnerability report

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 1.1.1j-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The OpenSSL public API function X509_issuer_and_serial_hash() attempts to create a unique hash value based on the issuer and serial number data contained within an X509 certificate. However it fails to correctly handle any errors that may occur while parsing the issuer field (which might occur if the issuer field is maliciously constructed). This may subsequently result in a NULL pointer deref and a crash leading to a potential denial of service attack. The function X509_issuer_and_serial_hash() is never directly called by OpenSSL itself so applications are only vulnerable if they use this function directly and they use it on certificates that may have been obtained from untrusted sources. OpenSSL versions 1.1.1i and below are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1j. OpenSSL versions 1.0.2x and below are affected by this issue. However OpenSSL 1.0.2 is out of support and no longer receiving public updates. Premium support customers of OpenSSL 1.0.2 should upgrade to 1.0.2y. Other users should upgrade to 1.1.1j. Fixed in OpenSSL 1.1.1j (Affected 1.1.1-1.1.1i). Fixed in OpenSSL 1.0.2y (Affected 1.0.2-1.0.2x).

Remediation

Upgrade Debian:unstable openssl to version 1.1.1j-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

medium severity

NULL Pointer Dereference

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 1.1.1i-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The X.509 GeneralName type is a generic type for representing different types of names. One of those name types is known as EDIPartyName. OpenSSL provides a function GENERAL_NAME_cmp which compares different instances of a GENERAL_NAME to see if they are equal or not. This function behaves incorrectly when both GENERAL_NAMEs contain an EDIPARTYNAME. A NULL pointer dereference and a crash may occur leading to a possible denial of service attack. OpenSSL itself uses the GENERAL_NAME_cmp function for two purposes: 1) Comparing CRL distribution point names between an available CRL and a CRL distribution point embedded in an X509 certificate 2) When verifying that a timestamp response token signer matches the timestamp authority name (exposed via the API functions TS_RESP_verify_response and TS_RESP_verify_token) If an attacker can control both items being compared then that attacker could trigger a crash. For example if the attacker can trick a client or server into checking a malicious certificate against a malicious CRL then this may occur. Note that some applications automatically download CRLs based on a URL embedded in a certificate. This checking happens prior to the signatures on the certificate and CRL being verified. OpenSSL's s_server, s_client and verify tools have support for the "-crl_download" option which implements automatic CRL downloading and this attack has been demonstrated to work against those tools. Note that an unrelated bug means that affected versions of OpenSSL cannot parse or construct correct encodings of EDIPARTYNAME. However it is possible to construct a malformed EDIPARTYNAME that OpenSSL's parser will accept and hence trigger this attack. All OpenSSL 1.1.1 and 1.0.2 versions are affected by this issue. Other OpenSSL releases are out of support and have not been checked. Fixed in OpenSSL 1.1.1i (Affected 1.1.1-1.1.1h). Fixed in OpenSSL 1.0.2x (Affected 1.0.2-1.0.2w).

Remediation

Upgrade Debian:unstable openssl to version 1.1.1i-1 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

NULL Pointer Dereference

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 1.1.1k-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An OpenSSL TLS server may crash if sent a maliciously crafted renegotiation ClientHello message from a client. If a TLSv1.2 renegotiation ClientHello omits the signature_algorithms extension (where it was present in the initial ClientHello), but includes a signature_algorithms_cert extension then a NULL pointer dereference will result, leading to a crash and a denial of service attack. A server is only vulnerable if it has TLSv1.2 and renegotiation enabled (which is the default configuration). OpenSSL TLS clients are not impacted by this issue. All OpenSSL 1.1.1 versions are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1-1.1.1j).

Remediation

Upgrade Debian:unstable openssl to version 1.1.1k-1 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

Out-of-bounds Read

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 3.0.9-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Issue summary: The AES-XTS cipher decryption implementation for 64 bit ARM platform contains a bug that could cause it to read past the input buffer, leading to a crash.

Impact summary: Applications that use the AES-XTS algorithm on the 64 bit ARM platform can crash in rare circumstances. The AES-XTS algorithm is usually used for disk encryption.

The AES-XTS cipher decryption implementation for 64 bit ARM platform will read past the end of the ciphertext buffer if the ciphertext size is 4 mod 5 in 16 byte blocks, e.g. 144 bytes or 1024 bytes. If the memory after the ciphertext buffer is unmapped, this will trigger a crash which results in a denial of service.

If an attacker can control the size and location of the ciphertext buffer being decrypted by an application using AES-XTS on 64 bit ARM, the application is affected. This is fairly unlikely making this issue a Low severity one.

Remediation

Upgrade Debian:unstable openssl to version 3.0.9-1 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 1.1.1a-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The OpenSSL DSA signature algorithm has been shown to be vulnerable to a timing side channel attack. An attacker could use variations in the signing algorithm to recover the private key. Fixed in OpenSSL 1.1.1a (Affected 1.1.1). Fixed in OpenSSL 1.1.0j (Affected 1.1.0-1.1.0i). Fixed in OpenSSL 1.0.2q (Affected 1.0.2-1.0.2p).

Remediation

Upgrade Debian:unstable openssl to version 1.1.1a-1 or higher.

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

medium severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 1.1.1a-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The OpenSSL ECDSA signature algorithm has been shown to be vulnerable to a timing side channel attack. An attacker could use variations in the signing algorithm to recover the private key. Fixed in OpenSSL 1.1.0j (Affected 1.1.0-1.1.0i). Fixed in OpenSSL 1.1.1a (Affected 1.1.1).

Remediation

Upgrade Debian:unstable openssl to version 1.1.1a-1 or higher.

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

medium severity

NULL Pointer Dereference

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1
  • Fixed in: 3.30.1+fossil191229-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

SQLite 3.30.1 mishandles pExpr->y.pTab, as demonstrated by the TK_COLUMN case in sqlite3ExprCodeTarget in expr.c.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.30.1+fossil191229-1 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

CVE-2023-7008

  • Vulnerable module: systemd
  • Introduced through: systemd@238-4, systemd/libnss-systemd@238-4 and others
  • Fixed in: 255.1-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libnss-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libpam-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libsystemd0@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libudev1@238-2
  • Introduced through: openjdk@10-ea-jdk › systemd/systemd-sysv@238-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A vulnerability was found in systemd-resolved. This issue may allow systemd-resolved to accept records of DNSSEC-signed domains even when they have no signature, allowing man-in-the-middles (or the upstream DNS resolver) to manipulate records.

Remediation

Upgrade Debian:unstable systemd to version 255.1-3 or higher.

References

CVE-2023-7008 vulnerability report

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: apt
  • Introduced through: apt@1.6~beta1 and apt/libapt-pkg5.0@1.6~beta1
  • Fixed in: 2.1.13

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › apt@1.6~beta1
  • Introduced through: openjdk@10-ea-jdk › apt/libapt-pkg5.0@1.6~beta1

NVD Description

Note: Versions mentioned in the description apply only to the upstream apt package and not the apt package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

APT had several integer overflows and underflows while parsing .deb packages, aka GHSL-2020-168 GHSL-2020-169, in files apt-pkg/contrib/extracttar.cc, apt-pkg/deb/debfile.cc, and apt-pkg/contrib/arfile.cc. This issue affects: apt 1.2.32ubuntu0 versions prior to 1.2.32ubuntu0.2; 1.6.12ubuntu0 versions prior to 1.6.12ubuntu0.2; 2.0.2ubuntu0 versions prior to 2.0.2ubuntu0.2; 2.1.10ubuntu0 versions prior to 2.1.10ubuntu0.1;

Remediation

Upgrade Debian:unstable apt to version 2.1.13 or higher.

References

Integer Overflow or Wraparound vulnerability report

medium severity

Insufficiently Protected Credentials

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.83.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable 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:unstable curl to version 7.83.0-1 or higher.

References

Insufficiently Protected Credentials vulnerability report

medium severity

Information Exposure

  • Vulnerable module: nettle/libhogweed4
  • Introduced through: nettle/libhogweed4@3.4-1 and nettle/libnettle6@3.4-1
  • Fixed in: 3.4.1~rc1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nettle/libhogweed4@3.4-1
  • Introduced through: openjdk@10-ea-jdk › nettle/libnettle6@3.4-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nettle package and not the nettle package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A Bleichenbacher type side-channel based padding oracle attack was found in the way nettle handles endian conversion of RSA decrypted PKCS#1 v1.5 data. An attacker who is able to run a process on the same physical core as the victim process, could use this flaw extract plaintext or in some cases downgrade any TLS connections to a vulnerable server.

Remediation

Upgrade Debian:unstable nettle to version 3.4.1~rc1-1 or higher.

References

Information Exposure vulnerability report

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.56.1-2 and glib2.0/libglib2.0-data@2.56.1-2
  • Fixed in: 2.86.3-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-0@2.56.1-2
  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-data@2.56.1-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw was found in GLib (Gnome Lib). This vulnerability allows a remote attacker to cause heap corruption, leading to a denial of service or potential code execution via a buffer-underflow in the GVariant parser when processing maliciously crafted input strings.

Remediation

Upgrade Debian:unstable glib2.0 to version 2.86.3-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

medium severity

Information Exposure

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.18-1
  • Fixed in: 3.6.5-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gnutls28/libgnutls30@3.5.18-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A Bleichenbacher type side-channel based padding oracle attack was found in the way gnutls handles verification of RSA decrypted PKCS#1 v1.5 data. An attacker who is able to run process on the same physical core as the victim process, could use this to extract plaintext or in some cases downgrade any TLS connections to a vulnerable server.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.6.5-2 or higher.

References

Information Exposure vulnerability report

medium severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.18-1
  • Fixed in: 3.5.19-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gnutls28/libgnutls30@3.5.18-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A cache-based side channel in GnuTLS implementation that leads to plain text recovery in cross-VM attack setting was found. An attacker could use a combination of "Just in Time" Prime+probe attack in combination with Lucky-13 attack to recover plain text using crafted packets.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.5.19-1 or higher.

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

medium severity

Incorrect Permission Assignment for Critical Resource

  • Vulnerable module: apr/libapr1
  • Introduced through: apr/libapr1@1.6.3-2
  • Fixed in: 1.7.5-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › apr/libapr1@1.6.3-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream apr package and not the apr package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Lax permissions set by the Apache Portable Runtime library on Unix platforms would allow local users read access to named shared memory segments, potentially revealing sensitive application data.

This issue does not affect non-Unix platforms, or builds with APR_USE_SHMEM_SHMGET=1 (apr.h)

Users are recommended to upgrade to APR version 1.7.5, which fixes this issue.

Remediation

Upgrade Debian:unstable apr to version 1.7.5-1 or higher.

References

Incorrect Permission Assignment for Critical Resource vulnerability report

medium severity

Improper Input Validation

  • Vulnerable module: apt
  • Introduced through: apt@1.6~beta1 and apt/libapt-pkg5.0@1.6~beta1
  • Fixed in: 2.1.2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › apt@1.6~beta1
  • Introduced through: openjdk@10-ea-jdk › apt/libapt-pkg5.0@1.6~beta1

NVD Description

Note: Versions mentioned in the description apply only to the upstream apt package and not the apt package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Missing input validation in the ar/tar implementations of APT before version 2.1.2 could result in denial of service when processing specially crafted deb files.

Remediation

Upgrade Debian:unstable apt to version 2.1.2 or higher.

References

Improper Input Validation vulnerability report

medium severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: avahi/libavahi-client3
  • Introduced through: avahi/libavahi-client3@0.7-3.1, avahi/libavahi-common-data@0.7-3.1 and others
  • Fixed in: 0.8-7

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-client3@0.7-3.1
  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-common-data@0.7-3.1
  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-common3@0.7-3.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream avahi package and not the avahi package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw was found in avahi in versions 0.6 up to 0.8. The event used to signal the termination of the client connection on the avahi Unix socket is not correctly handled in the client_work function, allowing a local attacker to trigger an infinite loop. The highest threat from this vulnerability is to the availability of the avahi service, which becomes unresponsive after this flaw is triggered.

Remediation

Upgrade Debian:unstable avahi to version 0.8-7 or higher.

References

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability report

medium severity

NULL Pointer Dereference

  • Vulnerable module: avahi/libavahi-client3
  • Introduced through: avahi/libavahi-client3@0.7-3.1, avahi/libavahi-common-data@0.7-3.1 and others
  • Fixed in: 0.8-6

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-client3@0.7-3.1
  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-common-data@0.7-3.1
  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-common3@0.7-3.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream avahi package and not the avahi package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw was found in avahi 0.8-5. A reachable assertion is present in avahi_s_host_name_resolver_start function allowing a local attacker to crash the avahi service by requesting hostname resolutions through the avahi socket or dbus methods for invalid hostnames. The highest threat from this vulnerability is to the service availability.

Remediation

Upgrade Debian:unstable avahi to version 0.8-6 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

Reachable Assertion

  • Vulnerable module: avahi/libavahi-client3
  • Introduced through: avahi/libavahi-client3@0.7-3.1, avahi/libavahi-common-data@0.7-3.1 and others
  • Fixed in: 0.8-14

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-client3@0.7-3.1
  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-common-data@0.7-3.1
  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-common3@0.7-3.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream avahi package and not the avahi package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A vulnerability was found in Avahi, where a reachable assertion exists in avahi_dns_packet_append_record.

Remediation

Upgrade Debian:unstable avahi to version 0.8-14 or higher.

References

Reachable Assertion vulnerability report

medium severity

Reachable Assertion

  • Vulnerable module: avahi/libavahi-client3
  • Introduced through: avahi/libavahi-client3@0.7-3.1, avahi/libavahi-common-data@0.7-3.1 and others
  • Fixed in: 0.8-14

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-client3@0.7-3.1
  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-common-data@0.7-3.1
  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-common3@0.7-3.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream avahi package and not the avahi package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A vulnerability was found in Avahi. A reachable assertion exists in the avahi_escape_label() function.

Remediation

Upgrade Debian:unstable avahi to version 0.8-14 or higher.

References

Reachable Assertion vulnerability report

medium severity

Reachable Assertion

  • Vulnerable module: avahi/libavahi-client3
  • Introduced through: avahi/libavahi-client3@0.7-3.1, avahi/libavahi-common-data@0.7-3.1 and others
  • Fixed in: 0.8-14

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-client3@0.7-3.1
  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-common-data@0.7-3.1
  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-common3@0.7-3.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream avahi package and not the avahi package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A vulnerability was found in Avahi. A reachable assertion exists in the avahi_rdata_parse() function.

Remediation

Upgrade Debian:unstable avahi to version 0.8-14 or higher.

References

Reachable Assertion vulnerability report

medium severity

Reachable Assertion

  • Vulnerable module: avahi/libavahi-client3
  • Introduced through: avahi/libavahi-client3@0.7-3.1, avahi/libavahi-common-data@0.7-3.1 and others
  • Fixed in: 0.8-14

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-client3@0.7-3.1
  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-common-data@0.7-3.1
  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-common3@0.7-3.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream avahi package and not the avahi package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A vulnerability was found in Avahi. A reachable assertion exists in the dbus_set_host_name function.

Remediation

Upgrade Debian:unstable avahi to version 0.8-14 or higher.

References

Reachable Assertion vulnerability report

medium severity

Reachable Assertion

  • Vulnerable module: avahi/libavahi-client3
  • Introduced through: avahi/libavahi-client3@0.7-3.1, avahi/libavahi-common-data@0.7-3.1 and others
  • Fixed in: 0.8-14

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-client3@0.7-3.1
  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-common-data@0.7-3.1
  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-common3@0.7-3.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream avahi package and not the avahi package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A vulnerability was found in Avahi. A reachable assertion exists in the avahi_alternative_host_name() function.

Remediation

Upgrade Debian:unstable avahi to version 0.8-14 or higher.

References

Reachable Assertion vulnerability report

medium severity

Resource Exhaustion

  • Vulnerable module: avahi/libavahi-client3
  • Introduced through: avahi/libavahi-client3@0.7-3.1, avahi/libavahi-common-data@0.7-3.1 and others
  • Fixed in: 0.8-10

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-client3@0.7-3.1
  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-common-data@0.7-3.1
  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-common3@0.7-3.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream avahi package and not the avahi package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A vulnerability was found in the avahi library. This flaw allows an unprivileged user to make a dbus call, causing the avahi daemon to crash.

Remediation

Upgrade Debian:unstable avahi to version 0.8-10 or higher.

References

Resource Exhaustion vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: coreutils
  • Introduced through: coreutils@8.28-1
  • Fixed in: 9.5-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › coreutils@8.28-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream coreutils package and not the coreutils package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw was found in the GNU coreutils "split" program. A heap overflow with user-controlled data of multiple hundred bytes in length could occur in the line_bytes_split() function, potentially leading to an application crash and denial of service.

Remediation

Upgrade Debian:unstable coreutils to version 9.5-1 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

CVE-2018-4181

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.7-3
  • Fixed in: 2.2.8-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › cups/libcups2@2.2.7-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream cups package and not the cups package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In macOS High Sierra before 10.13.5, an issue existed in CUPS. This issue was addressed with improved access restrictions.

Remediation

Upgrade Debian:unstable cups to version 2.2.8-2 or higher.

References

CVE-2018-4181 vulnerability report

medium severity

CVE-2023-32360

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.7-3
  • Fixed in: 2.4.2-6

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › cups/libcups2@2.2.7-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream cups package and not the cups package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An authentication issue was addressed with improved state management. This issue is fixed in macOS Big Sur 11.7.7, macOS Monterey 12.6.6, macOS Ventura 13.4. An unauthenticated user may be able to access recently printed documents.

Remediation

Upgrade Debian:unstable cups to version 2.4.2-6 or higher.

References

CVE-2023-32360 vulnerability report

medium severity

Improper Input Validation

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.7-3
  • Fixed in: 2.3.3op2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › cups/libcups2@2.2.7-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream cups package and not the cups package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An input validation issue was addressed with improved memory handling. This issue is fixed in macOS Big Sur 11.1, Security Update 2020-001 Catalina, Security Update 2020-007 Mojave. A malicious application may be able to read restricted memory.

Remediation

Upgrade Debian:unstable cups to version 2.3.3op2-1 or higher.

References

Improper Input Validation vulnerability report

medium severity

Out-of-bounds Read

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.7-3
  • Fixed in: 2.2.12-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › cups/libcups2@2.2.7-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream cups package and not the cups package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In ippSetValueTag of ipp.c in Android 8.0, 8.1 and 9, there is a possible out of bounds read due to improper input validation. This could lead to local information disclosure from the printer service with no additional execution privileges needed. User interaction is not needed for exploitation.

Remediation

Upgrade Debian:unstable cups to version 2.2.12-1 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Out-of-bounds Read

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.7-3
  • Fixed in: 2.3.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › cups/libcups2@2.2.7-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream cups package and not the cups package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In array_find of array.c, there is a possible out-of-bounds read due to an incorrect bounds check. This could lead to local information disclosure in the printer spooler with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-8.0 Android-8.1 Android-9 Android-10Android ID: A-111210196

Remediation

Upgrade Debian:unstable cups to version 2.3.1-1 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.7-3
  • Fixed in: 2.4.2-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › cups/libcups2@2.2.7-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream cups package and not the cups package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

OpenPrinting CUPS is an open source printing system. In versions 2.4.2 and prior, a heap buffer overflow vulnerability would allow a remote attacker to launch a denial of service (DoS) attack. A buffer overflow vulnerability in the function format_log_line could allow remote attackers to cause a DoS on the affected system. Exploitation of the vulnerability can be triggered when the configuration file cupsd.conf sets the value of loglevel to DEBUG. No known patches or workarounds exist at time of publication.

Remediation

Upgrade Debian:unstable cups to version 2.4.2-4 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Resource Exhaustion

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.7-3
  • Fixed in: 2.4.15-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › cups/libcups2@2.2.7-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream cups package and not the cups package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

OpenPrinting CUPS is an open source printing system for Linux and other Unix-like operating systems. Prior to version 2.4.15, a client that connects to cupsd but sends slow messages, e.g. only one byte per second, delays cupsd as a whole, such that it becomes unusable by other clients. This issue has been patched in version 2.4.15.

Remediation

Upgrade Debian:unstable cups to version 2.4.15-1 or higher.

References

Resource Exhaustion vulnerability report

medium severity

Improper Authentication

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.88.1-7

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable 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:unstable curl to version 7.88.1-7 or higher.

References

Improper Authentication vulnerability report

medium severity

Improper Resource Shutdown or Release

  • Vulnerable module: dbus
  • Introduced through: dbus@1.12.6-2, dbus/dbus-user-session@1.12.6-2 and others
  • Fixed in: 1.12.18-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › dbus@1.12.6-2
  • Introduced through: openjdk@10-ea-jdk › dbus/dbus-user-session@1.12.6-2
  • Introduced through: openjdk@10-ea-jdk › dbus/libdbus-1-3@1.12.6-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream dbus package and not the dbus package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An issue was discovered in dbus >= 1.3.0 before 1.12.18. The DBusServer in libdbus, as used in dbus-daemon, leaks file descriptors when a message exceeds the per-message file descriptor limit. A local attacker with access to the D-Bus system bus or another system service's private AF_UNIX socket could use this to make the system service reach its file descriptor limit, denying service to subsequent D-Bus clients.

Remediation

Upgrade Debian:unstable dbus to version 1.12.18-1 or higher.

References

Improper Resource Shutdown or Release vulnerability report

medium severity

Out-of-Bounds

  • Vulnerable module: elfutils/libelf1
  • Introduced through: elfutils/libelf1@0.170-0.3
  • Fixed in: 0.175-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › elfutils/libelf1@0.170-0.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream elfutils package and not the elfutils package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An invalid memory address dereference was discovered in dwfl_segment_report_module.c in libdwfl in elfutils through v0.174. The vulnerability allows attackers to cause a denial of service (application crash) with a crafted ELF file, as demonstrated by consider_notes.

Remediation

Upgrade Debian:unstable elfutils to version 0.175-1 or higher.

References

Out-of-Bounds vulnerability report

medium severity

Out-of-bounds Read

  • Vulnerable module: elfutils/libelf1
  • Introduced through: elfutils/libelf1@0.170-0.3
  • Fixed in: 0.175-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › elfutils/libelf1@0.170-0.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream elfutils package and not the elfutils package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

dwarf_getaranges in dwarf_getaranges.c in libdw in elfutils before 2018-08-18 allows remote attackers to cause a denial of service (heap-based buffer over-read) via a crafted file.

Remediation

Upgrade Debian:unstable elfutils to version 0.175-1 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Out-of-bounds Read

  • Vulnerable module: elfutils/libelf1
  • Introduced through: elfutils/libelf1@0.170-0.3
  • Fixed in: 0.176-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › elfutils/libelf1@0.170-0.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream elfutils package and not the elfutils package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In elfutils 0.175, there is a buffer over-read in the ebl_object_note function in eblobjnote.c in libebl. Remote attackers could leverage this vulnerability to cause a denial-of-service via a crafted elf file, as demonstrated by eu-readelf.

Remediation

Upgrade Debian:unstable elfutils to version 0.176-1 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: elfutils/libelf1
  • Introduced through: elfutils/libelf1@0.170-0.3
  • Fixed in: 0.180-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › elfutils/libelf1@0.170-0.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream elfutils package and not the elfutils package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The libcpu component which is used by libasm of elfutils version 0.177 (git 47780c9e), suffers from denial-of-service vulnerability caused by application crashes due to out-of-bounds write (CWE-787), off-by-one error (CWE-193) and reachable assertion (CWE-617); to exploit the vulnerability, the attackers need to craft certain ELF files which bypass the missing bound checks.

Remediation

Upgrade Debian:unstable elfutils to version 0.180-1 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Algorithmic Complexity

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.5-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › expat/libexpat1@2.2.5-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In libexpat through 2.7.3, a crafted file with an approximate size of 2 MiB can lead to dozens of seconds of processing time.

Remediation

There is no fixed version for Debian:unstable expat.

References

Algorithmic Complexity vulnerability report

medium severity

Heap-based Buffer Overflow

  • Vulnerable module: fribidi/libfribidi0
  • Introduced through: fribidi/libfribidi0@0.19.7-2
  • Fixed in: 1.0.8-2.1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › fribidi/libfribidi0@0.19.7-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream fribidi package and not the fribidi package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A heap-based buffer overflow flaw was found in the Fribidi package and affects the fribidi_cap_rtl_to_unicode() function of the fribidi-char-sets-cap-rtl.c file. This flaw allows an attacker to pass a specially crafted file to the Fribidi application with the '--caprtl' option, leading to a crash and causing a denial of service.

Remediation

Upgrade Debian:unstable fribidi to version 1.0.8-2.1 or higher.

References

Heap-based Buffer Overflow vulnerability report

medium severity

NULL Pointer Dereference

  • Vulnerable module: fribidi/libfribidi0
  • Introduced through: fribidi/libfribidi0@0.19.7-2
  • Fixed in: 1.0.8-2.1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › fribidi/libfribidi0@0.19.7-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream fribidi package and not the fribidi package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A segmentation fault (SEGV) flaw was found in the Fribidi package and affects the fribidi_remove_bidi_marks() function of the lib/fribidi.c file. This flaw allows an attacker to pass a specially crafted file to Fribidi, leading to a crash and causing a denial of service.

Remediation

Upgrade Debian:unstable fribidi to version 1.0.8-2.1 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: gdk-pixbuf/libgdk-pixbuf2.0-0
  • Introduced through: gdk-pixbuf/libgdk-pixbuf2.0-0@2.36.11-2, gdk-pixbuf/libgdk-pixbuf2.0-bin@2.36.11-2 and others
  • Fixed in: 2.42.2+dfsg-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gdk-pixbuf/libgdk-pixbuf2.0-0@2.36.11-2
  • Introduced through: openjdk@10-ea-jdk › gdk-pixbuf/libgdk-pixbuf2.0-bin@2.36.11-2
  • Introduced through: openjdk@10-ea-jdk › gdk-pixbuf/libgdk-pixbuf2.0-common@2.36.11-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream gdk-pixbuf package and not the gdk-pixbuf package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

GNOME gdk-pixbuf (aka GdkPixbuf) before 2.42.2 allows a denial of service (infinite loop) in lzw.c in the function write_indexes. if c->self_code equals 10, self->code_table[10].extends will assign the value 11 to c. The next execution in the loop will assign self->code_table[11].extends to c, which will give the value of 10. This will make the loop run infinitely. This bug can, for example, be triggered by calling this function with a GIF image with LZW compression that is crafted in a special way.

Remediation

Upgrade Debian:unstable gdk-pixbuf to version 2.42.2+dfsg-1 or higher.

References

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability report

medium severity

Out-of-Bounds

  • Vulnerable module: giflib/libgif7
  • Introduced through: giflib/libgif7@5.1.4-2
  • Fixed in: 5.1.4-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › giflib/libgif7@5.1.4-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream giflib package and not the giflib package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Heap-based buffer overflow in util/gif2rgb.c in gif2rgb in giflib 5.1.2 allows remote attackers to cause a denial of service (application crash) via the background color index in a GIF file.

Remediation

Upgrade Debian:unstable giflib to version 5.1.4-3 or higher.

References

Out-of-Bounds vulnerability report

medium severity

Link Following

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.38.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Git is an open source, scalable, distributed revision control system. Versions prior to 2.30.6, 2.31.5, 2.32.4, 2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4 are subject to exposure of sensitive information to a malicious actor. When performing a local clone (where the source and target of the clone are on the same volume), Git copies the contents of the source's $GIT_DIR/objects directory into the destination by either creating hardlinks to the source contents, or copying them (if hardlinks are disabled via --no-hardlinks). A malicious actor could convince a victim to clone a repository with a symbolic link pointing at sensitive information on the victim's machine. This can be done either by having the victim clone a malicious repository on the same machine, or having them clone a malicious repository embedded as a bare repository via a submodule from any source, provided they clone with the --recurse-submodules option. Git does not create symbolic links in the $GIT_DIR/objects directory. The problem has been patched in the versions published on 2022-10-18, and backported to v2.30.x. Potential workarounds: Avoid cloning untrusted repositories using the --local optimization when on a shared machine, either by passing the --no-local option to git clone or cloning from a URL that uses the file:// scheme. Alternatively, avoid cloning repositories from untrusted sources with --recurse-submodules or run git config --global protocol.file.allow user.

Remediation

Upgrade Debian:unstable git to version 1:2.38.1-1 or higher.

References

Link Following vulnerability report

medium severity

Link Following

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.39.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Git is a revision control system. Using a specially-crafted repository, Git prior to versions 2.39.2, 2.38.4, 2.37.6, 2.36.5, 2.35.7, 2.34.7, 2.33.7, 2.32.6, 2.31.7, and 2.30.8 can be tricked into using its local clone optimization even when using a non-local transport. Though Git will abort local clones whose source $GIT_DIR/objects directory contains symbolic links, the objects directory itself may still be a symbolic link. These two may be combined to include arbitrary files based on known paths on the victim's filesystem within the malicious repository's working copy, allowing for data exfiltration in a similar manner as CVE-2022-39253.

A fix has been prepared and will appear in v2.39.2 v2.38.4 v2.37.6 v2.36.5 v2.35.7 v2.34.7 v2.33.7 v2.32.6, v2.31.7 and v2.30.8. If upgrading is impractical, two short-term workarounds are available. Avoid cloning repositories from untrusted sources with --recurse-submodules. Instead, consider cloning repositories without recursively cloning their submodules, and instead run git submodule update at each layer. Before doing so, inspect each new .gitmodules file to ensure that it does not contain suspicious module URLs.

Remediation

Upgrade Debian:unstable git to version 1:2.39.2-1 or higher.

References

Link Following vulnerability report

medium severity

Deserialization of Untrusted Data

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.56.1-2 and glib2.0/libglib2.0-data@2.56.1-2
  • Fixed in: 2.74.4-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-0@2.56.1-2
  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-data@2.56.1-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw was found in GLib. GVariant deserialization is vulnerable to an exponential blowup issue where a crafted GVariant can cause excessive processing, leading to denial of service.

Remediation

Upgrade Debian:unstable glib2.0 to version 2.74.4-1 or higher.

References

Deserialization of Untrusted Data vulnerability report

medium severity

Information Exposure

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.56.1-2 and glib2.0/libglib2.0-data@2.56.1-2
  • Fixed in: 2.64.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-0@2.56.1-2
  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-data@2.56.1-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw was found in glib before version 2.63.6. Due to random charset alias, pkexec can leak content from files owned by privileged users to unprivileged ones under the right condition.

Remediation

Upgrade Debian:unstable glib2.0 to version 2.64.0-1 or higher.

References

Information Exposure vulnerability report

medium severity

Resource Exhaustion

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.56.1-2 and glib2.0/libglib2.0-data@2.56.1-2
  • Fixed in: 2.74.4-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-0@2.56.1-2
  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-data@2.56.1-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw was found in GLib. GVariant deserialization is vulnerable to a slowdown issue where a crafted GVariant can cause excessive processing, leading to denial of service.

Remediation

Upgrade Debian:unstable glib2.0 to version 2.74.4-1 or higher.

References

Resource Exhaustion vulnerability report

medium severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2
  • Fixed in: 2.31-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The iconv function in the GNU C Library (aka glibc or libc6) 2.32 and earlier, when processing invalid multi-byte input sequences in IBM1364, IBM1371, IBM1388, IBM1390, and IBM1399 encodings, fails to advance the input state, which could lead to an infinite loop in applications, resulting in a denial of service, a different vulnerability from CVE-2016-10228.

Remediation

Upgrade Debian:unstable glibc to version 2.31-5 or higher.

References

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability report

medium severity

Out-of-Bounds

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2
  • Fixed in: 2.30-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The GNU C Library (aka glibc or libc6) before 2.32 could overflow an on-stack buffer during range reduction if an input to an 80-bit long double function contains a non-canonical bit pattern, a seen when passing a 0x5d414141414141410000 value to sinl on x86 targets. This is related to sysdeps/ieee754/ldbl-96/e_rem_pio2l.c.

Remediation

Upgrade Debian:unstable glibc to version 2.30-1 or higher.

References

Out-of-Bounds vulnerability report

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: harfbuzz/libharfbuzz0b
  • Introduced through: harfbuzz/libharfbuzz0b@1.7.6-1
  • Fixed in: 5.2.0-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › harfbuzz/libharfbuzz0b@1.7.6-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream harfbuzz package and not the harfbuzz package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An integer overflow in the component hb-ot-shape-fallback.cc of Harfbuzz v4.3.0 allows attackers to cause a Denial of Service (DoS) via unspecified vectors.

Remediation

Upgrade Debian:unstable harfbuzz to version 5.2.0-2 or higher.

References

Integer Overflow or Wraparound vulnerability report

medium severity

Use After Free

  • Vulnerable module: icu/libicu57
  • Introduced through: icu/libicu57@57.1-9
  • Fixed in: 67.1-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › icu/libicu57@57.1-9

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:unstable 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:unstable icu to version 67.1-2 or higher.

References

Use After Free vulnerability report

medium severity

Memory Leak

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.16-2, krb5/libk5crypto3@1.16-2 and others
  • Fixed in: 1.21.3-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › krb5/libgssapi-krb5-2@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libk5crypto3@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libkrb5-3@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libkrb5support0@1.16-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Kerberos 5 (aka krb5) 1.21.2 contains a memory leak vulnerability in /krb5/src/kdc/ndr.c.

Remediation

Upgrade Debian:unstable krb5 to version 1.21.3-1 or higher.

References

Memory Leak vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: lcms2/liblcms2-2
  • Introduced through: lcms2/liblcms2-2@2.9-1
  • Fixed in: 2.9-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › lcms2/liblcms2-2@2.9-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream lcms2 package and not the lcms2 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Little CMS (aka Little Color Management System) 2.9 has an integer overflow in the AllocateDataSet function in cmscgats.c, leading to a heap-based buffer overflow in the SetData function via a crafted file in the second argument to cmsIT8LoadFromFile.

Remediation

Upgrade Debian:unstable lcms2 to version 2.9-3 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

NULL Pointer Dereference

  • Vulnerable module: libjpeg-turbo/libjpeg62-turbo
  • Introduced through: libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+b1
  • Fixed in: 1:2.0.6-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+b1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libjpeg-turbo package and not the libjpeg-turbo package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A crafted input file could cause a null pointer dereference in jcopy_sample_rows() when processed by libjpeg-turbo.

Remediation

Upgrade Debian:unstable libjpeg-turbo to version 1:2.0.6-1 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: libjpeg-turbo/libjpeg62-turbo
  • Introduced through: libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+b1
  • Fixed in: 1:2.1.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+b1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libjpeg-turbo package and not the libjpeg-turbo package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The PPM reader in libjpeg-turbo through 2.0.90 mishandles use of tjLoadImage for loading a 16-bit binary PPM file into a grayscale buffer and loading a 16-bit binary PGM file into an RGB buffer. This is related to a heap-based buffer overflow in the get_word_rgb_row function in rdppm.c.

Remediation

Upgrade Debian:unstable libjpeg-turbo to version 1:2.1.1-1 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Directory Traversal

  • Vulnerable module: librsvg/librsvg2-2
  • Introduced through: librsvg/librsvg2-2@2.40.20-2 and librsvg/librsvg2-common@2.40.20-2
  • Fixed in: 2.54.7+dfsg-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › librsvg/librsvg2-2@2.40.20-2
  • Introduced through: openjdk@10-ea-jdk › librsvg/librsvg2-common@2.40.20-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream librsvg package and not the librsvg package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A directory traversal problem in the URL decoder of librsvg before 2.56.3 could be used by local or remote attackers to disclose files (on the local filesystem outside of the expected area), as demonstrated by href=".?../../../../../../../../../../etc/passwd" in an xi:include element.

Remediation

Upgrade Debian:unstable librsvg to version 2.54.7+dfsg-1 or higher.

References

Directory Traversal vulnerability report

medium severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: libx11/libx11-6
  • Introduced through: libx11/libx11-6@2:1.6.5-1, libx11/libx11-data@2:1.6.5-1 and others
  • Fixed in: 2:1.8.7-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-6@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-data@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-dev@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-doc@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-xcb1@2:1.6.5-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libx11 package and not the libx11 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A vulnerability was found in libX11 due to an infinite loop within the PutSubImage() function. This flaw allows a local user to consume all available system resources and cause a denial of service condition.

Remediation

Upgrade Debian:unstable libx11 to version 2:1.8.7-1 or higher.

References

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability report

medium severity

Out-of-bounds Read

  • Vulnerable module: libx11/libx11-6
  • Introduced through: libx11/libx11-6@2:1.6.5-1, libx11/libx11-data@2:1.6.5-1 and others
  • Fixed in: 2:1.8.7-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-6@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-data@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-dev@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-doc@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-xcb1@2:1.6.5-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libx11 package and not the libx11 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A vulnerability was found in libX11 due to a boundary condition within the _XkbReadKeySyms() function. This flaw allows a local user to trigger an out-of-bounds read error and read the contents of memory on the system.

Remediation

Upgrade Debian:unstable libx11 to version 2:1.8.7-1 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

CVE-2025-9714

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.14.5+dfsg-0.1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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:unstable relevant fixed versions and status.

Uncontrolled recursion in XPath evaluation in libxml2 up to and including version 2.9.14 allows a local attacker to cause a stack overflow via crafted expressions. XPath processing functions xmlXPathRunEval, xmlXPathCtxtCompile, and xmlXPathEvalExpr were resetting recursion depth to zero before making potentially recursive calls. When such functions were called recursively this could allow for uncontrolled recursion and lead to a stack overflow. These functions now preserve recursion depth across recursive calls, allowing recursion depth to be controlled.

Remediation

Upgrade Debian:unstable libxml2 to version 2.14.5+dfsg-0.1 or higher.

References

CVE-2025-9714 vulnerability report

medium severity

XML External Entity (XXE) Injection

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.9.10+dfsg-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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:unstable 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

Upgrade Debian:unstable libxml2 to version 2.9.10+dfsg-2 or higher.

References

XML External Entity (XXE) Injection vulnerability report

medium severity

Out-of-bounds Read

  • Vulnerable module: libxpm/libxpm4
  • Introduced through: libxpm/libxpm4@1:3.5.12-1
  • Fixed in: 1:3.5.17-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › 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:unstable 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:unstable libxpm to version 1:3.5.17-1 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Out-of-bounds Read

  • Vulnerable module: libxpm/libxpm4
  • Introduced through: libxpm/libxpm4@1:3.5.12-1
  • Fixed in: 1:3.5.17-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › 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:unstable 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:unstable libxpm to version 1:3.5.17-1 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

CVE-2023-51384

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:7.6p1-4
  • Fixed in: 1:9.6p1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssh/openssh-client@1:7.6p1-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In ssh-agent in OpenSSH before 9.6, certain destination constraints can be incompletely applied. When destination constraints are specified during addition of PKCS#11-hosted private keys, these constraints are only applied to the first key, even if a PKCS#11 token returns multiple keys.

Remediation

Upgrade Debian:unstable openssh to version 1:9.6p1-1 or higher.

References

CVE-2023-51384 vulnerability report

medium severity

CVE-2024-0727

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 3.1.5-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Issue summary: Processing a maliciously formatted PKCS12 file may lead OpenSSL to crash leading to a potential Denial of Service attack

Impact summary: Applications loading files in the PKCS12 format from untrusted sources might terminate abruptly.

A file in PKCS12 format can contain certificates and keys and may come from an untrusted source. The PKCS12 specification allows certain fields to be NULL, but OpenSSL does not correctly check for this case. This can lead to a NULL pointer dereference that results in OpenSSL crashing. If an application processes PKCS12 files from an untrusted source using the OpenSSL APIs then that application will be vulnerable to this issue.

OpenSSL APIs that are vulnerable to this are: PKCS12_parse(), PKCS12_unpack_p7data(), PKCS12_unpack_p7encdata(), PKCS12_unpack_authsafes() and PKCS12_newpass().

We have also fixed a similar issue in SMIME_write_PKCS7(). However since this function is related to writing data we do not consider it security significant.

The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue.

Remediation

Upgrade Debian:unstable openssl to version 3.1.5-1 or higher.

References

CVE-2024-0727 vulnerability report

medium severity

CVE-2024-22365

  • Vulnerable module: pam/libpam-modules
  • Introduced through: pam/libpam-modules@1.1.8-3.7, pam/libpam-modules-bin@1.1.8-3.7 and others
  • Fixed in: 1.5.3-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › pam/libpam-modules@1.1.8-3.7
  • Introduced through: openjdk@10-ea-jdk › pam/libpam-modules-bin@1.1.8-3.7
  • Introduced through: openjdk@10-ea-jdk › pam/libpam-runtime@1.1.8-3.7
  • Introduced through: openjdk@10-ea-jdk › pam/libpam0g@1.1.8-3.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream pam package and not the pam package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

linux-pam (aka Linux PAM) before 1.6.0 allows attackers to cause a denial of service (blocked login process) via mkfifo because the openat call (for protect_dir) lacks O_DIRECTORY.

Remediation

Upgrade Debian:unstable pam to version 1.5.3-4 or higher.

References

CVE-2024-22365 vulnerability report

medium severity

Improper Authentication

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.5-1 and shadow/passwd@1:4.5-1
  • Fixed in: 1:4.13+dfsg1-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › shadow/login@1:4.5-1
  • Introduced through: openjdk@10-ea-jdk › shadow/passwd@1:4.5-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream shadow package and not the shadow package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw was found in shadow-utils. When asking for a new password, shadow-utils asks the password twice. If the password fails on the second attempt, shadow-utils fails in cleaning the buffer used to store the first entry. This may allow an attacker with enough access to retrieve the password from the memory.

Remediation

Upgrade Debian:unstable shadow to version 1:4.13+dfsg1-2 or higher.

References

Improper Authentication vulnerability report

medium severity

Buffer Overflow

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1
  • Fixed in: 3.27.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Buffer Overflow vulnerability found in SQLite3 v.3.27.1 and before allows a local attacker to cause a denial of service via a crafted script.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.27.2-1 or higher.

References

Buffer Overflow vulnerability report

medium severity

CVE-2020-13631

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1
  • Fixed in: 3.32.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

SQLite before 3.32.0 allows a virtual table to be renamed to the name of one of its shadow tables, related to alter.c and build.c.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.32.0-1 or higher.

References

CVE-2020-13631 vulnerability report

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1
  • Fixed in: 3.32.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

SQLite through 3.32.0 has an integer overflow in sqlite3_str_vappendf in printf.c.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.32.1-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

medium severity

NULL Pointer Dereference

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1
  • Fixed in: 3.32.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

SQLite through 3.32.0 has a segmentation fault in sqlite3ExprCodeTarget in expr.c.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.32.1-1 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

NULL Pointer Dereference

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1
  • Fixed in: 3.32.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

ext/fts3/fts3_snippet.c in SQLite before 3.32.0 has a NULL pointer dereference via a crafted matchinfo() query.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.32.0-1 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1
  • Fixed in: 3.32.3-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In SQLite before 3.32.3, select.c mishandles query-flattener optimization, leading to a multiSelectOrderBy heap overflow because of misuse of transitive properties for constant propagation.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.32.3-1 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Uncontrolled Recursion

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1
  • Fixed in: 3.30.1+fossil191229-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

alter.c in SQLite through 3.30.1 allows attackers to trigger infinite recursion via certain types of self-referential views in conjunction with ALTER TABLE statements.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.30.1+fossil191229-1 or higher.

References

Uncontrolled Recursion vulnerability report

medium severity

Use After Free

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1
  • Fixed in: 3.34.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw was found in SQLite's SELECT query functionality (src/select.c). This flaw allows an attacker who is capable of running SQL queries locally on the SQLite database to cause a denial of service or possible code execution by triggering a use-after-free. The highest threat from this vulnerability is to system availability.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.34.1-1 or higher.

References

Use After Free vulnerability report

medium severity

Use After Free

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1
  • Fixed in: 3.43.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A heap use-after-free issue has been identified in SQLite in the jsonParseAddNodeArray() function in sqlite3.c. This flaw allows a local attacker to leverage a victim to pass specially crafted malicious input to the application, potentially causing a crash and leading to a denial of service.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.43.2-1 or higher.

References

Use After Free vulnerability report

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: systemd
  • Introduced through: systemd@238-4, systemd/libnss-systemd@238-4 and others
  • Fixed in: 247.3-6

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libnss-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libpam-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libsystemd0@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libudev1@238-2
  • Introduced through: openjdk@10-ea-jdk › systemd/systemd-sysv@238-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

basic/unit-name.c in systemd prior to 246.15, 247.8, 248.5, and 249.1 has a Memory Allocation with an Excessive Size Value (involving strdupa and alloca for a pathname controlled by a local attacker) that results in an operating system crash.

Remediation

Upgrade Debian:unstable systemd to version 247.3-6 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

medium severity

CVE-2022-4415

  • Vulnerable module: systemd
  • Introduced through: systemd@238-4, systemd/libnss-systemd@238-4 and others
  • Fixed in: 252.4-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libnss-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libpam-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libsystemd0@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libudev1@238-2
  • Introduced through: openjdk@10-ea-jdk › systemd/systemd-sysv@238-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A vulnerability was found in systemd. This security flaw can cause a local information leak due to systemd-coredump not respecting the fs.suid_dumpable kernel setting.

Remediation

Upgrade Debian:unstable systemd to version 252.4-1 or higher.

References

CVE-2022-4415 vulnerability report

medium severity

Off-by-one Error

  • Vulnerable module: systemd
  • Introduced through: systemd@238-4, systemd/libnss-systemd@238-4 and others
  • Fixed in: 251.3-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libnss-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libpam-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libsystemd0@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libudev1@238-2
  • Introduced through: openjdk@10-ea-jdk › systemd/systemd-sysv@238-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An off-by-one Error issue was discovered in Systemd in format_timespan() function of time-util.c. An attacker could supply specific values for time and accuracy that leads to buffer overrun in format_timespan(), leading to a Denial of Service.

Remediation

Upgrade Debian:unstable systemd to version 251.3-1 or higher.

References

Off-by-one Error vulnerability report

medium severity

Out-of-Bounds

  • Vulnerable module: systemd
  • Introduced through: systemd@238-4, systemd/libnss-systemd@238-4 and others
  • Fixed in: 240-6

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libnss-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libpam-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libsystemd0@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libudev1@238-2
  • Introduced through: openjdk@10-ea-jdk › systemd/systemd-sysv@238-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An issue was discovered in sd-bus in systemd 239. bus_process_object() in libsystemd/sd-bus/bus-objects.c allocates a variable-length stack buffer for temporarily storing the object path of incoming D-Bus messages. An unprivileged local user can exploit this by sending a specially crafted message to PID1, causing the stack pointer to jump over the stack guard pages into an unmapped memory region and trigger a denial of service (systemd PID1 crash and kernel panic).

Remediation

Upgrade Debian:unstable systemd to version 240-6 or higher.

References

Out-of-Bounds vulnerability report

medium severity

Resource Exhaustion

  • Vulnerable module: systemd
  • Introduced through: systemd@238-4, systemd/libnss-systemd@238-4 and others
  • Fixed in: 252-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libnss-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libpam-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libsystemd0@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libudev1@238-2
  • Introduced through: openjdk@10-ea-jdk › systemd/systemd-sysv@238-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

systemd 250 and 251 allows local users to achieve a systemd-coredump deadlock by triggering a crash that has a long backtrace. This occurs in parse_elf_object in shared/elf-util.c. The exploitation methodology is to crash a binary calling the same function recursively, and put it in a deeply nested directory to make its backtrace large enough to cause the deadlock. This must be done 16 times when MaxConnections=16 is set for the systemd/units/systemd-coredump.socket file.

Remediation

Upgrade Debian:unstable systemd to version 252-1 or higher.

References

Resource Exhaustion vulnerability report

medium severity

Uncontrolled Recursion

  • Vulnerable module: systemd
  • Introduced through: systemd@238-4, systemd/libnss-systemd@238-4 and others
  • Fixed in: 250.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libnss-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libpam-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libsystemd0@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libudev1@238-2
  • Introduced through: openjdk@10-ea-jdk › systemd/systemd-sysv@238-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw was found in systemd. An uncontrolled recursion in systemd-tmpfiles may lead to a denial of service at boot time when too many nested directories are created in /tmp.

Remediation

Upgrade Debian:unstable systemd to version 250.2-1 or higher.

References

Uncontrolled Recursion vulnerability report

medium severity

Buffer Overflow

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.5.0-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.5.0-5 or higher.

References

Buffer Overflow vulnerability report

medium severity

Buffer Overflow

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.5.1~rc3-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.5.1~rc3-1 or higher.

References

Buffer Overflow vulnerability report

medium severity

Buffer Overflow

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.5.1~rc3-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.5.1~rc3-1 or higher.

References

Buffer Overflow vulnerability report

medium severity

Divide By Zero

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.3.0-6

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.3.0-6 or higher.

References

Divide By Zero vulnerability report

medium severity

Improper Validation of Specified Quantity in Input

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.4.0~rc1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.4.0~rc1-1 or higher.

References

Improper Validation of Specified Quantity in Input vulnerability report

medium severity

Integer Underflow

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.4.0~rc1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.4.0~rc1-1 or higher.

References

Integer Underflow vulnerability report

medium severity

Integer Underflow

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.4.0~rc1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.4.0~rc1-1 or higher.

References

Integer Underflow vulnerability report

medium severity

Memory Leak

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.5.1~rc3-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.5.1~rc3-1 or higher.

References

Memory Leak vulnerability report

medium severity

NULL Pointer Dereference

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.3.0-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.3.0-4 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

NULL Pointer Dereference

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.3.0-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.3.0-4 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

NULL Pointer Dereference

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.3.0-6

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.3.0-6 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

NULL Pointer Dereference

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.5.0-6

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable relevant fixed versions and status.

A NULL pointer dereference flaw was found in Libtiff's LZWDecode() function in the libtiff/tif_lzw.c file. This flaw allows a local attacker to craft specific input data that can cause the program to dereference a NULL pointer when decompressing a TIFF format file, resulting in a program crash or denial of service.

Remediation

Upgrade Debian:unstable tiff to version 4.5.0-6 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

NULL Pointer Dereference

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.5.1~rc3-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.5.1~rc3-1 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

Out-of-bounds Read

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.3.0-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.3.0-3 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Out-of-bounds Read

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.3.0-6

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.3.0-6 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Out-of-bounds Read

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.3.0-7

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.3.0-7 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Out-of-bounds Read

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.4.0~rc1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable relevant fixed versions and status.

LibTIFF master branch has an out-of-bounds read in LZWDecode in libtiff/tif_lzw.c:619, 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 b4e79bfa.

Remediation

Upgrade Debian:unstable tiff to version 4.4.0~rc1-1 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Out-of-bounds Read

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.4.0~rc1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable relevant fixed versions and status.

LibTIFF master branch has an out-of-bounds read in LZWDecode in libtiff/tif_lzw.c:624, 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 b4e79bfa.

Remediation

Upgrade Debian:unstable tiff to version 4.4.0~rc1-1 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Out-of-bounds Read

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.5.0-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.5.0-5 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Out-of-bounds Read

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.5.0-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.5.0-5 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Out-of-bounds Read

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.5.0-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.5.0-5 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Out-of-bounds Read

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.5.0-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.5.0-5 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Out-of-bounds Read

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.4.0-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.4.0-5 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.4.0-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.4.0-5 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.5.0-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.5.0-4 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.5.0-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.5.0-5 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.5.0-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.5.0-5 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.5.0-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.5.0-5 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.5.0-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.5.0-5 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.5.0-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.5.0-5 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.4.0-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.4.0-5 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.4.0-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.4.0-5 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.5.1~rc3-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.5.1~rc3-1 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.0.10+git190814-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable relevant fixed versions and status.

There exists one heap buffer overflow in _TIFFmemcpy in tif_unix.c in libtiff 4.0.10, which allows an attacker to cause a denial-of-service through a crafted tiff file.

Remediation

Upgrade Debian:unstable tiff to version 4.0.10+git190814-1 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Unchecked Return Value

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.3.0-6

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.3.0-6 or higher.

References

Unchecked Return Value vulnerability report

medium severity

Use After Free

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.5.0-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff to version 4.5.0-5 or higher.

References

Use After Free vulnerability report

medium severity

CVE-2022-0530

  • Vulnerable module: unzip
  • Introduced through: unzip@6.0-21
  • Fixed in: 6.0-27

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › unzip@6.0-21

NVD Description

Note: Versions mentioned in the description apply only to the upstream unzip package and not the unzip package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw was found in Unzip. The vulnerability occurs during the conversion of a wide string to a local string that leads to a heap of out-of-bound write. This flaw allows an attacker to input a specially crafted zip file, leading to a crash or code execution.

Remediation

Upgrade Debian:unstable unzip to version 6.0-27 or higher.

References

CVE-2022-0530 vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: unzip
  • Introduced through: unzip@6.0-21
  • Fixed in: 6.0-27

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › unzip@6.0-21

NVD Description

Note: Versions mentioned in the description apply only to the upstream unzip package and not the unzip package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw was found in Unzip. The vulnerability occurs during the conversion of a wide string to a local string that leads to a heap of out-of-bound write. This flaw allows an attacker to input a specially crafted zip file, leading to a crash or code execution.

Remediation

Upgrade Debian:unstable unzip to version 6.0-27 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Files or Directories Accessible to External Parties

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.31.1-0.5, util-linux/fdisk@2.31.1-0.5 and others
  • Fixed in: 2.37.3-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › util-linux@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/fdisk@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/libblkid1@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/libfdisk1@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/libmount1@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/libsmartcols1@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/libuuid1@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/mount@2.31.1-0.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream util-linux package and not the util-linux package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A logic error was found in the libmount library of util-linux in the function that allows an unprivileged user to unmount a FUSE filesystem. This flaw allows a local user on a vulnerable system to unmount other users' filesystems that are either world-writable themselves (like /tmp) or mounted in a world-writable directory. An attacker may use this flaw to cause a denial of service to applications that use the affected filesystems.

Remediation

Upgrade Debian:unstable util-linux to version 2.37.3-1 or higher.

References

Files or Directories Accessible to External Parties vulnerability report

medium severity

Files or Directories Accessible to External Parties

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.31.1-0.5, util-linux/fdisk@2.31.1-0.5 and others
  • Fixed in: 2.37.3-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › util-linux@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/fdisk@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/libblkid1@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/libfdisk1@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/libmount1@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/libsmartcols1@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/libuuid1@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/mount@2.31.1-0.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream util-linux package and not the util-linux package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A logic error was found in the libmount library of util-linux in the function that allows an unprivileged user to unmount a FUSE filesystem. This flaw allows an unprivileged local attacker to unmount FUSE filesystems that belong to certain other users who have a UID that is a prefix of the UID of the attacker in its string form. An attacker may use this flaw to cause a denial of service to applications that use the affected filesystems.

Remediation

Upgrade Debian:unstable util-linux to version 2.37.3-1 or higher.

References

Files or Directories Accessible to External Parties vulnerability report

medium severity

Small Space of Random Values

  • Vulnerable module: avahi/libavahi-client3
  • Introduced through: avahi/libavahi-client3@0.7-3.1, avahi/libavahi-common-data@0.7-3.1 and others

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-client3@0.7-3.1
  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-common-data@0.7-3.1
  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-common3@0.7-3.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream avahi package and not the avahi package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw was found in the Avahi-daemon, where it initializes DNS transaction IDs randomly only once at startup, incrementing them sequentially after that. This predictable behavior facilitates DNS spoofing attacks, allowing attackers to guess transaction IDs.

Remediation

There is no fixed version for Debian:unstable avahi.

References

Small Space of Random Values vulnerability report

medium severity

Use of Insufficiently Random Values

  • Vulnerable module: avahi/libavahi-client3
  • Introduced through: avahi/libavahi-client3@0.7-3.1, avahi/libavahi-common-data@0.7-3.1 and others

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-client3@0.7-3.1
  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-common-data@0.7-3.1
  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-common3@0.7-3.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream avahi package and not the avahi package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw was found in Avahi-daemon, which relies on fixed source ports for wide-area DNS queries. This issue simplifies attacks where malicious DNS responses are injected.

Remediation

There is no fixed version for Debian:unstable avahi.

References

Use of Insufficiently Random Values vulnerability report

medium severity

CVE-2022-27779

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.83.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable relevant fixed versions and status.

libcurl wrongly allows cookies to be set for Top Level Domains (TLDs) if thehost name is provided with a trailing dot.curl can be told to receive and send cookies. curl's "cookie engine" can bebuilt with or without Public Suffix Listawareness. If PSL support not provided, a more rudimentary check exists to atleast prevent cookies from being set on TLDs. This check was broken if thehost name in the URL uses a trailing dot.This can allow arbitrary sites to set cookies that then would get sent to adifferent and unrelated site or domain.

Remediation

Upgrade Debian:unstable curl to version 7.83.1-1 or higher.

References

CVE-2022-27779 vulnerability report

medium severity

Improper Certificate Validation

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 8.6.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable relevant fixed versions and status.

curl inadvertently kept the SSL session ID for connections in its cache even when the verify status (OCSP stapling) test failed. A subsequent transfer to the same hostname could then succeed if the session ID cache was still fresh, which then skipped the verify status check.

Remediation

Upgrade Debian:unstable curl to version 8.6.0-1 or higher.

References

Improper Certificate Validation vulnerability report

medium severity

Information Exposure

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.74.0-1.2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable relevant fixed versions and status.

curl 7.1.1 to and including 7.75.0 is vulnerable to an "Exposure of Private Personal Information to an Unauthorized Actor" by leaking credentials in the HTTP Referer: header. libcurl does not strip off user credentials from the URL when automatically populating the Referer: HTTP request header field in outgoing HTTP requests, and therefore risks leaking sensitive data to the server that is the target of the second HTTP request.

Remediation

Upgrade Debian:unstable curl to version 7.74.0-1.2 or higher.

References

Information Exposure vulnerability report

medium severity

Missing Encryption of Sensitive Data

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 8.5.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable relevant fixed versions and status.

When saving HSTS data to an excessively long file name, curl could end up removing all contents, making subsequent requests using that file unaware of the HSTS status they should otherwise use.

Remediation

Upgrade Debian:unstable curl to version 8.5.0-1 or higher.

References

Missing Encryption of Sensitive Data vulnerability report

medium severity

Link Following

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.56.1-2 and glib2.0/libglib2.0-data@2.56.1-2
  • Fixed in: 2.66.7-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-0@2.56.1-2
  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-data@2.56.1-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An issue was discovered in GNOME GLib before 2.66.8. When g_file_replace() is used with G_FILE_CREATE_REPLACE_DESTINATION to replace a path that is a dangling symlink, it incorrectly also creates the target of the symlink as an empty file, which could conceivably have security relevance if the symlink is attacker-controlled. (If the path is a symlink to a file that already exists, then the contents of that file correctly remain unchanged.)

Remediation

Upgrade Debian:unstable glib2.0 to version 2.66.7-2 or higher.

References

Link Following vulnerability report

medium severity

Improper Input Validation

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2
  • Fixed in: 2.28-6

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In the GNU C Library (aka glibc or libc6) through 2.28, the getaddrinfo function would successfully parse a string that contained an IPv4 address followed by whitespace and arbitrary characters, which could lead applications to incorrectly assume that it had parsed a valid string, without the possibility of embedded HTTP headers or other potentially dangerous substrings.

Remediation

Upgrade Debian:unstable glibc to version 2.28-6 or higher.

References

Improper Input Validation vulnerability report

medium severity

Incorrect Calculation of Buffer Size

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2
  • Fixed in: 2.37-15

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An integer overflow was found in the __vsyslog_internal function of the glibc library. This function is called by the syslog and vsyslog functions. This issue occurs when these functions are called with a very long message, leading to an incorrect calculation of the buffer size to store the message, resulting in undefined behavior. This issue affects glibc 2.37 and newer.

Remediation

Upgrade Debian:unstable glibc to version 2.37-15 or higher.

References

Incorrect Calculation of Buffer Size vulnerability report

medium severity

Algorithmic Complexity

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.18-1
  • Fixed in: 3.8.9-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gnutls28/libgnutls30@3.5.18-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw was found in GnuTLS, which relies on libtasn1 for ASN.1 data processing. Due to an inefficient algorithm in libtasn1, decoding certain DER-encoded certificate data can take excessive time, leading to increased resource consumption. This flaw allows a remote attacker to send a specially crafted certificate, causing GnuTLS to become unresponsive or slow, resulting in a denial-of-service condition.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.8.9-2 or higher.

References

Algorithmic Complexity vulnerability report

medium severity

Improper Certificate Validation

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.18-1
  • Fixed in: 3.8.9-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gnutls28/libgnutls30@3.5.18-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A heap-buffer-overread vulnerability was found in GnuTLS in how it handles the Certificate Transparency (CT) Signed Certificate Timestamp (SCT) extension during X.509 certificate parsing. This flaw allows a malicious user to create a certificate containing a malformed SCT extension (OID 1.3.6.1.4.1.11129.2.4.2) that contains sensitive data. This issue leads to the exposure of confidential information when GnuTLS verifies certificates from certain websites when the certificate (SCT) is not checked correctly.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.8.9-3 or higher.

References

Improper Certificate Validation vulnerability report

medium severity

Use After Free

  • Vulnerable module: libpng1.6/libpng16-16
  • Introduced through: libpng1.6/libpng16-16@1.6.34-1
  • Fixed in: 1.6.36-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libpng1.6/libpng16-16@1.6.34-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

png_image_free in png.c in libpng 1.6.x before 1.6.37 has a use-after-free because png_image_free_function is called under png_safe_execute.

Remediation

Upgrade Debian:unstable libpng1.6 to version 1.6.36-4 or higher.

References

Use After Free vulnerability report

medium severity

Algorithmic Complexity

  • Vulnerable module: libtasn1-6
  • Introduced through: libtasn1-6@4.13-2
  • Fixed in: 4.20.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libtasn1-6@4.13-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream libtasn1-6 package and not the libtasn1-6 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw in libtasn1 causes inefficient handling of specific certificate data. When processing a large number of elements in a certificate, libtasn1 takes much longer than expected, which can slow down or even crash the system. This flaw allows an attacker to send a specially crafted certificate, causing a denial of service attack.

Remediation

Upgrade Debian:unstable libtasn1-6 to version 4.20.0-1 or higher.

References

Algorithmic Complexity vulnerability report

medium severity

CVE-2020-6829

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.36.1-1
  • Fixed in: 2:3.55-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nss/libnss3@2:3.36.1-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nss package and not the nss package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

When performing EC scalar point multiplication, the wNAF point multiplication algorithm was used; which leaked partial information about the nonce used during signature generation. Given an electro-magnetic trace of a few signature generations, the private key could have been computed. This vulnerability affects Firefox < 80 and Firefox for Android < 80.

Remediation

Upgrade Debian:unstable nss to version 2:3.55-1 or higher.

References

CVE-2020-6829 vulnerability report

medium severity

Improper Certificate Validation

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.36.1-1
  • Fixed in: 2:3.45-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nss/libnss3@2:3.36.1-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nss package and not the nss package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A vulnerability exists where it possible to force Network Security Services (NSS) to sign CertificateVerify with PKCS#1 v1.5 signatures when those are the only ones advertised by server in CertificateRequest in TLS 1.3. PKCS#1 v1.5 signatures should not be used for TLS 1.3 messages. This vulnerability affects Firefox < 68.

Remediation

Upgrade Debian:unstable nss to version 2:3.45-1 or higher.

References

Improper Certificate Validation vulnerability report

medium severity

Incorrect Authorization

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:7.6p1-4
  • Fixed in: 1:7.9p1-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssh/openssh-client@1:7.6p1-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In OpenSSH 7.9, scp.c in the scp client allows remote SSH servers to bypass intended access restrictions via the filename of . or an empty filename. The impact is modifying the permissions of the target directory on the client side.

Remediation

Upgrade Debian:unstable openssh to version 1:7.9p1-5 or higher.

References

Incorrect Authorization vulnerability report

medium severity

Race Condition

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:7.6p1-4
  • Fixed in: 1:7.7p1-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssh/openssh-client@1:7.6p1-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

OpenSSH through 7.7 is prone to a user enumeration vulnerability due to not delaying bailout for an invalid authenticating user until after the packet containing the request has been fully parsed, related to auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c.

Remediation

Upgrade Debian:unstable openssh to version 1:7.7p1-4 or higher.

References

Race Condition vulnerability report

medium severity

Excessive Iteration

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 3.0.10-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Issue summary: Checking excessively long DH keys or parameters may be very slow.

Impact summary: Applications that use the functions DH_check(), DH_check_ex() or EVP_PKEY_param_check() to check a DH key or DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service.

The function DH_check() performs various checks on DH parameters. After fixing CVE-2023-3446 it was discovered that a large q parameter value can also trigger an overly long computation during some of these checks. A correct q value, if present, cannot be larger than the modulus p parameter, thus it is unnecessary to perform these checks if q is larger than p.

An application that calls DH_check() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack.

The function DH_check() is itself called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_ex() and EVP_PKEY_param_check().

Also vulnerable are the OpenSSL dhparam and pkeyparam command line applications when using the "-check" option.

The OpenSSL SSL/TLS implementation is not affected by this issue.

The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.

Remediation

Upgrade Debian:unstable openssl to version 3.0.10-1 or higher.

References

Excessive Iteration vulnerability report

medium severity

Improper Authentication

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 3.0.10-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Issue summary: The AES-SIV cipher implementation contains a bug that causes it to ignore empty associated data entries which are unauthenticated as a consequence.

Impact summary: Applications that use the AES-SIV algorithm and want to authenticate empty data entries as associated data can be misled by removing, adding or reordering such empty entries as these are ignored by the OpenSSL implementation. We are currently unaware of any such applications.

The AES-SIV algorithm allows for authentication of multiple associated data entries along with the encryption. To authenticate empty data the application has to call EVP_EncryptUpdate() (or EVP_CipherUpdate()) with NULL pointer as the output buffer and 0 as the input buffer length. The AES-SIV implementation in OpenSSL just returns success for such a call instead of performing the associated data authentication operation. The empty data thus will not be authenticated.

As this issue does not affect non-empty associated data authentication and we expect it to be rare for an application to use empty associated data entries this is qualified as Low severity issue.

Remediation

Upgrade Debian:unstable openssl to version 3.0.10-1 or higher.

References

Improper Authentication vulnerability report

medium severity

Improper Certificate Validation

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 3.0.9-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The function X509_VERIFY_PARAM_add0_policy() is documented to implicitly enable the certificate policy check when doing certificate verification. However the implementation of the function does not enable the check which allows certificates with invalid or incorrect policies to pass the certificate verification.

As suddenly enabling the policy check could break existing deployments it was decided to keep the existing behavior of the X509_VERIFY_PARAM_add0_policy() function.

Instead the applications that require OpenSSL to perform certificate policy check need to use X509_VERIFY_PARAM_set1_policies() or explicitly enable the policy check by calling X509_VERIFY_PARAM_set_flags() with the X509_V_FLAG_POLICY_CHECK flag argument.

Certificate policy checks are disabled by default in OpenSSL and are not commonly used by applications.

Remediation

Upgrade Debian:unstable openssl to version 3.0.9-1 or higher.

References

Improper Certificate Validation vulnerability report

medium severity

Improper Certificate Validation

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 3.0.9-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Applications that use a non-default option when verifying certificates may be vulnerable to an attack from a malicious CA to circumvent certain checks.

Invalid certificate policies in leaf certificates are silently ignored by OpenSSL and other certificate policy checks are skipped for that certificate. A malicious CA could use this to deliberately assert invalid certificate policies in order to circumvent policy checking on the certificate altogether.

Policy processing is disabled by default but can be enabled by passing the -policy&#39; argument to the command line utilities or by calling the X509_VERIFY_PARAM_set1_policies()' function.

Remediation

Upgrade Debian:unstable openssl to version 3.0.9-1 or higher.

References

Improper Certificate Validation vulnerability report

medium severity

Improper Check for Unusual or Exceptional Conditions

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 3.0.12-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Issue summary: Generating excessively long X9.42 DH keys or checking excessively long X9.42 DH keys or parameters may be very slow.

Impact summary: Applications that use the functions DH_generate_key() to generate an X9.42 DH key may experience long delays. Likewise, applications that use DH_check_pub_key(), DH_check_pub_key_ex() or EVP_PKEY_public_check() to check an X9.42 DH key or X9.42 DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service.

While DH_check() performs all the necessary checks (as of CVE-2023-3817), DH_check_pub_key() doesn't make any of these checks, and is therefore vulnerable for excessively large P and Q parameters.

Likewise, while DH_generate_key() performs a check for an excessively large P, it doesn't check for an excessively large Q.

An application that calls DH_generate_key() or DH_check_pub_key() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack.

DH_generate_key() and DH_check_pub_key() are also called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_pub_key_ex(), EVP_PKEY_public_check(), and EVP_PKEY_generate().

Also vulnerable are the OpenSSL pkey command line application when using the "-pubcheck" option, as well as the OpenSSL genpkey command line application.

The OpenSSL SSL/TLS implementation is not affected by this issue.

The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.

Remediation

Upgrade Debian:unstable openssl to version 3.0.12-2 or higher.

References

Improper Check for Unusual or Exceptional Conditions vulnerability report

medium severity

Inefficient Regular Expression Complexity

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 3.0.10-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Issue summary: Checking excessively long DH keys or parameters may be very slow.

Impact summary: Applications that use the functions DH_check(), DH_check_ex() or EVP_PKEY_param_check() to check a DH key or DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service.

The function DH_check() performs various checks on DH parameters. One of those checks confirms that the modulus ('p' parameter) is not too large. Trying to use a very large modulus is slow and OpenSSL will not normally use a modulus which is over 10,000 bits in length.

However the DH_check() function checks numerous aspects of the key or parameters that have been supplied. Some of those checks use the supplied modulus value even if it has already been found to be too large.

An application that calls DH_check() and supplies a key or parameters obtained from an untrusted source could be vulernable to a Denial of Service attack.

The function DH_check() is itself called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_ex() and EVP_PKEY_param_check().

Also vulnerable are the OpenSSL dhparam and pkeyparam command line applications when using the '-check' option.

The OpenSSL SSL/TLS implementation is not affected by this issue. The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.

Remediation

Upgrade Debian:unstable openssl to version 3.0.10-1 or higher.

References

Inefficient Regular Expression Complexity vulnerability report

medium severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 3.0.5-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

AES OCB mode for 32-bit x86 platforms using the AES-NI assembly optimised implementation will not encrypt the entirety of the data under some circumstances. This could reveal sixteen bytes of data that was preexisting in the memory that wasn't written. In the special case of "in place" encryption, sixteen bytes of the plaintext would be revealed. Since OpenSSL does not support OCB based cipher suites for TLS and DTLS, they are both unaffected. Fixed in OpenSSL 3.0.5 (Affected 3.0.0-3.0.4). Fixed in OpenSSL 1.1.1q (Affected 1.1.1-1.1.1p).

Remediation

Upgrade Debian:unstable openssl to version 3.0.5-1 or higher.

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

medium severity

Use of Insufficiently Random Values

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 1.1.1d-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

OpenSSL 1.1.1 introduced a rewritten random number generator (RNG). This was intended to include protection in the event of a fork() system call in order to ensure that the parent and child processes did not share the same RNG state. However this protection was not being used in the default case. A partial mitigation for this issue is that the output from a high precision timer is mixed into the RNG state so the likelihood of a parent and child process sharing state is significantly reduced. If an application already calls OPENSSL_init_crypto() explicitly using OPENSSL_INIT_ATFORK then this problem does not occur at all. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c).

Remediation

Upgrade Debian:unstable openssl to version 1.1.1d-1 or higher.

References

Use of Insufficiently Random Values vulnerability report

medium severity

Out-of-bounds Read

  • Vulnerable module: p11-kit/libp11-kit0
  • Introduced through: p11-kit/libp11-kit0@0.23.9-2
  • Fixed in: 0.23.22-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › p11-kit/libp11-kit0@0.23.9-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream p11-kit package and not the p11-kit package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An issue was discovered in p11-kit 0.21.1 through 0.23.21. A heap-based buffer over-read has been discovered in the RPC protocol used by thep11-kit server/remote commands and the client library. When the remote entity supplies a byte array through a serialized PKCS#11 function call, the receiving entity may allow the reading of up to 4 bytes of memory past the heap allocation.

Remediation

Upgrade Debian:unstable p11-kit to version 0.23.22-1 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Improper Handling of Exceptional Conditions

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1
  • Fixed in: 3.30.1+fossil191229-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

SQLite 3.30.1 mishandles certain parser-tree rewriting, related to expr.c, vdbeaux.c, and window.c. This is caused by incorrect sqlite3WindowRewrite() error handling.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.30.1+fossil191229-1 or higher.

References

Improper Handling of Exceptional Conditions vulnerability report

medium severity

Out-of-bounds Read

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 3.0.8-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A read buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed the malicious certificate or for the application to continue certificate verification despite failure to construct a path to a trusted issuer.

The read buffer overrun might result in a crash which could lead to a denial of service attack. In theory it could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext) although we are not aware of any working exploit leading to memory contents disclosure as of the time of release of this advisory.

In a TLS client, this can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server requests client authentication and a malicious client connects.

Remediation

Upgrade Debian:unstable openssl to version 3.0.8-1 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Buffer Underflow

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.56.1-2 and glib2.0/libglib2.0-data@2.56.1-2
  • Fixed in: 2.84.1-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-0@2.56.1-2
  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-data@2.56.1-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw was found in GLib, which is vulnerable to an integer overflow in the g_string_insert_unichar() function. When the position at which to insert the character is large, the position will overflow, leading to a buffer underwrite.

Remediation

Upgrade Debian:unstable glib2.0 to version 2.84.1-3 or higher.

References

Buffer Underflow vulnerability report

medium severity

Reachable Assertion

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2
  • Fixed in: 2.31-7

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The iconv function in the GNU C Library (aka glibc or libc6) 2.30 to 2.32, when converting UCS4 text containing an irreversible character, fails an assertion in the code path and aborts the program, potentially resulting in a denial of service.

Remediation

Upgrade Debian:unstable glibc to version 2.31-7 or higher.

References

Reachable Assertion vulnerability report

medium severity

Improper Encoding or Escaping of Output

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.47.2-0.1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals. When Git asks for credentials via a terminal prompt (i.e. without using any credential helper), it prints out the host name for which the user is expected to provide a username and/or a password. At this stage, any URL-encoded parts have been decoded already, and are printed verbatim. This allows attackers to craft URLs that contain ANSI escape sequences that the terminal interpret to confuse users e.g. into providing passwords for trusted Git hosting sites when in fact they are then sent to untrusted sites that are under the attacker's control. This issue has been patch via commits 7725b81 and c903985 which are included in release versions v2.48.1, v2.47.2, v2.46.3, v2.45.3, v2.44.3, v2.43.6, v2.42.4, v2.41.3, and v2.40.4. Users are advised to upgrade. Users unable to upgrade should avoid cloning from untrusted URLs, especially recursive clones.

Remediation

Upgrade Debian:unstable git to version 1:2.47.2-0.1 or higher.

References

Improper Encoding or Escaping of Output vulnerability report

medium severity

CVE-2025-30258

  • Vulnerable module: gnupg2/dirmngr
  • Introduced through: gnupg2/dirmngr@2.2.5-1, gnupg2/gnupg@2.2.5-1 and others
  • Fixed in: 2.2.46-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gnupg2/dirmngr@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gnupg@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gnupg-l10n@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gnupg-utils@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpg@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpg-agent@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpg-wks-client@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpg-wks-server@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpgconf@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpgsm@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpgv@2.2.5-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream gnupg2 package and not the gnupg2 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In GnuPG before 2.5.5, if a user chooses to import a certificate with certain crafted subkey data that lacks a valid backsig or that has incorrect usage flags, the user loses the ability to verify signatures made from certain other signing keys, aka a "verification DoS."

Remediation

Upgrade Debian:unstable gnupg2 to version 2.2.46-5 or higher.

References

CVE-2025-30258 vulnerability report

medium severity
new

Improper Verification of Cryptographic Signature

  • Vulnerable module: gnupg2/dirmngr
  • Introduced through: gnupg2/dirmngr@2.2.5-1, gnupg2/gnupg@2.2.5-1 and others

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gnupg2/dirmngr@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gnupg@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gnupg-l10n@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gnupg-utils@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpg@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpg-agent@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpg-wks-client@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpg-wks-server@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpgconf@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpgsm@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpgv@2.2.5-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream gnupg2 package and not the gnupg2 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In GnuPG through 2.4.8, if a signed message has \f at the end of a plaintext line, an adversary can construct a modified message that places additional text after the signed material, such that signature verification of the modified message succeeds (although an "invalid armor" message is printed during verification). This is related to use of \f as a marker to denote truncation of a long plaintext line.

Remediation

There is no fixed version for Debian:unstable gnupg2.

References

Improper Verification of Cryptographic Signature vulnerability report

medium severity

NULL Pointer Dereference

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.16-2, krb5/libk5crypto3@1.16-2 and others
  • Fixed in: 1.16.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › krb5/libgssapi-krb5-2@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libk5crypto3@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libkrb5-3@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libkrb5support0@1.16-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

MIT krb5 1.6 or later allows an authenticated kadmin with permission to add principals to an LDAP Kerberos database to cause a denial of service (NULL pointer dereference) or bypass a DN container check by supplying tagged data that is internal to the database module.

Remediation

Upgrade Debian:unstable krb5 to version 1.16.1-1 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

Information Exposure

  • Vulnerable module: libgcrypt20
  • Introduced through: libgcrypt20@1.8.1-4
  • Fixed in: 1.8.3-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libgcrypt20@1.8.1-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream libgcrypt20 package and not the libgcrypt20 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Libgcrypt before 1.7.10 and 1.8.x before 1.8.3 allows a memory-cache side-channel attack on ECDSA signatures that can be mitigated through the use of blinding during the signing process in the _gcry_ecc_ecdsa_sign function in cipher/ecc-ecdsa.c, aka the Return Of the Hidden Number Problem or ROHNP. To discover an ECDSA key, the attacker needs access to either the local machine or a different virtual machine on the same physical host.

Remediation

Upgrade Debian:unstable libgcrypt20 to version 1.8.3-1 or higher.

References

Information Exposure vulnerability report

medium severity

Information Exposure

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.36.1-1
  • Fixed in: 2:3.55-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nss/libnss3@2:3.36.1-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nss package and not the nss package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

When converting coordinates from projective to affine, the modular inversion was not performed in constant time, resulting in a possible timing-based side channel attack. This vulnerability affects Firefox < 80 and Firefox for Android < 80.

Remediation

Upgrade Debian:unstable nss to version 2:3.55-1 or higher.

References

Information Exposure vulnerability report

medium severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.36.1-1
  • Fixed in: 2:3.55-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nss/libnss3@2:3.36.1-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nss package and not the nss package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

During ECDSA signature generation, padding applied in the nonce designed to ensure constant-time scalar multiplication was removed, resulting in variable-time execution dependent on secret data. This vulnerability affects Firefox < 80 and Firefox for Android < 80.

Remediation

Upgrade Debian:unstable nss to version 2:3.55-1 or higher.

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

medium severity

CVE-2019-1547

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 1.1.1d-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Normally in OpenSSL EC groups always have a co-factor present and this is used in side channel resistant code paths. However, in some cases, it is possible to construct a group using explicit parameters (instead of using a named curve). In those cases it is possible that such a group does not have the cofactor present. This can occur even where all the parameters match a known named curve. If such a curve is used then OpenSSL falls back to non-side channel resistant code paths which may result in full key recovery during an ECDSA signature operation. In order to be vulnerable an attacker would have to have the ability to time the creation of a large number of signatures where explicit parameters with no co-factor present are in use by an application using libcrypto. For the avoidance of doubt libssl is not vulnerable because explicit parameters are never used. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s).

Remediation

Upgrade Debian:unstable openssl to version 1.1.1d-1 or higher.

References

CVE-2019-1547 vulnerability report

medium severity

Information Exposure

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 1.1.1~~pre9-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Simultaneous Multi-threading (SMT) in processors can enable local users to exploit software vulnerable to timing attacks via a side-channel timing attack on 'port contention'.

Remediation

Upgrade Debian:unstable openssl to version 1.1.1~~pre9-1 or higher.

References

Information Exposure vulnerability report

medium severity

Insecure Storage of Sensitive Information

  • Vulnerable module: pam/libpam-modules
  • Introduced through: pam/libpam-modules@1.1.8-3.7, pam/libpam-modules-bin@1.1.8-3.7 and others
  • Fixed in: 1.7.0-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › pam/libpam-modules@1.1.8-3.7
  • Introduced through: openjdk@10-ea-jdk › pam/libpam-modules-bin@1.1.8-3.7
  • Introduced through: openjdk@10-ea-jdk › pam/libpam-runtime@1.1.8-3.7
  • Introduced through: openjdk@10-ea-jdk › pam/libpam0g@1.1.8-3.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream pam package and not the pam package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A vulnerability was found in PAM. The secret information is stored in memory, where the attacker can trigger the victim program to execute by sending characters to its standard input (stdin). As this occurs, the attacker can train the branch predictor to execute an ROP chain speculatively. This flaw could result in leaked passwords, such as those found in /etc/shadow while performing authentications.

Remediation

Upgrade Debian:unstable pam to version 1.7.0-2 or higher.

References

Insecure Storage of Sensitive Information vulnerability report

medium severity

Race Condition

  • Vulnerable module: systemd
  • Introduced through: systemd@238-4, systemd/libnss-systemd@238-4 and others
  • Fixed in: 257.6-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libnss-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libpam-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libsystemd0@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libudev1@238-2
  • Introduced through: openjdk@10-ea-jdk › systemd/systemd-sysv@238-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A vulnerability was found in systemd-coredump. This flaw allows an attacker to force a SUID process to crash and replace it with a non-SUID binary to access the original's privileged process coredump, allowing the attacker to read sensitive data, such as /etc/shadow content, loaded by the original process.

A SUID binary or process has a special type of permission, which allows the process to run with the file owner's permissions, regardless of the user executing the binary. This allows the process to access more restricted data than unprivileged users or processes would be able to. An attacker can leverage this flaw by forcing a SUID process to crash and force the Linux kernel to recycle the process PID before systemd-coredump can analyze the /proc/pid/auxv file. If the attacker wins the race condition, they gain access to the original's SUID process coredump file. They can read sensitive content loaded into memory by the original binary, affecting data confidentiality.

Remediation

Upgrade Debian:unstable systemd to version 257.6-1 or higher.

References

Race Condition vulnerability report

medium severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: tar
  • Introduced through: tar@1.29b-2
  • Fixed in: 1.30+dfsg-3.1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tar@1.29b-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream tar package and not the tar package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

GNU Tar through 1.30, when --sparse is used, mishandles file shrinkage during read access, which allows local users to cause a denial of service (infinite read loop in sparse_dump_region in sparse.c) by modifying a file that is supposed to be archived by a different user's process (e.g., a system backup running as root).

Remediation

Upgrade Debian:unstable tar to version 1.30+dfsg-3.1 or higher.

References

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability report

medium severity

Use After Free

  • Vulnerable module: iproute2
  • Introduced through: iproute2@4.15.0-2
  • Fixed in: 5.2.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › iproute2@4.15.0-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream iproute2 package and not the iproute2 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

iproute2 before 5.1.0 has a use-after-free in get_netnsid_from_name in ip/ipnetns.c. NOTE: security relevance may be limited to certain uses of setuid that, although not a default, are sometimes a configuration option offered to end users. Even when setuid is used, other factors (such as C library configuration) may block exploitability.

Remediation

Upgrade Debian:unstable iproute2 to version 5.2.0-1 or higher.

References

Use After Free vulnerability report

medium severity

Information Exposure

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.36.1-1
  • Fixed in: 2:3.53-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nss/libnss3@2:3.36.1-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nss package and not the nss package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

NSS has shown timing differences when performing DSA signatures, which was exploitable and could eventually leak private keys. This vulnerability affects Thunderbird < 68.9.0, Firefox < 77, and Firefox ESR < 68.9.

Remediation

Upgrade Debian:unstable nss to version 2:3.53-1 or higher.

References

Information Exposure vulnerability report

medium severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.36.1-1
  • Fixed in: 2:3.53.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nss/libnss3@2:3.36.1-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nss package and not the nss package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

During RSA key generation, bignum implementations used a variation of the Binary Extended Euclidean Algorithm which entailed significantly input-dependent flow. This allowed an attacker able to perform electromagnetic-based side channel attacks to record traces leading to the recovery of the secret primes. Note: An unmodified Firefox browser does not generate RSA keys in normal operation and is not affected, but products built on top of it might. This vulnerability affects Firefox < 78.

Remediation

Upgrade Debian:unstable nss to version 2:3.53.1-1 or higher.

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

medium severity

CVE-2019-15718

  • Vulnerable module: systemd
  • Introduced through: systemd@238-4, systemd/libnss-systemd@238-4 and others
  • Fixed in: 242-7

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libnss-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libpam-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libsystemd0@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libudev1@238-2
  • Introduced through: openjdk@10-ea-jdk › systemd/systemd-sysv@238-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In systemd 240, bus_open_system_watch_bind_with_description in shared/bus-util.c (as used by systemd-resolved to connect to the system D-Bus instance), calls sd_bus_set_trusted, which disables access controls for incoming D-Bus messages. An unprivileged user can exploit this by executing D-Bus methods that should be restricted to privileged users, in order to change the system's DNS resolver settings.

Remediation

Upgrade Debian:unstable systemd to version 242-7 or higher.

References

CVE-2019-15718 vulnerability report

medium severity

Insufficient Verification of Data Authenticity

  • Vulnerable module: cryptsetup/libcryptsetup12
  • Introduced through: cryptsetup/libcryptsetup12@2:2.0.2-1
  • Fixed in: 2:2.4.3-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › cryptsetup/libcryptsetup12@2:2.0.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream cryptsetup package and not the cryptsetup package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

It was found that a specially crafted LUKS header could trick cryptsetup into disabling encryption during the recovery of the device. An attacker with physical access to the medium, such as a flash disk, could use this flaw to force a user into permanently disabling the encryption layer of that medium.

Remediation

Upgrade Debian:unstable cryptsetup to version 2:2.4.3-1 or higher.

References

Insufficient Verification of Data Authenticity vulnerability report

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.84.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable relevant fixed versions and status.

A malicious server can serve excessive amounts of Set-Cookie: headers in a HTTP response to curl and curl < 7.84.0 stores all of them. A sufficiently large amount of (big) cookies make subsequent HTTP requests to this, or other servers to which the cookies match, create requests that become larger than the threshold that curl uses internally to avoid sending crazy large requests (1048576 bytes) and instead returns an error.This denial state might remain for as long as the same cookies are kept, match and haven't expired. Due to cookie matching rules, a server on foo.example.com can set cookies that also would match for bar.example.com, making it it possible for a "sister server" to effectively cause a denial of service for a sibling site on the same second level domain using this method.

Remediation

Upgrade Debian:unstable curl to version 7.84.0-1 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

medium severity

Cleartext Transmission of Sensitive Information

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.83.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable relevant fixed versions and status.

Using its HSTS support, curl can be instructed to use HTTPS directly insteadof using an insecure clear-text HTTP step even when HTTP is provided in theURL. This mechanism could be bypassed if the host name in the given URL used atrailing dot while not using one when it built the HSTS cache. Or the otherway around - by having the trailing dot in the HSTS cache and not using thetrailing dot in the URL.

Remediation

Upgrade Debian:unstable curl to version 7.83.1-1 or higher.

References

Cleartext Transmission of Sensitive Information vulnerability report

medium severity

Out-of-bounds Read

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 8.9.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable relevant fixed versions and status.

libcurl's URL API function curl_url_get() offers punycode conversions, to and from IDN. Asking to convert a name that is exactly 256 bytes, libcurl ends up reading outside of a stack based buffer when built to use the macidn IDN backend. The conversion function then fills up the provided buffer exactly - but does not null terminate the string.

This flaw can lead to stack contents accidently getting returned as part of the converted string.

Remediation

Upgrade Debian:unstable curl to version 8.9.0-1 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Cross-site Scripting (XSS)

  • Vulnerable module: mercurial
  • Introduced through: mercurial@4.5-1 and mercurial/mercurial-common@4.5-1
  • Fixed in: 6.9.4-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › mercurial@4.5-1
  • Introduced through: openjdk@10-ea-jdk › mercurial/mercurial-common@4.5-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream mercurial package and not the mercurial package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A vulnerability was found in Mercurial SCM 4.5.3/71.19.145.211. It has been declared as problematic. This vulnerability affects unknown code of the component Web Interface. The manipulation of the argument cmd leads to cross site scripting. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Remediation

Upgrade Debian:unstable mercurial to version 6.9.4-1 or higher.

References

Cross-site Scripting (XSS) vulnerability report

medium severity

Information Exposure

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.36.1-1
  • Fixed in: 2:3.95-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nss/libnss3@2:3.36.1-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nss package and not the nss package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Multiple NSS NIST curves were susceptible to a side-channel attack known as "Minerva". This attack could potentially allow an attacker to recover the private key. This vulnerability affects Firefox < 121.

Remediation

Upgrade Debian:unstable nss to version 2:3.95-1 or higher.

References

Information Exposure vulnerability report

medium severity

Improper Input Validation

  • Vulnerable module: subversion
  • Introduced through: subversion@1.9.7-4 and subversion/libsvn1@1.9.7-4
  • Fixed in: 1.14.5-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › subversion@1.9.7-4
  • Introduced through: openjdk@10-ea-jdk › subversion/libsvn1@1.9.7-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream subversion package and not the subversion package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Insufficient validation of filenames against control characters in Apache Subversion repositories served via mod_dav_svn allows authenticated users with commit access to commit a corrupted revision, leading to disruption for users of the repository.

All versions of Subversion up to and including Subversion 1.14.4 are affected if serving repositories via mod_dav_svn. Users are recommended to upgrade to version 1.14.5, which fixes this issue.

Repositories served via other access methods are not affected.

Remediation

Upgrade Debian:unstable subversion to version 1.14.5-1 or higher.

References

Improper Input Validation vulnerability report

medium severity

Information Exposure

  • Vulnerable module: subversion
  • Introduced through: subversion@1.9.7-4 and subversion/libsvn1@1.9.7-4
  • Fixed in: 1.14.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › subversion@1.9.7-4
  • Introduced through: openjdk@10-ea-jdk › subversion/libsvn1@1.9.7-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream subversion package and not the subversion package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Apache Subversion SVN authz protected copyfrom paths regression Subversion servers reveal 'copyfrom' paths that should be hidden according to configured path-based authorization (authz) rules. When a node has been copied from a protected location, users with access to the copy can see the 'copyfrom' path of the original. This also reveals the fact that the node was copied. Only the 'copyfrom' path is revealed; not its contents. Both httpd and svnserve servers are vulnerable.

Remediation

Upgrade Debian:unstable subversion to version 1.14.2-1 or higher.

References

Information Exposure vulnerability report

low severity

Security Features

  • Vulnerable module: apparmor/libapparmor1
  • Introduced through: apparmor/libapparmor1@2.12-4
  • Fixed in: 3.0.12-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › apparmor/libapparmor1@2.12-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream apparmor package and not the apparmor package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In all versions of AppArmor mount rules are accidentally widened when compiled.

Remediation

Upgrade Debian:unstable apparmor to version 3.0.12-1 or higher.

References

Security Features vulnerability report

low severity

Double Free

  • Vulnerable module: elfutils/libelf1
  • Introduced through: elfutils/libelf1@0.170-0.3
  • Fixed in: 0.175-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › elfutils/libelf1@0.170-0.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream elfutils package and not the elfutils package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

libelf/elf_end.c in elfutils 0.173 allows remote attackers to cause a denial of service (double free and application crash) or possibly have unspecified other impact because it tries to decompress twice.

Remediation

Upgrade Debian:unstable elfutils to version 0.175-1 or higher.

References

Double Free vulnerability report

low severity

NULL Pointer Dereference

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.56.1-2 and glib2.0/libglib2.0-data@2.56.1-2
  • Fixed in: 2.58.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-0@2.56.1-2
  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-data@2.56.1-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In GNOME GLib 2.56.1, g_markup_parse_context_end_parse() in gmarkup.c has a NULL pointer dereference.

Remediation

Upgrade Debian:unstable glib2.0 to version 2.58.0-1 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

Out-of-Bounds

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may bypass stack guard protection. The component is: nptl. The attack vector is: Exploit stack buffer overflow vulnerability and use this bypass vulnerability to bypass stack guard. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat.

Remediation

There is no fixed version for Debian:unstable glibc.

References

Out-of-Bounds vulnerability report

low severity

Out-of-bounds Write

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2
  • Fixed in: 2.27-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

stdlib/canonicalize.c in the GNU C Library (aka glibc or libc6) 2.27 and earlier, when processing very long pathname arguments to the realpath function, could encounter an integer overflow on 32-bit architectures, leading to a stack-based buffer overflow and, potentially, arbitrary code execution.

Remediation

Upgrade Debian:unstable glibc to version 2.27-4 or higher.

References

Out-of-bounds Write vulnerability report

low severity

CVE-2019-9893

  • Vulnerable module: libseccomp/libseccomp2
  • Introduced through: libseccomp/libseccomp2@2.3.1-2.1
  • Fixed in: 2.4.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libseccomp/libseccomp2@2.3.1-2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libseccomp package and not the libseccomp package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

libseccomp before 2.4.0 did not correctly generate 64-bit syscall argument comparisons using the arithmetic operators (LT, GT, LE, GE), which might able to lead to bypassing seccomp filters and potential privilege escalations.

Remediation

Upgrade Debian:unstable libseccomp to version 2.4.1-1 or higher.

References

CVE-2019-9893 vulnerability report

low severity

Off-by-one Error

  • Vulnerable module: libx11/libx11-6
  • Introduced through: libx11/libx11-6@2:1.6.5-1, libx11/libx11-data@2:1.6.5-1 and others
  • Fixed in: 2:1.6.6-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-6@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-data@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-dev@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-doc@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-xcb1@2:1.6.5-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libx11 package and not the libx11 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An issue was discovered in libX11 through 1.6.5. The function XListExtensions in ListExt.c is vulnerable to an off-by-one error caused by malicious server responses, leading to DoS or possibly unspecified other impact.

Remediation

Upgrade Debian:unstable libx11 to version 2:1.6.6-1 or higher.

References

Off-by-one Error vulnerability report

low severity

Out-of-bounds Write

  • Vulnerable module: libx11/libx11-6
  • Introduced through: libx11/libx11-6@2:1.6.5-1, libx11/libx11-data@2:1.6.5-1 and others
  • Fixed in: 2:1.6.6-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-6@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-data@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-dev@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-doc@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-xcb1@2:1.6.5-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libx11 package and not the libx11 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An issue was discovered in libX11 through 1.6.5. The function XListExtensions in ListExt.c interprets a variable as signed instead of unsigned, resulting in an out-of-bounds write (of up to 128 bytes), leading to DoS or remote code execution.

Remediation

Upgrade Debian:unstable libx11 to version 2:1.6.6-1 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Out-of-bounds Write

  • Vulnerable module: perl
  • Introduced through: perl@5.26.1-5, perl/libperl5.26@5.26.1-5 and others
  • Fixed in: 5.36.0-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › perl@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/libperl5.26@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-base@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-modules-5.26@5.26.1-5

NVD Description

Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In Perl 5.34.0, function S_find_uninit_var in sv.c has a stack-based crash that can lead to remote code execution or local privilege escalation.

Remediation

Upgrade Debian:unstable perl to version 5.36.0-4 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Use After Free

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1
  • Fixed in: 3.32.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In SQLite through 3.31.1, the ALTER TABLE implementation has a use-after-free, as demonstrated by an ORDER BY clause that belongs to a compound SELECT statement.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.32.0-1 or higher.

References

Use After Free vulnerability report

low severity

Improper Certificate Validation

  • Vulnerable module: systemd
  • Introduced through: systemd@238-4, systemd/libnss-systemd@238-4 and others
  • Fixed in: 244-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libnss-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libpam-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libsystemd0@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libudev1@238-2
  • Introduced through: openjdk@10-ea-jdk › systemd/systemd-sysv@238-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

systemd 239 through 245 accepts any certificate signed by a trusted certificate authority for DNS Over TLS. Server Name Indication (SNI) is not sent, and there is no hostname validation with the GnuTLS backend. NOTE: This has been disputed by the developer as not a vulnerability since hostname validation does not have anything to do with this issue (i.e. there is no hostname to be sent)

Remediation

Upgrade Debian:unstable systemd to version 244-1 or higher.

References

Improper Certificate Validation vulnerability report

low severity

CVE-2005-2541

  • Vulnerable module: tar
  • Introduced through: tar@1.29b-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tar@1.29b-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream tar package and not the tar package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Tar 1.15.1 does not properly warn the user when extracting setuid or setgid files, which may allow local users or remote attackers to gain privileges.

Remediation

There is no fixed version for Debian:unstable tar.

References

CVE-2005-2541 vulnerability report

low severity

Origin Validation Error

  • Vulnerable module: avahi/libavahi-client3
  • Introduced through: avahi/libavahi-client3@0.7-3.1, avahi/libavahi-common-data@0.7-3.1 and others
  • Fixed in: 0.7-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-client3@0.7-3.1
  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-common-data@0.7-3.1
  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-common3@0.7-3.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream avahi package and not the avahi package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

avahi-daemon in Avahi through 0.6.32 and 0.7 inadvertently responds to IPv6 unicast queries with source addresses that are not on-link, which allows remote attackers to cause a denial of service (traffic amplification) and may cause information leakage by obtaining potentially sensitive information from the responding device via port-5353 UDP packets. NOTE: this may overlap CVE-2015-2809.

Remediation

Upgrade Debian:unstable avahi to version 0.7-5 or higher.

References

Origin Validation Error vulnerability report

low severity

Out-of-bounds Read

  • Vulnerable module: mercurial
  • Introduced through: mercurial@4.5-1 and mercurial/mercurial-common@4.5-1
  • Fixed in: 4.7.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › mercurial@4.5-1
  • Introduced through: openjdk@10-ea-jdk › mercurial/mercurial-common@4.5-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream mercurial package and not the mercurial package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

cext/manifest.c in Mercurial before 4.7.2 has an out-of-bounds read during parsing of a malformed manifest entry.

Remediation

Upgrade Debian:unstable mercurial to version 4.7.2-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Improper Input Validation

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.7-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › cups/libcups2@2.2.7-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream cups package and not the cups package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The browsing feature in the server in CUPS does not filter ANSI escape sequences from shared printer names, which might allow remote attackers to execute arbitrary code via a crafted printer name.

Remediation

There is no fixed version for Debian:unstable cups.

References

Improper Input Validation vulnerability report

low severity

Memory Leak

  • Vulnerable module: giflib/libgif7
  • Introduced through: giflib/libgif7@5.1.4-2
  • Fixed in: 5.2.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › giflib/libgif7@5.1.4-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream giflib package and not the giflib package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A memory leak (out-of-memory) in gif2rgb in util/gif2rgb.c in giflib 5.1.4 allows remote attackers trigger an out of memory exception or denial of service via a gif format file.

Remediation

Upgrade Debian:unstable giflib to version 5.2.2-1 or higher.

References

Memory Leak vulnerability report

low severity

Improper Encoding or Escaping of Output

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Git is a source code management tool. When cloning from a server (or fetching, or pushing), informational or error messages are transported from the remote Git process to the client via the so-called "sideband channel". These messages will be prefixed with "remote:" and printed directly to the standard error output. Typically, this standard error output is connected to a terminal that understands ANSI escape sequences, which Git did not protect against. Most modern terminals support control sequences that can be used by a malicious actor to hide and misrepresent information, or to mislead the user into executing untrusted scripts. As requested on the git-security mailing list, the patches are under discussion on the public mailing list. Users are advised to update as soon as possible. Users unable to upgrade should avoid recursive clones unless they are from trusted sources.

Remediation

There is no fixed version for Debian:unstable git.

References

Improper Encoding or Escaping of Output vulnerability report

low severity

Improper Input Validation

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.24.0-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-1349, CVE-2019-1350, CVE-2019-1352, CVE-2019-1387.

Remediation

Upgrade Debian:unstable git to version 1:2.24.0-2 or higher.

References

Improper Input Validation vulnerability report

low severity

Improper Input Validation

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.24.0-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-1349, CVE-2019-1352, CVE-2019-1354, CVE-2019-1387.

Remediation

Upgrade Debian:unstable git to version 1:2.24.0-2 or higher.

References

Improper Input Validation vulnerability report

low severity

CVE-2019-1010023

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

GNU Libc current is affected by: Re-mapping current loaded library with malicious ELF file. The impact is: In worst case attacker may evaluate privileges. The component is: libld. The attack vector is: Attacker sends 2 ELF files to victim and asks to run ldd on it. ldd execute code. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat.

Remediation

There is no fixed version for Debian:unstable glibc.

References

CVE-2019-1010023 vulnerability report

low severity

Out-of-bounds Write

  • Vulnerable module: libjpeg-turbo/libjpeg62-turbo
  • Introduced through: libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+b1
  • Fixed in: 1:2.0.5-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+b1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libjpeg-turbo package and not the libjpeg-turbo package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Libjpeg-turbo all version have a stack-based buffer overflow in the "transform" component. A remote attacker can send a malformed jpeg file to the service and cause arbitrary code execution or denial of service of the target service.

Remediation

Upgrade Debian:unstable libjpeg-turbo to version 1:2.0.5-1 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Out-of-bounds Write

  • Vulnerable module: libpng1.6/libpng16-16
  • Introduced through: libpng1.6/libpng16-16@1.6.34-1
  • Fixed in: 1.6.37-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libpng1.6/libpng16-16@1.6.34-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An issue has been found in third-party PNM decoding associated with libpng 1.6.35. It is a stack-based buffer overflow in the function get_token in pnm2png.c in pnm2png.

Remediation

Upgrade Debian:unstable libpng1.6 to version 1.6.37-1 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Out-of-bounds Write

  • Vulnerable module: ncurses/libncurses5
  • Introduced through: ncurses/libncurses5@6.1-1, ncurses/libncursesw5@6.1-1 and others
  • Fixed in: 6.2+20200912-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › ncurses/libncurses5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/libncursesw5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/libtinfo5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/ncurses-base@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/ncurses-bin@6.1-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An issue was discovered in ncurses through v6.2-1. _nc_captoinfo in captoinfo.c has a heap-based buffer overflow.

Remediation

Upgrade Debian:unstable ncurses to version 6.2+20200912-1 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Integer Overflow or Wraparound

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.0.9+git181026-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable relevant fixed versions and status.

An issue was discovered in LibTIFF 4.0.9. There is a int32 overflow in multiply_ms in tools/ppm2tiff.c, which can cause a denial of service (crash) or possibly have unspecified other impact via a crafted image file.

Remediation

Upgrade Debian:unstable tiff to version 4.0.9+git181026-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

low severity

Memory Leak

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.0.10-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable relevant fixed versions and status.

The TIFFFdOpen function in tif_unix.c in LibTIFF 4.0.10 has a memory leak, as demonstrated by pal2rgb.

Remediation

Upgrade Debian:unstable tiff to version 4.0.10-4 or higher.

References

Memory Leak vulnerability report

low severity

Integer Underflow

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2
  • Fixed in: 2.31-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An exploitable signed comparison vulnerability exists in the ARMv7 memcpy() implementation of GNU glibc 2.30.9000. Calling memcpy() (on ARMv7 targets that utilize the GNU glibc implementation) with a negative value for the 'num' parameter results in a signed comparison vulnerability. If an attacker underflows the 'num' parameter to memcpy(), this vulnerability could lead to undefined behavior such as writing to out-of-bounds memory and potentially remote code execution. Furthermore, this memcpy() implementation allows for program execution to continue in scenarios where a segmentation fault or crash should have occurred. The dangers occur in that subsequent execution and iterations of this code will be executed with this corrupted data.

Remediation

Upgrade Debian:unstable glibc to version 2.31-2 or higher.

References

Integer Underflow vulnerability report

low severity

Integer Overflow or Wraparound

  • Vulnerable module: libssh2/libssh2-1
  • Introduced through: libssh2/libssh2-1@1.8.0-1
  • Fixed in: 1.9.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libssh2/libssh2-1@1.8.0-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:unstable 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:unstable libssh2 to version 1.9.0-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

low severity

Out-of-bounds Write

  • Vulnerable module: lz4/liblz4-1
  • Introduced through: lz4/liblz4-1@0.0~r131-2+b1
  • Fixed in: 1.9.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › lz4/liblz4-1@0.0~r131-2+b1

NVD Description

Note: Versions mentioned in the description apply only to the upstream lz4 package and not the lz4 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

LZ4 before 1.9.2 has a heap-based buffer overflow in LZ4_write32 (related to LZ4_compress_destSize), affecting applications that call LZ4_compress_fast with a large input. (This issue can also lead to data corruption.) NOTE: the vendor states "only a few specific / uncommon usages of the API are at risk."

Remediation

Upgrade Debian:unstable lz4 to version 1.9.2-1 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Improper Certificate Validation

  • Vulnerable module: perl
  • Introduced through: perl@5.26.1-5, perl/libperl5.26@5.26.1-5 and others
  • Fixed in: 5.38.2-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › perl@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/libperl5.26@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-base@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-modules-5.26@5.26.1-5

NVD Description

Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

HTTP::Tiny before 0.083, a Perl core module since 5.13.9 and available standalone on CPAN, has an insecure default TLS configuration where users must opt in to verify certificates.

Remediation

Upgrade Debian:unstable perl to version 5.38.2-2 or higher.

References

Improper Certificate Validation vulnerability report

low severity

Improper Check for Dropped Privileges

  • Vulnerable module: bash
  • Introduced through: bash@4.4.18-1.1
  • Fixed in: 5.1~rc1-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › bash@4.4.18-1.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream bash package and not the bash package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An issue was discovered in disable_priv_mode in shell.c in GNU Bash through 5.0 patch 11. By default, if Bash is run with its effective UID not equal to its real UID, it will drop privileges by setting its effective UID to its real UID. However, it does so incorrectly. On Linux and other systems that support "saved UID" functionality, the saved UID is not dropped. An attacker with command execution in the shell can use "enable -f" for runtime loading of a new builtin, which can be a shared object that calls setuid() and therefore regains privileges. However, binaries running with an effective UID of 0 are unaffected.

Remediation

Upgrade Debian:unstable bash to version 5.1~rc1-2 or higher.

References

Improper Check for Dropped Privileges vulnerability report

low severity

Out-of-Bounds

  • Vulnerable module: elfutils/libelf1
  • Introduced through: elfutils/libelf1@0.170-0.3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › elfutils/libelf1@0.170-0.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream elfutils package and not the elfutils package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A vulnerability was found in GNU elfutils 0.192. It has been declared as critical. Affected by this vulnerability is the function dump_data_section/print_string_section of the file readelf.c of the component eu-readelf. The manipulation of the argument z/x leads to buffer overflow. An attack has to be approached locally. The exploit has been disclosed to the public and may be used. The identifier of the patch is 73db9d2021cab9e23fd734b0a76a612d52a6f1db. It is recommended to apply a patch to fix this issue.

Remediation

There is no fixed version for Debian:unstable elfutils.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

  • Vulnerable module: elfutils/libelf1
  • Introduced through: elfutils/libelf1@0.170-0.3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › elfutils/libelf1@0.170-0.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream elfutils package and not the elfutils package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A vulnerability, which was classified as critical, was found in GNU elfutils 0.192. This affects the function process_symtab of the file readelf.c of the component eu-readelf. The manipulation of the argument D/a leads to buffer overflow. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used. The identifier of the patch is 5e5c0394d82c53e97750fe7b18023e6f84157b81. It is recommended to apply a patch to fix this issue.

Remediation

There is no fixed version for Debian:unstable elfutils.

References

Out-of-Bounds vulnerability report

low severity

Out-of-bounds Write

  • Vulnerable module: freetype/libfreetype6
  • Introduced through: freetype/libfreetype6@2.8.1-2
  • Fixed in: 2.12.1+dfsg-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › freetype/libfreetype6@2.8.1-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream freetype package and not the freetype package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

ftbench.c in FreeType Demo Programs through 2.12.1 has a heap-based buffer overflow.

Remediation

Upgrade Debian:unstable freetype to version 2.12.1+dfsg-3 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Integer Overflow or Wraparound

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.56.1-2 and glib2.0/libglib2.0-data@2.56.1-2
  • Fixed in: 2.66.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-0@2.56.1-2
  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-data@2.56.1-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

GNOME GLib before 2.65.3 has an integer overflow, that might lead to an out-of-bounds write, in g_option_group_add_entries. NOTE: the vendor's position is "Realistically this is not a security issue. The standard pattern is for callers to provide a static list of option entries in a fixed number of calls to g_option_group_add_entries()." The researcher states that this pattern is undocumented

Remediation

Upgrade Debian:unstable glib2.0 to version 2.66.0-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

low severity

Improper Resource Shutdown or Release

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2
  • Fixed in: 2.28-6

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The string component in the GNU C Library (aka glibc or libc6) through 2.28, when running on the x32 architecture, incorrectly attempts to use a 64-bit register for size_t in assembly codes, which can lead to a segmentation fault or possibly unspecified other impact, as demonstrated by a crash in __memmove_avx_unaligned_erms in sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S during a memcpy.

Remediation

Upgrade Debian:unstable glibc to version 2.28-6 or higher.

References

Improper Resource Shutdown or Release vulnerability report

low severity

Out-of-bounds Write

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2
  • Fixed in: 2.27-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An AVX-512-optimized implementation of the mempcpy function in the GNU C Library (aka glibc or libc6) 2.27 and earlier may write data beyond the target buffer, leading to a buffer overflow in __mempcpy_avx512_no_vzeroupper.

Remediation

Upgrade Debian:unstable glibc to version 2.27-4 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Out-of-bounds Write

  • Vulnerable module: inetutils/inetutils-ping
  • Introduced through: inetutils/inetutils-ping@2:1.9.4-3
  • Fixed in: 2:1.9.4-11

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › inetutils/inetutils-ping@2:1.9.4-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream inetutils package and not the inetutils package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Insufficient validation of environment variables in the telnet client supplied in Junos OS can lead to stack-based buffer overflows, which can be exploited to bypass veriexec restrictions on Junos OS. A stack-based overflow is present in the handling of environment variables when connecting via the telnet client to remote telnet servers. This issue only affects the telnet client — accessible from the CLI or shell — in Junos OS. Inbound telnet services are not affected by this issue. This issue affects: Juniper Networks Junos OS: 12.3 versions prior to 12.3R12-S13; 12.3X48 versions prior to 12.3X48-D80; 14.1X53 versions prior to 14.1X53-D130, 14.1X53-D49; 15.1 versions prior to 15.1F6-S12, 15.1R7-S4; 15.1X49 versions prior to 15.1X49-D170; 15.1X53 versions prior to 15.1X53-D237, 15.1X53-D496, 15.1X53-D591, 15.1X53-D69; 16.1 versions prior to 16.1R3-S11, 16.1R7-S4; 16.2 versions prior to 16.2R2-S9; 17.1 versions prior to 17.1R3; 17.2 versions prior to 17.2R1-S8, 17.2R2-S7, 17.2R3-S1; 17.3 versions prior to 17.3R3-S4; 17.4 versions prior to 17.4R1-S6, 17.4R2-S3, 17.4R3; 18.1 versions prior to 18.1R2-S4, 18.1R3-S3; 18.2 versions prior to 18.2R1-S5, 18.2R2-S2, 18.2R3; 18.2X75 versions prior to 18.2X75-D40; 18.3 versions prior to 18.3R1-S3, 18.3R2; 18.4 versions prior to 18.4R1-S2, 18.4R2.

Remediation

Upgrade Debian:unstable inetutils to version 2:1.9.4-11 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Out-of-bounds Write

  • Vulnerable module: libjpeg-turbo/libjpeg62-turbo
  • Introduced through: libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+b1
  • Fixed in: 1:2.0.5-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+b1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libjpeg-turbo package and not the libjpeg-turbo package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In generate_jsimd_ycc_rgb_convert_neon of jsimd_arm64_neon.S, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execution in an unprivileged process with no additional execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-8.0 Android-8.1 Android-9 Android-10Android ID: A-120551338

Remediation

Upgrade Debian:unstable libjpeg-turbo to version 1:2.0.5-1 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Use After Free

  • Vulnerable module: libxkbcommon/libxkbcommon0
  • Introduced through: libxkbcommon/libxkbcommon0@0.8.0-1
  • Fixed in: 0.8.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxkbcommon/libxkbcommon0@0.8.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxkbcommon package and not the libxkbcommon package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An invalid free in ExprAppendMultiKeysymList in xkbcomp/ast-build.c in xkbcommon before 0.8.1 could be used by local attackers to crash xkbcommon keymap parsers or possibly have unspecified other impact by supplying a crafted keymap file.

Remediation

Upgrade Debian:unstable libxkbcommon to version 0.8.2-1 or higher.

References

Use After Free vulnerability report

low severity

Out-of-Bounds

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.36.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nss/libnss3@2:3.36.1-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nss package and not the nss package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Heap-based buffer overflow in the __get_page function in lib/dbm/src/h_page.c in Mozilla Network Security Services (NSS) allows context-dependent attackers to have unspecified impact using a crafted cert8.db file.

Remediation

There is no fixed version for Debian:unstable nss.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.36.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nss/libnss3@2:3.36.1-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nss package and not the nss package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The __hash_open function in hash.c:229 in Mozilla Network Security Services (NSS) allows context-dependent attackers to cause a denial of service (floating point exception and crash) via a crafted cert8.db file.

Remediation

There is no fixed version for Debian:unstable nss.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.36.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nss/libnss3@2:3.36.1-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nss package and not the nss package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Heap-based buffer overflow in the __hash_open function in lib/dbm/src/hash.c in Mozilla Network Security Services (NSS) allows context-dependent attackers to have unspecified impact using a crafted cert8.db file.

Remediation

There is no fixed version for Debian:unstable nss.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.36.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nss/libnss3@2:3.36.1-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nss package and not the nss package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Heap-based buffer overflow in the alloc_segs function in lib/dbm/src/hash.c in Mozilla Network Security Services (NSS) allows context-dependent attackers to have unspecified impact using a crafted cert8.db file.

Remediation

There is no fixed version for Debian:unstable nss.

References

Out-of-Bounds vulnerability report

low severity

Integer Overflow or Wraparound

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:7.6p1-4
  • Fixed in: 1:8.1p1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssh/openssh-client@1:7.6p1-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

OpenSSH 7.7 through 7.9 and 8.x before 8.1, when compiled with an experimental key type, has a pre-authentication integer overflow if a client or server is configured to use a crafted XMSS key. This leads to memory corruption and local code execution because of an error in the XMSS key parsing algorithm. NOTE: the XMSS implementation is considered experimental in all released OpenSSH versions, and there is no supported way to enable it when building portable OpenSSH.

Remediation

Upgrade Debian:unstable openssh to version 1:8.1p1-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

low severity

Incorrect Permission Assignment for Critical Resource

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.5-1 and shadow/passwd@1:4.5-1
  • Fixed in: 1:4.8.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › shadow/login@1:4.5-1
  • Introduced through: openjdk@10-ea-jdk › shadow/passwd@1:4.5-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream shadow package and not the shadow package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

shadow 4.8, in certain circumstances affecting at least Gentoo, Arch Linux, and Void Linux, allows local users to obtain root access because setuid programs are misconfigured. Specifically, this affects shadow 4.8 when compiled using --with-libpam but without explicitly passing --disable-account-tools-setuid, and without a PAM configuration suitable for use with setuid account management tools. This combination leads to account management tools (groupadd, groupdel, groupmod, useradd, userdel, usermod) that can easily be used by unprivileged local users to escalate privileges to root in multiple ways. This issue became much more relevant in approximately December 2019 when an unrelated bug was fixed (i.e., the chmod calls to suidusbins were fixed in the upstream Makefile which is now included in the release version 4.8).

Remediation

Upgrade Debian:unstable shadow to version 1:4.8.1-1 or higher.

References

Incorrect Permission Assignment for Critical Resource vulnerability report

low severity

Out-of-Bounds

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.7.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable relevant fixed versions and status.

A vulnerability was found in LibTIFF up to 4.7.0. It has been declared as critical. This vulnerability affects the function get_histogram of the file tools/tiffmedian.c. The manipulation leads to use after free. The attack needs to be approached locally. The exploit has been disclosed to the public and may be used. The patch is identified as fe10872e53efba9cc36c66ac4ab3b41a839d5172. It is recommended to apply a patch to fix this issue.

Remediation

Upgrade Debian:unstable tiff to version 4.7.1-1 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.7.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable relevant fixed versions and status.

A vulnerability was found in LibTIFF up to 4.7.0. It has been rated as critical. This issue affects the function setrow of the file tools/thumbnail.c. The manipulation leads to buffer overflow. An attack has to be approached locally. The patch is named e8c9d6c616b19438695fd829e58ae4fde5bfbc22. It is recommended to apply a patch to fix this issue. This vulnerability only affects products that are no longer supported by the maintainer.

Remediation

Upgrade Debian:unstable tiff to version 4.7.1-1 or higher.

References

Out-of-Bounds vulnerability report

low severity

Incorrect Default Permissions

  • Vulnerable module: xdg-user-dirs
  • Introduced through: xdg-user-dirs@0.17-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › xdg-user-dirs@0.17-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream xdg-user-dirs package and not the xdg-user-dirs package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

It was found that system umask policy is not being honored when creating XDG user directories, since Xsession sources xdg-user-dirs.sh before setting umask policy. This only affects xdg-user-dirs before 0.15.5 as shipped with Red Hat Enterprise Linux.

Remediation

There is no fixed version for Debian:unstable xdg-user-dirs.

References

Incorrect Default Permissions vulnerability report

low severity

Out-of-bounds Read

  • Vulnerable module: cairo/libcairo-gobject2
  • Introduced through: cairo/libcairo-gobject2@1.15.10-3 and cairo/libcairo2@1.15.10-3
  • Fixed in: 1.16.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › cairo/libcairo-gobject2@1.15.10-3
  • Introduced through: openjdk@10-ea-jdk › cairo/libcairo2@1.15.10-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream cairo package and not the cairo package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

cairo-truetype-subset.c in cairo 1.15.6 and earlier allows remote attackers to cause a denial of service (out-of-bounds read) because of mishandling of an unexpected malloc(0) call.

Remediation

Upgrade Debian:unstable cairo to version 1.16.0-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Memory Leak

  • Vulnerable module: colord/libcolord2
  • Introduced through: colord/libcolord2@1.3.3-2
  • Fixed in: 1.4.6-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › colord/libcolord2@1.3.3-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream colord package and not the colord package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

There are two Information Disclosure vulnerabilities in colord, and they lie in colord/src/cd-device-db.c and colord/src/cd-profile-db.c separately. They exist because the 'err_msg' of 'sqlite3_exec' is not releasing after use, while libxml2 emphasizes that the caller needs to release it.

Remediation

Upgrade Debian:unstable colord to version 1.4.6-1 or higher.

References

Memory Leak vulnerability report

low severity

Out-of-Bounds

  • Vulnerable module: elfutils/libelf1
  • Introduced through: elfutils/libelf1@0.170-0.3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › elfutils/libelf1@0.170-0.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream elfutils package and not the elfutils package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A vulnerability has been found in GNU elfutils 0.192 and classified as critical. This vulnerability affects the function __libdw_thread_tail in the library libdw_alloc.c of the component eu-readelf. The manipulation of the argument w leads to memory corruption. The attack can be initiated remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The name of the patch is 2636426a091bd6c6f7f02e49ab20d4cdc6bfc753. It is recommended to apply a patch to fix this issue.

Remediation

There is no fixed version for Debian:unstable elfutils.

References

Out-of-Bounds vulnerability report

low severity

Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion')

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.5-3
  • Fixed in: 2.6.1-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › expat/libexpat1@2.2.5-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

libexpat through 2.6.1 allows an XML Entity Expansion attack when there is isolated use of external parsers (created via XML_ExternalEntityParserCreate).

Remediation

Upgrade Debian:unstable expat to version 2.6.1-2 or higher.

References

Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion') vulnerability report

low severity

Exposure of Resource to Wrong Sphere

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The --mirror documentation for Git through 2.35.1 does not mention the availability of deleted content, aka the "GitBleed" issue. This could present a security risk if information-disclosure auditing processes rely on a clone operation without the --mirror option. Note: This has been disputed by multiple 3rd parties who believe this is an intended feature of the git binary and does not pose a security risk.

Remediation

There is no fixed version for Debian:unstable git.

References

Exposure of Resource to Wrong Sphere vulnerability report

low severity

Out-of-bounds Read

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.17.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In Git before 2.13.7, 2.14.x before 2.14.4, 2.15.x before 2.15.2, 2.16.x before 2.16.4, and 2.17.x before 2.17.1, code to sanity-check pathnames on NTFS can result in reading out-of-bounds memory.

Remediation

Upgrade Debian:unstable git to version 1:2.17.1-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Use of Incorrectly-Resolved Name or Reference

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.24.0-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A tampering vulnerability exists when Git for Visual Studio improperly handles virtual drive paths, aka 'Git for Visual Studio Tampering Vulnerability'.

Remediation

Upgrade Debian:unstable git to version 1:2.24.0-2 or higher.

References

Use of Incorrectly-Resolved Name or Reference vulnerability report

low severity

Integer Overflow or Wraparound

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.56.1-2 and glib2.0/libglib2.0-data@2.56.1-2
  • Fixed in: 2.84.3-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-0@2.56.1-2
  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-data@2.56.1-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw was found in how GLib’s GString manages memory when adding data to strings. If a string is already very large, combining it with more input can cause a hidden overflow in the size calculation. This makes the system think it has enough memory when it doesn’t. As a result, data may be written past the end of the allocated memory, leading to crashes or memory corruption.

Remediation

Upgrade Debian:unstable glib2.0 to version 2.84.3-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

low severity

Out-of-bounds Read

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.56.1-2 and glib2.0/libglib2.0-data@2.56.1-2
  • Fixed in: 2.58.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-0@2.56.1-2
  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-data@2.56.1-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

GNOME GLib 2.56.1 has an out-of-bounds read vulnerability in g_markup_parse_context_parse() in gmarkup.c, related to utf8_str().

Remediation

Upgrade Debian:unstable glib2.0 to version 2.58.0-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

CVE-2021-43396

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2
  • Fixed in: 2.32-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In iconvdata/iso-2022-jp-3.c in the GNU C Library (aka glibc) 2.34, remote attackers can force iconv() to emit a spurious '\0' character via crafted ISO-2022-JP-3 data that is accompanied by an internal state reset. This may affect data integrity in certain iconv() use cases. NOTE: the vendor states "the bug cannot be invoked through user input and requires iconv to be invoked with a NULL inbuf, which ought to require a separate application bug to do so unintentionally. Hence there's no security impact to the bug.

Remediation

Upgrade Debian:unstable glibc to version 2.32-5 or higher.

References

CVE-2021-43396 vulnerability report

low severity

Uncontrolled Recursion

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In the GNU C Library (aka glibc or libc6) through 2.29, check_dst_limits_calc_pos_1 in posix/regexec.c has Uncontrolled Recursion, as demonstrated by '(|)(\1\1)*' in grep, a different issue than CVE-2018-20796. NOTE: the software maintainer disputes that this is a vulnerability because the behavior occurs only with a crafted pattern

Remediation

There is no fixed version for Debian:unstable glibc.

References

Uncontrolled Recursion vulnerability report

low severity

Uncontrolled Recursion

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In the GNU C Library (aka glibc or libc6) through 2.29, check_dst_limits_calc_pos_1 in posix/regexec.c has Uncontrolled Recursion, as demonstrated by '(\227|)(\1\1|t1|\\2537)+' in grep.

Remediation

There is no fixed version for Debian:unstable glibc.

References

Uncontrolled Recursion vulnerability report

low severity

Key Management Errors

  • Vulnerable module: gnupg2/dirmngr
  • Introduced through: gnupg2/dirmngr@2.2.5-1, gnupg2/gnupg@2.2.5-1 and others
  • Fixed in: 2.2.7-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gnupg2/dirmngr@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gnupg@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gnupg-l10n@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gnupg-utils@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpg@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpg-agent@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpg-wks-client@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpg-wks-server@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpgconf@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpgsm@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpgv@2.2.5-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream gnupg2 package and not the gnupg2 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

GnuPG 2.2.4 and 2.2.5 does not enforce a configuration in which key certification requires an offline master Certify key, which results in apparently valid certifications that occurred only with access to a signing subkey.

Remediation

Upgrade Debian:unstable gnupg2 to version 2.2.7-1 or higher.

References

Key Management Errors vulnerability report

low severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: gnupg2/dirmngr
  • Introduced through: gnupg2/dirmngr@2.2.5-1, gnupg2/gnupg@2.2.5-1 and others
  • Fixed in: 2.2.19-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gnupg2/dirmngr@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gnupg@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gnupg-l10n@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gnupg-utils@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpg@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpg-agent@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpg-wks-client@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpg-wks-server@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpgconf@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpgsm@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpgv@2.2.5-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream gnupg2 package and not the gnupg2 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw was found in the way certificate signatures could be forged using collisions found in the SHA-1 algorithm. An attacker could use this weakness to create forged certificate signatures. This issue affects GnuPG versions before 2.2.18.

Remediation

Upgrade Debian:unstable gnupg2 to version 2.2.19-1 or higher.

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

low severity

Integer Overflow or Wraparound

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.16-2, krb5/libk5crypto3@1.16-2 and others

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › krb5/libgssapi-krb5-2@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libk5crypto3@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libkrb5-3@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libkrb5support0@1.16-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An issue was discovered in MIT Kerberos 5 (aka krb5) through 1.16. There is a variable "dbentry->n_key_data" in kadmin/dbutil/dump.c that can store 16-bit data but unknowingly the developer has assigned a "u4" variable to it, which is for 32-bit data. An attacker can use this vulnerability to affect other artifacts of the database as we know that a Kerberos database dump file contains trusted data.

Remediation

There is no fixed version for Debian:unstable krb5.

References

Integer Overflow or Wraparound vulnerability report

low severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: libgcrypt20
  • Introduced through: libgcrypt20@1.8.1-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libgcrypt20@1.8.1-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream libgcrypt20 package and not the libgcrypt20 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

cipher/elgamal.c in Libgcrypt through 1.8.2, when used to encrypt messages directly, improperly encodes plaintexts, which allows attackers to obtain sensitive information by reading ciphertext data (i.e., it does not have semantic security in face of a ciphertext-only attack). The Decisional Diffie-Hellman (DDH) assumption does not hold for Libgcrypt's ElGamal implementation.

Remediation

There is no fixed version for Debian:unstable libgcrypt20.

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

low severity

Excessive Iteration

  • Vulnerable module: libjpeg-turbo/libjpeg62-turbo
  • Introduced through: libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+b1
  • Fixed in: 1:2.0.5-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+b1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libjpeg-turbo package and not the libjpeg-turbo package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

libjpeg 9c has a large loop because read_pixel in rdtarga.c mishandles EOF.

Remediation

Upgrade Debian:unstable libjpeg-turbo to version 1:2.0.5-1 or higher.

References

Excessive Iteration vulnerability report

low severity

Improper Input Validation

  • Vulnerable module: libx11/libx11-6
  • Introduced through: libx11/libx11-6@2:1.6.5-1, libx11/libx11-data@2:1.6.5-1 and others
  • Fixed in: 2:1.6.6-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-6@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-data@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-dev@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-doc@2:1.6.5-1
  • Introduced through: openjdk@10-ea-jdk › libx11/libx11-xcb1@2:1.6.5-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libx11 package and not the libx11 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An issue was discovered in XListExtensions in ListExt.c in libX11 through 1.6.5. A malicious server can send a reply in which the first string overflows, causing a variable to be set to NULL that will be freed later on, leading to DoS (segmentation fault).

Remediation

Upgrade Debian:unstable libx11 to version 2:1.6.6-1 or higher.

References

Improper Input Validation vulnerability report

low severity

NULL Pointer Dereference

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.9.10+dfsg-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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:unstable relevant fixed versions and status.

A NULL pointer dereference vulnerability exists in the xpath.c:xmlXPathCompOpEval() function of libxml2 through 2.9.8 when parsing an invalid XPath expression in the XPATH_OP_AND or XPATH_OP_OR case. Applications processing untrusted XSL format inputs with the use of the libxml2 library may be vulnerable to a denial of service attack due to a crash of the application.

Remediation

Upgrade Debian:unstable libxml2 to version 2.9.10+dfsg-2 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

Improper Input Validation

  • Vulnerable module: nghttp2/libnghttp2-14
  • Introduced through: nghttp2/libnghttp2-14@1.31.0-1
  • Fixed in: 1.31.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nghttp2/libnghttp2-14@1.31.0-1

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:unstable relevant fixed versions and status.

nghttp2 version >= 1.10.0 and nghttp2 <= v1.31.0 contains an Improper Input Validation CWE-20 vulnerability in ALTSVC frame handling that can result in segmentation fault leading to denial of service. This attack appears to be exploitable via network client. This vulnerability appears to have been fixed in >= 1.31.1.

Remediation

Upgrade Debian:unstable nghttp2 to version 1.31.1-1 or higher.

References

Improper Input Validation vulnerability report

low severity

Cryptographic Issues

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1 and openldap/libldap-common@2.4.45+dfsg-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-2.4-2@2.4.45+dfsg-1
  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-common@2.4.45+dfsg-1

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:unstable 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:unstable openldap.

References

Cryptographic Issues vulnerability report

low severity

CVE-2019-13565

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1 and openldap/libldap-common@2.4.45+dfsg-1
  • Fixed in: 2.4.48+dfsg-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-2.4-2@2.4.45+dfsg-1
  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-common@2.4.45+dfsg-1

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:unstable relevant fixed versions and status.

An issue was discovered in OpenLDAP 2.x before 2.4.48. When using SASL authentication and session encryption, and relying on the SASL security layers in slapd access controls, it is possible to obtain access that would otherwise be denied via a simple bind for any identity covered in those ACLs. After the first SASL bind is completed, the sasl_ssf value is retained for all new non-SASL connections. Depending on the ACL configuration, this can affect different types of operations (searches, modifications, etc.). In other words, a successful authorization step completed by one user affects the authorization requirement for a different user.

Remediation

Upgrade Debian:unstable openldap to version 2.4.48+dfsg-1 or higher.

References

CVE-2019-13565 vulnerability report

low severity

Out-of-Bounds

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1 and openldap/libldap-common@2.4.45+dfsg-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-2.4-2@2.4.45+dfsg-1
  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-common@2.4.45+dfsg-1

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:unstable 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:unstable openldap.

References

Out-of-Bounds vulnerability report

low severity

Improper Input Validation

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:7.6p1-4
  • Fixed in: 1:8.3p1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssh/openssh-client@1:7.6p1-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The scp client in OpenSSH 8.2 incorrectly sends duplicate responses to the server upon a utimes system call failure, which allows a malicious unprivileged user on the remote server to overwrite arbitrary files in the client's download directory by creating a crafted subdirectory anywhere on the remote server. The victim must use the command scp -rp to download a file hierarchy containing, anywhere inside, this crafted subdirectory. NOTE: the vendor points out that "this attack can achieve no more than a hostile peer is already able to achieve within the scp protocol" and "utimes does not fail under normal circumstances.

Remediation

Upgrade Debian:unstable openssh to version 1:8.3p1-1 or higher.

References

Improper Input Validation vulnerability report

low severity

Key Management Errors

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 1.1.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

During key agreement in a TLS handshake using a DH(E) based ciphersuite a malicious server can send a very large prime value to the client. This will cause the client to spend an unreasonably long period of time generating a key for this prime resulting in a hang until the client has finished. This could be exploited in a Denial Of Service attack. Fixed in OpenSSL 1.1.0i-dev (Affected 1.1.0-1.1.0h). Fixed in OpenSSL 1.0.2p-dev (Affected 1.0.2-1.0.2o).

Remediation

Upgrade Debian:unstable openssl to version 1.1.1-1 or higher.

References

Key Management Errors vulnerability report

low severity

Integer Overflow or Wraparound

  • Vulnerable module: pcre2/libpcre2-8-0
  • Introduced through: pcre2/libpcre2-8-0@10.31-3
  • Fixed in: 10.42-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › pcre2/libpcre2-8-0@10.31-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream pcre2 package and not the pcre2 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Integer overflow vulnerability in pcre2test before 10.41 allows attackers to cause a denial of service or other unspecified impacts via negative input.

Remediation

Upgrade Debian:unstable pcre2 to version 10.42-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

low severity

CVE-2019-19244

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1
  • Fixed in: 3.30.1+fossil191229-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

sqlite3Select in select.c in SQLite 3.30.1 allows a crash if a sub-select uses both DISTINCT and window functions, and also has certain ORDER BY usage.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.30.1+fossil191229-1 or higher.

References

CVE-2019-19244 vulnerability report

low severity

Improper Validation of Array Index

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1
  • Fixed in: 3.39.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

SQLite 1.0.12 through 3.39.x before 3.39.2 sometimes allows an array-bounds overflow if billions of bytes are used in a string argument to a C API.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.39.2-1 or higher.

References

Improper Validation of Array Index vulnerability report

low severity

NULL Pointer Dereference

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1
  • Fixed in: 3.27.2-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In SQLite 3.27.2, interleaving reads and writes in a single transaction with an fts5 virtual table will lead to a NULL Pointer Dereference in fts5ChunkIterate in sqlite3.c. This is related to ext/fts5/fts5_hash.c and ext/fts5/fts5_index.c.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.27.2-2 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

Out-of-bounds Read

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1
  • Fixed in: 3.36.0-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A segmentation fault can occur in the sqlite3.exe command-line component of SQLite 3.36.0 via the idxGetTableInfo function when there is a crafted SQL query. NOTE: the vendor disputes the relevance of this report because a sqlite3.exe user already has full privileges (e.g., is intentionally allowed to execute commands). This report does NOT imply any problem in the SQLite library.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.36.0-2 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-bounds Read

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1
  • Fixed in: 3.27.2-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In SQLite 3.27.2, running fts5 prefix queries inside a transaction could trigger a heap-based buffer over-read in fts5HashEntrySort in sqlite3.c, which may lead to an information leak. This is related to ext/fts5/fts5_hash.c.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.27.2-2 or higher.

References

Out-of-bounds Read vulnerability report

low severity

NULL Pointer Dereference

  • Vulnerable module: tar
  • Introduced through: tar@1.29b-2
  • Fixed in: 1.32+dfsg-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tar@1.29b-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream tar package and not the tar package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

pax_decode_header in sparse.c in GNU Tar before 1.32 had a NULL pointer dereference when parsing certain archives that have malformed extended headers.

Remediation

Upgrade Debian:unstable tar to version 1.32+dfsg-1 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

Missing Release of Resource after Effective Lifetime

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff.

References

Missing Release of Resource after Effective Lifetime vulnerability report

low severity

OS Command Injection

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:7.6p1-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssh/openssh-client@1:7.6p1-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

scp in OpenSSH through 8.3p1 allows command injection in the scp.c toremote function, as demonstrated by backtick characters in the destination argument. NOTE: the vendor reportedly has stated that they intentionally omit validation of "anomalous argument transfers" because that could "stand a great chance of breaking existing workflows."

Remediation

There is no fixed version for Debian:unstable openssh.

References

OS Command Injection vulnerability report

low severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 1.1.1c-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

ChaCha20-Poly1305 is an AEAD cipher, and requires a unique nonce input for every encryption operation. RFC 7539 specifies that the nonce value (IV) should be 96 bits (12 bytes). OpenSSL allows a variable nonce length and front pads the nonce with 0 bytes if it is less than 12 bytes. However it also incorrectly allows a nonce to be set of up to 16 bytes. In this case only the last 12 bytes are significant and any additional leading bytes are ignored. It is a requirement of using this cipher that nonce values are unique. Messages encrypted using a reused nonce value are susceptible to serious confidentiality and integrity attacks. If an application changes the default nonce length to be longer than 12 bytes and then makes a change to the leading bytes of the nonce expecting the new value to be a new unique nonce then such an application could inadvertently encrypt messages with a reused nonce. Additionally the ignored bytes in a long nonce are not covered by the integrity guarantee of this cipher. Any application that relies on the integrity of these ignored leading bytes of a long nonce may be further affected. Any OpenSSL internal use of this cipher, including in SSL/TLS, is safe because no such use sets such a long nonce value. However user applications that use this cipher directly and set a non-default nonce length to be longer than 12 bytes may be vulnerable. OpenSSL versions 1.1.1 and 1.1.0 are affected by this issue. Due to the limited scope of affected deployments this has been assessed as low severity and therefore we are not creating new releases at this time. Fixed in OpenSSL 1.1.1c (Affected 1.1.1-1.1.1b). Fixed in OpenSSL 1.1.0k (Affected 1.1.0-1.1.0j).

Remediation

Upgrade Debian:unstable openssl to version 1.1.1c-1 or higher.

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

low severity

CVE-2012-2663

  • Vulnerable module: iptables/libip4tc0
  • Introduced through: iptables/libip4tc0@1.6.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › iptables/libip4tc0@1.6.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream iptables package and not the iptables package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

extensions/libxt_tcp.c in iptables through 1.4.21 does not match TCP SYN+FIN packets in --syn rules, which might allow remote attackers to bypass intended firewall restrictions via crafted packets. NOTE: the CVE-2012-6638 fix makes this issue less relevant.

Remediation

There is no fixed version for Debian:unstable iptables.

References

CVE-2012-2663 vulnerability report

low severity

Out-of-bounds Read

  • Vulnerable module: giflib/libgif7
  • Introduced through: giflib/libgif7@5.1.4-2
  • Fixed in: 5.2.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › giflib/libgif7@5.1.4-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream giflib package and not the giflib package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An issue was discovered in giflib through 5.1.4. DumpScreen2RGB in gif2rgb.c has a heap-based buffer over-read.

Remediation

Upgrade Debian:unstable giflib to version 5.2.2-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-bounds Write

  • Vulnerable module: giflib/libgif7
  • Introduced through: giflib/libgif7@5.1.4-2
  • Fixed in: 5.2.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › giflib/libgif7@5.1.4-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream giflib package and not the giflib package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Buffer Overflow vulnerability in GifLib Project GifLib v.5.2.1 allows a local attacker to obtain sensitive information via the DumpSCreen2RGB function in gif2rgb.c

Remediation

Upgrade Debian:unstable giflib to version 5.2.2-1 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Inappropriate Encoding for Output Context

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:7.6p1-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssh/openssh-client@1:7.6p1-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In OpenSSH 7.9, due to accepting and displaying arbitrary stderr output from the server, a malicious server (or Man-in-The-Middle attacker) can manipulate the client output, for example to use ANSI control codes to hide additional files being transferred.

Remediation

There is no fixed version for Debian:unstable openssh.

References

Inappropriate Encoding for Output Context vulnerability report

low severity

Improper Input Validation

  • Vulnerable module: systemd
  • Introduced through: systemd@238-4, systemd/libnss-systemd@238-4 and others
  • Fixed in: 246-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libnss-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libpam-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libsystemd0@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libudev1@238-2
  • Introduced through: openjdk@10-ea-jdk › systemd/systemd-sysv@238-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

systemd through v245 mishandles numerical usernames such as ones composed of decimal digits or 0x followed by hex digits, as demonstrated by use of root privileges when privileges of the 0x0 user account were intended. NOTE: this issue exists because of an incomplete fix for CVE-2017-1000082.

Remediation

Upgrade Debian:unstable systemd to version 246-2 or higher.

References

Improper Input Validation vulnerability report

low severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: cairo/libcairo-gobject2
  • Introduced through: cairo/libcairo-gobject2@1.15.10-3 and cairo/libcairo2@1.15.10-3
  • Fixed in: 1.17.8-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › cairo/libcairo-gobject2@1.15.10-3
  • Introduced through: openjdk@10-ea-jdk › cairo/libcairo2@1.15.10-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream cairo package and not the cairo package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An issue was discovered in cairo 1.16.0. There is an infinite loop in the function _arc_error_normalized in the file cairo-arc.c, related to _arc_max_angle_for_tolerance_normalized.

Remediation

Upgrade Debian:unstable cairo to version 1.17.8-3 or higher.

References

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability report

low severity

Out-of-bounds Write

  • Vulnerable module: cairo/libcairo-gobject2
  • Introduced through: cairo/libcairo-gobject2@1.15.10-3 and cairo/libcairo2@1.15.10-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › cairo/libcairo-gobject2@1.15.10-3
  • Introduced through: openjdk@10-ea-jdk › cairo/libcairo2@1.15.10-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream cairo package and not the cairo package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

cairo through 1.15.14 has an out-of-bounds stack-memory write during processing of a crafted document by WebKitGTK+ because of the interaction between cairo-rectangular-scan-converter.c (the generate and render_rows functions) and cairo-image-compositor.c (the _cairo_image_spans_and_zero function).

Remediation

There is no fixed version for Debian:unstable cairo.

References

Out-of-bounds Write vulnerability report

low severity

Reachable Assertion

  • Vulnerable module: cairo/libcairo-gobject2
  • Introduced through: cairo/libcairo-gobject2@1.15.10-3 and cairo/libcairo2@1.15.10-3
  • Fixed in: 1.18.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › cairo/libcairo-gobject2@1.15.10-3
  • Introduced through: openjdk@10-ea-jdk › cairo/libcairo2@1.15.10-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream cairo package and not the cairo package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An issue was discovered in cairo 1.16.0. There is an assertion problem in the function _cairo_arc_in_direction in the file cairo-arc.c.

Remediation

Upgrade Debian:unstable cairo to version 1.18.0-1 or higher.

References

Reachable Assertion vulnerability report

low severity

Improper Input Validation

  • Vulnerable module: coreutils
  • Introduced through: coreutils@8.28-1
  • Fixed in: 9.4-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › coreutils@8.28-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream coreutils package and not the coreutils package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

chroot in GNU coreutils, when used with --userspec, allows local users to escape to the parent session via a crafted TIOCSTI ioctl call, which pushes characters to the terminal's input buffer.

Remediation

Upgrade Debian:unstable coreutils to version 9.4-1 or higher.

References

Improper Input Validation vulnerability report

low severity

Improper Validation of Integrity Check Value

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.79.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable 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

Upgrade Debian:unstable curl to version 7.79.1-1 or higher.

References

Improper Validation of Integrity Check Value vulnerability report

low severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: elfutils/libelf1
  • Introduced through: elfutils/libelf1@0.170-0.3
  • Fixed in: 0.176-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › elfutils/libelf1@0.170-0.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream elfutils package and not the elfutils package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An attempted excessive memory allocation was discovered in the function read_long_names in elf_begin.c in libelf in elfutils 0.174. Remote attackers could leverage this vulnerability to cause a denial-of-service via crafted elf input, which leads to an out-of-memory exception. NOTE: The maintainers believe this is not a real issue, but instead a "warning caused by ASAN because the allocation is big. By setting ASAN_OPTIONS=allocator_may_return_null=1 and running the reproducer, nothing happens."

Remediation

Upgrade Debian:unstable elfutils to version 0.176-1 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

low severity

Out-of-Bounds

  • Vulnerable module: elfutils/libelf1
  • Introduced through: elfutils/libelf1@0.170-0.3
  • Fixed in: 0.175-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › elfutils/libelf1@0.170-0.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream elfutils package and not the elfutils package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An Invalid Memory Address Dereference exists in the function elf_end in libelf in elfutils through v0.174. Although eu-size is intended to support ar files inside ar files, handle_ar in size.c closes the outer ar file before handling all inner entries. The vulnerability allows attackers to cause a denial of service (application crash) with a crafted ELF file.

Remediation

Upgrade Debian:unstable elfutils to version 0.175-1 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-bounds Read

  • Vulnerable module: elfutils/libelf1
  • Introduced through: elfutils/libelf1@0.170-0.3
  • Fixed in: 0.176-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › elfutils/libelf1@0.170-0.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream elfutils package and not the elfutils package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A heap-based buffer over-read was discovered in the function read_srclines in dwarf_getsrclines.c in libdw in elfutils 0.175. A crafted input can cause segmentation faults, leading to denial-of-service, as demonstrated by eu-nm.

Remediation

Upgrade Debian:unstable elfutils to version 0.176-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-Bounds

  • Vulnerable module: jbigkit/libjbig0
  • Introduced through: jbigkit/libjbig0@2.1-3.1+b2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › 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:unstable 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:unstable jbigkit.

References

Out-of-Bounds vulnerability report

low severity

Divide By Zero

  • Vulnerable module: libjpeg-turbo/libjpeg62-turbo
  • Introduced through: libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+b1
  • Fixed in: 1:2.0.5-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+b1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libjpeg-turbo package and not the libjpeg-turbo package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

libjpeg-turbo 1.5.90 is vulnerable to a denial of service vulnerability caused by a divide by zero when processing a crafted BMP image.

Remediation

Upgrade Debian:unstable libjpeg-turbo to version 1:2.0.5-1 or higher.

References

Divide By Zero vulnerability report

low severity

NULL Pointer Dereference

  • Vulnerable module: libjpeg-turbo/libjpeg62-turbo
  • Introduced through: libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+b1
  • Fixed in: 1:2.0.5-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+b1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libjpeg-turbo package and not the libjpeg-turbo package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

libjpeg-turbo 1.5.2 has a NULL Pointer Dereference in jdpostct.c and jquant1.c via a crafted JPEG file.

Remediation

Upgrade Debian:unstable libjpeg-turbo to version 1:2.0.5-1 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

Out-of-bounds Read

  • Vulnerable module: libjpeg-turbo/libjpeg62-turbo
  • Introduced through: libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+b1
  • Fixed in: 1:2.0.5-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libjpeg-turbo/libjpeg62-turbo@1:1.5.2-2+b1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libjpeg-turbo package and not the libjpeg-turbo package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

get_8bit_row in rdbmp.c in libjpeg-turbo through 1.5.90 and MozJPEG through 3.3.1 allows attackers to cause a denial of service (heap-based buffer over-read and application crash) via a crafted 8-bit BMP in which one or more of the color indices is out of range for the number of palette entries.

Remediation

Upgrade Debian:unstable libjpeg-turbo to version 1:2.0.5-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

CVE-2018-14048

  • Vulnerable module: libpng1.6/libpng16-16
  • Introduced through: libpng1.6/libpng16-16@1.6.34-1
  • Fixed in: 1.6.37-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libpng1.6/libpng16-16@1.6.34-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An issue has been found in libpng 1.6.34. It is a SEGV in the function png_free_data in png.c, related to the recommended error handling for png_read_image.

Remediation

Upgrade Debian:unstable libpng1.6 to version 1.6.37-1 or higher.

References

CVE-2018-14048 vulnerability report

low severity

Memory Leak

  • Vulnerable module: libpng1.6/libpng16-16
  • Introduced through: libpng1.6/libpng16-16@1.6.34-1
  • Fixed in: 1.6.39-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libpng1.6/libpng16-16@1.6.34-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

png_create_info_struct in png.c in libpng 1.6.36 has a memory leak, as demonstrated by pngcp. NOTE: a third party has stated "I don't think it is libpng's job to free this buffer.

Remediation

Upgrade Debian:unstable libpng1.6 to version 1.6.39-1 or higher.

References

Memory Leak vulnerability report

low severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.9.10+dfsg-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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:unstable relevant fixed versions and status.

The xz_head function in xzlib.c in libxml2 before 2.9.6 allows remote attackers to cause a denial of service (memory consumption) via a crafted LZMA file, because the decoder functionality does not restrict memory usage to what is required for a legitimate file.

Remediation

Upgrade Debian:unstable libxml2 to version 2.9.10+dfsg-2 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

low severity

Out-of-bounds Read

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.9.10+dfsg-6.2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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:unstable 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:unstable libxml2 to version 2.9.10+dfsg-6.2 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-Bounds

  • Vulnerable module: pango1.0/libpango-1.0-0
  • Introduced through: pango1.0/libpango-1.0-0@1.42.1-1, pango1.0/libpangocairo-1.0-0@1.42.1-1 and others
  • Fixed in: 1.42.4-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › pango1.0/libpango-1.0-0@1.42.1-1
  • Introduced through: openjdk@10-ea-jdk › pango1.0/libpangocairo-1.0-0@1.42.1-1
  • Introduced through: openjdk@10-ea-jdk › pango1.0/libpangoft2-1.0-0@1.42.1-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream pango1.0 package and not the pango1.0 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

libpango in Pango 1.40.8 through 1.42.3, as used in hexchat and other products, allows remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via crafted text with invalid Unicode sequences.

Remediation

Upgrade Debian:unstable pango1.0 to version 1.42.4-1 or higher.

References

Out-of-Bounds vulnerability report

low severity

Divide By Zero

  • Vulnerable module: pixman/libpixman-1-0
  • Introduced through: pixman/libpixman-1-0@0.34.0-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › pixman/libpixman-1-0@0.34.0-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream pixman package and not the pixman package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

stress-test master commit e4c878 was discovered to contain a FPE vulnerability via the component combine_inner at /pixman-combine-float.c.

Remediation

There is no fixed version for Debian:unstable pixman.

References

Divide By Zero vulnerability report

low severity

Double Free

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.4.0-6

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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

Upgrade Debian:unstable tiff to version 4.4.0-6 or higher.

References

Double Free vulnerability report

low severity

Improper Resource Shutdown or Release

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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:unstable tiff.

References

Improper Resource Shutdown or Release vulnerability report

low severity

Incorrect Calculation of Buffer Size

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.4.0-6

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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

Upgrade Debian:unstable tiff to version 4.4.0-6 or higher.

References

Incorrect Calculation of Buffer Size vulnerability report

low severity

Integer Overflow or Wraparound

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.0.10+git190814-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable relevant fixed versions and status.

_TIFFCheckMalloc and _TIFFCheckRealloc in tif_aux.c in LibTIFF through 4.0.10 mishandle Integer Overflow checks because they rely on compiler behavior that is undefined by the applicable C standards. This can, for example, lead to an application crash.

Remediation

Upgrade Debian:unstable tiff to version 4.0.10+git190814-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

low severity

NULL Pointer Dereference

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.0.10-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable relevant fixed versions and status.

An issue was discovered in LibTIFF 4.0.9. There is a NULL pointer dereference in the function LZWDecode in the file tif_lzw.c.

Remediation

Upgrade Debian:unstable tiff to version 4.0.10-1 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

NULL Pointer Dereference

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable relevant fixed versions and status.

ijg-libjpeg before 9d, as used in tiff2pdf (from LibTIFF) and other products, does not check for a NULL pointer at a certain place in jpeg_fdct_16x16 in jfdctint.c.

Remediation

There is no fixed version for Debian:unstable tiff.

References

NULL Pointer Dereference vulnerability report

low severity

Release of Invalid Pointer or Reference

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.4.0-6

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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

Upgrade Debian:unstable tiff to version 4.4.0-6 or higher.

References

Release of Invalid Pointer or Reference vulnerability report

low severity

XML External Entity (XXE) Injection

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.5-3
  • Fixed in: 2.4.1-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › expat/libexpat1@2.2.5-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

expat before version 2.4.0 does not properly handle entities expansion unless an application developer uses the XML_SetEntityDeclHandler function, which allows remote attackers to cause a denial of service (resource consumption), send HTTP requests to intranet servers, or read arbitrary files via a crafted XML document, aka an XML External Entity (XXE) issue. NOTE: it could be argued that because expat already provides the ability to disable external entity expansion, the responsibility for resolving this issue lies with application developers; according to this argument, this entry should be REJECTed, and each affected application would need its own CVE.

Remediation

Upgrade Debian:unstable expat to version 2.4.1-2 or higher.

References

XML External Entity (XXE) Injection vulnerability report

low severity

Access Restriction Bypass

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:7.6p1-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssh/openssh-client@1:7.6p1-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

sshd in OpenSSH 4 on Debian GNU/Linux, and the 20070303 OpenSSH snapshot, allows remote authenticated users to obtain access to arbitrary SELinux roles by appending a :/ (colon slash) sequence, followed by the role name, to the username.

Remediation

There is no fixed version for Debian:unstable openssh.

References

Access Restriction Bypass vulnerability report

low severity

Access Restriction Bypass

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.5-1 and shadow/passwd@1:4.5-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › shadow/login@1:4.5-1
  • Introduced through: openjdk@10-ea-jdk › shadow/passwd@1:4.5-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream shadow package and not the shadow package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

initscripts in rPath Linux 1 sets insecure permissions for the /var/log/btmp file, which allows local users to obtain sensitive information regarding authentication attempts. NOTE: because sshd detects the insecure permissions and does not log certain events, this also prevents sshd from logging failed authentication attempts by remote attackers.

Remediation

There is no fixed version for Debian:unstable shadow.

References

Access Restriction Bypass vulnerability report

low severity

Authentication Bypass

  • Vulnerable module: systemd
  • Introduced through: systemd@238-4, systemd/libnss-systemd@238-4 and others
  • Fixed in: 249.4-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libnss-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libpam-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libsystemd0@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libudev1@238-2
  • Introduced through: openjdk@10-ea-jdk › systemd/systemd-sysv@238-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An exploitable denial-of-service vulnerability exists in Systemd 245. A specially crafted DHCP FORCERENEW packet can cause a server running the DHCP client to be vulnerable to a DHCP ACK spoofing attack. An attacker can forge a pair of FORCERENEW and DCHP ACK packets to reconfigure the server.

Remediation

Upgrade Debian:unstable systemd to version 249.4-2 or higher.

References

Authentication Bypass vulnerability report

low severity

Out-of-bounds Read

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.7.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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

Upgrade Debian:unstable tiff to version 4.7.0-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Race Condition

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.88.1-10

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable 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

Upgrade Debian:unstable curl to version 7.88.1-10 or higher.

References

Race Condition vulnerability report

low severity

Improper Data Handling

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2
  • Fixed in: 2.28-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The pop_fail_stack function in the GNU C Library (aka glibc or libc6) allows context-dependent attackers to cause a denial of service (assertion failure and application crash) via vectors related to extended regular expression processing.

Remediation

Upgrade Debian:unstable glibc to version 2.28-1 or higher.

References

Improper Data Handling vulnerability report

low severity

Improper Input Validation

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2
  • Fixed in: 2.31-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The iconv program in the GNU C Library (aka glibc or libc6) 2.31 and earlier, when invoked with multiple suffixes in the destination encoding (TRANSLATE or IGNORE) along with the -c option, enters an infinite loop when processing invalid multi-byte input sequences, leading to a denial of service.

Remediation

Upgrade Debian:unstable glibc to version 2.31-3 or higher.

References

Improper Input Validation vulnerability report

low severity

PRNG Seed Error

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.36.1-1
  • Fixed in: 2:3.39-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nss/libnss3@2:3.36.1-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nss package and not the nss package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

When handling a SSLv2-compatible ClientHello request, the server doesn't generate a new random value but sends an all-zero value instead. This results in full malleability of the ClientHello for SSLv2 used for TLS 1.2 in all versions prior to NSS 3.39. This does not impact TLS 1.3.

Remediation

Upgrade Debian:unstable nss to version 2:3.39-1 or higher.

References

PRNG Seed Error vulnerability report

low severity

Information Exposure

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:7.6p1-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssh/openssh-client@1:7.6p1-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The client side in OpenSSH 5.7 through 8.4 has an Observable Discrepancy leading to an information leak in the algorithm negotiation. This allows man-in-the-middle attackers to target initial connection attempts (where no host key for the server has been cached by the client). NOTE: some reports state that 8.5 and 8.6 are also affected.

Remediation

There is no fixed version for Debian:unstable openssh.

References

Information Exposure vulnerability report

low severity

CVE-2018-0733

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 1.1.0h-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Because of an implementation bug the PA-RISC CRYPTO_memcmp function is effectively reduced to only comparing the least significant bit of each byte. This allows an attacker to forge messages that would be considered as authenticated in an amount of tries lower than that guaranteed by the security claims of the scheme. The module can only be compiled by the HP-UX assembler, so that only HP-UX PA-RISC targets are affected. Fixed in OpenSSL 1.1.0h (Affected 1.1.0-1.1.0g).

Remediation

Upgrade Debian:unstable openssl to version 1.1.0h-1 or higher.

References

CVE-2018-0733 vulnerability report

low severity

Information Exposure

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 1.1.0h-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

There is an overflow bug in the AVX2 Montgomery multiplication procedure used in exponentiation with 1024-bit moduli. No EC algorithms are affected. 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 DH1024 are considered just feasible, 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 DH1024 private key among multiple clients, which is no longer an option since CVE-2016-0701. This only affects processors that support the AVX2 but not ADX extensions like Intel Haswell (4th generation). Note: The impact from this issue is similar to CVE-2017-3736, CVE-2017-3732 and CVE-2015-3193. OpenSSL version 1.0.2-1.0.2m and 1.1.0-1.1.0g are affected. Fixed in OpenSSL 1.0.2n. Due to the low severity of this issue we are not issuing a new release of OpenSSL 1.1.0 at this time. The fix will be included in OpenSSL 1.1.0h when it becomes available. The fix is also available in commit e502cc86d in the OpenSSL git repository.

Remediation

Upgrade Debian:unstable openssl to version 1.1.0h-1 or higher.

References

Information Exposure vulnerability report

low severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 1.1.0h-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The OpenSSL RSA Key generation algorithm has been shown to be vulnerable to a cache timing side channel attack. An attacker with sufficient access to mount cache timing attacks during the RSA key generation process could recover the private key. Fixed in OpenSSL 1.1.0i-dev (Affected 1.1.0-1.1.0h). Fixed in OpenSSL 1.0.2p-dev (Affected 1.0.2b-1.0.2o).

Remediation

Upgrade Debian:unstable openssl to version 1.1.0h-3 or higher.

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

low severity

NULL Pointer Dereference

  • Vulnerable module: cairo/libcairo-gobject2
  • Introduced through: cairo/libcairo-gobject2@1.15.10-3 and cairo/libcairo2@1.15.10-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › cairo/libcairo-gobject2@1.15.10-3
  • Introduced through: openjdk@10-ea-jdk › cairo/libcairo2@1.15.10-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream cairo package and not the cairo package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Cairo version 1.15.4 is vulnerable to a NULL pointer dereference related to the FT_Load_Glyph and FT_Render_Glyph resulting in an application crash.

Remediation

There is no fixed version for Debian:unstable cairo.

References

NULL Pointer Dereference vulnerability report

low severity

Divide By Zero

  • Vulnerable module: elfutils/libelf1
  • Introduced through: elfutils/libelf1@0.170-0.3
  • Fixed in: 0.175-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › elfutils/libelf1@0.170-0.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream elfutils package and not the elfutils package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Divide-by-zero vulnerabilities in the function arlib_add_symbols() in arlib.c in elfutils 0.174 allow remote attackers to cause a denial of service (application crash) with a crafted ELF file, as demonstrated by eu-ranlib, because a zero sh_entsize is mishandled.

Remediation

Upgrade Debian:unstable elfutils to version 0.175-1 or higher.

References

Divide By Zero vulnerability report

low severity

Improper Resource Shutdown or Release

  • Vulnerable module: elfutils/libelf1
  • Introduced through: elfutils/libelf1@0.170-0.3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › elfutils/libelf1@0.170-0.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream elfutils package and not the elfutils package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A vulnerability, which was classified as problematic, has been found in GNU elfutils 0.192. This issue affects the function gelf_getsymshndx of the file strip.c of the component eu-strip. The manipulation leads to denial of service. The attack needs to be approached locally. The exploit has been disclosed to the public and may be used. The identifier of the patch is fbf1df9ca286de3323ae541973b08449f8d03aba. It is recommended to apply a patch to fix this issue.

Remediation

There is no fixed version for Debian:unstable elfutils.

References

Improper Resource Shutdown or Release vulnerability report

low severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: elfutils/libelf1
  • Introduced through: elfutils/libelf1@0.170-0.3
  • Fixed in: 0.185-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › elfutils/libelf1@0.170-0.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream elfutils package and not the elfutils package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In elfutils 0.183, an infinite loop was found in the function handle_symtab in readelf.c .Which allows attackers to cause a denial of service (infinite loop) via crafted file.

Remediation

Upgrade Debian:unstable elfutils to version 0.185-2 or higher.

References

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability report

low severity

NULL Pointer Dereference

  • Vulnerable module: elfutils/libelf1
  • Introduced through: elfutils/libelf1@0.170-0.3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › elfutils/libelf1@0.170-0.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream elfutils package and not the elfutils package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A vulnerability has been found in GNU elfutils 0.192 and classified as problematic. This vulnerability affects the function handle_dynamic_symtab of the file readelf.c of the component eu-read. The manipulation leads to null pointer dereference. Attacking locally is a requirement. The exploit has been disclosed to the public and may be used. The patch is identified as b38e562a4c907e08171c76b8b2def8464d5a104a. It is recommended to apply a patch to fix this issue.

Remediation

There is no fixed version for Debian:unstable elfutils.

References

NULL Pointer Dereference vulnerability report

low severity

Out-of-bounds Read

  • Vulnerable module: elfutils/libelf1
  • Introduced through: elfutils/libelf1@0.170-0.3
  • Fixed in: 0.176-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › elfutils/libelf1@0.170-0.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream elfutils package and not the elfutils package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An issue was discovered in elfutils 0.175. A segmentation fault can occur in the function elf64_xlatetom in libelf/elf32_xlatetom.c, due to dwfl_segment_report_module not checking whether the dyn data read from a core file is truncated. A crafted input can cause a program crash, leading to denial-of-service, as demonstrated by eu-stack.

Remediation

Upgrade Debian:unstable elfutils to version 0.176-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-bounds Read

  • Vulnerable module: elfutils/libelf1
  • Introduced through: elfutils/libelf1@0.170-0.3
  • Fixed in: 0.175-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › elfutils/libelf1@0.170-0.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream elfutils package and not the elfutils package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

libdw in elfutils 0.173 checks the end of the attributes list incorrectly in dwarf_getabbrev in dwarf_getabbrev.c and dwarf_hasattr in dwarf_hasattr.c, leading to a heap-based buffer over-read and an application crash.

Remediation

Upgrade Debian:unstable elfutils to version 0.175-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-bounds Read

  • Vulnerable module: elfutils/libelf1
  • Introduced through: elfutils/libelf1@0.170-0.3
  • Fixed in: 0.176-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › elfutils/libelf1@0.170-0.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream elfutils package and not the elfutils package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In elfutils 0.175, a heap-based buffer over-read was discovered in the function elf32_xlatetom in elf32_xlatetom.c in libelf. A crafted ELF input can cause a segmentation fault leading to denial of service (program crash) because ebl_core_note does not reject malformed core file notes.

Remediation

Upgrade Debian:unstable elfutils to version 0.176-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-bounds Write

  • Vulnerable module: elfutils/libelf1
  • Introduced through: elfutils/libelf1@0.170-0.3
  • Fixed in: 0.176-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › elfutils/libelf1@0.170-0.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream elfutils package and not the elfutils package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In elfutils 0.175, a negative-sized memcpy is attempted in elf_cvt_note in libelf/note_xlate.h because of an incorrect overflow check. Crafted elf input causes a segmentation fault, leading to denial of service (program crash).

Remediation

Upgrade Debian:unstable elfutils to version 0.176-1 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion')

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.5-3
  • Fixed in: 2.6.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › expat/libexpat1@2.2.5-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

libexpat through 2.5.0 allows recursive XML Entity Expansion if XML_DTD is undefined at compile time.

Remediation

Upgrade Debian:unstable expat to version 2.6.0-1 or higher.

References

Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion') vulnerability report

low severity

Buffer Overflow

  • Vulnerable module: giflib/libgif7
  • Introduced through: giflib/libgif7@5.1.4-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › giflib/libgif7@5.1.4-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream giflib package and not the giflib package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

giflib v5.2.1 was discovered to contain a segmentation fault via the component getarg.c.

Remediation

There is no fixed version for Debian:unstable giflib.

References

Buffer Overflow vulnerability report

low severity

Out-of-bounds Write

  • Vulnerable module: giflib/libgif7
  • Introduced through: giflib/libgif7@5.1.4-2
  • Fixed in: 5.2.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › giflib/libgif7@5.1.4-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream giflib package and not the giflib package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

There is a heap-buffer-overflow in GIFLIB 5.2.1 function DumpScreen2RGB() in gif2rgb.c:298:45.

Remediation

Upgrade Debian:unstable giflib to version 5.2.2-1 or higher.

References

Out-of-bounds Write vulnerability report

low severity

CVE-2019-7309

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2
  • Fixed in: 2.28-6

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In the GNU C Library (aka glibc or libc6) through 2.29, the memcmp function for the x32 architecture can incorrectly return zero (indicating that the inputs are equal) because the RDX most significant bit is mishandled.

Remediation

Upgrade Debian:unstable glibc to version 2.28-6 or higher.

References

CVE-2019-7309 vulnerability report

low severity

Buffer Overflow

  • Vulnerable module: libpng1.6/libpng16-16
  • Introduced through: libpng1.6/libpng16-16@1.6.34-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libpng1.6/libpng16-16@1.6.34-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A heap overflow flaw was found in libpngs' pngimage.c program. This flaw allows an attacker with local network access to pass a specially crafted PNG file to the pngimage utility, causing an application to crash, leading to a denial of service.

Remediation

There is no fixed version for Debian:unstable libpng1.6.

References

Buffer Overflow vulnerability report

low severity

CVE-2018-1000654

  • Vulnerable module: libtasn1-6
  • Introduced through: libtasn1-6@4.13-2
  • Fixed in: 4.14-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libtasn1-6@4.13-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream libtasn1-6 package and not the libtasn1-6 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

GNU Libtasn1-4.13 libtasn1-4.13 version libtasn1-4.13, libtasn1-4.12 contains a DoS, specifically CPU usage will reach 100% when running asn1Paser against the POC due to an issue in _asn1_expand_object_id(p_tree), after a long time, the program will be killed. This attack appears to be exploitable via parsing a crafted file.

Remediation

Upgrade Debian:unstable libtasn1-6 to version 4.14-2 or higher.

References

CVE-2018-1000654 vulnerability report

low severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: libxkbcommon/libxkbcommon0
  • Introduced through: libxkbcommon/libxkbcommon0@0.8.0-1
  • Fixed in: 0.8.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxkbcommon/libxkbcommon0@0.8.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxkbcommon package and not the libxkbcommon package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An infinite loop when reaching EOL unexpectedly in compose/parser.c (aka the keymap parser) in xkbcommon before 0.8.1 could be used by local attackers to cause a denial of service during parsing of crafted keymap files.

Remediation

Upgrade Debian:unstable libxkbcommon to version 0.8.2-1 or higher.

References

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability report

low severity

NULL Pointer Dereference

  • Vulnerable module: libxkbcommon/libxkbcommon0
  • Introduced through: libxkbcommon/libxkbcommon0@0.8.0-1
  • Fixed in: 0.8.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxkbcommon/libxkbcommon0@0.8.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxkbcommon package and not the libxkbcommon package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Unchecked NULL pointer usage in ExprResolveLhs in xkbcomp/expr.c in xkbcommon before 0.8.2 could be used by local attackers to crash (NULL pointer dereference) the xkbcommon parser by supplying a crafted keymap file that triggers an xkb_intern_atom failure.

Remediation

Upgrade Debian:unstable libxkbcommon to version 0.8.2-1 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

NULL Pointer Dereference

  • Vulnerable module: libxkbcommon/libxkbcommon0
  • Introduced through: libxkbcommon/libxkbcommon0@0.8.0-1
  • Fixed in: 0.8.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxkbcommon/libxkbcommon0@0.8.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxkbcommon package and not the libxkbcommon package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Unchecked NULL pointer usage in resolve_keysym in xkbcomp/parser.y in xkbcommon before 0.8.2 could be used by local attackers to crash (NULL pointer dereference) the xkbcommon parser by supplying a crafted keymap file, because a map access attempt can occur for a map that was never created.

Remediation

Upgrade Debian:unstable libxkbcommon to version 0.8.2-1 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

NULL Pointer Dereference

  • Vulnerable module: libxkbcommon/libxkbcommon0
  • Introduced through: libxkbcommon/libxkbcommon0@0.8.0-1
  • Fixed in: 0.8.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxkbcommon/libxkbcommon0@0.8.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxkbcommon package and not the libxkbcommon package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Unchecked NULL pointer usage when parsing invalid atoms in ExprResolveLhs in xkbcomp/expr.c in xkbcommon before 0.8.2 could be used by local attackers to crash (NULL pointer dereference) the xkbcommon parser by supplying a crafted keymap file, because lookup failures are mishandled.

Remediation

Upgrade Debian:unstable libxkbcommon to version 0.8.2-1 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

NULL Pointer Dereference

  • Vulnerable module: libxkbcommon/libxkbcommon0
  • Introduced through: libxkbcommon/libxkbcommon0@0.8.0-1
  • Fixed in: 0.8.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxkbcommon/libxkbcommon0@0.8.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxkbcommon package and not the libxkbcommon package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Unchecked NULL pointer usage in xkbcommon before 0.8.1 could be used by local attackers to crash (NULL pointer dereference) the xkbcommon parser by supplying a crafted keymap file, because the XkbFile for an xkb_geometry section was mishandled.

Remediation

Upgrade Debian:unstable libxkbcommon to version 0.8.2-1 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

NULL Pointer Dereference

  • Vulnerable module: libxkbcommon/libxkbcommon0
  • Introduced through: libxkbcommon/libxkbcommon0@0.8.0-1
  • Fixed in: 0.8.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxkbcommon/libxkbcommon0@0.8.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxkbcommon package and not the libxkbcommon package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Unchecked NULL pointer usage in xkbcommon before 0.8.1 could be used by local attackers to crash (NULL pointer dereference) the xkbcommon parser by supplying a crafted keymap file, because geometry tokens were desupported incorrectly.

Remediation

Upgrade Debian:unstable libxkbcommon to version 0.8.2-1 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

NULL Pointer Dereference

  • Vulnerable module: libxkbcommon/libxkbcommon0
  • Introduced through: libxkbcommon/libxkbcommon0@0.8.0-1
  • Fixed in: 0.8.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxkbcommon/libxkbcommon0@0.8.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxkbcommon package and not the libxkbcommon package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Unchecked NULL pointer usage when handling invalid aliases in CopyKeyAliasesToKeymap in xkbcomp/keycodes.c in xkbcommon before 0.8.1 could be used by local attackers to crash (NULL pointer dereference) the xkbcommon parser by supplying a crafted keymap file.

Remediation

Upgrade Debian:unstable libxkbcommon to version 0.8.2-1 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

NULL Pointer Dereference

  • Vulnerable module: libxkbcommon/libxkbcommon0
  • Introduced through: libxkbcommon/libxkbcommon0@0.8.0-1
  • Fixed in: 0.8.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxkbcommon/libxkbcommon0@0.8.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxkbcommon package and not the libxkbcommon package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Unchecked NULL pointer usage in LookupModMask in xkbcomp/expr.c in xkbcommon before 0.8.2 could be used by local attackers to crash (NULL pointer dereference) the xkbcommon parser by supplying a crafted keymap file with invalid virtual modifiers.

Remediation

Upgrade Debian:unstable libxkbcommon to version 0.8.2-1 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

NULL Pointer Dereference

  • Vulnerable module: libxkbcommon/libxkbcommon0
  • Introduced through: libxkbcommon/libxkbcommon0@0.8.0-1
  • Fixed in: 0.8.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxkbcommon/libxkbcommon0@0.8.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxkbcommon package and not the libxkbcommon package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Unchecked NULL pointer usage in ResolveStateAndPredicate in xkbcomp/compat.c in xkbcommon before 0.8.2 could be used by local attackers to crash (NULL pointer dereference) the xkbcommon parser by supplying a crafted keymap file with a no-op modmask expression.

Remediation

Upgrade Debian:unstable libxkbcommon to version 0.8.2-1 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

Resource Exhaustion

  • Vulnerable module: libxkbcommon/libxkbcommon0
  • Introduced through: libxkbcommon/libxkbcommon0@0.8.0-1
  • Fixed in: 0.8.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxkbcommon/libxkbcommon0@0.8.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxkbcommon package and not the libxkbcommon package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Endless recursion exists in xkbcomp/expr.c in xkbcommon and libxkbcommon before 0.8.1, which could be used by local attackers to crash xkbcommon users by supplying a crafted keymap file that triggers boolean negation.

Remediation

Upgrade Debian:unstable libxkbcommon to version 0.8.2-1 or higher.

References

Resource Exhaustion vulnerability report

low severity

NULL Pointer Dereference

  • Vulnerable module: ncurses/libncurses5
  • Introduced through: ncurses/libncurses5@6.1-1, ncurses/libncursesw5@6.1-1 and others
  • Fixed in: 6.1+20180210-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › ncurses/libncurses5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/libncursesw5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/libtinfo5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/ncurses-base@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/ncurses-bin@6.1-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In ncurses 6.1, there is a NULL pointer dereference at function _nc_parse_entry in parse_entry.c that will lead to a denial of service attack. The product proceeds to the dereference code path even after a "dubious character `*' in name or alias field" detection.

Remediation

Upgrade Debian:unstable ncurses to version 6.1+20180210-3 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

Integer Overflow or Wraparound

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1
  • Fixed in: 3.46.1-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In SQLite 3.49.0 before 3.49.1, certain argument values to sqlite3_db_config (in the C-language API) can cause a denial of service (application crash). An sz*nBig multiplication is not cast to a 64-bit integer, and consequently some memory allocations may be incorrect.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.46.1-4 or higher.

References

Integer Overflow or Wraparound vulnerability report

low severity

Out-of-bounds Read

  • Vulnerable module: tar
  • Introduced through: tar@1.29b-2
  • Fixed in: 1.34+dfsg-1.4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tar@1.29b-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream tar package and not the tar package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

GNU Tar through 1.34 has a one-byte out-of-bounds read that results in use of uninitialized memory for a conditional jump. Exploitation to change the flow of control has not been demonstrated. The issue occurs in from_header in list.c via a V7 archive in which mtime has approximately 11 whitespace characters.

Remediation

Upgrade Debian:unstable tar to version 1.34+dfsg-1.4 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-Bounds

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.1.0+git201212-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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

Upgrade Debian:unstable tiff to version 4.1.0+git201212-1 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.1.0+git201212-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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

Upgrade Debian:unstable tiff to version 4.1.0+git201212-1 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.5.0-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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

Upgrade Debian:unstable tiff to version 4.5.0-2 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-bounds Read

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.4.0~rc1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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

Upgrade Debian:unstable tiff to version 4.4.0~rc1-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-bounds Read

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.4.0-6

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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

Upgrade Debian:unstable tiff to version 4.4.0-6 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.7.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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

Upgrade Debian:unstable tiff to version 4.7.0-1 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Information Exposure

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.31.1-0.5, util-linux/fdisk@2.31.1-0.5 and others

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › util-linux@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/fdisk@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/libblkid1@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/libfdisk1@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/libmount1@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/libsmartcols1@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/libuuid1@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/mount@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/bsdutils@1:2.31.1-0.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream util-linux package and not the util-linux package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw was found in the util-linux chfn and chsh utilities when compiled with Readline support. The Readline library uses an "INPUTRC" environment variable to get a path to the library config file. When the library cannot parse the specified file, it prints an error message containing data from the file. This flaw allows an unprivileged user to read root-owned files, potentially leading to privilege escalation. This flaw affects util-linux versions prior to 2.37.4.

Remediation

There is no fixed version for Debian:unstable util-linux.

References

Information Exposure vulnerability report

low severity

Integer Overflow or Wraparound

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.31.1-0.5, util-linux/fdisk@2.31.1-0.5 and others
  • Fixed in: 2.36.1-8

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › util-linux@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/fdisk@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/libblkid1@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/libfdisk1@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/libmount1@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/libsmartcols1@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/libuuid1@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/mount@2.31.1-0.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream util-linux package and not the util-linux package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An integer overflow in util-linux through 2.37.1 can potentially cause a buffer overflow if an attacker were able to use system resources in a way that leads to a large number in the /proc/sysvipc/sem file. NOTE: this is unexploitable in GNU C Library environments, and possibly in all realistic environments.

Remediation

Upgrade Debian:unstable util-linux to version 2.36.1-8 or higher.

References

Integer Overflow or Wraparound vulnerability report

low severity

Out-of-bounds Read

  • Vulnerable module: ncurses/libncurses5
  • Introduced through: ncurses/libncurses5@6.1-1, ncurses/libncursesw5@6.1-1 and others
  • Fixed in: 6.1+20191019-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › ncurses/libncurses5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/libncursesw5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/libtinfo5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/ncurses-base@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/ncurses-bin@6.1-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

There is a heap-based buffer over-read in the fmt_entry function in tinfo/comp_hash.c in the terminfo library in ncurses before 6.1-20191012.

Remediation

Upgrade Debian:unstable ncurses to version 6.1+20191019-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Insufficiently Protected Credentials

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.79.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable 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

Upgrade Debian:unstable curl to version 7.79.1-1 or higher.

References

Insufficiently Protected Credentials vulnerability report

low severity

Cryptographic Issues

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.56.1-2 and glib2.0/libglib2.0-data@2.56.1-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-0@2.56.1-2
  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-data@2.56.1-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

GLib 2.31.8 and earlier, when the g_str_hash function is used, computes hash values without restricting the ability to trigger hash collisions predictably, which allows context-dependent attackers to cause a denial of service (CPU consumption) via crafted input to an application that maintains a hash table. NOTE: this issue may be disputed by the vendor; the existence of the g_str_hash function is not a vulnerability in the library, because callers of g_hash_table_new and g_hash_table_new_full can specify an arbitrary hash function that is appropriate for the application.

Remediation

There is no fixed version for Debian:unstable glib2.0.

References

Cryptographic Issues vulnerability report

low severity

Information Exposure

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may bypass ASLR using cache of thread stack and heap. The component is: glibc. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat.

Remediation

There is no fixed version for Debian:unstable glibc.

References

Information Exposure vulnerability report

low severity

Use of Insufficiently Random Values

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may guess the heap addresses of pthread_created thread. The component is: glibc. NOTE: the vendor's position is "ASLR bypass itself is not a vulnerability.

Remediation

There is no fixed version for Debian:unstable glibc.

References

Use of Insufficiently Random Values vulnerability report

low severity

Reachable Assertion

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.16-2, krb5/libk5crypto3@1.16-2 and others
  • Fixed in: 1.16.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › krb5/libgssapi-krb5-2@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libk5crypto3@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libkrb5-3@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libkrb5support0@1.16-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A Reachable Assertion issue was discovered in the KDC in MIT Kerberos 5 (aka krb5) before 1.17. If an attacker can obtain a krbtgt ticket using an older encryption type (single-DES, triple-DES, or RC4), the attacker can crash the KDC by making an S4U2Self request.

Remediation

Upgrade Debian:unstable krb5 to version 1.16.2-1 or higher.

References

Reachable Assertion vulnerability report

low severity

Out-of-bounds Read

  • Vulnerable module: ncurses/libncurses5
  • Introduced through: ncurses/libncurses5@6.1-1, ncurses/libncursesw5@6.1-1 and others
  • Fixed in: 6.1+20191019-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › ncurses/libncurses5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/libncursesw5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/libtinfo5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/ncurses-base@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/ncurses-bin@6.1-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

There is a heap-based buffer over-read in the _nc_find_entry function in tinfo/comp_hash.c in the terminfo library in ncurses before 6.1-20191012.

Remediation

Upgrade Debian:unstable ncurses to version 6.1+20191019-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

CVE-2016-20012

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:7.6p1-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssh/openssh-client@1:7.6p1-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

OpenSSH through 8.7 allows remote attackers, who have a suspicion that a certain combination of username and public key is known to an SSH server, to test whether this suspicion is correct. This occurs because a challenge is sent only when that combination could be valid for a login session. NOTE: the vendor does not recognize user enumeration as a vulnerability for this product

Remediation

There is no fixed version for Debian:unstable openssh.

References

CVE-2016-20012 vulnerability report

low severity

Improper Authentication

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:7.6p1-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssh/openssh-client@1:7.6p1-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

OpenSSH 4.6 and earlier, when ChallengeResponseAuthentication is enabled, allows remote attackers to determine the existence of user accounts by attempting to authenticate via S/KEY, which displays a different response if the user account exists, a similar issue to CVE-2001-1483.

Remediation

There is no fixed version for Debian:unstable openssh.

References

Improper Authentication vulnerability report

low severity

Information Exposure

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:7.6p1-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssh/openssh-client@1:7.6p1-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Remotely observable behaviour in auth-gss2.c in OpenSSH through 7.8 could be used by remote attackers to detect existence of users on a target system when GSS2 is in use. NOTE: the discoverer states 'We understand that the OpenSSH developers do not want to treat such a username enumeration (or "oracle") as a vulnerability.'

Remediation

There is no fixed version for Debian:unstable openssh.

References

Information Exposure vulnerability report

low severity

Information Exposure

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 1.1.1e-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

There is an overflow bug in the x64_64 Montgomery squaring procedure used in exponentiation with 512-bit moduli. No EC algorithms are affected. Analysis suggests that attacks against 2-prime RSA1024, 3-prime RSA1536, and DSA1024 as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH512 are considered just feasible. However, for an attack the target would have to re-use the DH512 private key, which is not recommended anyway. Also applications directly using the low level API BN_mod_exp may be affected if they use BN_FLG_CONSTTIME. Fixed in OpenSSL 1.1.1e (Affected 1.1.1-1.1.1d). Fixed in OpenSSL 1.0.2u (Affected 1.0.2-1.0.2t).

Remediation

Upgrade Debian:unstable openssl to version 1.1.1e-1 or higher.

References

Information Exposure vulnerability report

low severity

Incorrect Permission Assignment for Critical Resource

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.5-1 and shadow/passwd@1:4.5-1
  • Fixed in: 1:4.7-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › shadow/login@1:4.5-1
  • Introduced through: openjdk@10-ea-jdk › shadow/passwd@1:4.5-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream shadow package and not the shadow package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An issue was discovered in shadow 4.5. newgidmap (in shadow-utils) is setuid and allows an unprivileged user to be placed in a user namespace where setgroups(2) is permitted. This allows an attacker to remove themselves from a supplementary group, which may allow access to certain filesystem paths if the administrator has used "group blacklisting" (e.g., chmod g-rwx) to restrict access to paths. This flaw effectively reverts a security feature in the kernel (in particular, the /proc/self/setgroups knob) to prevent this sort of privilege escalation.

Remediation

Upgrade Debian:unstable shadow to version 1:4.7-1 or higher.

References

Incorrect Permission Assignment for Critical Resource vulnerability report

low severity

Improper Validation of Integrity Check Value

  • Vulnerable module: systemd
  • Introduced through: systemd@238-4, systemd/libnss-systemd@238-4 and others

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libnss-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libpam-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libsystemd0@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libudev1@238-2
  • Introduced through: openjdk@10-ea-jdk › systemd/systemd-sysv@238-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An issue was discovered in systemd 253. An attacker can modify the contents of past events in a sealed log file and then adjust the file such that checking the integrity shows no error, despite modifications. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability."

Remediation

There is no fixed version for Debian:unstable systemd.

References

Improper Validation of Integrity Check Value vulnerability report

low severity

Improper Validation of Integrity Check Value

  • Vulnerable module: systemd
  • Introduced through: systemd@238-4, systemd/libnss-systemd@238-4 and others

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libnss-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libpam-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libsystemd0@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libudev1@238-2
  • Introduced through: openjdk@10-ea-jdk › systemd/systemd-sysv@238-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An issue was discovered in systemd 253. An attacker can truncate a sealed log file and then resume log sealing such that checking the integrity shows no error, despite modifications. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability."

Remediation

There is no fixed version for Debian:unstable systemd.

References

Improper Validation of Integrity Check Value vulnerability report

low severity

Improper Validation of Integrity Check Value

  • Vulnerable module: systemd
  • Introduced through: systemd@238-4, systemd/libnss-systemd@238-4 and others

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libnss-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libpam-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libsystemd0@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libudev1@238-2
  • Introduced through: openjdk@10-ea-jdk › systemd/systemd-sysv@238-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An issue was discovered in systemd 253. An attacker can modify a sealed log file such that, in some views, not all existing and sealed log messages are displayed. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability."

Remediation

There is no fixed version for Debian:unstable systemd.

References

Improper Validation of Integrity Check Value vulnerability report

low severity

Out-of-Bounds

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.7.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable relevant fixed versions and status.

A vulnerability was determined in LibTIFF up to 4.5.1. Affected by this issue is the function readSeparateStripsetoBuffer of the file tools/tiffcrop.c of the component tiffcrop. The manipulation leads to stack-based buffer overflow. Local access is required to approach this attack. The patch is identified as 8a7a48d7a645992ca83062b3a1873c951661e2b3. It is recommended to apply a patch to fix this issue.

Remediation

Upgrade Debian:unstable tiff to version 4.7.0-1 or higher.

References

Out-of-Bounds vulnerability report

low severity

Improper Input Validation

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

GIT version 2.15.1 and earlier contains a Input Validation Error vulnerability in Client that can result in problems including messing up terminal configuration to RCE. This attack appear to be exploitable via The user must interact with a malicious git server, (or have their traffic modified in a MITM attack).

Remediation

There is no fixed version for Debian:unstable git.

References

Improper Input Validation vulnerability report

low severity

CVE-2019-13057

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1 and openldap/libldap-common@2.4.45+dfsg-1
  • Fixed in: 2.4.48+dfsg-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-2.4-2@2.4.45+dfsg-1
  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-common@2.4.45+dfsg-1

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:unstable relevant fixed versions and status.

An issue was discovered in the server in OpenLDAP before 2.4.48. When the server administrator delegates rootDN (database admin) privileges for certain databases but wants to maintain isolation (e.g., for multi-tenant deployments), slapd does not properly stop a rootDN from requesting authorization as an identity from another database during a SASL bind or with a proxyAuthz (RFC 4370) control. (It is not a common configuration to deploy a system where the server administrator and a DB administrator enjoy different levels of trust.)

Remediation

Upgrade Debian:unstable openldap to version 2.4.48+dfsg-1 or higher.

References

CVE-2019-13057 vulnerability report

low severity

Out-of-bounds Read

  • Vulnerable module: glib-networking
  • Introduced through: glib-networking@2.56.0-1, glib-networking/glib-networking-common@2.56.0-1 and others

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glib-networking@2.56.0-1
  • Introduced through: openjdk@10-ea-jdk › glib-networking/glib-networking-common@2.56.0-1
  • Introduced through: openjdk@10-ea-jdk › glib-networking/glib-networking-services@2.56.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib-networking package and not the glib-networking package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

glib-networking's OpenSSL backend fails to properly check the return value of a call to BIO_write(), resulting in an out of bounds read.

Remediation

There is no fixed version for Debian:unstable glib-networking.

References

Out-of-bounds Read vulnerability report

low severity

Race Condition

  • Vulnerable module: coreutils
  • Introduced through: coreutils@8.28-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › coreutils@8.28-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream coreutils package and not the coreutils package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In GNU Coreutils through 8.29, chown-core.c in chown and chgrp does not prevent replacement of a plain file with a symlink during use of the POSIX "-R -L" options, which allows local users to modify the ownership of arbitrary files by leveraging a race condition.

Remediation

There is no fixed version for Debian:unstable coreutils.

References

Race Condition vulnerability report

low severity

Improper Resource Shutdown or Release

  • Vulnerable module: elfutils/libelf1
  • Introduced through: elfutils/libelf1@0.170-0.3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › elfutils/libelf1@0.170-0.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream elfutils package and not the elfutils package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A vulnerability classified as problematic was found in GNU elfutils 0.192. This vulnerability affects the function elf_strptr in the library /libelf/elf_strptr.c of the component eu-strip. The manipulation leads to denial of service. It is possible to launch the attack on the local host. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The name of the patch is b16f441cca0a4841050e3215a9f120a6d8aea918. It is recommended to apply a patch to fix this issue.

Remediation

There is no fixed version for Debian:unstable elfutils.

References

Improper Resource Shutdown or Release vulnerability report

low severity

Improper Initialization

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1 and openldap/libldap-common@2.4.45+dfsg-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-2.4-2@2.4.45+dfsg-1
  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-common@2.4.45+dfsg-1

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:unstable 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:unstable openldap.

References

Improper Initialization vulnerability report

low severity

Time-of-check Time-of-use (TOCTOU)

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.5-1 and shadow/passwd@1:4.5-1
  • Fixed in: 1:4.12.3+dfsg1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › shadow/login@1:4.5-1
  • Introduced through: openjdk@10-ea-jdk › shadow/passwd@1:4.5-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream shadow package and not the shadow package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

shadow: TOCTOU (time-of-check time-of-use) race condition when copying and removing directory trees

Remediation

Upgrade Debian:unstable shadow to version 1:4.12.3+dfsg1-1 or higher.

References

Time-of-check Time-of-use (TOCTOU) vulnerability report

low severity

Stack-based Buffer Overflow

  • Vulnerable module: coreutils
  • Introduced through: coreutils@8.28-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › coreutils@8.28-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream coreutils package and not the coreutils package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw was found in GNU Coreutils. The sort utility's begfield() function is vulnerable to a heap buffer under-read. The program may access memory outside the allocated buffer if a user runs a crafted command using the traditional key format. A malicious input could lead to a crash or leak sensitive data.

Remediation

There is no fixed version for Debian:unstable coreutils.

References

Stack-based Buffer Overflow vulnerability report

low severity

Incorrect Permission Assignment for Critical Resource

  • Vulnerable module: mesa/libegl-mesa0
  • Introduced through: mesa/libegl-mesa0@17.3.9-1, mesa/libgbm1@17.3.9-1 and others
  • Fixed in: 19.2.6-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › mesa/libegl-mesa0@17.3.9-1
  • Introduced through: openjdk@10-ea-jdk › mesa/libgbm1@17.3.9-1
  • Introduced through: openjdk@10-ea-jdk › mesa/libgl1-mesa-dri@17.3.9-1
  • Introduced through: openjdk@10-ea-jdk › mesa/libgl1-mesa-glx@17.3.9-1
  • Introduced through: openjdk@10-ea-jdk › mesa/libglapi-mesa@17.3.9-1
  • Introduced through: openjdk@10-ea-jdk › mesa/libglx-mesa0@17.3.9-1
  • Introduced through: openjdk@10-ea-jdk › mesa/libwayland-egl1-mesa@17.3.9-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream mesa package and not the mesa package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An exploitable shared memory permissions vulnerability exists in the functionality of X11 Mesa 3D Graphics Library 19.1.2. An attacker can access the shared memory without any specific permissions to trigger this vulnerability.

Remediation

Upgrade Debian:unstable mesa to version 19.2.6-1 or higher.

References

Incorrect Permission Assignment for Critical Resource vulnerability report

low severity

Link Following

  • Vulnerable module: systemd
  • Introduced through: systemd@238-4, systemd/libnss-systemd@238-4 and others

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libnss-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libpam-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libsystemd0@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libudev1@238-2
  • Introduced through: openjdk@10-ea-jdk › systemd/systemd-sysv@238-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

systemd, when updating file permissions, allows local users to change the permissions and SELinux security contexts for arbitrary files via a symlink attack on unspecified files.

Remediation

There is no fixed version for Debian:unstable systemd.

References

Link Following vulnerability report

low severity

Resource Management Errors

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The glob implementation in the GNU C Library (aka glibc or libc6) allows remote authenticated users to cause a denial of service (CPU and memory consumption) via crafted glob expressions that do not match any pathnames, as demonstrated by glob expressions in STAT commands to an FTP daemon, a different vulnerability than CVE-2010-2632.

Remediation

There is no fixed version for Debian:unstable glibc.

References

Resource Management Errors vulnerability report

low severity

Improper Input Validation

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.18-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gnutls28/libgnutls30@3.5.18-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The SSL protocol, as used in certain configurations in Microsoft Windows and Microsoft Internet Explorer, Mozilla Firefox, Google Chrome, Opera, and other products, encrypts data by using CBC mode with chained initialization vectors, which allows man-in-the-middle attackers to obtain plaintext HTTP headers via a blockwise chosen-boundary attack (BCBA) on an HTTPS session, in conjunction with JavaScript code that uses (1) the HTML5 WebSocket API, (2) the Java URLConnection API, or (3) the Silverlight WebClient API, aka a "BEAST" attack.

Remediation

There is no fixed version for Debian:unstable gnutls28.

References

Improper Input Validation vulnerability report

low severity

Information Exposure

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:7.6p1-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssh/openssh-client@1:7.6p1-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

OpenSSH, when using OPIE (One-Time Passwords in Everything) for PAM, allows remote attackers to determine the existence of certain user accounts, which displays a different response if the user account exists and is configured to use one-time passwords (OTP), a similar issue to CVE-2007-2243.

Remediation

There is no fixed version for Debian:unstable openssh.

References

Information Exposure vulnerability report

low severity

Memory Leak

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A Memory Leak vulnerability exists in SQLite Project SQLite3 3.35.1 and 3.37.0 via maliciously crafted SQL Queries (made via editing the Database File), it is possible to query a record, and leak subsequent bytes of memory that extend beyond the record, which could let a malicious user obtain sensitive information. NOTE: The developer disputes this as a vulnerability stating that If you give SQLite a corrupted database file and submit a query against the database, it might read parts of the database that you did not intend or expect.

Remediation

There is no fixed version for Debian:unstable sqlite3.

References

Memory Leak vulnerability report

low severity

Out-of-Bounds

  • Vulnerable module: iptables/libip4tc0
  • Introduced through: iptables/libip4tc0@1.6.2-1
  • Fixed in: 1.8.3-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › iptables/libip4tc0@1.6.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream iptables package and not the iptables package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A buffer overflow in iptables-restore in netfilter iptables 1.8.2 allows an attacker to (at least) crash the program or potentially gain code execution via a specially crafted iptables-save file. This is related to add_param_to_argv in xshared.c.

Remediation

Upgrade Debian:unstable iptables to version 1.8.3-2 or higher.

References

Out-of-Bounds vulnerability report

low severity

Improper Certificate Validation

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1 and openldap/libldap-common@2.4.45+dfsg-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-2.4-2@2.4.45+dfsg-1
  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-common@2.4.45+dfsg-1

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:unstable 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:unstable openldap.

References

Improper Certificate Validation vulnerability report

low severity

LDAP Injection

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.16-2, krb5/libk5crypto3@1.16-2 and others
  • Fixed in: 1.16.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › krb5/libgssapi-krb5-2@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libk5crypto3@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libkrb5-3@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libkrb5support0@1.16-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

MIT krb5 1.6 or later allows an authenticated kadmin with permission to add principals to an LDAP Kerberos database to circumvent a DN containership check by supplying both a "linkdn" and "containerdn" database argument, or by supplying a DN string which is a left extension of a container DN string but is not hierarchically within the container DN.

Remediation

Upgrade Debian:unstable krb5 to version 1.16.1-1 or higher.

References

LDAP Injection vulnerability report

low severity

CVE-2025-32728

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:7.6p1-4
  • Fixed in: 1:10.0p1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssh/openssh-client@1:7.6p1-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In sshd in OpenSSH before 10.0, the DisableForwarding directive does not adhere to the documentation stating that it disables X11 and agent forwarding.

Remediation

Upgrade Debian:unstable openssh to version 1:10.0p1-1 or higher.

References

CVE-2025-32728 vulnerability report

low severity

Improper Verification of Cryptographic Signature

  • Vulnerable module: apt
  • Introduced through: apt@1.6~beta1 and apt/libapt-pkg5.0@1.6~beta1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › apt@1.6~beta1
  • Introduced through: openjdk@10-ea-jdk › apt/libapt-pkg5.0@1.6~beta1

NVD Description

Note: Versions mentioned in the description apply only to the upstream apt package and not the apt package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

It was found that apt-key in apt, all versions, do not correctly validate gpg keys with the master keyring, leading to a potential man-in-the-middle attack.

Remediation

There is no fixed version for Debian:unstable apt.

References

Improper Verification of Cryptographic Signature vulnerability report

low severity

Authentication Bypass

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.74.0-1.2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable relevant fixed versions and status.

curl 7.63.0 to and including 7.75.0 includes vulnerability that allows a malicious HTTPS proxy to MITM a connection due to bad handling of TLS 1.3 session tickets. When using a HTTPS proxy and TLS 1.3, libcurl can confuse session tickets arriving from the HTTPS proxy but work as if they arrived from the remote server and then wrongly "short-cut" the host handshake. When confusing the tickets, a HTTPS proxy can trick libcurl to use the wrong session ticket resume for the host and thereby circumvent the server TLS certificate check and make a MITM attack to be possible to perform unnoticed. Note that such a malicious HTTPS proxy needs to provide a certificate that curl will accept for the MITMed server for an attack to work - unless curl has been told to ignore the server certificate check.

Remediation

Upgrade Debian:unstable curl to version 7.74.0-1.2 or higher.

References

Authentication Bypass vulnerability report

low severity

CVE-2020-8284

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.74.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable relevant fixed versions and status.

A malicious server can use the FTP PASV response to trick curl 7.73.0 and earlier into connecting back to a given IP address and port, and this way potentially make curl extract information about services that are otherwise private and not disclosed, for example doing port scanning and service banner extractions.

Remediation

Upgrade Debian:unstable curl to version 7.74.0-1 or higher.

References

CVE-2020-8284 vulnerability report

low severity

CVE-2022-35252

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.85.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable 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:unstable curl to version 7.85.0-1 or higher.

References

CVE-2022-35252 vulnerability report

low severity

CVE-2023-28322

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.88.1-10

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable 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:unstable curl to version 7.88.1-10 or higher.

References

CVE-2023-28322 vulnerability report

low severity

CVE-2023-38546

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 8.3.0-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable 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:unstable curl to version 8.3.0-3 or higher.

References

CVE-2023-38546 vulnerability report

low severity

Integer Overflow or Wraparound

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.64.0-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable relevant fixed versions and status.

An integer overflow in curl's URL API results in a buffer overflow in libcurl 7.62.0 to and including 7.64.1.

Remediation

Upgrade Debian:unstable curl to version 7.64.0-4 or higher.

References

Integer Overflow or Wraparound vulnerability report

low severity

Use of Incorrectly-Resolved Name or Reference

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.79.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable 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:unstable curl to version 7.79.1-1 or higher.

References

Use of Incorrectly-Resolved Name or Reference vulnerability report

low severity

NULL Pointer Dereference

  • Vulnerable module: glib-networking
  • Introduced through: glib-networking@2.56.0-1, glib-networking/glib-networking-common@2.56.0-1 and others

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glib-networking@2.56.0-1
  • Introduced through: openjdk@10-ea-jdk › glib-networking/glib-networking-common@2.56.0-1
  • Introduced through: openjdk@10-ea-jdk › glib-networking/glib-networking-services@2.56.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib-networking package and not the glib-networking package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

glib-networking's OpenSSL backend fails to properly check the return value of memory allocation routines. An out of memory condition could potentially result in writing to an invalid memory location.

Remediation

There is no fixed version for Debian:unstable glib-networking.

References

NULL Pointer Dereference vulnerability report

low severity

Directory Traversal

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.56.1-2 and glib2.0/libglib2.0-data@2.56.1-2
  • Fixed in: 2.84.4-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-0@2.56.1-2
  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-data@2.56.1-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw was found in glib. An integer overflow during temporary file creation leads to an out-of-bounds memory access, allowing an attacker to potentially perform path traversal or access private temporary file content by creating symbolic links. This vulnerability allows a local attacker to manipulate file paths and access unauthorized data. The core issue stems from insufficient validation of file path lengths during temporary file operations.

Remediation

Upgrade Debian:unstable glib2.0 to version 2.84.4-1 or higher.

References

Directory Traversal vulnerability report

low severity

Integer Overflow or Wraparound

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.56.1-2 and glib2.0/libglib2.0-data@2.56.1-2
  • Fixed in: 2.84.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-0@2.56.1-2
  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-data@2.56.1-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw was found in GLib. An integer overflow and buffer under-read occur when parsing a long invalid ISO 8601 timestamp with the g_date_time_new_from_iso8601() function.

Remediation

Upgrade Debian:unstable glib2.0 to version 2.84.1-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

low severity
new

Uncontrolled Recursion

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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:unstable relevant fixed versions and status.

A flaw was identified in the RelaxNG parser of libxml2 related to how external schema inclusions are handled. The parser does not enforce a limit on inclusion depth when resolving nested <include> directives. Specially crafted or overly complex schemas can cause excessive recursion during parsing. This may lead to stack exhaustion and application crashes, creating a denial-of-service risk.

Remediation

There is no fixed version for Debian:unstable libxml2.

References

Uncontrolled Recursion vulnerability report

low severity

Improper Authentication

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:7.6p1-4
  • Fixed in: 1:8.9p1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssh/openssh-client@1:7.6p1-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An issue was discovered in OpenSSH before 8.9. If a client is using public-key authentication with agent forwarding but without -oLogLevel=verbose, and an attacker has silently modified the server to support the None authentication option, then the user cannot determine whether FIDO authentication is going to confirm that the user wishes to connect to that server, or that the user wishes to allow that server to connect to a different server on the user's behalf. NOTE: the vendor's position is "this is not an authentication bypass, since nothing is being bypassed.

Remediation

Upgrade Debian:unstable openssh to version 1:8.9p1-1 or higher.

References

Improper Authentication vulnerability report

low severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 1.1.1d-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In situations where an attacker receives automated notification of the success or failure of a decryption attempt an attacker, after sending a very large number of messages to be decrypted, can recover a CMS/PKCS7 transported encryption key or decrypt any RSA encrypted message that was encrypted with the public RSA key, using a Bleichenbacher padding oracle attack. Applications are not affected if they use a certificate together with the private RSA key to the CMS_decrypt or PKCS7_decrypt functions to select the correct recipient info to decrypt. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s).

Remediation

Upgrade Debian:unstable openssl to version 1.1.1d-1 or higher.

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

low severity

Buffer Overflow

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.7-3
  • Fixed in: 2.3.1-12

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › cups/libcups2@2.2.7-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream cups package and not the cups package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A buffer overflow was addressed with improved bounds checking. This issue is fixed in macOS Catalina 10.15.2, Security Update 2019-002 Mojave, and Security Update 2019-007 High Sierra. In certain configurations, a remote attacker may be able to submit arbitrary print jobs.

Remediation

Upgrade Debian:unstable cups to version 2.3.1-12 or higher.

References

Buffer Overflow vulnerability report

low severity

Integer Overflow or Wraparound

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.66.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable 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

Upgrade Debian:unstable curl to version 7.66.0-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

low severity

CVE-2025-6199

  • Vulnerable module: gdk-pixbuf/libgdk-pixbuf2.0-0
  • Introduced through: gdk-pixbuf/libgdk-pixbuf2.0-0@2.36.11-2, gdk-pixbuf/libgdk-pixbuf2.0-bin@2.36.11-2 and others
  • Fixed in: 2.42.12+dfsg-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gdk-pixbuf/libgdk-pixbuf2.0-0@2.36.11-2
  • Introduced through: openjdk@10-ea-jdk › gdk-pixbuf/libgdk-pixbuf2.0-bin@2.36.11-2
  • Introduced through: openjdk@10-ea-jdk › gdk-pixbuf/libgdk-pixbuf2.0-common@2.36.11-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream gdk-pixbuf package and not the gdk-pixbuf package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw was found in the GIF parser of GdkPixbuf’s LZW decoder. When an invalid symbol is encountered during decompression, the decoder sets the reported output size to the full buffer length rather than the actual number of written bytes. This logic error results in uninitialized sections of the buffer being included in the output, potentially leaking arbitrary memory contents in the processed image.

Remediation

Upgrade Debian:unstable gdk-pixbuf to version 2.42.12+dfsg-3 or higher.

References

CVE-2025-6199 vulnerability report

low severity

CVE-2019-1348

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.24.0-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An issue was found in Git before v2.24.1, v2.23.1, v2.22.2, v2.21.1, v2.20.2, v2.19.3, v2.18.2, v2.17.3, v2.16.6, v2.15.4, and v2.14.6. The --export-marks option of git fast-import is exposed also via the in-stream command feature export-marks=... and it allows overwriting arbitrary paths.

Remediation

Upgrade Debian:unstable git to version 1:2.24.0-2 or higher.

References

CVE-2019-1348 vulnerability report

low severity

CVE-2024-32020

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.45.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, local clones may end up hardlinking files into the target repository's object database when source and target repository reside on the same disk. If the source repository is owned by a different user, then those hardlinked files may be rewritten at any point in time by the untrusted user. Cloning local repositories will cause Git to either copy or hardlink files of the source repository into the target repository. This significantly speeds up such local clones compared to doing a "proper" clone and saves both disk space and compute time. When cloning a repository located on the same disk that is owned by a different user than the current user we also end up creating such hardlinks. These files will continue to be owned and controlled by the potentially-untrusted user and can be rewritten by them at will in the future. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4.

Remediation

Upgrade Debian:unstable git to version 1:2.45.1-1 or higher.

References

CVE-2024-32020 vulnerability report

low severity

Information Exposure

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2
  • Fixed in: 2.29-8

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

On the x86-64 architecture, the GNU C Library (aka glibc) before 2.31 fails to ignore the LD_PREFER_MAP_32BIT_EXEC environment variable during program execution after a security transition, allowing local attackers to restrict the possible mapping addresses for loaded libraries and thus bypass ASLR for a setuid program.

Remediation

Upgrade Debian:unstable glibc to version 2.29-8 or higher.

References

Information Exposure vulnerability report

low severity

Out-of-bounds Write

  • Vulnerable module: gnupg2/dirmngr
  • Introduced through: gnupg2/dirmngr@2.2.5-1, gnupg2/gnupg@2.2.5-1 and others

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gnupg2/dirmngr@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gnupg@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gnupg-l10n@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gnupg-utils@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpg@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpg-agent@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpg-wks-client@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpg-wks-server@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpgconf@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpgsm@2.2.5-1
  • Introduced through: openjdk@10-ea-jdk › gnupg2/gpgv@2.2.5-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream gnupg2 package and not the gnupg2 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB.

Remediation

There is no fixed version for Debian:unstable gnupg2.

References

Out-of-bounds Write vulnerability report

low severity

Memory Leak

  • Vulnerable module: libcap2
  • Introduced through: libcap2@1:2.25-1.2
  • Fixed in: 1:2.66-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libcap2@1:2.25-1.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream libcap2 package and not the libcap2 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A vulnerability was found in the pthread_create() function in libcap. This issue may allow a malicious actor to use cause __real_pthread_create() to return an error, which can exhaust the process memory.

Remediation

Upgrade Debian:unstable libcap2 to version 1:2.66-4 or higher.

References

Memory Leak vulnerability report

low severity

Out-of-bounds Read

  • Vulnerable module: libsepol/libsepol1
  • Introduced through: libsepol/libsepol1@2.7-1
  • Fixed in: 3.3-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libsepol/libsepol1@2.7-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libsepol package and not the libsepol package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The CIL compiler in SELinux 3.2 has a heap-based buffer over-read in ebitmap_match_any (called indirectly from cil_check_neverallow). This occurs because there is sometimes a lack of checks for invalid statements in an optional block.

Remediation

Upgrade Debian:unstable libsepol to version 3.3-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Use After Free

  • Vulnerable module: libsepol/libsepol1
  • Introduced through: libsepol/libsepol1@2.7-1
  • Fixed in: 3.3-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libsepol/libsepol1@2.7-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libsepol package and not the libsepol package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The CIL compiler in SELinux 3.2 has a use-after-free in __cil_verify_classperms (called from __cil_verify_classpermission and __cil_pre_verify_helper).

Remediation

Upgrade Debian:unstable libsepol to version 3.3-1 or higher.

References

Use After Free vulnerability report

low severity

Use After Free

  • Vulnerable module: libsepol/libsepol1
  • Introduced through: libsepol/libsepol1@2.7-1
  • Fixed in: 3.3-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libsepol/libsepol1@2.7-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libsepol package and not the libsepol package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The CIL compiler in SELinux 3.2 has a use-after-free in __cil_verify_classperms (called from __verify_map_perm_classperms and hashtab_map).

Remediation

Upgrade Debian:unstable libsepol to version 3.3-1 or higher.

References

Use After Free vulnerability report

low severity

Use After Free

  • Vulnerable module: libsepol/libsepol1
  • Introduced through: libsepol/libsepol1@2.7-1
  • Fixed in: 3.3-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libsepol/libsepol1@2.7-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libsepol package and not the libsepol package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The CIL compiler in SELinux 3.2 has a use-after-free in cil_reset_classpermission (called from cil_reset_classperms_set and cil_reset_classperms_list).

Remediation

Upgrade Debian:unstable libsepol to version 3.3-1 or higher.

References

Use After Free vulnerability report

low severity

Improper Resource Shutdown or Release

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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:unstable relevant fixed versions and status.

A vulnerability was found in libxml2 up to 2.14.5. It has been declared as problematic. This vulnerability affects the function xmlParseSGMLCatalog of the component xmlcatalog. The manipulation leads to uncontrolled recursion. Attacking locally is a requirement. The exploit has been disclosed to the public and may be used. The real existence of this vulnerability is still doubted at the moment. The code maintainer explains, that "[t]he issue can only be triggered with untrusted SGML catalogs and it makes absolutely no sense to use untrusted catalogs. I also doubt that anyone is still using SGML catalogs at all."

Remediation

There is no fixed version for Debian:unstable libxml2.

References

Improper Resource Shutdown or Release vulnerability report

low severity

Out-of-Bounds

  • Vulnerable module: ncurses/libncurses5
  • Introduced through: ncurses/libncurses5@6.1-1, ncurses/libncursesw5@6.1-1 and others
  • Fixed in: 6.5+20251115-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › ncurses/libncurses5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/libncursesw5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/libtinfo5@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/ncurses-base@6.1-1
  • Introduced through: openjdk@10-ea-jdk › ncurses/ncurses-bin@6.1-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A vulnerability has been found in GNU ncurses up to 6.5-20250322 and classified as problematic. This vulnerability affects the function postprocess_termcap of the file tinfo/parse_entry.c. The manipulation leads to stack-based buffer overflow. The attack needs to be approached locally. Upgrading to version 6.5-20250329 is able to address this issue. It is recommended to upgrade the affected component.

Remediation

Upgrade Debian:unstable ncurses to version 6.5+20251115-2 or higher.

References

Out-of-Bounds vulnerability report

low severity

Link Following

  • Vulnerable module: perl
  • Introduced through: perl@5.26.1-5, perl/libperl5.26@5.26.1-5 and others

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › perl@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/libperl5.26@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-base@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-modules-5.26@5.26.1-5

NVD Description

Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

_is_safe in the File::Temp module for Perl does not properly handle symlinks.

Remediation

There is no fixed version for Debian:unstable perl.

References

Link Following vulnerability report

low severity

Out-of-bounds Write

  • Vulnerable module: procps
  • Introduced through: procps@2:3.3.12-4 and procps/libprocps6@2:3.3.12-4
  • Fixed in: 2:4.0.4-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › procps@2:3.3.12-4
  • Introduced through: openjdk@10-ea-jdk › procps/libprocps6@2:3.3.12-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream procps package and not the procps package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Under some circumstances, this weakness allows a user who has access to run the “ps” utility on a machine, the ability to write almost unlimited amounts of unfiltered data into the process heap.

Remediation

Upgrade Debian:unstable procps to version 2:4.0.4-1 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Arbitrary Code Injection

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.5-1 and shadow/passwd@1:4.5-1
  • Fixed in: 1:4.13+dfsg1-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › shadow/login@1:4.5-1
  • Introduced through: openjdk@10-ea-jdk › shadow/passwd@1:4.5-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream shadow package and not the shadow package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In Shadow 4.13, it is possible to inject control characters into fields provided to the SUID program chfn (change finger). Although it is not possible to exploit this directly (e.g., adding a new user fails because \n is in the block list), it is possible to misrepresent the /etc/passwd file when viewed. Use of \r manipulations and Unicode characters to work around blocking of the : character make it possible to give the impression that a new user has been added. In other words, an adversary may be able to convince a system administrator to take the system offline (an indirect, social-engineered denial of service) by demonstrating that "cat /etc/passwd" shows a rogue user account.

Remediation

Upgrade Debian:unstable shadow to version 1:4.13+dfsg1-2 or higher.

References

Arbitrary Code Injection vulnerability report

low severity

Out-of-bounds Read

  • Vulnerable module: systemd
  • Introduced through: systemd@238-4, systemd/libnss-systemd@238-4 and others
  • Fixed in: 240-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libnss-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libpam-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libsystemd0@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libudev1@238-2
  • Introduced through: openjdk@10-ea-jdk › systemd/systemd-sysv@238-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An out of bounds read was discovered in systemd-journald in the way it parses log messages that terminate with a colon ':'. A local attacker can use this flaw to disclose process memory data. Versions from v221 to v239 are vulnerable.

Remediation

Upgrade Debian:unstable systemd to version 240-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-bounds Read

  • Vulnerable module: tar
  • Introduced through: tar@1.29b-2
  • Fixed in: 1.34+dfsg-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tar@1.29b-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream tar package and not the tar package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw was found in the src/list.c of tar 1.33 and earlier. This flaw allows an attacker who can submit a crafted input file to tar to cause uncontrolled consumption of memory. The highest threat from this vulnerability is to system availability.

Remediation

Upgrade Debian:unstable tar to version 1.34+dfsg-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-Bounds

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.7.0-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable relevant fixed versions and status.

A weakness has been identified in LibTIFF 4.7.0. This affects the function main of the file tiffcrop.c of the component tiffcrop. Executing manipulation can lead to memory corruption. The attack can only be executed locally. The exploit has been made available to the public and could be exploited.

Remediation

Upgrade Debian:unstable tiff to version 4.7.0-5 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.7.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable 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

Upgrade Debian:unstable tiff to version 4.7.0-1 or higher.

References

Out-of-bounds Write vulnerability report

low severity

NULL Pointer Dereference

  • Vulnerable module: unzip
  • Introduced through: unzip@6.0-21

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › unzip@6.0-21

NVD Description

Note: Versions mentioned in the description apply only to the upstream unzip package and not the unzip package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw was found in unzip. The vulnerability occurs due to improper handling of Unicode strings, which can lead to a null pointer dereference. This flaw allows an attacker to input a specially crafted zip file, leading to a crash or code execution.

Remediation

There is no fixed version for Debian:unstable unzip.

References

NULL Pointer Dereference vulnerability report

low severity

Resource Exhaustion

  • Vulnerable module: unzip
  • Introduced through: unzip@6.0-21
  • Fixed in: 6.0-24

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › unzip@6.0-21

NVD Description

Note: Versions mentioned in the description apply only to the upstream unzip package and not the unzip package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Info-ZIP UnZip 6.0 mishandles the overlapping of files inside a ZIP container, leading to denial of service (resource consumption), aka a "better zip bomb" issue.

Remediation

Upgrade Debian:unstable unzip to version 6.0-24 or higher.

References

Resource Exhaustion vulnerability report

low severity

Missing Initialization of Resource

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 7.79.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable 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:unstable curl to version 7.79.1-1 or higher.

References

Missing Initialization of Resource vulnerability report

low severity
new

Resource Exhaustion

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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:unstable relevant fixed versions and status.

A flaw was found in the libxml2 library. This uncontrolled resource consumption vulnerability occurs when processing XML catalogs that contain repeated <nextCatalog> elements pointing to the same downstream catalog. A remote attacker can exploit this by supplying crafted catalogs, causing the parser to redundantly traverse catalog chains. This leads to excessive CPU consumption and degrades application availability, resulting in a denial-of-service condition.

Remediation

There is no fixed version for Debian:unstable libxml2.

References

Resource Exhaustion vulnerability report

low severity

Double Free

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2
  • Fixed in: 2.31-10

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The nameserver caching daemon (nscd) in the GNU C Library (aka glibc or libc6) 2.29 through 2.33, when processing a request for netgroup lookup, may crash due to a double-free, potentially resulting in degraded service or Denial of Service on the local system. This is related to netgroupcache.c.

Remediation

Upgrade Debian:unstable glibc to version 2.31-10 or higher.

References

Double Free vulnerability report

low severity

Stack-based Buffer Overflow

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.12.7+dfsg+really2.9.14-2.1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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:unstable relevant fixed versions and status.

A flaw was found in the interactive shell of the xmllint command-line tool, used for parsing XML files. When a user inputs an overly long command, the program does not check the input size properly, which can cause it to crash. This issue might allow attackers to run harmful code in rare configurations without modern protections.

Remediation

Upgrade Debian:unstable libxml2 to version 2.12.7+dfsg+really2.9.14-2.1 or higher.

References

Stack-based Buffer Overflow vulnerability report

low severity

Improper Resource Shutdown or Release

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.7.0-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable relevant fixed versions and status.

A vulnerability was found in LibTIFF up to 4.7.0. It has been declared as problematic. Affected by this vulnerability is the function t2p_read_tiff_init of the file tools/tiff2pdf.c of the component fax2ps. The manipulation leads to null pointer dereference. The attack needs to be approached locally. The complexity of an attack is rather high. The exploitation appears to be difficult. The patch is named 2ebfffb0e8836bfb1cd7d85c059cd285c59761a4. It is recommended to apply a patch to fix this issue.

Remediation

Upgrade Debian:unstable tiff to version 4.7.0-4 or higher.

References

Improper Resource Shutdown or Release vulnerability report

low severity

Improper Resource Shutdown or Release

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.7.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable relevant fixed versions and status.

A vulnerability classified as problematic was found in libtiff 4.6.0. This vulnerability affects the function PS_Lvl2page of the file tools/tiff2ps.c of the component tiff2ps. The manipulation leads to null pointer dereference. It is possible to launch the attack on the local host. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The name of the patch is 6ba36f159fd396ad11bf6b7874554197736ecc8b. It is recommended to apply a patch to fix this issue. One of the maintainers explains, that "[t]his error only occurs if DEFER_STRILE_LOAD (defer-strile-load:BOOL=ON) or TIFFOpen( .. "rD") option is used."

Remediation

Upgrade Debian:unstable tiff to version 4.7.1-1 or higher.

References

Improper Resource Shutdown or Release vulnerability report

low severity

Memory Leak

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.9-5
  • Fixed in: 4.7.0-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tiff/libtiff5@4.0.9-5

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:unstable relevant fixed versions and status.

A flaw has been found in LibTIFF 4.7.0. This affects the function _TIFFmallocExt/_TIFFCheckRealloc/TIFFHashSetNew/InitCCITTFax3 of the file tools/tiffcmp.c of the component tiffcmp. Executing manipulation can lead to memory leak. The attack is restricted to local execution. This attack is characterized by high complexity. It is indicated that the exploitability is difficult. The exploit has been published and may be used. There is ongoing doubt regarding the real existence of this vulnerability. This patch is called ed141286a37f6e5ddafb5069347ff5d587e7a4e0. It is best practice to apply a patch to resolve this issue. A researcher disputes the security impact of this issue, because "this is a memory leak on a command line tool that is about to exit anyway". In the reply the project maintainer declares this issue as "a simple 'bug' when leaving the command line tool and (...) not a security issue at all".

Remediation

Upgrade Debian:unstable tiff to version 4.7.0-4 or higher.

References

Memory Leak vulnerability report

low severity

Missing Release of Resource after Effective Lifetime

  • Vulnerable module: systemd
  • Introduced through: systemd@238-4, systemd/libnss-systemd@238-4 and others
  • Fixed in: 243-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libnss-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libpam-systemd@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libsystemd0@238-4
  • Introduced through: openjdk@10-ea-jdk › systemd/libudev1@238-2
  • Introduced through: openjdk@10-ea-jdk › systemd/systemd-sysv@238-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An issue was discovered in button_open in login/logind-button.c in systemd before 243. When executing the udevadm trigger command, a memory leak may occur.

Remediation

Upgrade Debian:unstable systemd to version 243-5 or higher.

References

Missing Release of Resource after Effective Lifetime vulnerability report

low severity

Use of Externally-Controlled Format String

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.40.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In Git for Windows, the Windows port of Git, no localized messages are shipped with the installer. As a consequence, Git is expected not to localize messages at all, and skips the gettext initialization. However, due to a change in MINGW-packages, the gettext() function's implicit initialization no longer uses the runtime prefix but uses the hard-coded path C:\mingw64\share\locale to look for localized messages. And since any authenticated user has the permission to create folders in C:\ (and since C:\mingw64 does not typically exist), it is possible for low-privilege users to place fake messages in that location where git.exe will pick them up in version 2.40.1.

This vulnerability is relatively hard to exploit and requires social engineering. For example, a legitimate message at the end of a clone could be maliciously modified to ask the user to direct their web browser to a malicious website, and the user might think that the message comes from Git and is legitimate. It does require local write access by the attacker, though, which makes this attack vector less likely. Version 2.40.1 contains a patch for this issue. Some workarounds are available. Do not work on a Windows machine with shared accounts, or alternatively create a C:\mingw64 folder and leave it empty. Users who have administrative rights may remove the permission to create folders in C:\.

Remediation

Upgrade Debian:unstable git to version 1:2.40.1-1 or higher.

References

Use of Externally-Controlled Format String vulnerability report

low severity
new

Reachable Assertion

  • Vulnerable module: avahi/libavahi-client3
  • Introduced through: avahi/libavahi-client3@0.7-3.1, avahi/libavahi-common-data@0.7-3.1 and others

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-client3@0.7-3.1
  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-common-data@0.7-3.1
  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-common3@0.7-3.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream avahi package and not the avahi package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Avahi is a system which facilitates service discovery on a local network via the mDNS/DNS-SD protocol suite. In 0.9-rc2 and earlier, an unprivileged local users can crash avahi-daemon (with wide-area disabled) by creating record browsers with the AVAHI_LOOKUP_USE_WIDE_AREA flag set via D-Bus. This can be done by either calling the RecordBrowserNew method directly or creating hostname/address/service resolvers/browsers that create those browsers internally themselves.

Remediation

There is no fixed version for Debian:unstable avahi.

References

Reachable Assertion vulnerability report

low severity
new

Reachable Assertion

  • Vulnerable module: avahi/libavahi-client3
  • Introduced through: avahi/libavahi-client3@0.7-3.1, avahi/libavahi-common-data@0.7-3.1 and others

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-client3@0.7-3.1
  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-common-data@0.7-3.1
  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-common3@0.7-3.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream avahi package and not the avahi package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Avahi is a system which facilitates service discovery on a local network via the mDNS/DNS-SD protocol suite. In 0.9-rc2 and earlier, avahi-daemon can be crashed by sending unsolicited announcements containing CNAME resource records pointing it to resource records with short TTLs. As soon as they expire avahi-daemon crashes.

Remediation

There is no fixed version for Debian:unstable avahi.

References

Reachable Assertion vulnerability report

low severity
new

Reachable Assertion

  • Vulnerable module: avahi/libavahi-client3
  • Introduced through: avahi/libavahi-client3@0.7-3.1, avahi/libavahi-common-data@0.7-3.1 and others

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-client3@0.7-3.1
  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-common-data@0.7-3.1
  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-common3@0.7-3.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream avahi package and not the avahi package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Avahi is a system which facilitates service discovery on a local network via the mDNS/DNS-SD protocol suite. In 0.9-rc2 and earlier, avahi-daemon can be crashed by sending 2 unsolicited announcements with CNAME resource records 2 seconds apart.

Remediation

There is no fixed version for Debian:unstable avahi.

References

Reachable Assertion vulnerability report

low severity

Resource Exhaustion

  • Vulnerable module: avahi/libavahi-client3
  • Introduced through: avahi/libavahi-client3@0.7-3.1, avahi/libavahi-common-data@0.7-3.1 and others

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-client3@0.7-3.1
  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-common-data@0.7-3.1
  • Introduced through: openjdk@10-ea-jdk › avahi/libavahi-common3@0.7-3.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream avahi package and not the avahi package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Avahi is a system which facilitates service discovery on a local network via the mDNS/DNS-SD protocol suite. In versions up to and including 0.9-rc2, the simple protocol server ignores the documented client limit and accepts unlimited connections, allowing for easy local DoS. Although CLIENTS_MAX is defined, server_work() unconditionally accept()s and client_new() always appends the new client and increments n_clients. There is no check against the limit. When client cannot be accepted as a result of maximal socket number of avahi-daemon, it logs unconditionally error per each connection. Unprivileged local users can exhaust daemon memory and file descriptors, causing a denial of service system-wide for mDNS/DNS-SD. Exhausting local file descriptors causes increased system load caused by logging errors of each of request. Overloading prevents glibc calls using nss-mdns plugins to resolve *.local. names and link-local addresses. As of time of publication, no known patched versions are available, but a candidate fix is available in pull request 808, and some workarounds are available. Simple clients are offered for nss-mdns package functionality. It is not possible to disable the unix socket /run/avahi-daemon/socket, but resolution requests received via DBus are not affected directly. Tools avahi-resolve, avahi-resolve-address and avahi-resolve-host-name are not affected, they use DBus interface. It is possible to change permissions of unix socket after avahi-daemon is started. But avahi-daemon does not provide any configuration for it. Additional access restrictions like SELinux can also prevent unwanted tools to access the socket and keep resolution working for trusted users.

Remediation

There is no fixed version for Debian:unstable avahi.

References

Resource Exhaustion vulnerability report

low severity

Reachable Assertion

  • Vulnerable module: cairo/libcairo-gobject2
  • Introduced through: cairo/libcairo-gobject2@1.15.10-3 and cairo/libcairo2@1.15.10-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › cairo/libcairo-gobject2@1.15.10-3
  • Introduced through: openjdk@10-ea-jdk › cairo/libcairo2@1.15.10-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream cairo package and not the cairo package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Cairo through 1.18.4, as used in Poppler through 25.08.0, has an "unscaled->face == NULL" assertion failure for _cairo_ft_unscaled_font_fini in cairo-ft-font.c.

Remediation

There is no fixed version for Debian:unstable cairo.

References

Reachable Assertion vulnerability report

low severity

Improper Authentication

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.7-3
  • Fixed in: 2.4.10-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › cups/libcups2@2.2.7-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream cups package and not the cups package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

OpenPrinting CUPS is an open source printing system for Linux and other Unix-like operating systems. In versions 2.4.12 and earlier, when the AuthType is set to anything but Basic, if the request contains an Authorization: Basic ... header, the password is not checked. This results in authentication bypass. Any configuration that allows an AuthType that is not Basic is affected. Version 2.4.13 fixes the issue.

Remediation

Upgrade Debian:unstable cups to version 2.4.10-4 or higher.

References

Improper Authentication vulnerability report

low severity

Improper Input Validation

  • Vulnerable module: cups/libcups2
  • Introduced through: cups/libcups2@2.2.7-3
  • Fixed in: 2.4.10-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › cups/libcups2@2.2.7-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream cups package and not the cups package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

OpenPrinting CUPS is an open source printing system for Linux and other Unix-like operating systems. In versions 2.4.12 and earlier, an unsafe deserialization and validation of printer attributes causes null dereference in the libcups library. This is a remote DoS vulnerability available in local subnet in default configurations. It can cause the cups & cups-browsed to crash, on all the machines in local network who are listening for printers (so by default for all regular linux machines). On systems where the vulnerability CVE-2024-47176 (cups-filters 1.x/cups-browsed 2.x vulnerability) was not fixed, and the firewall on the machine does not reject incoming communication to IPP port, and the machine is set to be available to public internet, attack vector "Network" is possible. The current versions of CUPS and cups-browsed projects have the attack vector "Adjacent" in their default configurations. Version 2.4.13 contains a patch for CVE-2025-58364.

Remediation

Upgrade Debian:unstable cups to version 2.4.10-4 or higher.

References

Improper Input Validation vulnerability report

low severity

Buffer Overflow

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 8.12.0+git20250209.89ed161+ds-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable relevant fixed versions and status.

When libcurl is asked to perform automatic gzip decompression of content-encoded HTTP responses with the CURLOPT_ACCEPT_ENCODING option, using zlib 1.2.0.3 or older, an attacker-controlled integer overflow would make libcurl perform a buffer overflow.

Remediation

Upgrade Debian:unstable curl to version 8.12.0+git20250209.89ed161+ds-1 or higher.

References

Buffer Overflow vulnerability report

low severity

CVE-2024-11053

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 8.11.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable relevant fixed versions and status.

When asked to both use a .netrc file for credentials and to follow HTTP redirects, curl could leak the password used for the first host to the followed-to host under certain circumstances.

This flaw only manifests itself if the netrc file has an entry that matches the redirect target hostname but the entry either omits just the password or omits both login and password.

Remediation

Upgrade Debian:unstable curl to version 8.11.1-1 or higher.

References

CVE-2024-11053 vulnerability report

low severity

CVE-2024-2004

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 8.7.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable relevant fixed versions and status.

When a protocol selection parameter option disables all protocols without adding any then the default set of protocols would remain in the allowed set due to an error in the logic for removing protocols. The below command would perform a request to curl.se with a plaintext protocol which has been explicitly disabled. curl --proto -all,-http http://curl.se The flaw is only present if the set of selected protocols disables the entire set of available protocols, in itself a command with no practical use and therefore unlikely to be encountered in real situations. The curl security team has thus assessed this to be low severity bug.

Remediation

Upgrade Debian:unstable curl to version 8.7.1-1 or higher.

References

CVE-2024-2004 vulnerability report

low severity

CVE-2024-2466

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 8.7.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable relevant fixed versions and status.

libcurl did not check the server certificate of TLS connections done to a host specified as an IP address, when built to use mbedTLS. libcurl would wrongly avoid using the set hostname function when the specified hostname was given as an IP address, therefore completely skipping the certificate check. This affects all uses of TLS protocols (HTTPS, FTPS, IMAPS, POPS3, SMTPS, etc).

Remediation

Upgrade Debian:unstable curl to version 8.7.1-1 or higher.

References

CVE-2024-2466 vulnerability report

low severity

CVE-2024-8096

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 8.10.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable relevant fixed versions and status.

When curl is told to use the Certificate Status Request TLS extension, often referred to as OCSP stapling, to verify that the server certificate is valid, it might fail to detect some OCSP problems and instead wrongly consider the response as fine. If the returned status reports another error than 'revoked' (like for example 'unauthorized') it is not treated as a bad certficate.

Remediation

Upgrade Debian:unstable curl to version 8.10.0-1 or higher.

References

CVE-2024-8096 vulnerability report

low severity

CVE-2025-0167

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 8.12.0+git20250209.89ed161+ds-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable relevant fixed versions and status.

When asked to use a .netrc file for credentials and to follow HTTP redirects, curl could leak the password used for the first host to the followed-to host under certain circumstances.

This flaw only manifests itself if the netrc file has a default entry that omits both login and password. A rare circumstance.

Remediation

Upgrade Debian:unstable curl to version 8.12.0+git20250209.89ed161+ds-1 or higher.

References

CVE-2025-0167 vulnerability report

low severity

CVE-2025-0665

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 8.12.0+git20250209.89ed161+ds-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable relevant fixed versions and status.

libcurl would wrongly close the same eventfd file descriptor twice when taking down a connection channel after having completed a threaded name resolve.

Remediation

Upgrade Debian:unstable curl to version 8.12.0+git20250209.89ed161+ds-1 or higher.

References

CVE-2025-0665 vulnerability report

low severity

CVE-2025-10148

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 8.16.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable relevant fixed versions and status.

curl's websocket code did not update the 32 bit mask pattern for each new outgoing frame as the specification says. Instead it used a fixed mask that persisted and was used throughout the entire connection.

A predictable mask pattern allows for a malicious server to induce traffic between the two communicating parties that could be interpreted by an involved proxy (configured or transparent) as genuine, real, HTTP traffic with content and thereby poison its cache. That cached poisoned content could then be served to all users of that proxy.

Remediation

Upgrade Debian:unstable curl to version 8.16.0-1 or higher.

References

CVE-2025-10148 vulnerability report

low severity

CVE-2025-10966

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 8.17.0~rc2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable relevant fixed versions and status.

curl's code for managing SSH connections when SFTP was done using the wolfSSH powered backend was flawed and missed host verification mechanisms.

This prevents curl from detecting MITM attackers and more.

Remediation

Upgrade Debian:unstable curl to version 8.17.0~rc2-1 or higher.

References

CVE-2025-10966 vulnerability report

low severity

CVE-2025-11563

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 8.17.0-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

NVD Description

This vulnerability has not been analyzed by NVD yet.

Remediation

Upgrade Debian:unstable curl to version 8.17.0-2 or higher.

References

CVE-2025-11563 vulnerability report

low severity
new

CVE-2025-13034

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 8.18.0~rc2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable relevant fixed versions and status.

When using CURLOPT_PINNEDPUBLICKEY option with libcurl or --pinnedpubkey with the curl tool,curl should check the public key of the server certificate to verify the peer.

This check was skipped in a certain condition that would then make curl allow the connection without performing the proper check, thus not noticing a possible impostor. To skip this check, the connection had to be done with QUIC with ngtcp2 built to use GnuTLS and the user had to explicitly disable the standard certificate verification.

Remediation

Upgrade Debian:unstable curl to version 8.18.0~rc2-1 or higher.

References

CVE-2025-13034 vulnerability report

low severity
new

CVE-2025-14017

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 8.18.0~rc2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable relevant fixed versions and status.

When doing multi-threaded LDAPS transfers (LDAP over TLS) with libcurl, changing TLS options in one thread would inadvertently change them globally and therefore possibly also affect other concurrently setup transfers.

Disabling certificate verification for a specific transfer could unintentionally disable the feature for other threads as well.

Remediation

Upgrade Debian:unstable curl to version 8.18.0~rc2-1 or higher.

References

CVE-2025-14017 vulnerability report

low severity
new

CVE-2025-14819

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 8.18.0~rc3-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable relevant fixed versions and status.

When doing TLS related transfers with reused easy or multi handles and altering the CURLSSLOPT_NO_PARTIALCHAIN option, libcurl could accidentally reuse a CA store cached in memory for which the partial chain option was reversed. Contrary to the user's wishes and expectations. This could make libcurl find and accept a trust chain that it otherwise would not.

Remediation

Upgrade Debian:unstable curl to version 8.18.0~rc3-1 or higher.

References

CVE-2025-14819 vulnerability report

low severity
new

CVE-2025-15079

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 8.18.0~rc3-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable relevant fixed versions and status.

When doing SSH-based transfers using either SCP or SFTP, and setting the known_hosts file, libcurl could still mistakenly accept connecting to hosts not present in the specified file if they were added as recognized in the libssh global known_hosts file.

Remediation

Upgrade Debian:unstable curl to version 8.18.0~rc3-1 or higher.

References

CVE-2025-15079 vulnerability report

low severity
new

CVE-2025-15224

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 8.18.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable relevant fixed versions and status.

When doing SSH-based transfers using either SCP or SFTP, and asked to do public key authentication, curl would wrongly still ask and authenticate using a locally running SSH agent.

Remediation

Upgrade Debian:unstable curl to version 8.18.0-1 or higher.

References

CVE-2025-15224 vulnerability report

low severity

Improper Certificate Validation

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 8.14.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable relevant fixed versions and status.

libcurl accidentally skips the certificate verification for QUIC connections when connecting to a host specified as an IP address in the URL. Therefore, it does not detect impostors or man-in-the-middle attacks.

Remediation

Upgrade Debian:unstable curl to version 8.14.0-1 or higher.

References

Improper Certificate Validation vulnerability report

low severity

Improper Certificate Validation

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 8.14.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable relevant fixed versions and status.

libcurl supports pinning of the server certificate public key for HTTPS transfers. Due to an omission, this check is not performed when connecting with QUIC for HTTP/3, when the TLS backend is wolfSSL. Documentation says the option works with wolfSSL, failing to specify that it does not for QUIC and HTTP/3. Since pinning makes the transfer succeed if the pin is fine, users could unwittingly connect to an impostor server without noticing.

Remediation

Upgrade Debian:unstable curl to version 8.14.0-1 or higher.

References

Improper Certificate Validation vulnerability report

low severity

Improper Certificate Validation

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 8.7.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable 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

Upgrade Debian:unstable curl to version 8.7.1-1 or higher.

References

Improper Certificate Validation vulnerability report

low severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 8.14.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable relevant fixed versions and status.

Due to a mistake in libcurl's WebSocket code, a malicious server can send a particularly crafted packet which makes libcurl get trapped in an endless busy-loop.

There is no other way for the application to escape or exit this loop other than killing the thread/process.

This might be used to DoS libcurl-using application.

Remediation

Upgrade Debian:unstable curl to version 8.14.1-1 or higher.

References

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability report

low severity

Missing Release of Resource after Effective Lifetime

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 8.7.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable 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

Upgrade Debian:unstable curl to version 8.7.1-1 or higher.

References

Missing Release of Resource after Effective Lifetime vulnerability report

low severity
new

Open Redirect

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 8.18.0~rc2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable relevant fixed versions and status.

When an OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer performs a cross-protocol redirect to a second URL that uses an IMAP, LDAP, POP3 or SMTP scheme, curl might wrongly pass on the bearer token to the new target host.

Remediation

Upgrade Debian:unstable curl to version 8.18.0~rc2-1 or higher.

References

Open Redirect vulnerability report

low severity

Out-of-bounds Read

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2, curl/libcurl3@7.58.0-2 and others
  • Fixed in: 8.16.0~rc2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › curl@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3@7.58.0-2
  • Introduced through: openjdk@10-ea-jdk › curl/libcurl3-gnutls@7.58.0-2

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:unstable relevant fixed versions and status.

  1. A cookie is set using the secure keyword for https://target
  2. curl is redirected to or otherwise made to speak with http://target (same hostname, but using clear text HTTP) using the same cookie set
  3. The same cookie name is set - but with just a slash as path (path=\&#34;/\&#34;,). Since this site is not secure, the cookie should just be ignored.
  4. A bug in the path comparison logic makes curl read outside a heap buffer boundary

The bug either causes a crash or it potentially makes the comparison come to the wrong conclusion and lets the clear-text site override the contents of the secure cookie, contrary to expectations and depending on the memory contents immediately following the single-byte allocation that holds the path.

The presumed and correct behavior would be to plainly ignore the second set of the cookie since it was already set as secure on a secure host so overriding it on an insecure host should not be okay.

Remediation

Upgrade Debian:unstable curl to version 8.16.0~rc2-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

CVE-2025-6297

  • Vulnerable module: dpkg
  • Introduced through: dpkg@1.19.0.5
  • Fixed in: 1.22.21

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › dpkg@1.19.0.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream dpkg package and not the dpkg package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

It was discovered that dpkg-deb does not properly sanitize directory permissions when extracting a control member into a temporary directory, which is documented as being a safe operation even on untrusted data. This may result in leaving temporary files behind on cleanup. Given automated and repeated execution of dpkg-deb commands on adversarial .deb packages or with well compressible files, placed inside a directory with permissions not allowing removal by a non-root user, this can end up in a DoS scenario due to causing disk quota exhaustion or disk full conditions.

Remediation

Upgrade Debian:unstable dpkg to version 1.22.21 or higher.

References

CVE-2025-6297 vulnerability report

low severity

CVE-2024-25260

  • Vulnerable module: elfutils/libelf1
  • Introduced through: elfutils/libelf1@0.170-0.3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › elfutils/libelf1@0.170-0.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream elfutils package and not the elfutils package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

elfutils v0.189 was discovered to contain a NULL pointer dereference via the handle_verdef() function at readelf.c.

Remediation

There is no fixed version for Debian:unstable elfutils.

References

CVE-2024-25260 vulnerability report

low severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.5-3
  • Fixed in: 2.7.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › expat/libexpat1@2.2.5-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

libexpat in Expat before 2.7.2 allows attackers to trigger large dynamic memory allocations via a small document that is submitted for parsing.

Remediation

Upgrade Debian:unstable expat to version 2.7.2-1 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

low severity

CVE-2024-50602

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.5-3
  • Fixed in: 2.6.3-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › expat/libexpat1@2.2.5-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An issue was discovered in libexpat before 2.6.4. There is a crash within the XML_ResumeParser function because XML_StopParser can stop/suspend an unstarted parser.

Remediation

Upgrade Debian:unstable expat to version 2.6.3-2 or higher.

References

CVE-2024-50602 vulnerability report

low severity

CVE-2025-31344

  • Vulnerable module: giflib/libgif7
  • Introduced through: giflib/libgif7@5.1.4-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › giflib/libgif7@5.1.4-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream giflib package and not the giflib package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Heap-based Buffer Overflow vulnerability in openEuler giflib on Linux. This vulnerability is associated with program files gif2rgb.C.

This issue affects giflib: through 5.2.2.

Remediation

There is no fixed version for Debian:unstable giflib.

References

CVE-2025-31344 vulnerability report

low severity

Out-of-bounds Write

  • Vulnerable module: giflib/libgif7
  • Introduced through: giflib/libgif7@5.1.4-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › giflib/libgif7@5.1.4-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream giflib package and not the giflib package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Giflib Project v5.2.2 is vulnerable to a heap buffer overflow via gif2rgb.

Remediation

There is no fixed version for Debian:unstable giflib.

References

Out-of-bounds Write vulnerability report

low severity

Arbitrary Argument Injection

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.50.1-0.1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Git GUI allows you to use the Git source control management tools via a GUI. When a user clones an untrusted repository and is tricked into editing a file located in a maliciously named directory in the repository, then Git GUI can create and overwrite files for which the user has write permission. This vulnerability is fixed in 2.43.7, 2.44.4, 2.45.4, 2.46.4, 2.47.3, 2.48.2, 2.49.1, and 2.50.1.

Remediation

Upgrade Debian:unstable git to version 1:2.50.1-0.1 or higher.

References

Arbitrary Argument Injection vulnerability report

low severity

External Control of File Name or Path

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.50.1-0.1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals. When cloning a repository Git knows to optionally fetch a bundle advertised by the remote server, which allows the server-side to offload parts of the clone to a CDN. The Git client does not perform sufficient validation of the advertised bundles, which allows the remote side to perform protocol injection. This protocol injection can cause the client to write the fetched bundle to a location controlled by the adversary. The fetched content is fully controlled by the server, which can in the worst case lead to arbitrary code execution. The use of bundle URIs is not enabled by default and can be controlled by the bundle.heuristic config option. Some cases of the vulnerability require that the adversary is in control of where a repository will be cloned to. This either requires social engineering or a recursive clone with submodules. These cases can thus be avoided by disabling recursive clones. This vulnerability is fixed in v2.43.7, v2.44.4, v2.45.4, v2.46.4, v2.47.3, v2.48.2, v2.49.1, and v2.50.1.

Remediation

Upgrade Debian:unstable git to version 1:2.50.1-0.1 or higher.

References

External Control of File Name or Path vulnerability report

low severity

Link Following

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.50.1-0.1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals. When reading a config value, Git strips any trailing carriage return and line feed (CRLF). When writing a config entry, values with a trailing CR are not quoted, causing the CR to be lost when the config is later read. When initializing a submodule, if the submodule path contains a trailing CR, the altered path is read resulting in the submodule being checked out to an incorrect location. If a symlink exists that points the altered path to the submodule hooks directory, and the submodule contains an executable post-checkout hook, the script may be unintentionally executed after checkout. This vulnerability is fixed in v2.43.7, v2.44.4, v2.45.4, v2.46.4, v2.47.3, v2.48.2, v2.49.1, and v2.50.1.

Remediation

Upgrade Debian:unstable git to version 1:2.50.1-0.1 or higher.

References

Link Following vulnerability report

low severity

OS Command Injection

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.50.1-0.1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Gitk is a Tcl/Tk based Git history browser. Starting with 2.41.0, a Git repository can be crafted in such a way that with some social engineering a user who has cloned the repository can be tricked into running any script (e.g., Bourne shell, Perl, Python, ...) supplied by the attacker by invoking gitk filename, where filename has a particular structure. The script is run with the privileges of the user. This vulnerability is fixed in 2.43.7, 2.44.4, 2.45.4, 2.46.4, 2.47.3, 2.48.2, 2.49.1, and 2.50.

Remediation

Upgrade Debian:unstable git to version 1:2.50.1-0.1 or higher.

References

OS Command Injection vulnerability report

low severity

OS Command Injection

  • Vulnerable module: git
  • Introduced through: git@1:2.16.2-1 and git/git-man@1:2.16.2-1
  • Fixed in: 1:2.50.1-0.1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › git@1:2.16.2-1
  • Introduced through: openjdk@10-ea-jdk › git/git-man@1:2.16.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Gitk is a Tcl/Tk based Git history browser. Starting with 1.7.0, when a user clones an untrusted repository and runs gitk without additional command arguments, files for which the user has write permission can be created and truncated. The option Support per-file encoding must have been enabled before in Gitk's Preferences. This option is disabled by default. The same happens when Show origin of this line is used in the main window (regardless of whether Support per-file encoding is enabled or not). This vulnerability is fixed in 2.43.7, 2.44.4, 2.45.4, 2.46.4, 2.47.3, 2.48.2, 2.49.1, and 2.50.1.

Remediation

Upgrade Debian:unstable git to version 1:2.50.1-0.1 or higher.

References

OS Command Injection vulnerability report

low severity

CVE-2024-34397

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.56.1-2 and glib2.0/libglib2.0-data@2.56.1-2
  • Fixed in: 2.80.0-10

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-0@2.56.1-2
  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-data@2.56.1-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An issue was discovered in GNOME GLib before 2.78.5, and 2.79.x and 2.80.x before 2.80.1. When a GDBus-based client subscribes to signals from a trusted system service such as NetworkManager on a shared computer, other users of the same computer can send spoofed D-Bus signals that the GDBus-based client will wrongly interpret as having been sent by the trusted system service. This could lead to the GDBus-based client behaving incorrectly, with an application-dependent impact.

Remediation

Upgrade Debian:unstable glib2.0 to version 2.80.0-10 or higher.

References

CVE-2024-34397 vulnerability report

low severity

CVE-2024-52533

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.56.1-2 and glib2.0/libglib2.0-data@2.56.1-2
  • Fixed in: 2.82.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-0@2.56.1-2
  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-data@2.56.1-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

gio/gsocks4aproxy.c in GNOME GLib before 2.82.1 has an off-by-one error and resultant buffer overflow because SOCKS4_CONN_MSG_LEN is not sufficient for a trailing '\0' character.

Remediation

Upgrade Debian:unstable glib2.0 to version 2.82.1-1 or higher.

References

CVE-2024-52533 vulnerability report

low severity
new

CVE-2026-0988

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.56.1-2 and glib2.0/libglib2.0-data@2.56.1-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-0@2.56.1-2
  • Introduced through: openjdk@10-ea-jdk › glib2.0/libglib2.0-data@2.56.1-2

NVD Description

This vulnerability has not been analyzed by NVD yet.

Remediation

There is no fixed version for Debian:unstable glib2.0.

References

CVE-2026-0988 vulnerability report

low severity

CVE-2024-2961

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2
  • Fixed in: 2.37-18

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The iconv() function in the GNU C Library versions 2.39 and older may overflow the output buffer passed to it by up to 4 bytes when converting strings to the ISO-2022-CN-EXT character set, which may be used to crash an application or overwrite a neighbouring variable.

Remediation

Upgrade Debian:unstable glibc to version 2.37-18 or higher.

References

CVE-2024-2961 vulnerability report

low severity

CVE-2024-33599

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2
  • Fixed in: 2.37-19

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

nscd: Stack-based buffer overflow in netgroup cache

If the Name Service Cache Daemon's (nscd) fixed size cache is exhausted by client requests then a subsequent client request for netgroup data may result in a stack-based buffer overflow. This flaw was introduced in glibc 2.15 when the cache was added to nscd.

This vulnerability is only present in the nscd binary.

Remediation

Upgrade Debian:unstable glibc to version 2.37-19 or higher.

References

CVE-2024-33599 vulnerability report

low severity

CVE-2024-33600

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2
  • Fixed in: 2.37-19

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

nscd: Null pointer crashes after notfound response

If the Name Service Cache Daemon's (nscd) cache fails to add a not-found netgroup response to the cache, the client request can result in a null pointer dereference. This flaw was introduced in glibc 2.15 when the cache was added to nscd.

This vulnerability is only present in the nscd binary.

Remediation

Upgrade Debian:unstable glibc to version 2.37-19 or higher.

References

CVE-2024-33600 vulnerability report

low severity

CVE-2024-33601

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2
  • Fixed in: 2.37-19

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

nscd: netgroup cache may terminate daemon on memory allocation failure

The Name Service Cache Daemon's (nscd) netgroup cache uses xmalloc or xrealloc and these functions may terminate the process due to a memory allocation failure resulting in a denial of service to the clients. The flaw was introduced in glibc 2.15 when the cache was added to nscd.

This vulnerability is only present in the nscd binary.

Remediation

Upgrade Debian:unstable glibc to version 2.37-19 or higher.

References

CVE-2024-33601 vulnerability report

low severity

CVE-2024-33602

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2
  • Fixed in: 2.37-19

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

nscd: netgroup cache assumes NSS callback uses in-buffer strings

The Name Service Cache Daemon's (nscd) netgroup cache can corrupt memory when the NSS callback does not store all strings in the provided buffer. The flaw was introduced in glibc 2.15 when the cache was added to nscd.

This vulnerability is only present in the nscd binary.

Remediation

Upgrade Debian:unstable glibc to version 2.37-19 or higher.

References

CVE-2024-33602 vulnerability report

low severity

CVE-2025-0395

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2
  • Fixed in: 2.40-6

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

When the assert() function in the GNU C Library versions 2.13 to 2.40 fails, it does not allocate enough space for the assertion failure message string and size information, which may lead to a buffer overflow if the message string size aligns to page size.

Remediation

Upgrade Debian:unstable glibc to version 2.40-6 or higher.

References

CVE-2025-0395 vulnerability report

low severity
new

CVE-2025-15281

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Calling wordexp with WRDE_REUSE in conjunction with WRDE_APPEND in the GNU C Library version 2.0 to version 2.42 may cause the interface to return uninitialized memory in the we_wordv member, which on subsequent calls to wordfree may abort the process.

Remediation

There is no fixed version for Debian:unstable glibc.

References

CVE-2025-15281 vulnerability report

low severity

CVE-2025-4802

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2
  • Fixed in: 2.39-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Untrusted LD_LIBRARY_PATH environment variable vulnerability in the GNU C Library version 2.27 to 2.38 allows attacker controlled loading of dynamically shared library in statically compiled setuid binaries that call dlopen (including internal dlopen calls after setlocale or calls to NSS functions such as getaddrinfo).

Remediation

Upgrade Debian:unstable glibc to version 2.39-4 or higher.

References

CVE-2025-4802 vulnerability report

low severity

CVE-2025-5702

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2
  • Fixed in: 2.41-9

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The strcmp implementation optimized for the Power10 processor in the GNU C Library version 2.39 and later writes to vector registers v20 to v31 without saving contents from the caller (those registers are defined as non-volatile registers by the powerpc64le ABI), resulting in overwriting of its contents and potentially altering control flow of the caller, or leaking the input strings to the function to other parts of the program.

Remediation

Upgrade Debian:unstable glibc to version 2.41-9 or higher.

References

CVE-2025-5702 vulnerability report

low severity

CVE-2025-5745

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2
  • Fixed in: 2.41-9

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The strncmp implementation optimized for the Power10 processor in the GNU C Library version 2.40 and later writes to vector registers v20 to v31 without saving contents from the caller (those registers are defined as non-volatile registers by the powerpc64le ABI), resulting in overwriting of its contents and potentially altering control flow of the caller, or leaking the input strings to the function to other parts of the program.

Remediation

Upgrade Debian:unstable glibc to version 2.41-9 or higher.

References

CVE-2025-5745 vulnerability report

low severity

CVE-2025-8058

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2
  • Fixed in: 2.41-11

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The regcomp function in the GNU C library version from 2.4 to 2.41 is subject to a double free if some previous allocation fails. It can be accomplished either by a malloc failure or by using an interposed malloc that injects random malloc failures. The double free can allow buffer manipulation depending of how the regex is constructed. This issue affects all architectures and ABIs supported by the GNU C library.

Remediation

Upgrade Debian:unstable glibc to version 2.41-11 or higher.

References

CVE-2025-8058 vulnerability report

low severity
new

CVE-2026-0861

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2
  • Fixed in: 2.42-8

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Passing too large an alignment to the memalign suite of functions (memalign, posix_memalign, aligned_alloc) in the GNU C Library version 2.30 to 2.42 may result in an integer overflow, which could consequently result in a heap corruption.

Note that the attacker must have control over both, the size as well as the alignment arguments of the memalign function to be able to exploit this. The size parameter must be close enough to PTRDIFF_MAX so as to overflow size_t along with the large alignment argument. This limits the malicious inputs for the alignment for memalign to the range [1<<62+ 1, 1<<63] and exactly 1<<63 for posix_memalign and aligned_alloc.

Typically the alignment argument passed to such functions is a known constrained quantity (e.g. page size, block size, struct sizes) and is not attacker controlled, because of which this may not be easily exploitable in practice. An application bug could potentially result in the input alignment being too large, e.g. due to a different buffer overflow or integer overflow in the application or its dependent libraries, but that is again an uncommon usage pattern given typical sources of alignments.

Remediation

Upgrade Debian:unstable glibc to version 2.42-8 or higher.

References

CVE-2026-0861 vulnerability report

low severity
new

CVE-2026-0915

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-2 and glibc/libc6@2.27-2
  • Fixed in: 2.42-8

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › glibc/libc-bin@2.27-2
  • Introduced through: openjdk@10-ea-jdk › glibc/libc6@2.27-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Calling getnetbyaddr or getnetbyaddr_r with a configured nsswitch.conf that specifies the library's DNS backend for networks and queries for a zero-valued network in the GNU C Library version 2.0 to version 2.42 can leak stack contents to the configured DNS resolver.

Remediation

Upgrade Debian:unstable glibc to version 2.42-8 or higher.

References

CVE-2026-0915 vulnerability report

low severity

CVE-2025-9820

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.18-1
  • Fixed in: 3.8.11-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gnutls28/libgnutls30@3.5.18-1

NVD Description

This vulnerability has not been analyzed by NVD yet.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.8.11-3 or higher.

References

CVE-2025-9820 vulnerability report

low severity

Uncaught Exception

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.18-1
  • Fixed in: 3.8.4-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gnutls28/libgnutls30@3.5.18-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw has been discovered in GnuTLS where an application crash can be induced when attempting to verify a specially crafted .pem bundle using the "certtool --verify-chain" command.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.8.4-2 or higher.

References

Uncaught Exception vulnerability report

low severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.18-1
  • Fixed in: 3.8.4-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gnutls28/libgnutls30@3.5.18-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw was found in GnuTLS. The Minerva attack is a cryptographic vulnerability that exploits deterministic behavior in systems like GnuTLS, leading to side-channel leaks. In specific scenarios, such as when using the GNUTLS_PRIVKEY_FLAG_REPRODUCIBLE flag, it can result in a noticeable step in nonce size from 513 to 512 bits, exposing a potential timing side-channel.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.8.4-2 or higher.

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

low severity

Arbitrary Code Injection

  • Vulnerable module: gtk+2.0/libgail-common
  • Introduced through: gtk+2.0/libgail-common@2.24.32-1, gtk+2.0/libgail18@2.24.32-1 and others
  • Fixed in: 2.24.33-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gtk+2.0/libgail-common@2.24.32-1
  • Introduced through: openjdk@10-ea-jdk › gtk+2.0/libgail18@2.24.32-1
  • Introduced through: openjdk@10-ea-jdk › gtk+2.0/libgtk2.0-0@2.24.32-1
  • Introduced through: openjdk@10-ea-jdk › gtk+2.0/libgtk2.0-bin@2.24.32-1
  • Introduced through: openjdk@10-ea-jdk › gtk+2.0/libgtk2.0-common@2.24.32-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream gtk+2.0 package and not the gtk+2.0 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw was found in the GTK library. Under certain conditions, it is possible for a library to be injected into a GTK application from the current working directory.

Remediation

Upgrade Debian:unstable gtk+2.0 to version 2.24.33-5 or higher.

References

Arbitrary Code Injection vulnerability report

low severity

Arbitrary Code Injection

  • Vulnerable module: gtk+3.0/gtk-update-icon-cache
  • Introduced through: gtk+3.0/gtk-update-icon-cache@3.22.30-1, gtk+3.0/libgtk-3-0@3.22.30-1 and others
  • Fixed in: 3.24.43-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › gtk+3.0/gtk-update-icon-cache@3.22.30-1
  • Introduced through: openjdk@10-ea-jdk › gtk+3.0/libgtk-3-0@3.22.30-1
  • Introduced through: openjdk@10-ea-jdk › gtk+3.0/libgtk-3-bin@3.22.30-1
  • Introduced through: openjdk@10-ea-jdk › gtk+3.0/libgtk-3-common@3.22.30-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream gtk+3.0 package and not the gtk+3.0 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw was found in the GTK library. Under certain conditions, it is possible for a library to be injected into a GTK application from the current working directory.

Remediation

Upgrade Debian:unstable gtk+3.0 to version 3.24.43-1 or higher.

References

Arbitrary Code Injection vulnerability report

low severity

Heap-based Buffer Overflow

  • Vulnerable module: harfbuzz/libharfbuzz0b
  • Introduced through: harfbuzz/libharfbuzz0b@1.7.6-1
  • Fixed in: 10.1.0-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › harfbuzz/libharfbuzz0b@1.7.6-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream harfbuzz package and not the harfbuzz package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

HarfBuzz is a text shaping engine. Starting with 8.5.0 through 10.0.1, there is a heap-based buffer overflow in the hb_cairo_glyphs_from_buffer function.

Remediation

Upgrade Debian:unstable harfbuzz to version 10.1.0-2 or higher.

References

Heap-based Buffer Overflow vulnerability report

low severity
new

NULL Pointer Dereference

  • Vulnerable module: harfbuzz/libharfbuzz0b
  • Introduced through: harfbuzz/libharfbuzz0b@1.7.6-1
  • Fixed in: 12.3.0-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › harfbuzz/libharfbuzz0b@1.7.6-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream harfbuzz package and not the harfbuzz package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

HarfBuzz is a text shaping engine. Prior to version 12.3.0, a null pointer dereference vulnerability exists in the SubtableUnicodesCache::create function located in src/hb-ot-cmap-table.hh. The function fails to check if hb_malloc returns NULL before using placement new to construct an object at the returned pointer address. When hb_malloc fails to allocate memory (which can occur in low-memory conditions or when using custom allocators that simulate allocation failures), it returns NULL. The code then attempts to call the constructor on this null pointer using placement new syntax, resulting in undefined behavior and a Segmentation Fault. This issue has been patched in version 12.3.0.

Remediation

Upgrade Debian:unstable harfbuzz to version 12.3.0-4 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

CVE-2024-26461

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.16-2, krb5/libk5crypto3@1.16-2 and others

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › krb5/libgssapi-krb5-2@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libk5crypto3@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libkrb5-3@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libkrb5support0@1.16-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Kerberos 5 (aka krb5) 1.21.2 contains a memory leak vulnerability in /krb5/src/lib/gssapi/krb5/k5sealv3.c.

Remediation

There is no fixed version for Debian:unstable krb5.

References

CVE-2024-26461 vulnerability report

low severity

Integer Overflow or Wraparound

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.16-2, krb5/libk5crypto3@1.16-2 and others
  • Fixed in: 1.21.3-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › krb5/libgssapi-krb5-2@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libk5crypto3@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libkrb5-3@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libkrb5support0@1.16-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In MIT Kerberos 5 (aka krb5) before 1.22 (with incremental propagation), there is an integer overflow for a large update size to resize() in kdb_log.c. An authenticated attacker can cause an out-of-bounds write and kadmind daemon crash.

Remediation

Upgrade Debian:unstable krb5 to version 1.21.3-5 or higher.

References

Integer Overflow or Wraparound vulnerability report

low severity

Memory Leak

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.16-2, krb5/libk5crypto3@1.16-2 and others

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › krb5/libgssapi-krb5-2@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libk5crypto3@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libkrb5-3@1.16-2
  • Introduced through: openjdk@10-ea-jdk › krb5/libkrb5support0@1.16-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Kerberos 5 (aka krb5) 1.21.2 contains a memory leak in /krb5/src/lib/rpc/pmap_rmt.c.

Remediation

There is no fixed version for Debian:unstable krb5.

References

Memory Leak vulnerability report

low severity

CVE-2025-29070

  • Vulnerable module: lcms2/liblcms2-2
  • Introduced through: lcms2/liblcms2-2@2.9-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › lcms2/liblcms2-2@2.9-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream lcms2 package and not the lcms2 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A heap buffer overflow vulnerability has been identified in thesmooth2() in cmsgamma.c in lcms2-2.16 which allows a remote attacker to cause a denial of service. NOTE: the Supplier disputes this because "this is not exploitable as this function is never called on normal color management, is there only as a helper for low-level programming and investigation."

Remediation

There is no fixed version for Debian:unstable lcms2.

References

CVE-2025-29070 vulnerability report

low severity

CVE-2025-1390

  • Vulnerable module: libcap2
  • Introduced through: libcap2@1:2.25-1.2
  • Fixed in: 1:2.73-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libcap2@1:2.25-1.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream libcap2 package and not the libcap2 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The PAM module pam_cap.so of libcap configuration supports group names starting with “@”, during actual parsing, configurations not starting with “@” are incorrectly recognized as group names. This may result in nonintended users being granted an inherited capability set, potentially leading to security risks. Attackers can exploit this vulnerability to achieve local privilege escalation on systems where /etc/security/capability.conf is used to configure user inherited privileges by constructing specific usernames.

Remediation

Upgrade Debian:unstable libcap2 to version 1:2.73-4 or higher.

References

CVE-2025-1390 vulnerability report

low severity

Information Exposure

  • Vulnerable module: libgcrypt20
  • Introduced through: libgcrypt20@1.8.1-4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libgcrypt20@1.8.1-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream libgcrypt20 package and not the libgcrypt20 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A timing-based side-channel flaw was found in libgcrypt's RSA implementation. This issue may allow a remote attacker to initiate a Bleichenbacher-style attack, which can lead to the decryption of RSA ciphertexts.

Remediation

There is no fixed version for Debian:unstable libgcrypt20.

References

Information Exposure vulnerability report

low severity

CVE-2023-45924

  • Vulnerable module: libglvnd/libegl1
  • Introduced through: libglvnd/libegl1@1.0.0+git20180308-1, libglvnd/libgl1@1.0.0+git20180308-1 and others

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libglvnd/libegl1@1.0.0+git20180308-1
  • Introduced through: openjdk@10-ea-jdk › libglvnd/libgl1@1.0.0+git20180308-1
  • Introduced through: openjdk@10-ea-jdk › libglvnd/libglvnd0@1.0.0+git20180308-1
  • Introduced through: openjdk@10-ea-jdk › libglvnd/libglx0@1.0.0+git20180308-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libglvnd package and not the libglvnd package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

libglxproto.c in OpenGL libglvnd bb06db5a was discovered to contain a segmentation violation via the function glXGetDrawableScreen(). NOTE: this is disputed because there are no common situations in which users require uninterrupted operation with an attacker-controller server.

Remediation

There is no fixed version for Debian:unstable libglvnd.

References

CVE-2023-45924 vulnerability report

low severity

CVE-2025-66293

  • Vulnerable module: libpng1.6/libpng16-16
  • Introduced through: libpng1.6/libpng16-16@1.6.34-1
  • Fixed in: 1.6.52-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libpng1.6/libpng16-16@1.6.34-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. Prior to 1.6.52, an out-of-bounds read vulnerability in libpng's simplified API allows reading up to 1012 bytes beyond the png_sRGB_base[512] array when processing valid palette PNG images with partial transparency and gamma correction. The PNG files that trigger this vulnerability are valid per the PNG specification; the bug is in libpng's internal state management. Upgrade to libpng 1.6.52 or later.

Remediation

Upgrade Debian:unstable libpng1.6 to version 1.6.52-1 or higher.

References

CVE-2025-66293 vulnerability report

low severity

Heap-based Buffer Overflow

  • Vulnerable module: libpng1.6/libpng16-16
  • Introduced through: libpng1.6/libpng16-16@1.6.34-1
  • Fixed in: 1.6.51-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libpng1.6/libpng16-16@1.6.34-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From version 1.6.0 to before 1.6.51, there is a heap buffer overflow vulnerability in the libpng simplified API function png_image_finish_read when processing 16-bit interlaced PNGs with 8-bit output format. Attacker-crafted interlaced PNG files cause heap writes beyond allocated buffer bounds. This issue has been patched in version 1.6.51.

Remediation

Upgrade Debian:unstable libpng1.6 to version 1.6.51-1 or higher.

References

Heap-based Buffer Overflow vulnerability report

low severity

Out-of-bounds Read

  • Vulnerable module: libpng1.6/libpng16-16
  • Introduced through: libpng1.6/libpng16-16@1.6.34-1
  • Fixed in: 1.6.51-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libpng1.6/libpng16-16@1.6.34-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. Prior to version 1.6.51, a heap buffer over-read vulnerability exists in libpng's png_do_quantize function when processing PNG files with malformed palette indices. The vulnerability occurs when palette_lookup array bounds are not validated against externally-supplied image data, allowing an attacker to craft a PNG file with out-of-range palette indices that trigger out-of-bounds memory access. This issue has been patched in version 1.6.51.

Remediation

Upgrade Debian:unstable libpng1.6 to version 1.6.51-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-bounds Read

  • Vulnerable module: libpng1.6/libpng16-16
  • Introduced through: libpng1.6/libpng16-16@1.6.34-1
  • Fixed in: 1.6.51-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libpng1.6/libpng16-16@1.6.34-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From version 1.6.0 to before 1.6.51, an out-of-bounds read vulnerability exists in png_image_read_composite when processing palette images with PNG_FLAG_OPTIMIZE_ALPHA enabled. The palette compositing code in png_init_read_transformations incorrectly applies background compositing during premultiplication, violating the invariant component ≤ alpha × 257 required by the simplified PNG API. This issue has been patched in version 1.6.51.

Remediation

Upgrade Debian:unstable libpng1.6 to version 1.6.51-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-bounds Read

  • Vulnerable module: libpng1.6/libpng16-16
  • Introduced through: libpng1.6/libpng16-16@1.6.34-1
  • Fixed in: 1.6.51-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libpng1.6/libpng16-16@1.6.34-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From version 1.6.0 to before 1.6.51, a heap buffer over-read vulnerability exists in libpng's png_write_image_8bit function when processing 8-bit images through the simplified write API with convert_to_8bit enabled. The vulnerability affects 8-bit grayscale+alpha, RGB/RGBA, and images with incomplete row data. A conditional guard incorrectly allows 8-bit input to enter code expecting 16-bit input, causing reads up to 2 bytes beyond allocated buffer boundaries. This issue has been patched in version 1.6.51.

Remediation

Upgrade Debian:unstable libpng1.6 to version 1.6.51-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity
new

Out-of-bounds Read

  • Vulnerable module: libpng1.6/libpng16-16
  • Introduced through: libpng1.6/libpng16-16@1.6.34-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libpng1.6/libpng16-16@1.6.34-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From 1.6.51 to 1.6.53, there is a heap buffer over-read in the libpng simplified API function png_image_finish_read when processing interlaced 16-bit PNGs with 8-bit output format and non-minimal row stride. This is a regression introduced by the fix for CVE-2025-65018. This vulnerability is fixed in 1.6.54.

Remediation

There is no fixed version for Debian:unstable libpng1.6.

References

Out-of-bounds Read vulnerability report

low severity
new

Out-of-bounds Read

  • Vulnerable module: libpng1.6/libpng16-16
  • Introduced through: libpng1.6/libpng16-16@1.6.34-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libpng1.6/libpng16-16@1.6.34-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From 1.6.26 to 1.6.53, there is an integer truncation in the libpng simplified write API functions png_write_image_16bit and png_write_image_8bit causes heap buffer over-read when the caller provides a negative row stride (for bottom-up image layouts) or a stride exceeding 65535 bytes. The bug was introduced in libpng 1.6.26 (October 2016) by casts added to silence compiler warnings on 16-bit systems. This vulnerability is fixed in 1.6.54.

Remediation

There is no fixed version for Debian:unstable libpng1.6.

References

Out-of-bounds Read vulnerability report

low severity
new

CVE-2025-13151

  • Vulnerable module: libtasn1-6
  • Introduced through: libtasn1-6@4.13-2
  • Fixed in: 4.21.0-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libtasn1-6@4.13-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream libtasn1-6 package and not the libtasn1-6 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Stack-based buffer overflow in libtasn1 version: v4.20.0. The function fails to validate the size of input data resulting in a buffer overflow in asn1_expend_octet_string.

Remediation

Upgrade Debian:unstable libtasn1-6 to version 4.21.0-2 or higher.

References

CVE-2025-13151 vulnerability report

low severity

CVE-2024-34459

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-6.1
  • Fixed in: 2.12.7+dfsg+really2.9.14-0.4

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › libxml2@2.9.4+dfsg1-6.1

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:unstable relevant fixed versions and status.

An issue was discovered in xmllint (from libxml2) before 2.11.8 and 2.12.x before 2.12.7. Formatting error messages with xmllint --htmlout can result in a buffer over-read in xmlHTMLPrintFileContext in xmllint.c.

Remediation

Upgrade Debian:unstable libxml2 to version 2.12.7+dfsg+really2.9.14-0.4 or higher.

References

CVE-2024-34459 vulnerability report

low severity

CVE-2023-45913

  • Vulnerable module: mesa/libegl-mesa0
  • Introduced through: mesa/libegl-mesa0@17.3.9-1, mesa/libgbm1@17.3.9-1 and others

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › mesa/libegl-mesa0@17.3.9-1
  • Introduced through: openjdk@10-ea-jdk › mesa/libgbm1@17.3.9-1
  • Introduced through: openjdk@10-ea-jdk › mesa/libgl1-mesa-dri@17.3.9-1
  • Introduced through: openjdk@10-ea-jdk › mesa/libgl1-mesa-glx@17.3.9-1
  • Introduced through: openjdk@10-ea-jdk › mesa/libglapi-mesa@17.3.9-1
  • Introduced through: openjdk@10-ea-jdk › mesa/libglx-mesa0@17.3.9-1
  • Introduced through: openjdk@10-ea-jdk › mesa/libwayland-egl1-mesa@17.3.9-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream mesa package and not the mesa package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Mesa v23.0.4 was discovered to contain a NULL pointer dereference via the function dri2GetGlxDrawableFromXDrawableId(). This vulnerability is triggered when the X11 server sends an DRI2_BufferSwapComplete event unexpectedly when the application is using DRI3. NOTE: this is disputed because there is no scenario in which the vulnerability was demonstrated.

Remediation

There is no fixed version for Debian:unstable mesa.

References

CVE-2023-45913 vulnerability report

low severity

CVE-2023-45919

  • Vulnerable module: mesa/libegl-mesa0
  • Introduced through: mesa/libegl-mesa0@17.3.9-1, mesa/libgbm1@17.3.9-1 and others

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › mesa/libegl-mesa0@17.3.9-1
  • Introduced through: openjdk@10-ea-jdk › mesa/libgbm1@17.3.9-1
  • Introduced through: openjdk@10-ea-jdk › mesa/libgl1-mesa-dri@17.3.9-1
  • Introduced through: openjdk@10-ea-jdk › mesa/libgl1-mesa-glx@17.3.9-1
  • Introduced through: openjdk@10-ea-jdk › mesa/libglapi-mesa@17.3.9-1
  • Introduced through: openjdk@10-ea-jdk › mesa/libglx-mesa0@17.3.9-1
  • Introduced through: openjdk@10-ea-jdk › mesa/libwayland-egl1-mesa@17.3.9-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream mesa package and not the mesa package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Mesa 23.0.4 was discovered to contain a buffer over-read in glXQueryServerString(). NOTE: this is disputed because there are no common situations in which users require uninterrupted operation with an attacker-controller server.

Remediation

There is no fixed version for Debian:unstable mesa.

References

CVE-2023-45919 vulnerability report

low severity

CVE-2023-45922

  • Vulnerable module: mesa/libegl-mesa0
  • Introduced through: mesa/libegl-mesa0@17.3.9-1, mesa/libgbm1@17.3.9-1 and others

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › mesa/libegl-mesa0@17.3.9-1
  • Introduced through: openjdk@10-ea-jdk › mesa/libgbm1@17.3.9-1
  • Introduced through: openjdk@10-ea-jdk › mesa/libgl1-mesa-dri@17.3.9-1
  • Introduced through: openjdk@10-ea-jdk › mesa/libgl1-mesa-glx@17.3.9-1
  • Introduced through: openjdk@10-ea-jdk › mesa/libglapi-mesa@17.3.9-1
  • Introduced through: openjdk@10-ea-jdk › mesa/libglx-mesa0@17.3.9-1
  • Introduced through: openjdk@10-ea-jdk › mesa/libwayland-egl1-mesa@17.3.9-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream mesa package and not the mesa package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

glx_pbuffer.c in Mesa 23.0.4 was discovered to contain a segmentation violation when calling __glXGetDrawableAttribute(). NOTE: this is disputed because there are no common situations in which users require uninterrupted operation with an attacker-controller server.

Remediation

There is no fixed version for Debian:unstable mesa.

References

CVE-2023-45922 vulnerability report

low severity

CVE-2023-45931

  • Vulnerable module: mesa/libegl-mesa0
  • Introduced through: mesa/libegl-mesa0@17.3.9-1, mesa/libgbm1@17.3.9-1 and others

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › mesa/libegl-mesa0@17.3.9-1
  • Introduced through: openjdk@10-ea-jdk › mesa/libgbm1@17.3.9-1
  • Introduced through: openjdk@10-ea-jdk › mesa/libgl1-mesa-dri@17.3.9-1
  • Introduced through: openjdk@10-ea-jdk › mesa/libgl1-mesa-glx@17.3.9-1
  • Introduced through: openjdk@10-ea-jdk › mesa/libglapi-mesa@17.3.9-1
  • Introduced through: openjdk@10-ea-jdk › mesa/libglx-mesa0@17.3.9-1
  • Introduced through: openjdk@10-ea-jdk › mesa/libwayland-egl1-mesa@17.3.9-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream mesa package and not the mesa package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Mesa 23.0.4 was discovered to contain a NULL pointer dereference in check_xshm() for the has_error state. NOTE: this is disputed because there is no scenario in which the vulnerability was demonstrated.

Remediation

There is no fixed version for Debian:unstable mesa.

References

CVE-2023-45931 vulnerability report

low severity

CVE-2024-28182

  • Vulnerable module: nghttp2/libnghttp2-14
  • Introduced through: nghttp2/libnghttp2-14@1.31.0-1
  • Fixed in: 1.61.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nghttp2/libnghttp2-14@1.31.0-1

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:unstable 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

Upgrade Debian:unstable nghttp2 to version 1.61.0-1 or higher.

References

CVE-2024-28182 vulnerability report

low severity

CVE-2024-6602

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.36.1-1
  • Fixed in: 2:3.101-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nss/libnss3@2:3.36.1-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nss package and not the nss package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A mismatch between allocator and deallocator could have led to memory corruption. This vulnerability affects Firefox < 128, Firefox ESR < 115.13, Thunderbird < 115.13, and Thunderbird < 128.

Remediation

Upgrade Debian:unstable nss to version 2:3.101-1 or higher.

References

CVE-2024-6602 vulnerability report

low severity

Information Exposure

  • Vulnerable module: nss/libnss3
  • Introduced through: nss/libnss3@2:3.36.1-1
  • Fixed in: 2:3.98-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › nss/libnss3@2:3.36.1-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nss package and not the nss package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

NSS was susceptible to a timing side-channel attack when performing RSA decryption. This attack could potentially allow an attacker to recover the private data. This vulnerability affects Firefox < 124, Firefox ESR < 115.9, and Thunderbird < 115.9.

Remediation

Upgrade Debian:unstable nss to version 2:3.98-1 or higher.

References

Information Exposure vulnerability report

low severity
new

Out-of-bounds Read

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1 and openldap/libldap-common@2.4.45+dfsg-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-2.4-2@2.4.45+dfsg-1
  • Introduced through: openjdk@10-ea-jdk › openldap/libldap-common@2.4.45+dfsg-1

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:unstable relevant fixed versions and status.

OpenLDAP Lightning Memory-Mapped Database (LMDB) versions up to and including 0.9.14, prior to commit 8e1fda8, contain a heap buffer underflow in the readline() function of mdb_load. When processing malformed input containing an embedded NUL byte, an unsigned offset calculation can underflow and cause an out-of-bounds read of one byte before the allocated heap buffer. This can cause mdb_load to crash, leading to a limited denial-of-service condition.

Remediation

There is no fixed version for Debian:unstable openldap.

References

Out-of-bounds Read vulnerability report

low severity

CVE-2024-39894

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:7.6p1-4
  • Fixed in: 1:9.8p1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssh/openssh-client@1:7.6p1-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

OpenSSH 9.5 through 9.7 before 9.8 sometimes allows timing attacks against echo-off password entry (e.g., for su and Sudo) because of an ObscureKeystrokeTiming logic error. Similarly, other timing attacks against keystroke entry could occur.

Remediation

Upgrade Debian:unstable openssh to version 1:9.8p1-1 or higher.

References

CVE-2024-39894 vulnerability report

low severity

Failure to Sanitize Special Element

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:7.6p1-4
  • Fixed in: 1:10.1p1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssh/openssh-client@1:7.6p1-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

ssh in OpenSSH before 10.1 allows control characters in usernames that originate from certain possibly untrusted sources, potentially leading to code execution when a ProxyCommand is used. The untrusted sources are the command line and %-sequence expansion of a configuration file. (A configuration file that provides a complete literal username is not categorized as an untrusted source.)

Remediation

Upgrade Debian:unstable openssh to version 1:10.1p1-1 or higher.

References

Failure to Sanitize Special Element vulnerability report

low severity

Improper Neutralization of Null Byte or NUL Character

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:7.6p1-4
  • Fixed in: 1:10.1p1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssh/openssh-client@1:7.6p1-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

ssh in OpenSSH before 10.1 allows the '\0' character in an ssh:// URI, potentially leading to code execution when a ProxyCommand is used.

Remediation

Upgrade Debian:unstable openssh to version 1:10.1p1-1 or higher.

References

Improper Neutralization of Null Byte or NUL Character vulnerability report

low severity

CVE-2023-6237

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 3.1.5-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Issue summary: Checking excessively long invalid RSA public keys may take a long time.

Impact summary: Applications that use the function EVP_PKEY_public_check() to check RSA public keys may experience long delays. Where the key that is being checked has been obtained from an untrusted source this may lead to a Denial of Service.

When function EVP_PKEY_public_check() is called on RSA public keys, a computation is done to confirm that the RSA modulus, n, is composite. For valid RSA keys, n is a product of two or more large primes and this computation completes quickly. However, if n is an overly large prime, then this computation would take a long time.

An application that calls EVP_PKEY_public_check() and supplies an RSA key obtained from an untrusted source could be vulnerable to a Denial of Service attack.

The function EVP_PKEY_public_check() is not called from other OpenSSL functions however it is called from the OpenSSL pkey command line application. For that reason that application is also vulnerable if used with the '-pubin' and '-check' options on untrusted data.

The OpenSSL SSL/TLS implementation is not affected by this issue.

The OpenSSL 3.0 and 3.1 FIPS providers are affected by this issue.

Remediation

Upgrade Debian:unstable openssl to version 3.1.5-1 or higher.

References

CVE-2023-6237 vulnerability report

low severity

CVE-2024-12797

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 3.4.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Issue summary: Clients using RFC7250 Raw Public Keys (RPKs) to authenticate a server may fail to notice that the server was not authenticated, because handshakes don't abort as expected when the SSL_VERIFY_PEER verification mode is set.

Impact summary: TLS and DTLS connections using raw public keys may be vulnerable to man-in-middle attacks when server authentication failure is not detected by clients.

RPKs are disabled by default in both TLS clients and TLS servers. The issue only arises when TLS clients explicitly enable RPK use by the server, and the server, likewise, enables sending of an RPK instead of an X.509 certificate chain. The affected clients are those that then rely on the handshake to fail when the server's RPK fails to match one of the expected public keys, by setting the verification mode to SSL_VERIFY_PEER.

Clients that enable server-side raw public keys can still find out that raw public key verification failed by calling SSL_get_verify_result(), and those that do, and take appropriate action, are not affected. This issue was introduced in the initial implementation of RPK support in OpenSSL 3.2.

The FIPS modules in 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.

Remediation

Upgrade Debian:unstable openssl to version 3.4.1-1 or higher.

References

CVE-2024-12797 vulnerability report

low severity

CVE-2024-13176

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 3.4.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Issue summary: A timing side-channel which could potentially allow recovering the private key exists in the ECDSA signature computation.

Impact summary: A timing side-channel in ECDSA signature computations could allow recovering the private key by an attacker. However, measuring the timing would require either local access to the signing application or a very fast network connection with low latency.

There is a timing signal of around 300 nanoseconds when the top word of the inverted ECDSA nonce value is zero. This can happen with significant probability only for some of the supported elliptic curves. In particular the NIST P-521 curve is affected. To be able to measure this leak, the attacker process must either be located in the same physical computer or must have a very fast network connection with low latency. For that reason the severity of this vulnerability is Low.

The FIPS modules in 3.4, 3.3, 3.2, 3.1 and 3.0 are affected by this issue.

Remediation

Upgrade Debian:unstable openssl to version 3.4.1-1 or higher.

References

CVE-2024-13176 vulnerability report

low severity

CVE-2024-2511

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 3.2.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Issue summary: Some non-default TLS server configurations can cause unbounded memory growth when processing TLSv1.3 sessions

Impact summary: An attacker may exploit certain server configurations to trigger unbounded memory growth that would lead to a Denial of Service

This problem can occur in TLSv1.3 if the non-default SSL_OP_NO_TICKET option is being used (but not if early_data support is also configured and the default anti-replay protection is in use). In this case, under certain conditions, the session cache can get into an incorrect state and it will fail to flush properly as it fills. The session cache will continue to grow in an unbounded manner. A malicious client could deliberately create the scenario for this failure to force a Denial of Service. It may also happen by accident in normal operation.

This issue only affects TLS servers supporting TLSv1.3. It does not affect TLS clients.

The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue. OpenSSL 1.0.2 is also not affected by this issue.

Remediation

Upgrade Debian:unstable openssl to version 3.2.2-1 or higher.

References

CVE-2024-2511 vulnerability report

low severity

CVE-2024-4603

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 3.2.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Issue summary: Checking excessively long DSA keys or parameters may be very slow.

Impact summary: Applications that use the functions EVP_PKEY_param_check() or EVP_PKEY_public_check() to check a DSA public key or DSA parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service.

The functions EVP_PKEY_param_check() or EVP_PKEY_public_check() perform various checks on DSA parameters. Some of those computations take a long time if the modulus (p parameter) is too large.

Trying to use a very large modulus is slow and OpenSSL will not allow using public keys with a modulus which is over 10,000 bits in length for signature verification. However the key and parameter check functions do not limit the modulus size when performing the checks.

An application that calls EVP_PKEY_param_check() or EVP_PKEY_public_check() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack.

These functions are not called by OpenSSL itself on untrusted DSA keys so only applications that directly call these functions may be vulnerable.

Also vulnerable are the OpenSSL pkey and pkeyparam command line applications when using the -check option.

The OpenSSL SSL/TLS implementation is not affected by this issue.

The OpenSSL 3.0 and 3.1 FIPS providers are affected by this issue.

Remediation

Upgrade Debian:unstable openssl to version 3.2.2-1 or higher.

References

CVE-2024-4603 vulnerability report

low severity

CVE-2024-4741

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 3.2.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause memory to be accessed that was previously freed in some situations

Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, only applications that directly call the SSL_free_buffers function are affected by this issue. Applications that do not call this function are not vulnerable. Our investigations indicate that this function is rarely used by applications.

The SSL_free_buffers function is used to free the internal OpenSSL buffer used when processing an incoming record from the network. The call is only expected to succeed if the buffer is not currently in use. However, two scenarios have been identified where the buffer is freed even when still in use.

The first scenario occurs where a record header has been received from the network and processed by OpenSSL, but the full record body has not yet arrived. In this case calling SSL_free_buffers will succeed even though a record has only been partially processed and the buffer is still in use.

The second scenario occurs where a full record containing application data has been received and processed by OpenSSL but the application has only read part of this data. Again a call to SSL_free_buffers will succeed even though the buffer is still in use.

While these scenarios could occur accidentally during normal operation a malicious attacker could attempt to engineer a stituation where this occurs. We are not aware of this issue being actively exploited.

The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.

Remediation

Upgrade Debian:unstable openssl to version 3.2.2-1 or higher.

References

CVE-2024-4741 vulnerability report

low severity

CVE-2024-5535

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 3.3.2-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Issue summary: Calling the OpenSSL API function SSL_select_next_proto with an empty supported client protocols buffer may cause a crash or memory contents to be sent to the peer.

Impact summary: A buffer overread can have a range of potential consequences such as unexpected application beahviour or a crash. In particular this issue could result in up to 255 bytes of arbitrary private data from memory being sent to the peer leading to a loss of confidentiality. However, only applications that directly call the SSL_select_next_proto function with a 0 length list of supported client protocols are affected by this issue. This would normally never be a valid scenario and is typically not under attacker control but may occur by accident in the case of a configuration or programming error in the calling application.

The OpenSSL API function SSL_select_next_proto is typically used by TLS applications that support ALPN (Application Layer Protocol Negotiation) or NPN (Next Protocol Negotiation). NPN is older, was never standardised and is deprecated in favour of ALPN. We believe that ALPN is significantly more widely deployed than NPN. The SSL_select_next_proto function accepts a list of protocols from the server and a list of protocols from the client and returns the first protocol that appears in the server list that also appears in the client list. In the case of no overlap between the two lists it returns the first item in the client list. In either case it will signal whether an overlap between the two lists was found. In the case where SSL_select_next_proto is called with a zero length client list it fails to notice this condition and returns the memory immediately following the client list pointer (and reports that there was no overlap in the lists).

This function is typically called from a server side application callback for ALPN or a client side application callback for NPN. In the case of ALPN the list of protocols supplied by the client is guaranteed by libssl to never be zero in length. The list of server protocols comes from the application and should never normally be expected to be of zero length. In this case if the SSL_select_next_proto function has been called as expected (with the list supplied by the client passed in the client/client_len parameters), then the application will not be vulnerable to this issue. If the application has accidentally been configured with a zero length server list, and has accidentally passed that zero length server list in the client/client_len parameters, and has additionally failed to correctly handle a "no overlap" response (which would normally result in a handshake failure in ALPN) then it will be vulnerable to this problem.

In the case of NPN, the protocol permits the client to opportunistically select a protocol when there is no overlap. OpenSSL returns the first client protocol in the no overlap case in support of this. The list of client protocols comes from the application and should never normally be expected to be of zero length. However if the SSL_select_next_proto function is accidentally called with a client_len of 0 then an invalid memory pointer will be returned instead. If the application uses this output as the opportunistic protocol then the loss of confidentiality will occur.

This issue has been assessed as Low severity because applications are most likely to be vulnerable if they are using NPN instead of ALPN - but NPN is not widely used. It also requires an application configuration or programming error. Finally, this issue would not typically be under attacker control making active exploitation unlikely.

The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.

Due to the low severity of this issue we are not issuing new releases of OpenSSL at this time. The fix will be included in the next releases when they become available.

Remediation

Upgrade Debian:unstable openssl to version 3.3.2-1 or higher.

References

CVE-2024-5535 vulnerability report

low severity

CVE-2024-9143

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 3.3.2-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted explicit values for the field polynomial can lead to out-of-bounds memory reads or writes.

Impact summary: Out of bound memory writes can lead to an application crash or even a possibility of a remote code execution, however, in all the protocols involving Elliptic Curve Cryptography that we're aware of, either only "named curves" are supported, or, if explicit curve parameters are supported, they specify an X9.62 encoding of binary (GF(2^m)) curves that can't represent problematic input values. Thus the likelihood of existence of a vulnerable application is low.

In particular, the X9.62 encoding is used for ECC keys in X.509 certificates, so problematic inputs cannot occur in the context of processing X.509 certificates. Any problematic use-cases would have to be using an "exotic" curve encoding.

The affected APIs include: EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(), and various supporting BN_GF2m_*() functions.

Applications working with "exotic" explicit binary (GF(2^m)) curve parameters, that make it possible to represent invalid field polynomials with a zero constant term, via the above or similar APIs, may terminate abruptly as a result of reading or writing outside of array bounds. Remote code execution cannot easily be ruled out.

The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.

Remediation

Upgrade Debian:unstable openssl to version 3.3.2-2 or higher.

References

CVE-2024-9143 vulnerability report

low severity

CVE-2025-27587

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 3.5.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

OpenSSL 3.0.0 through 3.3.2 on the PowerPC architecture is vulnerable to a Minerva attack, exploitable by measuring the time of signing of random messages using the EVP_DigestSign API, and then using the private key to extract the K value (nonce) from the signatures. Next, based on the bit size of the extracted nonce, one can compare the signing time of full-sized nonces to signatures that used smaller nonces, via statistical tests. There is a side-channel in the P-364 curve that allows private key extraction (also, there is a dependency between the bit size of K and the size of the side channel). NOTE: This CVE is disputed because the OpenSSL security policy explicitly notes that any side channels which require same physical system to be detected are outside of the threat model for the software. The timing signal is so small that it is infeasible to be detected without having the attacking process running on the same physical system.

Remediation

Upgrade Debian:unstable openssl to version 3.5.0-1 or higher.

References

CVE-2025-27587 vulnerability report

low severity

CVE-2025-4575

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 3.5.0-2

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Issue summary: Use of -addreject option with the openssl x509 application adds a trusted use instead of a rejected use for a certificate.

Impact summary: If a user intends to make a trusted certificate rejected for a particular use it will be instead marked as trusted for that use.

A copy & paste error during minor refactoring of the code introduced this issue in the OpenSSL 3.5 version. If, for example, a trusted CA certificate should be trusted only for the purpose of authenticating TLS servers but not for CMS signature verification and the CMS signature verification is intended to be marked as rejected with the -addreject option, the resulting CA certificate will be trusted for CMS signature verification purpose instead.

Only users which use the trusted certificate format who use the openssl x509 command line application to add rejected uses are affected by this issue. The issues affecting only the command line application are considered to be Low severity.

The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.

OpenSSL 3.4, 3.3, 3.2, 3.1, 3.0, 1.1.1 and 1.0.2 are also not affected by this issue.

Remediation

Upgrade Debian:unstable openssl to version 3.5.0-2 or higher.

References

CVE-2025-4575 vulnerability report

low severity

CVE-2025-9230

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 3.5.4-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Issue summary: An application trying to decrypt CMS messages encrypted using password based encryption can trigger an out-of-bounds read and write.

Impact summary: This out-of-bounds read may trigger a crash which leads to Denial of Service for an application. The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service or Execution of attacker-supplied code.

Although the consequences of a successful exploit of this vulnerability could be severe, the probability that the attacker would be able to perform it is low. Besides, password based (PWRI) encryption support in CMS messages is very rarely used. For that reason the issue was assessed as Moderate severity according to our Security Policy.

The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as the CMS implementation is outside the OpenSSL FIPS module boundary.

Remediation

Upgrade Debian:unstable openssl to version 3.5.4-1 or higher.

References

CVE-2025-9230 vulnerability report

low severity

CVE-2025-9231

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 3.5.4-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Issue summary: A timing side-channel which could potentially allow remote recovery of the private key exists in the SM2 algorithm implementation on 64 bit ARM platforms.

Impact summary: A timing side-channel in SM2 signature computations on 64 bit ARM platforms could allow recovering the private key by an attacker..

While remote key recovery over a network was not attempted by the reporter, timing measurements revealed a timing signal which may allow such an attack.

OpenSSL does not directly support certificates with SM2 keys in TLS, and so this CVE is not relevant in most TLS contexts. However, given that it is possible to add support for such certificates via a custom provider, coupled with the fact that in such a custom provider context the private key may be recoverable via remote timing measurements, we consider this to be a Moderate severity issue.

The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as SM2 is not an approved algorithm.

Remediation

Upgrade Debian:unstable openssl to version 3.5.4-1 or higher.

References

CVE-2025-9231 vulnerability report

low severity

CVE-2025-9232

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0g-2 and openssl/libssl1.1@1.1.0g-2
  • Fixed in: 3.5.4-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › openssl@1.1.0g-2
  • Introduced through: openjdk@10-ea-jdk › openssl/libssl1.1@1.1.0g-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Issue summary: An application using the OpenSSL HTTP client API functions may trigger an out-of-bounds read if the 'no_proxy' environment variable is set and the host portion of the authority component of the HTTP URL is an IPv6 address.

Impact summary: An out-of-bounds read can trigger a crash which leads to Denial of Service for an application.

The OpenSSL HTTP client API functions can be used directly by applications but they are also used by the OCSP client functions and CMP (Certificate Management Protocol) client implementation in OpenSSL. However the URLs used by these implementations are unlikely to be controlled by an attacker.

In this vulnerable code the out of bounds read can only trigger a crash. Furthermore the vulnerability requires an attacker-controlled URL to be passed from an application to the OpenSSL function and the user has to have a 'no_proxy' environment variable set. For the aforementioned reasons the issue was assessed as Low severity.

The vulnerable code was introduced in the following patch releases: 3.0.16, 3.1.8, 3.2.4, 3.3.3, 3.4.0 and 3.5.0.

The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as the HTTP client implementation is outside the OpenSSL FIPS module boundary.

Remediation

Upgrade Debian:unstable openssl to version 3.5.4-1 or higher.

References

CVE-2025-9232 vulnerability report

low severity

CVE-2025-40909

  • Vulnerable module: perl
  • Introduced through: perl@5.26.1-5, perl/libperl5.26@5.26.1-5 and others
  • Fixed in: 5.40.1-5

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › perl@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/libperl5.26@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-base@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-modules-5.26@5.26.1-5

NVD Description

Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Perl threads have a working directory race condition where file operations may target unintended paths.

If a directory handle is open at thread creation, the process-wide current working directory is temporarily changed in order to clone that handle for the new thread, which is visible from any third (or more) thread already running.

This may lead to unintended operations such as loading code or accessing files from unexpected locations, which a local attacker may be able to exploit.

The bug was introduced in commit 11a11ecf4bea72b17d250cfb43c897be1341861e and released in Perl version 5.13.6

Remediation

Upgrade Debian:unstable perl to version 5.40.1-5 or higher.

References

CVE-2025-40909 vulnerability report

low severity

Out-of-bounds Write

  • Vulnerable module: perl
  • Introduced through: perl@5.26.1-5, perl/libperl5.26@5.26.1-5 and others
  • Fixed in: 5.40.1-3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › perl@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/libperl5.26@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-base@5.26.1-5
  • Introduced through: openjdk@10-ea-jdk › perl/perl-modules-5.26@5.26.1-5

NVD Description

Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A heap buffer overflow vulnerability was discovered in Perl.

Release branches 5.34, 5.36, 5.38 and 5.40 are affected, including development versions from 5.33.1 through 5.41.10.

When there are non-ASCII bytes in the left-hand-side of the tr operator, S_do_trans_invmap can overflow the destination pointer d.

   $ perl -e '$_ = "\x{FF}" x 1000000; tr/\xFF/\x{100}/;'    Segmentation fault (core dumped)

It is believed that this vulnerability can enable Denial of Service and possibly Code Execution attacks on platforms that lack sufficient defenses.

Remediation

Upgrade Debian:unstable perl to version 5.40.1-3 or higher.

References

Out-of-bounds Write vulnerability report

low severity

CVE-2024-56433

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.5-1 and shadow/passwd@1:4.5-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › shadow/login@1:4.5-1
  • Introduced through: openjdk@10-ea-jdk › shadow/passwd@1:4.5-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream shadow package and not the shadow package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

shadow-utils (aka shadow) 4.4 through 4.17.0 establishes a default /etc/subuid behavior (e.g., uid 100000 through 165535 for the first user account) that can realistically conflict with the uids of users defined on locally administered networks, potentially leading to account takeover, e.g., by leveraging newuidmap for access to an NFS home directory (or same-host resources in the case of remote logins by these local network users). NOTE: it may also be argued that system administrators should not have assigned uids, within local networks, that are within the range that can occur in /etc/subuid.

Remediation

There is no fixed version for Debian:unstable shadow.

References

CVE-2024-56433 vulnerability report

low severity

CVE-2025-7709

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1
  • Fixed in: 3.46.1-8

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › sqlite3/libsqlite3-0@3.22.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An integer overflow exists in the FTS5 https://sqlite.org/fts5.html  extension. It occurs when the size of an array of tombstone pointers is calculated and truncated into a 32-bit integer. A pointer to partially controlled data can then be written out of bounds.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.46.1-8 or higher.

References

CVE-2025-7709 vulnerability report

low severity

CVE-2023-39804

  • Vulnerable module: tar
  • Introduced through: tar@1.29b-2
  • Fixed in: 1.34+dfsg-1.3

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › tar@1.29b-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream tar package and not the tar package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In GNU tar before 1.35, mishandled extension attributes in a PAX archive can lead to an application crash in xheader.c.

Remediation

Upgrade Debian:unstable tar to version 1.34+dfsg-1.3 or higher.

References

CVE-2023-39804 vulnerability report

low severity

CVE-2024-28085

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.31.1-0.5, util-linux/fdisk@2.31.1-0.5 and others
  • Fixed in: 2.39.3-11

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › util-linux@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/fdisk@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/libblkid1@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/libfdisk1@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/libmount1@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/libsmartcols1@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/libuuid1@2.31.1-0.5
  • Introduced through: openjdk@10-ea-jdk › util-linux/mount@2.31.1-0.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream util-linux package and not the util-linux package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

wall in util-linux through 2.40, often installed with setgid tty permissions, allows escape sequences to be sent to other users' terminals through argv. (Specifically, escape sequences received from stdin are blocked, but escape sequences received from argv are not blocked.) There may be plausible scenarios where this leads to account takeover.

Remediation

Upgrade Debian:unstable util-linux to version 2.39.3-11 or higher.

References

CVE-2024-28085 vulnerability report

low severity

Server-Side Request Forgery (SSRF)

  • Vulnerable module: wget
  • Introduced through: wget@1.19.4-1
  • Fixed in: 1.25.0-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › wget@1.19.4-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream wget package and not the wget package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Applications that use Wget to access a remote resource using shorthand URLs and pass arbitrary user credentials in the URL are vulnerable. In these cases attackers can enter crafted credentials which will cause Wget to access an arbitrary host.

Remediation

Upgrade Debian:unstable wget to version 1.25.0-1 or higher.

References

Server-Side Request Forgery (SSRF) vulnerability report

low severity

Race Condition

  • Vulnerable module: xz-utils
  • Introduced through: xz-utils@5.2.2-1.3 and xz-utils/liblzma5@5.2.2-1.3
  • Fixed in: 5.8.1-1

Detailed paths

  • Introduced through: openjdk@10-ea-jdk › xz-utils@5.2.2-1.3
  • Introduced through: openjdk@10-ea-jdk › xz-utils/liblzma5@5.2.2-1.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream xz-utils package and not the xz-utils package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

XZ Utils provide a general-purpose data-compression library plus command-line tools. In XZ Utils 5.3.3alpha to 5.8.0, the multithreaded .xz decoder in liblzma has a bug where invalid input can at least result in a crash. The effects include heap use after free and writing to an address based on the null pointer plus an offset. Applications and libraries that use the lzma_stream_decoder_mt function are affected. The bug has been fixed in XZ Utils 5.8.1, and the fix has been committed to the v5.4, v5.6, v5.8, and master branches in the xz Git repository. No new release packages will be made from the old stable branches, but a standalone patch is available that applies to all affected releases.

Remediation

Upgrade Debian:unstable xz-utils to version 5.8.1-1 or higher.

References

Race Condition vulnerability report