Vulnerabilities

127 via 280 paths

Dependencies

166

Source

Group 6 Copy Created with Sketch. Docker

Target OS

debian:12
Test your Docker Hub image against our market leading vulnerability database Sign up for free
Severity
  • 4
  • 14
  • 20
  • 89
Status
  • 127
  • 0
  • 0

critical severity

Out-of-bounds Write

  • Vulnerable module: curl
  • Introduced through: curl@7.88.1-9, curl/libcurl3-gnutls@7.88.1-9 and others
  • Fixed in: 7.88.1-10+deb12u4

Detailed paths

  • Introduced through: buildpack-deps@testing-scm curl@7.88.1-9
  • Introduced through: buildpack-deps@testing-scm curl/libcurl3-gnutls@7.88.1-9
  • Introduced through: buildpack-deps@testing-scm curl/libcurl4@7.88.1-9

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

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

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

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

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

Remediation

Upgrade Debian:12 curl to version 7.88.1-10+deb12u4 or higher.

References

critical severity

CVE-2023-28531

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:9.2p1-2
  • Fixed in: 1:9.2p1-2+deb12u2

Detailed paths

  • Introduced through: buildpack-deps@testing-scm openssh/openssh-client@1:9.2p1-2

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

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

Remediation

Upgrade Debian:12 openssh to version 1:9.2p1-2+deb12u2 or higher.

References

critical severity

Unquoted Search Path or Element

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:9.2p1-2
  • Fixed in: 1:9.2p1-2+deb12u1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm openssh/openssh-client@1:9.2p1-2

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

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

Remediation

Upgrade Debian:12 openssh to version 1:9.2p1-2+deb12u1 or higher.

References

critical severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: buildpack-deps@testing-scm zlib/zlib1g@1:1.2.13.dfsg-1

NVD Description

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

References

high severity

Out-of-bounds Write

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.36-9 and glibc/libc6@2.36-9
  • Fixed in: 2.36-9+deb12u3

Detailed paths

  • Introduced through: buildpack-deps@testing-scm glibc/libc-bin@2.36-9
  • Introduced through: buildpack-deps@testing-scm glibc/libc6@2.36-9

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

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

Remediation

Upgrade Debian:12 glibc to version 2.36-9+deb12u3 or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.36-9 and glibc/libc6@2.36-9
  • Fixed in: 2.36-9+deb12u4

Detailed paths

  • Introduced through: buildpack-deps@testing-scm glibc/libc-bin@2.36-9
  • Introduced through: buildpack-deps@testing-scm glibc/libc6@2.36-9

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

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

Remediation

Upgrade Debian:12 glibc to version 2.36-9+deb12u4 or higher.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: libcap2
  • Introduced through: libcap2@1:2.66-3
  • Fixed in: 1:2.66-4

Detailed paths

  • Introduced through: buildpack-deps@testing-scm libcap2@1:2.66-3

NVD Description

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

A vulnerability was found in libcap. This issue occurs in the _libcap_strdup() function and can lead to an integer overflow if the input string is close to 4GiB.

Remediation

Upgrade Debian:12 libcap2 to version 1:2.66-4 or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: perl
  • Introduced through: perl@5.36.0-7, perl/libperl5.36@5.36.0-7 and others
  • Fixed in: 5.36.0-7+deb12u1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm perl@5.36.0-7
  • Introduced through: buildpack-deps@testing-scm perl/libperl5.36@5.36.0-7
  • Introduced through: buildpack-deps@testing-scm perl/perl-base@5.36.0-7
  • Introduced through: buildpack-deps@testing-scm perl/perl-modules-5.36@5.36.0-7

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

A vulnerability was found in perl. This issue occurs when a crafted regular expression is compiled by perl, which can allow an attacker controlled byte buffer overflow in a heap allocated buffer.

Remediation

Upgrade Debian:12 perl to version 5.36.0-7+deb12u1 or higher.

References

high severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: curl
  • Introduced through: curl@7.88.1-9, curl/libcurl3-gnutls@7.88.1-9 and others
  • Fixed in: 7.88.1-10+deb12u3

Detailed paths

  • Introduced through: buildpack-deps@testing-scm curl@7.88.1-9
  • Introduced through: buildpack-deps@testing-scm curl/libcurl3-gnutls@7.88.1-9
  • Introduced through: buildpack-deps@testing-scm curl/libcurl4@7.88.1-9

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

When curl retrieves an HTTP response, it stores the incoming headers so that they can be accessed later via the libcurl headers API.

However, curl did not have a limit in how many or how large headers it would accept in a response, allowing a malicious server to stream an endless series of headers and eventually cause curl to run out of heap memory.

Remediation

Upgrade Debian:12 curl to version 7.88.1-10+deb12u3 or higher.

References

high severity

Use After Free

  • Vulnerable module: curl
  • Introduced through: curl@7.88.1-9, curl/libcurl3-gnutls@7.88.1-9 and others
  • Fixed in: 7.88.1-10

Detailed paths

  • Introduced through: buildpack-deps@testing-scm curl@7.88.1-9
  • Introduced through: buildpack-deps@testing-scm curl/libcurl3-gnutls@7.88.1-9
  • Introduced through: buildpack-deps@testing-scm curl/libcurl4@7.88.1-9

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

A use after free vulnerability exists in curl <v8.1.0 in the way libcurl offers a feature to verify an SSH server's public key using a SHA 256 hash. When this check fails, libcurl would free the memory for the fingerprint before it returns an error message containing the (now freed) hash. This flaw risks inserting sensitive heap-based data into the error message that might be shown to users or otherwise get leaked and revealed.

Remediation

Upgrade Debian:12 curl to version 7.88.1-10 or higher.

References

high severity

Resource Exhaustion

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

Detailed paths

  • Introduced through: buildpack-deps@testing-scm expat/libexpat1@2.5.0-1

NVD Description

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

References

high severity

Out-of-bounds Write

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.36-9 and glibc/libc6@2.36-9
  • Fixed in: 2.36-9+deb12u4

Detailed paths

  • Introduced through: buildpack-deps@testing-scm glibc/libc-bin@2.36-9
  • Introduced through: buildpack-deps@testing-scm glibc/libc6@2.36-9

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

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

Remediation

Upgrade Debian:12 glibc to version 2.36-9+deb12u4 or higher.

References

high severity

Improper Verification of Cryptographic Signature

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.7.9-2
  • Fixed in: 3.7.9-2+deb12u2

Detailed paths

  • Introduced through: buildpack-deps@testing-scm gnutls28/libgnutls30@3.7.9-2

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

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

Remediation

Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u2 or higher.

References

high severity

Information Exposure

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.7.9-2
  • Fixed in: 3.7.9-2+deb12u2

Detailed paths

  • Introduced through: buildpack-deps@testing-scm gnutls28/libgnutls30@3.7.9-2

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

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

Remediation

Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u2 or higher.

References

high severity

Resource Exhaustion

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

Detailed paths

  • Introduced through: buildpack-deps@testing-scm nghttp2/libnghttp2-14@1.52.0-1

NVD Description

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

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

Remediation

Upgrade Debian:12 nghttp2 to version 1.52.0-1+deb12u1 or higher.

References

high severity

CVE-2023-5363

  • Vulnerable module: openssl
  • Introduced through: openssl@3.0.8-1 and openssl/libssl3@3.0.8-1
  • Fixed in: 3.0.11-1~deb12u2

Detailed paths

  • Introduced through: buildpack-deps@testing-scm openssl@3.0.8-1
  • Introduced through: buildpack-deps@testing-scm openssl/libssl3@3.0.8-1

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

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

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

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

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

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

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

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

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

OpenSSL 3.1 and 3.0 are vulnerable to this issue.

Remediation

