Vulnerabilities

206 via 390 paths

Dependencies

143

Source

Group 6 Copy Created with Sketch. Docker

Target OS

debian:11
Test your Docker Hub image against our market leading vulnerability database Sign up for free
Severity
  • 17
  • 41
  • 41
  • 107
Status
  • 206
  • 0
  • 0

critical severity

Exposure of Resource to Wrong Sphere

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
  • Fixed in: 7.74.0-1.3+deb11u5

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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:11 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:11 curl to version 7.74.0-1.3+deb11u5 or higher.

References

critical severity

Incorrect Default Permissions

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
  • Fixed in: 7.74.0-1.3+deb11u2

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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:11 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:11 curl to version 7.74.0-1.3+deb11u2 or higher.

References

critical severity

Out-of-bounds Write

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
  • Fixed in: 7.74.0-1.3+deb11u10

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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:11 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:11 curl to version 7.74.0-1.3+deb11u10 or higher.

References

critical severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: openjdk@11-jre db5.3/libdb5.3@5.3.28+dfsg1-0.8

NVD Description

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

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

Remediation

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

References

critical severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: openjdk@11-jre expat/libexpat1@2.2.10-2+deb11u3

NVD Description

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

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:11 expat to version 2.2.10-2+deb11u6 or higher.

References

critical severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: openjdk@11-jre expat/libexpat1@2.2.10-2+deb11u3

NVD Description

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

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:11 expat to version 2.2.10-2+deb11u6 or higher.

References

critical severity

Integer Overflow or Wraparound

  • Vulnerable module: libksba/libksba8
  • Introduced through: libksba/libksba8@1.5.0-3
  • Fixed in: 1.5.0-3+deb11u1

Detailed paths

  • Introduced through: openjdk@11-jre libksba/libksba8@1.5.0-3

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:11 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:11 libksba to version 1.5.0-3+deb11u1 or higher.

References

critical severity

Integer Overflow or Wraparound

  • Vulnerable module: libksba/libksba8
  • Introduced through: libksba/libksba8@1.5.0-3
  • Fixed in: 1.5.0-3+deb11u2

Detailed paths

  • Introduced through: openjdk@11-jre libksba/libksba8@1.5.0-3

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:11 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:11 libksba to version 1.5.0-3+deb11u2 or higher.

References

critical severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: openjdk@11-jre zlib/zlib1g@1:1.2.11.dfsg-2+deb11u1

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 zlib.

References

critical severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: openjdk@11-jre zlib/zlib1g@1:1.2.11.dfsg-2+deb11u1

NVD Description

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

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

Remediation

Upgrade Debian:11 zlib to version 1:1.2.11.dfsg-2+deb11u2 or higher.

References

critical severity

Cleartext Transmission of Sensitive Information

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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

There is no fixed version for Debian:11 curl.

References

critical severity

Double Free

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
  • Fixed in: 7.74.0-1.3+deb11u2

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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:11 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:11 curl to version 7.74.0-1.3+deb11u2 or higher.

References

critical severity

CVE-2024-37371

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

Detailed paths

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

NVD Description

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

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:11 krb5 to version 1.18.3-6+deb11u5 or higher.

References

critical severity

Off-by-one Error

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

Detailed paths

  • Introduced through: openjdk@11-jre libtasn1-6@4.16.0-2

NVD Description

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

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

Remediation

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

References

critical severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: openjdk@11-jre pcre2/libpcre2-8-0@10.36-2

NVD Description

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

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

Remediation

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

References

critical severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: openjdk@11-jre pcre2/libpcre2-8-0@10.36-2

NVD Description

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

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

Remediation

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

References

critical severity

Interpretation Conflict

  • Vulnerable module: wget
  • Introduced through: wget@1.21-1+deb11u1
  • Fixed in: 1.21-1+deb11u2

Detailed paths

  • Introduced through: openjdk@11-jre wget@1.21-1+deb11u1

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:11 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:11 wget to version 1.21-1+deb11u2 or higher.

References

high severity

Arbitrary Code Injection

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
  • Fixed in: 7.74.0-1.3+deb11u8

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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:11 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:11 curl to version 7.74.0-1.3+deb11u8 or higher.

References

high severity

Directory Traversal

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
  • Fixed in: 7.74.0-1.3+deb11u8

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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:11 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:11 curl to version 7.74.0-1.3+deb11u8 or higher.

References

high severity

Integer Overflow or Wraparound

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

Detailed paths

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

NVD Description

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

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

Remediation

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

References

high severity

Double Free

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

Detailed paths

  • Introduced through: openjdk@11-jre gnutls28/libgnutls30@3.7.1-5+deb11u1

NVD Description

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

A flaw was found in GnuTLS. 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:11 gnutls28 to version 3.7.1-5+deb11u8 or higher.

References

high severity

Heap-based Buffer Overflow

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

Detailed paths

  • Introduced through: openjdk@11-jre gnutls28/libgnutls30@3.7.1-5+deb11u1

NVD Description

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

A 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:11 gnutls28 to version 3.7.1-5+deb11u8 or higher.

References

high severity

Missing Authentication for Critical Function

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
  • Fixed in: 7.74.0-1.3+deb11u2

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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:11 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:11 curl to version 7.74.0-1.3+deb11u2 or higher.

References

high severity

Use After Free

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

Detailed paths

  • Introduced through: openjdk@11-jre expat/libexpat1@2.2.10-2+deb11u3

NVD Description

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

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

Remediation

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

References

high severity

CVE-2025-27363

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

Detailed paths

  • Introduced through: openjdk@11-jre freetype/libfreetype6@2.10.4+dfsg-1+deb11u1

NVD Description

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

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:11 freetype to version 2.10.4+dfsg-1+deb11u2 or higher.

References

high severity

Improper Certificate Validation

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

Detailed paths

  • Introduced through: openjdk@11-jre perl/perl-base@5.32.1-4+deb11u2

NVD Description

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

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

Remediation

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

References

high severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: openjdk@11-jre e2fsprogs@1.46.2-2
  • Introduced through: openjdk@11-jre e2fsprogs/libcom-err2@1.46.2-2
  • Introduced through: openjdk@11-jre e2fsprogs/libext2fs2@1.46.2-2
  • Introduced through: openjdk@11-jre e2fsprogs/libss2@1.46.2-2
  • Introduced through: openjdk@11-jre e2fsprogs/logsave@1.46.2-2

NVD Description

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

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

Remediation

Upgrade Debian:11 e2fsprogs to version 1.46.2-2+deb11u1 or higher.

References

high severity

Off-by-one Error

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

Detailed paths

  • Introduced through: openjdk@11-jre glibc/libc-bin@2.31-13+deb11u3
  • Introduced through: openjdk@11-jre glibc/libc6@2.31-13+deb11u3

NVD Description

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

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

Remediation

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

References

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: openjdk@11-jre glibc/libc-bin@2.31-13+deb11u3
  • Introduced through: openjdk@11-jre glibc/libc6@2.31-13+deb11u3

NVD Description

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

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

Remediation

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

References

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: openjdk@11-jre ncurses/libncursesw6@6.2+20201114-2
  • Introduced through: openjdk@11-jre ncurses/libtinfo6@6.2+20201114-2
  • Introduced through: openjdk@11-jre ncurses/ncurses-base@6.2+20201114-2
  • Introduced through: openjdk@11-jre ncurses/ncurses-bin@6.2+20201114-2

NVD Description

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

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

Remediation

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

References

high severity

Directory Traversal

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

