Vulnerabilities

130 via 295 paths

Dependencies

166

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
  • 2
  • 4
  • 2
  • 122
Status
  • 130
  • 0
  • 0

critical severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm zlib/zlib1g@1:1.2.11.dfsg-2+deb11u2

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

Cleartext Transmission of Sensitive Information

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u11, curl/libcurl3-gnutls@7.74.0-1.3+deb11u11 and others

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm curl@7.74.0-1.3+deb11u11
  • Introduced through: buildpack-deps@bullseye-scm curl/libcurl3-gnutls@7.74.0-1.3+deb11u11
  • Introduced through: buildpack-deps@bullseye-scm curl/libcurl4@7.74.0-1.3+deb11u11

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

high severity

Cleartext Transmission of Sensitive Information

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u11, curl/libcurl3-gnutls@7.74.0-1.3+deb11u11 and others

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm curl@7.74.0-1.3+deb11u11
  • Introduced through: buildpack-deps@bullseye-scm curl/libcurl3-gnutls@7.74.0-1.3+deb11u11
  • Introduced through: buildpack-deps@bullseye-scm curl/libcurl4@7.74.0-1.3+deb11u11

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+deb11u11, curl/libcurl3-gnutls@7.74.0-1.3+deb11u11 and others

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm curl@7.74.0-1.3+deb11u11
  • Introduced through: buildpack-deps@bullseye-scm curl/libcurl3-gnutls@7.74.0-1.3+deb11u11
  • Introduced through: buildpack-deps@bullseye-scm curl/libcurl4@7.74.0-1.3+deb11u11

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

Resource Exhaustion

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm expat/libexpat1@2.2.10-2+deb11u5

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 expat.

References

high severity

Allocation of Resources Without Limits or Throttling

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm systemd/libsystemd0@247.3-7+deb11u4
  • Introduced through: buildpack-deps@bullseye-scm systemd/libudev1@247.3-7+deb11u4

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 systemd.

References

medium severity

Cleartext Transmission of Sensitive Information

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u11, curl/libcurl3-gnutls@7.74.0-1.3+deb11u11 and others

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm curl@7.74.0-1.3+deb11u11
  • Introduced through: buildpack-deps@bullseye-scm curl/libcurl3-gnutls@7.74.0-1.3+deb11u11
  • Introduced through: buildpack-deps@bullseye-scm curl/libcurl4@7.74.0-1.3+deb11u11

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

Missing Encryption of Sensitive Data

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u11, curl/libcurl3-gnutls@7.74.0-1.3+deb11u11 and others

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm curl@7.74.0-1.3+deb11u11
  • Introduced through: buildpack-deps@bullseye-scm curl/libcurl3-gnutls@7.74.0-1.3+deb11u11
  • Introduced through: buildpack-deps@bullseye-scm curl/libcurl4@7.74.0-1.3+deb11u11

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

low severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm db5.3/libdb5.3@5.3.28+dfsg1-0.8

NVD Description

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

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

Remediation

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

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm glibc/libc-bin@2.31-13+deb11u9
  • Introduced through: buildpack-deps@bullseye-scm glibc/libc6@2.31-13+deb11u9

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 glibc.

References

low severity

CVE-2020-27619

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm python3.9@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/libpython3.9-minimal@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/libpython3.9-stdlib@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/python3.9-minimal@3.9.2-1

NVD Description

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

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

Remediation

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

References

low severity

Improper Input Validation

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm python3.9@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/libpython3.9-minimal@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/libpython3.9-stdlib@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/python3.9-minimal@3.9.2-1

NVD Description

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

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

Remediation

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

References

low severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm python3.9@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/libpython3.9-minimal@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/libpython3.9-stdlib@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/python3.9-minimal@3.9.2-1

NVD Description

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

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

Remediation

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

References

low severity

CVE-2005-2541

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm tar@1.34+dfsg-1+deb11u1

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

Improper Input Validation

  • Vulnerable module: git
  • Introduced through: git@1:2.30.2-1+deb11u2 and git/git-man@1:2.30.2-1+deb11u2

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm git@1:2.30.2-1+deb11u2
  • Introduced through: buildpack-deps@bullseye-scm git/git-man@1:2.30.2-1+deb11u2

NVD Description

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

GIT version 2.15.1 and earlier contains a Input Validation Error vulnerability in Client that can result in problems including messing up terminal configuration to RCE. This attack appear to be exploitable via The user must interact with a malicious git server, (or have their traffic modified in a MITM attack).

Remediation

There is no fixed version for Debian:11 git.

References

low severity