Upgrade Debian:12 openssl to version 3.0.11-1~deb12u2 or higher.

References

high severity

Improper Certificate Validation

  • Vulnerable module: openssl
  • Introduced through: openssl@3.0.8-1 and openssl/libssl3@3.0.8-1
  • Fixed in: 3.0.9-1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm openssl@3.0.8-1
  • Introduced through: buildpack-deps@testing-scm openssl/libssl3@3.0.8-1

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

A security vulnerability has been identified in all supported versions

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

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

Remediation

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

References

high severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@252.6-1 and systemd/libudev1@252.6-1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm systemd/libsystemd0@252.6-1
  • Introduced through: buildpack-deps@testing-scm systemd/libudev1@252.6-1

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:12 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:12 systemd.

References

medium severity

CVE-2023-46218

  • Vulnerable module: curl
  • Introduced through: curl@7.88.1-9, curl/libcurl3-gnutls@7.88.1-9 and others
  • Fixed in: 7.88.1-10+deb12u5

Detailed paths

  • Introduced through: buildpack-deps@testing-scm curl@7.88.1-9
  • Introduced through: buildpack-deps@testing-scm curl/libcurl3-gnutls@7.88.1-9
  • Introduced through: buildpack-deps@testing-scm curl/libcurl4@7.88.1-9

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

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

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

Remediation

Upgrade Debian:12 curl to version 7.88.1-10+deb12u5 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.36-9 and glibc/libc6@2.36-9
  • Fixed in: 2.36-9+deb12u3

Detailed paths

  • Introduced through: buildpack-deps@testing-scm glibc/libc-bin@2.36-9
  • Introduced through: buildpack-deps@testing-scm glibc/libc6@2.36-9

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

A flaw was found in glibc. When the getaddrinfo function is called with the AF_UNSPEC address family and the system is configured with no-aaaa mode via /etc/resolv.conf, a DNS response via TCP larger than 2048 bytes can potentially disclose stack contents through the function returned address data, and may cause a crash.

Remediation

Upgrade Debian:12 glibc to version 2.36-9+deb12u3 or higher.

References

medium severity

Access of Uninitialized Pointer

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

Detailed paths

  • Introduced through: buildpack-deps@testing-scm krb5/libgssapi-krb5-2@1.20.1-1+b1
  • Introduced through: buildpack-deps@testing-scm krb5/libk5crypto3@1.20.1-1+b1
  • Introduced through: buildpack-deps@testing-scm krb5/libkrb5-3@1.20.1-1+b1
  • Introduced through: buildpack-deps@testing-scm krb5/libkrb5support0@1.20.1-1+b1

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

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

Remediation

Upgrade Debian:12 krb5 to version 1.20.1-2+deb12u1 or higher.

References

medium severity

OS Command Injection

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:9.2p1-2
  • Fixed in: 1:9.2p1-2+deb12u2

Detailed paths

  • Introduced through: buildpack-deps@testing-scm openssh/openssh-client@1:9.2p1-2

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

In ssh in OpenSSH before 9.6, OS command injection might occur if a user name or host name has shell metacharacters, and this name is referenced by an expansion token in certain situations. For example, an untrusted Git repository can have a submodule with shell metacharacters in a user name or host name.

Remediation

Upgrade Debian:12 openssh to version 1:9.2p1-2+deb12u2 or higher.

References

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: openssl
  • Introduced through: openssl@3.0.8-1 and openssl/libssl3@3.0.8-1
  • Fixed in: 3.0.9-1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm openssl@3.0.8-1
  • Introduced through: buildpack-deps@testing-scm openssl/libssl3@3.0.8-1

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

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

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

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

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

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

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

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

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

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

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

Remediation

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

References

medium severity

Improper Certificate Validation

  • Vulnerable module: curl
  • Introduced through: curl@7.88.1-9, curl/libcurl3-gnutls@7.88.1-9 and others
  • Fixed in: 7.88.1-10

Detailed paths

  • Introduced through: buildpack-deps@testing-scm curl@7.88.1-9
  • Introduced through: buildpack-deps@testing-scm curl/libcurl3-gnutls@7.88.1-9
  • Introduced through: buildpack-deps@testing-scm curl/libcurl4@7.88.1-9

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

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

Remediation

Upgrade Debian:12 curl to version 7.88.1-10 or higher.

References

medium severity

Use After Free

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.36-9 and glibc/libc6@2.36-9
  • Fixed in: 2.36-9+deb12u3

Detailed paths

  • Introduced through: buildpack-deps@testing-scm glibc/libc-bin@2.36-9
  • Introduced through: buildpack-deps@testing-scm glibc/libc6@2.36-9

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

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

Remediation

Upgrade Debian:12 glibc to version 2.36-9+deb12u3 or higher.

References

medium severity

Information Exposure

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.7.9-2
  • Fixed in: 3.7.9-2+deb12u1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm gnutls28/libgnutls30@3.7.9-2

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

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

Remediation

Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u1 or higher.

References

medium severity

Improper Validation of Integrity Check Value

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:9.2p1-2
  • Fixed in: 1:9.2p1-2+deb12u2

Detailed paths

  • Introduced through: buildpack-deps@testing-scm openssh/openssh-client@1:9.2p1-2

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

The SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 and other products, allows remote attackers to bypass integrity checks such that some packets are omitted (from the extension negotiation message), and a client and server may consequently end up with a connection for which some security features have been downgraded or disabled, aka a Terrapin attack. This occurs because the SSH Binary Packet Protocol (BPP), implemented by these extensions, mishandles the handshake phase and mishandles use of sequence numbers. For example, there is an effective attack against SSH's use of ChaCha20-Poly1305 (and CBC with Encrypt-then-MAC). The bypass occurs in chacha20-poly1305@openssh.com and (if CBC is used) the -etm@openssh.com MAC algorithms. This also affects Maverick Synergy Java SSH API before 3.1.0-SNAPSHOT, Dropbear through 2022.83, Ssh before 5.1.1 in Erlang/OTP, PuTTY before 0.80, AsyncSSH before 2.14.2, golang.org/x/crypto before 0.17.0, libssh before 0.10.6, libssh2 through 1.11.0, Thorn Tech SFTP Gateway before 3.4.6, Tera Term before 5.1, Paramiko before 3.4.0, jsch before 0.2.15, SFTPGo before 2.5.6, Netgate pfSense Plus through 23.09.1, Netgate pfSense CE through 2.7.2, HPN-SSH through 18.2.0, ProFTPD before 1.3.8b (and before 1.3.9rc2), ORYX CycloneSSH before 2.3.4, NetSarang XShell 7 before Build 0144, CrushFTP before 10.6.0, ConnectBot SSH library before 2.2.22, Apache MINA sshd through 2.11.0, sshj through 0.37.0, TinySSH through 20230101, trilead-ssh2 6401, LANCOM LCOS and LANconfig, FileZilla before 3.66.4, Nova before 11.8, PKIX-SSH before 14.4, SecureCRT before 9.4.3, Transmit5 before 5.10.4, Win32-OpenSSH before 9.5.0.0p1-Beta, WinSCP before 6.2.2, Bitvise SSH Server before 9.32, Bitvise SSH Client before 9.33, KiTTY through 0.76.1.13, the net-ssh gem 7.2.0 for Ruby, the mscdex ssh2 module before 1.15.0 for Node.js, the thrussh library before 0.35.1 for Rust, and the Russh crate before 0.40.2 for Rust.

Remediation

Upgrade Debian:12 openssh to version 1:9.2p1-2+deb12u2 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: openssl
  • Introduced through: openssl@3.0.8-1 and openssl/libssl3@3.0.8-1
  • Fixed in: 3.0.9-1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm openssl@3.0.8-1
  • Introduced through: buildpack-deps@testing-scm openssl/libssl3@3.0.8-1

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