Detailed paths

  • Introduced through: openjdk@11-jre pam/libpam-modules@1.4.0-9+deb11u1
  • Introduced through: openjdk@11-jre pam/libpam-modules-bin@1.4.0-9+deb11u1
  • Introduced through: openjdk@11-jre pam/libpam-runtime@1.4.0-9+deb11u1
  • Introduced through: openjdk@11-jre pam/libpam0g@1.4.0-9+deb11u1

NVD Description

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

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

There is no fixed version for Debian:11 pam.

References

high severity

Improper Verification of Cryptographic Signature

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: openjdk@11-jre perl/perl-base@5.32.1-4+deb11u2

NVD Description

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

A vulnerability was found in perl 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:11 perl to version 5.32.1-4+deb11u3 or higher.

References

high severity

Cleartext Transmission of Sensitive Information

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
  • Fixed in: 7.74.0-1.3+deb11u2

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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:11 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:11 curl to version 7.74.0-1.3+deb11u2 or higher.

References

high severity

Cleartext Transmission of Sensitive Information

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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

There is no fixed version for Debian:11 curl.

References

high severity

Cleartext Transmission of Sensitive Information

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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

There is no fixed version for Debian:11 curl.

References

high severity

CVE-2022-27775

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
  • Fixed in: 7.74.0-1.3+deb11u2

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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:11 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:11 curl to version 7.74.0-1.3+deb11u2 or higher.

References

high severity

Improper Certificate Validation

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
  • Fixed in: 7.74.0-1.3+deb11u2

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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:11 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:11 curl to version 7.74.0-1.3+deb11u2 or higher.

References

high severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
  • Fixed in: 7.74.0-1.3+deb11u2

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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:11 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:11 curl to version 7.74.0-1.3+deb11u2 or higher.

References

high severity

Resource Exhaustion

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

Detailed paths

  • Introduced through: openjdk@11-jre expat/libexpat1@2.2.10-2+deb11u3

NVD Description

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

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

Remediation

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

References

high severity

Use After Free

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

Detailed paths

  • Introduced through: openjdk@11-jre expat/libexpat1@2.2.10-2+deb11u3

NVD Description

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

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

Remediation

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

References

high severity

XML External Entity (XXE) Injection

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

Detailed paths

  • Introduced through: openjdk@11-jre expat/libexpat1@2.2.10-2+deb11u3

NVD Description

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

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

Remediation

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

References

high severity

Double Free

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

Detailed paths

  • Introduced through: openjdk@11-jre gnutls28/libgnutls30@3.7.1-5+deb11u1

NVD Description

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

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

Remediation

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

References

high severity

Improper Verification of Cryptographic Signature

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

Detailed paths

  • Introduced through: openjdk@11-jre gnutls28/libgnutls30@3.7.1-5+deb11u1

NVD Description

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

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

Remediation

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

References

high severity

Information Exposure

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

Detailed paths

  • Introduced through: openjdk@11-jre gnutls28/libgnutls30@3.7.1-5+deb11u1

NVD Description

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

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

Remediation

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

References

high severity

CVE-2024-37370

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

Detailed paths

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

NVD Description

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

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:11 krb5 to version 1.18.3-6+deb11u5 or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: libssh2/libssh2-1
  • Introduced through: libssh2/libssh2-1@1.9.0-2
  • Fixed in: 1.9.0-2+deb11u1

Detailed paths

  • Introduced through: openjdk@11-jre libssh2/libssh2-1@1.9.0-2

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:11 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:11 libssh2 to version 1.9.0-2+deb11u1 or higher.

References

high severity

Improper Handling of Exceptional Conditions

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

Detailed paths

  • Introduced through: openjdk@11-jre libtirpc/libtirpc-common@1.3.1-1
  • Introduced through: openjdk@11-jre libtirpc/libtirpc3@1.3.1-1

NVD Description

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

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

Remediation

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

References

high severity

CVE-2023-44487

  • Vulnerable module: nghttp2/libnghttp2-14
  • Introduced through: nghttp2/libnghttp2-14@1.43.0-1
  • Fixed in: 1.43.0-1+deb11u1

Detailed paths

  • Introduced through: openjdk@11-jre nghttp2/libnghttp2-14@1.43.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:11 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:11 nghttp2 to version 1.43.0-1+deb11u1 or higher.

References

high severity

Double Free

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

Detailed paths

  • Introduced through: openjdk@11-jre openssl@1.1.1n-0+deb11u3
  • Introduced through: openjdk@11-jre openssl/libssl1.1@1.1.1n-0+deb11u3

NVD Description

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

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

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

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

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

Remediation

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

References

high severity

Improper Certificate Validation

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

Detailed paths

  • Introduced through: openjdk@11-jre openssl@1.1.1n-0+deb11u3
  • Introduced through: openjdk@11-jre openssl/libssl1.1@1.1.1n-0+deb11u3

NVD Description

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

A security vulnerability has been identified in all supported versions

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

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

Remediation

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

References

high severity

Use After Free

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

Detailed paths

  • Introduced through: openjdk@11-jre openssl@1.1.1n-0+deb11u3
  • Introduced through: openjdk@11-jre openssl/libssl1.1@1.1.1n-0+deb11u3

NVD Description

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

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

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

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

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

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

Remediation

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

References

high severity

Out-of-bounds Read

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.34.1-3
  • Fixed in: 3.34.1-3+deb11u1

Detailed paths

  • Introduced through: openjdk@11-jre sqlite3/libsqlite3-0@3.34.1-3

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:11 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:11 sqlite3 to version 3.34.1-3+deb11u1 or higher.

References

high severity

Allocation of Resources Without Limits or Throttling

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

Detailed paths

  • Introduced through: openjdk@11-jre systemd/libsystemd0@247.3-7
  • Introduced through: openjdk@11-jre systemd/libudev1@247.3-7

NVD Description

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

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

Remediation

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

References

high severity

Information Exposure

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

Detailed paths

  • Introduced through: openjdk@11-jre gnutls28/libgnutls30@3.7.1-5+deb11u1

NVD Description

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

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

Remediation

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

References

high severity

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

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

Detailed paths

  • Introduced through: openjdk@11-jre openssl@1.1.1n-0+deb11u3
  • Introduced through: openjdk@11-jre openssl/libssl1.1@1.1.1n-0+deb11u3

NVD Description

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

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

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

Remediation

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

References

high severity

Out-of-Bounds

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.34.1-3
  • Fixed in: 3.34.1-3+deb11u1

Detailed paths

  • Introduced through: openjdk@11-jre sqlite3/libsqlite3-0@3.34.1-3

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:11 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:11 sqlite3 to version 3.34.1-3+deb11u1 or higher.

References

high severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: openjdk@11-jre ncurses/libncursesw6@6.2+20201114-2
  • Introduced through: openjdk@11-jre ncurses/libtinfo6@6.2+20201114-2
  • Introduced through: openjdk@11-jre ncurses/ncurses-base@6.2+20201114-2
  • Introduced through: openjdk@11-jre ncurses/ncurses-bin@6.2+20201114-2

NVD Description

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

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

Remediation

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

References

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
  • Fixed in: 7.74.0-1.3+deb11u2

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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:11 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:11 curl to version 7.74.0-1.3+deb11u2 or higher.

References

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
  • Fixed in: 7.74.0-1.3+deb11u7

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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:11 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:11 curl to version 7.74.0-1.3+deb11u7 or higher.

References

medium severity

Cleartext Transmission of Sensitive Information

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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

There is no fixed version for Debian:11 curl.

References

medium severity

CVE-2023-46218

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
  • Fixed in: 7.74.0-1.3+deb11u11

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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:11 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:11 curl to version 7.74.0-1.3+deb11u11 or higher.

References

medium severity

Insufficient Comparison

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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

There is no fixed version for Debian:11 curl.

References

medium severity