CVE-2019-1010023

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm glibc/libc-bin@2.31-13+deb11u9
  • Introduced through: buildpack-deps@bullseye-scm glibc/libc6@2.31-13+deb11u9

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
  • Introduced through: perl@5.32.1-4+deb11u3, perl/libperl5.32@5.32.1-4+deb11u3 and others

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm perl@5.32.1-4+deb11u3
  • Introduced through: buildpack-deps@bullseye-scm perl/libperl5.32@5.32.1-4+deb11u3
  • Introduced through: buildpack-deps@bullseye-scm perl/perl-base@5.32.1-4+deb11u3
  • Introduced through: buildpack-deps@bullseye-scm perl/perl-modules-5.32@5.32.1-4+deb11u3

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 perl.

References

low severity

Improper Certificate Validation

  • Vulnerable module: perl
  • Introduced through: perl@5.32.1-4+deb11u3, perl/libperl5.32@5.32.1-4+deb11u3 and others

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm perl@5.32.1-4+deb11u3
  • Introduced through: buildpack-deps@bullseye-scm perl/libperl5.32@5.32.1-4+deb11u3
  • Introduced through: buildpack-deps@bullseye-scm perl/perl-base@5.32.1-4+deb11u3
  • Introduced through: buildpack-deps@bullseye-scm perl/perl-modules-5.32@5.32.1-4+deb11u3

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 perl.

References

low severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm bash@5.1-2+deb11u1

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 bash.

References

low severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm e2fsprogs@1.46.2-2
  • Introduced through: buildpack-deps@bullseye-scm e2fsprogs/libcom-err2@1.46.2-2
  • Introduced through: buildpack-deps@bullseye-scm e2fsprogs/libext2fs2@1.46.2-2
  • Introduced through: buildpack-deps@bullseye-scm e2fsprogs/libss2@1.46.2-2
  • Introduced through: buildpack-deps@bullseye-scm e2fsprogs/logsave@1.46.2-2

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 e2fsprogs.

References

low severity

Arbitrary Code Injection

  • Vulnerable module: git
  • Introduced through: git@1:2.30.2-1+deb11u2 and git/git-man@1:2.30.2-1+deb11u2

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm git@1:2.30.2-1+deb11u2
  • Introduced through: buildpack-deps@bullseye-scm git/git-man@1:2.30.2-1+deb11u2

NVD Description

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

Git is a revision control system. Prior to versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1, a specially crafted .gitmodules file with submodule URLs that are longer than 1024 characters can used to exploit a bug in config.c::git_config_copy_or_rename_section_in_file(). This bug can be used to inject arbitrary configuration into a user's $GIT_DIR/config when attempting to remove the configuration section associated with that submodule. When the attacker injects configuration values which specify executables to run (such as core.pager, core.editor, core.sshCommand, etc.) this can lead to a remote code execution. A fix A fix is available in versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1. As a workaround, avoid running git submodule deinit on untrusted repositories or without prior inspection of any submodule sections in $GIT_DIR/config.

Remediation

There is no fixed version for Debian:11 git.

References

low severity

OS Command Injection

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:8.4p1-5+deb11u3

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm openssh/openssh-client@1:8.4p1-5+deb11u3

NVD Description

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

scp in OpenSSH through 8.3p1 allows command injection in the scp.c toremote function, as demonstrated by backtick characters in the destination argument. NOTE: the vendor reportedly has stated that they intentionally omit validation of "anomalous argument transfers" because that could "stand a great chance of breaking existing workflows."

Remediation

There is no fixed version for Debian:11 openssh.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm 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: buildpack-deps@bullseye-scm pcre3/libpcre3@2:8.39-13

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 pcre3.

References

low severity

Improper Verification of Cryptographic Signature

  • Vulnerable module: perl
  • Introduced through: perl@5.32.1-4+deb11u3, perl/libperl5.32@5.32.1-4+deb11u3 and others

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm perl@5.32.1-4+deb11u3
  • Introduced through: buildpack-deps@bullseye-scm perl/libperl5.32@5.32.1-4+deb11u3
  • Introduced through: buildpack-deps@bullseye-scm perl/perl-base@5.32.1-4+deb11u3
  • Introduced through: buildpack-deps@bullseye-scm perl/perl-modules-5.32@5.32.1-4+deb11u3

NVD Description

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

CPAN 2.28 allows Signature Verification Bypass.

Remediation

There is no fixed version for Debian:11 perl.

References

low severity

CVE-2022-42919

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm python3.9@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/libpython3.9-minimal@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/libpython3.9-stdlib@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/python3.9-minimal@3.9.2-1

NVD Description

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

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

Remediation

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

References

low severity

Incorrect Permission Assignment for Critical Resource

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm shadow/login@1:4.8.1-1
  • Introduced through: buildpack-deps@bullseye-scm shadow/passwd@1:4.8.1-1

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 shadow.

References

low severity

Arbitrary Command Injection

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm python3.9@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/libpython3.9-minimal@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/libpython3.9-stdlib@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/python3.9-minimal@3.9.2-1

NVD Description

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

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