Issue summary: The AES-XTS cipher decryption implementation for 64 bit ARM platform contains a bug that could cause it to read past the input buffer, leading to a crash.

Impact summary: Applications that use the AES-XTS algorithm on the 64 bit ARM platform can crash in rare circumstances. The AES-XTS algorithm is usually used for disk encryption.

The AES-XTS cipher decryption implementation for 64 bit ARM platform will read past the end of the ciphertext buffer if the ciphertext size is 4 mod 5 in 16 byte blocks, e.g. 144 bytes or 1024 bytes. If the memory after the ciphertext buffer is unmapped, this will trigger a crash which results in a denial of service.

If an attacker can control the size and location of the ciphertext buffer being decrypted by an application using AES-XTS on 64 bit ARM, the application is affected. This is fairly unlikely making this issue a Low severity one.

Remediation

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

References

medium severity

CVE-2023-7008

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@252.6-1 and systemd/libudev1@252.6-1
  • Fixed in: 252.21-1~deb12u1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm systemd/libsystemd0@252.6-1
  • Introduced through: buildpack-deps@testing-scm systemd/libudev1@252.6-1

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

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

Remediation

Upgrade Debian:12 systemd to version 252.21-1~deb12u1 or higher.

References

medium severity

CVE-2023-51384

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:9.2p1-2
  • Fixed in: 1:9.2p1-2+deb12u2

Detailed paths

  • Introduced through: buildpack-deps@testing-scm openssh/openssh-client@1:9.2p1-2

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

In ssh-agent in OpenSSH before 9.6, certain destination constraints can be incompletely applied. When destination constraints are specified during addition of PKCS#11-hosted private keys, these constraints are only applied to the first key, even if a PKCS#11 token returns multiple keys.

Remediation

Upgrade Debian:12 openssh to version 1:9.2p1-2+deb12u2 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: tar
  • Introduced through: tar@1.34+dfsg-1.2
  • Fixed in: 1.34+dfsg-1.2+deb12u1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm tar@1.34+dfsg-1.2

NVD Description

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

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

Remediation

Upgrade Debian:12 tar to version 1.34+dfsg-1.2+deb12u1 or higher.

References

medium severity

Missing Encryption of Sensitive Data

  • Vulnerable module: curl
  • Introduced through: curl@7.88.1-9, curl/libcurl3-gnutls@7.88.1-9 and others
  • Fixed in: 7.88.1-10+deb12u5

Detailed paths

  • Introduced through: buildpack-deps@testing-scm curl@7.88.1-9
  • Introduced through: buildpack-deps@testing-scm curl/libcurl3-gnutls@7.88.1-9
  • Introduced through: buildpack-deps@testing-scm curl/libcurl4@7.88.1-9

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

When saving HSTS data to an excessively long file name, curl could end up removing all contents, making subsequent requests using that file unaware of the HSTS status they should otherwise use.

Remediation

Upgrade Debian:12 curl to version 7.88.1-10+deb12u5 or higher.

References

medium severity

Incorrect Calculation of Buffer Size

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.36-9 and glibc/libc6@2.36-9
  • Fixed in: 2.36-9+deb12u4

Detailed paths

  • Introduced through: buildpack-deps@testing-scm glibc/libc-bin@2.36-9
  • Introduced through: buildpack-deps@testing-scm glibc/libc6@2.36-9

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

An integer overflow was found in the __vsyslog_internal function of the glibc library. This function is called by the syslog and vsyslog functions. This issue occurs when these functions are called with a very long message, leading to an incorrect calculation of the buffer size to store the message, resulting in undefined behavior. This issue affects glibc 2.37 and newer.

Remediation

Upgrade Debian:12 glibc to version 2.36-9+deb12u4 or higher.

References

medium severity

Excessive Iteration

  • Vulnerable module: openssl
  • Introduced through: openssl@3.0.8-1 and openssl/libssl3@3.0.8-1
  • Fixed in: 3.0.10-1~deb12u1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm openssl@3.0.8-1
  • Introduced through: buildpack-deps@testing-scm openssl/libssl3@3.0.8-1

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

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

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

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

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

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

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

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

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

Remediation

Upgrade Debian:12 openssl to version 3.0.10-1~deb12u1 or higher.

References

medium severity

Improper Authentication

  • Vulnerable module: openssl
  • Introduced through: openssl@3.0.8-1 and openssl/libssl3@3.0.8-1
  • Fixed in: 3.0.10-1~deb12u1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm openssl@3.0.8-1
  • Introduced through: buildpack-deps@testing-scm openssl/libssl3@3.0.8-1

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

Issue summary: The AES-SIV cipher implementation contains a bug that causes it to ignore empty associated data entries which are unauthenticated as a consequence.

Impact summary: Applications that use the AES-SIV algorithm and want to authenticate empty data entries as associated data can be mislead by removing adding or reordering such empty entries as these are ignored by the OpenSSL implementation. We are currently unaware of any such applications.

The AES-SIV algorithm allows for authentication of multiple associated data entries along with the encryption. To authenticate empty data the application has to call EVP_EncryptUpdate() (or EVP_CipherUpdate()) with NULL pointer as the output buffer and 0 as the input buffer length. The AES-SIV implementation in OpenSSL just returns success for such a call instead of performing the associated data authentication operation. The empty data thus will not be authenticated.

As this issue does not affect non-empty associated data authentication and we expect it to be rare for an application to use empty associated data entries this is qualified as Low severity issue.

Remediation

Upgrade Debian:12 openssl to version 3.0.10-1~deb12u1 or higher.

References

medium severity

Improper Certificate Validation

  • Vulnerable module: openssl
  • Introduced through: openssl@3.0.8-1 and openssl/libssl3@3.0.8-1
  • Fixed in: 3.0.9-1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm openssl@3.0.8-1
  • Introduced through: buildpack-deps@testing-scm openssl/libssl3@3.0.8-1

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

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

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

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

Remediation

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

References

medium severity

Improper Certificate Validation

  • Vulnerable module: openssl
  • Introduced through: openssl@3.0.8-1 and openssl/libssl3@3.0.8-1
  • Fixed in: 3.0.9-1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm openssl@3.0.8-1
  • Introduced through: buildpack-deps@testing-scm openssl/libssl3@3.0.8-1

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

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

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

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

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

Remediation

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

References

medium severity

Inefficient Regular Expression Complexity

  • Vulnerable module: openssl
  • Introduced through: openssl@3.0.8-1 and openssl/libssl3@3.0.8-1
  • Fixed in: 3.0.10-1~deb12u1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm openssl@3.0.8-1
  • Introduced through: buildpack-deps@testing-scm openssl/libssl3@3.0.8-1

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

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

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

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

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

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

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

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

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

Remediation

Upgrade Debian:12 openssl to version 3.0.10-1~deb12u1 or higher.

References

low severity

Out-of-Bounds

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.36-9 and glibc/libc6@2.36-9

Detailed paths

  • Introduced through: buildpack-deps@testing-scm glibc/libc-bin@2.36-9
  • Introduced through: buildpack-deps@testing-scm glibc/libc6@2.36-9

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:12 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:12 glibc.

References

low severity

CVE-2005-2541

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

Detailed paths

  • Introduced through: buildpack-deps@testing-scm tar@1.34+dfsg-1.2

NVD Description

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

References

low severity

Improper Input Validation

  • Vulnerable module: git
  • Introduced through: git@1:2.39.2-1.1 and git/git-man@1:2.39.2-1.1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm git@1:2.39.2-1.1
  • Introduced through: buildpack-deps@testing-scm git/git-man@1:2.39.2-1.1

NVD Description

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

References

low severity

CVE-2019-1010023

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.36-9 and glibc/libc6@2.36-9