Insufficiently Protected Credentials

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
  • Fixed in: 7.74.0-1.3+deb11u2

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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:11 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:11 curl to version 7.74.0-1.3+deb11u2 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
  • Fixed in: 7.74.0-1.3+deb11u13

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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:11 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:11 curl to version 7.74.0-1.3+deb11u13 or higher.

References

medium severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: openjdk@11-jre gnutls28/libgnutls30@3.7.1-5+deb11u1

NVD Description

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

A NULL pointer dereference flaw was found in the GnuTLS software in _gnutls_figure_common_ciphersuite().

Remediation

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

References

medium severity

Access of Uninitialized Pointer

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

Detailed paths

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

NVD Description

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

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

Remediation

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

References

medium severity

Allocation of Resources Without Limits or Throttling

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

Detailed paths

  • Introduced through: openjdk@11-jre openssl@1.1.1n-0+deb11u3
  • Introduced through: openjdk@11-jre openssl/libssl1.1@1.1.1n-0+deb11u3

NVD Description

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

Issue summary: Processing some specially crafted ASN.1 object identifiers or data containing them may be very slow.

Impact summary: Applications that use OBJ_obj2txt() directly, or use any of the OpenSSL subsystems OCSP, PKCS7/SMIME, CMS, CMP/CRMF or TS with no message size limit may experience notable to very long delays when processing those messages, which may lead to a Denial of Service.

An OBJECT IDENTIFIER is composed of a series of numbers - sub-identifiers - most of which have no size limit. OBJ_obj2txt() may be used to translate an ASN.1 OBJECT IDENTIFIER given in DER encoding form (using the OpenSSL type ASN1_OBJECT) to its canonical numeric text form, which are the sub-identifiers of the OBJECT IDENTIFIER in decimal form, separated by periods.

When one of the sub-identifiers in the OBJECT IDENTIFIER is very large (these are sizes that are seen as absurdly large, taking up tens or hundreds of KiBs), the translation to a decimal number in text may take a very long time. The time complexity is O(n^2) with 'n' being the size of the sub-identifiers in bytes (*).

With OpenSSL 3.0, support to fetch cryptographic algorithms using names / identifiers in string form was introduced. This includes using OBJECT IDENTIFIERs in canonical numeric text form as identifiers for fetching algorithms.

Such OBJECT IDENTIFIERs may be received through the ASN.1 structure AlgorithmIdentifier, which is commonly used in multiple protocols to specify what cryptographic algorithm should be used to sign or verify, encrypt or decrypt, or digest passed data.

Applications that call OBJ_obj2txt() directly with untrusted data are affected, with any version of OpenSSL. If the use is for the mere purpose of display, the severity is considered low.

In OpenSSL 3.0 and newer, this affects the subsystems OCSP, PKCS7/SMIME, CMS, CMP/CRMF or TS. It also impacts anything that processes X.509 certificates, including simple things like verifying its signature.

The impact on TLS is relatively low, because all versions of OpenSSL have a 100KiB limit on the peer's certificate chain. Additionally, this only impacts clients, or servers that have explicitly enabled client authentication.

In OpenSSL 1.1.1 and 1.0.2, this only affects displaying diverse objects, such as X.509 certificates. This is assumed to not happen in such a way that it would cause a Denial of Service, so these versions are considered not affected by this issue in such a way that it would be cause for concern, and the severity is therefore considered low.

Remediation

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

References

medium severity

Improper Authentication

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
  • Fixed in: 7.74.0-1.3+deb11u8

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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:11 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:11 curl to version 7.74.0-1.3+deb11u8 or higher.

References

medium severity

Improper Authentication

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
  • Fixed in: 7.74.0-1.3+deb11u8

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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:11 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:11 curl to version 7.74.0-1.3+deb11u8 or higher.

References

medium severity

Improper Certificate Validation

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
  • Fixed in: 7.74.0-1.3+deb11u9

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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:11 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:11 curl to version 7.74.0-1.3+deb11u9 or higher.

References

medium severity

Insufficient Verification of Data Authenticity

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
  • Fixed in: 7.74.0-1.3+deb11u2

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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:11 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:11 curl to version 7.74.0-1.3+deb11u2 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
  • Fixed in: 7.74.0-1.3+deb11u2

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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:11 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:11 curl to version 7.74.0-1.3+deb11u2 or higher.

References

medium severity

Use After Free

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
  • Fixed in: 7.74.0-1.3+deb11u5

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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:11 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:11 curl to version 7.74.0-1.3+deb11u5 or higher.

References

medium severity

Use After Free

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

Detailed paths

  • Introduced through: openjdk@11-jre glibc/libc-bin@2.31-13+deb11u3
  • Introduced through: openjdk@11-jre glibc/libc6@2.31-13+deb11u3

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 glibc.

References

medium severity

Information Exposure

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

Detailed paths

  • Introduced through: openjdk@11-jre gnutls28/libgnutls30@3.7.1-5+deb11u1

NVD Description

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

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

Remediation

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

References

medium severity

Reversible One-Way Hash

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

Detailed paths

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

NVD Description

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

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:11 krb5 to version 1.18.3-6+deb11u7 or higher.

References

medium severity

Information Exposure

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

Detailed paths

  • Introduced through: openjdk@11-jre openssl@1.1.1n-0+deb11u3
  • Introduced through: openjdk@11-jre openssl/libssl1.1@1.1.1n-0+deb11u3

NVD Description

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

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

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

Remediation

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

References

medium severity

CVE-2023-7008

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

Detailed paths

  • Introduced through: openjdk@11-jre systemd/libsystemd0@247.3-7
  • Introduced through: openjdk@11-jre systemd/libudev1@247.3-7

NVD Description

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

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

Remediation

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

References

medium severity

Insufficiently Protected Credentials

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
  • Fixed in: 7.74.0-1.3+deb11u2

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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:11 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:11 curl to version 7.74.0-1.3+deb11u2 or higher.

References

medium severity

Improper Authentication

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
  • Fixed in: 7.74.0-1.3+deb11u8

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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:11 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:11 curl to version 7.74.0-1.3+deb11u8 or higher.

References

medium severity

CVE-2024-0727

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

Detailed paths

  • Introduced through: openjdk@11-jre openssl@1.1.1n-0+deb11u3
  • Introduced through: openjdk@11-jre openssl/libssl1.1@1.1.1n-0+deb11u3

NVD Description

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

Issue summary: Processing a maliciously formatted PKCS12 file may lead OpenSSL to crash leading to a potential Denial of Service attack

Impact summary: Applications loading files in the PKCS12 format from untrusted sources might terminate abruptly.

A file in PKCS12 format can contain certificates and keys and may come from an untrusted source. The PKCS12 specification allows certain fields to be NULL, but OpenSSL does not correctly check for this case. This can lead to a NULL pointer dereference that results in OpenSSL crashing. If an application processes PKCS12 files from an untrusted source using the OpenSSL APIs then that application will be vulnerable to this issue.

OpenSSL APIs that are vulnerable to this are: PKCS12_parse(), PKCS12_unpack_p7data(), PKCS12_unpack_p7encdata(), PKCS12_unpack_authsafes() and PKCS12_newpass().

We have also fixed a similar issue in SMIME_write_PKCS7(). However since this function is related to writing data we do not consider it security significant.

The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue.

Remediation

Upgrade Debian:11 openssl to version 1.1.1w-0+deb11u2 or higher.

References

medium severity

Improper Authentication

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.8.1-1 and shadow/passwd@1:4.8.1-1
  • Fixed in: 1:4.8.1-1+deb11u1

Detailed paths

  • Introduced through: openjdk@11-jre shadow/login@1:4.8.1-1
  • Introduced through: openjdk@11-jre shadow/passwd@1:4.8.1-1