Remediation

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

References

low severity

Directory Traversal

  • Vulnerable module: git
  • Introduced through: git@1:2.30.2-1+deb11u2 and git/git-man@1:2.30.2-1+deb11u2

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm git@1:2.30.2-1+deb11u2
  • Introduced through: buildpack-deps@bullseye-scm git/git-man@1:2.30.2-1+deb11u2

NVD Description

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

Git is a revision control system. Prior to versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1, by feeding specially crafted input to git apply --reject, a path outside the working tree can be overwritten with partially controlled contents (corresponding to the rejected hunk(s) from the given patch). A fix is available in versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1. As a workaround, avoid using git apply with --reject when applying patches from an untrusted source. Use git apply --stat to inspect a patch before applying; avoid applying one that create a conflict where a link corresponding to the *.rej file exists.

Remediation

There is no fixed version for Debian:11 git.

References

low severity

Exposure of Resource to Wrong Sphere

  • Vulnerable module: git
  • Introduced through: git@1:2.30.2-1+deb11u2 and git/git-man@1:2.30.2-1+deb11u2

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm git@1:2.30.2-1+deb11u2
  • Introduced through: buildpack-deps@bullseye-scm git/git-man@1:2.30.2-1+deb11u2

NVD Description

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

The --mirror documentation for Git through 2.35.1 does not mention the availability of deleted content, aka the "GitBleed" issue. This could present a security risk if information-disclosure auditing processes rely on a clone operation without the --mirror option.

Remediation

There is no fixed version for Debian:11 git.

References

low severity

Uncontrolled Recursion

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm glibc/libc-bin@2.31-13+deb11u9
  • Introduced through: buildpack-deps@bullseye-scm glibc/libc6@2.31-13+deb11u9

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+deb11u9 and glibc/libc6@2.31-13+deb11u9

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm glibc/libc-bin@2.31-13+deb11u9
  • Introduced through: buildpack-deps@bullseye-scm glibc/libc6@2.31-13+deb11u9

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 glibc.

References

low severity

Improper Verification of Cryptographic Signature

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm gnutls28/libgnutls30@3.7.1-5+deb11u4

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 gnutls28.

References

low severity

Information Exposure

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm gnutls28/libgnutls30@3.7.1-5+deb11u4

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 gnutls28.

References

low severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm krb5/libgssapi-krb5-2@1.18.3-6+deb11u4
  • Introduced through: buildpack-deps@bullseye-scm krb5/libk5crypto3@1.18.3-6+deb11u4
  • Introduced through: buildpack-deps@bullseye-scm krb5/libkrb5-3@1.18.3-6+deb11u4
  • Introduced through: buildpack-deps@bullseye-scm krb5/libkrb5support0@1.18.3-6+deb11u4

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: buildpack-deps@bullseye-scm 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: buildpack-deps@bullseye-scm 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

Out-of-bounds Write

  • Vulnerable module: libssh2/libssh2-1
  • Introduced through: libssh2/libssh2-1@1.9.0-2

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm 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

There is no fixed version for Debian:11 libssh2.

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: buildpack-deps@bullseye-scm 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: buildpack-deps@bullseye-scm 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: buildpack-deps@bullseye-scm 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+deb11u1

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm pcre2/libpcre2-8-0@10.36-2+deb11u1

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: buildpack-deps@bullseye-scm 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: buildpack-deps@bullseye-scm pcre3/libpcre3@2:8.39-13

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 pcre3.

References

low severity

Link Following

  • Vulnerable module: perl
  • Introduced through: perl@5.32.1-4+deb11u3, perl/libperl5.32@5.32.1-4+deb11u3 and others

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm perl@5.32.1-4+deb11u3
  • Introduced through: buildpack-deps@bullseye-scm perl/libperl5.32@5.32.1-4+deb11u3
  • Introduced through: buildpack-deps@bullseye-scm perl/perl-base@5.32.1-4+deb11u3
  • Introduced through: buildpack-deps@bullseye-scm perl/perl-modules-5.32@5.32.1-4+deb11u3

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 perl.

References

low severity

Algorithmic Complexity

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm python3.9@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/libpython3.9-minimal@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/libpython3.9-stdlib@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/python3.9-minimal@3.9.2-1

NVD Description

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

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

Remediation

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

References

low severity

Arbitrary Code Injection

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm python3.9@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/libpython3.9-minimal@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/libpython3.9-stdlib@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/python3.9-minimal@3.9.2-1

NVD Description

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

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

Remediation

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

References

low severity

Improper Input Validation

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm python3.9@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/libpython3.9-minimal@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/libpython3.9-stdlib@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/python3.9-minimal@3.9.2-1

NVD Description

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

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

Remediation

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

References

low severity

Incorrect Type Conversion or Cast

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm python3.9@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/libpython3.9-minimal@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/libpython3.9-stdlib@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/python3.9-minimal@3.9.2-1