Detailed paths

  • Introduced through: buildpack-deps@testing-scm glibc/libc-bin@2.36-9
  • Introduced through: buildpack-deps@testing-scm glibc/libc6@2.36-9

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:12 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:12 glibc.

References

low severity

Improper Certificate Validation

  • Vulnerable module: perl
  • Introduced through: perl@5.36.0-7, perl/libperl5.36@5.36.0-7 and others

Detailed paths

  • Introduced through: buildpack-deps@testing-scm perl@5.36.0-7
  • Introduced through: buildpack-deps@testing-scm perl/libperl5.36@5.36.0-7
  • Introduced through: buildpack-deps@testing-scm perl/perl-base@5.36.0-7
  • Introduced through: buildpack-deps@testing-scm perl/perl-modules-5.36@5.36.0-7

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:12 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:12 perl.

References

low severity

Improper Certificate Validation

  • Vulnerable module: perl
  • Introduced through: perl@5.36.0-7, perl/libperl5.36@5.36.0-7 and others

Detailed paths

  • Introduced through: buildpack-deps@testing-scm perl@5.36.0-7
  • Introduced through: buildpack-deps@testing-scm perl/libperl5.36@5.36.0-7
  • Introduced through: buildpack-deps@testing-scm perl/perl-base@5.36.0-7
  • Introduced through: buildpack-deps@testing-scm perl/perl-modules-5.36@5.36.0-7

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:12 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:12 perl.

References

low severity

Arbitrary Code Injection

  • Vulnerable module: git
  • Introduced through: git@1:2.39.2-1.1 and git/git-man@1:2.39.2-1.1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm git@1:2.39.2-1.1
  • Introduced through: buildpack-deps@testing-scm git/git-man@1:2.39.2-1.1

NVD Description

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

References

low severity

OS Command Injection

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:9.2p1-2

Detailed paths

  • Introduced through: buildpack-deps@testing-scm openssh/openssh-client@1:9.2p1-2

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:12 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:12 openssh.

References

low severity

Incorrect Permission Assignment for Critical Resource

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.13+dfsg1-1+b1 and shadow/passwd@1:4.13+dfsg1-1+b1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm shadow/login@1:4.13+dfsg1-1+b1
  • Introduced through: buildpack-deps@testing-scm shadow/passwd@1:4.13+dfsg1-1+b1

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:12 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:12 shadow.

References

low severity

Directory Traversal

  • Vulnerable module: git
  • Introduced through: git@1:2.39.2-1.1 and git/git-man@1:2.39.2-1.1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm git@1:2.39.2-1.1
  • Introduced through: buildpack-deps@testing-scm git/git-man@1:2.39.2-1.1

NVD Description

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

References

low severity

Exposure of Resource to Wrong Sphere

  • Vulnerable module: git
  • Introduced through: git@1:2.39.2-1.1 and git/git-man@1:2.39.2-1.1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm git@1:2.39.2-1.1
  • Introduced through: buildpack-deps@testing-scm git/git-man@1:2.39.2-1.1

NVD Description

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

References

low severity

Uncontrolled Recursion

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.36-9 and glibc/libc6@2.36-9

Detailed paths

  • Introduced through: buildpack-deps@testing-scm glibc/libc-bin@2.36-9
  • Introduced through: buildpack-deps@testing-scm glibc/libc6@2.36-9

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:12 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:12 glibc.

References

low severity

Uncontrolled Recursion

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.36-9 and glibc/libc6@2.36-9

Detailed paths

  • Introduced through: buildpack-deps@testing-scm glibc/libc-bin@2.36-9
  • Introduced through: buildpack-deps@testing-scm glibc/libc6@2.36-9

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:12 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:12 glibc.

References

low severity

Integer Overflow or Wraparound

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.20.1-1+b1, krb5/libk5crypto3@1.20.1-1+b1 and others

Detailed paths

  • Introduced through: buildpack-deps@testing-scm krb5/libgssapi-krb5-2@1.20.1-1+b1
  • Introduced through: buildpack-deps@testing-scm krb5/libk5crypto3@1.20.1-1+b1
  • Introduced through: buildpack-deps@testing-scm krb5/libkrb5-3@1.20.1-1+b1
  • Introduced through: buildpack-deps@testing-scm krb5/libkrb5support0@1.20.1-1+b1

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:12 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:12 krb5.

References

low severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: libgcrypt20
  • Introduced through: libgcrypt20@1.10.1-3

Detailed paths

  • Introduced through: buildpack-deps@testing-scm libgcrypt20@1.10.1-3

NVD Description

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

References

low severity

Cryptographic Issues

  • Vulnerable module: openldap/libldap-2.5-0
  • Introduced through: openldap/libldap-2.5-0@2.5.13+dfsg-5

Detailed paths

  • Introduced through: buildpack-deps@testing-scm openldap/libldap-2.5-0@2.5.13+dfsg-5

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

References

low severity

NULL Pointer Dereference

  • Vulnerable module: openldap/libldap-2.5-0
  • Introduced through: openldap/libldap-2.5-0@2.5.13+dfsg-5

Detailed paths

  • Introduced through: buildpack-deps@testing-scm openldap/libldap-2.5-0@2.5.13+dfsg-5

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

References

low severity

Out-of-Bounds

  • Vulnerable module: openldap/libldap-2.5-0
  • Introduced through: openldap/libldap-2.5-0@2.5.13+dfsg-5

Detailed paths

  • Introduced through: buildpack-deps@testing-scm openldap/libldap-2.5-0@2.5.13+dfsg-5

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

References

low severity

Link Following

  • Vulnerable module: perl
  • Introduced through: perl@5.36.0-7, perl/libperl5.36@5.36.0-7 and others

Detailed paths

  • Introduced through: buildpack-deps@testing-scm perl@5.36.0-7
  • Introduced through: buildpack-deps@testing-scm perl/libperl5.36@5.36.0-7
  • Introduced through: buildpack-deps@testing-scm perl/perl-base@5.36.0-7
  • Introduced through: buildpack-deps@testing-scm perl/perl-modules-5.36@5.36.0-7

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:12 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:12 perl.

References

low severity

Improper Input Validation

  • Vulnerable module: python3.11
  • Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others

Detailed paths

  • Introduced through: buildpack-deps@testing-scm python3.11@3.11.2-6
  • Introduced through: buildpack-deps@testing-scm python3.11/libpython3.11-minimal@3.11.2-6
  • Introduced through: buildpack-deps@testing-scm python3.11/libpython3.11-stdlib@3.11.2-6
  • Introduced through: buildpack-deps@testing-scm python3.11/python3.11-minimal@3.11.2-6

NVD Description

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

References

low severity

Untrusted Search Path

  • Vulnerable module: python3.11
  • Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others

Detailed paths

  • Introduced through: buildpack-deps@testing-scm python3.11@3.11.2-6
  • Introduced through: buildpack-deps@testing-scm python3.11/libpython3.11-minimal@3.11.2-6
  • Introduced through: buildpack-deps@testing-scm python3.11/libpython3.11-stdlib@3.11.2-6
  • Introduced through: buildpack-deps@testing-scm python3.11/python3.11-minimal@3.11.2-6

NVD Description

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

An issue was discovered in Python 3.11 through 3.11.4. If a path containing '\0' bytes is passed to os.path.normpath(), the path will be truncated unexpectedly at the first '\0' byte. There are plausible cases in which an application would have rejected a filename for security reasons in Python 3.10.x or earlier, but that filename is no longer rejected in Python 3.11.x.

Remediation

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

References

low severity

Out-of-Bounds

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.40.1-2

Detailed paths

  • Introduced through: buildpack-deps@testing-scm sqlite3/libsqlite3-0@3.40.1-2

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

References

low severity

CVE-2023-51767

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:9.2p1-2