NVD Description

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

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

Remediation

Upgrade Debian:11 shadow to version 1:4.8.1-1+deb11u1 or higher.

References

medium severity

CVE-2022-4415

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

Detailed paths

  • Introduced through: openjdk@11-jre systemd/libsystemd0@247.3-7
  • Introduced through: openjdk@11-jre systemd/libudev1@247.3-7

NVD Description

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

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

Remediation

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

References

medium severity

Off-by-one Error

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

Detailed paths

  • Introduced through: openjdk@11-jre systemd/libsystemd0@247.3-7
  • Introduced through: openjdk@11-jre systemd/libudev1@247.3-7

NVD Description

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

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

Remediation

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

References

medium severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: openjdk@11-jre tar@1.34+dfsg-1

NVD Description

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

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

Remediation

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

References

medium severity

CVE-2022-0530

  • Vulnerable module: unzip
  • Introduced through: unzip@6.0-26
  • Fixed in: 6.0-26+deb11u1

Detailed paths

  • Introduced through: openjdk@11-jre unzip@6.0-26

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:11 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:11 unzip to version 6.0-26+deb11u1 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: unzip
  • Introduced through: unzip@6.0-26
  • Fixed in: 6.0-26+deb11u1

Detailed paths

  • Introduced through: openjdk@11-jre unzip@6.0-26

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:11 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:11 unzip to version 6.0-26+deb11u1 or higher.

References

medium severity

Missing Encryption of Sensitive Data

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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

There is no fixed version for Debian:11 curl.

References

medium severity

Algorithmic Complexity

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

Detailed paths

  • Introduced through: openjdk@11-jre gnutls28/libgnutls30@3.7.1-5+deb11u1

NVD Description

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

A flaw was found in GnuTLS, 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:11 gnutls28 to version 3.7.1-5+deb11u7 or higher.

References

medium severity

Algorithmic Complexity

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

Detailed paths

  • Introduced through: openjdk@11-jre libtasn1-6@4.16.0-2

NVD Description

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

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:11 libtasn1-6 to version 4.16.0-2+deb11u2 or higher.

References

medium severity

Excessive Iteration

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

Detailed paths

  • Introduced through: openjdk@11-jre openssl@1.1.1n-0+deb11u3
  • Introduced through: openjdk@11-jre openssl/libssl1.1@1.1.1n-0+deb11u3

NVD Description

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

Issue summary: Checking excessively long DH keys or parameters may be very slow.

Impact summary: Applications that use the functions DH_check(), DH_check_ex() or EVP_PKEY_param_check() to check a DH key or DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service.

The function DH_check() performs various checks on DH parameters. After fixing CVE-2023-3446 it was discovered that a large q parameter value can also trigger an overly long computation during some of these checks. A correct q value, if present, cannot be larger than the modulus p parameter, thus it is unnecessary to perform these checks if q is larger than p.

An application that calls DH_check() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack.

The function DH_check() is itself called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_ex() and EVP_PKEY_param_check().

Also vulnerable are the OpenSSL dhparam and pkeyparam command line applications when using the "-check" option.

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

The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.

Remediation

Upgrade Debian:11 openssl to version 1.1.1v-0~deb11u1 or higher.

References

medium severity

Improper Certificate Validation

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

Detailed paths

  • Introduced through: openjdk@11-jre openssl@1.1.1n-0+deb11u3
  • Introduced through: openjdk@11-jre openssl/libssl1.1@1.1.1n-0+deb11u3

NVD Description

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

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

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

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

Remediation

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

References

medium severity

Improper Certificate Validation

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

Detailed paths

  • Introduced through: openjdk@11-jre openssl@1.1.1n-0+deb11u3
  • Introduced through: openjdk@11-jre openssl/libssl1.1@1.1.1n-0+deb11u3

NVD Description

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

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

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

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

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

Remediation

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

References

medium severity

Improper Check for Unusual or Exceptional Conditions

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

Detailed paths

  • Introduced through: openjdk@11-jre openssl@1.1.1n-0+deb11u3
  • Introduced through: openjdk@11-jre openssl/libssl1.1@1.1.1n-0+deb11u3

NVD Description

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

Issue summary: Generating excessively long X9.42 DH keys or checking excessively long X9.42 DH keys or parameters may be very slow.

Impact summary: Applications that use the functions DH_generate_key() to generate an X9.42 DH key may experience long delays. Likewise, applications that use DH_check_pub_key(), DH_check_pub_key_ex() or EVP_PKEY_public_check() to check an X9.42 DH key or X9.42 DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service.

While DH_check() performs all the necessary checks (as of CVE-2023-3817), DH_check_pub_key() doesn't make any of these checks, and is therefore vulnerable for excessively large P and Q parameters.

Likewise, while DH_generate_key() performs a check for an excessively large P, it doesn't check for an excessively large Q.

An application that calls DH_generate_key() or DH_check_pub_key() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack.

DH_generate_key() and DH_check_pub_key() are also called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_pub_key_ex(), EVP_PKEY_public_check(), and EVP_PKEY_generate().

Also vulnerable are the OpenSSL pkey command line application when using the "-pubcheck" option, as well as the OpenSSL genpkey command line application.

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

The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.

Remediation

Upgrade Debian:11 openssl to version 1.1.1w-0+deb11u2 or higher.

References

medium severity

Inefficient Regular Expression Complexity

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

Detailed paths

  • Introduced through: openjdk@11-jre openssl@1.1.1n-0+deb11u3
  • Introduced through: openjdk@11-jre openssl/libssl1.1@1.1.1n-0+deb11u3

NVD Description

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

Issue summary: Checking excessively long DH keys or parameters may be very slow.

Impact summary: Applications that use the functions DH_check(), DH_check_ex() or EVP_PKEY_param_check() to check a DH key or DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service.

The function DH_check() performs various checks on DH parameters. One of those checks confirms that the modulus ('p' parameter) is not too large. Trying to use a very large modulus is slow and OpenSSL will not normally use a modulus which is over 10,000 bits in length.

However the DH_check() function checks numerous aspects of the key or parameters that have been supplied. Some of those checks use the supplied modulus value even if it has already been found to be too large.

An application that calls DH_check() and supplies a key or parameters obtained from an untrusted source could be vulernable to a Denial of Service attack.

The function DH_check() is itself called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_ex() and EVP_PKEY_param_check().

Also vulnerable are the OpenSSL dhparam and pkeyparam command line applications when using the '-check' option.

The OpenSSL SSL/TLS implementation is not affected by this issue. The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.

Remediation

Upgrade Debian:11 openssl to version 1.1.1v-0~deb11u1 or higher.

References

medium severity

Use of a Broken or Risky Cryptographic Algorithm

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

Detailed paths

  • Introduced through: openjdk@11-jre openssl@1.1.1n-0+deb11u3
  • Introduced through: openjdk@11-jre openssl/libssl1.1@1.1.1n-0+deb11u3

NVD Description

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

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

Remediation

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

References

medium severity

Race Condition

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

Detailed paths

  • Introduced through: openjdk@11-jre systemd/libsystemd0@247.3-7
  • Introduced through: openjdk@11-jre systemd/libudev1@247.3-7

NVD Description

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

A vulnerability was found in systemd-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:11 systemd to version 247.3-7+deb11u7 or higher.

References

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
  • Fixed in: 7.74.0-1.3+deb11u2

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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:11 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:11 curl to version 7.74.0-1.3+deb11u2 or higher.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: openjdk@11-jre glibc/libc-bin@2.31-13+deb11u3
  • Introduced through: openjdk@11-jre glibc/libc6@2.31-13+deb11u3

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 glibc.