NVD Description

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

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

Remediation

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

References

low severity

Resource Exhaustion

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm python3.9@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/libpython3.9-minimal@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/libpython3.9-stdlib@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/python3.9-minimal@3.9.2-1

NVD Description

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

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

Remediation

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

References

low severity

Improper Validation of Array Index

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm 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

Out-of-bounds Read

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm 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

There is no fixed version for Debian:11 sqlite3.

References

low severity

Out-of-bounds Read

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

low severity

Open Redirect

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm python3.9@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/libpython3.9-minimal@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/libpython3.9-stdlib@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/python3.9-minimal@3.9.2-1

NVD Description

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

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

Remediation

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

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm 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

There is no fixed version for Debian:11 sqlite3.

References

low severity

CVE-2023-51767

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:8.4p1-5+deb11u3

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm openssh/openssh-client@1:8.4p1-5+deb11u3

NVD Description

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

OpenSSH through 9.6, when common types of DRAM are used, might allow row hammer attacks (for authentication bypass) because the integer value of authenticated in mm_answer_authpassword does not resist flips of a single bit. NOTE: this is applicable to a certain threat model of attacker-victim co-location in which the attacker has user privileges.

Remediation

There is no fixed version for Debian:11 openssh.

References

low severity

Inappropriate Encoding for Output Context

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:8.4p1-5+deb11u3

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm openssh/openssh-client@1:8.4p1-5+deb11u3

NVD Description

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

In OpenSSH 7.9, due to accepting and displaying arbitrary stderr output from the server, a malicious server (or Man-in-The-Middle attacker) can manipulate the client output, for example to use ANSI control codes to hide additional files being transferred.

Remediation

There is no fixed version for Debian:11 openssh.

References

low severity

Improper Input Validation

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm 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+deb11u11, curl/libcurl3-gnutls@7.74.0-1.3+deb11u11 and others

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm curl@7.74.0-1.3+deb11u11
  • Introduced through: buildpack-deps@bullseye-scm curl/libcurl3-gnutls@7.74.0-1.3+deb11u11
  • Introduced through: buildpack-deps@bullseye-scm curl/libcurl4@7.74.0-1.3+deb11u11

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

CVE-2023-50495

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm ncurses/libncurses6@6.2+20201114-2+deb11u2
  • Introduced through: buildpack-deps@bullseye-scm ncurses/libncursesw6@6.2+20201114-2+deb11u2
  • Introduced through: buildpack-deps@bullseye-scm ncurses/libtinfo6@6.2+20201114-2+deb11u2
  • Introduced through: buildpack-deps@bullseye-scm ncurses/ncurses-base@6.2+20201114-2+deb11u2
  • Introduced through: buildpack-deps@bullseye-scm ncurses/ncurses-bin@6.2+20201114-2+deb11u2

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 ncurses.

References

low severity

Resource Exhaustion

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm python3.9@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/libpython3.9-minimal@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/libpython3.9-stdlib@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/python3.9-minimal@3.9.2-1

NVD Description

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

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

Remediation

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

References

low severity

XML External Entity (XXE) Injection

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm expat/libexpat1@2.2.10-2+deb11u5

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: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:8.4p1-5+deb11u3

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm openssh/openssh-client@1:8.4p1-5+deb11u3

NVD Description

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

sshd in OpenSSH 4 on Debian GNU/Linux, and the 20070303 OpenSSH snapshot, allows remote authenticated users to obtain access to arbitrary SELinux roles by appending a :/ (colon slash) sequence, followed by the role name, to the username.

Remediation

There is no fixed version for Debian:11 openssh.

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: buildpack-deps@bullseye-scm shadow/login@1:4.8.1-1
  • Introduced through: buildpack-deps@bullseye-scm 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+deb11u4 and systemd/libudev1@247.3-7+deb11u4

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm systemd/libsystemd0@247.3-7+deb11u4
  • Introduced through: buildpack-deps@bullseye-scm systemd/libudev1@247.3-7+deb11u4

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: buildpack-deps@bullseye-scm 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+deb11u11, curl/libcurl3-gnutls@7.74.0-1.3+deb11u11 and others

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm curl@7.74.0-1.3+deb11u11
  • Introduced through: buildpack-deps@bullseye-scm curl/libcurl3-gnutls@7.74.0-1.3+deb11u11
  • Introduced through: buildpack-deps@bullseye-scm curl/libcurl4@7.74.0-1.3+deb11u11

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+deb11u9 and glibc/libc6@2.31-13+deb11u9

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm glibc/libc-bin@2.31-13+deb11u9
  • Introduced through: buildpack-deps@bullseye-scm glibc/libc6@2.31-13+deb11u9

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 glibc.

References

low severity