Detailed paths

  • Introduced through: buildpack-deps@testing-scm openssh/openssh-client@1:9.2p1-2

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:12 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:12 openssh.

References

low severity

Inappropriate Encoding for Output Context

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:9.2p1-2

Detailed paths

  • Introduced through: buildpack-deps@testing-scm openssh/openssh-client@1:9.2p1-2

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:12 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:12 openssh.

References

low severity

Improper Input Validation

  • Vulnerable module: coreutils
  • Introduced through: coreutils@9.1-1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm coreutils@9.1-1

NVD Description

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

References

low severity

CVE-2023-50495

  • Vulnerable module: ncurses/libncursesw6
  • Introduced through: ncurses/libncursesw6@6.4-4, ncurses/libtinfo6@6.4-4 and others

Detailed paths

  • Introduced through: buildpack-deps@testing-scm ncurses/libncursesw6@6.4-4
  • Introduced through: buildpack-deps@testing-scm ncurses/libtinfo6@6.4-4
  • Introduced through: buildpack-deps@testing-scm ncurses/ncurses-base@6.4-4
  • Introduced through: buildpack-deps@testing-scm ncurses/ncurses-bin@6.4-4

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:12 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:12 ncurses.

References

low severity

Out-of-bounds Write

  • Vulnerable module: openssl
  • Introduced through: openssl@3.0.8-1 and openssl/libssl3@3.0.8-1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm openssl@3.0.8-1
  • Introduced through: buildpack-deps@testing-scm openssl/libssl3@3.0.8-1

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

Issue summary: The POLY1305 MAC (message authentication code) implementation contains a bug that might corrupt the internal state of applications running on PowerPC CPU based platforms if the CPU provides vector instructions.

Impact summary: If an attacker can influence whether the POLY1305 MAC algorithm is used, the application state might be corrupted with various application dependent consequences.

The POLY1305 MAC (message authentication code) implementation in OpenSSL for PowerPC CPUs restores the contents of vector registers in a different order than they are saved. Thus the contents of some of these vector registers are corrupted when returning to the caller. The vulnerable code is used only on newer PowerPC processors supporting the PowerISA 2.07 instructions.

The consequences of this kind of internal application state corruption can be various - from no consequences, if the calling application does not depend on the contents of non-volatile XMM registers at all, to the worst consequences, where the attacker could get complete control of the application process. However unless the compiler uses the vector registers for storing pointers, the most likely consequence, if any, would be an incorrect result of some application dependent calculations or a crash leading to a denial of service.

The POLY1305 MAC algorithm is most frequently used as part of the CHACHA20-POLY1305 AEAD (authenticated encryption with associated data) algorithm. The most common usage of this AEAD cipher is with TLS protocol versions 1.2 and 1.3. If this cipher is enabled on the server a malicious client can influence whether this AEAD cipher is used. This implies that TLS server applications using OpenSSL can be potentially impacted. However we are currently not aware of any concrete application that would be affected by this issue therefore we consider this a Low severity security issue.

Remediation

There is no fixed version for Debian:12 openssl.

References

low severity

Access Restriction Bypass

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:9.2p1-2

Detailed paths

  • Introduced through: buildpack-deps@testing-scm openssh/openssh-client@1:9.2p1-2

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:12 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:12 openssh.

References

low severity

Access Restriction Bypass

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.13+dfsg1-1+b1 and shadow/passwd@1:4.13+dfsg1-1+b1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm shadow/login@1:4.13+dfsg1-1+b1
  • Introduced through: buildpack-deps@testing-scm shadow/passwd@1:4.13+dfsg1-1+b1

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:12 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:12 shadow.

References

low severity

Open Redirect

  • Vulnerable module: wget/wget
  • Introduced through: wget/wget@1.21.3-1+b2

Detailed paths

  • Introduced through: buildpack-deps@testing-scm wget/wget@1.21.3-1+b2

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

References

low severity

Race Condition

  • Vulnerable module: curl
  • Introduced through: curl@7.88.1-9, curl/libcurl3-gnutls@7.88.1-9 and others
  • Fixed in: 7.88.1-10

Detailed paths

  • Introduced through: buildpack-deps@testing-scm curl@7.88.1-9
  • Introduced through: buildpack-deps@testing-scm curl/libcurl3-gnutls@7.88.1-9
  • Introduced through: buildpack-deps@testing-scm curl/libcurl4@7.88.1-9

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

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

Remediation

Upgrade Debian:12 curl to version 7.88.1-10 or higher.

References

low severity

Information Exposure

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:9.2p1-2

Detailed paths

  • Introduced through: buildpack-deps@testing-scm openssh/openssh-client@1:9.2p1-2

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:12 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:12 openssh.

References

low severity

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

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

Detailed paths

  • Introduced through: buildpack-deps@testing-scm expat/libexpat1@2.5.0-1

NVD Description

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

References

low severity

Uncontrolled Recursion

  • Vulnerable module: gcc-12/gcc-12-base
  • Introduced through: gcc-12/gcc-12-base@12.2.0-14, gcc-12/libgcc-s1@12.2.0-14 and others

Detailed paths

  • Introduced through: buildpack-deps@testing-scm gcc-12/gcc-12-base@12.2.0-14
  • Introduced through: buildpack-deps@testing-scm gcc-12/libgcc-s1@12.2.0-14
  • Introduced through: buildpack-deps@testing-scm gcc-12/libstdc++6@12.2.0-14

NVD Description

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

libiberty/rust-demangle.c in GNU GCC 11.2 allows stack consumption in demangle_const, as demonstrated by nm-new.

Remediation

There is no fixed version for Debian:12 gcc-12.

References

low severity

CVE-2024-0727

  • Vulnerable module: openssl
  • Introduced through: openssl@3.0.8-1 and openssl/libssl3@3.0.8-1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm openssl@3.0.8-1
  • Introduced through: buildpack-deps@testing-scm openssl/libssl3@3.0.8-1

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:12 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:12 openssl.

References

low severity

CVE-2024-22365

  • Vulnerable module: pam/libpam-modules
  • Introduced through: pam/libpam-modules@1.5.2-6, pam/libpam-modules-bin@1.5.2-6 and others

Detailed paths

  • Introduced through: buildpack-deps@testing-scm pam/libpam-modules@1.5.2-6
  • Introduced through: buildpack-deps@testing-scm pam/libpam-modules-bin@1.5.2-6
  • Introduced through: buildpack-deps@testing-scm pam/libpam-runtime@1.5.2-6
  • Introduced through: buildpack-deps@testing-scm pam/libpam0g@1.5.2-6

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:12 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:12 pam.

References

low severity

Improper Authentication

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.13+dfsg1-1+b1 and shadow/passwd@1:4.13+dfsg1-1+b1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm shadow/login@1:4.13+dfsg1-1+b1
  • Introduced through: buildpack-deps@testing-scm shadow/passwd@1:4.13+dfsg1-1+b1

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:12 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:12 shadow.

References

low severity

Use After Free

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.40.1-2

Detailed paths

  • Introduced through: buildpack-deps@testing-scm sqlite3/libsqlite3-0@3.40.1-2

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

A heap use-after-free issue has been identified in SQLite in the jsonParseAddNodeArray() function in sqlite3.c. This flaw allows a local attacker to leverage a victim to pass specially crafted malicious input to the application, potentially causing a crash and leading to a denial of service.

Remediation

There is no fixed version for Debian:12 sqlite3.

References

low severity

Information Exposure

  • Vulnerable module: util-linux/bsdutils
  • Introduced through: util-linux/bsdutils@1:2.38.1-5+b1, util-linux/libblkid1@2.38.1-5+b1 and others