References

low severity

CVE-2025-6965

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.34.1-3

Detailed paths

  • Introduced through: openjdk@11-jre sqlite3/libsqlite3-0@3.34.1-3

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

There is no fixed version for Debian:11 sqlite3.

References

low severity

CVE-2005-2541

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

Detailed paths

  • Introduced through: openjdk@11-jre tar@1.34+dfsg-1

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 tar.

References

low severity

CVE-2019-1010023

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

Detailed paths

  • Introduced through: openjdk@11-jre glibc/libc-bin@2.31-13+deb11u3
  • Introduced through: openjdk@11-jre glibc/libc6@2.31-13+deb11u3

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 glibc.

References

low severity

Improper Certificate Validation

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

Detailed paths

  • Introduced through: openjdk@11-jre perl/perl-base@5.32.1-4+deb11u2

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 perl.

References

low severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: openjdk@11-jre bash@5.1-2+deb11u1

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 bash.

References

low severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: openjdk@11-jre freetype/libfreetype6@2.10.4+dfsg-1+deb11u1

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 freetype.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: openjdk@11-jre pcre3/libpcre3@2:8.39-13

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 pcre3.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: openjdk@11-jre pcre3/libpcre3@2:8.39-13

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 pcre3.

References

low severity

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

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

Detailed paths

  • Introduced through: openjdk@11-jre expat/libexpat1@2.2.10-2+deb11u3

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 expat.

References

low severity

Uncontrolled Recursion

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

Detailed paths

  • Introduced through: openjdk@11-jre expat/libexpat1@2.2.10-2+deb11u3

NVD Description

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

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

There is no fixed version for Debian:11 expat.

References

low severity

Uncontrolled Recursion

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

Detailed paths

  • Introduced through: openjdk@11-jre glibc/libc-bin@2.31-13+deb11u3
  • Introduced through: openjdk@11-jre glibc/libc6@2.31-13+deb11u3

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 glibc.

References

low severity

Uncontrolled Recursion

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

Detailed paths

  • Introduced through: openjdk@11-jre glibc/libc-bin@2.31-13+deb11u3
  • Introduced through: openjdk@11-jre glibc/libc6@2.31-13+deb11u3

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 glibc.

References

low severity

Integer Overflow or Wraparound

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

Detailed paths

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

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 krb5.

References

low severity

Information Exposure

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

Detailed paths

  • Introduced through: openjdk@11-jre libgcrypt20@1.8.7-6

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 libgcrypt20.

References

low severity

Use of a Broken or Risky Cryptographic Algorithm

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

Detailed paths

  • Introduced through: openjdk@11-jre libgcrypt20@1.8.7-6

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 libgcrypt20.

References

low severity

Resource Exhaustion

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

low severity

Cryptographic Issues

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.57+dfsg-3+deb11u1

Detailed paths

  • Introduced through: openjdk@11-jre openldap/libldap-2.4-2@2.4.57+dfsg-3+deb11u1

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:11 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:11 openldap.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.57+dfsg-3+deb11u1

Detailed paths

  • Introduced through: openjdk@11-jre openldap/libldap-2.4-2@2.4.57+dfsg-3+deb11u1

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

A vulnerability was found in openldap. This security flaw causes a null pointer dereference in ber_memalloc_x() function.

Remediation

There is no fixed version for Debian:11 openldap.

References

low severity

Out-of-Bounds

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.57+dfsg-3+deb11u1

Detailed paths

  • Introduced through: openjdk@11-jre openldap/libldap-2.4-2@2.4.57+dfsg-3+deb11u1

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:11 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:11 openldap.

References

low severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: openjdk@11-jre pcre2/libpcre2-8-0@10.36-2

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 pcre2.

References

low severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: openjdk@11-jre pcre3/libpcre3@2:8.39-13

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 pcre3.

References

low severity

Uncontrolled Recursion

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

Detailed paths

  • Introduced through: openjdk@11-jre pcre3/libpcre3@2:8.39-13

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 pcre3.

References

low severity

Improper Validation of Array Index

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.34.1-3

Detailed paths

  • Introduced through: openjdk@11-jre sqlite3/libsqlite3-0@3.34.1-3

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

There is no fixed version for Debian:11 sqlite3.

References

low severity

Improper Input Validation

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

Detailed paths

  • Introduced through: openjdk@11-jre coreutils/coreutils@8.32-4+b1

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 coreutils.

References

low severity

Improper Validation of Integrity Check Value

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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

When curl is instructed to download content using the metalink feature, thecontents is verified against a hash provided in the metalink XML file.The metalink XML file points out to the client how to get the same contentfrom a set of different URLs, potentially hosted by different servers and theclient can then download the file from one or several of them. In a serial orparallel manner.If one of the servers hosting the contents has been breached and the contentsof the specific file on that server is replaced with a modified payload, curlshould detect this when the hash of the file mismatches after a completeddownload. It should remove the contents and instead try getting the contentsfrom another URL. This is not done, and instead such a hash mismatch is onlymentioned in text and the potentially malicious content is kept in the file ondisk.

Remediation

There is no fixed version for Debian:11 curl.

References

low severity

Memory Leak

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

Detailed paths

  • Introduced through: openjdk@11-jre libpng1.6/libpng16-16@1.6.37-3

NVD Description

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

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

Remediation

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

References

low severity

CVE-2023-50495

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

Detailed paths

  • Introduced through: openjdk@11-jre ncurses/libncursesw6@6.2+20201114-2
  • Introduced through: openjdk@11-jre ncurses/libtinfo6@6.2+20201114-2
  • Introduced through: openjdk@11-jre ncurses/ncurses-base@6.2+20201114-2
  • Introduced through: openjdk@11-jre ncurses/ncurses-bin@6.2+20201114-2

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 ncurses.

References

low severity

XML External Entity (XXE) Injection

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

Detailed paths

  • Introduced through: openjdk@11-jre expat/libexpat1@2.2.10-2+deb11u3

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 expat.

References

low severity

Access Restriction Bypass

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

Detailed paths

  • Introduced through: openjdk@11-jre shadow/login@1:4.8.1-1
  • Introduced through: openjdk@11-jre shadow/passwd@1:4.8.1-1

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 shadow.

References

low severity

Authentication Bypass

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

Detailed paths

  • Introduced through: openjdk@11-jre systemd/libsystemd0@247.3-7
  • Introduced through: openjdk@11-jre systemd/libudev1@247.3-7

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 systemd.

References

low severity

Open Redirect

  • Vulnerable module: wget
  • Introduced through: wget@1.21-1+deb11u1

Detailed paths

  • Introduced through: openjdk@11-jre wget@1.21-1+deb11u1

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:11 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:11 wget.

References

low severity

Race Condition

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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

A denial of service vulnerability exists in curl <v8.1.0 in the way libcurl provides several different backends for resolving host names, selected at build time. If it is built to use the synchronous resolver, it allows name resolves to time-out slow operations using alarm() and siglongjmp(). When doing this, libcurl used a global buffer that was not mutex protected and a multi-threaded application might therefore crash or otherwise misbehave.

Remediation

There is no fixed version for Debian:11 curl.

References

low severity

Use After Free

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

Detailed paths

  • Introduced through: openjdk@11-jre glibc/libc-bin@2.31-13+deb11u3
  • Introduced through: openjdk@11-jre glibc/libc6@2.31-13+deb11u3

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 glibc.

References

low severity

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

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

Detailed paths

  • Introduced through: openjdk@11-jre expat/libexpat1@2.2.10-2+deb11u3

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 expat.

References

low severity

Buffer Overflow

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

Detailed paths

  • Introduced through: openjdk@11-jre libpng1.6/libpng16-16@1.6.37-3