Use After Free

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm glibc/libc-bin@2.31-13+deb11u9
  • Introduced through: buildpack-deps@bullseye-scm glibc/libc6@2.31-13+deb11u9

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 glibc.

References

low severity

Information Exposure

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:8.4p1-5+deb11u3

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm openssh/openssh-client@1:8.4p1-5+deb11u3

NVD Description

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

The client side in OpenSSH 5.7 through 8.4 has an Observable Discrepancy leading to an information leak in the algorithm negotiation. This allows man-in-the-middle attackers to target initial connection attempts (where no host key for the server has been cached by the client). NOTE: some reports state that 8.5 and 8.6 are also affected.

Remediation

There is no fixed version for Debian:11 openssh.

References

low severity

CVE-2023-7008

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm systemd/libsystemd0@247.3-7+deb11u4
  • Introduced through: buildpack-deps@bullseye-scm systemd/libudev1@247.3-7+deb11u4

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 systemd.

References

low severity

Information Exposure

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm python3.9@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/libpython3.9-minimal@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/libpython3.9-stdlib@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/python3.9-minimal@3.9.2-1

NVD Description

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

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

Remediation

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

References

low severity

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

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm expat/libexpat1@2.2.10-2+deb11u5

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

CVE-2024-0727

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm openssl@1.1.1w-0+deb11u1
  • Introduced through: buildpack-deps@bullseye-scm openssl/libssl1.1@1.1.1w-0+deb11u1

NVD Description

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

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

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

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

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

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

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

Remediation

There is no fixed version for Debian:11 openssl.

References

low severity

CVE-2024-22365

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm pam/libpam-modules@1.4.0-9+deb11u1
  • Introduced through: buildpack-deps@bullseye-scm pam/libpam-modules-bin@1.4.0-9+deb11u1
  • Introduced through: buildpack-deps@bullseye-scm pam/libpam-runtime@1.4.0-9+deb11u1
  • Introduced through: buildpack-deps@bullseye-scm 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: buildpack-deps@bullseye-scm pcre3/libpcre3@2:8.39-13

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 pcre3.

References

low severity

Improper Authentication

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm shadow/login@1:4.8.1-1
  • Introduced through: buildpack-deps@bullseye-scm shadow/passwd@1:4.8.1-1

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 shadow.

References

low severity

Information Exposure

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm util-linux@2.36.1-8+deb11u2
  • Introduced through: buildpack-deps@bullseye-scm util-linux/bsdutils@1:2.36.1-8+deb11u2
  • Introduced through: buildpack-deps@bullseye-scm util-linux/libblkid1@2.36.1-8+deb11u2
  • Introduced through: buildpack-deps@bullseye-scm util-linux/libmount1@2.36.1-8+deb11u2
  • Introduced through: buildpack-deps@bullseye-scm util-linux/libsmartcols1@2.36.1-8+deb11u2
  • Introduced through: buildpack-deps@bullseye-scm util-linux/libuuid1@2.36.1-8+deb11u2
  • Introduced through: buildpack-deps@bullseye-scm util-linux/mount@2.36.1-8+deb11u2

NVD Description

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

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

Remediation

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

References

low severity

Cryptographic Issues

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm openssl@1.1.1w-0+deb11u1
  • Introduced through: buildpack-deps@bullseye-scm openssl/libssl1.1@1.1.1w-0+deb11u1

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 openssl.

References

low severity

Insufficiently Protected Credentials

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u11, curl/libcurl3-gnutls@7.74.0-1.3+deb11u11 and others

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm curl@7.74.0-1.3+deb11u11
  • Introduced through: buildpack-deps@bullseye-scm curl/libcurl3-gnutls@7.74.0-1.3+deb11u11
  • Introduced through: buildpack-deps@bullseye-scm curl/libcurl4@7.74.0-1.3+deb11u11

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+deb11u9 and glibc/libc6@2.31-13+deb11u9

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm glibc/libc-bin@2.31-13+deb11u9
  • Introduced through: buildpack-deps@bullseye-scm glibc/libc6@2.31-13+deb11u9

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+deb11u9 and glibc/libc6@2.31-13+deb11u9

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm glibc/libc-bin@2.31-13+deb11u9
  • Introduced through: buildpack-deps@bullseye-scm glibc/libc6@2.31-13+deb11u9

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

CVE-2016-20012

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:8.4p1-5+deb11u3

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm openssh/openssh-client@1:8.4p1-5+deb11u3

NVD Description

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

OpenSSH through 8.7 allows remote attackers, who have a suspicion that a certain combination of username and public key is known to an SSH server, to test whether this suspicion is correct. This occurs because a challenge is sent only when that combination could be valid for a login session. NOTE: the vendor does not recognize user enumeration as a vulnerability for this product

Remediation

There is no fixed version for Debian:11 openssh.

References

low severity