Detailed paths

  • Introduced through: buildpack-deps@testing-scm util-linux/bsdutils@1:2.38.1-5+b1
  • Introduced through: buildpack-deps@testing-scm util-linux/libblkid1@2.38.1-5+b1
  • Introduced through: buildpack-deps@testing-scm util-linux/libmount1@2.38.1-5+b1
  • Introduced through: buildpack-deps@testing-scm util-linux/libsmartcols1@2.38.1-5+b1
  • Introduced through: buildpack-deps@testing-scm util-linux/libuuid1@2.38.1-5+b1
  • Introduced through: buildpack-deps@testing-scm util-linux/mount@2.38.1-5+b1
  • Introduced through: buildpack-deps@testing-scm util-linux/util-linux@2.38.1-5+b1
  • Introduced through: buildpack-deps@testing-scm util-linux/util-linux-extra@2.38.1-5+b1

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:12 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:12 util-linux.

References

low severity

Cryptographic Issues

  • Vulnerable module: openssl
  • Introduced through: openssl@3.0.8-1 and openssl/libssl3@3.0.8-1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm openssl@3.0.8-1
  • Introduced through: buildpack-deps@testing-scm openssl/libssl3@3.0.8-1

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:12 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:12 openssl.

References

low severity

Information Exposure

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.36-9 and glibc/libc6@2.36-9

Detailed paths

  • Introduced through: buildpack-deps@testing-scm glibc/libc-bin@2.36-9
  • Introduced through: buildpack-deps@testing-scm glibc/libc6@2.36-9

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:12 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:12 glibc.

References

low severity

Use of Insufficiently Random Values

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.36-9 and glibc/libc6@2.36-9

Detailed paths

  • Introduced through: buildpack-deps@testing-scm glibc/libc-bin@2.36-9
  • Introduced through: buildpack-deps@testing-scm glibc/libc6@2.36-9

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:12 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:12 glibc.

References

low severity

CVE-2016-20012

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:9.2p1-2

Detailed paths

  • Introduced through: buildpack-deps@testing-scm openssh/openssh-client@1:9.2p1-2

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:12 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:12 openssh.

References

low severity

Improper Authentication

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:9.2p1-2

Detailed paths

  • Introduced through: buildpack-deps@testing-scm openssh/openssh-client@1:9.2p1-2

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:12 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:12 openssh.

References

low severity

Information Exposure

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:9.2p1-2

Detailed paths

  • Introduced through: buildpack-deps@testing-scm openssh/openssh-client@1:9.2p1-2

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:12 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:12 openssh.

References

low severity

Improper Check for Unusual or Exceptional Conditions

  • Vulnerable module: openssl
  • Introduced through: openssl@3.0.8-1 and openssl/libssl3@3.0.8-1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm openssl@3.0.8-1
  • Introduced through: buildpack-deps@testing-scm openssl/libssl3@3.0.8-1

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:12 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:12 openssl.

References

low severity

CVE-2023-40217

  • Vulnerable module: python3.11
  • Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others

Detailed paths

  • Introduced through: buildpack-deps@testing-scm python3.11@3.11.2-6
  • Introduced through: buildpack-deps@testing-scm python3.11/libpython3.11-minimal@3.11.2-6
  • Introduced through: buildpack-deps@testing-scm python3.11/libpython3.11-stdlib@3.11.2-6
  • Introduced through: buildpack-deps@testing-scm python3.11/python3.11-minimal@3.11.2-6

NVD Description

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

References

low severity

Improper Input Validation

  • Vulnerable module: python3.11
  • Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others

Detailed paths

  • Introduced through: buildpack-deps@testing-scm python3.11@3.11.2-6
  • Introduced through: buildpack-deps@testing-scm python3.11/libpython3.11-minimal@3.11.2-6
  • Introduced through: buildpack-deps@testing-scm python3.11/libpython3.11-stdlib@3.11.2-6
  • Introduced through: buildpack-deps@testing-scm python3.11/python3.11-minimal@3.11.2-6

NVD Description

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

References

low severity

Improper Validation of Integrity Check Value

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@252.6-1 and systemd/libudev1@252.6-1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm systemd/libsystemd0@252.6-1
  • Introduced through: buildpack-deps@testing-scm systemd/libudev1@252.6-1

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:12 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:12 systemd.

References

low severity

Improper Validation of Integrity Check Value

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@252.6-1 and systemd/libudev1@252.6-1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm systemd/libsystemd0@252.6-1
  • Introduced through: buildpack-deps@testing-scm systemd/libudev1@252.6-1

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:12 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:12 systemd.

References

low severity

Improper Validation of Integrity Check Value

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@252.6-1 and systemd/libudev1@252.6-1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm systemd/libsystemd0@252.6-1
  • Introduced through: buildpack-deps@testing-scm systemd/libudev1@252.6-1

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:12 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:12 systemd.

References

low severity

Cryptographic Issues

  • Vulnerable module: openssl
  • Introduced through: openssl@3.0.8-1 and openssl/libssl3@3.0.8-1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm openssl@3.0.8-1
  • Introduced through: buildpack-deps@testing-scm openssl/libssl3@3.0.8-1

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:12 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:12 openssl.

References

low severity

CVE-2023-4039

  • Vulnerable module: gcc-12/gcc-12-base
  • Introduced through: gcc-12/gcc-12-base@12.2.0-14, gcc-12/libgcc-s1@12.2.0-14 and others

Detailed paths

  • Introduced through: buildpack-deps@testing-scm gcc-12/gcc-12-base@12.2.0-14
  • Introduced through: buildpack-deps@testing-scm gcc-12/libgcc-s1@12.2.0-14
  • Introduced through: buildpack-deps@testing-scm gcc-12/libstdc++6@12.2.0-14

NVD Description

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

References

low severity

Race Condition

  • Vulnerable module: coreutils
  • Introduced through: coreutils@9.1-1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm coreutils@9.1-1

NVD Description

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

References

low severity

Improper Initialization

  • Vulnerable module: openldap/libldap-2.5-0
  • Introduced through: openldap/libldap-2.5-0@2.5.13+dfsg-5

Detailed paths

  • Introduced through: buildpack-deps@testing-scm openldap/libldap-2.5-0@2.5.13+dfsg-5

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

References

low severity

Link Following

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@252.6-1 and systemd/libudev1@252.6-1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm systemd/libsystemd0@252.6-1
  • Introduced through: buildpack-deps@testing-scm systemd/libudev1@252.6-1

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:12 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:12 systemd.

References

low severity

Resource Management Errors

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.36-9 and glibc/libc6@2.36-9

Detailed paths

  • Introduced through: buildpack-deps@testing-scm glibc/libc-bin@2.36-9
  • Introduced through: buildpack-deps@testing-scm glibc/libc6@2.36-9

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:12 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:12 glibc.

References

low severity

Improper Input Validation

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.7.9-2

Detailed paths

  • Introduced through: buildpack-deps@testing-scm gnutls28/libgnutls30@3.7.9-2

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:12 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:12 gnutls28.

References

low severity

Information Exposure

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:9.2p1-2

Detailed paths

  • Introduced through: buildpack-deps@testing-scm openssh/openssh-client@1:9.2p1-2

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:12 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:12 openssh.

References

low severity

Memory Leak

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.40.1-2

Detailed paths

  • Introduced through: buildpack-deps@testing-scm sqlite3/libsqlite3-0@3.40.1-2

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

References

low severity

Improper Certificate Validation

  • Vulnerable module: openldap/libldap-2.5-0
  • Introduced through: openldap/libldap-2.5-0@2.5.13+dfsg-5

Detailed paths

  • Introduced through: buildpack-deps@testing-scm openldap/libldap-2.5-0@2.5.13+dfsg-5

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

References

low severity

Improper Verification of Cryptographic Signature

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

Detailed paths

  • Introduced through: buildpack-deps@testing-scm apt@2.6.0
  • Introduced through: buildpack-deps@testing-scm apt/libapt-pkg6.0@2.6.0