NVD Description

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

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

Remediation

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

References

low severity

CVE-2024-22365

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

Detailed paths

  • Introduced through: openjdk@11-jre pam/libpam-modules@1.4.0-9+deb11u1
  • Introduced through: openjdk@11-jre pam/libpam-modules-bin@1.4.0-9+deb11u1
  • Introduced through: openjdk@11-jre pam/libpam-runtime@1.4.0-9+deb11u1
  • Introduced through: openjdk@11-jre pam/libpam0g@1.4.0-9+deb11u1

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 pam.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: openjdk@11-jre pcre3/libpcre3@2:8.39-13

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 pcre3.

References

low severity

Information Exposure

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

Detailed paths

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

NVD Description

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

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

Remediation

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

References

low severity

Insufficiently Protected Credentials

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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

When curl is instructed to get content using the metalink feature, and a user name and password are used to download the metalink XML file, those same credentials are then subsequently passed on to each of the servers from which curl will download or try to download the contents from. Often contrary to the user's expectations and intentions and without telling the user it happened.

Remediation

There is no fixed version for Debian:11 curl.

References

low severity

Information Exposure

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

Detailed paths

  • Introduced through: openjdk@11-jre glibc/libc-bin@2.31-13+deb11u3
  • Introduced through: openjdk@11-jre glibc/libc6@2.31-13+deb11u3

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 glibc.

References

low severity

Use of Insufficiently Random Values

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

Detailed paths

  • Introduced through: openjdk@11-jre glibc/libc-bin@2.31-13+deb11u3
  • Introduced through: openjdk@11-jre glibc/libc6@2.31-13+deb11u3

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 glibc.

References

low severity

Improper Validation of Integrity Check Value

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

Detailed paths

  • Introduced through: openjdk@11-jre systemd/libsystemd0@247.3-7
  • Introduced through: openjdk@11-jre systemd/libudev1@247.3-7

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 systemd.

References

low severity

Improper Validation of Integrity Check Value

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

Detailed paths

  • Introduced through: openjdk@11-jre systemd/libsystemd0@247.3-7
  • Introduced through: openjdk@11-jre systemd/libudev1@247.3-7

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 systemd.

References

low severity

Improper Validation of Integrity Check Value

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

Detailed paths

  • Introduced through: openjdk@11-jre systemd/libsystemd0@247.3-7
  • Introduced through: openjdk@11-jre systemd/libudev1@247.3-7

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 systemd.

References

low severity

CVE-2023-4039

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

Detailed paths

  • Introduced through: openjdk@11-jre gcc-10/gcc-10-base@10.2.1-6
  • Introduced through: openjdk@11-jre gcc-10/libgcc-s1@10.2.1-6
  • Introduced through: openjdk@11-jre gcc-10/libstdc++6@10.2.1-6

NVD Description

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

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

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

Remediation

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

References

low severity

CVE-2023-4039

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

Detailed paths

  • Introduced through: openjdk@11-jre gcc-9/gcc-9-base@9.3.0-22

NVD Description

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

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

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

Remediation

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

References

low severity

Race Condition

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

Detailed paths

  • Introduced through: openjdk@11-jre coreutils/coreutils@8.32-4+b1

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 coreutils.

References

low severity

Improper Initialization

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.57+dfsg-3+deb11u1

Detailed paths

  • Introduced through: openjdk@11-jre openldap/libldap-2.4-2@2.4.57+dfsg-3+deb11u1

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:11 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:11 openldap.

References

low severity

Insecure Storage of Sensitive Information

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

Detailed paths

  • Introduced through: openjdk@11-jre pam/libpam-modules@1.4.0-9+deb11u1
  • Introduced through: openjdk@11-jre pam/libpam-modules-bin@1.4.0-9+deb11u1
  • Introduced through: openjdk@11-jre pam/libpam-runtime@1.4.0-9+deb11u1
  • Introduced through: openjdk@11-jre pam/libpam0g@1.4.0-9+deb11u1

NVD Description

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

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

There is no fixed version for Debian:11 pam.

References

low severity

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

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

Detailed paths

  • Introduced through: openjdk@11-jre shadow/login@1:4.8.1-1
  • Introduced through: openjdk@11-jre shadow/passwd@1:4.8.1-1

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 shadow.

References

low severity

Stack-based Buffer Overflow

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

Detailed paths

  • Introduced through: openjdk@11-jre coreutils/coreutils@8.32-4+b1

NVD Description

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

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:11 coreutils.

References

low severity

Link Following

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

Detailed paths

  • Introduced through: openjdk@11-jre systemd/libsystemd0@247.3-7
  • Introduced through: openjdk@11-jre systemd/libudev1@247.3-7

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 systemd.

References

low severity

Resource Management Errors

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

Detailed paths

  • Introduced through: openjdk@11-jre glibc/libc-bin@2.31-13+deb11u3
  • Introduced through: openjdk@11-jre glibc/libc6@2.31-13+deb11u3

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 glibc.

References

low severity

Improper Input Validation

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

Detailed paths

  • Introduced through: openjdk@11-jre gnutls28/libgnutls30@3.7.1-5+deb11u1

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 gnutls28.

References

low severity

Memory Leak

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.34.1-3

Detailed paths

  • Introduced through: openjdk@11-jre sqlite3/libsqlite3-0@3.34.1-3

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:11 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:11 sqlite3.

References

low severity

Improper Certificate Validation

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.57+dfsg-3+deb11u1

Detailed paths

  • Introduced through: openjdk@11-jre openldap/libldap-2.4-2@2.4.57+dfsg-3+deb11u1

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:11 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:11 openldap.

References

low severity

Improper Verification of Cryptographic Signature

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

Detailed paths

  • Introduced through: openjdk@11-jre apt@2.2.4
  • Introduced through: openjdk@11-jre apt/libapt-pkg6.0@2.2.4

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 apt.

References

low severity

CVE-2022-35252

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
  • Fixed in: 7.74.0-1.3+deb11u3

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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:11 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:11 curl to version 7.74.0-1.3+deb11u3 or higher.

References

low severity

CVE-2023-28322

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
  • Fixed in: 7.74.0-1.3+deb11u9

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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:11 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:11 curl to version 7.74.0-1.3+deb11u9 or higher.

References

low severity

CVE-2023-38546

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
  • Fixed in: 7.74.0-1.3+deb11u10

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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:11 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:11 curl to version 7.74.0-1.3+deb11u10 or higher.

References

low severity

Use of Incorrectly-Resolved Name or Reference

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
  • Fixed in: 7.74.0-1.3+deb11u2

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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:11 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:11 curl to version 7.74.0-1.3+deb11u2 or higher.

References

low severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: openjdk@11-jre gnupg2/dirmngr@2.2.27-2+deb11u2
  • Introduced through: openjdk@11-jre gnupg2/gnupg@2.2.27-2+deb11u2
  • Introduced through: openjdk@11-jre gnupg2/gnupg-l10n@2.2.27-2+deb11u2
  • Introduced through: openjdk@11-jre gnupg2/gnupg-utils@2.2.27-2+deb11u2
  • Introduced through: openjdk@11-jre gnupg2/gpg@2.2.27-2+deb11u2
  • Introduced through: openjdk@11-jre gnupg2/gpg-agent@2.2.27-2+deb11u2
  • Introduced through: openjdk@11-jre gnupg2/gpg-wks-client@2.2.27-2+deb11u2
  • Introduced through: openjdk@11-jre gnupg2/gpg-wks-server@2.2.27-2+deb11u2
  • Introduced through: openjdk@11-jre gnupg2/gpgconf@2.2.27-2+deb11u2
  • Introduced through: openjdk@11-jre gnupg2/gpgsm@2.2.27-2+deb11u2
  • Introduced through: openjdk@11-jre gnupg2/gpgv@2.2.27-2+deb11u2

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 gnupg2.