Improper Authentication

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:8.4p1-5+deb11u3

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm openssh/openssh-client@1:8.4p1-5+deb11u3

NVD Description

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

OpenSSH 4.6 and earlier, when ChallengeResponseAuthentication is enabled, allows remote attackers to determine the existence of user accounts by attempting to authenticate via S/KEY, which displays a different response if the user account exists, a similar issue to CVE-2001-1483.

Remediation

There is no fixed version for Debian:11 openssh.

References

low severity

Information Exposure

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:8.4p1-5+deb11u3

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm openssh/openssh-client@1:8.4p1-5+deb11u3

NVD Description

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

Remotely observable behaviour in auth-gss2.c in OpenSSH through 7.8 could be used by remote attackers to detect existence of users on a target system when GSS2 is in use. NOTE: the discoverer states 'We understand that the OpenSSH developers do not want to treat such a username enumeration (or "oracle") as a vulnerability.'

Remediation

There is no fixed version for Debian:11 openssh.

References

low severity

Improper Check for Unusual or Exceptional Conditions

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm openssl@1.1.1w-0+deb11u1
  • Introduced through: buildpack-deps@bullseye-scm openssl/libssl1.1@1.1.1w-0+deb11u1

NVD Description

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

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

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

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

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

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

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

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

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

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

Remediation

There is no fixed version for Debian:11 openssl.

References

low severity

CVE-2023-40217

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm python3.9@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/libpython3.9-minimal@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/libpython3.9-stdlib@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/python3.9-minimal@3.9.2-1

NVD Description

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

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

Remediation

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

References

low severity

Improper Input Validation

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm python3.9@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/libpython3.9-minimal@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/libpython3.9-stdlib@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/python3.9-minimal@3.9.2-1

NVD Description

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

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

Remediation

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

References

low severity

Unchecked Return Value

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm python3.9@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/libpython3.9-minimal@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/libpython3.9-stdlib@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/python3.9-minimal@3.9.2-1

NVD Description

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

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

Remediation

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

References

low severity

Improper Validation of Integrity Check Value

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm systemd/libsystemd0@247.3-7+deb11u4
  • Introduced through: buildpack-deps@bullseye-scm systemd/libudev1@247.3-7+deb11u4

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+deb11u4 and systemd/libudev1@247.3-7+deb11u4

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm systemd/libsystemd0@247.3-7+deb11u4
  • Introduced through: buildpack-deps@bullseye-scm systemd/libudev1@247.3-7+deb11u4

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+deb11u4 and systemd/libudev1@247.3-7+deb11u4

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm systemd/libsystemd0@247.3-7+deb11u4
  • Introduced through: buildpack-deps@bullseye-scm systemd/libudev1@247.3-7+deb11u4

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 systemd.

References

low severity

Cryptographic Issues

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm openssl@1.1.1w-0+deb11u1
  • Introduced through: buildpack-deps@bullseye-scm openssl/libssl1.1@1.1.1w-0+deb11u1

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 openssl.

References

low severity

CVE-2023-4039

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm gcc-10/gcc-10-base@10.2.1-6
  • Introduced through: buildpack-deps@bullseye-scm gcc-10/libgcc-s1@10.2.1-6
  • Introduced through: buildpack-deps@bullseye-scm 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: buildpack-deps@bullseye-scm 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: buildpack-deps@bullseye-scm 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: buildpack-deps@bullseye-scm 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

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: buildpack-deps@bullseye-scm shadow/login@1:4.8.1-1
  • Introduced through: buildpack-deps@bullseye-scm shadow/passwd@1:4.8.1-1

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 shadow.

References

low severity

Link Following

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm systemd/libsystemd0@247.3-7+deb11u4
  • Introduced through: buildpack-deps@bullseye-scm systemd/libudev1@247.3-7+deb11u4

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+deb11u9 and glibc/libc6@2.31-13+deb11u9

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm glibc/libc-bin@2.31-13+deb11u9
  • Introduced through: buildpack-deps@bullseye-scm glibc/libc6@2.31-13+deb11u9

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+deb11u4

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm gnutls28/libgnutls30@3.7.1-5+deb11u4

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

Information Exposure

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:8.4p1-5+deb11u3

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm openssh/openssh-client@1:8.4p1-5+deb11u3

NVD Description

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

OpenSSH, when using OPIE (One-Time Passwords in Everything) for PAM, allows remote attackers to determine the existence of certain user accounts, which displays a different response if the user account exists and is configured to use one-time passwords (OTP), a similar issue to CVE-2007-2243.

Remediation

There is no fixed version for Debian:11 openssh.

References

low severity

Memory Leak

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm 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: buildpack-deps@bullseye-scm 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: buildpack-deps@bullseye-scm apt@2.2.4
  • Introduced through: buildpack-deps@bullseye-scm 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