NVD Description

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

References

low severity

CVE-2023-28322

  • Vulnerable module: curl
  • Introduced through: curl@7.88.1-9, curl/libcurl3-gnutls@7.88.1-9 and others
  • Fixed in: 7.88.1-10

Detailed paths

  • Introduced through: buildpack-deps@testing-scm curl@7.88.1-9
  • Introduced through: buildpack-deps@testing-scm curl/libcurl3-gnutls@7.88.1-9
  • Introduced through: buildpack-deps@testing-scm curl/libcurl4@7.88.1-9

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

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

Remediation

Upgrade Debian:12 curl to version 7.88.1-10 or higher.

References

low severity

CVE-2023-38546

  • Vulnerable module: curl
  • Introduced through: curl@7.88.1-9, curl/libcurl3-gnutls@7.88.1-9 and others
  • Fixed in: 7.88.1-10+deb12u4

Detailed paths

  • Introduced through: buildpack-deps@testing-scm curl@7.88.1-9
  • Introduced through: buildpack-deps@testing-scm curl/libcurl3-gnutls@7.88.1-9
  • Introduced through: buildpack-deps@testing-scm curl/libcurl4@7.88.1-9

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

This flaw allows an attacker to insert cookies at will into a running program using libcurl, if the specific series of conditions are met.

libcurl performs transfers. In its API, an application creates "easy handles" that are the individual handles for single transfers.

libcurl provides a function call that duplicates en easy handle called curl_easy_duphandle.

If a transfer has cookies enabled when the handle is duplicated, the cookie-enable state is also cloned - but without cloning the actual cookies. If the source handle did not read any cookies from a specific file on disk, the cloned version of the handle would instead store the file name as none (using the four ASCII letters, no quotes).

Subsequent use of the cloned handle that does not explicitly set a source to load cookies from would then inadvertently load cookies from a file named none - if such a file exists and is readable in the current directory of the program using libcurl. And if using the correct file format of course.

Remediation

Upgrade Debian:12 curl to version 7.88.1-10+deb12u4 or higher.

References

low severity

Out-of-bounds Write

  • Vulnerable module: gnupg2/dirmngr
  • Introduced through: gnupg2/dirmngr@2.2.40-1.1, gnupg2/gnupg@2.2.40-1.1 and others

Detailed paths

  • Introduced through: buildpack-deps@testing-scm gnupg2/dirmngr@2.2.40-1.1
  • Introduced through: buildpack-deps@testing-scm gnupg2/gnupg@2.2.40-1.1
  • Introduced through: buildpack-deps@testing-scm gnupg2/gnupg-l10n@2.2.40-1.1
  • Introduced through: buildpack-deps@testing-scm gnupg2/gnupg-utils@2.2.40-1.1
  • Introduced through: buildpack-deps@testing-scm gnupg2/gpg@2.2.40-1.1
  • Introduced through: buildpack-deps@testing-scm gnupg2/gpg-agent@2.2.40-1.1
  • Introduced through: buildpack-deps@testing-scm gnupg2/gpg-wks-client@2.2.40-1.1
  • Introduced through: buildpack-deps@testing-scm gnupg2/gpg-wks-server@2.2.40-1.1
  • Introduced through: buildpack-deps@testing-scm gnupg2/gpgconf@2.2.40-1.1
  • Introduced through: buildpack-deps@testing-scm gnupg2/gpgsm@2.2.40-1.1
  • Introduced through: buildpack-deps@testing-scm gnupg2/gpgv@2.2.40-1.1

NVD Description

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

References

low severity

Memory Leak

  • Vulnerable module: libcap2
  • Introduced through: libcap2@1:2.66-3
  • Fixed in: 1:2.66-4

Detailed paths

  • Introduced through: buildpack-deps@testing-scm libcap2@1:2.66-3

NVD Description

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

A vulnerability was found in the pthread_create() function in libcap. This issue may allow a malicious actor to use cause __real_pthread_create() to return an error, which can exhaust the process memory.

Remediation

Upgrade Debian:12 libcap2 to version 1:2.66-4 or higher.

References

low severity

Out-of-bounds Write

  • Vulnerable module: procps
  • Introduced through: procps@2:4.0.2-3 and procps/libproc2-0@2:4.0.2-3

Detailed paths

  • Introduced through: buildpack-deps@testing-scm procps@2:4.0.2-3
  • Introduced through: buildpack-deps@testing-scm procps/libproc2-0@2:4.0.2-3

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:12 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:12 procps.

References

low severity

Arbitrary Code Injection

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.13+dfsg1-1+b1 and shadow/passwd@1:4.13+dfsg1-1+b1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm shadow/login@1:4.13+dfsg1-1+b1
  • Introduced through: buildpack-deps@testing-scm shadow/passwd@1:4.13+dfsg1-1+b1

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:12 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:12 shadow.

References

low severity

Use of Externally-Controlled Format String

  • Vulnerable module: git
  • Introduced through: git@1:2.39.2-1.1 and git/git-man@1:2.39.2-1.1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm git@1:2.39.2-1.1
  • Introduced through: buildpack-deps@testing-scm git/git-man@1:2.39.2-1.1

NVD Description

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

References

low severity
new

CVE-2024-2004

  • Vulnerable module: curl
  • Introduced through: curl@7.88.1-9, curl/libcurl3-gnutls@7.88.1-9 and others

Detailed paths

  • Introduced through: buildpack-deps@testing-scm curl@7.88.1-9
  • Introduced through: buildpack-deps@testing-scm curl/libcurl3-gnutls@7.88.1-9
  • Introduced through: buildpack-deps@testing-scm curl/libcurl4@7.88.1-9

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

When a protocol selection parameter option disables all protocols without adding any then the default set of protocols would remain in the allowed set due to an error in the logic for removing protocols. The below command would perform a request to curl.se with a plaintext protocol which has been explicitly disabled. curl --proto -all,-http http://curl.se The flaw is only present if the set of selected protocols disables the entire set of available protocols, in itself a command with no practical use and therefore unlikely to be encountered in real situations. The curl security team has thus assessed this to be low severity bug.

Remediation

There is no fixed version for Debian:12 curl.

References

low severity
new

CVE-2024-2379

  • Vulnerable module: curl
  • Introduced through: curl@7.88.1-9, curl/libcurl3-gnutls@7.88.1-9 and others

Detailed paths

  • Introduced through: buildpack-deps@testing-scm curl@7.88.1-9
  • Introduced through: buildpack-deps@testing-scm curl/libcurl3-gnutls@7.88.1-9
  • Introduced through: buildpack-deps@testing-scm curl/libcurl4@7.88.1-9

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:12 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:12 curl.

References

low severity
new

CVE-2024-2398

  • Vulnerable module: curl
  • Introduced through: curl@7.88.1-9, curl/libcurl3-gnutls@7.88.1-9 and others

Detailed paths

  • Introduced through: buildpack-deps@testing-scm curl@7.88.1-9
  • Introduced through: buildpack-deps@testing-scm curl/libcurl3-gnutls@7.88.1-9
  • Introduced through: buildpack-deps@testing-scm curl/libcurl4@7.88.1-9

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:12 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:12 curl.

References

low severity

CVE-2024-28757

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

Detailed paths

  • Introduced through: buildpack-deps@testing-scm expat/libexpat1@2.5.0-1

NVD Description

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

References

low severity
new

CVE-2024-2961

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.36-9 and glibc/libc6@2.36-9

Detailed paths

  • Introduced through: buildpack-deps@testing-scm glibc/libc-bin@2.36-9
  • Introduced through: buildpack-deps@testing-scm glibc/libc6@2.36-9

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