References

low severity

Out-of-bounds Read

  • Vulnerable module: libsepol/libsepol1
  • Introduced through: libsepol/libsepol1@3.1-1
  • Fixed in: 3.1-1+deb11u1

Detailed paths

  • Introduced through: openjdk@11-jre libsepol/libsepol1@3.1-1

NVD Description

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

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

Remediation

Upgrade Debian:11 libsepol to version 3.1-1+deb11u1 or higher.

References

low severity

Use After Free

  • Vulnerable module: libsepol/libsepol1
  • Introduced through: libsepol/libsepol1@3.1-1
  • Fixed in: 3.1-1+deb11u1

Detailed paths

  • Introduced through: openjdk@11-jre libsepol/libsepol1@3.1-1

NVD Description

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

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

Remediation

Upgrade Debian:11 libsepol to version 3.1-1+deb11u1 or higher.

References

low severity

Use After Free

  • Vulnerable module: libsepol/libsepol1
  • Introduced through: libsepol/libsepol1@3.1-1
  • Fixed in: 3.1-1+deb11u1

Detailed paths

  • Introduced through: openjdk@11-jre libsepol/libsepol1@3.1-1

NVD Description

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

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

Remediation

Upgrade Debian:11 libsepol to version 3.1-1+deb11u1 or higher.

References

low severity

Use After Free

  • Vulnerable module: libsepol/libsepol1
  • Introduced through: libsepol/libsepol1@3.1-1
  • Fixed in: 3.1-1+deb11u1

Detailed paths

  • Introduced through: openjdk@11-jre libsepol/libsepol1@3.1-1

NVD Description

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

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

Remediation

Upgrade Debian:11 libsepol to version 3.1-1+deb11u1 or higher.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: openjdk@11-jre ncurses/libncursesw6@6.2+20201114-2
  • Introduced through: openjdk@11-jre ncurses/libtinfo6@6.2+20201114-2
  • Introduced through: openjdk@11-jre ncurses/ncurses-base@6.2+20201114-2
  • Introduced through: openjdk@11-jre ncurses/ncurses-bin@6.2+20201114-2

NVD Description

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

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

There is no fixed version for Debian:11 ncurses.

References

low severity

Link Following

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

Detailed paths

  • Introduced through: openjdk@11-jre perl/perl-base@5.32.1-4+deb11u2

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 perl.

References

low severity

Arbitrary Code Injection

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.8.1-1 and shadow/passwd@1:4.8.1-1
  • Fixed in: 1:4.8.1-1+deb11u1

Detailed paths

  • Introduced through: openjdk@11-jre shadow/login@1:4.8.1-1
  • Introduced through: openjdk@11-jre shadow/passwd@1:4.8.1-1

NVD Description

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

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

Remediation

Upgrade Debian:11 shadow to version 1:4.8.1-1+deb11u1 or higher.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: unzip
  • Introduced through: unzip@6.0-26

Detailed paths

  • Introduced through: openjdk@11-jre unzip@6.0-26

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:11 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:11 unzip.

References

low severity

Missing Initialization of Resource

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
  • Fixed in: 7.74.0-1.3+deb11u2

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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:11 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:11 curl to version 7.74.0-1.3+deb11u2 or higher.

References

low severity

Buffer Overflow

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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

There is no fixed version for Debian:11 curl.

References

low severity

CVE-2024-8096

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
  • Fixed in: 7.74.0-1.3+deb11u14

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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:11 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:11 curl to version 7.74.0-1.3+deb11u14 or higher.

References

low severity

Improper Certificate Validation

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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

libcurl skips the certificate verification for a QUIC connection under certain conditions, when built to use wolfSSL. If told to use an unknown/bad cipher or curve, the error path accidentally skips the verification and returns OK, thus ignoring any certificate problems.

Remediation

There is no fixed version for Debian:11 curl.

References

low severity

Missing Release of Resource after Effective Lifetime

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
  • Fixed in: 7.74.0-1.3+deb11u12

Detailed paths

  • Introduced through: openjdk@11-jre curl@7.74.0-1.3+deb11u1
  • Introduced through: openjdk@11-jre curl/libcurl4@7.74.0-1.3+deb11u1

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:11 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:11 curl to version 7.74.0-1.3+deb11u12 or higher.

References

low severity

CVE-2025-6297

  • Vulnerable module: dpkg
  • Introduced through: dpkg@1.20.11

Detailed paths

  • Introduced through: openjdk@11-jre dpkg@1.20.11

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

There is no fixed version for Debian:11 dpkg.

References

low severity

CVE-2024-50602

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

Detailed paths

  • Introduced through: openjdk@11-jre expat/libexpat1@2.2.10-2+deb11u3

NVD Description

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

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:11 expat to version 2.2.10-2+deb11u7 or higher.

References

low severity

CVE-2024-2961

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
  • Fixed in: 2.31-13+deb11u9

Detailed paths

  • Introduced through: openjdk@11-jre glibc/libc-bin@2.31-13+deb11u3
  • Introduced through: openjdk@11-jre glibc/libc6@2.31-13+deb11u3

NVD Description

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

The 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:11 glibc to version 2.31-13+deb11u9 or higher.

References

low severity

CVE-2024-33599

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
  • Fixed in: 2.31-13+deb11u10

Detailed paths

  • Introduced through: openjdk@11-jre glibc/libc-bin@2.31-13+deb11u3
  • Introduced through: openjdk@11-jre glibc/libc6@2.31-13+deb11u3

NVD Description

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

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:11 glibc to version 2.31-13+deb11u10 or higher.

References

low severity

CVE-2024-33600

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
  • Fixed in: 2.31-13+deb11u10

Detailed paths

  • Introduced through: openjdk@11-jre glibc/libc-bin@2.31-13+deb11u3
  • Introduced through: openjdk@11-jre glibc/libc6@2.31-13+deb11u3

NVD Description

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

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:11 glibc to version 2.31-13+deb11u10 or higher.

References

low severity

CVE-2024-33601

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
  • Fixed in: 2.31-13+deb11u10

Detailed paths

  • Introduced through: openjdk@11-jre glibc/libc-bin@2.31-13+deb11u3
  • Introduced through: openjdk@11-jre glibc/libc6@2.31-13+deb11u3

NVD Description

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

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:11 glibc to version 2.31-13+deb11u10 or higher.

References

low severity

CVE-2024-33602

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
  • Fixed in: 2.31-13+deb11u10

Detailed paths

  • Introduced through: openjdk@11-jre glibc/libc-bin@2.31-13+deb11u3
  • Introduced through: openjdk@11-jre glibc/libc6@2.31-13+deb11u3

NVD Description

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

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:11 glibc to version 2.31-13+deb11u10 or higher.

References

low severity

CVE-2025-0395

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
  • Fixed in: 2.31-13+deb11u12

Detailed paths

  • Introduced through: openjdk@11-jre glibc/libc-bin@2.31-13+deb11u3
  • Introduced through: openjdk@11-jre glibc/libc6@2.31-13+deb11u3

NVD Description

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

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:11 glibc to version 2.31-13+deb11u12 or higher.

References

low severity

CVE-2025-4802

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
  • Fixed in: 2.31-13+deb11u13

Detailed paths

  • Introduced through: openjdk@11-jre glibc/libc-bin@2.31-13+deb11u3
  • Introduced through: openjdk@11-jre glibc/libc6@2.31-13+deb11u3

NVD Description

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

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:11 glibc to version 2.31-13+deb11u13 or higher.

References

low severity