Improper Authentication

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:8.4p1-5+deb11u3

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm openssh/openssh-client@1:8.4p1-5+deb11u3

NVD Description

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

An issue was discovered in OpenSSH before 8.9. If a client is using public-key authentication with agent forwarding but without -oLogLevel=verbose, and an attacker has silently modified the server to support the None authentication option, then the user cannot determine whether FIDO authentication is going to confirm that the user wishes to connect to that server, or that the user wishes to allow that server to connect to a different server on the user's behalf. NOTE: the vendor's position is "this is not an authentication bypass, since nothing is being bypassed.

Remediation

There is no fixed version for Debian:11 openssh.

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: buildpack-deps@bullseye-scm gnupg2/dirmngr@2.2.27-2+deb11u2
  • Introduced through: buildpack-deps@bullseye-scm gnupg2/gnupg@2.2.27-2+deb11u2
  • Introduced through: buildpack-deps@bullseye-scm gnupg2/gnupg-l10n@2.2.27-2+deb11u2
  • Introduced through: buildpack-deps@bullseye-scm gnupg2/gnupg-utils@2.2.27-2+deb11u2
  • Introduced through: buildpack-deps@bullseye-scm gnupg2/gpg@2.2.27-2+deb11u2
  • Introduced through: buildpack-deps@bullseye-scm gnupg2/gpg-agent@2.2.27-2+deb11u2
  • Introduced through: buildpack-deps@bullseye-scm gnupg2/gpg-wks-client@2.2.27-2+deb11u2
  • Introduced through: buildpack-deps@bullseye-scm gnupg2/gpg-wks-server@2.2.27-2+deb11u2
  • Introduced through: buildpack-deps@bullseye-scm gnupg2/gpgconf@2.2.27-2+deb11u2
  • Introduced through: buildpack-deps@bullseye-scm gnupg2/gpgsm@2.2.27-2+deb11u2
  • Introduced through: buildpack-deps@bullseye-scm gnupg2/gpgv@2.2.27-2+deb11u2

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 gnupg2.

References

low severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm libsepol/libsepol1@3.1-1

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 libsepol.

References

low severity

Use After Free

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm libsepol/libsepol1@3.1-1

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 libsepol.

References

low severity

Use After Free

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm libsepol/libsepol1@3.1-1

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 libsepol.

References

low severity

Use After Free

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm libsepol/libsepol1@3.1-1

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 libsepol.

References

low severity

Out-of-bounds Write

  • Vulnerable module: procps
  • Introduced through: procps@2:3.3.17-5 and procps/libprocps8@2:3.3.17-5

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm procps@2:3.3.17-5
  • Introduced through: buildpack-deps@bullseye-scm procps/libprocps8@2:3.3.17-5

NVD Description

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

Under some circumstances, this weakness allows a user who has access to run the “ps” utility on a machine, the ability to write almost unlimited amounts of unfiltered data into the process heap.

Remediation

There is no fixed version for Debian:11 procps.

References

low severity

Arbitrary Code Injection

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm shadow/login@1:4.8.1-1
  • Introduced through: buildpack-deps@bullseye-scm shadow/passwd@1:4.8.1-1

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 shadow.

References

low severity

Use of Externally-Controlled Format String

  • Vulnerable module: git
  • Introduced through: git@1:2.30.2-1+deb11u2 and git/git-man@1:2.30.2-1+deb11u2

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm git@1:2.30.2-1+deb11u2
  • Introduced through: buildpack-deps@bullseye-scm git/git-man@1:2.30.2-1+deb11u2

NVD Description

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

In Git for Windows, the Windows port of Git, no localized messages are shipped with the installer. As a consequence, Git is expected not to localize messages at all, and skips the gettext initialization. However, due to a change in MINGW-packages, the gettext() function's implicit initialization no longer uses the runtime prefix but uses the hard-coded path C:\mingw64\share\locale to look for localized messages. And since any authenticated user has the permission to create folders in C:\ (and since C:\mingw64 does not typically exist), it is possible for low-privilege users to place fake messages in that location where git.exe will pick them up in version 2.40.1.

This vulnerability is relatively hard to exploit and requires social engineering. For example, a legitimate message at the end of a clone could be maliciously modified to ask the user to direct their web browser to a malicious website, and the user might think that the message comes from Git and is legitimate. It does require local write access by the attacker, though, which makes this attack vector less likely. Version 2.40.1 contains a patch for this issue. Some workarounds are available. Do not work on a Windows machine with shared accounts, or alternatively create a C:\mingw64 folder and leave it empty. Users who have administrative rights may remove the permission to create folders in C:\.

Remediation

There is no fixed version for Debian:11 git.

References

low severity
new