The iconv() function in the GNU C Library versions 2.39 and older may overflow the output buffer passed to it by up to 4 bytes when converting strings to the ISO-2022-CN-EXT character set, which may be used to crash an application or overwrite a neighbouring variable.

Remediation

There is no fixed version for Debian:12 glibc.

References

low severity
new

Information Exposure

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.7.9-2

Detailed paths

  • Introduced through: buildpack-deps@testing-scm gnutls28/libgnutls30@3.7.9-2

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:12 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:12 gnutls28.

References

low severity
new

Uncaught Exception

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.7.9-2

Detailed paths

  • Introduced through: buildpack-deps@testing-scm gnutls28/libgnutls30@3.7.9-2

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:12 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:12 gnutls28.

References

low severity

CVE-2024-26458

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.20.1-1+b1, krb5/libk5crypto3@1.20.1-1+b1 and others

Detailed paths

  • Introduced through: buildpack-deps@testing-scm krb5/libgssapi-krb5-2@1.20.1-1+b1
  • Introduced through: buildpack-deps@testing-scm krb5/libk5crypto3@1.20.1-1+b1
  • Introduced through: buildpack-deps@testing-scm krb5/libkrb5-3@1.20.1-1+b1
  • Introduced through: buildpack-deps@testing-scm krb5/libkrb5support0@1.20.1-1+b1

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:12 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:12 krb5.

References

low severity

CVE-2024-26461

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.20.1-1+b1, krb5/libk5crypto3@1.20.1-1+b1 and others

Detailed paths

  • Introduced through: buildpack-deps@testing-scm krb5/libgssapi-krb5-2@1.20.1-1+b1
  • Introduced through: buildpack-deps@testing-scm krb5/libk5crypto3@1.20.1-1+b1
  • Introduced through: buildpack-deps@testing-scm krb5/libkrb5-3@1.20.1-1+b1
  • Introduced through: buildpack-deps@testing-scm krb5/libkrb5support0@1.20.1-1+b1

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:12 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:12 krb5.

References

low severity

CVE-2024-26462

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.20.1-1+b1, krb5/libk5crypto3@1.20.1-1+b1 and others

Detailed paths

  • Introduced through: buildpack-deps@testing-scm krb5/libgssapi-krb5-2@1.20.1-1+b1
  • Introduced through: buildpack-deps@testing-scm krb5/libk5crypto3@1.20.1-1+b1
  • Introduced through: buildpack-deps@testing-scm krb5/libkrb5-3@1.20.1-1+b1
  • Introduced through: buildpack-deps@testing-scm krb5/libkrb5support0@1.20.1-1+b1

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:12 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:12 krb5.

References

low severity

Information Exposure

  • Vulnerable module: libgcrypt20
  • Introduced through: libgcrypt20@1.10.1-3

Detailed paths

  • Introduced through: buildpack-deps@testing-scm libgcrypt20@1.10.1-3

NVD Description

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

References

low severity

CVE-2023-45918

  • Vulnerable module: ncurses/libncursesw6
  • Introduced through: ncurses/libncursesw6@6.4-4, ncurses/libtinfo6@6.4-4 and others

Detailed paths

  • Introduced through: buildpack-deps@testing-scm ncurses/libncursesw6@6.4-4
  • Introduced through: buildpack-deps@testing-scm ncurses/libtinfo6@6.4-4
  • Introduced through: buildpack-deps@testing-scm ncurses/ncurses-base@6.4-4
  • Introduced through: buildpack-deps@testing-scm ncurses/ncurses-bin@6.4-4

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:12 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:12 ncurses.

References

low severity
new

CVE-2024-28182

  • Vulnerable module: nghttp2/libnghttp2-14
  • Introduced through: nghttp2/libnghttp2-14@1.52.0-1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm nghttp2/libnghttp2-14@1.52.0-1

NVD Description

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

References

low severity

CVE-2023-6237

  • Vulnerable module: openssl
  • Introduced through: openssl@3.0.8-1 and openssl/libssl3@3.0.8-1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm openssl@3.0.8-1
  • Introduced through: buildpack-deps@testing-scm openssl/libssl3@3.0.8-1

NVD Description

This vulnerability has not been analyzed by NVD yet.

Remediation

There is no fixed version for Debian:12 openssl.

References

low severity
new

CVE-2024-2511

  • Vulnerable module: openssl
  • Introduced through: openssl@3.0.8-1 and openssl/libssl3@3.0.8-1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm openssl@3.0.8-1
  • Introduced through: buildpack-deps@testing-scm openssl/libssl3@3.0.8-1

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:12 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:12 openssl.

References

low severity
new

CVE-2023-6597

  • Vulnerable module: python3.11
  • Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others

Detailed paths

  • Introduced through: buildpack-deps@testing-scm python3.11@3.11.2-6
  • Introduced through: buildpack-deps@testing-scm python3.11/libpython3.11-minimal@3.11.2-6
  • Introduced through: buildpack-deps@testing-scm python3.11/libpython3.11-stdlib@3.11.2-6
  • Introduced through: buildpack-deps@testing-scm python3.11/python3.11-minimal@3.11.2-6

NVD Description

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

References

low severity
new

CVE-2024-0450

  • Vulnerable module: python3.11
  • Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others

Detailed paths

  • Introduced through: buildpack-deps@testing-scm python3.11@3.11.2-6
  • Introduced through: buildpack-deps@testing-scm python3.11/libpython3.11-minimal@3.11.2-6
  • Introduced through: buildpack-deps@testing-scm python3.11/libpython3.11-stdlib@3.11.2-6
  • Introduced through: buildpack-deps@testing-scm python3.11/python3.11-minimal@3.11.2-6

NVD Description

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

References

low severity

CVE-2023-50868

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@252.6-1 and systemd/libudev1@252.6-1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm systemd/libsystemd0@252.6-1
  • Introduced through: buildpack-deps@testing-scm systemd/libudev1@252.6-1

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:12 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:12 systemd.

References

low severity

CVE-2023-39804

  • Vulnerable module: tar
  • Introduced through: tar@1.34+dfsg-1.2
  • Fixed in: 1.34+dfsg-1.2+deb12u1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm tar@1.34+dfsg-1.2

NVD Description

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

In GNU tar before 1.35, mishandled extension attributes in a PAX archive can lead to an application crash in xheader.c.

Remediation

Upgrade Debian:12 tar to version 1.34+dfsg-1.2+deb12u1 or higher.

References

low severity
new

CVE-2024-28085

  • Vulnerable module: util-linux/libblkid1
  • Introduced through: util-linux/libblkid1@2.38.1-5+b1, util-linux/libmount1@2.38.1-5+b1 and others
  • Fixed in: 2.38.1-5+deb12u1

Detailed paths

  • Introduced through: buildpack-deps@testing-scm util-linux/libblkid1@2.38.1-5+b1
  • Introduced through: buildpack-deps@testing-scm util-linux/libmount1@2.38.1-5+b1
  • Introduced through: buildpack-deps@testing-scm util-linux/libsmartcols1@2.38.1-5+b1
  • Introduced through: buildpack-deps@testing-scm util-linux/libuuid1@2.38.1-5+b1
  • Introduced through: buildpack-deps@testing-scm util-linux/mount@2.38.1-5+b1
  • Introduced through: buildpack-deps@testing-scm util-linux/util-linux@2.38.1-5+b1
  • Introduced through: buildpack-deps@testing-scm util-linux/util-linux-extra@2.38.1-5+b1

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

wall in util-linux through 2.40, often installed with setgid tty permissions, allows escape sequences to be sent to other users' terminals through argv. (Specifically, escape sequences received from stdin are blocked, but escape sequences received from argv are not blocked.) There may be plausible scenarios where this leads to account takeover.

Remediation

Upgrade Debian:12 util-linux to version 2.38.1-5+deb12u1 or higher.

References