CVE-2025-8058

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

Detailed paths

  • Introduced through: openjdk@11-jre glibc/libc-bin@2.31-13+deb11u3
  • Introduced through: openjdk@11-jre glibc/libc6@2.31-13+deb11u3

NVD Description

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

The 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

There is no fixed version for Debian:11 glibc.

References

low severity

CVE-2025-30258

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

Detailed paths

  • Introduced through: openjdk@11-jre gnupg2/dirmngr@2.2.27-2+deb11u2
  • Introduced through: openjdk@11-jre gnupg2/gnupg@2.2.27-2+deb11u2
  • Introduced through: openjdk@11-jre gnupg2/gnupg-l10n@2.2.27-2+deb11u2
  • Introduced through: openjdk@11-jre gnupg2/gnupg-utils@2.2.27-2+deb11u2
  • Introduced through: openjdk@11-jre gnupg2/gpg@2.2.27-2+deb11u2
  • Introduced through: openjdk@11-jre gnupg2/gpg-agent@2.2.27-2+deb11u2
  • Introduced through: openjdk@11-jre gnupg2/gpg-wks-client@2.2.27-2+deb11u2
  • Introduced through: openjdk@11-jre gnupg2/gpg-wks-server@2.2.27-2+deb11u2
  • Introduced through: openjdk@11-jre gnupg2/gpgconf@2.2.27-2+deb11u2
  • Introduced through: openjdk@11-jre gnupg2/gpgsm@2.2.27-2+deb11u2
  • Introduced through: openjdk@11-jre gnupg2/gpgv@2.2.27-2+deb11u2

NVD Description

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

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

There is no fixed version for Debian:11 gnupg2.

References

low severity

Uncaught Exception

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

Detailed paths

  • Introduced through: openjdk@11-jre gnutls28/libgnutls30@3.7.1-5+deb11u1

NVD Description

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

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

Remediation

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

References

low severity

Use of a Broken or Risky Cryptographic Algorithm

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

Detailed paths

  • Introduced through: openjdk@11-jre gnutls28/libgnutls30@3.7.1-5+deb11u1

NVD Description

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

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

Remediation

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

References

low severity

CVE-2024-26461

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

Detailed paths

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

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 krb5.

References

low severity

CVE-2025-24528

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

Detailed paths

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

NVD Description

This vulnerability has not been analyzed by NVD yet.

Remediation

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

References

low severity

Memory Leak

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

Detailed paths

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

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 krb5.

References

low severity

Information Exposure

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

Detailed paths

  • Introduced through: openjdk@11-jre libgcrypt20@1.8.7-6

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 libgcrypt20.

References

low severity

CVE-2024-28182

  • Vulnerable module: nghttp2/libnghttp2-14
  • Introduced through: nghttp2/libnghttp2-14@1.43.0-1
  • Fixed in: 1.43.0-1+deb11u2

Detailed paths

  • Introduced through: openjdk@11-jre nghttp2/libnghttp2-14@1.43.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:11 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:11 nghttp2 to version 1.43.0-1+deb11u2 or higher.

References

low severity

CVE-2024-13176

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

Detailed paths

  • Introduced through: openjdk@11-jre openssl@1.1.1n-0+deb11u3
  • Introduced through: openjdk@11-jre openssl/libssl1.1@1.1.1n-0+deb11u3

NVD Description

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

Issue summary: 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:11 openssl to version 1.1.1w-0+deb11u3 or higher.

References

low severity

CVE-2024-2511

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

Detailed paths

  • Introduced through: openjdk@11-jre openssl@1.1.1n-0+deb11u3
  • Introduced through: openjdk@11-jre openssl/libssl1.1@1.1.1n-0+deb11u3

NVD Description

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

Issue summary: 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:11 openssl to version 1.1.1w-0+deb11u2 or higher.

References

low severity

CVE-2024-4741

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

Detailed paths

  • Introduced through: openjdk@11-jre openssl@1.1.1n-0+deb11u3
  • Introduced through: openjdk@11-jre openssl/libssl1.1@1.1.1n-0+deb11u3

NVD Description

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

Issue summary: 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:11 openssl to version 1.1.1w-0+deb11u2 or higher.

References

low severity

CVE-2024-5535

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

Detailed paths

  • Introduced through: openjdk@11-jre openssl@1.1.1n-0+deb11u3
  • Introduced through: openjdk@11-jre openssl/libssl1.1@1.1.1n-0+deb11u3

NVD Description

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

Issue summary: 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:11 openssl to version 1.1.1w-0+deb11u2 or higher.

References

low severity

CVE-2024-9143

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

Detailed paths

  • Introduced through: openjdk@11-jre openssl@1.1.1n-0+deb11u3
  • Introduced through: openjdk@11-jre openssl/libssl1.1@1.1.1n-0+deb11u3

NVD Description

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

Issue summary: 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:11 openssl to version 1.1.1w-0+deb11u2 or higher.

References

low severity

CVE-2025-27587

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

Detailed paths

  • Introduced through: openjdk@11-jre openssl@1.1.1n-0+deb11u3
  • Introduced through: openjdk@11-jre openssl/libssl1.1@1.1.1n-0+deb11u3

NVD Description

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

OpenSSL 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

There is no fixed version for Debian:11 openssl.

References

low severity

CVE-2025-40909

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

Detailed paths

  • Introduced through: openjdk@11-jre perl/perl-base@5.32.1-4+deb11u2

NVD Description

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

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

There is no fixed version for Debian:11 perl.

References

low severity

CVE-2024-56433

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

Detailed paths

  • Introduced through: openjdk@11-jre shadow/login@1:4.8.1-1
  • Introduced through: openjdk@11-jre shadow/passwd@1:4.8.1-1

NVD Description

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

shadow-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:11 shadow.

References

low severity

Integer Overflow or Wraparound

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.34.1-3

Detailed paths

  • Introduced through: openjdk@11-jre sqlite3/libsqlite3-0@3.34.1-3

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

There is no fixed version for Debian:11 sqlite3.

References

low severity

CVE-2023-50868

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

Detailed paths

  • Introduced through: openjdk@11-jre systemd/libsystemd0@247.3-7
  • Introduced through: openjdk@11-jre systemd/libudev1@247.3-7

NVD Description

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

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

Remediation

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

References

low severity

CVE-2023-39804

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

Detailed paths

  • Introduced through: openjdk@11-jre tar@1.34+dfsg-1

NVD Description

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

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

Remediation

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

References

low severity

CVE-2024-28085

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.36.1-8+deb11u1, util-linux/libblkid1@2.36.1-8+deb11u1 and others
  • Fixed in: 2.36.1-8+deb11u2

Detailed paths

  • Introduced through: openjdk@11-jre util-linux@2.36.1-8+deb11u1
  • Introduced through: openjdk@11-jre util-linux/libblkid1@2.36.1-8+deb11u1
  • Introduced through: openjdk@11-jre util-linux/libmount1@2.36.1-8+deb11u1
  • Introduced through: openjdk@11-jre util-linux/libsmartcols1@2.36.1-8+deb11u1
  • Introduced through: openjdk@11-jre util-linux/libuuid1@2.36.1-8+deb11u1
  • Introduced through: openjdk@11-jre util-linux/mount@2.36.1-8+deb11u1

NVD Description

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

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

Remediation

Upgrade Debian:11 util-linux to version 2.36.1-8+deb11u2 or higher.

References

low severity

Server-Side Request Forgery (SSRF)

  • Vulnerable module: wget
  • Introduced through: wget@1.21-1+deb11u1

Detailed paths

  • Introduced through: openjdk@11-jre wget@1.21-1+deb11u1

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

There is no fixed version for Debian:11 wget.

References