CVE-2024-2379

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u11, curl/libcurl3-gnutls@7.74.0-1.3+deb11u11 and others

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm curl@7.74.0-1.3+deb11u11
  • Introduced through: buildpack-deps@bullseye-scm curl/libcurl3-gnutls@7.74.0-1.3+deb11u11
  • Introduced through: buildpack-deps@bullseye-scm curl/libcurl4@7.74.0-1.3+deb11u11

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
new

CVE-2024-2398

  • Vulnerable module: curl
  • Introduced through: curl@7.74.0-1.3+deb11u11, curl/libcurl3-gnutls@7.74.0-1.3+deb11u11 and others

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm curl@7.74.0-1.3+deb11u11
  • Introduced through: buildpack-deps@bullseye-scm curl/libcurl3-gnutls@7.74.0-1.3+deb11u11
  • Introduced through: buildpack-deps@bullseye-scm curl/libcurl4@7.74.0-1.3+deb11u11

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

There is no fixed version for Debian:11 curl.

References

low severity

CVE-2024-28757

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm expat/libexpat1@2.2.10-2+deb11u5

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

Information Exposure

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm gnutls28/libgnutls30@3.7.1-5+deb11u4

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 gnutls28.

References

low severity

Uncaught Exception

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm gnutls28/libgnutls30@3.7.1-5+deb11u4

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 gnutls28.

References

low severity

CVE-2024-26458

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm krb5/libgssapi-krb5-2@1.18.3-6+deb11u4
  • Introduced through: buildpack-deps@bullseye-scm krb5/libk5crypto3@1.18.3-6+deb11u4
  • Introduced through: buildpack-deps@bullseye-scm krb5/libkrb5-3@1.18.3-6+deb11u4
  • Introduced through: buildpack-deps@bullseye-scm krb5/libkrb5support0@1.18.3-6+deb11u4

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 krb5.

References

low severity

CVE-2024-26461

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm krb5/libgssapi-krb5-2@1.18.3-6+deb11u4
  • Introduced through: buildpack-deps@bullseye-scm krb5/libk5crypto3@1.18.3-6+deb11u4
  • Introduced through: buildpack-deps@bullseye-scm krb5/libkrb5-3@1.18.3-6+deb11u4
  • Introduced through: buildpack-deps@bullseye-scm krb5/libkrb5support0@1.18.3-6+deb11u4

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 krb5.

References

low severity

CVE-2024-26462

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm krb5/libgssapi-krb5-2@1.18.3-6+deb11u4
  • Introduced through: buildpack-deps@bullseye-scm krb5/libk5crypto3@1.18.3-6+deb11u4
  • Introduced through: buildpack-deps@bullseye-scm krb5/libkrb5-3@1.18.3-6+deb11u4
  • Introduced through: buildpack-deps@bullseye-scm krb5/libkrb5support0@1.18.3-6+deb11u4

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 krb5.

References

low severity

Information Exposure

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm libgcrypt20@1.8.7-6

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 libgcrypt20.

References

low severity

CVE-2023-45918

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm ncurses/libncurses6@6.2+20201114-2+deb11u2
  • Introduced through: buildpack-deps@bullseye-scm ncurses/libncursesw6@6.2+20201114-2+deb11u2
  • Introduced through: buildpack-deps@bullseye-scm ncurses/libtinfo6@6.2+20201114-2+deb11u2
  • Introduced through: buildpack-deps@bullseye-scm ncurses/ncurses-base@6.2+20201114-2+deb11u2
  • Introduced through: buildpack-deps@bullseye-scm ncurses/ncurses-bin@6.2+20201114-2+deb11u2

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 ncurses.

References

low severity
new

CVE-2024-28182

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm nghttp2/libnghttp2-14@1.43.0-1+deb11u1

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

There is no fixed version for Debian:11 nghttp2.

References

low severity
new

CVE-2024-2511

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm openssl@1.1.1w-0+deb11u1
  • Introduced through: buildpack-deps@bullseye-scm openssl/libssl1.1@1.1.1w-0+deb11u1

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

There is no fixed version for Debian:11 openssl.

References

low severity

CVE-2023-6597

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm python3.9@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/libpython3.9-minimal@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/libpython3.9-stdlib@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/python3.9-minimal@3.9.2-1

NVD Description

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

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

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

Remediation

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

References

low severity

CVE-2024-0450

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm python3.9@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/libpython3.9-minimal@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/libpython3.9-stdlib@3.9.2-1
  • Introduced through: buildpack-deps@bullseye-scm python3.9/python3.9-minimal@3.9.2-1

NVD Description

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

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

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

Remediation

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

References

low severity

CVE-2023-50868

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

Detailed paths

  • Introduced through: buildpack-deps@bullseye-scm systemd/libsystemd0@247.3-7+deb11u4
  • Introduced through: buildpack-deps@bullseye-scm systemd/libudev1@247.3-7+deb11u4

NVD Description

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

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

Remediation

There is no fixed version for Debian:11 systemd.

References