Vulnerabilities |
369 via 1259 paths |
|---|---|
Dependencies |
205 |
Source |
Docker |
Target OS |
debian:12 |
critical severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1
- Fixed in: 2.5.0-1+deb12u1
Detailed paths
-
Introduced through: golang@1.20 › 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.
An issue was discovered in libexpat before 2.6.3. nextScaffoldPart in xmlparse.c can have an integer overflow for m_groupSize on 32-bit platforms (where UINT_MAX equals SIZE_MAX).
Remediation
Upgrade Debian:12 expat to version 2.5.0-1+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-45492
- https://github.com/libexpat/libexpat/issues/889
- https://github.com/libexpat/libexpat/pull/892
- https://security.netapp.com/advisory/ntap-20241018-0005/
- https://lists.debian.org/debian-lts-announce/2024/09/msg00036.html
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-613116.html
critical severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1
- Fixed in: 2.5.0-1+deb12u1
Detailed paths
-
Introduced through: golang@1.20 › 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.
An issue was discovered in libexpat before 2.6.3. dtdCopy in xmlparse.c can have an integer overflow for nDefaultAtts on 32-bit platforms (where UINT_MAX equals SIZE_MAX).
Remediation
Upgrade Debian:12 expat to version 2.5.0-1+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-45491
- https://github.com/libexpat/libexpat/issues/888
- https://github.com/libexpat/libexpat/pull/891
- https://security.netapp.com/advisory/ntap-20241018-0003/
- https://lists.debian.org/debian-lts-announce/2024/09/msg00036.html
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-613116.html
critical severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u1
- Fixed in: 3.7.9-2+deb12u7
Detailed paths
-
Introduced through: golang@1.20 › gnutls28/libgnutls30@3.7.9-2+deb12u1
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. Servers configured with RSA-PSK (Rivest–Shamir–Adleman – Pre-Shared Key) wrongfully matched usernames containing a NUL character with truncated usernames. A remote attacker could exploit this by sending a specially crafted username, leading to an authentication bypass. This vulnerability allows an attacker to gain unauthorized access by circumventing the authentication process.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-42010
- https://access.redhat.com/security/cve/CVE-2026-42010
- https://bugzilla.redhat.com/show_bug.cgi?id=2467289
- https://access.redhat.com/errata/RHSA-2026:13274
- https://access.redhat.com/errata/RHSA-2026:20611
- https://access.redhat.com/errata/RHSA-2026:20613
- https://access.redhat.com/errata/RHSA-2026:20612
critical severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.11-1~deb12u2 and openssl/libssl3@3.0.11-1~deb12u2
- Fixed in: 3.0.19-1~deb12u2
Detailed paths
-
Introduced through: golang@1.20 › openssl@3.0.11-1~deb12u2
-
Introduced through: golang@1.20 › openssl/libssl3@3.0.11-1~deb12u2
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: Converting an excessively large OCTET STRING value to a hexadecimal string leads to a heap buffer overflow on 32 bit platforms.
Impact summary: A heap buffer overflow may lead to a crash or possibly an attacker controlled code execution or other undefined behavior.
If an attacker can supply a crafted X.509 certificate with an excessively large OCTET STRING value in extensions such as the Subject Key Identifier (SKID) or Authority Key Identifier (AKID) which are being converted to hex, the size of the buffer needed for the result is calculated as multiplication of the input length by 3. On 32 bit platforms, this multiplication may overflow resulting in the allocation of a smaller buffer and a heap buffer overflow.
Applications and services that print or log contents of untrusted X.509 certificates are vulnerable to this issue. As the certificates would have to have sizes of over 1 Gigabyte, printing or logging such certificates is a fairly unlikely operation and only 32 bit platforms are affected, this issue was assigned Low severity.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.
Remediation
Upgrade Debian:12 openssl to version 3.0.19-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-31789
- https://github.com/openssl/openssl/commit/364f095b80601db632b0def6a33316967f863bde
- https://github.com/openssl/openssl/commit/7a9087efd769f362ad9c0e30c7baaa6bbfa65ecf
- https://github.com/openssl/openssl/commit/945b935ac66cc7f1a41f1b849c7c25adb5351f49
- https://github.com/openssl/openssl/commit/a24216018e1ede8ff01a4ff5afff7dfbd443e2f9
- https://github.com/openssl/openssl/commit/a91e537d16d74050dbde50bb0dfb1fe9930f0521
- https://openssl-library.org/news/secadv/20260407.txt
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
critical severity
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2
- Fixed in: 3.40.1-2+deb12u2
Detailed paths
-
Introduced through: golang@1.20 › 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.
There exists a vulnerability in SQLite versions before 3.50.2 where the number of aggregate terms could exceed the number of columns available. This could lead to a memory corruption issue. We recommend upgrading to version 3.50.2 or above.
Remediation
Upgrade Debian:12 sqlite3 to version 3.40.1-2+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-6965
- https://www.sqlite.org/src/info/5508b56fd24016c13981ec280ecdd833007c9d8dd595edb295b984c2b487b5c8
- http://seclists.org/fulldisclosure/2025/Sep/49
- http://seclists.org/fulldisclosure/2025/Sep/53
- http://seclists.org/fulldisclosure/2025/Sep/56
- http://seclists.org/fulldisclosure/2025/Sep/57
- http://seclists.org/fulldisclosure/2025/Sep/58
- http://www.openwall.com/lists/oss-security/2025/09/06/1
- https://cert-portal.siemens.com/productcert/html/ssa-225816.html
- https://cert-portal.siemens.com/productcert/html/ssa-485750.html
- https://www.exploit-db.com/exploits/52499
critical severity
- Vulnerable module: zlib/zlib1g
- Introduced through: zlib/zlib1g@1:1.2.13.dfsg-1
Detailed paths
-
Introduced through: golang@1.20 › 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
- https://security-tracker.debian.org/tracker/CVE-2023-45853
- http://www.openwall.com/lists/oss-security/2023/10/20/9
- http://www.openwall.com/lists/oss-security/2024/01/24/10
- https://chromium.googlesource.com/chromium/src/+/d709fb23806858847131027da95ef4c548813356
- https://chromium.googlesource.com/chromium/src/+/de29dd6c7151d3cd37cb4cf0036800ddfb1d8b61
- https://github.com/madler/zlib/blob/ac8f12c97d1afd9bafa9c710f827d40a407d3266/contrib/README.contrib#L1-L4
- https://github.com/madler/zlib/pull/843
- https://lists.debian.org/debian-lts-announce/2023/11/msg00026.html
- https://pypi.org/project/pyminizip/#history
- https://security.gentoo.org/glsa/202401-18
- https://security.netapp.com/advisory/ntap-20231130-0009/
- https://www.winimage.com/zLibDll/minizip.html
critical severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u1
- Fixed in: 3.7.9-2+deb12u7
Detailed paths
-
Introduced through: golang@1.20 › gnutls28/libgnutls30@3.7.9-2+deb12u1
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 in GnuTLS DTLS handshake parsing allows malformed fragments with zero length and non-zero offset, leading to an integer underflow during reassembly and resulting in an out-of-bounds read. This issue is remotely exploitable and may cause information disclosure or denial of service.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-33845
- https://access.redhat.com/errata/RHSA-2026:13274
- https://access.redhat.com/security/cve/CVE-2026-33845
- https://bugzilla.redhat.com/show_bug.cgi?id=2450624
- https://access.redhat.com/errata/RHSA-2026:20611
- https://access.redhat.com/errata/RHSA-2026:20613
- https://access.redhat.com/errata/RHSA-2026:20612
critical severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u1, krb5/libk5crypto3@1.20.1-2+deb12u1 and others
- Fixed in: 1.20.1-2+deb12u2
Detailed paths
-
Introduced through: golang@1.20 › krb5/libgssapi-krb5-2@1.20.1-2+deb12u1
-
Introduced through: golang@1.20 › krb5/libk5crypto3@1.20.1-2+deb12u1
-
Introduced through: golang@1.20 › krb5/libkrb5-3@1.20.1-2+deb12u1
-
Introduced through: golang@1.20 › krb5/libkrb5support0@1.20.1-2+deb12u1
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.
In MIT Kerberos 5 (aka krb5) before 1.21.3, an attacker can cause invalid memory reads during GSS message token handling by sending message tokens with invalid length fields.
Remediation
Upgrade Debian:12 krb5 to version 1.20.1-2+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-37371
- https://security.netapp.com/advisory/ntap-20241108-0009/
- https://security.netapp.com/advisory/ntap-20250124-0010/
- https://github.com/krb5/krb5/commit/55fbf435edbe2e92dd8101669b1ce7144bc96fef
- https://web.mit.edu/kerberos/www/advisories/
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
critical severity
- Vulnerable module: wget/wget
- Introduced through: wget/wget@1.21.3-1+b2
- Fixed in: 1.21.3-1+deb12u1
Detailed paths
-
Introduced through: golang@1.20 › 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.
url.c in GNU Wget through 1.24.5 mishandles semicolons in the userinfo subcomponent of a URI, and thus there may be insecure behavior in which data that was supposed to be in the userinfo subcomponent is misinterpreted to be part of the host subcomponent.
Remediation
Upgrade Debian:12 wget to version 1.21.3-1+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-38428
- https://security.netapp.com/advisory/ntap-20241115-0005/
- https://git.savannah.gnu.org/cgit/wget.git/commit/?id=ed0c7c7e0e8f7298352646b2fd6e06a11e242ace
- https://lists.debian.org/debian-lts-announce/2025/04/msg00029.html
- https://lists.gnu.org/archive/html/bug-wget/2024-06/msg00005.html
critical severity
- Vulnerable module: git
- Introduced through: git@1:2.39.2-1.1 and git/git-man@1:2.39.2-1.1
- Fixed in: 1:2.39.5-0+deb12u1
Detailed paths
-
Introduced through: golang@1.20 › git@1:2.39.2-1.1
-
Introduced through: golang@1.20 › 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.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, repositories with submodules can be crafted in a way that exploits a bug in Git whereby it can be fooled into writing files not into the submodule's worktree but into a .git/ directory. This allows writing a hook that will be executed while the clone operation is still running, giving the user no opportunity to inspect the code that is being executed. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4. If symbolic link support is disabled in Git (e.g. via git config --global core.symlinks false), the described attack won't work. As always, it is best to avoid cloning repositories from untrusted sources.
Remediation
Upgrade Debian:12 git to version 1:2.39.5-0+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-32002
- http://www.openwall.com/lists/oss-security/2024/05/14/2
- https://git-scm.com/docs/git-clone#Documentation/git-clone.txt---recurse-submodulesltpathspecgt
- https://git-scm.com/docs/git-config#Documentation/git-config.txt-coresymlinks
- https://github.com/git/git/commit/97065761333fd62db1912d81b489db938d8c991d
- https://github.com/git/git/security/advisories/GHSA-8h77-4q3w-gfgv
- https://lists.debian.org/debian-lts-announce/2024/06/msg00018.html
- https://lists.debian.org/debian-lts-announce/2024/09/msg00009.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/S4CK4IYTXEOBZTEM5K3T6LWOIZ3S44AR/
- https://github.com/amalmurali47/git_rce
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u1
- Fixed in: 3.7.9-2+deb12u5
Detailed paths
-
Introduced through: golang@1.20 › gnutls28/libgnutls30@3.7.9-2+deb12u1
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. A double-free vulnerability exists in GnuTLS due to incorrect ownership handling in the export logic of Subject Alternative Name (SAN) entries containing an otherName. If the type-id OID is invalid or malformed, GnuTLS will call asn1_delete_structure() on an ASN.1 node it does not own, leading to a double-free condition when the parent function or caller later attempts to free the same structure.
This vulnerability can be triggered using only public GnuTLS APIs and may result in denial of service or memory corruption, depending on allocator behavior.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-32988
- https://access.redhat.com/security/cve/CVE-2025-32988
- https://bugzilla.redhat.com/show_bug.cgi?id=2359622
- https://access.redhat.com/errata/RHSA-2025:16115
- https://access.redhat.com/errata/RHSA-2025:16116
- https://access.redhat.com/errata/RHSA-2025:17348
- https://access.redhat.com/errata/RHSA-2025:17361
- https://access.redhat.com/errata/RHSA-2025:17415
- https://access.redhat.com/errata/RHSA-2025:19088
- https://lists.debian.org/debian-lts-announce/2025/08/msg00005.html
- http://www.openwall.com/lists/oss-security/2025/07/11/3
- https://access.redhat.com/errata/RHSA-2025:17181
- https://access.redhat.com/errata/RHSA-2025:22529
- https://lists.gnupg.org/pipermail/gnutls-help/2025-July/004883.html
- https://access.redhat.com/errata/RHSA-2026:7477
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u1
- Fixed in: 3.7.9-2+deb12u5
Detailed paths
-
Introduced through: golang@1.20 › gnutls28/libgnutls30@3.7.9-2+deb12u1
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 heap-buffer-overflow (off-by-one) flaw was found in the GnuTLS software in the template parsing logic within the certtool utility. When it reads certain settings from a template file, it allows an attacker to cause an out-of-bounds (OOB) NULL pointer write, resulting in memory corruption and a denial-of-service (DoS) that could potentially crash the system.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-32990
- https://access.redhat.com/security/cve/CVE-2025-32990
- https://bugzilla.redhat.com/show_bug.cgi?id=2359620
- https://access.redhat.com/errata/RHSA-2025:16115
- https://access.redhat.com/errata/RHSA-2025:16116
- https://access.redhat.com/errata/RHSA-2025:17348
- https://access.redhat.com/errata/RHSA-2025:17361
- https://access.redhat.com/errata/RHSA-2025:17415
- https://access.redhat.com/errata/RHSA-2025:19088
- https://lists.debian.org/debian-lts-announce/2025/08/msg00005.html
- http://www.openwall.com/lists/oss-security/2025/07/11/3
- https://access.redhat.com/errata/RHSA-2025:17181
- https://access.redhat.com/errata/RHSA-2025:22529
- https://lists.gnupg.org/pipermail/gnutls-help/2025-July/004883.html
- https://access.redhat.com/errata/RHSA-2026:7477
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u1
- Fixed in: 3.7.9-2+deb12u7
Detailed paths
-
Introduced through: golang@1.20 › gnutls28/libgnutls30@3.7.9-2+deb12u1
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. When validating certificates, an oversized Subject Alternative Name (SAN) could cause the validation process to incorrectly fall back to checking the Common Name (CN) field. This could allow a remote attacker to bypass proper certificate validation, potentially leading to spoofing or man-in-the-middle attacks.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-42013
- https://access.redhat.com/security/cve/CVE-2026-42013
- https://bugzilla.redhat.com/show_bug.cgi?id=2467448
- https://access.redhat.com/errata/RHSA-2026:20611
- https://access.redhat.com/errata/RHSA-2026:20613
- https://access.redhat.com/errata/RHSA-2026:20612
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u1
- Fixed in: 3.7.9-2+deb12u7
Detailed paths
-
Introduced through: golang@1.20 › gnutls28/libgnutls30@3.7.9-2+deb12u1
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 libgnutls. A remote attacker, by sending an extremely short premaster secret during an RSA key exchange to a server using an RSA key backed by a PKCS#11 token, could trigger a short heap overread. This memory corruption vulnerability could lead to information disclosure.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-5260
- https://access.redhat.com/security/cve/CVE-2026-5260
- https://bugzilla.redhat.com/show_bug.cgi?id=2467450
- https://access.redhat.com/errata/RHSA-2026:20611
- https://access.redhat.com/errata/RHSA-2026:20613
- https://access.redhat.com/errata/RHSA-2026:20612
high severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2+deb12u2
- Fixed in: 1:9.2p1-2+deb12u10
Detailed paths
-
Introduced through: golang@1.20 › openssh/openssh-client@1:9.2p1-2+deb12u2
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 before 10.3 mishandles the authorized_keys principals option in uncommon scenarios involving a principals list in conjunction with a Certificate Authority that makes certain use of comma characters.
Remediation
Upgrade Debian:12 openssh to version 1:9.2p1-2+deb12u10 or higher.
References
high severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2+deb12u2
- Fixed in: 1:9.2p1-2+deb12u10
Detailed paths
-
Introduced through: golang@1.20 › openssh/openssh-client@1:9.2p1-2+deb12u2
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 before 10.3, a file downloaded by scp may be installed setuid or setgid, an outcome contrary to some users' expectations, if the download is performed as root with -O (legacy scp protocol) and without -p (preserve mode).
Remediation
Upgrade Debian:12 openssh to version 1:9.2p1-2+deb12u10 or higher.
References
high severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2+deb12u2
- Fixed in: 1:9.2p1-2+deb12u10
Detailed paths
-
Introduced through: golang@1.20 › openssh/openssh-client@1:9.2p1-2+deb12u2
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 before 10.3, command execution can occur via shell metacharacters in a username within a command line. This requires a scenario where the username on the command line is untrusted, and also requires a non-default configurations of % in ssh_config.
Remediation
Upgrade Debian:12 openssh to version 1:9.2p1-2+deb12u10 or higher.
References
high severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2+deb12u2
- Fixed in: 1:9.2p1-2+deb12u3
Detailed paths
-
Introduced through: golang@1.20 › openssh/openssh-client@1:9.2p1-2+deb12u2
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.
A security regression (CVE-2006-5051) was discovered in OpenSSH's server (sshd). There is a race condition which can lead sshd to handle some signals in an unsafe manner. An unauthenticated, remote attacker may be able to trigger it by failing to authenticate within a set time period.
Remediation
Upgrade Debian:12 openssh to version 1:9.2p1-2+deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-6387
- http://seclists.org/fulldisclosure/2024/Jul/18
- http://seclists.org/fulldisclosure/2024/Jul/19
- http://seclists.org/fulldisclosure/2024/Jul/20
- http://www.openwall.com/lists/oss-security/2024/07/01/12
- http://www.openwall.com/lists/oss-security/2024/07/01/13
- http://www.openwall.com/lists/oss-security/2024/07/02/1
- http://www.openwall.com/lists/oss-security/2024/07/03/1
- http://www.openwall.com/lists/oss-security/2024/07/03/11
- http://www.openwall.com/lists/oss-security/2024/07/03/2
- http://www.openwall.com/lists/oss-security/2024/07/03/3
- http://www.openwall.com/lists/oss-security/2024/07/03/4
- http://www.openwall.com/lists/oss-security/2024/07/03/5
- http://www.openwall.com/lists/oss-security/2024/07/04/1
- http://www.openwall.com/lists/oss-security/2024/07/04/2
- http://www.openwall.com/lists/oss-security/2024/07/08/2
- http://www.openwall.com/lists/oss-security/2024/07/08/3
- http://www.openwall.com/lists/oss-security/2024/07/09/2
- http://www.openwall.com/lists/oss-security/2024/07/09/5
- http://www.openwall.com/lists/oss-security/2024/07/10/1
- http://www.openwall.com/lists/oss-security/2024/07/10/2
- http://www.openwall.com/lists/oss-security/2024/07/10/3
- http://www.openwall.com/lists/oss-security/2024/07/10/4
- http://www.openwall.com/lists/oss-security/2024/07/10/6
- http://www.openwall.com/lists/oss-security/2024/07/11/1
- http://www.openwall.com/lists/oss-security/2024/07/11/3
- http://www.openwall.com/lists/oss-security/2024/07/23/4
- http://www.openwall.com/lists/oss-security/2024/07/23/6
- http://www.openwall.com/lists/oss-security/2024/07/28/2
- http://www.openwall.com/lists/oss-security/2024/07/28/3
- https://archlinux.org/news/the-sshd-service-needs-to-be-restarted-after-upgrading-to-openssh-98p1/
- https://arstechnica.com/security/2024/07/regresshion-vulnerability-in-openssh-gives-attackers-root-on-linux/
- https://blog.qualys.com/vulnerabilities-threat-research/2024/07/01/regresshion-remote-unauthenticated-code-execution-vulnerability-in-openssh-server
- https://explore.alas.aws.amazon.com/CVE-2024-6387.html
- https://forum.vmssoftware.com/viewtopic.php?f=8&t=9132
- https://ftp.netbsd.org/pub/NetBSD/security/advisories/NetBSD-SA2024-002.txt.asc
- https://github.com/AlmaLinux/updates/issues/629
- https://github.com/Azure/AKS/issues/4379
- https://github.com/PowerShell/Win32-OpenSSH/discussions/2248
- https://github.com/PowerShell/Win32-OpenSSH/issues/2249
- https://github.com/microsoft/azurelinux/issues/9555
- https://github.com/openela-main/openssh/commit/e1f438970e5a337a17070a637c1b9e19697cad09
- https://github.com/oracle/oracle-linux/issues/149
- https://github.com/rapier1/hpn-ssh/issues/87
- https://github.com/zgzhang/cve-2024-6387-poc
- https://lists.almalinux.org/archives/list/announce@lists.almalinux.org/thread/23BF5BMGFVEVUI2WNVAGMLKT557EU7VY/
- https://lists.mindrot.org/pipermail/openssh-unix-announce/2024-July/000158.html
- https://lists.mindrot.org/pipermail/openssh-unix-dev/2024-July/041431.html
- https://news.ycombinator.com/item?id=40843778
- https://packetstorm.news/files/id/190587/
- https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2024-0010
- https://security.netapp.com/advisory/ntap-20240701-0001/
- https://sig-security.rocky.page/issues/CVE-2024-6387/
- https://stackdiary.com/openssh-race-condition-in-sshd-allows-remote-code-execution/
- https://support.apple.com/kb/HT214118
- https://support.apple.com/kb/HT214119
- https://support.apple.com/kb/HT214120
- https://ubuntu.com/security/CVE-2024-6387
- https://ubuntu.com/security/notices/USN-6859-1
- https://www.akamai.com/blog/security-research/2024-openssh-vulnerability-regression-what-to-know-and-do
- https://www.arista.com/en/support/advisories-notices/security-advisory/19904-security-advisory-0100
- https://www.exploit-db.com/exploits/52269
- https://www.freebsd.org/security/advisories/FreeBSD-SA-24:04.openssh.asc
- https://www.splunk.com/en_us/blog/security/cve-2024-6387-regresshion-vulnerability.html
- https://www.suse.com/security/cve/CVE-2024-6387.html
- https://www.theregister.com/2024/07/01/regresshion_openssh/
- https://www.vicarius.io/vsociety/posts/regresshion-an-openssh-regression-error-cve-2024-6387
- https://access.redhat.com/errata/RHSA-2024:4312
- https://access.redhat.com/errata/RHSA-2024:4340
- https://access.redhat.com/errata/RHSA-2024:4389
- https://access.redhat.com/errata/RHSA-2024:4469
- https://access.redhat.com/errata/RHSA-2024:4474
- https://access.redhat.com/errata/RHSA-2024:4479
- https://access.redhat.com/errata/RHSA-2024:4484
- https://access.redhat.com/security/cve/CVE-2024-6387
- https://bugzilla.redhat.com/show_bug.cgi?id=2294604
- https://santandersecurityresearch.github.io/blog/sshing_the_masses.html
- https://www.openssh.com/txt/release-9.8
- https://www.qualys.com/2024/07/01/cve-2024-6387/regresshion.txt
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-446545.html
- https://github.com/xonoxitron/regreSSHion-checker
high severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.11-1~deb12u2 and openssl/libssl3@3.0.11-1~deb12u2
- Fixed in: 3.0.19-1~deb12u2
Detailed paths
-
Introduced through: golang@1.20 › openssl@3.0.11-1~deb12u2
-
Introduced through: golang@1.20 › openssl/libssl3@3.0.11-1~deb12u2
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: An uncommon configuration of clients performing DANE TLSA-based server authentication, when paired with uncommon server DANE TLSA records, may result in a use-after-free and/or double-free on the client side.
Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of arbitrary code.
However, the issue only affects clients that make use of TLSA records with both the PKIX-TA(0/PKIX-EE(1) certificate usages and the DANE-TA(2) certificate usage.
By far the most common deployment of DANE is in SMTP MTAs for which RFC7672 recommends that clients treat as 'unusable' any TLSA records that have the PKIX certificate usages. These SMTP (or other similar) clients are not vulnerable to this issue. Conversely, any clients that support only the PKIX usages, and ignore the DANE-TA(2) usage are also not vulnerable.
The client would also need to be communicating with a server that publishes a TLSA RRset with both types of TLSA records.
No FIPS modules are affected by this issue, the problem code is outside the FIPS module boundary.
Remediation
Upgrade Debian:12 openssl to version 3.0.19-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-28387
- https://github.com/openssl/openssl/commit/07e727d304746edb49a98ee8f6ab00256e1f012b
- https://github.com/openssl/openssl/commit/258a8f63b26995ba357f4326da00e19e29c6acbe
- https://github.com/openssl/openssl/commit/444958deaf450aea819171f97ae69eaedede42c3
- https://github.com/openssl/openssl/commit/7a4e08cee62a728d32e60b0de89e6764339df0a7
- https://github.com/openssl/openssl/commit/ec03fa050b3346997ed9c5fef3d0e16ad7db8177
- https://openssl-library.org/news/secadv/20260407.txt
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
high severity
- Vulnerable module: perl
- Introduced through: perl@5.36.0-7+deb12u1, perl/libperl5.36@5.36.0-7+deb12u1 and others
- Fixed in: 5.36.0-7+deb12u3
Detailed paths
-
Introduced through: golang@1.20 › perl@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/libperl5.36@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/perl-base@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/perl-modules-5.36@5.36.0-7+deb12u1
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
Upgrade Debian:12 perl to version 5.36.0-7+deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-31484
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BM6UW55CNFUTNGD5ZRKGUKKKFDJGMFHL/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LEGCEOKFJVBJ2QQ6S2H4NAEWTUERC7SB/
- http://www.openwall.com/lists/oss-security/2023/04/29/1
- http://www.openwall.com/lists/oss-security/2023/05/03/3
- http://www.openwall.com/lists/oss-security/2023/05/03/5
- http://www.openwall.com/lists/oss-security/2023/05/07/2
- https://blog.hackeriet.no/perl-http-tiny-insecure-tls-default-affects-cpan-modules/
- https://github.com/andk/cpanpm/pull/175
- https://lists.debian.org/debian-lts-announce/2024/10/msg00017.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BM6UW55CNFUTNGD5ZRKGUKKKFDJGMFHL/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LEGCEOKFJVBJ2QQ6S2H4NAEWTUERC7SB/
- https://metacpan.org/dist/CPAN/changes
- https://security.netapp.com/advisory/ntap-20240621-0007/
- https://www.openwall.com/lists/oss-security/2023/04/18/14
high severity
- Vulnerable module: git
- Introduced through: git@1:2.39.2-1.1 and git/git-man@1:2.39.2-1.1
- Fixed in: 1:2.39.5-0+deb12u1
Detailed paths
-
Introduced through: golang@1.20 › git@1:2.39.2-1.1
-
Introduced through: golang@1.20 › 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
Upgrade Debian:12 git to version 1:2.39.5-0+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-29007
- https://github.com/git/git/blob/9ce9dea4e1c2419cca126d29fa7730baa078a11b/Documentation/RelNotes/2.30.9.txt
- https://github.com/git/git/commit/528290f8c61222433a8cf02fb7cfffa8438432b4
- https://github.com/git/git/security/advisories/GHSA-v48j-4xgg-4844
- https://lists.debian.org/debian-lts-announce/2024/06/msg00018.html
- https://lists.debian.org/debian-lts-announce/2024/09/msg00009.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PI7FZ4NNR5S5J5K6AMVQBH2JFP6NE4L7/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RKOXOAZ42HLXHXTW6JZI4L5DAIYDTYCU/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YFZWGQKB6MM5MNF2DLFTD7KS2KWPICKL/
- https://security.gentoo.org/glsa/202312-15
- https://github.com/ethiack/CVE-2023-29007
high severity
- Vulnerable module: git
- Introduced through: git@1:2.39.2-1.1 and git/git-man@1:2.39.2-1.1
- Fixed in: 1:2.39.5-0+deb12u1
Detailed paths
-
Introduced through: golang@1.20 › git@1:2.39.2-1.1
-
Introduced through: golang@1.20 › 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.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, an attacker can prepare a local repository in such a way that, when cloned, will execute arbitrary code during the operation. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4. As a workaround, avoid cloning repositories from untrusted sources.
Remediation
Upgrade Debian:12 git to version 1:2.39.5-0+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-32004
- http://www.openwall.com/lists/oss-security/2024/05/14/2
- https://git-scm.com/docs/git-clone
- https://github.com/git/git/commit/f4aa8c8bb11dae6e769cd930565173808cbb69c8
- https://github.com/git/git/security/advisories/GHSA-xfc6-vwr8-r389
- https://lists.debian.org/debian-lts-announce/2024/06/msg00018.html
- https://lists.debian.org/debian-lts-announce/2024/09/msg00009.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/S4CK4IYTXEOBZTEM5K3T6LWOIZ3S44AR/
high severity
- Vulnerable module: git
- Introduced through: git@1:2.39.2-1.1 and git/git-man@1:2.39.2-1.1
- Fixed in: 1:2.39.5-0+deb12u1
Detailed paths
-
Introduced through: golang@1.20 › git@1:2.39.2-1.1
-
Introduced through: golang@1.20 › 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. The Git project recommends to avoid working in untrusted repositories, and instead to clone it first with git clone --no-local to obtain a clean copy. Git has specific protections to make that a safe operation even with an untrusted source repository, but vulnerabilities allow those protections to be bypassed. In the context of cloning local repositories owned by other users, this vulnerability has been covered in CVE-2024-32004. But there are circumstances where the fixes for CVE-2024-32004 are not enough: For example, when obtaining a .zip file containing a full copy of a Git repository, it should not be trusted by default to be safe, as e.g. hooks could be configured to run within the context of that repository. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4. As a workaround, avoid using Git in repositories that have been obtained via archives from untrusted sources.
Remediation
Upgrade Debian:12 git to version 1:2.39.5-0+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-32465
- http://www.openwall.com/lists/oss-security/2024/05/14/2
- https://git-scm.com/docs/git#_security
- https://git-scm.com/docs/git-clone
- https://github.com/git/git/commit/7b70e9efb18c2cc3f219af399bd384c5801ba1d7
- https://github.com/git/git/security/advisories/GHSA-vm9j-46j9-qvq4
- https://lists.debian.org/debian-lts-announce/2024/06/msg00018.html
- https://lists.debian.org/debian-lts-announce/2024/09/msg00009.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/S4CK4IYTXEOBZTEM5K3T6LWOIZ3S44AR/
high severity
- Vulnerable module: pam/libpam-modules
- Introduced through: pam/libpam-modules@1.5.2-6+deb12u1, pam/libpam-modules-bin@1.5.2-6+deb12u1 and others
- Fixed in: 1.5.2-6+deb12u2
Detailed paths
-
Introduced through: golang@1.20 › pam/libpam-modules@1.5.2-6+deb12u1
-
Introduced through: golang@1.20 › pam/libpam-modules-bin@1.5.2-6+deb12u1
-
Introduced through: golang@1.20 › pam/libpam-runtime@1.5.2-6+deb12u1
-
Introduced through: golang@1.20 › pam/libpam0g@1.5.2-6+deb12u1
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.
A flaw was found in linux-pam. The module pam_namespace may use access user-controlled paths without proper protection, allowing local users to elevate their privileges to root via multiple symlink attacks and race conditions.
Remediation
Upgrade Debian:12 pam to version 1.5.2-6+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-6020
- https://access.redhat.com/security/cve/CVE-2025-6020
- https://bugzilla.redhat.com/show_bug.cgi?id=2372512
- http://www.openwall.com/lists/oss-security/2025/06/17/1
- https://access.redhat.com/errata/RHSA-2025:9526
- https://access.redhat.com/errata/RHSA-2025:10024
- https://access.redhat.com/errata/RHSA-2025:10027
- https://access.redhat.com/errata/RHSA-2025:10180
- https://access.redhat.com/errata/RHSA-2025:10354
- https://access.redhat.com/errata/RHSA-2025:10357
- https://access.redhat.com/errata/RHSA-2025:10358
- https://access.redhat.com/errata/RHSA-2025:10359
- https://access.redhat.com/errata/RHSA-2025:10361
- https://access.redhat.com/errata/RHSA-2025:10362
- https://access.redhat.com/errata/RHSA-2025:10735
- https://access.redhat.com/errata/RHSA-2025:10823
- https://access.redhat.com/errata/RHSA-2025:11386
- https://access.redhat.com/errata/RHSA-2025:11487
- https://access.redhat.com/errata/RHSA-2025:14557
- https://access.redhat.com/errata/RHSA-2025:15099
- https://access.redhat.com/errata/RHSA-2025:15709
- https://access.redhat.com/errata/RHSA-2025:15828
- https://access.redhat.com/errata/RHSA-2025:15827
- https://access.redhat.com/errata/RHSA-2025:16524
- https://access.redhat.com/errata/RHSA-2025:18219
- https://lists.debian.org/debian-lts-announce/2025/09/msg00021.html
- https://access.redhat.com/errata/RHSA-2025:17181
- https://access.redhat.com/errata/RHSA-2025:20181
- https://access.redhat.com/errata/RHSA-2025:21885
- https://access.redhat.com/errata/RHSA-2025:22019
- https://access.redhat.com/errata/RHSA-2026:0934
- https://github.com/linux-pam/linux-pam/security/advisories/GHSA-f9p8-gjr4-j9gx
- https://cert-portal.siemens.com/productcert/html/ssa-577017.html
high severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u5
Detailed paths
-
Introduced through: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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.
A vulnerability has been found in the CPython venv module and CLI where path names provided when creating a virtual environment were not quoted properly, allowing the creator to inject commands into virtual environment "activation" scripts (ie "source venv/bin/activate"). This means that attacker-controlled virtual environments are able to run commands when the virtual environment is activated. Virtual environments which are not created by an attacker or which aren't activated before being used (ie "./venv/bin/python") are not affected.
Remediation
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-9287
- https://github.com/python/cpython/commit/633555735a023d3e4d92ba31da35b1205f9ecbd7
- https://github.com/python/cpython/commit/8450b2482586857d689b6658f08de9c8179af7db
- https://github.com/python/cpython/commit/9286ab3a107ea41bd3f3c3682ce2512692bdded8
- https://github.com/python/cpython/commit/ae961ae94bf19c8f8c7fbea3d1c25cc55ce8ae97
- https://github.com/python/cpython/commit/d48cc82ed25e26b02eb97c6263d95dcaa1e9111b
- https://github.com/python/cpython/commit/e52095a0c1005a87eed2276af7a1f2f66e2b6483
- https://github.com/python/cpython/issues/124651
- https://github.com/python/cpython/pull/124712
- https://mail.python.org/archives/list/security-announce@python.org/thread/RSPJ2B5JL22FG3TKUJ7D7DQ4N5JRRBZL/
- https://security.netapp.com/advisory/ntap-20250425-0006/
- https://lists.debian.org/debian-lts-announce/2024/11/msg00024.html
- https://lists.debian.org/debian-lts-announce/2024/12/msg00000.html
high severity
new
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1
Detailed paths
-
Introduced through: golang@1.20 › 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.
In libexpat before 2.8.1, the computational complexity of attribute name collision checks allows a denial of service via moderately sized crafted XML input.
Remediation
There is no fixed version for Debian:12 expat.
References
high severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1
- Fixed in: 2.5.0-1+deb12u2
Detailed paths
-
Introduced through: golang@1.20 › 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
Upgrade Debian:12 expat to version 2.5.0-1+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-52425
- https://lists.debian.org/debian-lts-announce/2024/09/msg00036.html
- http://www.openwall.com/lists/oss-security/2024/03/20/5
- https://github.com/libexpat/libexpat/pull/789
- https://lists.debian.org/debian-lts-announce/2024/04/msg00006.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PNRIHC7DVVRAIWFRGV23Y6UZXFBXSQDB/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WNUBSGZFEZOBHJFTAD42SAN4ATW2VEMV/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PNRIHC7DVVRAIWFRGV23Y6UZXFBXSQDB/
- https://security.netapp.com/advisory/ntap-20240614-0003/
high severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1
- Fixed in: 2.5.0-1+deb12u2
Detailed paths
-
Introduced through: golang@1.20 › 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.
A stack overflow vulnerability exists in the libexpat library due to the way it handles recursive entity expansion in XML documents. When parsing an XML document with deeply nested entity references, libexpat can be forced to recurse indefinitely, exhausting the stack space and causing a crash. This issue could lead to denial of service (DoS) or, in some cases, exploitable memory corruption, depending on the environment and library usage.
Remediation
Upgrade Debian:12 expat to version 2.5.0-1+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-8176
- https://access.redhat.com/security/cve/CVE-2024-8176
- https://bugzilla.redhat.com/show_bug.cgi?id=2310137
- https://github.com/libexpat/libexpat/issues/893
- http://www.openwall.com/lists/oss-security/2025/03/15/1
- https://blog.hartwork.org/posts/expat-2-7-0-released/
- https://bugzilla.suse.com/show_bug.cgi?id=1239618
- https://github.com/libexpat/libexpat/blob/R_2_7_0/expat/Changes#L40-L52
- https://gitlab.alpinelinux.org/alpine/aports/-/commit/d068c3ff36fc6f4789988a09c69b434db757db53
- https://ubuntu.com/security/CVE-2024-8176
- https://security.netapp.com/advisory/ntap-20250328-0009/
- https://access.redhat.com/errata/RHSA-2025:3531
- https://access.redhat.com/errata/RHSA-2025:3734
- https://access.redhat.com/errata/RHSA-2025:3913
- https://access.redhat.com/errata/RHSA-2025:4048
- https://access.redhat.com/errata/RHSA-2025:4447
- https://access.redhat.com/errata/RHSA-2025:4446
- https://access.redhat.com/errata/RHSA-2025:4448
- https://access.redhat.com/errata/RHSA-2025:4449
- https://www.kb.cert.org/vuls/id/760160
- https://access.redhat.com/errata/RHSA-2025:7444
- https://access.redhat.com/errata/RHSA-2025:7512
- https://access.redhat.com/errata/RHSA-2025:8385
- https://access.redhat.com/errata/RHSA-2025:13681
- http://seclists.org/fulldisclosure/2025/May/10
- http://seclists.org/fulldisclosure/2025/May/11
- http://seclists.org/fulldisclosure/2025/May/12
- http://seclists.org/fulldisclosure/2025/May/6
- http://seclists.org/fulldisclosure/2025/May/7
- http://seclists.org/fulldisclosure/2025/May/8
- http://www.openwall.com/lists/oss-security/2025/09/24/11
- https://access.redhat.com/errata/RHSA-2025:22033
- https://access.redhat.com/errata/RHSA-2025:22035
- https://access.redhat.com/errata/RHSA-2025:22034
- https://access.redhat.com/errata/RHSA-2025:22607
- https://access.redhat.com/errata/RHSA-2025:22785
- https://access.redhat.com/errata/RHSA-2025:22842
- https://access.redhat.com/errata/RHSA-2025:22871
- https://github.com/libexpat/libexpat/pull/973
high severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1
- Fixed in: 2.5.0-1+deb12u1
Detailed paths
-
Introduced through: golang@1.20 › 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.
An issue was discovered in libexpat before 2.6.3. xmlparse.c does not reject a negative length for XML_ParseBuffer.
Remediation
Upgrade Debian:12 expat to version 2.5.0-1+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-45490
- https://github.com/libexpat/libexpat/issues/887
- https://github.com/libexpat/libexpat/pull/890
- https://security.netapp.com/advisory/ntap-20241018-0004/
- http://seclists.org/fulldisclosure/2024/Dec/10
- http://seclists.org/fulldisclosure/2024/Dec/12
- http://seclists.org/fulldisclosure/2024/Dec/6
- http://seclists.org/fulldisclosure/2024/Dec/7
- http://seclists.org/fulldisclosure/2024/Dec/8
- https://lists.debian.org/debian-lts-announce/2024/09/msg00036.html
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-613116.html
high severity
- Vulnerable module: git
- Introduced through: git@1:2.39.2-1.1 and git/git-man@1:2.39.2-1.1
- Fixed in: 1:2.39.5-0+deb12u1
Detailed paths
-
Introduced through: golang@1.20 › git@1:2.39.2-1.1
-
Introduced through: golang@1.20 › 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
Upgrade Debian:12 git to version 1:2.39.5-0+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-25652
- http://www.openwall.com/lists/oss-security/2023/04/25/2
- https://github.com/git/git/commit/18e2b1cfc80990719275d7b08e6e50f3e8cbc902
- https://github.com/git/git/commit/668f2d53613ac8fd373926ebe219f2c29112d93e
- https://github.com/git/git/security/advisories/GHSA-2hvf-7c8p-28fx
- https://lists.debian.org/debian-lts-announce/2024/06/msg00018.html
- https://lists.debian.org/debian-lts-announce/2024/09/msg00009.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BSXOGVVBJLYX26IAYX6PJSYQB36BREWH/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PI7FZ4NNR5S5J5K6AMVQBH2JFP6NE4L7/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RKOXOAZ42HLXHXTW6JZI4L5DAIYDTYCU/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YFZWGQKB6MM5MNF2DLFTD7KS2KWPICKL/
- https://security.gentoo.org/glsa/202312-15
high severity
- Vulnerable module: git
- Introduced through: git@1:2.39.2-1.1 and git/git-man@1:2.39.2-1.1
- Fixed in: 1:2.39.5-0+deb12u2
Detailed paths
-
Introduced through: golang@1.20 › git@1:2.39.2-1.1
-
Introduced through: golang@1.20 › 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 fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals. Git defines a line-based protocol that is used to exchange information between Git and Git credential helpers. Some ecosystems (most notably, .NET and node.js) interpret single Carriage Return characters as newlines, which renders the protections against CVE-2020-5260 incomplete for credential helpers that treat Carriage Returns in this way. This issue has been addressed in commit b01b9b8 which is included in release versions v2.48.1, v2.47.2, v2.46.3, v2.45.3, v2.44.3, v2.43.6, v2.42.4, v2.41.3, and v2.40.4. Users are advised to upgrade. Users unable to upgrade should avoid cloning from untrusted URLs, especially recursive clones.
Remediation
Upgrade Debian:12 git to version 1:2.39.5-0+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-52006
- https://github.com/git-ecosystem/git-credential-manager/security/advisories/GHSA-86c2-4x57-wc8g
- https://github.com/git/git/commit/b01b9b81d36759cdcd07305e78765199e1bc2060
- https://github.com/git/git/security/advisories/GHSA-qm7j-c969-7j4q
- https://github.com/git/git/security/advisories/GHSA-r5ph-xg7q-xfrp
- https://lists.debian.org/debian-lts-announce/2025/01/msg00025.html
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u1
- Fixed in: 3.7.9-2+deb12u7
Detailed paths
-
Introduced through: golang@1.20 › gnutls28/libgnutls30@3.7.9-2+deb12u1
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 heap buffer overflow vulnerability exists in the DTLS handshake fragment reassembly logic of GnuTLS. The issue arises in merge_handshake_packet() where incoming handshake fragments are matched and merged based solely on handshake type, without validating that the message_length field remains consistent across all fragments of the same logical message. An attacker can exploit this by sending crafted DTLS fragments with conflicting message_length values, causing the implementation to allocate a buffer based on a smaller initial fragment and subsequently write beyond its bounds using larger, inconsistent fragments. Because the merge operation does not enforce proper bounds checking against the allocated buffer size, this results in an out-of-bounds write on the heap. The vulnerability is remotely exploitable without authentication via the DTLS handshake path and can lead to application crashes or potential memory corruption.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-33846
- https://access.redhat.com/security/cve/CVE-2026-33846
- https://bugzilla.redhat.com/show_bug.cgi?id=2450625
- https://access.redhat.com/errata/RHSA-2026:13274
- https://access.redhat.com/errata/RHSA-2026:20611
- https://access.redhat.com/errata/RHSA-2026:20613
- https://access.redhat.com/errata/RHSA-2026:20612
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u1
- Fixed in: 3.7.9-2+deb12u2
Detailed paths
-
Introduced through: golang@1.20 › gnutls28/libgnutls30@3.7.9-2+deb12u1
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
- https://security-tracker.debian.org/tracker/CVE-2024-0567
- http://www.openwall.com/lists/oss-security/2024/01/19/3
- https://access.redhat.com/errata/RHSA-2024:0533
- https://access.redhat.com/errata/RHSA-2024:1082
- https://access.redhat.com/errata/RHSA-2024:1383
- https://access.redhat.com/errata/RHSA-2024:2094
- https://access.redhat.com/security/cve/CVE-2024-0567
- https://bugzilla.redhat.com/show_bug.cgi?id=2258544
- https://gitlab.com/gnutls/gnutls/-/issues/1521
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/7ZEIOLORQ7N6WRPFXZSYDL2MC4LP7VFV/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GNXKVR5YNUEBNHAHM5GSYKBZX4W2HMN2/
- https://lists.gnupg.org/pipermail/gnutls-help/2024-January/004841.html
- https://security.netapp.com/advisory/ntap-20240202-0011/
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u1
- Fixed in: 3.7.9-2+deb12u2
Detailed paths
-
Introduced through: golang@1.20 › gnutls28/libgnutls30@3.7.9-2+deb12u1
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
- https://security-tracker.debian.org/tracker/CVE-2024-0553
- http://www.openwall.com/lists/oss-security/2024/01/19/3
- https://lists.debian.org/debian-lts-announce/2024/02/msg00010.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/7ZEIOLORQ7N6WRPFXZSYDL2MC4LP7VFV/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GNXKVR5YNUEBNHAHM5GSYKBZX4W2HMN2/
- https://security.netapp.com/advisory/ntap-20240202-0011/
- https://access.redhat.com/errata/RHSA-2024:0533
- https://access.redhat.com/errata/RHSA-2024:0627
- https://access.redhat.com/errata/RHSA-2024:0796
- https://access.redhat.com/errata/RHSA-2024:1082
- https://access.redhat.com/errata/RHSA-2024:1108
- https://access.redhat.com/errata/RHSA-2024:1383
- https://access.redhat.com/errata/RHSA-2024:2094
- https://access.redhat.com/security/cve/CVE-2024-0553
- https://bugzilla.redhat.com/show_bug.cgi?id=2258412
- https://gitlab.com/gnutls/gnutls/-/issues/1522
- https://lists.gnupg.org/pipermail/gnutls-help/2024-January/004841.html
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u1
- Fixed in: 3.7.9-2+deb12u7
Detailed paths
-
Introduced through: golang@1.20 › gnutls28/libgnutls30@3.7.9-2+deb12u1
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. A remote attacker could exploit an issue in the Datagram Transport Layer Security (DTLS) packet reordering logic. The comparator function, responsible for ordering DTLS packets by sequence numbers, did not correctly handle packets with duplicate sequence numbers. This could lead to unstable packet ordering or undefined behavior, resulting in a denial of service.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-42009
- https://access.redhat.com/security/cve/CVE-2026-42009
- https://bugzilla.redhat.com/show_bug.cgi?id=2467279
- https://access.redhat.com/errata/RHSA-2026:13274
- https://access.redhat.com/errata/RHSA-2026:20611
- https://access.redhat.com/errata/RHSA-2026:20613
- https://access.redhat.com/errata/RHSA-2026:20612
high severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u1, krb5/libk5crypto3@1.20.1-2+deb12u1 and others
- Fixed in: 1.20.1-2+deb12u2
Detailed paths
-
Introduced through: golang@1.20 › krb5/libgssapi-krb5-2@1.20.1-2+deb12u1
-
Introduced through: golang@1.20 › krb5/libk5crypto3@1.20.1-2+deb12u1
-
Introduced through: golang@1.20 › krb5/libkrb5-3@1.20.1-2+deb12u1
-
Introduced through: golang@1.20 › krb5/libkrb5support0@1.20.1-2+deb12u1
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.
In MIT Kerberos 5 (aka krb5) before 1.21.3, an attacker can modify the plaintext Extra Count field of a confidential GSS krb5 wrap token, causing the unwrapped token to appear truncated to the application.
Remediation
Upgrade Debian:12 krb5 to version 1.20.1-2+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-37370
- https://security.netapp.com/advisory/ntap-20241108-0007/
- https://github.com/krb5/krb5/commit/55fbf435edbe2e92dd8101669b1ce7144bc96fef
- https://web.mit.edu/kerberos/www/advisories/
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
high severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2+deb12u2
- Fixed in: 1:9.2p1-2+deb12u9
Detailed paths
-
Introduced through: golang@1.20 › openssh/openssh-client@1:9.2p1-2+deb12u2
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.
Vulnerability in the OpenSSH GSSAPI delta included in various Linux distributions. This vulnerability affects the GSSAPI patches added by various Linux distributions and does not affect the OpenSSH upstream project itself. The usage of sshpkt_disconnect() on an error, which does not terminate the process, allows an attacker to send an unexpected GSSAPI message type during the GSSAPI key exchange to the server, which will call the underlying function and continue the execution of the program without setting the related connection variables. As the variables are not initialized to NULL the code later accesses those uninitialized variables, accessing random memory, which could lead to undefined behavior. The recommended workaround is to use ssh_packet_disconnect() instead, which does terminate the process. The impact of the vulnerability depends heavily on the compiler flag hardening configuration.
Remediation
Upgrade Debian:12 openssh to version 1:9.2p1-2+deb12u9 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-3497
- https://ubuntu.com/security/CVE-2026-3497
- https://www.openwall.com/lists/oss-security/2026/03/12/3
- http://www.openwall.com/lists/oss-security/2026/03/12/3
- http://www.openwall.com/lists/oss-security/2026/03/14/3
- http://www.openwall.com/lists/oss-security/2026/03/14/4
- http://www.openwall.com/lists/oss-security/2026/03/18/2
- http://www.openwall.com/lists/oss-security/2026/03/18/4
- http://www.openwall.com/lists/oss-security/2026/03/18/5
- http://www.openwall.com/lists/oss-security/2026/03/18/7
- https://lists.debian.org/debian-lts-announce/2026/04/msg00014.html
high severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.11-1~deb12u2 and openssl/libssl3@3.0.11-1~deb12u2
- Fixed in: 3.0.14-1~deb12u2
Detailed paths
-
Introduced through: golang@1.20 › openssl@3.0.11-1~deb12u2
-
Introduced through: golang@1.20 › openssl/libssl3@3.0.11-1~deb12u2
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: Applications performing certificate name checks (e.g., TLS clients checking server certificates) may attempt to read an invalid memory address resulting in abnormal termination of the application process.
Impact summary: Abnormal termination of an application can a cause a denial of service.
Applications performing certificate name checks (e.g., TLS clients checking
server certificates) may attempt to read an invalid memory address when
comparing the expected name with an otherName subject alternative name of an
X.509 certificate. This may result in an exception that terminates the
application program.
Note that basic certificate chain validation (signatures, dates, ...) is not affected, the denial of service can occur only when the application also specifies an expected DNS name, Email address or IP address.
TLS servers rarely solicit client certificates, and even when they do, they generally don't perform a name check against a reference identifier (expected identity), but rather extract the presented identity after checking the certificate chain. So TLS servers are generally not affected and the severity of the issue is Moderate.
The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.14-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-6119
- https://github.com/openssl/openssl/commit/05f360d9e849a1b277db628f1f13083a7f8dd04f
- https://github.com/openssl/openssl/commit/06d1dc3fa96a2ba5a3e22735a033012aadc9f0d6
- https://github.com/openssl/openssl/commit/621f3729831b05ee828a3203eddb621d014ff2b2
- https://github.com/openssl/openssl/commit/7dfcee2cd2a63b2c64b9b4b0850be64cb695b0a0
- https://openssl-library.org/news/secadv/20240903.txt
- http://www.openwall.com/lists/oss-security/2024/09/03/4
- https://lists.freebsd.org/archives/freebsd-security/2024-September/000303.html
- https://security.netapp.com/advisory/ntap-20240912-0001/
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-613116.html
- https://cert-portal.siemens.com/productcert/html/ssa-769027.html
high severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.11-1~deb12u2 and openssl/libssl3@3.0.11-1~deb12u2
- Fixed in: 3.0.18-1~deb12u2
Detailed paths
-
Introduced through: golang@1.20 › openssl@3.0.11-1~deb12u2
-
Introduced through: golang@1.20 › openssl/libssl3@3.0.11-1~deb12u2
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 malformed PKCS#12 file can trigger a NULL pointer dereference in the PKCS12_item_decrypt_d2i_ex() function.
Impact summary: A NULL pointer dereference can trigger a crash which leads to Denial of Service for an application processing PKCS#12 files.
The PKCS12_item_decrypt_d2i_ex() function does not check whether the oct parameter is NULL before dereferencing it. When called from PKCS12_unpack_p7encdata() with a malformed PKCS#12 file, this parameter can be NULL, causing a crash. The vulnerability is limited to Denial of Service and cannot be escalated to achieve code execution or memory disclosure.
Exploiting this issue requires an attacker to provide a malformed PKCS#12 file to an application that processes it. For that reason the issue was assessed as Low severity according to our Security Policy.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#12 implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.18-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-69421
- https://github.com/openssl/openssl/commit/3524a29271f8191b8fd8a5257eb05173982a097b
- https://github.com/openssl/openssl/commit/36ecb4960872a4ce04bf6f1e1f4e78d75ec0c0c7
- https://github.com/openssl/openssl/commit/4bbc8d41a72c842ce4077a8a3eccd1109aaf74bd
- https://github.com/openssl/openssl/commit/643986985cd1c21221f941129d76fe0c2785aeb3
- https://github.com/openssl/openssl/commit/a2dbc539f0f9cc63832709fa5aa33ad9495eb19c
- https://openssl-library.org/news/secadv/20260127.txt
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
high severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.11-1~deb12u2 and openssl/libssl3@3.0.11-1~deb12u2
- Fixed in: 3.0.19-1~deb12u2
Detailed paths
-
Introduced through: golang@1.20 › openssl@3.0.11-1~deb12u2
-
Introduced through: golang@1.20 › openssl/libssl3@3.0.11-1~deb12u2
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: When a delta CRL that contains a Delta CRL Indicator extension is processed a NULL pointer dereference might happen if the required CRL Number extension is missing.
Impact summary: A NULL pointer dereference can trigger a crash which leads to a Denial of Service for an application.
When CRL processing and delta CRL processing is enabled during X.509 certificate verification, the delta CRL processing does not check whether the CRL Number extension is NULL before dereferencing it. When a malformed delta CRL file is being processed, this parameter can be NULL, causing a NULL pointer dereference.
Exploiting this issue requires the X509_V_FLAG_USE_DELTAS flag to be enabled in the verification context, the certificate being verified to contain a freshestCRL extension or the base CRL to have the EXFLAG_FRESHEST flag set, and an attacker to provide a malformed CRL to an application that processes it.
The vulnerability is limited to Denial of Service and cannot be escalated to achieve code execution or memory disclosure. For that reason the issue was assessed as Low severity according to our Security Policy.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.
Remediation
Upgrade Debian:12 openssl to version 3.0.19-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-28388
- https://github.com/openssl/openssl/commit/59c3b3158553ab53275bbbccca5cb305d591cf2e
- https://github.com/openssl/openssl/commit/5a0b4930779cd2408880979db765db919da55139
- https://github.com/openssl/openssl/commit/602542f2c0c2d5edb47128f93eac10b62aeeefb3
- https://github.com/openssl/openssl/commit/a9d187dd1000130100fa7ab915f8513532cb3bb8
- https://github.com/openssl/openssl/commit/d3a901e8d9f021f3e67d6cfbc12e768129862726
- https://openssl-library.org/news/secadv/20260407.txt
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
high severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.11-1~deb12u2 and openssl/libssl3@3.0.11-1~deb12u2
- Fixed in: 3.0.19-1~deb12u2
Detailed paths
-
Introduced through: golang@1.20 › openssl@3.0.11-1~deb12u2
-
Introduced through: golang@1.20 › openssl/libssl3@3.0.11-1~deb12u2
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: During processing of a crafted CMS EnvelopedData message with KeyAgreeRecipientInfo a NULL pointer dereference can happen.
Impact summary: Applications that process attacker-controlled CMS data may crash before authentication or cryptographic operations occur resulting in Denial of Service.
When a CMS EnvelopedData message that uses KeyAgreeRecipientInfo is processed, the optional parameters field of KeyEncryptionAlgorithmIdentifier is examined without checking for its presence. This results in a NULL pointer dereference if the field is missing.
Applications and services that call CMS_decrypt() on untrusted input (e.g., S/MIME processing or CMS-based protocols) are vulnerable.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.
Remediation
Upgrade Debian:12 openssl to version 3.0.19-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-28389
- https://github.com/openssl/openssl/commit/16cea4188e0ea567deb4f93f85902247e67384f5
- https://github.com/openssl/openssl/commit/785cbf7ea3b5a6f5adf0c1ccb92b79d89c35c616
- https://github.com/openssl/openssl/commit/7b5274e812400cacb6f3be4c2df5340923fa807f
- https://github.com/openssl/openssl/commit/c6725634e089eb2b634b10ede33944be7248172a
- https://github.com/openssl/openssl/commit/f80f83bc5fd036bc47d773e8b15a001e2b4ce686
- https://openssl-library.org/news/secadv/20260407.txt
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
high severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.11-1~deb12u2 and openssl/libssl3@3.0.11-1~deb12u2
- Fixed in: 3.0.19-1~deb12u2
Detailed paths
-
Introduced through: golang@1.20 › openssl@3.0.11-1~deb12u2
-
Introduced through: golang@1.20 › openssl/libssl3@3.0.11-1~deb12u2
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: During processing of a crafted CMS EnvelopedData message with KeyTransportRecipientInfo a NULL pointer dereference can happen.
Impact summary: Applications that process attacker-controlled CMS data may crash before authentication or cryptographic operations occur resulting in Denial of Service.
When a CMS EnvelopedData message that uses KeyTransportRecipientInfo with RSA-OAEP encryption is processed, the optional parameters field of RSA-OAEP SourceFunc algorithm identifier is examined without checking for its presence. This results in a NULL pointer dereference if the field is missing.
Applications and services that call CMS_decrypt() on untrusted input (e.g., S/MIME processing or CMS-based protocols) are vulnerable.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.
Remediation
Upgrade Debian:12 openssl to version 3.0.19-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-28390
- https://github.com/openssl/openssl/commit/01194a8f1941115cd0383bfa91c736dd3993c8bc
- https://github.com/openssl/openssl/commit/2e39b7a6993be445fddb9fbce316fa756e0397b6
- https://github.com/openssl/openssl/commit/af2a5fecd3e71a29e7568f9c1453dec5cebbaff4
- https://github.com/openssl/openssl/commit/ea7b4ea4f9f853521ba34830cbcadc970d2e0788
- https://github.com/openssl/openssl/commit/fd2f1a6cf53b9ceeca723a001aa4b825d7c7ee75
- https://openssl-library.org/news/secadv/20260407.txt
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
high severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u2
Detailed paths
-
Introduced through: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-24329
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/6PEVICI7YNGGMSL3UCMWGE66QFLATH72/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DSL6NSOAXWBJJ67XPLSSC74MNKZF3BBO/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/EM2XLZSTXG44TMFXF4E6VTGKR2MQCW3G/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/F2NY75GFDZ5T6YPN44D3VMFT5SUVTOTG/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GR5US3BYILYJ4SKBV6YBNPRUBAL5P2CN/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/H23OSKC6UG6IWOQAUPW74YUHWRWVXJP7/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JZTLGV2HYFF4AMYJL25VDIGAIHCU7UPA/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LWC4WGXER5P6Q75RFGL7QUTPP3N5JR7T/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MZEHSXSCMA4WWQKXT6QV7AAR6SWNZ2VP/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/O5SP4RT3RRS434ZS2HQKQJ3VZW7YPKYR/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OHHJHJRLEF3TDT2K3676CAUVRDD4CCMR/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PEUN6T22UJFXR7J5F6UUHCXXPKJ2DVHI/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PURM5CFDABEWAIWZFD2MQ7ZJGCPYSQ44/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/Q3J5N24ECS4B6MJDRO6UAYU6GPLYBDCL/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QRQHN7RWJQJHYP6E5EKESOYP5VDSHZG4/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RA2MBEEES6L46OD64OBSVUUMGKNGMOWW/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/T4IDB5OAR5Y4UK3HLMZBW4WEL2B7YFMJ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TZH26JGNZ5XYPZ5SAU3NKSBSPRE5OHTG/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/U2MZOJYGFCB5PPT6AKMAU72N7QOYWLBP/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UONZWLB4QVLQIY5CPDLEUEKH6WX4VQMC/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WTOAUJNDWZDRWVSXJ354AYZYKRMT56HU/
- https://github.com/python/cpython/issues/102153
- https://github.com/python/cpython/pull/99421
- https://lists.debian.org/debian-lts-announce/2023/09/msg00022.html
- https://lists.debian.org/debian-lts-announce/2024/11/msg00005.html
- https://lists.debian.org/debian-lts-announce/2024/12/msg00000.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/6PEVICI7YNGGMSL3UCMWGE66QFLATH72/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/DSL6NSOAXWBJJ67XPLSSC74MNKZF3BBO/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/EM2XLZSTXG44TMFXF4E6VTGKR2MQCW3G/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/F2NY75GFDZ5T6YPN44D3VMFT5SUVTOTG/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/GR5US3BYILYJ4SKBV6YBNPRUBAL5P2CN/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/H23OSKC6UG6IWOQAUPW74YUHWRWVXJP7/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/JZTLGV2HYFF4AMYJL25VDIGAIHCU7UPA/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LWC4WGXER5P6Q75RFGL7QUTPP3N5JR7T/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/MZEHSXSCMA4WWQKXT6QV7AAR6SWNZ2VP/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/O5SP4RT3RRS434ZS2HQKQJ3VZW7YPKYR/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/OHHJHJRLEF3TDT2K3676CAUVRDD4CCMR/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PEUN6T22UJFXR7J5F6UUHCXXPKJ2DVHI/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PURM5CFDABEWAIWZFD2MQ7ZJGCPYSQ44/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/Q3J5N24ECS4B6MJDRO6UAYU6GPLYBDCL/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/QRQHN7RWJQJHYP6E5EKESOYP5VDSHZG4/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/RA2MBEEES6L46OD64OBSVUUMGKNGMOWW/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/T4IDB5OAR5Y4UK3HLMZBW4WEL2B7YFMJ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/TZH26JGNZ5XYPZ5SAU3NKSBSPRE5OHTG/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/U2MZOJYGFCB5PPT6AKMAU72N7QOYWLBP/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/UONZWLB4QVLQIY5CPDLEUEKH6WX4VQMC/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WTOAUJNDWZDRWVSXJ354AYZYKRMT56HU/
- https://pointernull.com/security/python-url-parse-problem.html
- https://security.netapp.com/advisory/ntap-20230324-0004/
- https://www.kb.cert.org/vuls/id/127587
high severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u5
Detailed paths
-
Introduced through: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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.
There is a LOW severity vulnerability affecting CPython, specifically the 'http.cookies' standard library module.
When parsing cookies that contained backslashes for quoted characters in the cookie value, the parser would use an algorithm with quadratic complexity, resulting in excess CPU resources being used while parsing the value.
Remediation
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-7592
- https://github.com/python/cpython/issues/123067
- https://github.com/python/cpython/pull/123075
- https://mail.python.org/archives/list/security-announce@python.org/thread/HXJAAAALNUNGCQUS2W7WR6GFIZIHFOOK/
- https://github.com/python/cpython/commit/391e5626e3ee5af267b97e37abc7475732e67621
- https://github.com/python/cpython/commit/44e458357fca05ca0ae2658d62c8c595b048b5ef
- https://github.com/python/cpython/commit/a77ab24427a18bff817025adb03ca920dc3f1a06
- https://github.com/python/cpython/commit/b2f11ca7667e4d57c71c1c88b255115f16042d9a
- https://github.com/python/cpython/commit/d4ac921a4b081f7f996a5d2b101684b67ba0ed7f
- https://github.com/python/cpython/commit/d662e2db2605515a767f88ad48096b8ac623c774
- https://github.com/python/cpython/commit/dcc3eaef98cd94d6cb6cb0f44bd1c903d04f33b1
- https://security.netapp.com/advisory/ntap-20241018-0006/
- https://lists.debian.org/debian-lts-announce/2024/12/msg00000.html
high severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u4
Detailed paths
-
Introduced through: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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.
There is a MEDIUM severity vulnerability affecting CPython.
Regular expressions that allowed excessive backtracking during tarfile.TarFile header parsing are vulnerable to ReDoS via specifically-crafted tar archives.
Remediation
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-6232
- https://github.com/python/cpython/commit/4eaf4891c12589e3c7bdad5f5b076e4c8392dd06
- https://github.com/python/cpython/commit/743acbe872485dc18df4d8ab2dc7895187f062c4
- https://github.com/python/cpython/commit/d449caf8a179e3b954268b3a88eb9170be3c8fbf
- https://github.com/python/cpython/commit/ed3a49ea734ada357ff4442996fd4ae71d253373
- https://github.com/python/cpython/issues/121285
- https://github.com/python/cpython/pull/121286
- https://mail.python.org/archives/list/security-announce@python.org/thread/JRYFTPRHZRTLMZLWQEUHZSJXNHM4ACTY/
- https://github.com/python/cpython/commit/34ddb64d088dd7ccc321f6103d23153256caa5d4
- https://github.com/python/cpython/commit/7d1f50cd92ff7e10a1c15a8f591dde8a6843a64d
- https://github.com/python/cpython/commit/b4225ca91547aa97ed3aca391614afbb255bc877
- http://www.openwall.com/lists/oss-security/2024/09/03/5
- https://security.netapp.com/advisory/ntap-20241018-0007/
- https://lists.debian.org/debian-lts-announce/2024/12/msg00000.html
high severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u7
Detailed paths
-
Introduced through: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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.
When reading an HTTP response from a server, if no read amount is specified, the default behavior will be to use Content-Length. This allows a malicious server to cause the client to read large amounts of data into memory, potentially causing OOM or other DoS.
Remediation
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-13836
- https://github.com/python/cpython/commit/14b1fdb0a94b96f86fc7b86671ea9582b8676628
- https://github.com/python/cpython/commit/289f29b0fe38baf2d7cb5854f4bb573cc34a6a15
- https://github.com/python/cpython/commit/4ce27904b597c77d74dd93f2c912676021a99155
- https://github.com/python/cpython/commit/5a4c4a033a4a54481be6870aa1896fad732555b5
- https://github.com/python/cpython/issues/119451
- https://github.com/python/cpython/pull/119454
- https://mail.python.org/archives/list/security-announce@python.org/thread/OQ6G7MKRQIS3OAREC3HNG3D2DPOU34XO/
- https://github.com/python/cpython/commit/5dc101675fd22918facbbe0fecdc821502beaaf0
- https://github.com/python/cpython/commit/afc40bdd3dd71f343fd9016f6d8eebbacbd6587c
high severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u2
Detailed paths
-
Introduced through: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-41105
- https://mail.python.org/archives/list/security-announce@python.org/thread/D6CDW3ZZC5D444YGL3VQUY6D4ECMCQLD/
- https://github.com/python/cpython/issues/106242
- https://github.com/python/cpython/pull/107981
- https://github.com/python/cpython/pull/107982
- https://github.com/python/cpython/pull/107983
- https://mail.python.org/archives/list/security-announce%40python.org/thread/D6CDW3ZZC5D444YGL3VQUY6D4ECMCQLD/
- https://security.netapp.com/advisory/ntap-20231006-0015/
high severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.19-1~deb12u1 and systemd/libudev1@252.19-1~deb12u1
- Fixed in: 252.23-1~deb12u1
Detailed paths
-
Introduced through: golang@1.20 › systemd/libsystemd0@252.19-1~deb12u1
-
Introduced through: golang@1.20 › systemd/libudev1@252.19-1~deb12u1
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
Upgrade Debian:12 systemd to version 252.23-1~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-50387
- https://datatracker.ietf.org/doc/html/rfc4035
- https://lists.debian.org/debian-lts-announce/2024/11/msg00035.html
- https://lists.debian.org/debian-lts-announce/2024/09/msg00001.html
- http://www.openwall.com/lists/oss-security/2024/02/16/2
- http://www.openwall.com/lists/oss-security/2024/02/16/3
- https://access.redhat.com/security/cve/CVE-2023-50387
- https://bugzilla.suse.com/show_bug.cgi?id=1219823
- https://docs.powerdns.com/recursor/security-advisories/powerdns-advisory-2024-01.html
- https://gitlab.nic.cz/knot/knot-resolver/-/releases/v5.7.1
- https://kb.isc.org/docs/cve-2023-50387
- https://lists.debian.org/debian-lts-announce/2024/02/msg00006.html
- https://lists.debian.org/debian-lts-announce/2024/05/msg00011.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/6FV5O347JTX7P5OZA6NGO4MKTXRXMKOZ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BUIP7T7Z4T3UHLXFWG6XIVDP4GYPD3AI/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HVRDSJVZKMCXKKPP6PNR62T7RWZ3YSDZ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/IGSLGKUAQTW5JPPZCMF5YPEYALLRUZZ6/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PNNHZSZPG2E7NBMBNYPGHCFI4V4XRWNQ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/RGS7JN6FZXUSTC2XKQHH27574XOULYYJ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/SVYA42BLXUCIDLD35YIJPJSHDIADNYMP/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/TEXGOYGW7DBS3N2QSSQONZ4ENIRQEAPG/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/UQESRWMJCF4JEYJEAKLRM6CT55GLJAB7/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZDZFMEKQTZ4L7RY46FCENWFB5MDT263R/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BUIP7T7Z4T3UHLXFWG6XIVDP4GYPD3AI/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HVRDSJVZKMCXKKPP6PNR62T7RWZ3YSDZ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RGS7JN6FZXUSTC2XKQHH27574XOULYYJ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZDZFMEKQTZ4L7RY46FCENWFB5MDT263R/
- https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2024q1/017430.html
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-50387
- https://news.ycombinator.com/item?id=39367411
- https://news.ycombinator.com/item?id=39372384
- https://nlnetlabs.nl/news/2024/Feb/13/unbound-1.19.1-released/
- https://security.netapp.com/advisory/ntap-20240307-0007/
- https://www.athene-center.de/aktuelles/key-trap
- https://www.athene-center.de/fileadmin/content/PDF/Technical_Report_KeyTrap.pdf
- https://www.isc.org/blogs/2024-bind-security-release/
- https://www.securityweek.com/keytrap-dns-attack-could-disable-large-parts-of-internet-researchers/
- https://www.theregister.com/2024/02/13/dnssec_vulnerability_internet/
- https://github.com/knqyf263/CVE-2023-50387
high severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.19-1~deb12u1 and systemd/libudev1@252.19-1~deb12u1
- Fixed in: 252.23-1~deb12u1
Detailed paths
-
Introduced through: golang@1.20 › systemd/libsystemd0@252.19-1~deb12u1
-
Introduced through: golang@1.20 › systemd/libudev1@252.19-1~deb12u1
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
Upgrade Debian:12 systemd to version 252.23-1~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-50868
- http://www.openwall.com/lists/oss-security/2024/02/16/2
- http://www.openwall.com/lists/oss-security/2024/02/16/3
- https://access.redhat.com/security/cve/CVE-2023-50868
- https://bugzilla.suse.com/show_bug.cgi?id=1219826
- https://datatracker.ietf.org/doc/html/rfc5155
- https://docs.powerdns.com/recursor/security-advisories/powerdns-advisory-2024-01.html
- https://gitlab.nic.cz/knot/knot-resolver/-/releases/v5.7.1
- https://kb.isc.org/docs/cve-2023-50868
- https://lists.debian.org/debian-lts-announce/2024/02/msg00006.html
- https://lists.debian.org/debian-lts-announce/2024/05/msg00011.html
- https://lists.debian.org/debian-lts-announce/2024/09/msg00001.html
- https://lists.debian.org/debian-lts-announce/2024/11/msg00035.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/6FV5O347JTX7P5OZA6NGO4MKTXRXMKOZ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BUIP7T7Z4T3UHLXFWG6XIVDP4GYPD3AI/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HVRDSJVZKMCXKKPP6PNR62T7RWZ3YSDZ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/IGSLGKUAQTW5JPPZCMF5YPEYALLRUZZ6/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PNNHZSZPG2E7NBMBNYPGHCFI4V4XRWNQ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/RGS7JN6FZXUSTC2XKQHH27574XOULYYJ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/SVYA42BLXUCIDLD35YIJPJSHDIADNYMP/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/TEXGOYGW7DBS3N2QSSQONZ4ENIRQEAPG/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/UQESRWMJCF4JEYJEAKLRM6CT55GLJAB7/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZDZFMEKQTZ4L7RY46FCENWFB5MDT263R/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BUIP7T7Z4T3UHLXFWG6XIVDP4GYPD3AI/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HVRDSJVZKMCXKKPP6PNR62T7RWZ3YSDZ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZDZFMEKQTZ4L7RY46FCENWFB5MDT263R/
- https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2024q1/017430.html
- https://nlnetlabs.nl/news/2024/Feb/13/unbound-1.19.1-released/
- https://security.netapp.com/advisory/ntap-20240307-0008/
- https://www.isc.org/blogs/2024-bind-security-release/
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u1
- Fixed in: 3.7.9-2+deb12u7
Detailed paths
-
Introduced through: golang@1.20 › gnutls28/libgnutls30@3.7.9-2+deb12u1
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. This vulnerability occurs because permitted name constraints were incorrectly ignored when previous Certificate Authorities (CAs) only had excluded name constraints. A remote attacker could exploit this to bypass critical name constraint checks during certificate validation. This bypass could lead to the acceptance of invalid certificates, potentially enabling spoofing or man-in-the-middle attacks against affected systems.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-42011
- https://access.redhat.com/security/cve/CVE-2026-42011
- https://bugzilla.redhat.com/show_bug.cgi?id=2467437
- https://access.redhat.com/errata/RHSA-2026:13274
- https://access.redhat.com/errata/RHSA-2026:20611
- https://access.redhat.com/errata/RHSA-2026:20613
- https://access.redhat.com/errata/RHSA-2026:20612
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u1
- Fixed in: 3.7.9-2+deb12u7
Detailed paths
-
Introduced through: golang@1.20 › gnutls28/libgnutls30@3.7.9-2+deb12u1
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. This vulnerability occurs because gnutls performs case-sensitive comparisons of nameConstraints labels, specifically for dNSName (DNS) or rfc822Name (email) constraints within excludedSubtrees or permittedSubtrees. A remote attacker can exploit this by crafting a leaf certificate with casing differences in the Subject Alternative Name (SAN), leading to a policy bypass where a certificate that should be rejected is instead accepted. This could result in unauthorized access or information disclosure.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-3833
- https://access.redhat.com/errata/RHSA-2026:13274
- https://access.redhat.com/security/cve/CVE-2026-3833
- https://bugzilla.redhat.com/show_bug.cgi?id=2445763
- https://access.redhat.com/errata/RHSA-2026:20611
- https://access.redhat.com/errata/RHSA-2026:20613
- https://access.redhat.com/errata/RHSA-2026:20612
- https://gitlab.com/gnutls/gnutls/-/issues/1803
high severity
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2
- Fixed in: 3.40.1-2+deb12u1
Detailed paths
-
Introduced through: golang@1.20 › 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
Upgrade Debian:12 sqlite3 to version 3.40.1-2+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-7104
- https://lists.debian.org/debian-lts-announce/2024/09/msg00050.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/AYONA2XSNFMXLAW4IHLFI5UVV3QRNG5K/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/D6C2HN4T2S6GYNTAUXLH45LQZHK7QPHP/
- https://security.netapp.com/advisory/ntap-20240112-0008/
- https://sqlite.org/forum/forumpost/5bcbf4571c
- https://sqlite.org/src/info/0e4e7a05c4204b47
- https://vuldb.com/?ctiid.248999
- https://vuldb.com/?id.248999
high severity
- Vulnerable module: git
- Introduced through: git@1:2.39.2-1.1 and git/git-man@1:2.39.2-1.1
- Fixed in: 1:2.39.5-0+deb12u1
Detailed paths
-
Introduced through: golang@1.20 › git@1:2.39.2-1.1
-
Introduced through: golang@1.20 › 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.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, when cloning a local source repository that contains symlinks via the filesystem, Git may create hardlinks to arbitrary user-readable files on the same filesystem as the target repository in the objects/ directory. Cloning a local repository over the filesystem may creating hardlinks to arbitrary user-owned files on the same filesystem in the target Git repository's objects/ directory. When cloning a repository over the filesystem (without explicitly specifying the file:// protocol or --no-local), the optimizations for local cloning
will be used, which include attempting to hard link the object files instead of copying them. While the code includes checks against symbolic links in the source repository, which were added during the fix for CVE-2022-39253, these checks can still be raced because the hard link operation ultimately follows symlinks. If the object on the filesystem appears as a file during the check, and then a symlink during the operation, this will allow the adversary to bypass the check and create hardlinks in the destination objects directory to arbitrary, user-readable files. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4.
Remediation
Upgrade Debian:12 git to version 1:2.39.5-0+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-32021
- http://www.openwall.com/lists/oss-security/2024/05/14/2
- https://github.com/git/git/security/advisories/GHSA-mvxm-9j2h-qjx7
- https://lists.debian.org/debian-lts-announce/2024/06/msg00018.html
- https://lists.debian.org/debian-lts-announce/2024/09/msg00009.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/S4CK4IYTXEOBZTEM5K3T6LWOIZ3S44AR/
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u1
- Fixed in: 3.7.9-2+deb12u7
Detailed paths
-
Introduced through: golang@1.20 › gnutls28/libgnutls30@3.7.9-2+deb12u1
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. A remote attacker could exploit this vulnerability by presenting a specially crafted certificate that contains Uniform Resource Identifier (URI) or Service (SRV) Subject Alternative Names (SANs). This could cause the certificate validation process to incorrectly fall back to checking DNS hostnames against the Common Name (CN), potentially allowing the attacker to spoof legitimate services or intercept sensitive information.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-42012
- https://access.redhat.com/security/cve/CVE-2026-42012
- https://bugzilla.redhat.com/show_bug.cgi?id=2467441
- https://access.redhat.com/errata/RHSA-2026:20611
- https://access.redhat.com/errata/RHSA-2026:20613
- https://access.redhat.com/errata/RHSA-2026:20612
high severity
- Vulnerable module: gnupg2/dirmngr
- Introduced through: gnupg2/dirmngr@2.2.40-1.1, gnupg2/gnupg@2.2.40-1.1 and others
- Fixed in: 2.2.40-1.1+deb12u2
Detailed paths
-
Introduced through: golang@1.20 › gnupg2/dirmngr@2.2.40-1.1
-
Introduced through: golang@1.20 › gnupg2/gnupg@2.2.40-1.1
-
Introduced through: golang@1.20 › gnupg2/gnupg-l10n@2.2.40-1.1
-
Introduced through: golang@1.20 › gnupg2/gnupg-utils@2.2.40-1.1
-
Introduced through: golang@1.20 › gnupg2/gpg@2.2.40-1.1
-
Introduced through: golang@1.20 › gnupg2/gpg-agent@2.2.40-1.1
-
Introduced through: golang@1.20 › gnupg2/gpg-wks-client@2.2.40-1.1
-
Introduced through: golang@1.20 › gnupg2/gpg-wks-server@2.2.40-1.1
-
Introduced through: golang@1.20 › gnupg2/gpgconf@2.2.40-1.1
-
Introduced through: golang@1.20 › gnupg2/gpgsm@2.2.40-1.1
-
Introduced through: golang@1.20 › 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.
In GnuPG before 2.4.9, armor_filter in g10/armor.c has two increments of an index variable where one is intended, leading to an out-of-bounds write for crafted input. (For ExtendedLTS, 2.2.51 and later are fixed versions.)
Remediation
Upgrade Debian:12 gnupg2 to version 2.2.40-1.1+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-68973
- https://github.com/gpg/gnupg/blob/ff30683418695f5d2cc9e6cf8c9418e09378ebe4/g10/armor.c#L1305-L1306
- https://github.com/gpg/gnupg/commit/115d138ba599328005c5321c0ef9f00355838ca9
- https://github.com/gpg/gnupg/compare/gnupg-2.2.50...gnupg-2.2.51
- https://media.ccc.de/v/39c3-to-sign-or-not-to-sign-practical-vulnerabilities-i
- https://news.ycombinator.com/item?id=46403200
- https://www.openwall.com/lists/oss-security/2025/12/28/5
- http://www.openwall.com/lists/oss-security/2025/12/29/11
- https://lists.debian.org/debian-lts-announce/2026/01/msg00008.html
- https://gpg.fail/memcpy
high severity
- Vulnerable module: libcap2
- Introduced through: libcap2@1:2.66-4
- Fixed in: 1:2.66-4+deb12u3
Detailed paths
-
Introduced through: golang@1.20 › libcap2@1:2.66-4
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 flaw was found in libcap. A local unprivileged user can exploit a Time-of-check-to-time-of-use (TOCTOU) race condition in the cap_set_file() function. This allows an attacker with write access to a parent directory to redirect file capability updates to an attacker-controlled file. By doing so, capabilities can be injected into or stripped from unintended executables, leading to privilege escalation.
Remediation
Upgrade Debian:12 libcap2 to version 1:2.66-4+deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-4878
- https://access.redhat.com/errata/RHSA-2026:7473
- https://access.redhat.com/security/cve/CVE-2026-4878
- https://bugzilla.redhat.com/show_bug.cgi?id=2447554
- https://bugzilla.redhat.com/show_bug.cgi?id=2451615
- http://www.openwall.com/lists/oss-security/2026/04/07/14
- http://www.openwall.com/lists/oss-security/2026/04/07/4
- http://www.openwall.com/lists/oss-security/2026/04/08/9
- http://www.openwall.com/lists/oss-security/2026/04/09/5
- http://www.openwall.com/lists/oss-security/2026/04/09/6
- https://access.redhat.com/errata/RHSA-2026:12423
- https://access.redhat.com/errata/RHSA-2026:12441
- https://access.redhat.com/errata/RHSA-2026:13285
- https://access.redhat.com/errata/RHSA-2026:14162
- https://access.redhat.com/errata/RHSA-2026:14937
- https://access.redhat.com/errata/RHSA-2026:19130
- https://access.redhat.com/errata/RHSA-2026:19346
- https://access.redhat.com/errata/RHSA-2026:19456
- https://access.redhat.com/errata/RHSA-2026:19458
- https://access.redhat.com/errata/RHSA-2026:20595
- https://access.redhat.com/errata/RHSA-2026:21275
- https://access.redhat.com/errata/RHSA-2026:21254
- https://access.redhat.com/errata/RHSA-2026:22634
- https://access.redhat.com/errata/RHSA-2026:22957
medium severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2+deb12u2
- Fixed in: 1:9.2p1-2+deb12u5
Detailed paths
-
Introduced through: golang@1.20 › openssh/openssh-client@1:9.2p1-2+deb12u2
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.
A vulnerability was found in OpenSSH when the VerifyHostKeyDNS option is enabled. A machine-in-the-middle attack can be performed by a malicious machine impersonating a legit server. This issue occurs due to how OpenSSH mishandles error codes in specific conditions when verifying the host key. For an attack to be considered successful, the attacker needs to manage to exhaust the client's memory resource first, turning the attack complexity high.
Remediation
Upgrade Debian:12 openssh to version 1:9.2p1-2+deb12u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-26465
- https://access.redhat.com/security/cve/CVE-2025-26465
- https://bugzilla.redhat.com/show_bug.cgi?id=2344780
- https://blog.qualys.com/vulnerabilities-threat-research/2025/02/18/qualys-tru-discovers-two-vulnerabilities-in-openssh-cve-2025-26465-cve-2025-26466
- https://bugzilla.suse.com/show_bug.cgi?id=1237040
- https://ftp.openbsd.org/pub/OpenBSD/patches/7.6/common/008_ssh.patch.sig
- https://lists.debian.org/debian-lts-announce/2025/02/msg00020.html
- https://lists.mindrot.org/pipermail/openssh-unix-announce/2025-February/000161.html
- https://security.netapp.com/advisory/ntap-20250228-0003/
- https://ubuntu.com/security/CVE-2025-26465
- https://www.openssh.com/releasenotes.html#9.9p2
- https://www.openwall.com/lists/oss-security/2025/02/18/1
- https://www.openwall.com/lists/oss-security/2025/02/18/4
- https://www.theregister.com/2025/02/18/openssh_vulnerabilities_mitm_dos/
- https://www.vicarius.io/vsociety/posts/cve-2025-26465-detect-vulnerable-openssh
- https://www.vicarius.io/vsociety/posts/cve-2025-26465-mitigate-vulnerable-openssh
- https://access.redhat.com/errata/RHSA-2025:3837
- https://access.redhat.com/errata/RHSA-2025:6993
- https://access.redhat.com/errata/RHSA-2025:8385
- https://access.redhat.com/errata/RHSA-2025:16823
- https://access.redhat.com/solutions/7109879
- http://seclists.org/fulldisclosure/2025/May/7
- http://seclists.org/fulldisclosure/2025/May/8
- http://seclists.org/fulldisclosure/2025/Feb/18
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://seclists.org/oss-sec/2025/q1/144
medium severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.19-1~deb12u1 and systemd/libudev1@252.19-1~deb12u1
- Fixed in: 252.39-1~deb12u2
Detailed paths
-
Introduced through: golang@1.20 › systemd/libsystemd0@252.19-1~deb12u1
-
Introduced through: golang@1.20 › systemd/libudev1@252.19-1~deb12u1
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 flaw was found in systemd. The systemd-machined service contains an Improper Access Control vulnerability due to insufficient validation of the class parameter in the RegisterMachine D-Bus (Desktop Bus) method. A local unprivileged user can exploit this by attempting to register a machine with a specific class value, which may leave behind a usable, attacker-controlled machine object. This allows the attacker to invoke methods on the privileged object, leading to the execution of arbitrary commands with root privileges on the host system.
Remediation
Upgrade Debian:12 systemd to version 252.39-1~deb12u2 or higher.
References
medium severity
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10+deb12u5, curl/libcurl3-gnutls@7.88.1-10+deb12u5 and others
- Fixed in: 7.88.1-10+deb12u9
Detailed paths
-
Introduced through: golang@1.20 › curl@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl3-gnutls@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl4@7.88.1-10+deb12u5
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 is asked to use HSTS, the expiry time for a subdomain might overwrite a parent domain's cache entry, making it end sooner or later than otherwise intended.
This affects curl using applications that enable HSTS and use URLs with the
insecure HTTP:// scheme and perform transfers with hosts like
x.example.com as well as example.com where the first host is a subdomain
of the second host.
(The HSTS cache either needs to have been populated manually or there needs to have been previous HTTPS accesses done as the cache needs to have entries for the domains involved to trigger this problem.)
When x.example.com responds with Strict-Transport-Security: headers, this
bug can make the subdomain's expiry timeout bleed over and get set for the
parent domain example.com in curl's HSTS cache.
The result of a triggered bug is that HTTP accesses to example.com get
converted to HTTPS for a different period of time than what was asked for by
the origin server. If example.com for example stops supporting HTTPS at its
expiry time, curl might then fail to access http://example.com until the
(wrongly set) timeout expires. This bug can also expire the parent's entry
earlier, thus making curl inadvertently switch back to insecure HTTP earlier
than otherwise intended.
Remediation
Upgrade Debian:12 curl to version 7.88.1-10+deb12u9 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-9681
- https://curl.se/docs/CVE-2024-9681.html
- https://curl.se/docs/CVE-2024-9681.json
- https://hackerone.com/reports/2764830
- http://www.openwall.com/lists/oss-security/2024/11/06/2
- https://security.netapp.com/advisory/ntap-20241213-0006/
- http://seclists.org/fulldisclosure/2025/Apr/13
- http://seclists.org/fulldisclosure/2025/Apr/10
- http://seclists.org/fulldisclosure/2025/Apr/11
- http://seclists.org/fulldisclosure/2025/Apr/12
- http://seclists.org/fulldisclosure/2025/Apr/4
- http://seclists.org/fulldisclosure/2025/Apr/5
- http://seclists.org/fulldisclosure/2025/Apr/8
- http://seclists.org/fulldisclosure/2025/Apr/9
medium severity
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10+deb12u5, curl/libcurl3-gnutls@7.88.1-10+deb12u5 and others
- Fixed in: 7.88.1-10+deb12u7
Detailed paths
-
Introduced through: golang@1.20 › curl@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl3-gnutls@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl4@7.88.1-10+deb12u5
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's ASN1 parser code has the GTime2str() function, used for parsing an
ASN.1 Generalized Time field. If given an syntactically incorrect field, the
parser might end up using -1 for the length of the time fraction, leading to
a strlen() getting performed on a pointer to a heap buffer area that is not
(purposely) null terminated.
This flaw most likely leads to a crash, but can also lead to heap contents getting returned to the application when CURLINFO_CERTINFO is used.
Remediation
Upgrade Debian:12 curl to version 7.88.1-10+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-7264
- https://curl.se/docs/CVE-2024-7264.html
- https://curl.se/docs/CVE-2024-7264.json
- https://hackerone.com/reports/2629968
- https://github.com/curl/curl/commit/27959ecce75cdb2809c0bdb3286e60e08fadb519
- https://security.netapp.com/advisory/ntap-20240828-0008/
- http://www.openwall.com/lists/oss-security/2024/07/31/1
- https://security.netapp.com/advisory/ntap-20241025-0006/
- https://security.netapp.com/advisory/ntap-20241025-0010/
medium severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u1
- Fixed in: 3.7.9-2+deb12u5
Detailed paths
-
Introduced through: golang@1.20 › gnutls28/libgnutls30@3.7.9-2+deb12u1
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 NULL pointer dereference flaw was found in the GnuTLS software in _gnutls_figure_common_ciphersuite().
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-6395
- https://access.redhat.com/security/cve/CVE-2025-6395
- https://bugzilla.redhat.com/show_bug.cgi?id=2376755
- https://access.redhat.com/errata/RHSA-2025:16115
- https://access.redhat.com/errata/RHSA-2025:16116
- https://access.redhat.com/errata/RHSA-2025:17348
- https://access.redhat.com/errata/RHSA-2025:17361
- https://access.redhat.com/errata/RHSA-2025:17415
- https://access.redhat.com/errata/RHSA-2025:19088
- https://lists.debian.org/debian-lts-announce/2025/08/msg00005.html
- http://www.openwall.com/lists/oss-security/2025/07/11/3
- https://access.redhat.com/errata/RHSA-2025:17181
- https://access.redhat.com/errata/RHSA-2025:22529
- https://gitlab.com/gnutls/gnutls/-/issues/1718
- https://lists.gnupg.org/pipermail/gnutls-help/2025-July/004883.html
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
medium severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2+deb12u2
- Fixed in: 1:9.2p1-2+deb12u10
Detailed paths
-
Introduced through: golang@1.20 › openssh/openssh-client@1:9.2p1-2+deb12u2
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 before 10.3 can use unintended ECDSA algorithms. Listing of any ECDSA algorithm in PubkeyAcceptedAlgorithms or HostbasedAcceptedAlgorithms is misinterpreted to mean all ECDSA algorithms.
Remediation
Upgrade Debian:12 openssh to version 1:9.2p1-2+deb12u10 or higher.
References
medium severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.11-1~deb12u2 and openssl/libssl3@3.0.11-1~deb12u2
- Fixed in: 3.0.13-1~deb12u1
Detailed paths
-
Introduced through: golang@1.20 › openssl@3.0.11-1~deb12u2
-
Introduced through: golang@1.20 › openssl/libssl3@3.0.11-1~deb12u2
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
Upgrade Debian:12 openssl to version 3.0.13-1~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-6129
- http://www.openwall.com/lists/oss-security/2024/01/09/1
- http://www.openwall.com/lists/oss-security/2024/03/11/1
- https://security.netapp.com/advisory/ntap-20240216-0009/
- https://security.netapp.com/advisory/ntap-20240426-0008/
- https://security.netapp.com/advisory/ntap-20240426-0013/
- https://security.netapp.com/advisory/ntap-20240503-0011/
- https://github.com/openssl/openssl/commit/050d26383d4e264966fb83428e72d5d48f402d35
- https://github.com/openssl/openssl/commit/5b139f95c9a47a55a0c54100f3837b1eee942b04
- https://github.com/openssl/openssl/commit/f3fc5808fe9ff74042d639839610d03b8fdcc015
- https://www.openssl.org/news/secadv/20240109.txt
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
- https://cert-portal.siemens.com/productcert/html/ssa-331112.html
- https://cert-portal.siemens.com/productcert/html/ssa-769027.html
- https://cert-portal.siemens.com/productcert/html/ssa-915275.html
medium severity
new
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1
Detailed paths
-
Introduced through: golang@1.20 › 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 before 2.8.2 lacks handler call depth tracking for calls to XML_GetBuffer, XML_Parse, XML_ParseBuffer, XML_ParserFree, or XML_ParserReset from within handlers in cases of a policy violation. Thus, a use-after-free can occur,
Remediation
There is no fixed version for Debian:12 expat.
References
medium severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u1, krb5/libk5crypto3@1.20.1-2+deb12u1 and others
- Fixed in: 1.20.1-2+deb12u4
Detailed paths
-
Introduced through: golang@1.20 › krb5/libgssapi-krb5-2@1.20.1-2+deb12u1
-
Introduced through: golang@1.20 › krb5/libk5crypto3@1.20.1-2+deb12u1
-
Introduced through: golang@1.20 › krb5/libkrb5-3@1.20.1-2+deb12u1
-
Introduced through: golang@1.20 › krb5/libkrb5support0@1.20.1-2+deb12u1
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.
A vulnerability in the MIT Kerberos implementation allows GSSAPI-protected messages using RC4-HMAC-MD5 to be spoofed due to weaknesses in the MD5 checksum design. If RC4 is preferred over stronger encryption types, an attacker could exploit MD5 collisions to forge message integrity codes. This may lead to unauthorized message tampering.
Remediation
Upgrade Debian:12 krb5 to version 1.20.1-2+deb12u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-3576
- https://access.redhat.com/security/cve/CVE-2025-3576
- https://bugzilla.redhat.com/show_bug.cgi?id=2359465
- https://lists.debian.org/debian-lts-announce/2025/05/msg00047.html
- https://access.redhat.com/errata/RHSA-2025:8411
- https://access.redhat.com/errata/RHSA-2025:9418
- https://access.redhat.com/errata/RHSA-2025:9430
- https://access.redhat.com/errata/RHSA-2025:11487
- https://web.mit.edu/kerberos/krb5-1.22/krb5-1.22.html
- https://access.redhat.com/errata/RHSA-2025:13664
- https://access.redhat.com/errata/RHSA-2025:13777
- https://access.redhat.com/errata/RHSA-2025:15000
- https://access.redhat.com/errata/RHSA-2025:15002
- https://access.redhat.com/errata/RHSA-2025:15004
- https://access.redhat.com/errata/RHSA-2025:15001
- https://access.redhat.com/errata/RHSA-2025:15003
- https://cert-portal.siemens.com/productcert/html/ssa-577017.html
medium severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.19-1~deb12u1 and systemd/libudev1@252.19-1~deb12u1
- Fixed in: 252.21-1~deb12u1
Detailed paths
-
Introduced through: golang@1.20 › systemd/libsystemd0@252.19-1~deb12u1
-
Introduced through: golang@1.20 › systemd/libudev1@252.19-1~deb12u1
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
- https://security-tracker.debian.org/tracker/CVE-2023-7008
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4GMDEG5PKONWNHOEYSUDRT6JEOISRMN2/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QHNBXGKJWISJETTTDTZKTBFIBJUOSLKL/
- https://security.netapp.com/advisory/ntap-20241122-0004/
- https://access.redhat.com/errata/RHSA-2024:2463
- https://access.redhat.com/errata/RHSA-2024:3203
- https://access.redhat.com/security/cve/CVE-2023-7008
- https://bugzilla.redhat.com/show_bug.cgi?id=2222261
- https://bugzilla.redhat.com/show_bug.cgi?id=2222672
- https://github.com/systemd/systemd/issues/25676
- https://lists.debian.org/debian-lts-announce/2024/09/msg00001.html
medium severity
- Vulnerable module: apr/libapr1
- Introduced through: apr/libapr1@1.7.2-3
- Fixed in: 1.7.2-3+deb12u1
Detailed paths
-
Introduced through: golang@1.20 › apr/libapr1@1.7.2-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream apr package and not the apr package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
Lax permissions set by the Apache Portable Runtime library on Unix platforms would allow local users read access to named shared memory segments, potentially revealing sensitive application data.
This issue does not affect non-Unix platforms, or builds with APR_USE_SHMEM_SHMGET=1 (apr.h)
Users are recommended to upgrade to APR version 1.7.5, which fixes this issue.
Remediation
Upgrade Debian:12 apr to version 1.7.2-3+deb12u1 or higher.
References
medium severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u1, krb5/libk5crypto3@1.20.1-2+deb12u1 and others
- Fixed in: 1.20.1-2+deb12u3
Detailed paths
-
Introduced through: golang@1.20 › krb5/libgssapi-krb5-2@1.20.1-2+deb12u1
-
Introduced through: golang@1.20 › krb5/libk5crypto3@1.20.1-2+deb12u1
-
Introduced through: golang@1.20 › krb5/libkrb5-3@1.20.1-2+deb12u1
-
Introduced through: golang@1.20 › krb5/libkrb5support0@1.20.1-2+deb12u1
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
Upgrade Debian:12 krb5 to version 1.20.1-2+deb12u3 or higher.
References
medium severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.11-1~deb12u2 and openssl/libssl3@3.0.11-1~deb12u2
- Fixed in: 3.0.13-1~deb12u1
Detailed paths
-
Introduced through: golang@1.20 › openssl@3.0.11-1~deb12u2
-
Introduced through: golang@1.20 › openssl/libssl3@3.0.11-1~deb12u2
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
Upgrade Debian:12 openssl to version 3.0.13-1~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-0727
- http://www.openwall.com/lists/oss-security/2024/03/11/1
- https://security.netapp.com/advisory/ntap-20240208-0006/
- https://lists.debian.org/debian-lts-announce/2024/10/msg00033.html
- https://lists.debian.org/debian-lts-announce/2024/11/msg00000.html
- https://github.com/openssl/openssl/commit/09df4395b5071217b76dc7d3d2e630eb8c5a79c2
- https://github.com/openssl/openssl/commit/775acfdbd0c6af9ac855f34969cdab0c0c90844a
- https://github.com/openssl/openssl/commit/d135eeab8a5dbf72b3da5240bab9ddb7678dbd2c
- https://github.openssl.org/openssl/extended-releases/commit/03b3941d60c4bce58fab69a0c22377ab439bc0e8
- https://github.openssl.org/openssl/extended-releases/commit/aebaa5883e31122b404e450732dc833dc9dee539
- https://www.openssl.org/news/secadv/20240125.txt
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
- https://cert-portal.siemens.com/productcert/html/ssa-277137.html
- https://cert-portal.siemens.com/productcert/html/ssa-331112.html
- https://cert-portal.siemens.com/productcert/html/ssa-769027.html
- https://cert-portal.siemens.com/productcert/html/ssa-915275.html
medium severity
- Vulnerable module: pam/libpam-modules
- Introduced through: pam/libpam-modules@1.5.2-6+deb12u1, pam/libpam-modules-bin@1.5.2-6+deb12u1 and others
- Fixed in: 1.5.2-6+deb12u2
Detailed paths
-
Introduced through: golang@1.20 › pam/libpam-modules@1.5.2-6+deb12u1
-
Introduced through: golang@1.20 › pam/libpam-modules-bin@1.5.2-6+deb12u1
-
Introduced through: golang@1.20 › pam/libpam-runtime@1.5.2-6+deb12u1
-
Introduced through: golang@1.20 › pam/libpam0g@1.5.2-6+deb12u1
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
Upgrade Debian:12 pam to version 1.5.2-6+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-22365
- https://lists.debian.org/debian-lts-announce/2025/09/msg00021.html
- http://www.openwall.com/lists/oss-security/2024/01/18/3
- https://github.com/linux-pam/linux-pam
- https://github.com/linux-pam/linux-pam/commit/031bb5a5d0d950253b68138b498dc93be69a64cb
- https://github.com/linux-pam/linux-pam/releases/tag/v1.6.0
- https://cert-portal.siemens.com/productcert/html/ssa-577017.html
- https://cert-portal.siemens.com/productcert/html/ssa-794697.html
medium severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u7
Detailed paths
-
Introduced through: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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.
When loading a plist file, the plistlib module reads data in size specified by the file itself, meaning a malicious file can cause OOM and DoS issues
Remediation
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-13837
- https://github.com/python/cpython/commit/5a8b19677d818fb41ee55f310233772e15aa1a2b
- https://github.com/python/cpython/commit/694922cf40aa3a28f898b5f5ee08b71b4922df70
- https://github.com/python/cpython/commit/71fa8eb8233b37f16c88b6e3e583b461b205d1ba
- https://github.com/python/cpython/commit/b64441e4852383645af5b435411a6f849dd1b4cb
- https://github.com/python/cpython/issues/119342
- https://github.com/python/cpython/pull/119343
- https://mail.python.org/archives/list/security-announce@python.org/thread/2X5IBCJXRQAZ5PSERLHMSJFBHFR3QM2C/
- https://github.com/python/cpython/commit/568342cfc8f002d9a15f30238f26b9d2e0e79036
- https://github.com/python/cpython/commit/cefee7d118a26ef6cd43db59bb9d98ca9a331111
medium severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u7
Detailed paths
-
Introduced through: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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.
If the value passed to os.path.expandvars() is user-controlled a performance degradation is possible when expanding environment variables.
Remediation
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-6075
- https://github.com/python/cpython/commit/2e6150adccaaf5bd95d4c19dfd04a36e0b325d8c
- https://github.com/python/cpython/commit/5dceb93486176e6b4a6d9754491005113eb23427
- https://github.com/python/cpython/commit/631ba3407e3348ccd56ce5160c4fb2c5dc5f4d84
- https://github.com/python/cpython/commit/892747b4cf0f95ba8beb51c0d0658bfaa381ebca
- https://github.com/python/cpython/commit/9ab89c026aa9611c4b0b67c288b8303a480fe742
- https://github.com/python/cpython/commit/c8a5f3435c342964e0a432cc9fb448b7dbecd1ba
- https://github.com/python/cpython/commit/f029e8db626ddc6e3a3beea4eff511a71aaceb5c
- https://github.com/python/cpython/issues/136065
- https://mail.python.org/archives/list/security-announce@python.org/thread/IUP5QJ6D4KK6ULHOMPC7DPNKRYQTQNLA/
medium severity
- Vulnerable module: shadow/login
- Introduced through: shadow/login@1:4.13+dfsg1-1+b1 and shadow/passwd@1:4.13+dfsg1-1+b1
- Fixed in: 1:4.13+dfsg1-1+deb12u1
Detailed paths
-
Introduced through: golang@1.20 › shadow/login@1:4.13+dfsg1-1+b1
-
Introduced through: golang@1.20 › 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
Upgrade Debian:12 shadow to version 1:4.13+dfsg1-1+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-4641
- https://access.redhat.com/errata/RHSA-2023:6632
- https://access.redhat.com/errata/RHSA-2023:7112
- https://access.redhat.com/errata/RHSA-2024:0417
- https://access.redhat.com/errata/RHSA-2024:2577
- https://access.redhat.com/security/cve/CVE-2023-4641
- https://bugzilla.redhat.com/show_bug.cgi?id=2215945
- https://lists.debian.org/debian-lts-announce/2025/04/msg00026.html
medium severity
- Vulnerable module: tar
- Introduced through: tar@1.34+dfsg-1.2
- Fixed in: 1.34+dfsg-1.2+deb12u1
Detailed paths
-
Introduced through: golang@1.20 › 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
- https://security-tracker.debian.org/tracker/CVE-2022-48303
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/CRY7VEL4AIG3GLIEVCTOXRZNSVYDYYUD/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/X5VQYCO52Z7GAVCLRYUITN7KXHLRZQS4/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/CRY7VEL4AIG3GLIEVCTOXRZNSVYDYYUD/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/X5VQYCO52Z7GAVCLRYUITN7KXHLRZQS4/
- https://savannah.gnu.org/bugs/?62387
- https://savannah.gnu.org/patch/?10307
medium severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u1
- Fixed in: 3.7.9-2+deb12u6
Detailed paths
-
Introduced through: golang@1.20 › gnutls28/libgnutls30@3.7.9-2+deb12u1
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. This vulnerability allows a denial of service (DoS) by excessive CPU (Central Processing Unit) and memory consumption via specially crafted malicious certificates containing a large number of name constraints and subject alternative names (SANs).
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u6 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-14831
- https://access.redhat.com/security/cve/CVE-2025-14831
- https://bugzilla.redhat.com/show_bug.cgi?id=2423177
- https://access.redhat.com/errata/RHSA-2026:3477
- https://access.redhat.com/errata/RHSA-2026:4188
- https://gitlab.com/gnutls/gnutls/-/issues/1773
- https://access.redhat.com/errata/RHSA-2026:4655
- https://access.redhat.com/errata/RHSA-2026:4943
- https://access.redhat.com/errata/RHSA-2026:5585
- https://access.redhat.com/errata/RHSA-2026:5606
- https://access.redhat.com/errata/RHSA-2026:6630
- https://access.redhat.com/errata/RHSA-2026:6618
- https://access.redhat.com/errata/RHSA-2026:6737
- https://access.redhat.com/errata/RHSA-2026:6738
- https://access.redhat.com/errata/RHSA-2026:7329
- https://access.redhat.com/errata/RHSA-2026:7335
- https://access.redhat.com/errata/RHSA-2026:8747
- https://access.redhat.com/errata/RHSA-2026:8746
- https://access.redhat.com/errata/RHSA-2026:8748
- https://access.redhat.com/errata/RHSA-2026:7477
- https://access.redhat.com/errata/RHSA-2026:13812
- https://access.redhat.com/errata/RHSA-2026:16174
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
- https://access.redhat.com/errata/RHSA-2026:16008
- https://access.redhat.com/errata/RHSA-2026:16009
medium severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u1
- Fixed in: 3.7.9-2+deb12u4
Detailed paths
-
Introduced through: golang@1.20 › gnutls28/libgnutls30@3.7.9-2+deb12u1
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, which relies on libtasn1 for ASN.1 data processing. Due to an inefficient algorithm in libtasn1, decoding certain DER-encoded certificate data can take excessive time, leading to increased resource consumption. This flaw allows a remote attacker to send a specially crafted certificate, causing GnuTLS to become unresponsive or slow, resulting in a denial-of-service condition.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-12243
- https://access.redhat.com/security/cve/CVE-2024-12243
- https://bugzilla.redhat.com/show_bug.cgi?id=2344615
- https://gitlab.com/gnutls/libtasn1/-/issues/52
- https://lists.debian.org/debian-lts-announce/2025/02/msg00027.html
- https://access.redhat.com/errata/RHSA-2025:4051
- https://access.redhat.com/errata/RHSA-2025:7076
- https://access.redhat.com/errata/RHSA-2025:8020
- https://security.netapp.com/advisory/ntap-20250523-0002/
- https://access.redhat.com/errata/RHSA-2025:8385
- https://access.redhat.com/errata/RHSA-2025:17361
- https://gitlab.com/gnutls/gnutls/-/issues/1553
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-202008.html
medium severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u1
- Fixed in: 3.7.9-2+deb12u5
Detailed paths
-
Introduced through: golang@1.20 › gnutls28/libgnutls30@3.7.9-2+deb12u1
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 heap-buffer-overread vulnerability was found in GnuTLS in how it handles the Certificate Transparency (CT) Signed Certificate Timestamp (SCT) extension during X.509 certificate parsing. This flaw allows a malicious user to create a certificate containing a malformed SCT extension (OID 1.3.6.1.4.1.11129.2.4.2) that contains sensitive data. This issue leads to the exposure of confidential information when GnuTLS verifies certificates from certain websites when the certificate (SCT) is not checked correctly.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-32989
- https://access.redhat.com/security/cve/CVE-2025-32989
- https://bugzilla.redhat.com/show_bug.cgi?id=2359621
- https://access.redhat.com/errata/RHSA-2025:16115
- https://access.redhat.com/errata/RHSA-2025:16116
- https://access.redhat.com/errata/RHSA-2025:17348
- https://access.redhat.com/errata/RHSA-2025:17361
- https://access.redhat.com/errata/RHSA-2025:19088
- http://www.openwall.com/lists/oss-security/2025/07/11/3
- https://access.redhat.com/errata/RHSA-2025:17181
- https://access.redhat.com/errata/RHSA-2025:22529
- https://lists.gnupg.org/pipermail/gnutls-help/2025-July/004883.html
- https://access.redhat.com/errata/RHSA-2026:7477
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
medium severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u1
- Fixed in: 3.7.9-2+deb12u7
Detailed paths
-
Introduced through: golang@1.20 › gnutls28/libgnutls30@3.7.9-2+deb12u1
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. An off-by-one error exists in the PKCS#12 bag element bounds check. This vulnerability allows an remote attacker to write past the internal array of a PKCS#12 bag when appending to a bag that already contains 32 elements. This memory corruption could lead to a denial of service (DoS) or potentially other unspecified impacts.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-42015
- https://access.redhat.com/security/cve/CVE-2026-42015
- https://bugzilla.redhat.com/show_bug.cgi?id=2467678
- https://access.redhat.com/errata/RHSA-2026:20611
- https://access.redhat.com/errata/RHSA-2026:20613
- https://access.redhat.com/errata/RHSA-2026:20612
medium severity
- Vulnerable module: libtasn1-6
- Introduced through: libtasn1-6@4.19.0-2
- Fixed in: 4.19.0-2+deb12u1
Detailed paths
-
Introduced through: golang@1.20 › libtasn1-6@4.19.0-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libtasn1-6 package and not the libtasn1-6 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A flaw in libtasn1 causes inefficient handling of specific certificate data. When processing a large number of elements in a certificate, libtasn1 takes much longer than expected, which can slow down or even crash the system. This flaw allows an attacker to send a specially crafted certificate, causing a denial of service attack.
Remediation
Upgrade Debian:12 libtasn1-6 to version 4.19.0-2+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-12133
- https://access.redhat.com/security/cve/CVE-2024-12133
- https://bugzilla.redhat.com/show_bug.cgi?id=2344611
- https://gitlab.com/gnutls/libtasn1/-/issues/52
- http://www.openwall.com/lists/oss-security/2025/02/06/6
- https://lists.debian.org/debian-lts-announce/2025/02/msg00025.html
- https://access.redhat.com/errata/RHSA-2025:4049
- https://access.redhat.com/errata/RHSA-2025:7077
- https://access.redhat.com/errata/RHSA-2025:8021
- https://security.netapp.com/advisory/ntap-20250523-0003/
- https://access.redhat.com/errata/RHSA-2025:8385
- https://access.redhat.com/errata/RHSA-2025:17347
- https://gitlab.com/gnutls/libtasn1/-/blob/master/doc/security/CVE-2024-12133.md
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-202008.html
medium severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.11-1~deb12u2 and openssl/libssl3@3.0.11-1~deb12u2
- Fixed in: 3.0.13-1~deb12u1
Detailed paths
-
Introduced through: golang@1.20 › openssl@3.0.11-1~deb12u2
-
Introduced through: golang@1.20 › openssl/libssl3@3.0.11-1~deb12u2
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
Upgrade Debian:12 openssl to version 3.0.13-1~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-5678
- http://www.openwall.com/lists/oss-security/2023/11/06/2
- http://www.openwall.com/lists/oss-security/2024/03/11/1
- https://security.netapp.com/advisory/ntap-20231130-0010/
- https://lists.debian.org/debian-lts-announce/2024/10/msg00033.html
- https://lists.debian.org/debian-lts-announce/2024/11/msg00000.html
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=34efaef6c103d636ab507a0cc34dca4d3aecc055
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=710fee740904b6290fef0dd5536fbcedbc38ff0c
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=db925ae2e65d0d925adef429afc37f75bd1c2017
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=ddeb4b6c6d527e54ce9a99cba785c0f7776e54b6
- https://www.openssl.org/news/secadv/20231106.txt
- https://cert-portal.siemens.com/productcert/html/ssa-093430.html
- https://cert-portal.siemens.com/productcert/html/ssa-128433.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
- https://cert-portal.siemens.com/productcert/html/ssa-277137.html
- https://cert-portal.siemens.com/productcert/html/ssa-331112.html
- https://cert-portal.siemens.com/productcert/html/ssa-341067.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-556635.html
- https://cert-portal.siemens.com/productcert/html/ssa-613116.html
- https://cert-portal.siemens.com/productcert/html/ssa-769027.html
- https://cert-portal.siemens.com/productcert/html/ssa-794697.html
- https://cert-portal.siemens.com/productcert/html/ssa-915275.html
medium severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u2
Detailed paths
-
Introduced through: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-40217
- https://mail.python.org/archives/list/security-announce@python.org/thread/PEPLII27KYHLF4AK3ZQGKYNCRERG4YXY/
- https://lists.debian.org/debian-lts-announce/2023/09/msg00022.html
- https://lists.debian.org/debian-lts-announce/2023/10/msg00017.html
- https://lists.debian.org/debian-lts-announce/2024/11/msg00005.html
- https://lists.debian.org/debian-lts-announce/2024/12/msg00000.html
- https://mail.python.org/archives/list/security-announce%40python.org/thread/PEPLII27KYHLF4AK3ZQGKYNCRERG4YXY/
- https://security.netapp.com/advisory/ntap-20231006-0014/
- https://www.python.org/dev/security/
medium severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u7
Detailed paths
-
Introduced through: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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.
When building nested elements using xml.dom.minidom methods such as appendChild() that have a dependency on _clear_id_cache() the algorithm is quadratic. Availability can be impacted when building excessively nested documents.
Remediation
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-12084
- https://github.com/python/cpython/commit/027f21e417b26eed4505ac2db101a4352b7c51a0
- https://github.com/python/cpython/commit/08d8e18ad81cd45bc4a27d6da478b51ea49486e4
- https://github.com/python/cpython/commit/ddcd2acd85d891a53e281c773b3093f9db953964
- https://github.com/python/cpython/issues/142145
- https://github.com/python/cpython/pull/142146
- https://github.com/python/cpython/commit/27648a1818749ef44c420afe6173af6868715437
- https://github.com/python/cpython/commit/8d2d7bb2e754f8649a68ce4116271a4932f76907
- https://github.com/python/cpython/commit/9c9dda6625a2a90d2a06c657eee021d6be19842d
- https://github.com/python/cpython/commit/a696ba8b4d42fd632afc9bc88ad830a2e4cceed8
- https://github.com/python/cpython/commit/41f468786762348960486c166833a218a0a436af
- https://github.com/python/cpython/commit/57937a8e5e293f0dcba5115f7b7a11b1e0c9a273
- https://github.com/python/cpython/commit/e91c11449cad34bac3ea55ee09ca557691d92b53
- https://github.com/python/cpython/commit/a46c10ec9d4050ab67b8a932e0859a2ea60c3cb8
- https://github.com/python/cpython/commit/c97e87593063d84a2bd9fe7068b30eb44de23dc0
medium severity
- 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: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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.
When passing data to the b64decode(), standard_b64decode(), and urlsafe_b64decode() functions in the "base64" module the characters "+/" will always be accepted, regardless of the value of "altchars" parameter, typically used to establish an "alternative base64 alphabet" such as the URL safe alphabet. This behavior matches what is recommended in earlier base64 RFCs, but newer RFCs now recommend either dropping characters outside the specified base64 alphabet or raising an error. The old behavior has the possibility of causing data integrity issues.
This behavior can only be insecure if your application uses an alternate base64 alphabet (without "+/"). If your application does not use the "altchars" parameter or the urlsafe_b64decode() function, then your application does not use an alternative base64 alphabet.
The attached patches DOES NOT make the base64-decode behavior raise an error, as this would be a change in behavior and break existing programs. Instead, the patch deprecates the behavior which will be replaced with the newly recommended behavior in a future version of Python. Users are recommended to mitigate by verifying user-controlled inputs match the base64 alphabet they are expecting or verify that their application would not be affected if the b64decode() functions accepted "+" or "/" outside of altchars.
Remediation
There is no fixed version for Debian:12 python3.11.
References
- https://security-tracker.debian.org/tracker/CVE-2025-12781
- https://github.com/python/cpython/commit/13360efd385d1a7d0659beba03787ea3d063ef9b
- https://github.com/python/cpython/commit/1be80bec7960f5ccd059e75f3dfbd45fca302947
- https://github.com/python/cpython/commit/9060b4abbe475591b6230b23c2afefeff26fcca5
- https://github.com/python/cpython/commit/e95e783dff443b68e8179fdb57737025bf02ba76
- https://github.com/python/cpython/commit/fd17ee026fa9b67f6288cbafe374a3e479fe03a5
- https://github.com/python/cpython/issues/125346
- https://github.com/python/cpython/pull/141128
- https://mail.python.org/archives/list/security-announce@python.org/thread/KRI7GC6S27YV5NJ4FPDALS2WI5ENAFJ6/
medium severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u5
Detailed paths
-
Introduced through: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-27043
- http://python.com
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4ZAEFSFZDNBNJPNOUTLG5COISGQDLMGV/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/75DTHSTNOFFNAWHXKMDXS7EJWC6W2FUC/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ARI7VDSNTQVXRQFM6IK5GSSLEIYV4VZH/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BQAKLUJMHFGVBRDPEY57BJGNCE5UUPHW/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HXYVPEZUA3465AEFX5JVFVP7KIFZMF3N/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/N6M5I6OQHJABNEYY555HUMMKX3Y4P25Z/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NEUNZSZ3CVSM2QWVYH3N2XGOCDWNYUA3/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ORLXS5YTKN65E2Q2NWKXMFS5FWQHRNZW/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/P2MAICLFDDO3QVNHTZ2OCERZQ34R2PIC/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/P2W2BZQIHMCKRI5FNBJERFYMS5PK6TAH/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PHVGRKQAGANCSGFI3QMYOCIMS4IFOZA5/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PU6Y2S5CBN5BWCBDAJFTGIBZLK3S2G3J/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QDRDDPDN3VFIYXJIYEABY6USX5EU66AG/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RDDC2VOX7OQC6OHMYTVD4HLFZIV6PYBC/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SINP4OVYNB2AGDYI2GS37EMW3H3F7XPZ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VZXC32CJ7TWDPJO6GY2XIQRO7JZX5FLP/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XWMBD4LNHWEXRI6YVFWJMTJQUL5WOFTS/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YQVY5C5REXWJIORJIL2FIL3ALOEJEF72/
- http://seclists.org/fulldisclosure/2025/Apr/8
- https://lists.debian.org/debian-lts-announce/2024/11/msg00024.html
- https://lists.debian.org/debian-lts-announce/2024/12/msg00000.html
- http://python.org
- https://github.com/python/cpython/issues/102988
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4ZAEFSFZDNBNJPNOUTLG5COISGQDLMGV/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/75DTHSTNOFFNAWHXKMDXS7EJWC6W2FUC/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ARI7VDSNTQVXRQFM6IK5GSSLEIYV4VZH/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BQAKLUJMHFGVBRDPEY57BJGNCE5UUPHW/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HXYVPEZUA3465AEFX5JVFVP7KIFZMF3N/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/N6M5I6OQHJABNEYY555HUMMKX3Y4P25Z/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/NEUNZSZ3CVSM2QWVYH3N2XGOCDWNYUA3/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ORLXS5YTKN65E2Q2NWKXMFS5FWQHRNZW/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/P2MAICLFDDO3QVNHTZ2OCERZQ34R2PIC/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/P2W2BZQIHMCKRI5FNBJERFYMS5PK6TAH/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PHVGRKQAGANCSGFI3QMYOCIMS4IFOZA5/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PU6Y2S5CBN5BWCBDAJFTGIBZLK3S2G3J/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/QDRDDPDN3VFIYXJIYEABY6USX5EU66AG/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/RDDC2VOX7OQC6OHMYTVD4HLFZIV6PYBC/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/SINP4OVYNB2AGDYI2GS37EMW3H3F7XPZ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/SOX7BCN6YL7B3RFPEEXPIU5CMTEHJOKR/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VZXC32CJ7TWDPJO6GY2XIQRO7JZX5FLP/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/XWMBD4LNHWEXRI6YVFWJMTJQUL5WOFTS/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/YQVY5C5REXWJIORJIL2FIL3ALOEJEF72/
- https://python-security.readthedocs.io/vuln/email-parseaddr-realname.html
- https://security.netapp.com/advisory/ntap-20230601-0003/
- https://cert-portal.siemens.com/productcert/html/ssa-202008.html
- https://cert-portal.siemens.com/productcert/html/ssa-577017.html
medium severity
- 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: golang@1.20 › util-linux/bsdutils@1:2.38.1-5+b1
-
Introduced through: golang@1.20 › util-linux/libblkid1@2.38.1-5+b1
-
Introduced through: golang@1.20 › util-linux/libmount1@2.38.1-5+b1
-
Introduced through: golang@1.20 › util-linux/libsmartcols1@2.38.1-5+b1
-
Introduced through: golang@1.20 › util-linux/libuuid1@2.38.1-5+b1
-
Introduced through: golang@1.20 › util-linux/mount@2.38.1-5+b1
-
Introduced through: golang@1.20 › util-linux/util-linux@2.38.1-5+b1
-
Introduced through: golang@1.20 › 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 util-linux. Improper hostname canonicalization in the login(1) utility, when invoked with the -h option, can modify the supplied remote hostname before setting PAM_RHOST. A remote attacker could exploit this by providing a specially crafted hostname, potentially bypassing host-based Pluggable Authentication Modules (PAM) access control rules that rely on fully qualified domain names. This could lead to unauthorized access.
Remediation
There is no fixed version for Debian:12 util-linux.
References
medium severity
- Vulnerable module: gcc-12
- Introduced through: gcc-12@12.2.0-14, gcc-12/cpp-12@12.2.0-14 and others
- Fixed in: 12.2.0-14+deb12u1
Detailed paths
-
Introduced through: golang@1.20 › gcc-12@12.2.0-14
-
Introduced through: golang@1.20 › gcc-12/cpp-12@12.2.0-14
-
Introduced through: golang@1.20 › gcc-12/g++-12@12.2.0-14
-
Introduced through: golang@1.20 › gcc-12/gcc-12-base@12.2.0-14
-
Introduced through: golang@1.20 › gcc-12/libasan8@12.2.0-14
-
Introduced through: golang@1.20 › gcc-12/libatomic1@12.2.0-14
-
Introduced through: golang@1.20 › gcc-12/libcc1-0@12.2.0-14
-
Introduced through: golang@1.20 › gcc-12/libgcc-12-dev@12.2.0-14
-
Introduced through: golang@1.20 › gcc-12/libgcc-s1@12.2.0-14
-
Introduced through: golang@1.20 › gcc-12/libgomp1@12.2.0-14
-
Introduced through: golang@1.20 › gcc-12/libitm1@12.2.0-14
-
Introduced through: golang@1.20 › gcc-12/liblsan0@12.2.0-14
-
Introduced through: golang@1.20 › gcc-12/libquadmath0@12.2.0-14
-
Introduced through: golang@1.20 › gcc-12/libstdc++-12-dev@12.2.0-14
-
Introduced through: golang@1.20 › gcc-12/libstdc++6@12.2.0-14
-
Introduced through: golang@1.20 › gcc-12/libtsan2@12.2.0-14
-
Introduced through: golang@1.20 › gcc-12/libubsan1@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
Upgrade Debian:12 gcc-12 to version 12.2.0-14+deb12u1 or higher.
References
medium severity
- Vulnerable module: git
- Introduced through: git@1:2.39.2-1.1 and git/git-man@1:2.39.2-1.1
- Fixed in: 1:2.39.5-0+deb12u2
Detailed paths
-
Introduced through: golang@1.20 › git@1:2.39.2-1.1
-
Introduced through: golang@1.20 › 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 fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals. When Git asks for credentials via a terminal prompt (i.e. without using any credential helper), it prints out the host name for which the user is expected to provide a username and/or a password. At this stage, any URL-encoded parts have been decoded already, and are printed verbatim. This allows attackers to craft URLs that contain ANSI escape sequences that the terminal interpret to confuse users e.g. into providing passwords for trusted Git hosting sites when in fact they are then sent to untrusted sites that are under the attacker's control. This issue has been patch via commits 7725b81 and c903985 which are included in release versions v2.48.1, v2.47.2, v2.46.3, v2.45.3, v2.44.3, v2.43.6, v2.42.4, v2.41.3, and v2.40.4. Users are advised to upgrade. Users unable to upgrade should avoid cloning from untrusted URLs, especially recursive clones.
Remediation
Upgrade Debian:12 git to version 1:2.39.5-0+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-50349
- https://github.com/git/git/commit/7725b8100ffbbff2750ee4d61a0fcc1f53a086e8
- https://github.com/git/git/commit/c903985bf7e772e2d08275c1a95c8a55ab011577
- https://github.com/git/git/security/advisories/GHSA-hmg8-h7qf-7cxr
- https://lists.debian.org/debian-lts-announce/2025/01/msg00025.html
medium severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.19-1~deb12u1 and systemd/libudev1@252.19-1~deb12u1
- Fixed in: 252.38-1~deb12u1
Detailed paths
-
Introduced through: golang@1.20 › systemd/libsystemd0@252.19-1~deb12u1
-
Introduced through: golang@1.20 › systemd/libudev1@252.19-1~deb12u1
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-coredump. This flaw allows an attacker to force a SUID process to crash and replace it with a non-SUID binary to access the original's privileged process coredump, allowing the attacker to read sensitive data, such as /etc/shadow content, loaded by the original process.
A SUID binary or process has a special type of permission, which allows the process to run with the file owner's permissions, regardless of the user executing the binary. This allows the process to access more restricted data than unprivileged users or processes would be able to. An attacker can leverage this flaw by forcing a SUID process to crash and force the Linux kernel to recycle the process PID before systemd-coredump can analyze the /proc/pid/auxv file. If the attacker wins the race condition, they gain access to the original's SUID process coredump file. They can read sensitive content loaded into memory by the original binary, affecting data confidentiality.
Remediation
Upgrade Debian:12 systemd to version 252.38-1~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-4598
- https://access.redhat.com/security/cve/CVE-2025-4598
- https://bugzilla.redhat.com/show_bug.cgi?id=2369242
- https://www.openwall.com/lists/oss-security/2025/05/29/3
- http://www.openwall.com/lists/oss-security/2025/06/05/1
- http://www.openwall.com/lists/oss-security/2025/06/05/3
- https://blogs.oracle.com/linux/post/analysis-of-cve-2025-4598
- https://ciq.com/blog/the-real-danger-of-systemd-coredump-cve-2025-4598/
- https://www.openwall.com/lists/oss-security/2025/08/18/3
- http://seclists.org/fulldisclosure/2025/Jun/9
- https://lists.debian.org/debian-lts-announce/2025/07/msg00022.html
- http://www.openwall.com/lists/oss-security/2025/08/18/3
- https://access.redhat.com/errata/RHSA-2025:22660
- https://access.redhat.com/errata/RHSA-2025:22868
- https://access.redhat.com/errata/RHSA-2025:23234
- https://access.redhat.com/errata/RHSA-2025:23227
- https://access.redhat.com/errata/RHSA-2026:0414
- https://access.redhat.com/errata/RHSA-2026:1652
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://access.redhat.com/errata/RHSA-2026:18153
medium severity
- Vulnerable module: mercurial
- Introduced through: mercurial@6.3.2-1 and mercurial/mercurial-common@6.3.2-1
- Fixed in: 6.3.2-1+deb12u1
Detailed paths
-
Introduced through: golang@1.20 › mercurial@6.3.2-1
-
Introduced through: golang@1.20 › mercurial/mercurial-common@6.3.2-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream mercurial package and not the mercurial package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability was found in Mercurial SCM 4.5.3/71.19.145.211. It has been declared as problematic. This vulnerability affects unknown code of the component Web Interface. The manipulation of the argument cmd leads to cross site scripting. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
Remediation
Upgrade Debian:12 mercurial to version 6.3.2-1+deb12u1 or higher.
References
medium severity
- Vulnerable module: subversion/libsvn1
- Introduced through: subversion/libsvn1@1.14.2-4+b2 and subversion/subversion@1.14.2-4+b2
- Fixed in: 1.14.2-4+deb12u1
Detailed paths
-
Introduced through: golang@1.20 › subversion/libsvn1@1.14.2-4+b2
-
Introduced through: golang@1.20 › subversion/subversion@1.14.2-4+b2
NVD Description
Note: Versions mentioned in the description apply only to the upstream subversion package and not the subversion package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
Insufficient validation of filenames against control characters in Apache Subversion repositories served via mod_dav_svn allows authenticated users with commit access to commit a corrupted revision, leading to disruption for users of the repository.
All versions of Subversion up to and including Subversion 1.14.4 are affected if serving repositories via mod_dav_svn. Users are recommended to upgrade to version 1.14.5, which fixes this issue.
Repositories served via other access methods are not affected.
Remediation
Upgrade Debian:12 subversion to version 1.14.2-4+deb12u1 or higher.
References
medium severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u1
- Fixed in: 3.7.9-2+deb12u6
Detailed paths
-
Introduced through: golang@1.20 › gnutls28/libgnutls30@3.7.9-2+deb12u1
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 the GnuTLS library, specifically in the gnutls_pkcs11_token_init() function that handles PKCS#11 token initialization. When a token label longer than expected is processed, the function writes past the end of a fixed-size stack buffer. This programming error can cause the application using GnuTLS to crash or, in certain conditions, be exploited for code execution. As a result, systems or applications relying on GnuTLS may be vulnerable to a denial of service or local privilege escalation attacks.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u6 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-9820
- https://access.redhat.com/security/cve/CVE-2025-9820
- https://bugzilla.redhat.com/show_bug.cgi?id=2392528
- https://gitlab.com/gnutls/gnutls/-/commit/1d56f96f6ab5034d677136b9d50b5a75dff0faf5
- https://gitlab.com/gnutls/gnutls/-/issues/1732
- https://www.gnutls.org/security-new.html#GNUTLS-SA-2025-11-18
- http://www.openwall.com/lists/oss-security/2025/11/20/2
- https://access.redhat.com/errata/RHSA-2026:3477
- https://access.redhat.com/errata/RHSA-2026:4188
- https://access.redhat.com/errata/RHSA-2026:4655
- https://access.redhat.com/errata/RHSA-2026:4943
- https://access.redhat.com/errata/RHSA-2026:5585
- https://access.redhat.com/errata/RHSA-2026:5606
- https://access.redhat.com/errata/RHSA-2026:7329
- https://access.redhat.com/errata/RHSA-2026:7477
- https://access.redhat.com/errata/RHSA-2026:13812
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u4, glibc/libc-dev-bin@2.36-9+deb12u4 and others
Detailed paths
-
Introduced through: golang@1.20 › glibc/libc-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc-dev-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6-dev@2.36-9+deb12u4
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
new
- Vulnerable module: perl
- Introduced through: perl@5.36.0-7+deb12u1, perl/libperl5.36@5.36.0-7+deb12u1 and others
Detailed paths
-
Introduced through: golang@1.20 › perl@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/libperl5.36@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/perl-base@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/perl-modules-5.36@5.36.0-7+deb12u1
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.
Perl versions through 5.43.10 have a heap buffer overflow when compiling regular expressions with a repeated fixed string on 32-bit builds.
Perl_study_chunk in regcomp_study.c checked the size of the joined substring buffer in characters rather than bytes. For a quantified fixed substring with a large minimum count, the byte length mincount * l could overflow SSize_t, producing an undersized SvGROW allocation; the subsequent copy writes past the end of the buffer.
A caller that compiles an attacker-controlled regular expression on a 32-bit perl build triggers a heap buffer overflow at compile time.
Remediation
There is no fixed version for Debian:12 perl.
References
low severity
- 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: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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 "tarfile" module would still apply normalization of AREGTYPE (\x00) blocks to DIRTYPE, even while processing a multi-block member such as GNUTYPE_LONGNAME or GNUTYPE_LONGLINK. This could result in a crafted tar archive being misinterpreted by the tarfile module compared to other implementations.
Remediation
There is no fixed version for Debian:12 python3.11.
References
- https://security-tracker.debian.org/tracker/CVE-2025-13462
- https://github.com/python/cpython/commit/42d754e34c06e57ad6b8e7f92f32af679912d8ab
- https://github.com/python/cpython/commit/72dde1016493c52abe857fc4a7bf6c40138b4114
- https://github.com/python/cpython/commit/7ad3093d76a748af55bdb1d2e8aad3638163b017
- https://github.com/python/cpython/commit/9a23b753552afa28e3a2f4d8863572fc66479406
- https://github.com/python/cpython/commit/ae99fe3a33b43e303a05f012815cef60b611a9c7
- https://github.com/python/cpython/commit/d10950739a78f54d0718d88fb5a868374603c084
- https://github.com/python/cpython/issues/141707
- https://github.com/python/cpython/pull/143934
- https://mail.python.org/archives/list/security-announce@python.org/thread/EOMI5I66ZMKQ2INNFT6T7IAIKUGPZYIE/
low severity
new
- 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: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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.
xml.parsers.expat and xml.etree.ElementTree use insufficient entropy for Expat hash-flooding protection, which allows a crafted XML document to trigger hash flooding.\r\n\r\nFully mitigating this vulnerability requires both updating libexpat to 2.8.0 or later and applying this patch.
Remediation
There is no fixed version for Debian:12 python3.11.
References
- https://security-tracker.debian.org/tracker/CVE-2026-7210
- https://github.com/python/cpython/issues/149018
- https://github.com/python/cpython/pull/149023
- https://mail.python.org/archives/list/security-announce@python.org/thread/PNY5OMBDPM2FRUZTWFFPJ6LISWKV627K/
- http://www.openwall.com/lists/oss-security/2026/05/11/13
- http://www.openwall.com/lists/oss-security/2026/05/11/8
low severity
- Vulnerable module: tar
- Introduced through: tar@1.34+dfsg-1.2
Detailed paths
-
Introduced through: golang@1.20 › 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
- https://security-tracker.debian.org/tracker/CVE-2005-2541
- http://marc.info/?l=bugtraq&m=112327628230258&w=2
- https://lists.apache.org/thread.html/rc713534b10f9daeee2e0990239fa407e2118e4aa9e88a7041177497c@%3Cissues.guacamole.apache.org%3E
- https://lists.apache.org/thread.html/rc713534b10f9daeee2e0990239fa407e2118e4aa9e88a7041177497c%40%3Cissues.guacamole.apache.org%3E
low severity
new
- Vulnerable module: perl
- Introduced through: perl@5.36.0-7+deb12u1, perl/libperl5.36@5.36.0-7+deb12u1 and others
Detailed paths
-
Introduced through: golang@1.20 › perl@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/libperl5.36@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/perl-base@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/perl-modules-5.36@5.36.0-7+deb12u1
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.
Archive::Tar versions before 3.08 for Perl extract symlinks with attacker controlled targets outside the extraction directory.
_make_special_file() passes the tar header's linkname to symlink() without validating it against absolute paths or .. segments. The secure-extract mode check that guards regular file extraction does not cover the symlink target.
A subsequent open through the extracted name reads or writes the attacker chosen path.
Remediation
There is no fixed version for Debian:12 perl.
References
low severity
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2
Detailed paths
-
Introduced through: golang@1.20 › 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.
An integer overflow in the sqlite3KeyInfoFromExprList function in SQLite versions 3.39.2 through 3.41.1 allows an attacker with the ability to execute arbitrary SQL statements to cause a denial of service or disclose sensitive information from process memory via a crafted SELECT statement with a large number of expressions in the ORDER BY clause.
Remediation
There is no fixed version for Debian:12 sqlite3.
References
low severity
- 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: golang@1.20 › git@1:2.39.2-1.1
-
Introduced through: golang@1.20 › 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 source code management tool. When cloning from a server (or fetching, or pushing), informational or error messages are transported from the remote Git process to the client via the so-called "sideband channel". These messages will be prefixed with "remote:" and printed directly to the standard error output. Typically, this standard error output is connected to a terminal that understands ANSI escape sequences, which Git did not protect against. Most modern terminals support control sequences that can be used by a malicious actor to hide and misrepresent information, or to mislead the user into executing untrusted scripts. As requested on the git-security mailing list, the patches are under discussion on the public mailing list. Users are advised to update as soon as possible. Users unable to upgrade should avoid recursive clones unless they are from trusted sources.
Remediation
There is no fixed version for Debian:12 git.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u4, glibc/libc-dev-bin@2.36-9+deb12u4 and others
Detailed paths
-
Introduced through: golang@1.20 › glibc/libc-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc-dev-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6-dev@2.36-9+deb12u4
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
- https://security-tracker.debian.org/tracker/CVE-2019-1010023
- https://support.f5.com/csp/article/K11932200?utm_source=f5support&utm_medium=RSS
- https://sourceware.org/bugzilla/show_bug.cgi?id=22851
- http://www.securityfocus.com/bid/109167
- https://ubuntu.com/security/CVE-2019-1010023
- https://support.f5.com/csp/article/K11932200?utm_source=f5support&%3Butm_medium=RSS
low severity
- Vulnerable module: perl
- Introduced through: perl@5.36.0-7+deb12u1, perl/libperl5.36@5.36.0-7+deb12u1 and others
Detailed paths
-
Introduced through: golang@1.20 › perl@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/libperl5.36@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/perl-base@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/perl-modules-5.36@5.36.0-7+deb12u1
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
- https://security-tracker.debian.org/tracker/CVE-2023-31486
- https://security.netapp.com/advisory/ntap-20241129-0011/
- http://www.openwall.com/lists/oss-security/2023/04/29/1
- http://www.openwall.com/lists/oss-security/2023/05/03/3
- http://www.openwall.com/lists/oss-security/2023/05/03/5
- http://www.openwall.com/lists/oss-security/2023/05/07/2
- https://blog.hackeriet.no/perl-http-tiny-insecure-tls-default-affects-cpan-modules/
- https://github.com/chansen/p5-http-tiny/pull/153
- https://hackeriet.github.io/cpan-http-tiny-overview/
- https://www.openwall.com/lists/oss-security/2023/04/18/14
- https://www.openwall.com/lists/oss-security/2023/05/03/4
- https://www.reddit.com/r/perl/comments/111tadi/psa_httptiny_disabled_ssl_verification_by_default/
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A flaw was found in binutils. A heap-buffer-overflow vulnerability exists when processing a specially crafted XCOFF (Extended Common Object File Format) object file during linking. A local attacker could trick a user into processing this malicious file, which could lead to arbitrary code execution, allowing the attacker to run unauthorized commands, or cause a denial of service, making the system unavailable.
Remediation
There is no fixed version for Debian:12 binutils.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability classified as critical has been found in GNU Binutils up to 2.44. This affects the function debug_type_samep of the file /binutils/debug.c of the component objdump. The manipulation leads to memory corruption. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue.
Remediation
There is no fixed version for Debian:12 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-5245
- https://sourceware.org/bugzilla/attachment.cgi?id=16004
- https://sourceware.org/bugzilla/show_bug.cgi?id=32829
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=6c3458a8b7ee7d39f070c7b2350851cb2110c65a
- https://vuldb.com/?ctiid.310347
- https://vuldb.com/?id.310347
- https://vuldb.com/?submit.584635
- https://www.gnu.org/
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability was found in GNU Binutils up to 2.44. It has been rated as critical. Affected by this issue is the function elf_gc_sweep of the file bfd/elflink.c of the component ld. The manipulation leads to memory corruption. An attack has to be approached locally. The exploit has been disclosed to the public and may be used. Upgrading to version 2.45 is able to address this issue. It is recommended to upgrade the affected component.
Remediation
There is no fixed version for Debian:12 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-5244
- https://sourceware.org/bugzilla/attachment.cgi?id=16010
- https://sourceware.org/bugzilla/show_bug.cgi?id=32858
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=d1458933830456e54223d9fc61f0d9b3a19256f5
- https://vuldb.com/?ctiid.310346
- https://vuldb.com/?id.310346
- https://vuldb.com/?submit.584634
- https://www.gnu.org/
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability, which was classified as problematic, has been found in GNU Binutils 2.45. Affected by this issue is the function bfd_elf_set_group_contents of the file bfd/elf.c. The manipulation leads to out-of-bounds write. It is possible to launch the attack on the local host. The exploit has been disclosed to the public and may be used. The name of the patch is 41461010eb7c79fee7a9d5f6209accdaac66cc6b. It is recommended to apply a patch to fix this issue.
Remediation
There is no fixed version for Debian:12 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-7546
- https://sourceware.org/bugzilla/attachment.cgi?id=16118
- https://sourceware.org/bugzilla/show_bug.cgi?id=33050#c2
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=41461010eb7c79fee7a9d5f6209accdaac66cc6b
- https://vuldb.com/?ctiid.316244
- https://vuldb.com/?id.316244
- https://vuldb.com/?submit.614375
- https://www.gnu.org/
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
- https://sourceware.org/bugzilla/show_bug.cgi?id=33050
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability classified as problematic was found in GNU Binutils 2.45. Affected by this vulnerability is the function copy_section of the file binutils/objcopy.c. The manipulation leads to heap-based buffer overflow. Attacking locally is a requirement. The exploit has been disclosed to the public and may be used. The patch is named 08c3cbe5926e4d355b5cb70bbec2b1eeb40c2944. It is recommended to apply a patch to fix this issue.
Remediation
There is no fixed version for Debian:12 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-7545
- https://sourceware.org/bugzilla/attachment.cgi?id=16117
- https://sourceware.org/bugzilla/show_bug.cgi?id=33049
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=08c3cbe5926e4d355b5cb70bbec2b1eeb40c2944
- https://vuldb.com/?ctiid.316243
- https://vuldb.com/?id.316243
- https://vuldb.com/?submit.614355
- https://www.gnu.org/
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
- https://sourceware.org/bugzilla/show_bug.cgi?id=33049#c1
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A flaw has been found in GNU Binutils 2.45. Impacted is the function _bfd_elf_parse_eh_frame of the file bfd/elf-eh-frame.c of the component Linker. Executing manipulation can lead to heap-based buffer overflow. The attack is restricted to local execution. The exploit has been published and may be used. This patch is called ea1a0737c7692737a644af0486b71e4a392cbca8. A patch should be applied to remediate this issue. The code maintainer replied with "[f]ixed for 2.46".
Remediation
There is no fixed version for Debian:12 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-11082
- https://sourceware.org/bugzilla/attachment.cgi?id=16358
- https://sourceware.org/bugzilla/show_bug.cgi?id=33464
- https://sourceware.org/bugzilla/show_bug.cgi?id=33464#c2
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=ea1a0737c7692737a644af0486b71e4a392cbca8
- https://vuldb.com/?ctiid.326123
- https://vuldb.com/?id.326123
- https://vuldb.com/?submit.661276
- https://www.gnu.org/
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability has been found in GNU Binutils 2.45. The affected element is the function elf_swap_shdr in the library bfd/elfcode.h of the component Linker. The manipulation leads to heap-based buffer overflow. The attack must be carried out locally. The exploit has been disclosed to the public and may be used. The identifier of the patch is 9ca499644a21ceb3f946d1c179c38a83be084490. To fix this issue, it is recommended to deploy a patch. The code maintainer replied with "[f]ixed for 2.46".
Remediation
There is no fixed version for Debian:12 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-11083
- https://sourceware.org/bugzilla/attachment.cgi?id=16353
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=9ca499644a21ceb3f946d1c179c38a83be084490
- https://vuldb.com/?ctiid.326124
- https://vuldb.com/?id.326124
- https://vuldb.com/?submit.661277
- https://www.gnu.org/
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://sourceware.org/bugzilla/show_bug.cgi?id=33457
- https://sourceware.org/bugzilla/show_bug.cgi?id=33457#c1
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1
Detailed paths
-
Introduced through: golang@1.20 › 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.
In libexpat before 2.7.4, the doContent function does not properly determine the buffer size bufSize because there is no integer overflow check for tag buffer reallocation.
Remediation
There is no fixed version for Debian:12 expat.
References
low severity
- Vulnerable module: ncurses/libncursesw6
- Introduced through: ncurses/libncursesw6@6.4-4, ncurses/libtinfo6@6.4-4 and others
Detailed paths
-
Introduced through: golang@1.20 › ncurses/libncursesw6@6.4-4
-
Introduced through: golang@1.20 › ncurses/libtinfo6@6.4-4
-
Introduced through: golang@1.20 › ncurses/ncurses-base@6.4-4
-
Introduced through: golang@1.20 › 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.
The infocmp command-line tool in ncurses before 6.5-20251213 has a stack-based buffer overflow in analyze_string in progs/infocmp.c.
Remediation
There is no fixed version for Debian:12 ncurses.
References
- https://security-tracker.debian.org/tracker/CVE-2025-69720
- https://github.com/Cao-Wuhui/CVE-2025-69720
- https://invisible-island.net/archives/ncurses/6.5/
- https://invisible-island.net/ncurses/
- https://marc.info/?l=ncurses-bug&m=176539968328570&w=2
- https://marc.info/?l=ncurses-bug&m=176540731801330&w=2
- https://marc.info/?l=ncurses-bug&m=176545557728083&w=2
- https://cert-portal.siemens.com/productcert/html/ssa-253495.html
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
An issue was discovered in function d_print_comp_inner in file cp-demangle.c in BinUtils 2.26 allows attackers to cause a denial of service via crafted PE file.
Remediation
There is no fixed version for Debian:12 binutils.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
An issue was discovered in function d_abi_tags in file cp-demangle.c in BinUtils 2.26 allows attackers to cause a denial of service via crafted PE file.
Remediation
There is no fixed version for Debian:12 binutils.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
GNU Binutils thru 2.46 readelf contains a null pointer dereference vulnerability when processing a crafted ELF binary with malformed header fields. During relocation processing, an invalid or null section pointer may be passed into display_relocations(), resulting in a segmentation fault (SIGSEGV) and abrupt termination. No evidence of memory corruption beyond the null pointer dereference, nor any possibility of code execution, was observed.
Remediation
There is no fixed version for Debian:12 binutils.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
GNU Binutils thru 2.46 readelf contains a double free vulnerability when processing a crafted ELF binary with malformed relocation data. During GOT relocation handling, dump_relocations may return early without initializing the all_relocations array. As a result, process_got_section_contents() may pass an uninitialized r_symbol pointer to free(), leading to a double free and terminating the program with SIGABRT. No evidence of exploitable memory corruption or code execution was observed; the impact is limited to denial of service. NOTE: this is disputed by third parties because the observed behavior occurred only in pre-release code and did not affect any tagged version.
Remediation
There is no fixed version for Debian:12 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-69650
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=ea4bc025abdba85a90e26e13f551c16a44bfa921
- https://sourceware.org/bugzilla/show_bug.cgi?id=33700
- https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=81e90cf63a10ad11772c2437c8f2a88f1a00c739
- https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=ea4bc025abdba85a90e26e13f551c16a44bfa92
- https://sourceware.org/bugzilla/show_bug.cgi?id=33698
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability, which was classified as problematic, was found in GNU Binutils up to 2.43. This affects the function disassemble_bytes of the file binutils/objdump.c. The manipulation of the argument buf leads to stack-based buffer overflow. It is possible to initiate the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. Upgrading to version 2.44 is able to address this issue. The identifier of the patch is baac6c221e9d69335bf41366a1c7d87d8ab2f893. It is recommended to upgrade the affected component.
Remediation
There is no fixed version for Debian:12 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-0840
- https://sourceware.org/bugzilla/attachment.cgi?id=15882
- https://sourceware.org/bugzilla/show_bug.cgi?id=32560
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=baac6c221e9d69335bf41366a1c7d87d8ab2f893
- https://vuldb.com/?ctiid.293997
- https://vuldb.com/?id.293997
- https://vuldb.com/?submit.485255
- https://www.gnu.org/
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability was found in GNU Binutils 2.43. It has been rated as critical. Affected by this issue is the function bfd_putl64 of the file bfd/libbfd.c of the component ld. The manipulation leads to memory corruption. The attack may be launched remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. Upgrading to version 2.44 is able to address this issue. It is recommended to upgrade the affected component. The code maintainer explains, that "[t]his bug has been fixed at some point between the 2.43 and 2.44 releases".
Remediation
There is no fixed version for Debian:12 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-1179
- https://sourceware.org/bugzilla/attachment.cgi?id=15915
- https://sourceware.org/bugzilla/show_bug.cgi?id=32640
- https://sourceware.org/bugzilla/show_bug.cgi?id=32640#c1
- https://vuldb.com/?ctiid.295082
- https://vuldb.com/?id.295082
- https://vuldb.com/?submit.495376
- https://www.gnu.org/
low severity
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10+deb12u5, curl/libcurl3-gnutls@7.88.1-10+deb12u5 and others
Detailed paths
-
Introduced through: golang@1.20 › curl@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl3-gnutls@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl4@7.88.1-10+deb12u5
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.
Using libcurl, when a custom Host: header is first set for an HTTP request
and a second request is subsequently done using the same easy handle but
without the custom Host: header set, the second request would use stale
information and pass on cookies meant for the first host in the second
request. Leak them.
Remediation
There is no fixed version for Debian:12 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10+deb12u5, curl/libcurl3-gnutls@7.88.1-10+deb12u5 and others
Detailed paths
-
Introduced through: golang@1.20 › curl@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl3-gnutls@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl4@7.88.1-10+deb12u5
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 might in some circumstances reuse the wrong connection for SMB(S) transfers.
libcurl features a pool of recent connections so that subsequent requests can reuse an existing connection to avoid overhead.
When reusing a connection a range of criteria must be met. Due to a logical error in the code, a network transfer operation that was requested by an application could wrongfully reuse an existing SMB connection to the same server that was using a different 'share' than the new subsequent transfer should.
This could in unlucky situations lead to the download of the wrong file or the upload of a file to the wrong place. When this happens, the same credentials are used and the server name is the same.
Remediation
There is no fixed version for Debian:12 curl.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1
Detailed paths
-
Introduced through: golang@1.20 › 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
- https://security-tracker.debian.org/tracker/CVE-2024-28757
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/FPLC6WDSRDUYS7F7JWAOVOHFNOUQ43DD/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VK2O34GH43NTHBZBN7G5Y6YKJKPUCTBE/
- http://www.openwall.com/lists/oss-security/2024/03/15/1
- https://github.com/libexpat/libexpat/issues/839
- https://github.com/libexpat/libexpat/pull/842
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FPLC6WDSRDUYS7F7JWAOVOHFNOUQ43DD/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LKJ7V5F6LJCEQJXDBWGT27J7NAP3E3N7/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VK2O34GH43NTHBZBN7G5Y6YKJKPUCTBE/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LKJ7V5F6LJCEQJXDBWGT27J7NAP3E3N7/
- https://security.netapp.com/advisory/ntap-20240322-0001/
low severity
- 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: golang@1.20 › git@1:2.39.2-1.1
-
Introduced through: golang@1.20 › 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. Note: This has been disputed by multiple 3rd parties who believe this is an intended feature of the git binary and does not pose a security risk.
Remediation
There is no fixed version for Debian:12 git.
References
- https://security-tracker.debian.org/tracker/CVE-2022-24975
- https://lore.kernel.org/git/xmqq4k14qe9g.fsf%40gitster.g/
- https://github.com/git/git/blob/2dc94da3744bfbbf145eca587a0f5ff480cc5867/Documentation/git-clone.txt#L185-L191
- https://www.aquasec.com/blog/undetected-hard-code-secrets-expose-corporations/
- https://wwws.nightwatchcybersecurity.com/2022/02/11/gitbleed/
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u4, glibc/libc-dev-bin@2.36-9+deb12u4 and others
Detailed paths
-
Introduced through: golang@1.20 › glibc/libc-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc-dev-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6-dev@2.36-9+deb12u4
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
- https://security-tracker.debian.org/tracker/CVE-2018-20796
- https://support.f5.com/csp/article/K26346590?utm_source=f5support&utm_medium=RSS
- https://debbugs.gnu.org/cgi/bugreport.cgi?bug=34141
- https://lists.gnu.org/archive/html/bug-gnulib/2019-01/msg00108.html
- https://security.netapp.com/advisory/ntap-20190315-0002/
- http://www.securityfocus.com/bid/107160
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2018-20796
- https://support.f5.com/csp/article/K26346590?utm_source=f5support&%3Butm_medium=RSS
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u4, glibc/libc-dev-bin@2.36-9+deb12u4 and others
Detailed paths
-
Introduced through: golang@1.20 › glibc/libc-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc-dev-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6-dev@2.36-9+deb12u4
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
- https://security-tracker.debian.org/tracker/CVE-2019-9192
- https://support.f5.com/csp/article/K26346590?utm_source=f5support&utm_medium=RSS
- https://sourceware.org/bugzilla/show_bug.cgi?id=24269
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2019-9192
- https://support.f5.com/csp/article/K26346590?utm_source=f5support&%3Butm_medium=RSS
low severity
- Vulnerable module: jansson/libjansson4
- Introduced through: jansson/libjansson4@2.14-2
Detailed paths
-
Introduced through: golang@1.20 › jansson/libjansson4@2.14-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream jansson package and not the jansson package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
An issue was discovered in Jansson through 2.13.1. Due to a parsing error in json_loads, there's an out-of-bounds read-access bug. NOTE: the vendor reports that this only occurs when a programmer fails to follow the API specification
Remediation
There is no fixed version for Debian:12 jansson.
References
low severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u1, krb5/libk5crypto3@1.20.1-2+deb12u1 and others
Detailed paths
-
Introduced through: golang@1.20 › krb5/libgssapi-krb5-2@1.20.1-2+deb12u1
-
Introduced through: golang@1.20 › krb5/libk5crypto3@1.20.1-2+deb12u1
-
Introduced through: golang@1.20 › krb5/libkrb5-3@1.20.1-2+deb12u1
-
Introduced through: golang@1.20 › krb5/libkrb5support0@1.20.1-2+deb12u1
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
- https://security-tracker.debian.org/tracker/CVE-2018-5709
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5709
- https://github.com/poojamnit/Kerberos-V5-1.16-Vulnerabilities/tree/master/Integer%20Overflow
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772@%3Cdev.mina.apache.org%3E
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2018-5709
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772%40%3Cdev.mina.apache.org%3E
low severity
- Vulnerable module: libgcrypt20
- Introduced through: libgcrypt20@1.10.1-3
Detailed paths
-
Introduced through: golang@1.20 › 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
- https://security-tracker.debian.org/tracker/CVE-2018-6829
- https://github.com/weikengchen/attack-on-libgcrypt-elgamal
- https://github.com/weikengchen/attack-on-libgcrypt-elgamal/wiki
- https://lists.gnupg.org/pipermail/gcrypt-devel/2018-February/004394.html
- https://www.oracle.com/security-alerts/cpujan2020.html
low severity
- Vulnerable module: openldap/libldap-2.5-0
- Introduced through: openldap/libldap-2.5-0@2.5.13+dfsg-5
Detailed paths
-
Introduced through: golang@1.20 › 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
- https://security-tracker.debian.org/tracker/CVE-2015-3276
- http://www.oracle.com/technetwork/topics/security/linuxbulletinoct2015-2719645.html
- https://bugzilla.redhat.com/show_bug.cgi?id=1238322
- http://rhn.redhat.com/errata/RHSA-2015-2131.html
- http://www.securitytracker.com/id/1034221
- https://access.redhat.com/errata/RHSA-2015:2131
- https://access.redhat.com/security/cve/CVE-2015-3276
low severity
- Vulnerable module: openldap/libldap-2.5-0
- Introduced through: openldap/libldap-2.5-0@2.5.13+dfsg-5
Detailed paths
-
Introduced through: golang@1.20 › 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
- https://security-tracker.debian.org/tracker/CVE-2023-2953
- http://seclists.org/fulldisclosure/2023/Jul/47
- http://seclists.org/fulldisclosure/2023/Jul/48
- http://seclists.org/fulldisclosure/2023/Jul/52
- https://access.redhat.com/security/cve/CVE-2023-2953
- https://bugs.openldap.org/show_bug.cgi?id=9904
- https://security.netapp.com/advisory/ntap-20230703-0005/
- https://support.apple.com/kb/HT213843
- https://support.apple.com/kb/HT213844
- https://support.apple.com/kb/HT213845
low severity
- Vulnerable module: openldap/libldap-2.5-0
- Introduced through: openldap/libldap-2.5-0@2.5.13+dfsg-5
Detailed paths
-
Introduced through: golang@1.20 › 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
- https://security-tracker.debian.org/tracker/CVE-2017-17740
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17740
- http://www.openldap.org/its/index.cgi/Incoming?id=8759
- http://lists.opensuse.org/opensuse-security-announce/2019-09/msg00053.html
- http://lists.opensuse.org/opensuse-security-announce/2019-09/msg00058.html
- https://kc.mcafee.com/corporate/index?page=content&id=SB10365
- https://www.oracle.com/security-alerts/cpuapr2022.html
low severity
new
- Vulnerable module: perl
- Introduced through: perl@5.36.0-7+deb12u1, perl/libperl5.36@5.36.0-7+deb12u1 and others
Detailed paths
-
Introduced through: golang@1.20 › perl@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/libperl5.36@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/perl-base@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/perl-modules-5.36@5.36.0-7+deb12u1
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.
Archive::Tar versions before 3.08 for Perl extract hardlinks to attacker controlled paths outside the extraction directory.
_make_special_file() passes the tar header's linkname to link() without validating it against absolute paths or .. segments, creating a hardlink that shares the victim file's inode.
A subsequent write through the extracted name modifies the victim file, and the post-extraction chmod, chown, and utime block in _extract_file() (guarded only against symlinks via -l) applies the tar header's mode, owner, and timestamps to the shared inode during extraction alone.
Remediation
There is no fixed version for Debian:12 perl.
References
low severity
new
- Vulnerable module: perl
- Introduced through: perl@5.36.0-7+deb12u1, perl/libperl5.36@5.36.0-7+deb12u1 and others
Detailed paths
-
Introduced through: golang@1.20 › perl@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/libperl5.36@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/perl-base@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/perl-modules-5.36@5.36.0-7+deb12u1
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.
Archive::Tar versions before 3.10 for Perl allow memory exhaustion via attacker controlled entry size field in tar header.
_read_tar() reads each entry's payload with $handle->read($$data, $block), where $block is derived from the entry's 12-byte size field in the tar header with no upper bound on that value.
A crafted header declaring a multi-gigabyte size causes Perl to allocate a scalar of that size.
Remediation
There is no fixed version for Debian:12 perl.
References
low severity
- 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: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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.
Python-Markdown version 3.8 contain a vulnerability where malformed HTML-like sequences can cause html.parser.HTMLParser to raise an unhandled AssertionError during Markdown parsing. Because Python-Markdown does not catch this exception, any application that processes attacker-controlled Markdown may crash. This enables remote, unauthenticated Denial of Service in web applications, documentation systems, CI/CD pipelines, and any service that renders untrusted Markdown. The issue was acknowledged by the vendor and fixed in version 3.8.1. This issue causes a remote Denial of Service in any application parsing untrusted Markdown, and can lead to Information Disclosure through uncaught exceptions.
Remediation
There is no fixed version for Debian:12 python3.11.
References
low severity
- 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: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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 fix for CVE-2026-0672, which rejected control characters in http.cookies.Morsel, was incomplete. The Morsel.update(), |= operator, and unpickling paths were not patched, allowing control characters to bypass input validation. Additionally, BaseCookie.js_output() lacked the output validation applied to BaseCookie.output().
Remediation
There is no fixed version for Debian:12 python3.11.
References
- https://security-tracker.debian.org/tracker/CVE-2026-3644
- https://github.com/python/cpython/commit/57e88c1cf95e1481b94ae57abe1010469d47a6b4
- https://github.com/python/cpython/commit/62ceb396fcbe69da1ded3702de586f4072b590dd
- https://github.com/python/cpython/commit/d16ecc6c3626f0e2cc8f08c309c83934e8a979dd
- https://github.com/python/cpython/issues/145599
- https://github.com/python/cpython/pull/145600
- https://mail.python.org/archives/list/security-announce@python.org/thread/H6CADMBCDRFGWCMOXWUIHFJNV43GABJ7/
low severity
- 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: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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.
When an Expat parser with a registered ElementDeclHandler parses an inline document type definition containing a deeply nested content model a C stack overflow occurs.
Remediation
There is no fixed version for Debian:12 python3.11.
References
- https://security-tracker.debian.org/tracker/CVE-2026-4224
- https://github.com/python/cpython/commit/196edfb06a7458377d4d0f4b3cd41724c1f3bd4a
- https://github.com/python/cpython/commit/642865ddf4b232da1f3b1f7abcfa3254c4bfe785
- https://github.com/python/cpython/commit/af856a7177326ac25d9f66cc6dd28b554d914fee
- https://github.com/python/cpython/commit/e0a8a6da90597a924b300debe045cdb4628ee1f3
- https://github.com/python/cpython/commit/eb0e8be3a7e11b87d198a2c3af1ed0eccf532768
- https://github.com/python/cpython/issues/145986
- https://github.com/python/cpython/pull/145987
- https://mail.python.org/archives/list/security-announce@python.org/thread/5M7CGUW3XBRY7II4DK43KF7NQQ3TPZ6R/
- http://www.openwall.com/lists/oss-security/2026/03/16/4
low severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2+deb12u2
Detailed paths
-
Introduced through: golang@1.20 › openssh/openssh-client@1:9.2p1-2+deb12u2
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
- https://security-tracker.debian.org/tracker/CVE-2020-15778
- https://security.netapp.com/advisory/ntap-20200731-0007/
- https://github.com/cpandya2909/CVE-2020-15778/
- https://news.ycombinator.com/item?id=25005567
- https://www.openssh.com/security.html
- https://github.com/cpandya2909/CVE-2020-15778#example
- https://access.redhat.com/errata/RHSA-2024:3166
- https://security.gentoo.org/glsa/202212-06
- https://github.com/Neko-chanQwQ/CVE-2020-15778-Exploit
low severity
- Vulnerable module: libssh2/libssh2-1
- Introduced through: libssh2/libssh2-1@1.10.0-3+b1
Detailed paths
-
Introduced through: golang@1.20 › libssh2/libssh2-1@1.10.0-3+b1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libssh2 package and not the libssh2 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A security vulnerability has been detected in libssh2 up to 1.11.1. The impacted element is the function userauth_password of the file src/userauth.c. Such manipulation of the argument username_len/password_len leads to integer overflow. The attack may be launched remotely. The name of the patch is 256d04b60d80bf1190e96b0ad1e91b2174d744b1. A patch should be applied to remediate this issue.
Remediation
There is no fixed version for Debian:12 libssh2.
References
- https://security-tracker.debian.org/tracker/CVE-2026-7598
- https://github.com/libssh2/libssh2/
- https://github.com/libssh2/libssh2/commit/256d04b60d80bf1190e96b0ad1e91b2174d744b1
- https://github.com/libssh2/libssh2/pull/1858
- https://vuldb.com/vuln/360555
- https://vuldb.com/vuln/360555/cti
- https://vuldb.com/submit/805564
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A flaw was found in GNU Binutils. This heap-based buffer overflow vulnerability, specifically an out-of-bounds read in the bfd linker, allows an attacker to gain access to sensitive information. By convincing a user to process a specially crafted XCOFF object file, an attacker can trigger this flaw, potentially leading to information disclosure or an application level denial of service.
Remediation
There is no fixed version for Debian:12 binutils.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A flaw was found in GNU Binutils. This vulnerability, a heap-based buffer overflow, specifically an out-of-bounds read, exists in the bfd linker component. An attacker could exploit this by convincing a user to process a specially crafted malicious XCOFF object file. Successful exploitation may lead to the disclosure of sensitive information or cause the application to crash, resulting in an application level denial of service.
Remediation
There is no fixed version for Debian:12 binutils.
References
low severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2+deb12u2
Detailed paths
-
Introduced through: golang@1.20 › openssh/openssh-client@1:9.2p1-2+deb12u2
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
- https://security-tracker.debian.org/tracker/CVE-2019-6110
- https://www.exploit-db.com/exploits/46193/
- https://security.gentoo.org/glsa/201903-16
- https://cvsweb.openbsd.org/src/usr.bin/ssh/progressmeter.c
- https://cvsweb.openbsd.org/src/usr.bin/ssh/scp.c
- https://sintonen.fi/advisories/scp-client-multiple-vulnerabilities.txt
- https://security.netapp.com/advisory/ntap-20190213-0001/
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2019-6110
- https://cert-portal.siemens.com/productcert/pdf/ssa-412672.pdf
- https://www.exploit-db.com/exploits/46516
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A heap-based buffer over-read exists in the function d_expression_1 in cp-demangle.c in GNU libiberty, as distributed in GNU Binutils 2.31.1. A crafted input can cause segmentation faults, leading to denial-of-service, as demonstrated by c++filt.
Remediation
There is no fixed version for Debian:12 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2018-20712
- https://support.f5.com/csp/article/K38336243
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20712
- https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88629
- https://sourceware.org/bugzilla/show_bug.cgi?id=24043
- http://www.securityfocus.com/bid/106563
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2018-20712
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A potential heap based buffer overflow was found in _bfd_elf_slurp_version_tables() in bfd/elf.c. This may lead to loss of availability.
Remediation
There is no fixed version for Debian:12 binutils.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
An issue was discovered in GNU libiberty, as distributed in GNU Binutils 2.36. It is a stack-overflow issue in demangle_type in rust-demangle.c.
Remediation
There is no fixed version for Debian:12 binutils.
References
low severity
- Vulnerable module: coreutils
- Introduced through: coreutils@9.1-1
Detailed paths
-
Introduced through: golang@1.20 › 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
- https://security-tracker.debian.org/tracker/CVE-2016-2781
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772@%3Cdev.mina.apache.org%3E
- http://www.openwall.com/lists/oss-security/2016/02/28/2
- http://www.openwall.com/lists/oss-security/2016/02/28/3
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2016-2781
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772%40%3Cdev.mina.apache.org%3E
low severity
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10+deb12u5, curl/libcurl3-gnutls@7.88.1-10+deb12u5 and others
Detailed paths
-
Introduced through: golang@1.20 › curl@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl3-gnutls@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl4@7.88.1-10+deb12u5
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 might in some circumstances reuse the wrong connection when asked to do an authenticated HTTP(S) request after a Negotiate-authenticated one, when both use the same host.
libcurl features a pool of recent connections so that subsequent requests can reuse an existing connection to avoid overhead.
When reusing a connection a range of criteria must be met. Due to a logical error in the code, a request that was issued by an application could wrongfully reuse an existing connection to the same server that was authenticated using different credentials.
An application that first uses Negotiate authentication to a server with
user1:password1 and then does another operation to the same server asking
for any authentication method but for user2:password2 (while the previous
connection is still alive) - the second request gets confused and wrongly
reuses the same connection and sends the new request over that connection
thinking it uses a mix of user1's and user2's credentials when it is in fact
still using the connection authenticated for user1...
Remediation
There is no fixed version for Debian:12 curl.
References
low severity
- Vulnerable module: ncurses/libncursesw6
- Introduced through: ncurses/libncursesw6@6.4-4, ncurses/libtinfo6@6.4-4 and others
Detailed paths
-
Introduced through: golang@1.20 › ncurses/libncursesw6@6.4-4
-
Introduced through: golang@1.20 › ncurses/libtinfo6@6.4-4
-
Introduced through: golang@1.20 › ncurses/ncurses-base@6.4-4
-
Introduced through: golang@1.20 › 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
- https://security-tracker.debian.org/tracker/CVE-2023-50495
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LU4MYMKFEZQ5VSCVLRIZGDQOUW3T44GT/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LU4MYMKFEZQ5VSCVLRIZGDQOUW3T44GT/
- https://lists.gnu.org/archive/html/bug-ncurses/2023-04/msg00020.html
- https://lists.gnu.org/archive/html/bug-ncurses/2023-04/msg00029.html
- https://security.netapp.com/advisory/ntap-20240119-0008/
low severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2+deb12u2
Detailed paths
-
Introduced through: golang@1.20 › openssh/openssh-client@1:9.2p1-2+deb12u2
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
- 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: golang@1.20 › shadow/login@1:4.13+dfsg1-1+b1
-
Introduced through: golang@1.20 › 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
- https://security-tracker.debian.org/tracker/CVE-2007-5686
- http://www.securityfocus.com/archive/1/482129/100/100/threaded
- http://www.securityfocus.com/archive/1/482857/100/0/threaded
- https://issues.rpath.com/browse/RPL-1825
- http://secunia.com/advisories/27215
- http://www.securityfocus.com/bid/26048
- http://www.vupen.com/english/advisories/2007/3474
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A flaw was found in the GNU Binutils BFD library, a widely used component for handling binary files such as object files and executables. The issue occurs when processing specially crafted XCOFF object files, where a relocation type value is not properly validated before being used. This can cause the program to read memory outside of intended bounds. As a result, affected tools may crash or expose unintended memory contents, leading to denial-of-service or limited information disclosure risks.
Remediation
There is no fixed version for Debian:12 binutils.
References
low severity
- 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: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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.
http.cookies.Morsel.js_output() returns an inline <script> snippet and only escapes " for JavaScript string context. It does not neutralize the HTML parser-sensitive sequence </script> inside the generated script element. Mitigation base64-encodes the cookie value to disallow escaping using cookie value.
Remediation
There is no fixed version for Debian:12 python3.11.
References
- https://security-tracker.debian.org/tracker/CVE-2026-6019
- https://github.com/python/cpython/commit/3c59b8b53fc75c7f9578d16fb8201ceb43e8f76c
- https://github.com/python/cpython/commit/76b3923d688c0efc580658476c5f525ec8735104
- https://github.com/python/cpython/commit/f795e042043dfe26c42e1971d4502c1cdc4c65b8
- https://github.com/python/cpython/issues/90309
- https://github.com/python/cpython/pull/148848
- https://mail.python.org/archives/list/security-announce@python.org/thread/IVNWGV2BBNC3RHQAFS22UP4DY56SAXX3/
low severity
- 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: golang@1.20 › util-linux/bsdutils@1:2.38.1-5+b1
-
Introduced through: golang@1.20 › util-linux/libblkid1@2.38.1-5+b1
-
Introduced through: golang@1.20 › util-linux/libmount1@2.38.1-5+b1
-
Introduced through: golang@1.20 › util-linux/libsmartcols1@2.38.1-5+b1
-
Introduced through: golang@1.20 › util-linux/libuuid1@2.38.1-5+b1
-
Introduced through: golang@1.20 › util-linux/mount@2.38.1-5+b1
-
Introduced through: golang@1.20 › util-linux/util-linux@2.38.1-5+b1
-
Introduced through: golang@1.20 › 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 util-linux. This vulnerability allows a heap buffer overread when processing 256-byte usernames, specifically within the setpwnam() function, affecting SUID (Set User ID) login-utils utilities writing to the password database.
Remediation
There is no fixed version for Debian:12 util-linux.
References
- https://security-tracker.debian.org/tracker/CVE-2025-14104
- https://access.redhat.com/security/cve/CVE-2025-14104
- https://bugzilla.redhat.com/show_bug.cgi?id=2419369
- https://access.redhat.com/errata/RHSA-2026:1696
- https://access.redhat.com/errata/RHSA-2026:1852
- https://access.redhat.com/errata/RHSA-2026:1913
- https://access.redhat.com/errata/RHSA-2026:2485
- https://access.redhat.com/errata/RHSA-2026:2563
- https://access.redhat.com/errata/RHSA-2026:2737
- https://access.redhat.com/errata/RHSA-2026:2800
- https://access.redhat.com/errata/RHSA-2026:3406
- https://access.redhat.com/errata/RHSA-2026:4943
- https://access.redhat.com/errata/RHSA-2026:7180
low severity
- Vulnerable module: wget/wget
- Introduced through: wget/wget@1.21.3-1+b2
Detailed paths
-
Introduced through: golang@1.20 › 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
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability classified as problematic was found in GNU Binutils 2.43/2.44. Affected by this vulnerability is the function bfd_set_format of the file format.c. The manipulation leads to memory corruption. The attack can be launched remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. Upgrading to version 2.45 is able to address this issue. The identifier of the patch is 8d97c1a53f3dc9fd8e1ccdb039b8a33d50133150. It is recommended to upgrade the affected component.
Remediation
There is no fixed version for Debian:12 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-1153
- https://sourceware.org/bugzilla/show_bug.cgi?id=32603
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=8d97c1a53f3dc9fd8e1ccdb039b8a33d50133150
- https://vuldb.com/?ctiid.295057
- https://vuldb.com/?id.295057
- https://vuldb.com/?submit.489991
- https://www.gnu.org/
- https://security.netapp.com/advisory/ntap-20250404-0005/
low severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2+deb12u2
Detailed paths
-
Introduced through: golang@1.20 › openssh/openssh-client@1:9.2p1-2+deb12u2
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
- https://security-tracker.debian.org/tracker/CVE-2020-14145
- https://security.netapp.com/advisory/ntap-20200709-0004/
- https://security.gentoo.org/glsa/202105-35
- https://anongit.mindrot.org/openssh.git/commit/?id=b3855ff053f5078ec3d3c653cdaedefaa5fc362d
- https://docs.ssh-mitm.at/CVE-2020-14145.html
- https://github.com/openssh/openssh-portable/compare/V_8_3_P1...V_8_4_P1
- https://github.com/ssh-mitm/ssh-mitm/blob/master/ssh_proxy_server/plugins/session/cve202014145.py
- https://www.fzi.de/en/news/news/detail-en/artikel/fsa-2020-2-ausnutzung-eines-informationslecks-fuer-gezielte-mitm-angriffe-auf-ssh-clients/
- http://www.openwall.com/lists/oss-security/2020/12/02/1
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability was found in GNU Binutils 2.43. It has been declared as problematic. Affected by this vulnerability is the function bfd_putl64 of the file libbfd.c of the component ld. The manipulation leads to memory corruption. The attack can be launched remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The identifier of the patch is 75086e9de1707281172cc77f178e7949a4414ed0. It is recommended to apply a patch to fix this issue.
Remediation
There is no fixed version for Debian:12 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-1178
- https://sourceware.org/bugzilla/attachment.cgi?id=15914
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=75086e9de1707281172cc77f178e7949a4414ed0
- https://vuldb.com/?ctiid.295081
- https://vuldb.com/?id.295081
- https://vuldb.com/?submit.495369
- https://www.gnu.org/
- https://security.netapp.com/advisory/ntap-20250411-0008/
- https://sourceware.org/bugzilla/show_bug.cgi?id=32638
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
The C++ symbol demangler routine in cplus-dem.c in libiberty, as distributed in GNU Binutils 2.29, allows remote attackers to cause a denial of service (excessive memory allocation and application crash) via a crafted file, as demonstrated by a call from the Binary File Descriptor (BFD) library (aka libbfd).
Remediation
There is no fixed version for Debian:12 binutils.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
GNU Binutils thru 2.46 readelf contains a vulnerability that leads to an invalid pointer free when processing a crafted ELF binary with malformed relocation or symbol data. If dump_relocations returns early due to parsing errors, the internal all_relocations array may remain partially uninitialized. Later, process_got_section_contents() may attempt to free an invalid r_symbol pointer, triggering memory corruption checks in glibc and causing the program to terminate with SIGABRT. No evidence of further memory corruption or code execution was observed; the impact is limited to denial of service. NOTE: this is disputed by third parties because the observed behavior occurred only in pre-release code and did not affect any tagged version.
Remediation
There is no fixed version for Debian:12 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-69651
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=ea4bc025abdba85a90e26e13f551c16a44bfa921
- https://sourceware.org/bugzilla/show_bug.cgi?id=33698
- https://sourceware.org/bugzilla/show_bug.cgi?id=33700
- https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=81e90cf63a10ad11772c2437c8f2a88f1a00c739
- https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=ea4bc025abdba85a90e26e13f551c16a44bfa92
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability has been found in GNU Binutils 2.43/2.44 and classified as problematic. Affected by this vulnerability is the function display_info of the file binutils/bucomm.c of the component objdump. The manipulation leads to memory leak. An attack has to be approached locally. The exploit has been disclosed to the public and may be used. The patch is named ba6ad3a18cb26b79e0e3b84c39f707535bbc344d. It is recommended to apply a patch to fix this issue.
Remediation
There is no fixed version for Debian:12 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-3198
- https://sourceware.org/bugzilla/show_bug.cgi?id=32716#c0
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=ba6ad3a18cb26b79e0e3b84c39f707535bbc344d
- https://vuldb.com/?ctiid.303151
- https://vuldb.com/?id.303151
- https://www.gnu.org/
- https://vuldb.com/?submit.545773
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
- https://sourceware.org/bugzilla/show_bug.cgi?id=32716
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability has been found in GNU Binutils 2.44 and classified as problematic. This vulnerability affects the function bfd_elf_get_str_section of the file bfd/elf.c of the component BFD Library. The manipulation leads to null pointer dereference. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used. The name of the patch is db856d41004301b3a56438efd957ef5cabb91530. It is recommended to apply a patch to fix this issue.
Remediation
There is no fixed version for Debian:12 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-8224
- https://sourceware.org/bugzilla/attachment.cgi?id=15680
- https://sourceware.org/bugzilla/show_bug.cgi?id=32109
- https://sourceware.org/bugzilla/show_bug.cgi?id=32109#c2
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=db856d41004301b3a56438efd957ef5cabb91530
- https://vuldb.com/?ctiid.317812
- https://vuldb.com/?id.317812
- https://vuldb.com/?submit.621878
- https://www.gnu.org/
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability was detected in GNU Binutils 2.45. This issue affects the function dump_dwarf_section of the file binutils/objdump.c. Performing manipulation results in out-of-bounds read. The attack is only possible with local access. The exploit is now public and may be used. The patch is named f87a66db645caf8cc0e6fc87b0c28c78a38af59b. It is suggested to install a patch to address this issue.
Remediation
There is no fixed version for Debian:12 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-11081
- https://github.com/user-attachments/files/20623354/hdf5_crash_3.txt
- https://sourceware.org/bugzilla/show_bug.cgi?id=33406
- https://sourceware.org/bugzilla/show_bug.cgi?id=33406#c2
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=f87a66db645caf8cc0e6fc87b0c28c78a38af59b
- https://vuldb.com/?ctiid.326122
- https://vuldb.com/?id.326122
- https://vuldb.com/?submit.661275
- https://www.gnu.org/
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability was determined in GNU Binutils 2.45. The affected element is the function elf_x86_64_relocate_section of the file elf64-x86-64.c of the component Linker. This manipulation causes heap-based buffer overflow. The attack can only be executed locally. The exploit has been publicly disclosed and may be utilized. Patch name: 6b21c8b2ecfef5c95142cbc2c32f185cb1c26ab0. To fix this issue, it is recommended to deploy a patch.
Remediation
There is no fixed version for Debian:12 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-11495
- https://sourceware.org/bugzilla/attachment.cgi?id=16393
- https://sourceware.org/bugzilla/show_bug.cgi?id=33502
- https://sourceware.org/bugzilla/show_bug.cgi?id=33502#c3
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=6b21c8b2ecfef5c95142cbc2c32f185cb1c26ab0
- https://vuldb.com/?ctiid.327620
- https://vuldb.com/?id.327620
- https://vuldb.com/?submit.668290
- https://www.gnu.org/
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability was found in GNU Binutils 2.45. Affected is the function elf_link_add_object_symbols of the file bfd/elflink.c of the component Linker. The manipulation results in out-of-bounds read. The attack needs to be approached locally. The exploit has been made public and could be used. Upgrading to version 2.46 is able to address this issue. The patch is identified as 72efdf166aa0ed72ecc69fc2349af6591a7a19c0. Upgrading the affected component is advised.
Remediation
There is no fixed version for Debian:12 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-11413
- https://sourceware.org/bugzilla/attachment.cgi?id=16362
- https://sourceware.org/bugzilla/show_bug.cgi?id=33456#c10
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=72efdf166aa0ed72ecc69fc2349af6591a7a19c0
- https://vuldb.com/?ctiid.327349
- https://vuldb.com/?id.327349
- https://vuldb.com/?submit.665587
- https://www.gnu.org/
- https://vuldb.com/?submit.665590
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://sourceware.org/bugzilla/show_bug.cgi?id=33452
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability was determined in GNU Binutils 2.45. Affected by this vulnerability is the function get_link_hash_entry of the file bfd/elflink.c of the component Linker. This manipulation causes out-of-bounds read. The attack can only be executed locally. The exploit has been publicly disclosed and may be utilized. Upgrading to version 2.46 addresses this issue. Patch name: aeaaa9af6359c8e394ce9cf24911fec4f4d23703. It is advisable to upgrade the affected component.
Remediation
There is no fixed version for Debian:12 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-11414
- https://sourceware.org/bugzilla/attachment.cgi?id=16361
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=aeaaa9af6359c8e394ce9cf24911fec4f4d23703
- https://vuldb.com/?ctiid.327350
- https://vuldb.com/?id.327350
- https://vuldb.com/?submit.665591
- https://www.gnu.org/
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://sourceware.org/bugzilla/show_bug.cgi?id=33450
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability has been found in GNU Binutils 2.45. This impacts the function bfd_elf_gc_record_vtentry of the file bfd/elflink.c of the component Linker. The manipulation leads to out-of-bounds read. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used. The identifier of the patch is 047435dd988a3975d40c6626a8f739a0b2e154bc. To fix this issue, it is recommended to deploy a patch.
Remediation
There is no fixed version for Debian:12 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-11412
- https://sourceware.org/bugzilla/attachment.cgi?id=16378
- https://sourceware.org/bugzilla/show_bug.cgi?id=33452#c8
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=047435dd988a3975d40c6626a8f739a0b2e154bc
- https://vuldb.com/?ctiid.327348
- https://vuldb.com/?id.327348
- https://www.gnu.org/
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://sourceware.org/bugzilla/show_bug.cgi?id=33452
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability was found in GNU Binutils 2.45. Impacted is the function _bfd_x86_elf_late_size_sections of the file bfd/elfxx-x86.c of the component Linker. The manipulation results in out-of-bounds read. The attack needs to be approached locally. The exploit has been made public and could be used. The patch is identified as b6ac5a8a5b82f0ae6a4642c8d7149b325f4cc60a. A patch should be applied to remediate this issue.
Remediation
There is no fixed version for Debian:12 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-11494
- https://sourceware.org/bugzilla/attachment.cgi?id=16389
- https://sourceware.org/bugzilla/show_bug.cgi?id=33499
- https://sourceware.org/bugzilla/show_bug.cgi?id=33499#c2
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b6ac5a8a5b82f0ae6a4642c8d7149b325f4cc60a
- https://vuldb.com/?ctiid.327619
- https://vuldb.com/?id.327619
- https://vuldb.com/?submit.668281
- https://www.gnu.org/
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A weakness has been identified in GNU Binutils 2.45. The affected element is the function vfinfo of the file ldmisc.c. Executing a manipulation can lead to out-of-bounds read. The attack can only be executed locally. The exploit has been made available to the public and could be used for attacks. This patch is called 16357. It is best practice to apply a patch to resolve this issue.
Remediation
There is no fixed version for Debian:12 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-11840
- https://sourceware.org/bugzilla/attachment.cgi?id=16351
- https://sourceware.org/bugzilla/attachment.cgi?id=16357
- https://sourceware.org/bugzilla/show_bug.cgi?id=33455
- https://vuldb.com/?ctiid.328775
- https://vuldb.com/?id.328775
- https://vuldb.com/?submit.661281
- https://www.gnu.org/
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
The demangle_template function in cplus-dem.c in GNU libiberty, as distributed in GNU Binutils 2.31.1, contains an integer overflow vulnerability (for "Create an array for saving the template argument values") that can trigger a heap-based buffer overflow, as demonstrated by nm.
Remediation
There is no fixed version for Debian:12 binutils.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A flaw was found in the readelf utility of the binutils package. A local attacker could exploit two Denial of Service (DoS) vulnerabilities by providing a specially crafted Executable and Linkable Format (ELF) file. One vulnerability, a resource exhaustion (CWE-400), can lead to an out-of-memory condition. The other, a null pointer dereference (CWE-476), can cause a segmentation fault. Both issues can result in the readelf utility becoming unresponsive or crashing, leading to a denial of service.
Remediation
There is no fixed version for Debian:12 binutils.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A security flaw has been discovered in GNU Binutils 2.45. Impacted is the function tg_tag_type of the file prdbg.c. Performing a manipulation results in unchecked return value. The attack needs to be approached locally. The exploit has been released to the public and may be used for attacks.
Remediation
There is no fixed version for Debian:12 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-11839
- https://sourceware.org/bugzilla/attachment.cgi?id=16344
- https://vuldb.com/?ctiid.328774
- https://vuldb.com/?id.328774
- https://vuldb.com/?submit.661279
- https://www.gnu.org/
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://sourceware.org/bugzilla/show_bug.cgi?id=33448
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
An issue was discovered in cplus-dem.c in GNU libiberty, as distributed in GNU Binutils 2.30. Stack Exhaustion occurs in the C++ demangling functions provided by libiberty, and there are recursive stack frames: demangle_template_value_parm, demangle_integral_value, and demangle_expression.
Remediation
There is no fixed version for Debian:12 binutils.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1
Detailed paths
-
Introduced through: golang@1.20 › 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.
In libexpat through 2.7.3, a crafted file with an approximate size of 2 MiB can lead to dozens of seconds of processing time.
Remediation
There is no fixed version for Debian:12 expat.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1
Detailed paths
-
Introduced through: golang@1.20 › 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
- https://security-tracker.debian.org/tracker/CVE-2023-52426
- https://cwe.mitre.org/data/definitions/776.html
- https://github.com/libexpat/libexpat/commit/0f075ec8ecb5e43f8fdca5182f8cca4703da0404
- https://github.com/libexpat/libexpat/pull/777
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PNRIHC7DVVRAIWFRGV23Y6UZXFBXSQDB/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WNUBSGZFEZOBHJFTAD42SAN4ATW2VEMV/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PNRIHC7DVVRAIWFRGV23Y6UZXFBXSQDB/
- https://security.netapp.com/advisory/ntap-20240307-0005/
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1
Detailed paths
-
Introduced through: golang@1.20 › 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 before 2.7.5 allows an infinite loop while parsing DTD content.
Remediation
There is no fixed version for Debian:12 expat.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1
Detailed paths
-
Introduced through: golang@1.20 › 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 before 2.7.5 allows a NULL pointer dereference in the function setContext on retry after an earlier ouf-of-memory condition.
Remediation
There is no fixed version for Debian:12 expat.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1
Detailed paths
-
Introduced through: golang@1.20 › 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 before 2.7.5 allows a NULL pointer dereference with empty external parameter entity content.
Remediation
There is no fixed version for Debian:12 expat.
References
low severity
- Vulnerable module: gcc-12
- Introduced through: gcc-12@12.2.0-14, gcc-12/cpp-12@12.2.0-14 and others
Detailed paths
-
Introduced through: golang@1.20 › gcc-12@12.2.0-14
-
Introduced through: golang@1.20 › gcc-12/cpp-12@12.2.0-14
-
Introduced through: golang@1.20 › gcc-12/g++-12@12.2.0-14
-
Introduced through: golang@1.20 › gcc-12/gcc-12-base@12.2.0-14
-
Introduced through: golang@1.20 › gcc-12/libasan8@12.2.0-14
-
Introduced through: golang@1.20 › gcc-12/libatomic1@12.2.0-14
-
Introduced through: golang@1.20 › gcc-12/libcc1-0@12.2.0-14
-
Introduced through: golang@1.20 › gcc-12/libgcc-12-dev@12.2.0-14
-
Introduced through: golang@1.20 › gcc-12/libgcc-s1@12.2.0-14
-
Introduced through: golang@1.20 › gcc-12/libgomp1@12.2.0-14
-
Introduced through: golang@1.20 › gcc-12/libitm1@12.2.0-14
-
Introduced through: golang@1.20 › gcc-12/liblsan0@12.2.0-14
-
Introduced through: golang@1.20 › gcc-12/libquadmath0@12.2.0-14
-
Introduced through: golang@1.20 › gcc-12/libstdc++-12-dev@12.2.0-14
-
Introduced through: golang@1.20 › gcc-12/libstdc++6@12.2.0-14
-
Introduced through: golang@1.20 › gcc-12/libtsan2@12.2.0-14
-
Introduced through: golang@1.20 › gcc-12/libubsan1@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
- https://security-tracker.debian.org/tracker/CVE-2022-27943
- https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105039
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/H424YXGW7OKXS2NCAP35OP6Y4P4AW6VG/
- https://sourceware.org/bugzilla/show_bug.cgi?id=28995
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/H424YXGW7OKXS2NCAP35OP6Y4P4AW6VG/
low severity
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2
Detailed paths
-
Introduced through: golang@1.20 › 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.
In SQLite 3.49.0 before 3.49.1, certain argument values to sqlite3_db_config (in the C-language API) can cause a denial of service (application crash). An sz*nBig multiplication is not cast to a 64-bit integer, and consequently some memory allocations may be incorrect.
Remediation
There is no fixed version for Debian:12 sqlite3.
References
- https://security-tracker.debian.org/tracker/CVE-2025-29088
- https://gist.github.com/ylwango613/d3883fb9f6ba8a78086356779ce88248
- https://github.com/sqlite/sqlite/commit/56d2fd008b108109f489339f5fd55212bb50afd4
- https://sqlite.org/forum/forumpost/48f365daec
- https://sqlite.org/releaselog/3_49_1.html
- https://www.sqlite.org/cves.html
low severity
- Vulnerable module: tar
- Introduced through: tar@1.34+dfsg-1.2
Detailed paths
-
Introduced through: golang@1.20 › 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.
A flaw was found in tar. A remote attacker could exploit this vulnerability by crafting a malicious archive, leading to hidden file injection with fully attacker-controlled content. This bypasses pre-extraction inspection mechanisms, potentially allowing an attacker to introduce malicious files onto a system without detection.
Remediation
There is no fixed version for Debian:12 tar.
References
- https://security-tracker.debian.org/tracker/CVE-2026-5704
- https://access.redhat.com/security/cve/CVE-2026-5704
- https://bugzilla.redhat.com/show_bug.cgi?id=2455360
- http://www.openwall.com/lists/oss-security/2026/04/11/10
- http://www.openwall.com/lists/oss-security/2026/04/11/11
- http://www.openwall.com/lists/oss-security/2026/04/12/2
low severity
- 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: golang@1.20 › util-linux/bsdutils@1:2.38.1-5+b1
-
Introduced through: golang@1.20 › util-linux/libblkid1@2.38.1-5+b1
-
Introduced through: golang@1.20 › util-linux/libmount1@2.38.1-5+b1
-
Introduced through: golang@1.20 › util-linux/libsmartcols1@2.38.1-5+b1
-
Introduced through: golang@1.20 › util-linux/libuuid1@2.38.1-5+b1
-
Introduced through: golang@1.20 › util-linux/mount@2.38.1-5+b1
-
Introduced through: golang@1.20 › util-linux/util-linux@2.38.1-5+b1
-
Introduced through: golang@1.20 › 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
- https://security-tracker.debian.org/tracker/CVE-2022-0563
- https://lore.kernel.org/util-linux/20220214110609.msiwlm457ngoic6w@ws.net.home/T/#u
- https://lore.kernel.org/util-linux/20220214110609.msiwlm457ngoic6w%40ws.net.home/T/#u
- https://security.gentoo.org/glsa/202401-08
- https://security.netapp.com/advisory/ntap-20220331-0002/
low severity
- Vulnerable module: zlib/zlib1g
- Introduced through: zlib/zlib1g@1:1.2.13.dfsg-1
Detailed paths
-
Introduced through: golang@1.20 › 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.
zlib before 1.3.2 allows CPU consumption via crc32_combine64 and crc32_combine_gen64 because x2nmodp can do right shifts within a loop that has no termination condition.
Remediation
There is no fixed version for Debian:12 zlib.
References
- https://security-tracker.debian.org/tracker/CVE-2026-27171
- https://7asecurity.com/blog/2026/02/zlib-7asecurity-audit/
- https://github.com/madler/zlib/releases/tag/v1.3.2
- https://ostif.org/zlib-audit-complete/
- https://github.com/madler/zlib/issues/904
- https://7asecurity.com/reports/pentest-report-zlib-RC1.1.pdf
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability has been found in GNU Binutils 2.43 and classified as problematic. Affected by this vulnerability is the function __sanitizer::internal_strlen of the file binutils/nm.c of the component nm. The manipulation of the argument const leads to buffer overflow. The attack can be launched remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used.
Remediation
There is no fixed version for Debian:12 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-1147
- https://sourceware.org/bugzilla/attachment.cgi?id=15881
- https://sourceware.org/bugzilla/show_bug.cgi?id=32556
- https://vuldb.com/?ctiid.295051
- https://vuldb.com/?id.295051
- https://www.gnu.org/
- https://security.netapp.com/advisory/ntap-20250404-0003/
- https://vuldb.com/?submit.485254
low severity
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10+deb12u5, curl/libcurl3-gnutls@7.88.1-10+deb12u5 and others
Detailed paths
-
Introduced through: golang@1.20 › curl@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl3-gnutls@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl4@7.88.1-10+deb12u5
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.
Successfully using libcurl to do a transfer over a specific HTTP proxy
(proxyA) with Digest authentication and then changing the proxy host to
a second one (proxyB) for a second transfer, reusing the same handle, makes
libcurl wrongly pass on the Proxy-Authorization: header field meant for
proxyA, to proxyB.
Remediation
There is no fixed version for Debian:12 curl.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u4, glibc/libc-dev-bin@2.36-9+deb12u4 and others
Detailed paths
-
Introduced through: golang@1.20 › glibc/libc-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc-dev-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6-dev@2.36-9+deb12u4
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
- https://security-tracker.debian.org/tracker/CVE-2019-1010024
- https://support.f5.com/csp/article/K06046097
- https://support.f5.com/csp/article/K06046097?utm_source=f5support&utm_medium=RSS
- https://sourceware.org/bugzilla/show_bug.cgi?id=22852
- http://www.securityfocus.com/bid/109162
- https://ubuntu.com/security/CVE-2019-1010024
- https://support.f5.com/csp/article/K06046097?utm_source=f5support&%3Butm_medium=RSS
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u4, glibc/libc-dev-bin@2.36-9+deb12u4 and others
Detailed paths
-
Introduced through: golang@1.20 › glibc/libc-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc-dev-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6-dev@2.36-9+deb12u4
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
- https://security-tracker.debian.org/tracker/CVE-2019-1010025
- https://support.f5.com/csp/article/K06046097
- https://support.f5.com/csp/article/K06046097?utm_source=f5support&utm_medium=RSS
- https://sourceware.org/bugzilla/show_bug.cgi?id=22853
- https://ubuntu.com/security/CVE-2019-1010025
- https://support.f5.com/csp/article/K06046097?utm_source=f5support&%3Butm_medium=RSS
low severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2+deb12u2
Detailed paths
-
Introduced through: golang@1.20 › openssh/openssh-client@1:9.2p1-2+deb12u2
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
- https://security-tracker.debian.org/tracker/CVE-2016-20012
- https://security.netapp.com/advisory/ntap-20211014-0005/
- https://github.com/openssh/openssh-portable/blob/d0fffc88c8fe90c1815c6f4097bc8cbcabc0f3dd/auth2-pubkey.c#L261-L265
- https://github.com/openssh/openssh-portable/pull/270
- https://rushter.com/blog/public-ssh-keys/
- https://utcc.utoronto.ca/~cks/space/blog/tech/SSHKeysAreInfoLeak
- https://github.com/openssh/openssh-portable/pull/270#issuecomment-920577097
- https://github.com/openssh/openssh-portable/pull/270#issuecomment-943909185
- https://www.openwall.com/lists/oss-security/2018/08/24/1
low severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2+deb12u2
Detailed paths
-
Introduced through: golang@1.20 › openssh/openssh-client@1:9.2p1-2+deb12u2
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
- https://security-tracker.debian.org/tracker/CVE-2007-2243
- https://security.netapp.com/advisory/ntap-20191107-0003/
- http://lists.grok.org.uk/pipermail/full-disclosure/2007-April/053906.html
- http://lists.grok.org.uk/pipermail/full-disclosure/2007-April/053951.html
- http://securityreason.com/securityalert/2631
- http://www.securityfocus.com/bid/23601
- https://exchange.xforce.ibmcloud.com/vulnerabilities/33794
- http://www.osvdb.org/34600
low severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2+deb12u2
Detailed paths
-
Introduced through: golang@1.20 › openssh/openssh-client@1:9.2p1-2+deb12u2
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
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.19-1~deb12u1 and systemd/libudev1@252.19-1~deb12u1
Detailed paths
-
Introduced through: golang@1.20 › systemd/libsystemd0@252.19-1~deb12u1
-
Introduced through: golang@1.20 › systemd/libudev1@252.19-1~deb12u1
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
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.19-1~deb12u1 and systemd/libudev1@252.19-1~deb12u1
Detailed paths
-
Introduced through: golang@1.20 › systemd/libsystemd0@252.19-1~deb12u1
-
Introduced through: golang@1.20 › systemd/libudev1@252.19-1~deb12u1
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
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.19-1~deb12u1 and systemd/libudev1@252.19-1~deb12u1
Detailed paths
-
Introduced through: golang@1.20 › systemd/libsystemd0@252.19-1~deb12u1
-
Introduced through: golang@1.20 › systemd/libudev1@252.19-1~deb12u1
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
- Vulnerable module: xz-utils/liblzma5
- Introduced through: xz-utils/liblzma5@5.4.1-0.2
Detailed paths
-
Introduced through: golang@1.20 › xz-utils/liblzma5@5.4.1-0.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream xz-utils package and not the xz-utils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
XZ Utils provide a general-purpose data-compression library plus command-line tools. Prior to version 5.8.3, if lzma_index_decoder() was used to decode an Index that contained no Records, the resulting lzma_index was left in a state where where a subsequent lzma_index_append() would allocate too little memory, and a buffer overflow would occur. This issue has been patched in version 5.8.3.
Remediation
There is no fixed version for Debian:12 xz-utils.
References
- https://security-tracker.debian.org/tracker/CVE-2026-34743
- https://github.com/tukaani-project/xz/commit/c8c22869e780ff57c96b46939c3d79ff99395f87
- https://github.com/tukaani-project/xz/releases/tag/v5.8.3
- https://github.com/tukaani-project/xz/security/advisories/GHSA-x872-m794-cxhv
- http://www.openwall.com/lists/oss-security/2026/03/31/13
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A flaw was found in binutils, specifically within the readelf utility. This vulnerability allows a local attacker to cause a Denial of Service (DoS) by tricking a user into processing a specially crafted Executable and Linkable Format (ELF) file. The exploitation of this flaw can lead to the system becoming unresponsive due to excessive resource consumption or a program crash.
Remediation
There is no fixed version for Debian:12 binutils.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability classified as critical was found in GNU Binutils 2.43. This vulnerability affects the function _bfd_elf_gc_mark_rsec of the file bfd/elflink.c of the component ld. The manipulation leads to memory corruption. The attack can be initiated remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The name of the patch is 931494c9a89558acb36a03a340c01726545eef24. It is recommended to apply a patch to fix this issue.
Remediation
There is no fixed version for Debian:12 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-1181
- https://sourceware.org/bugzilla/attachment.cgi?id=15918
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=931494c9a89558acb36a03a340c01726545eef24
- https://vuldb.com/?ctiid.295084
- https://vuldb.com/?id.295084
- https://www.gnu.org/
- https://security.netapp.com/advisory/ntap-20250425-0007/
- https://sourceware.org/bugzilla/show_bug.cgi?id=32643
- https://vuldb.com/?submit.495402
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability was found in GNU Binutils 2.43 and classified as critical. This issue affects the function _bfd_elf_gc_mark_rsec of the file elflink.c of the component ld. The manipulation leads to heap-based buffer overflow. The attack may be initiated remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. The patch is named f9978defb6fab0bd8583942d97c112b0932ac814. It is recommended to apply a patch to fix this issue.
Remediation
There is no fixed version for Debian:12 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-1176
- https://sourceware.org/bugzilla/attachment.cgi?id=15913
- https://sourceware.org/bugzilla/show_bug.cgi?id=32636
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=f9978defb6fab0bd8583942d97c112b0932ac814
- https://vuldb.com/?ctiid.295079
- https://vuldb.com/?id.295079
- https://vuldb.com/?submit.495329
- https://www.gnu.org/
- https://security.netapp.com/advisory/ntap-20250411-0007/
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability, which was classified as critical, was found in GNU Binutils 2.43. Affected is the function bfd_elf_reloc_symbol_deleted_p of the file bfd/elflink.c of the component ld. The manipulation leads to memory corruption. It is possible to launch the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. The patch is identified as b425859021d17adf62f06fb904797cf8642986ad. It is recommended to apply a patch to fix this issue.
Remediation
There is no fixed version for Debian:12 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-1182
- https://sourceware.org/bugzilla/attachment.cgi?id=15919
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b425859021d17adf62f06fb904797cf8642986ad
- https://vuldb.com/?ctiid.295086
- https://vuldb.com/?id.295086
- https://www.gnu.org/
- https://sourceware.org/bugzilla/show_bug.cgi?id=32644
- https://vuldb.com/?submit.495407
low severity
- 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: golang@1.20 › git@1:2.39.2-1.1
-
Introduced through: golang@1.20 › 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
- Vulnerable module: coreutils
- Introduced through: coreutils@9.1-1
Detailed paths
-
Introduced through: golang@1.20 › 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
- 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: golang@1.20 › gnupg2/dirmngr@2.2.40-1.1
-
Introduced through: golang@1.20 › gnupg2/gnupg@2.2.40-1.1
-
Introduced through: golang@1.20 › gnupg2/gnupg-l10n@2.2.40-1.1
-
Introduced through: golang@1.20 › gnupg2/gnupg-utils@2.2.40-1.1
-
Introduced through: golang@1.20 › gnupg2/gpg@2.2.40-1.1
-
Introduced through: golang@1.20 › gnupg2/gpg-agent@2.2.40-1.1
-
Introduced through: golang@1.20 › gnupg2/gpg-wks-client@2.2.40-1.1
-
Introduced through: golang@1.20 › gnupg2/gpg-wks-server@2.2.40-1.1
-
Introduced through: golang@1.20 › gnupg2/gpgconf@2.2.40-1.1
-
Introduced through: golang@1.20 › gnupg2/gpgsm@2.2.40-1.1
-
Introduced through: golang@1.20 › 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.
In GnuPG before 2.5.5, if a user chooses to import a certificate with certain crafted subkey data that lacks a valid backsig or that has incorrect usage flags, the user loses the ability to verify signatures made from certain other signing keys, aka a "verification DoS."
Remediation
There is no fixed version for Debian:12 gnupg2.
References
low severity
- 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: golang@1.20 › gnupg2/dirmngr@2.2.40-1.1
-
Introduced through: golang@1.20 › gnupg2/gnupg@2.2.40-1.1
-
Introduced through: golang@1.20 › gnupg2/gnupg-l10n@2.2.40-1.1
-
Introduced through: golang@1.20 › gnupg2/gnupg-utils@2.2.40-1.1
-
Introduced through: golang@1.20 › gnupg2/gpg@2.2.40-1.1
-
Introduced through: golang@1.20 › gnupg2/gpg-agent@2.2.40-1.1
-
Introduced through: golang@1.20 › gnupg2/gpg-wks-client@2.2.40-1.1
-
Introduced through: golang@1.20 › gnupg2/gpg-wks-server@2.2.40-1.1
-
Introduced through: golang@1.20 › gnupg2/gpgconf@2.2.40-1.1
-
Introduced through: golang@1.20 › gnupg2/gpgsm@2.2.40-1.1
-
Introduced through: golang@1.20 › 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.
In GnuPG through 2.4.8, if a signed message has \f at the end of a plaintext line, an adversary can construct a modified message that places additional text after the signed material, such that signature verification of the modified message succeeds (although an "invalid armor" message is printed during verification). This is related to use of \f as a marker to denote truncation of a long plaintext line.
Remediation
There is no fixed version for Debian:12 gnupg2.
References
low severity
- Vulnerable module: openldap/libldap-2.5-0
- Introduced through: openldap/libldap-2.5-0@2.5.13+dfsg-5
Detailed paths
-
Introduced through: golang@1.20 › 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
- Vulnerable module: pam/libpam-modules
- Introduced through: pam/libpam-modules@1.5.2-6+deb12u1, pam/libpam-modules-bin@1.5.2-6+deb12u1 and others
Detailed paths
-
Introduced through: golang@1.20 › pam/libpam-modules@1.5.2-6+deb12u1
-
Introduced through: golang@1.20 › pam/libpam-modules-bin@1.5.2-6+deb12u1
-
Introduced through: golang@1.20 › pam/libpam-runtime@1.5.2-6+deb12u1
-
Introduced through: golang@1.20 › pam/libpam0g@1.5.2-6+deb12u1
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.
A vulnerability was found in PAM. The secret information is stored in memory, where the attacker can trigger the victim program to execute by sending characters to its standard input (stdin). As this occurs, the attacker can train the branch predictor to execute an ROP chain speculatively. This flaw could result in leaked passwords, such as those found in /etc/shadow while performing authentications.
Remediation
There is no fixed version for Debian:12 pam.
References
- https://security-tracker.debian.org/tracker/CVE-2024-10041
- https://access.redhat.com/security/cve/CVE-2024-10041
- https://bugzilla.redhat.com/show_bug.cgi?id=2319212
- https://access.redhat.com/errata/RHSA-2024:9941
- https://access.redhat.com/errata/RHSA-2024:10379
- https://access.redhat.com/errata/RHSA-2024:11250
low severity
- Vulnerable module: coreutils
- Introduced through: coreutils@9.1-1
Detailed paths
-
Introduced through: golang@1.20 › 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.
A flaw was found in GNU Coreutils. The sort utility's begfield() function is vulnerable to a heap buffer under-read. The program may access memory outside the allocated buffer if a user runs a crafted command using the traditional key format. A malicious input could lead to a crash or leak sensitive data.
Remediation
There is no fixed version for Debian:12 coreutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-5278
- https://access.redhat.com/security/cve/CVE-2025-5278
- https://bugzilla.redhat.com/show_bug.cgi?id=2368764
- http://www.openwall.com/lists/oss-security/2025/05/27/2
- http://www.openwall.com/lists/oss-security/2025/05/29/1
- https://cgit.git.savannah.gnu.org/cgit/coreutils.git/tree/NEWS?id=8c9602e3a145e9596dc1a63c6ed67865814b6633#n14
- http://www.openwall.com/lists/oss-security/2025/05/29/2
- https://debbugs.gnu.org/cgi/bugreport.cgi?bug=78507
- https://cgit.git.savannah.gnu.org/cgit/coreutils.git/commit/?id=8c9602e3a145e9596dc1a63c6ed67865814b6633
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.19-1~deb12u1 and systemd/libudev1@252.19-1~deb12u1
Detailed paths
-
Introduced through: golang@1.20 › systemd/libsystemd0@252.19-1~deb12u1
-
Introduced through: golang@1.20 › systemd/libudev1@252.19-1~deb12u1
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
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u4, glibc/libc-dev-bin@2.36-9+deb12u4 and others
Detailed paths
-
Introduced through: golang@1.20 › glibc/libc-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc-dev-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6-dev@2.36-9+deb12u4
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
- https://security-tracker.debian.org/tracker/CVE-2010-4756
- http://cxib.net/stuff/glob-0day.c
- http://securityreason.com/achievement_securityalert/89
- http://securityreason.com/exploitalert/9223
- https://bugzilla.redhat.com/show_bug.cgi?id=681681
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2010-4756
- https://security.netapp.com/advisory/ntap-20241108-0002/
low severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u1
Detailed paths
-
Introduced through: golang@1.20 › gnutls28/libgnutls30@3.7.9-2+deb12u1
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
- https://security-tracker.debian.org/tracker/CVE-2011-3389
- http://lists.apple.com/archives/Security-announce/2011//Oct/msg00001.html
- http://lists.apple.com/archives/Security-announce/2011//Oct/msg00002.html
- http://support.apple.com/kb/HT4999
- http://support.apple.com/kb/HT5001
- http://support.apple.com/kb/HT5130
- http://support.apple.com/kb/HT5281
- http://support.apple.com/kb/HT5501
- http://support.apple.com/kb/HT6150
- http://lists.apple.com/archives/security-announce/2012/Feb/msg00000.html
- http://lists.apple.com/archives/security-announce/2012/Jul/msg00001.html
- http://lists.apple.com/archives/security-announce/2012/May/msg00001.html
- http://lists.apple.com/archives/security-announce/2012/Sep/msg00004.html
- http://lists.apple.com/archives/security-announce/2013/Oct/msg00004.html
- http://www.us-cert.gov/cas/techalerts/TA12-010A.html
- http://www.kb.cert.org/vuls/id/864643
- http://googlechromereleases.blogspot.com/2011/10/chrome-stable-release.html
- http://blog.mozilla.com/security/2011/09/27/attack-against-tls-protected-communications/
- http://blogs.technet.com/b/msrc/archive/2011/09/26/microsoft-releases-security-advisory-2588513.aspx
- http://blogs.technet.com/b/srd/archive/2011/09/26/is-ssl-broken-more-about-security-advisory-2588513.aspx
- http://curl.haxx.se/docs/adv_20120124B.html
- http://downloads.asterisk.org/pub/security/AST-2016-001.html
- http://my.opera.com/securitygroup/blog/2011/09/28/the-beast-ssl-tls-issue
- https://blogs.oracle.com/sunsecurity/entry/multiple_vulnerabilities_in_fetchmail
- https://bugzilla.novell.com/show_bug.cgi?id=719047
- https://cert-portal.siemens.com/productcert/pdf/ssa-556833.pdf
- http://technet.microsoft.com/security/advisory/2588513
- http://www.apcmedia.com/salestools/SJHN-7RKGNM/SJHN-7RKGNM_R4_EN.pdf
- http://www.ibm.com/developerworks/java/jdk/alerts/
- http://www.imperialviolet.org/2011/09/23/chromeandbeast.html
- http://www.opera.com/docs/changelogs/mac/1151/
- http://www.opera.com/docs/changelogs/mac/1160/
- http://www.opera.com/docs/changelogs/unix/1151/
- http://www.opera.com/docs/changelogs/unix/1160/
- http://www.opera.com/docs/changelogs/windows/1151/
- http://www.opera.com/docs/changelogs/windows/1160/
- http://www.opera.com/support/kb/view/1004/
- http://www.debian.org/security/2012/dsa-2398
- http://security.gentoo.org/glsa/glsa-201203-02.xml
- http://security.gentoo.org/glsa/glsa-201406-32.xml
- https://h20564.www2.hp.com/portal/site/hpsc/public/kb/docDisplay?docId=emr_na-c03839862
- http://marc.info/?l=bugtraq&m=132750579901589&w=2
- http://marc.info/?l=bugtraq&m=132872385320240&w=2
- http://marc.info/?l=bugtraq&m=133365109612558&w=2
- http://marc.info/?l=bugtraq&m=133728004526190&w=2
- http://marc.info/?l=bugtraq&m=134254866602253&w=2
- http://marc.info/?l=bugtraq&m=134254957702612&w=2
- http://ekoparty.org/2011/juliano-rizzo.php
- http://eprint.iacr.org/2004/111
- http://eprint.iacr.org/2006/136
- http://isc.sans.edu/diary/SSL+TLS+part+3+/11635
- https://ics-cert.us-cert.gov/advisories/ICSMA-18-058-02
- http://vnhacker.blogspot.com/2011/09/beast.html
- http://www.educatedguesswork.org/2011/09/security_impact_of_the_rizzodu.html
- http://www.insecure.cl/Beast-SSL.rar
- https://docs.microsoft.com/en-us/security-updates/securitybulletins/2012/ms12-006
- http://technet.microsoft.com/security/bulletin/MS12-006
- http://lists.opensuse.org/opensuse-security-announce/2012-01/msg00049.html
- http://lists.opensuse.org/opensuse-security-announce/2012-01/msg00051.html
- http://lists.opensuse.org/opensuse-security-announce/2012-05/msg00009.html
- http://www.oracle.com/technetwork/topics/security/cpujan2015-1972971.html
- http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html
- http://www.oracle.com/technetwork/topics/security/javacpuoct2011-443431.html
- http://osvdb.org/74829
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14752
- https://bugzilla.redhat.com/show_bug.cgi?id=737506
- http://rhn.redhat.com/errata/RHSA-2012-0508.html
- http://rhn.redhat.com/errata/RHSA-2013-1455.html
- http://secunia.com/advisories/45791
- http://secunia.com/advisories/47998
- http://secunia.com/advisories/48256
- http://secunia.com/advisories/48692
- http://secunia.com/advisories/48915
- http://secunia.com/advisories/48948
- http://secunia.com/advisories/49198
- http://secunia.com/advisories/55322
- http://secunia.com/advisories/55350
- http://secunia.com/advisories/55351
- http://www.securityfocus.com/bid/49388
- http://www.securityfocus.com/bid/49778
- http://www.securitytracker.com/id?1025997
- http://www.securitytracker.com/id?1026103
- http://www.securitytracker.com/id?1026704
- http://www.securitytracker.com/id/1029190
- http://lists.opensuse.org/opensuse-security-announce/2020-01/msg00040.html
- https://hermes.opensuse.org/messages/13154861
- https://hermes.opensuse.org/messages/13155432
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2011-3389
- http://www.ubuntu.com/usn/USN-1263-1
- http://www.mandriva.com/security/advisories?name=MDVSA-2012:058
- http://www.redhat.com/support/errata/RHSA-2011-1384.html
- http://www.redhat.com/support/errata/RHSA-2012-0006.html
- https://github.com/mpgn/BEAST-PoC
low severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2+deb12u2
Detailed paths
-
Introduced through: golang@1.20 › openssh/openssh-client@1:9.2p1-2+deb12u2
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
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2
Detailed paths
-
Introduced through: golang@1.20 › 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
- https://security-tracker.debian.org/tracker/CVE-2021-45346
- https://github.com/guyinatuxedo/sqlite3_record_leaking
- https://security.netapp.com/advisory/ntap-20220303-0001/
- https://sqlite.org/forum/forumpost/056d557c2f8c452ed5
- https://sqlite.org/forum/forumpost/53de8864ba114bf6
- https://www.sqlite.org/cves.html#status_of_recent_sqlite_cves
low severity
- Vulnerable module: openldap/libldap-2.5-0
- Introduced through: openldap/libldap-2.5-0@2.5.13+dfsg-5
Detailed paths
-
Introduced through: golang@1.20 › 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
- https://security-tracker.debian.org/tracker/CVE-2020-15719
- https://access.redhat.com/errata/RHBA-2019:3674
- https://bugs.openldap.org/show_bug.cgi?id=9266
- https://bugzilla.redhat.com/show_bug.cgi?id=1740070
- http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00033.html
- http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00059.html
- https://kc.mcafee.com/corporate/index?page=content&id=SB10365
- https://www.oracle.com/security-alerts/cpuapr2022.html
low severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2+deb12u2
- Fixed in: 1:9.2p1-2+deb12u6
Detailed paths
-
Introduced through: golang@1.20 › openssh/openssh-client@1:9.2p1-2+deb12u2
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 sshd in OpenSSH before 10.0, the DisableForwarding directive does not adhere to the documentation stating that it disables X11 and agent forwarding.
Remediation
Upgrade Debian:12 openssh to version 1:9.2p1-2+deb12u6 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-32728
- https://ftp.openbsd.org/pub/OpenBSD/patches/7.6/common/013_ssh.patch.sig
- https://github.com/openssh/openssh-portable/commit/fc86875e6acb36401dfc1dfb6b628a9d1460f367
- https://lists.mindrot.org/pipermail/openssh-unix-dev/2025-April/041879.html
- https://www.openssh.com/txt/release-10.0
- https://www.openssh.com/txt/release-7.4
- https://lists.debian.org/debian-lts-announce/2025/05/msg00008.html
- https://security.netapp.com/advisory/ntap-20250425-0002/
low severity
- Vulnerable module: apt
- Introduced through: apt@2.6.1 and apt/libapt-pkg6.0@2.6.1
Detailed paths
-
Introduced through: golang@1.20 › apt@2.6.1
-
Introduced through: golang@1.20 › apt/libapt-pkg6.0@2.6.1
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
- https://security-tracker.debian.org/tracker/CVE-2011-3374
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642480
- https://people.canonical.com/~ubuntu-security/cve/2011/CVE-2011-3374.html
- https://seclists.org/fulldisclosure/2011/Sep/221
- https://snyk.io/vuln/SNYK-LINUX-APT-116518
- https://ubuntu.com/security/CVE-2011-3374
- https://access.redhat.com/security/cve/cve-2011-3374
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability classified as problematic has been found in GNU Binutils 2.43. Affected is the function xstrdup of the file xstrdup.c of the component ld. The manipulation leads to memory leak. It is possible to launch the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue. The code maintainer explains: "I'm not going to commit some of the leak fixes I've been working on to the 2.44 branch due to concern that would destabilise ld. All of the reported leaks in this bugzilla have been fixed on binutils master."
Remediation
There is no fixed version for Debian:12 binutils.
References
low severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u1
- Fixed in: 3.7.9-2+deb12u7
Detailed paths
-
Introduced through: golang@1.20 › gnutls28/libgnutls30@3.7.9-2+deb12u1
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 PKCS#7 padding check, performed during decryption, was not constant-time. This timing side-channel could allow a remote attacker to potentially leak sensitive information about the padding bytes through observable timing differences. This vulnerability is a form of information disclosure.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u7 or higher.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability was found in GNU Binutils 2.44 and classified as problematic. This issue affects the function process_debug_info of the file binutils/dwarf.c of the component DWARF Section Handler. The manipulation leads to memory leak. Attacking locally is a requirement. The identifier of the patch is e51fdff7d2e538c0e5accdd65649ac68e6e0ddd4. It is recommended to apply a patch to fix this issue.
Remediation
There is no fixed version for Debian:12 binutils.
References
low severity
- Vulnerable module: git
- Introduced through: git@1:2.39.2-1.1 and git/git-man@1:2.39.2-1.1
- Fixed in: 1:2.39.5-0+deb12u1
Detailed paths
-
Introduced through: golang@1.20 › git@1:2.39.2-1.1
-
Introduced through: golang@1.20 › 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.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, local clones may end up hardlinking files into the target repository's object database when source and target repository reside on the same disk. If the source repository is owned by a different user, then those hardlinked files may be rewritten at any point in time by the untrusted user. Cloning local repositories will cause Git to either copy or hardlink files of the source repository into the target repository. This significantly speeds up such local clones compared to doing a "proper" clone and saves both disk space and compute time. When cloning a repository located on the same disk that is owned by a different user than the current user we also end up creating such hardlinks. These files will continue to be owned and controlled by the potentially-untrusted user and can be rewritten by them at will in the future. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4.
Remediation
Upgrade Debian:12 git to version 1:2.39.5-0+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-32020
- http://www.openwall.com/lists/oss-security/2024/05/14/2
- https://github.com/git/git/commit/1204e1a824c34071019fe106348eaa6d88f9528d
- https://github.com/git/git/commit/9e65df5eab274bf74c7b570107aacd1303a1e703
- https://github.com/git/git/security/advisories/GHSA-5rfh-556j-fhgj
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/S4CK4IYTXEOBZTEM5K3T6LWOIZ3S44AR/
low severity
- 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: golang@1.20 › gnupg2/dirmngr@2.2.40-1.1
-
Introduced through: golang@1.20 › gnupg2/gnupg@2.2.40-1.1
-
Introduced through: golang@1.20 › gnupg2/gnupg-l10n@2.2.40-1.1
-
Introduced through: golang@1.20 › gnupg2/gnupg-utils@2.2.40-1.1
-
Introduced through: golang@1.20 › gnupg2/gpg@2.2.40-1.1
-
Introduced through: golang@1.20 › gnupg2/gpg-agent@2.2.40-1.1
-
Introduced through: golang@1.20 › gnupg2/gpg-wks-client@2.2.40-1.1
-
Introduced through: golang@1.20 › gnupg2/gpg-wks-server@2.2.40-1.1
-
Introduced through: golang@1.20 › gnupg2/gpgconf@2.2.40-1.1
-
Introduced through: golang@1.20 › gnupg2/gpgsm@2.2.40-1.1
-
Introduced through: golang@1.20 › 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
- https://security-tracker.debian.org/tracker/CVE-2022-3219
- https://access.redhat.com/security/cve/CVE-2022-3219
- https://bugzilla.redhat.com/show_bug.cgi?id=2127010
- https://dev.gnupg.org/D556
- https://dev.gnupg.org/T5993
- https://marc.info/?l=oss-security&m=165696590211434&w=4
- https://security.netapp.com/advisory/ntap-20230324-0001/
low severity
- Vulnerable module: ncurses/libncursesw6
- Introduced through: ncurses/libncursesw6@6.4-4, ncurses/libtinfo6@6.4-4 and others
Detailed paths
-
Introduced through: golang@1.20 › ncurses/libncursesw6@6.4-4
-
Introduced through: golang@1.20 › ncurses/libtinfo6@6.4-4
-
Introduced through: golang@1.20 › ncurses/ncurses-base@6.4-4
-
Introduced through: golang@1.20 › 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.
A vulnerability has been found in GNU ncurses up to 6.5-20250322 and classified as problematic. This vulnerability affects the function postprocess_termcap of the file tinfo/parse_entry.c. The manipulation leads to stack-based buffer overflow. The attack needs to be approached locally. Upgrading to version 6.5-20250329 is able to address this issue. It is recommended to upgrade the affected component.
Remediation
There is no fixed version for Debian:12 ncurses.
References
- https://security-tracker.debian.org/tracker/CVE-2025-6141
- https://invisible-island.net/ncurses/NEWS.html#index-t20250329
- https://lists.gnu.org/archive/html/bug-ncurses/2025-03/msg00107.html
- https://lists.gnu.org/archive/html/bug-ncurses/2025-03/msg00109.html
- https://lists.gnu.org/archive/html/bug-ncurses/2025-03/msg00114.html
- https://vuldb.com/?ctiid.312610
- https://vuldb.com/?id.312610
- https://vuldb.com/?submit.593000
- https://www.gnu.org/
- https://cert-portal.siemens.com/productcert/html/ssa-089022.html
- https://cert-portal.siemens.com/productcert/html/ssa-253495.html
low severity
- Vulnerable module: perl
- Introduced through: perl@5.36.0-7+deb12u1, perl/libperl5.36@5.36.0-7+deb12u1 and others
Detailed paths
-
Introduced through: golang@1.20 › perl@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/libperl5.36@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/perl-base@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/perl-modules-5.36@5.36.0-7+deb12u1
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
- https://security-tracker.debian.org/tracker/CVE-2011-4116
- https://github.com/Perl-Toolchain-Gang/File-Temp/issues/14
- https://rt.cpan.org/Public/Bug/Display.html?id=69106
- https://seclists.org/oss-sec/2011/q4/238
- http://www.openwall.com/lists/oss-security/2011/11/04/2
- http://www.openwall.com/lists/oss-security/2011/11/04/4
low severity
- Vulnerable module: procps
- Introduced through: procps@2:4.0.2-3 and procps/libproc2-0@2:4.0.2-3
Detailed paths
-
Introduced through: golang@1.20 › procps@2:4.0.2-3
-
Introduced through: golang@1.20 › 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
- 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: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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 webbrowser.open() API would accept leading dashes in the URL which could be handled as command line options for certain web browsers. New behavior rejects leading dashes. Users are recommended to sanitize URLs prior to passing to webbrowser.open().
Remediation
There is no fixed version for Debian:12 python3.11.
References
- https://security-tracker.debian.org/tracker/CVE-2026-4519
- https://github.com/python/cpython/commit/3681d47a440865aead912a054d4599087b4270dd
- https://github.com/python/cpython/commit/43fe06b96f6a6cf5cfd5bdab20b8649374956866
- https://github.com/python/cpython/commit/591ed890270c5697b013bf637029fb3e6cd2d73e
- https://github.com/python/cpython/commit/594b5a05dc9913880ac92eded440defbf32a28d1
- https://github.com/python/cpython/commit/82a24a4442312bdcfc4c799885e8b3e00990f02b
- https://github.com/python/cpython/commit/89bfb8e5ed3c7caa241028f1a4eac5f6275a46a4
- https://github.com/python/cpython/commit/9669a912a0e329c094e992204d6bdb8787024d76
- https://github.com/python/cpython/commit/96fc5048605863c7b6fd6289643feb0e97edd96c
- https://github.com/python/cpython/commit/ad4d5ba32af4d80b0dfa2ba9d8203bfb219e60a5
- https://github.com/python/cpython/commit/cbba6119391112aba9c5aebf7b94aea447922c48
- https://github.com/python/cpython/commit/cc023511238ad93ecc8796157c6f9139a2bb2932
- https://github.com/python/cpython/commit/ceac1efc66516ac387eef2c9a0ce671895b44f03
- https://github.com/python/cpython/issues/143930
- https://github.com/python/cpython/pull/143931
- https://mail.python.org/archives/list/security-announce@python.org/thread/AY5NDSS433JK56Q7Q5IS7B37QFZVVOUS/
- http://www.openwall.com/lists/oss-security/2026/03/20/1
low severity
- Vulnerable module: shadow/login
- Introduced through: shadow/login@1:4.13+dfsg1-1+b1 and shadow/passwd@1:4.13+dfsg1-1+b1
- Fixed in: 1:4.13+dfsg1-1+deb12u1
Detailed paths
-
Introduced through: golang@1.20 › shadow/login@1:4.13+dfsg1-1+b1
-
Introduced through: golang@1.20 › 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
Upgrade Debian:12 shadow to version 1:4.13+dfsg1-1+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-29383
- https://github.com/shadow-maint/shadow/commit/e5905c4b84d4fb90aefcd96ee618411ebfac663d
- https://github.com/shadow-maint/shadow/pull/687
- https://lists.debian.org/debian-lts-announce/2025/04/msg00026.html
- https://www.trustwave.com/en-us/resources/blogs/spiderlabs-blog/cve-2023-29383-abusing-linux-chfn-to-misrepresent-etc-passwd/
- https://www.trustwave.com/en-us/resources/security-resources/security-advisories/?fid=31797
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.19-1~deb12u1 and systemd/libudev1@252.19-1~deb12u1
Detailed paths
-
Introduced through: golang@1.20 › systemd/libsystemd0@252.19-1~deb12u1
-
Introduced through: golang@1.20 › systemd/libudev1@252.19-1~deb12u1
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.
In systemd 259, systemd-journald can send ANSI escape sequences to the terminals of arbitrary users when a "logger -p emerg" command is executed, if ForwardToWall=yes is set.
Remediation
There is no fixed version for Debian:12 systemd.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability was found in GNU Binutils 2.43. It has been classified as problematic. This affects the function xstrdup of the file libiberty/xmalloc.c of the component ld. The manipulation leads to memory leak. It is possible to initiate the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue. The code maintainer explains: "I'm not going to commit some of the leak fixes I've been working on to the 2.44 branch due to concern that would destabilise ld. All of the reported leaks in this bugzilla have been fixed on binutils master."
Remediation
There is no fixed version for Debian:12 binutils.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability was found in GNU Binutils 2.43. It has been declared as problematic. This vulnerability affects the function bfd_malloc of the file libbfd.c of the component ld. The manipulation leads to memory leak. The attack can be initiated remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue. The code maintainer explains: "I'm not going to commit some of the leak fixes I've been working on to the 2.44 branch due to concern that would destabilise ld. All of the reported leaks in this bugzilla have been fixed on binutils master."
Remediation
There is no fixed version for Debian:12 binutils.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability was found in GNU Binutils 2.43 and classified as problematic. Affected by this issue is the function link_order_scan of the file ld/ldelfgen.c of the component ld. The manipulation leads to memory leak. The attack may be launched remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue. The code maintainer explains: "I'm not going to commit some of the leak fixes I've been working on to the 2.44 branch due to concern that would destabilise ld. All of the reported leaks in this bugzilla have been fixed on binutils master."
Remediation
There is no fixed version for Debian:12 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-1148
- https://sourceware.org/bugzilla/attachment.cgi?id=15887
- https://sourceware.org/bugzilla/show_bug.cgi?id=32576
- https://vuldb.com/?ctiid.295052
- https://vuldb.com/?id.295052
- https://vuldb.com/?submit.485747
- https://www.gnu.org/
- https://security.netapp.com/advisory/ntap-20250404-0004/
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability was found in GNU Binutils 2.43. It has been rated as problematic. This issue affects the function xmemdup of the file xmemdup.c of the component ld. The manipulation leads to memory leak. The attack may be initiated remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue. The code maintainer explains: "I'm not going to commit some of the leak fixes I've been working on to the 2.44 branch due to concern that would destabilise ld. All of the reported leaks in this bugzilla have been fixed on binutils master."
Remediation
There is no fixed version for Debian:12 binutils.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability classified as problematic has been found in GNU Binutils 2.43. This affects the function _bfd_elf_write_section_eh_frame of the file bfd/elf-eh-frame.c of the component ld. The manipulation leads to memory corruption. It is possible to initiate the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue.
Remediation
There is no fixed version for Debian:12 binutils.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1
Detailed paths
-
Introduced through: golang@1.20 › 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.
In libexpat before 2.7.4, XML_ExternalEntityParserCreate does not copy unknown encoding handler user data.
Remediation
There is no fixed version for Debian:12 expat.
References
low severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2+deb12u2
- Fixed in: 1:9.2p1-2+deb12u10
Detailed paths
-
Introduced through: golang@1.20 › openssh/openssh-client@1:9.2p1-2+deb12u2
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 before 10.3 omits connection multiplexing confirmation for proxy-mode multiplexing sessions.
Remediation
Upgrade Debian:12 openssh to version 1:9.2p1-2+deb12u10 or higher.
References
low severity
- Vulnerable module: git
- Introduced through: git@1:2.39.2-1.1 and git/git-man@1:2.39.2-1.1
- Fixed in: 1:2.39.5-0+deb12u1
Detailed paths
-
Introduced through: golang@1.20 › git@1:2.39.2-1.1
-
Introduced through: golang@1.20 › 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
Upgrade Debian:12 git to version 1:2.39.5-0+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-25815
- http://www.openwall.com/lists/oss-security/2023/04/25/2
- https://axcheron.github.io/exploit-101-format-strings/#writing-to-the-stack
- https://github.com/git-for-windows/git/releases/tag/v2.40.1.windows.1
- https://github.com/git-for-windows/git/security/advisories/GHSA-9w66-8mq8-5vm8
- https://github.com/msys2/MINGW-packages/pull/10461
- https://lists.debian.org/debian-lts-announce/2024/06/msg00018.html
- https://lists.debian.org/debian-lts-announce/2024/09/msg00009.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PI7FZ4NNR5S5J5K6AMVQBH2JFP6NE4L7/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RKOXOAZ42HLXHXTW6JZI4L5DAIYDTYCU/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YFZWGQKB6MM5MNF2DLFTD7KS2KWPICKL/
- https://pubs.opengroup.org/onlinepubs/9699919799/functions/printf.html
- https://security.gentoo.org/glsa/202312-15
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
GNU objdump 2.43 is vulnerable to Buffer Overflow in the BFD (Binary File Descriptor) library's handling of tekhex format files.
Remediation
There is no fixed version for Debian:12 binutils.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
https://www.gnu.org/software/binutils/ nm >=2.43 is affected by: Incorrect Access Control. The type of exploitation is: local. The component is: nm --without-symbol-version function.
Remediation
There is no fixed version for Debian:12 binutils.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
An issue was discovered in function d_unqualified_name in file cp-demangle.c in BinUtils 2.26 allowing attackers to cause a denial of service via crafted PE file.
Remediation
There is no fixed version for Debian:12 binutils.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A buffer overflow vulnerability in function gnu_special in file cplus-dem.c in BinUtils 2.26 allows attackers to cause a denial of service via crafted PE file.
Remediation
There is no fixed version for Debian:12 binutils.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
An issue was discovered in function d_discriminator in file cp-demangle.c in BinUtils 2.26 allows attackers to cause a denial of service via crafted PE file.
Remediation
There is no fixed version for Debian:12 binutils.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
An issue was discovered in function d_print_comp_inner in file cp-demangle.c in BinUtils 2.26 allows attackers to cause a denial of service via crafted PE file.
Remediation
There is no fixed version for Debian:12 binutils.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
An issue was discovered in Binutils before 2.46. The objdump contains a denial-of-service vulnerability when processing a crafted binary with malformed debug information. A logic flaw in the handling of DWARF location list headers can cause objdump to enter an unbounded loop and produce endless output until manually interrupted. This issue affects versions prior to the upstream fix and allows a local attacker to cause excessive resource consumption by supplying a malicious input file.
Remediation
There is no fixed version for Debian:12 binutils.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
Binutils objdump contains a denial-of-service vulnerability when processing a crafted binary with malformed DWARF debug information. A logic error in the handling of DWARF compilation units can result in an invalid offset_size value being used inside byte_get_little_endian, leading to an abort (SIGABRT). The issue was observed in binutils 2.44. A local attacker can trigger the crash by supplying a malicious input file.
Remediation
There is no fixed version for Debian:12 binutils.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
Binutils objdump contains a denial-of-service vulnerability when processing a crafted binary with malformed DWARF debug_rnglists data. A logic error in the handling of the debug_rnglists header can cause objdump to repeatedly print the same warning message and fail to terminate, resulting in an unbounded logging loop until the process is interrupted. The issue was observed in binutils 2.44. A local attacker can exploit this vulnerability by supplying a malicious input file, leading to excessive CPU and I/O usage and preventing completion of the objdump analysis.
Remediation
There is no fixed version for Debian:12 binutils.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
GNU Binutils thru 2.45.1 readelf contains a denial-of-service vulnerability when processing a crafted binary with malformed DWARF loclists data. A logic flaw in the DWARF parsing code can cause readelf to repeatedly print the same table output without making forward progress, resulting in an unbounded output loop that never terminates unless externally interrupted. A local attacker can trigger this behavior by supplying a malicious input file, causing excessive CPU and I/O usage and preventing readelf from completing its analysis.
Remediation
There is no fixed version for Debian:12 binutils.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
GNU Binutils thru 2.45.1 readelf contains a denial-of-service vulnerability when processing a crafted binary with malformed DWARF .debug_rnglists data. A logic flaw in the DWARF parsing path causes readelf to repeatedly print the same warning message without making forward progress, resulting in a non-terminating output loop that requires manual interruption. No evidence of memory corruption or code execution was observed.
Remediation
There is no fixed version for Debian:12 binutils.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: golang@1.20 › binutils@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-common@2.40-2
-
Introduced through: golang@1.20 › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: golang@1.20 › binutils/libbinutils@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf-nobfd0@2.40-2
-
Introduced through: golang@1.20 › binutils/libctf0@2.40-2
-
Introduced through: golang@1.20 › binutils/libgprofng0@2.40-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
GNU Binutils thru 2.46 readelf contains a vulnerability that leads to an abort (SIGABRT) when processing a crafted ELF binary with malformed DWARF abbrev or debug information. Due to incomplete state cleanup in process_debug_info(), an invalid debug_info_p state may propagate into DWARF attribute parsing routines. When certain malformed attributes result in an unexpected data length of zero, byte_get_little_endian() triggers a fatal abort. No evidence of memory corruption or code execution was observed; the impact is limited to denial of service.
Remediation
There is no fixed version for Debian:12 binutils.
References
low severity
new
- Vulnerable module: bzip2/libbz2-1.0
- Introduced through: bzip2/libbz2-1.0@1.0.8-5+b1
Detailed paths
-
Introduced through: golang@1.20 › bzip2/libbz2-1.0@1.0.8-5+b1
NVD Description
Note: Versions mentioned in the description apply only to the upstream bzip2 package and not the bzip2 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
bzip2 contains an off‑by‑one error in the bzip2recover utility. When processing a specially crafted file, the application performs an out‑of‑bounds write to a global buffer, resulting in memory corruption and a crash (denial of service).
This issue was fixed in bzip2 patch 35d122a3df8b0cc4082a4d89fdc6ee99f375fe67
Remediation
There is no fixed version for Debian:12 bzip2.
References
- https://security-tracker.debian.org/tracker/CVE-2026-42250
- https://cert.pl/en/posts/2026/05/CVE-2026-42250/
- https://sourceware.org/bzip2/
- https://inbox.sourceware.org/bzip2-devel/20260528145407.293768-1-mark@klomp.org/
- https://sourceware.org/cgit/bzip2/commit/?id=35d122a3df8b0cc4082a4d89fdc6ee99f375fe67
low severity
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10+deb12u5, curl/libcurl3-gnutls@7.88.1-10+deb12u5 and others
Detailed paths
-
Introduced through: golang@1.20 › curl@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl3-gnutls@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl4@7.88.1-10+deb12u5
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 libcurl is asked to perform automatic gzip decompression of
content-encoded HTTP responses with the CURLOPT_ACCEPT_ENCODING option,
using zlib 1.2.0.3 or older, an attacker-controlled integer overflow would
make libcurl perform a buffer overflow.
Remediation
There is no fixed version for Debian:12 curl.
References
- https://security-tracker.debian.org/tracker/CVE-2025-0725
- https://curl.se/docs/CVE-2025-0725.html
- https://curl.se/docs/CVE-2025-0725.json
- https://hackerone.com/reports/2956023
- http://www.openwall.com/lists/oss-security/2025/02/05/3
- http://www.openwall.com/lists/oss-security/2025/02/06/2
- http://www.openwall.com/lists/oss-security/2025/02/06/4
- https://security.netapp.com/advisory/ntap-20250306-0009/
- https://github.com/curl/curl/commit/76f83f0db23846e254d940ec7
low severity
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10+deb12u5, curl/libcurl3-gnutls@7.88.1-10+deb12u5 and others
- Fixed in: 7.88.1-10+deb12u10
Detailed paths
-
Introduced through: golang@1.20 › curl@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl3-gnutls@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl4@7.88.1-10+deb12u5
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 asked to both use a .netrc file for credentials and to follow HTTP
redirects, curl could leak the password used for the first host to the
followed-to host under certain circumstances.
This flaw only manifests itself if the netrc file has an entry that matches the redirect target hostname but the entry either omits just the password or omits both login and password.
Remediation
Upgrade Debian:12 curl to version 7.88.1-10+deb12u10 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-11053
- https://curl.se/docs/CVE-2024-11053.html
- https://curl.se/docs/CVE-2024-11053.json
- https://hackerone.com/reports/2829063
- http://www.openwall.com/lists/oss-security/2024/12/11/1
- https://security.netapp.com/advisory/ntap-20250124-0012/
- https://security.netapp.com/advisory/ntap-20250131-0003/
- https://security.netapp.com/advisory/ntap-20250131-0004/
low severity
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10+deb12u5, curl/libcurl3-gnutls@7.88.1-10+deb12u5 and others
- Fixed in: 7.88.1-10+deb12u6
Detailed paths
-
Introduced through: golang@1.20 › curl@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl3-gnutls@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl4@7.88.1-10+deb12u5
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
Upgrade Debian:12 curl to version 7.88.1-10+deb12u6 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-2004
- http://seclists.org/fulldisclosure/2024/Jul/18
- http://seclists.org/fulldisclosure/2024/Jul/19
- http://seclists.org/fulldisclosure/2024/Jul/20
- http://www.openwall.com/lists/oss-security/2024/03/27/1
- https://curl.se/docs/CVE-2024-2004.html
- https://curl.se/docs/CVE-2024-2004.json
- https://hackerone.com/reports/2384833
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/2D44YLAUFJU6BZ4XFG2FYV7SBKXB5IZ6/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GMD6UYKCCRCYETWQZUJ65ZRFULT6SHLI/
- https://security.netapp.com/advisory/ntap-20240524-0006/
- https://support.apple.com/kb/HT214118
- https://support.apple.com/kb/HT214119
- https://support.apple.com/kb/HT214120
low severity
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10+deb12u5, curl/libcurl3-gnutls@7.88.1-10+deb12u5 and others
- Fixed in: 7.88.1-10+deb12u8
Detailed paths
-
Introduced through: golang@1.20 › curl@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl3-gnutls@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl4@7.88.1-10+deb12u5
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 is told to use the Certificate Status Request TLS extension, often referred to as OCSP stapling, to verify that the server certificate is valid, it might fail to detect some OCSP problems and instead wrongly consider the response as fine. If the returned status reports another error than 'revoked' (like for example 'unauthorized') it is not treated as a bad certficate.
Remediation
Upgrade Debian:12 curl to version 7.88.1-10+deb12u8 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-8096
- https://curl.se/docs/CVE-2024-8096.html
- https://curl.se/docs/CVE-2024-8096.json
- https://hackerone.com/reports/2669852
- http://www.openwall.com/lists/oss-security/2024/09/11/1
- https://lists.debian.org/debian-lts-announce/2024/11/msg00008.html
- https://security.netapp.com/advisory/ntap-20241011-0005/
low severity
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10+deb12u5, curl/libcurl3-gnutls@7.88.1-10+deb12u5 and others
- Fixed in: 7.88.1-10+deb12u11
Detailed paths
-
Introduced through: golang@1.20 › curl@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl3-gnutls@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl4@7.88.1-10+deb12u5
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 asked to use a .netrc file for credentials and to follow HTTP
redirects, curl could leak the password used for the first host to the
followed-to host under certain circumstances.
This flaw only manifests itself if the netrc file has a default entry that
omits both login and password. A rare circumstance.
Remediation
Upgrade Debian:12 curl to version 7.88.1-10+deb12u11 or higher.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10+deb12u5, curl/libcurl3-gnutls@7.88.1-10+deb12u5 and others
Detailed paths
-
Introduced through: golang@1.20 › curl@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl3-gnutls@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl4@7.88.1-10+deb12u5
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.
curl's websocket code did not update the 32 bit mask pattern for each new outgoing frame as the specification says. Instead it used a fixed mask that persisted and was used throughout the entire connection.
A predictable mask pattern allows for a malicious server to induce traffic between the two communicating parties that could be interpreted by an involved proxy (configured or transparent) as genuine, real, HTTP traffic with content and thereby poison its cache. That cached poisoned content could then be served to all users of that proxy.
Remediation
There is no fixed version for Debian:12 curl.
References
- https://security-tracker.debian.org/tracker/CVE-2025-10148
- https://curl.se/docs/CVE-2025-10148.html
- https://curl.se/docs/CVE-2025-10148.json
- https://hackerone.com/reports/3330839
- http://www.openwall.com/lists/oss-security/2025/09/10/2
- http://www.openwall.com/lists/oss-security/2025/09/10/3
- http://www.openwall.com/lists/oss-security/2025/09/10/4
low severity
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10+deb12u5, curl/libcurl3-gnutls@7.88.1-10+deb12u5 and others
Detailed paths
-
Introduced through: golang@1.20 › curl@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl3-gnutls@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl4@7.88.1-10+deb12u5
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.
curl's code for managing SSH connections when SFTP was done using the wolfSSH powered backend was flawed and missed host verification mechanisms.
This prevents curl from detecting MITM attackers and more.
Remediation
There is no fixed version for Debian:12 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10+deb12u5, curl/libcurl3-gnutls@7.88.1-10+deb12u5 and others
Detailed paths
-
Introduced through: golang@1.20 › curl@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl3-gnutls@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl4@7.88.1-10+deb12u5
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 doing multi-threaded LDAPS transfers (LDAP over TLS) with libcurl, changing TLS options in one thread would inadvertently change them globally and therefore possibly also affect other concurrently setup transfers.
Disabling certificate verification for a specific transfer could unintentionally disable the feature for other threads as well.
Remediation
There is no fixed version for Debian:12 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10+deb12u5, curl/libcurl3-gnutls@7.88.1-10+deb12u5 and others
Detailed paths
-
Introduced through: golang@1.20 › curl@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl3-gnutls@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl4@7.88.1-10+deb12u5
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 doing TLS related transfers with reused easy or multi handles and
altering the CURLSSLOPT_NO_PARTIALCHAIN option, libcurl could accidentally
reuse a CA store cached in memory for which the partial chain option was
reversed. Contrary to the user's wishes and expectations. This could make
libcurl find and accept a trust chain that it otherwise would not.
Remediation
There is no fixed version for Debian:12 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10+deb12u5, curl/libcurl3-gnutls@7.88.1-10+deb12u5 and others
Detailed paths
-
Introduced through: golang@1.20 › curl@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl3-gnutls@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl4@7.88.1-10+deb12u5
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 doing SSH-based transfers using either SCP or SFTP, and setting the known_hosts file, libcurl could still mistakenly accept connecting to hosts not present in the specified file if they were added as recognized in the libssh global known_hosts file.
Remediation
There is no fixed version for Debian:12 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10+deb12u5, curl/libcurl3-gnutls@7.88.1-10+deb12u5 and others
Detailed paths
-
Introduced through: golang@1.20 › curl@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl3-gnutls@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl4@7.88.1-10+deb12u5
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 doing SSH-based transfers using either SCP or SFTP, and asked to do public key authentication, curl would wrongly still ask and authenticate using a locally running SSH agent.
Remediation
There is no fixed version for Debian:12 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10+deb12u5, curl/libcurl3-gnutls@7.88.1-10+deb12u5 and others
Detailed paths
-
Introduced through: golang@1.20 › curl@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl3-gnutls@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl4@7.88.1-10+deb12u5
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 can in some circumstances reuse the wrong connection when asked to do an Negotiate-authenticated HTTP or HTTPS request.
libcurl features a pool of recent connections so that subsequent requests can reuse an existing connection to avoid overhead.
When reusing a connection a range of criterion must first be met. Due to a logical error in the code, a request that was issued by an application could wrongfully reuse an existing connection to the same server that was authenticated using different credentials. One underlying reason being that Negotiate sometimes authenticates connections and not requests, contrary to how HTTP is designed to work.
An application that allows Negotiate authentication to a server (that responds
wanting Negotiate) with user1:password1 and then does another operation to
the same server also using Negotiate but with user2:password2 (while the
previous connection is still alive) - the second request wrongly reused the
same connection and since it then sees that the Negotiate negotiation is
already made, it just sends the request over that connection thinking it uses
the user2 credentials when it is in fact still using the connection
authenticated for user1...
The set of authentication methods to use is set with CURLOPT_HTTPAUTH.
Applications can disable libcurl's reuse of connections and thus mitigate this
problem, by using one of the following libcurl options to alter how
connections are or are not reused: CURLOPT_FRESH_CONNECT,
CURLOPT_MAXCONNECTS and CURLMOPT_MAX_HOST_CONNECTIONS (if using the
curl_multi API).
Remediation
There is no fixed version for Debian:12 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10+deb12u5, curl/libcurl3-gnutls@7.88.1-10+deb12u5 and others
Detailed paths
-
Introduced through: golang@1.20 › curl@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl3-gnutls@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl4@7.88.1-10+deb12u5
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 OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer performs a redirect to a second URL, curl could leak that token to the second hostname under some circumstances.
If the hostname that the first request is redirected to has information in the
used .netrc file, with either of the machine or default keywords, curl
would pass on the bearer token set for the first host also to the second one.
Remediation
There is no fixed version for Debian:12 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10+deb12u5, curl/libcurl3-gnutls@7.88.1-10+deb12u5 and others
Detailed paths
-
Introduced through: golang@1.20 › curl@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl3-gnutls@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl4@7.88.1-10+deb12u5
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.
curl would wrongly reuse an existing HTTP proxy connection doing CONNECT to a server, even if the new request uses different credentials for the HTTP proxy. The proper behavior is to create or use a separate connection.
Remediation
There is no fixed version for Debian:12 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10+deb12u5, curl/libcurl3-gnutls@7.88.1-10+deb12u5 and others
Detailed paths
-
Introduced through: golang@1.20 › curl@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl3-gnutls@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl4@7.88.1-10+deb12u5
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 asked to both use a .netrc file for credentials and to follow HTTP
redirects, libcurl could leak the password used for the first host to the
followed-to host under certain circumstances.
Remediation
There is no fixed version for Debian:12 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10+deb12u5, curl/libcurl3-gnutls@7.88.1-10+deb12u5 and others
Detailed paths
-
Introduced through: golang@1.20 › curl@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl3-gnutls@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl4@7.88.1-10+deb12u5
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 vulnerability exists where a connection requiring TLS incorrectly reuses an existing unencrypted connection from the same connection pool. If an initial transfer is made in clear-text (via IMAP, SMTP, or POP3), a subsequent request to that same host bypasses the TLS requirement and instead transmit data unencrypted.
Remediation
There is no fixed version for Debian:12 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10+deb12u5, curl/libcurl3-gnutls@7.88.1-10+deb12u5 and others
Detailed paths
-
Introduced through: golang@1.20 › curl@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl3-gnutls@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl4@7.88.1-10+deb12u5
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
- https://security-tracker.debian.org/tracker/CVE-2024-2379
- http://seclists.org/fulldisclosure/2024/Jul/18
- http://seclists.org/fulldisclosure/2024/Jul/19
- http://seclists.org/fulldisclosure/2024/Jul/20
- http://www.openwall.com/lists/oss-security/2024/03/27/2
- https://curl.se/docs/CVE-2024-2379.html
- https://curl.se/docs/CVE-2024-2379.json
- https://hackerone.com/reports/2410774
- https://security.netapp.com/advisory/ntap-20240531-0001/
- https://support.apple.com/kb/HT214118
- https://support.apple.com/kb/HT214119
- https://support.apple.com/kb/HT214120
low severity
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10+deb12u5, curl/libcurl3-gnutls@7.88.1-10+deb12u5 and others
Detailed paths
-
Introduced through: golang@1.20 › curl@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl3-gnutls@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl4@7.88.1-10+deb12u5
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.
curl might erroneously pass on credentials for a first proxy to a second proxy.
This can happen when the following conditions are true:
- curl is setup to use specific different proxies for different URL schemes
- the first proxy needs credentials
- the second proxy uses no credentials
- while using the first proxy (using say
http://), curl is asked to follow a redirect to a URL using another scheme (sayhttps://), accessed using a second, different, proxy
Remediation
There is no fixed version for Debian:12 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10+deb12u5, curl/libcurl3-gnutls@7.88.1-10+deb12u5 and others
- Fixed in: 7.88.1-10+deb12u6
Detailed paths
-
Introduced through: golang@1.20 › curl@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl3-gnutls@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl4@7.88.1-10+deb12u5
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
Upgrade Debian:12 curl to version 7.88.1-10+deb12u6 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-2398
- http://seclists.org/fulldisclosure/2024/Jul/18
- http://seclists.org/fulldisclosure/2024/Jul/19
- http://seclists.org/fulldisclosure/2024/Jul/20
- http://www.openwall.com/lists/oss-security/2024/03/27/3
- https://curl.se/docs/CVE-2024-2398.html
- https://curl.se/docs/CVE-2024-2398.json
- https://hackerone.com/reports/2402845
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/2D44YLAUFJU6BZ4XFG2FYV7SBKXB5IZ6/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GMD6UYKCCRCYETWQZUJ65ZRFULT6SHLI/
- https://security.netapp.com/advisory/ntap-20240503-0009/
- https://support.apple.com/kb/HT214118
- https://support.apple.com/kb/HT214119
- https://support.apple.com/kb/HT214120
low severity
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10+deb12u5, curl/libcurl3-gnutls@7.88.1-10+deb12u5 and others
Detailed paths
-
Introduced through: golang@1.20 › curl@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl3-gnutls@7.88.1-10+deb12u5
-
Introduced through: golang@1.20 › curl/libcurl4@7.88.1-10+deb12u5
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 OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer performs a cross-protocol redirect to a second URL that uses an IMAP, LDAP, POP3 or SMTP scheme, curl might wrongly pass on the bearer token to the new target host.
Remediation
There is no fixed version for Debian:12 curl.
References
low severity
- Vulnerable module: dpkg
- Introduced through: dpkg@1.21.22
- Fixed in: 1.21.23
Detailed paths
-
Introduced through: golang@1.20 › dpkg@1.21.22
NVD Description
Note: Versions mentioned in the description apply only to the upstream dpkg package and not the dpkg package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
It was discovered that dpkg-deb does not properly sanitize directory permissions when extracting a control member into a temporary directory, which is documented as being a safe operation even on untrusted data. This may result in leaving temporary files behind on cleanup. Given automated and repeated execution of dpkg-deb commands on adversarial .deb packages or with well compressible files, placed inside a directory with permissions not allowing removal by a non-root user, this can end up in a DoS scenario due to causing disk quota exhaustion or disk full conditions.
Remediation
Upgrade Debian:12 dpkg to version 1.21.23 or higher.
References
low severity
- Vulnerable module: dpkg
- Introduced through: dpkg@1.21.22
- Fixed in: 1.21.23
Detailed paths
-
Introduced through: golang@1.20 › dpkg@1.21.22
NVD Description
Note: Versions mentioned in the description apply only to the upstream dpkg package and not the dpkg package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
It was discovered that dpkg-deb (a component of dpkg, the Debian package management system) does not properly validate the end of the data stream when uncompressing a zstd-compressed .deb archive, which may result in denial of service (infinite loop spinning the CPU).
Remediation
Upgrade Debian:12 dpkg to version 1.21.23 or higher.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1
Detailed paths
-
Introduced through: golang@1.20 › 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 in Expat before 2.7.2 allows attackers to trigger large dynamic memory allocations via a small document that is submitted for parsing.
Remediation
There is no fixed version for Debian:12 expat.
References
- https://security-tracker.debian.org/tracker/CVE-2025-59375
- https://github.com/libexpat/libexpat/blob/676a4c531ec768732fac215da9730b5f50fbd2bf/expat/Changes#L45-L74
- https://github.com/libexpat/libexpat/blob/R_2_7_2/expat/Changes
- https://github.com/libexpat/libexpat/issues/1018
- https://github.com/libexpat/libexpat/pull/1034
- https://issues.oss-fuzz.com/issues/439133977
- http://www.openwall.com/lists/oss-security/2025/09/16/2
- http://www.openwall.com/lists/oss-security/2026/05/01/5
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-089022.html
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1
- Fixed in: 2.5.0-1+deb12u2
Detailed paths
-
Introduced through: golang@1.20 › 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.
An issue was discovered in libexpat before 2.6.4. There is a crash within the XML_ResumeParser function because XML_StopParser can stop/suspend an unstarted parser.
Remediation
Upgrade Debian:12 expat to version 2.5.0-1+deb12u2 or higher.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1
Detailed paths
-
Introduced through: golang@1.20 › 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 before 2.8.0 uses insufficient entropy, and thus hash flooding can occur via a crafted XML document.
Remediation
There is no fixed version for Debian:12 expat.
References
- https://security-tracker.debian.org/tracker/CVE-2026-41080
- https://github.com/libexpat/libexpat/issues/47
- https://github.com/libexpat/libexpat/pull/1183
- http://www.openwall.com/lists/oss-security/2026/04/26/1
- https://blog.hartwork.org/posts/expat-2-8-0-released/
- https://www.openwall.com/lists/oss-security/2026/04/26/1
low severity
- Vulnerable module: git
- Introduced through: git@1:2.39.2-1.1 and git/git-man@1:2.39.2-1.1
- Fixed in: 1:2.39.5-0+deb12u3
Detailed paths
-
Introduced through: golang@1.20 › git@1:2.39.2-1.1
-
Introduced through: golang@1.20 › 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 GUI allows you to use the Git source control management tools via a GUI. When a user clones an untrusted repository and is tricked into editing a file located in a maliciously named directory in the repository, then Git GUI can create and overwrite files for which the user has write permission. This vulnerability is fixed in 2.43.7, 2.44.4, 2.45.4, 2.46.4, 2.47.3, 2.48.2, 2.49.1, and 2.50.1.
Remediation
Upgrade Debian:12 git to version 1:2.39.5-0+deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-46835
- https://github.com/j6t/git-gui/compare/dcda716dbc9c90bcac4611bd1076747671ee0906..a437f5bc93330a70b42a230e52f3bd036ca1b1da
- https://github.com/j6t/git-gui/security/advisories/GHSA-xfx7-68v4-v8fg
- https://lists.debian.org/debian-lts-announce/2025/10/msg00003.html
- http://www.openwall.com/lists/oss-security/2025/07/08/4
low severity
- Vulnerable module: git
- Introduced through: git@1:2.39.2-1.1 and git/git-man@1:2.39.2-1.1
- Fixed in: 1:2.39.5-0+deb12u3
Detailed paths
-
Introduced through: golang@1.20 › git@1:2.39.2-1.1
-
Introduced through: golang@1.20 › 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 fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals. When cloning a repository Git knows to optionally fetch a bundle advertised by the remote server, which allows the server-side to offload parts of the clone to a CDN. The Git client does not perform sufficient validation of the advertised bundles, which allows the remote side to perform protocol injection. This protocol injection can cause the client to write the fetched bundle to a location controlled by the adversary. The fetched content is fully controlled by the server, which can in the worst case lead to arbitrary code execution. The use of bundle URIs is not enabled by default and can be controlled by the bundle.heuristic config option. Some cases of the vulnerability require that the adversary is in control of where a repository will be cloned to. This either requires social engineering or a recursive clone with submodules. These cases can thus be avoided by disabling recursive clones. This vulnerability is fixed in v2.43.7, v2.44.4, v2.45.4, v2.46.4, v2.47.3, v2.48.2, v2.49.1, and v2.50.1.
Remediation
Upgrade Debian:12 git to version 1:2.39.5-0+deb12u3 or higher.
References
low severity
- Vulnerable module: git
- Introduced through: git@1:2.39.2-1.1 and git/git-man@1:2.39.2-1.1
- Fixed in: 1:2.39.5-0+deb12u3
Detailed paths
-
Introduced through: golang@1.20 › git@1:2.39.2-1.1
-
Introduced through: golang@1.20 › 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 fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals. When reading a config value, Git strips any trailing carriage return and line feed (CRLF). When writing a config entry, values with a trailing CR are not quoted, causing the CR to be lost when the config is later read. When initializing a submodule, if the submodule path contains a trailing CR, the altered path is read resulting in the submodule being checked out to an incorrect location. If a symlink exists that points the altered path to the submodule hooks directory, and the submodule contains an executable post-checkout hook, the script may be unintentionally executed after checkout. This vulnerability is fixed in v2.43.7, v2.44.4, v2.45.4, v2.46.4, v2.47.3, v2.48.2, v2.49.1, and v2.50.1.
Remediation
Upgrade Debian:12 git to version 1:2.39.5-0+deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-48384
- https://github.com/git/git/security/advisories/GHSA-vwqx-4fm8-6qc9
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-48384
- http://seclists.org/fulldisclosure/2025/Sep/60
- https://lists.debian.org/debian-lts-announce/2025/10/msg00003.html
- http://www.openwall.com/lists/oss-security/2025/07/08/4
- https://github.com/liamg/CVE-2025-48384
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog
low severity
- Vulnerable module: git
- Introduced through: git@1:2.39.2-1.1 and git/git-man@1:2.39.2-1.1
- Fixed in: 1:2.39.5-0+deb12u3
Detailed paths
-
Introduced through: golang@1.20 › git@1:2.39.2-1.1
-
Introduced through: golang@1.20 › 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.
Gitk is a Tcl/Tk based Git history browser. Starting with 1.7.0, when a user clones an untrusted repository and runs gitk without additional command arguments, files for which the user has write permission can be created and truncated. The option Support per-file encoding must have been enabled before in Gitk's Preferences. This option is disabled by default. The same happens when Show origin of this line is used in the main window (regardless of whether Support per-file encoding is enabled or not). This vulnerability is fixed in 2.43.7, 2.44.4, 2.45.4, 2.46.4, 2.47.3, 2.48.2, 2.49.1, and 2.50.1.
Remediation
Upgrade Debian:12 git to version 1:2.39.5-0+deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-27613
- https://github.com/j6t/gitk/compare/465f03869ae11acd04abfa1b83c67879c867410c..026c397d911cde55924d7eb1311d0fd6e2e105d5
- https://github.com/j6t/gitk/compare/7dd272eca153058da2e8d5b9960bbbf0b4f0cbaa..67a128b91e25978a15f9f7e194d81b441d603652
- https://github.com/j6t/gitk/security/advisories/GHSA-f3cw-xrj3-wr2v
- https://lists.debian.org/debian-lts-announce/2025/10/msg00003.html
- http://www.openwall.com/lists/oss-security/2025/07/08/4
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u4, glibc/libc-dev-bin@2.36-9+deb12u4 and others
- Fixed in: 2.36-9+deb12u6
Detailed paths
-
Introduced through: golang@1.20 › glibc/libc-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc-dev-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6-dev@2.36-9+deb12u4
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
Upgrade Debian:12 glibc to version 2.36-9+deb12u6 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-2961
- https://www.ambionics.io/blog/iconv-cve-2024-2961-p1
- https://www.ambionics.io/blog/iconv-cve-2024-2961-p2
- https://www.ambionics.io/blog/iconv-cve-2024-2961-p3
- http://www.openwall.com/lists/oss-security/2024/04/17/9
- http://www.openwall.com/lists/oss-security/2024/04/18/4
- http://www.openwall.com/lists/oss-security/2024/04/24/2
- http://www.openwall.com/lists/oss-security/2024/05/27/1
- http://www.openwall.com/lists/oss-security/2024/05/27/2
- http://www.openwall.com/lists/oss-security/2024/05/27/3
- http://www.openwall.com/lists/oss-security/2024/05/27/4
- http://www.openwall.com/lists/oss-security/2024/05/27/5
- http://www.openwall.com/lists/oss-security/2024/05/27/6
- http://www.openwall.com/lists/oss-security/2024/07/22/5
- https://lists.debian.org/debian-lts-announce/2024/05/msg00001.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BTJFBGHDYG5PEIFD5WSSSKSFZ2AZWC5N/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/P3I4KYS6EU6S7QZ47WFNTPVAHFIUQNEL/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YAMJQI3Y6BHWV3CUTYBXOZONCUJNOB2Z/
- https://security.netapp.com/advisory/ntap-20240531-0002/
- https://sourceware.org/git/?p=glibc.git;a=blob;f=advisories/GLIBC-SA-2024-0004
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://github.com/ambionics/cnext-exploits
- https://github.com/projectdiscovery/nuclei-templates/blob/main/dast/cves/2024/CVE-2024-2961.yaml
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u4, glibc/libc-dev-bin@2.36-9+deb12u4 and others
- Fixed in: 2.36-9+deb12u7
Detailed paths
-
Introduced through: golang@1.20 › glibc/libc-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc-dev-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6-dev@2.36-9+deb12u4
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.
nscd: Stack-based buffer overflow in netgroup cache
If the Name Service Cache Daemon's (nscd) fixed size cache is exhausted by client requests then a subsequent client request for netgroup data may result in a stack-based buffer overflow. This flaw was introduced in glibc 2.15 when the cache was added to nscd.
This vulnerability is only present in the nscd binary.
Remediation
Upgrade Debian:12 glibc to version 2.36-9+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-33599
- http://www.openwall.com/lists/oss-security/2024/07/22/5
- https://lists.debian.org/debian-lts-announce/2024/06/msg00026.html
- https://security.netapp.com/advisory/ntap-20240524-0011/
- https://sourceware.org/git/?p=glibc.git;a=blob;f=advisories/GLIBC-SA-2024-0005
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u4, glibc/libc-dev-bin@2.36-9+deb12u4 and others
- Fixed in: 2.36-9+deb12u7
Detailed paths
-
Introduced through: golang@1.20 › glibc/libc-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc-dev-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6-dev@2.36-9+deb12u4
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.
nscd: Null pointer crashes after notfound response
If the Name Service Cache Daemon's (nscd) cache fails to add a not-found netgroup response to the cache, the client request can result in a null pointer dereference. This flaw was introduced in glibc 2.15 when the cache was added to nscd.
This vulnerability is only present in the nscd binary.
Remediation
Upgrade Debian:12 glibc to version 2.36-9+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-33600
- http://www.openwall.com/lists/oss-security/2024/07/22/5
- https://lists.debian.org/debian-lts-announce/2024/06/msg00026.html
- https://security.netapp.com/advisory/ntap-20240524-0013/
- https://sourceware.org/git/?p=glibc.git;a=blob;f=advisories/GLIBC-SA-2024-0006
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u4, glibc/libc-dev-bin@2.36-9+deb12u4 and others
- Fixed in: 2.36-9+deb12u7
Detailed paths
-
Introduced through: golang@1.20 › glibc/libc-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc-dev-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6-dev@2.36-9+deb12u4
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.
nscd: netgroup cache may terminate daemon on memory allocation failure
The Name Service Cache Daemon's (nscd) netgroup cache uses xmalloc or xrealloc and these functions may terminate the process due to a memory allocation failure resulting in a denial of service to the clients. The flaw was introduced in glibc 2.15 when the cache was added to nscd.
This vulnerability is only present in the nscd binary.
Remediation
Upgrade Debian:12 glibc to version 2.36-9+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-33601
- http://www.openwall.com/lists/oss-security/2024/07/22/5
- https://lists.debian.org/debian-lts-announce/2024/06/msg00026.html
- https://security.netapp.com/advisory/ntap-20240524-0014/
- https://sourceware.org/git/?p=glibc.git;a=blob;f=advisories/GLIBC-SA-2024-0007
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u4, glibc/libc-dev-bin@2.36-9+deb12u4 and others
- Fixed in: 2.36-9+deb12u7
Detailed paths
-
Introduced through: golang@1.20 › glibc/libc-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc-dev-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6-dev@2.36-9+deb12u4
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.
nscd: netgroup cache assumes NSS callback uses in-buffer strings
The Name Service Cache Daemon's (nscd) netgroup cache can corrupt memory when the NSS callback does not store all strings in the provided buffer. The flaw was introduced in glibc 2.15 when the cache was added to nscd.
This vulnerability is only present in the nscd binary.
Remediation
Upgrade Debian:12 glibc to version 2.36-9+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-33602
- http://www.openwall.com/lists/oss-security/2024/07/22/5
- https://lists.debian.org/debian-lts-announce/2024/06/msg00026.html
- https://security.netapp.com/advisory/ntap-20240524-0012/
- https://sourceware.org/git/?p=glibc.git;a=blob;f=advisories/GLIBC-SA-2024-0008
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u4, glibc/libc-dev-bin@2.36-9+deb12u4 and others
- Fixed in: 2.36-9+deb12u10
Detailed paths
-
Introduced through: golang@1.20 › glibc/libc-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc-dev-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6-dev@2.36-9+deb12u4
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.
When the assert() function in the GNU C Library versions 2.13 to 2.40 fails, it does not allocate enough space for the assertion failure message string and size information, which may lead to a buffer overflow if the message string size aligns to page size.
Remediation
Upgrade Debian:12 glibc to version 2.36-9+deb12u10 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-0395
- https://sourceware.org/bugzilla/show_bug.cgi?id=32582
- https://sourceware.org/git/?p=glibc.git;a=blob;f=advisories/GLIBC-SA-2025-0001
- https://sourceware.org/pipermail/libc-announce/2025/000044.html
- https://www.openwall.com/lists/oss-security/2025/01/22/4
- http://www.openwall.com/lists/oss-security/2025/01/22/4
- http://www.openwall.com/lists/oss-security/2025/01/23/2
- https://security.netapp.com/advisory/ntap-20250228-0006/
- http://www.openwall.com/lists/oss-security/2025/04/13/1
- http://www.openwall.com/lists/oss-security/2025/04/24/7
- https://lists.debian.org/debian-lts-announce/2025/04/msg00039.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-577017.html
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u4, glibc/libc-dev-bin@2.36-9+deb12u4 and others
- Fixed in: 2.36-9+deb12u14
Detailed paths
-
Introduced through: golang@1.20 › glibc/libc-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc-dev-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6-dev@2.36-9+deb12u4
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.
Calling wordexp with WRDE_REUSE in conjunction with WRDE_APPEND in the GNU C Library version 2.0 to version 2.42 may cause the interface to return uninitialized memory in the we_wordv member, which on subsequent calls to wordfree may abort the process.
Remediation
Upgrade Debian:12 glibc to version 2.36-9+deb12u14 or higher.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u4, glibc/libc-dev-bin@2.36-9+deb12u4 and others
- Fixed in: 2.36-9+deb12u11
Detailed paths
-
Introduced through: golang@1.20 › glibc/libc-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc-dev-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6-dev@2.36-9+deb12u4
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.
Untrusted LD_LIBRARY_PATH environment variable vulnerability in the GNU C Library version 2.27 to 2.38 allows attacker controlled loading of dynamically shared library in statically compiled setuid binaries that call dlopen (including internal dlopen calls after setlocale or calls to NSS functions such as getaddrinfo).
Remediation
Upgrade Debian:12 glibc to version 2.36-9+deb12u11 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-4802
- https://sourceware.org/bugzilla/show_bug.cgi?id=32976
- https://sourceware.org/cgit/glibc/commit/?id=1e18586c5820e329f741d5c710275e165581380e
- http://www.openwall.com/lists/oss-security/2025/05/16/7
- http://www.openwall.com/lists/oss-security/2025/05/17/2
- https://lists.debian.org/debian-lts-announce/2025/05/msg00033.html
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u4, glibc/libc-dev-bin@2.36-9+deb12u4 and others
- Fixed in: 2.36-9+deb12u13
Detailed paths
-
Introduced through: golang@1.20 › glibc/libc-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc-dev-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6-dev@2.36-9+deb12u4
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 regcomp function in the GNU C library version from 2.4 to 2.41 is subject to a double free if some previous allocation fails. It can be accomplished either by a malloc failure or by using an interposed malloc that injects random malloc failures. The double free can allow buffer manipulation depending of how the regex is constructed. This issue affects all architectures and ABIs supported by the GNU C library.
Remediation
Upgrade Debian:12 glibc to version 2.36-9+deb12u13 or higher.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u4, glibc/libc-dev-bin@2.36-9+deb12u4 and others
- Fixed in: 2.36-9+deb12u14
Detailed paths
-
Introduced through: golang@1.20 › glibc/libc-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc-dev-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6-dev@2.36-9+deb12u4
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.
Passing too large an alignment to the memalign suite of functions (memalign, posix_memalign, aligned_alloc) in the GNU C Library version 2.30 to 2.42 may result in an integer overflow, which could consequently result in a heap corruption.
Note that the attacker must have control over both, the size as well as the alignment arguments of the memalign function to be able to exploit this. The size parameter must be close enough to PTRDIFF_MAX so as to overflow size_t along with the large alignment argument. This limits the malicious inputs for the alignment for memalign to the range [1<<62+ 1, 1<<63] and exactly 1<<63 for posix_memalign and aligned_alloc.
Typically the alignment argument passed to such functions is a known constrained quantity (e.g. page size, block size, struct sizes) and is not attacker controlled, because of which this may not be easily exploitable in practice. An application bug could potentially result in the input alignment being too large, e.g. due to a different buffer overflow or integer overflow in the application or its dependent libraries, but that is again an uncommon usage pattern given typical sources of alignments.
Remediation
Upgrade Debian:12 glibc to version 2.36-9+deb12u14 or higher.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u4, glibc/libc-dev-bin@2.36-9+deb12u4 and others
- Fixed in: 2.36-9+deb12u14
Detailed paths
-
Introduced through: golang@1.20 › glibc/libc-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc-dev-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6-dev@2.36-9+deb12u4
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.
Calling getnetbyaddr or getnetbyaddr_r with a configured nsswitch.conf that specifies the library's DNS backend for networks and queries for a zero-valued network in the GNU C Library version 2.0 to version 2.42 can leak stack contents to the configured DNS resolver.
Remediation
Upgrade Debian:12 glibc to version 2.36-9+deb12u14 or higher.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u4, glibc/libc-dev-bin@2.36-9+deb12u4 and others
- Fixed in: 2.36-9+deb12u14
Detailed paths
-
Introduced through: golang@1.20 › glibc/libc-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc-dev-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6-dev@2.36-9+deb12u4
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.43 and earlier may crash due to an assertion failure when converting inputs from the IBM1390 or IBM1399 character sets, which may be used to remotely crash an application.
This vulnerability can be trivially mitigated by removing the IBM1390 and IBM1399 character sets from systems that do not need them.
Remediation
Upgrade Debian:12 glibc to version 2.36-9+deb12u14 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-4046
- https://sourceware.org/bugzilla/show_bug.cgi?id=33980
- https://sourceware.org/git/?p=glibc.git;a=blob_plain;f=advisories/GLIBC-SA-2026-0007;hb=HEAD
- https://inbox.sourceware.org/libc-announce/76814edf-cf7f-47ec-979d-2dce0a2c76bf@gotplt.org/T/#u
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u4, glibc/libc-dev-bin@2.36-9+deb12u4 and others
- Fixed in: 2.36-9+deb12u14
Detailed paths
-
Introduced through: golang@1.20 › glibc/libc-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc-dev-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6-dev@2.36-9+deb12u4
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.
Calling gethostbyaddr or gethostbyaddr_r with a configured nsswitch.conf that specifies the library's DNS backend in the GNU C Library version 2.34 to version 2.43 could, with a crafted response from the configured DNS server, result in a violation of the DNS specification that causes the application to treat a non-answer section of the DNS response as a valid answer.
Remediation
Upgrade Debian:12 glibc to version 2.36-9+deb12u14 or higher.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u4, glibc/libc-dev-bin@2.36-9+deb12u4 and others
- Fixed in: 2.36-9+deb12u14
Detailed paths
-
Introduced through: golang@1.20 › glibc/libc-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc-dev-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6-dev@2.36-9+deb12u4
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.
Calling gethostbyaddr or gethostbyaddr_r with a configured nsswitch.conf that specifies the library's DNS backend in the GNU C library version 2.34 to version 2.43 could result in an invalid DNS hostname being returned to the caller in violation of the DNS specification.
Remediation
Upgrade Debian:12 glibc to version 2.36-9+deb12u14 or higher.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u4, glibc/libc-dev-bin@2.36-9+deb12u4 and others
Detailed paths
-
Introduced through: golang@1.20 › glibc/libc-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc-dev-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6-dev@2.36-9+deb12u4
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 deprecated functions ns_printrrf, ns_printrr and fp_nquery in the GNU C Library version 2.2 and newer fail to enforce the caller-supplied buffer length, and can result in an out-of-bounds write when printing TSIG records.
Remediation
There is no fixed version for Debian:12 glibc.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u4, glibc/libc-dev-bin@2.36-9+deb12u4 and others
Detailed paths
-
Introduced through: golang@1.20 › glibc/libc-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc-dev-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6-dev@2.36-9+deb12u4
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.
Calling the ungetwc function on a FILE stream with wide characters encoded in a character set that has overlaps between its single byte and multi-byte character encodings, in the GNU C Library version 2.43 or earlier, may result in an attempt to read bytes before an allocated buffer, potentially resulting in unintentional disclosure of neighboring data in the heap, or a program crash.
A bug in the wide character pushback implementation (_IO_wdefault_pbackfail in libio/wgenops.c) causes ungetwc() to operate on the regular character buffer (fp->_IO_read_ptr) instead of the actual wide-stream read pointer (fp->_wide_data->_IO_read_ptr). The program crash may happen in cases where fp->_IO_read_ptr is not initialized and hence points to NULL. The buffer under-read requires a special situation where the input character encoding is such that there are overlaps between single byte representations and multibyte representations in that encoding, resulting in spurious matches. The spurious match case is not possible in the standard Unicode character sets.
Remediation
There is no fixed version for Debian:12 glibc.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u4, glibc/libc-dev-bin@2.36-9+deb12u4 and others
Detailed paths
-
Introduced through: golang@1.20 › glibc/libc-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc-dev-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6-dev@2.36-9+deb12u4
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 deprecated functions ns_printrrf, ns_printrr and fp_nquery in the GNU C Library version 2.2 and newer fail to validate the RDATA content against the RDATA length in a DNS response when processing LOC, CERT, TKEY or TSIG records, which may allow an attacker to craft a DNS response, causing a target application to crash or read uninitialized memory.
These functions are for application debugging only and hence not in the path of code executed by the DNS resolver. Further, they have been deprecated since version 2.34 and should not be used by any new applications. Applications should consider porting away from these interfaces since they may be removed in future versions.
Remediation
There is no fixed version for Debian:12 glibc.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u4, glibc/libc-dev-bin@2.36-9+deb12u4 and others
Detailed paths
-
Introduced through: golang@1.20 › glibc/libc-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc-dev-bin@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6@2.36-9+deb12u4
-
Introduced through: golang@1.20 › glibc/libc6-dev@2.36-9+deb12u4
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.
Calling the scanf family of functions with a %mc (malloc'd character match) in the GNU C Library version 2.7 to version 2.43 with a format width specifier with an explicit width greater than 1024 could result in a one byte heap buffer overflow.
Remediation
There is no fixed version for Debian:12 glibc.
References
low severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u1
- Fixed in: 3.7.9-2+deb12u7
Detailed paths
-
Introduced through: golang@1.20 › gnutls28/libgnutls30@3.7.9-2+deb12u1
NVD Description
This vulnerability has not been analyzed by NVD yet.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u7 or higher.
References
low severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u1
- Fixed in: 3.7.9-2+deb12u3
Detailed paths
-
Introduced through: golang@1.20 › gnutls28/libgnutls30@3.7.9-2+deb12u1
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
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-28835
- http://www.openwall.com/lists/oss-security/2024/03/22/1
- http://www.openwall.com/lists/oss-security/2024/03/22/2
- https://security.netapp.com/advisory/ntap-20241122-0009/
- https://lists.debian.org/debian-lts-announce/2024/09/msg00019.html
- https://access.redhat.com/errata/RHSA-2024:1879
- https://access.redhat.com/errata/RHSA-2024:2570
- https://access.redhat.com/errata/RHSA-2024:2889
- https://access.redhat.com/security/cve/CVE-2024-28835
- https://bugzilla.redhat.com/show_bug.cgi?id=2269084
- https://lists.gnupg.org/pipermail/gnutls-help/2024-March/004845.html
low severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u1
- Fixed in: 3.7.9-2+deb12u3
Detailed paths
-
Introduced through: golang@1.20 › gnutls28/libgnutls30@3.7.9-2+deb12u1
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
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-28834
- http://www.openwall.com/lists/oss-security/2024/03/22/1
- http://www.openwall.com/lists/oss-security/2024/03/22/2
- https://people.redhat.com/~hkario/marvin/
- https://security.netapp.com/advisory/ntap-20240524-0004/
- https://lists.debian.org/debian-lts-announce/2024/09/msg00019.html
- https://access.redhat.com/errata/RHSA-2024:1784
- https://access.redhat.com/errata/RHSA-2024:1879
- https://access.redhat.com/errata/RHSA-2024:1997
- https://access.redhat.com/errata/RHSA-2024:2044
- https://access.redhat.com/errata/RHSA-2024:2570
- https://access.redhat.com/errata/RHSA-2024:2889
- https://access.redhat.com/security/cve/CVE-2024-28834
- https://bugzilla.redhat.com/show_bug.cgi?id=2269228
- https://lists.gnupg.org/pipermail/gnutls-help/2024-March/004845.html
- https://minerva.crocs.fi.muni.cz/
low severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u1, krb5/libk5crypto3@1.20.1-2+deb12u1 and others
Detailed paths
-
Introduced through: golang@1.20 › krb5/libgssapi-krb5-2@1.20.1-2+deb12u1
-
Introduced through: golang@1.20 › krb5/libk5crypto3@1.20.1-2+deb12u1
-
Introduced through: golang@1.20 › krb5/libkrb5-3@1.20.1-2+deb12u1
-
Introduced through: golang@1.20 › krb5/libkrb5support0@1.20.1-2+deb12u1
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
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u1, krb5/libk5crypto3@1.20.1-2+deb12u1 and others
- Fixed in: 1.20.1-2+deb12u3
Detailed paths
-
Introduced through: golang@1.20 › krb5/libgssapi-krb5-2@1.20.1-2+deb12u1
-
Introduced through: golang@1.20 › krb5/libk5crypto3@1.20.1-2+deb12u1
-
Introduced through: golang@1.20 › krb5/libkrb5-3@1.20.1-2+deb12u1
-
Introduced through: golang@1.20 › krb5/libkrb5support0@1.20.1-2+deb12u1
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.
In MIT Kerberos 5 (aka krb5) before 1.22 (with incremental propagation), there is an integer overflow for a large update size to resize() in kdb_log.c. An authenticated attacker can cause an out-of-bounds write and kadmind daemon crash.
Remediation
Upgrade Debian:12 krb5 to version 1.20.1-2+deb12u3 or higher.
References
low severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u1, krb5/libk5crypto3@1.20.1-2+deb12u1 and others
- Fixed in: 1.20.1-2+deb12u5
Detailed paths
-
Introduced through: golang@1.20 › krb5/libgssapi-krb5-2@1.20.1-2+deb12u1
-
Introduced through: golang@1.20 › krb5/libk5crypto3@1.20.1-2+deb12u1
-
Introduced through: golang@1.20 › krb5/libkrb5-3@1.20.1-2+deb12u1
-
Introduced through: golang@1.20 › krb5/libkrb5support0@1.20.1-2+deb12u1
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.
In MIT Kerberos 5 (aka krb5) before 1.22.3, there is an integer underflow and resultant out-of-bounds read if an application calls gss_accept_sec_context() on a system with a NegoEx mechanism registered in /etc/gss/mech. An unauthenticated remote attacker can trigger this, possibly causing the process to terminate in parse_message.
Remediation
Upgrade Debian:12 krb5 to version 1.20.1-2+deb12u5 or higher.
References
low severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u1, krb5/libk5crypto3@1.20.1-2+deb12u1 and others
Detailed paths
-
Introduced through: golang@1.20 › krb5/libgssapi-krb5-2@1.20.1-2+deb12u1
-
Introduced through: golang@1.20 › krb5/libk5crypto3@1.20.1-2+deb12u1
-
Introduced through: golang@1.20 › krb5/libkrb5-3@1.20.1-2+deb12u1
-
Introduced through: golang@1.20 › krb5/libkrb5support0@1.20.1-2+deb12u1
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
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u1, krb5/libk5crypto3@1.20.1-2+deb12u1 and others
- Fixed in: 1.20.1-2+deb12u5
Detailed paths
-
Introduced through: golang@1.20 › krb5/libgssapi-krb5-2@1.20.1-2+deb12u1
-
Introduced through: golang@1.20 › krb5/libk5crypto3@1.20.1-2+deb12u1
-
Introduced through: golang@1.20 › krb5/libkrb5-3@1.20.1-2+deb12u1
-
Introduced through: golang@1.20 › krb5/libkrb5support0@1.20.1-2+deb12u1
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.
In MIT Kerberos 5 (aka krb5) before 1.22.3, there is a NULL pointer dereference if an application calls gss_accept_sec_context() on a system with a NegoEx mechanism registered in /etc/gss/mech. An unauthenticated remote attacker can trigger this, causing the process to terminate in parse_nego_message.
Remediation
Upgrade Debian:12 krb5 to version 1.20.1-2+deb12u5 or higher.
References
low severity
- Vulnerable module: libcap2
- Introduced through: libcap2@1:2.66-4
- Fixed in: 1:2.66-4+deb12u1
Detailed paths
-
Introduced through: golang@1.20 › libcap2@1:2.66-4
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.
The PAM module pam_cap.so of libcap configuration supports group names starting with “@”, during actual parsing, configurations not starting with “@” are incorrectly recognized as group names. This may result in nonintended users being granted an inherited capability set, potentially leading to security risks. Attackers can exploit this vulnerability to achieve local privilege escalation on systems where /etc/security/capability.conf is used to configure user inherited privileges by constructing specific usernames.
Remediation
Upgrade Debian:12 libcap2 to version 1:2.66-4+deb12u1 or higher.
References
low severity
- Vulnerable module: libgcrypt20
- Introduced through: libgcrypt20@1.10.1-3
Detailed paths
-
Introduced through: golang@1.20 › 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
- https://security-tracker.debian.org/tracker/CVE-2024-2236
- https://access.redhat.com/errata/RHSA-2024:9404
- https://bugzilla.redhat.com/show_bug.cgi?id=2268268
- https://access.redhat.com/errata/RHSA-2025:3534
- https://access.redhat.com/errata/RHSA-2025:3530
- https://access.redhat.com/security/cve/CVE-2024-2236
- https://bugzilla.redhat.com/show_bug.cgi?id=2245218
low severity
- Vulnerable module: libgcrypt20
- Introduced through: libgcrypt20@1.10.1-3
- Fixed in: 1.10.1-3+deb12u1
Detailed paths
-
Introduced through: golang@1.20 › 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.
Libgcrypt before 1.12.2 sometimes allows a heap-based buffer overflow and denial of service via crafted ECDH ciphertext to gcry_pk_decrypt.
Remediation
Upgrade Debian:12 libgcrypt20 to version 1.10.1-3+deb12u1 or higher.
References
low severity
- Vulnerable module: libtasn1-6
- Introduced through: libtasn1-6@4.19.0-2
Detailed paths
-
Introduced through: golang@1.20 › libtasn1-6@4.19.0-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libtasn1-6 package and not the libtasn1-6 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
Stack-based buffer overflow in libtasn1 version: v4.20.0. The function fails to validate the size of input data resulting in a buffer overflow in asn1_expend_octet_string.
Remediation
There is no fixed version for Debian:12 libtasn1-6.
References
low severity
- Vulnerable module: nghttp2/libnghttp2-14
- Introduced through: nghttp2/libnghttp2-14@1.52.0-1+deb12u1
- Fixed in: 1.52.0-1+deb12u2
Detailed paths
-
Introduced through: golang@1.20 › nghttp2/libnghttp2-14@1.52.0-1+deb12u1
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
Upgrade Debian:12 nghttp2 to version 1.52.0-1+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-28182
- https://lists.debian.org/debian-lts-announce/2024/09/msg00041.html
- http://www.openwall.com/lists/oss-security/2024/04/03/16
- https://github.com/nghttp2/nghttp2/commit/00201ecd8f982da3b67d4f6868af72a1b03b14e0
- https://github.com/nghttp2/nghttp2/commit/d71a4668c6bead55805d18810d633fbb98315af9
- https://github.com/nghttp2/nghttp2/security/advisories/GHSA-x6x3-gv8h-m57q
- https://lists.debian.org/debian-lts-announce/2024/04/msg00026.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/AGOME6ZXJG7664IPQNVE3DL67E3YP3HY/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/J6ZMXUGB66VAXDW5J6QSTHM5ET25FGSA/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PXJO2EASHM2OQQLGVDY5ZSO7UVDVHTDK/
- https://www.kb.cert.org/vuls/id/421644
low severity
- Vulnerable module: nghttp2/libnghttp2-14
- Introduced through: nghttp2/libnghttp2-14@1.52.0-1+deb12u1
- Fixed in: 1.52.0-1+deb12u3
Detailed paths
-
Introduced through: golang@1.20 › nghttp2/libnghttp2-14@1.52.0-1+deb12u1
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. Prior to version 1.68.1, the nghttp2 library stops reading the incoming data when user facing public API nghttp2_session_terminate_session or nghttp2_session_terminate_session2 is called by the application. They might be called internally by the library when it detects the situation that is subject to connection error. Due to the missing internal state validation, the library keeps reading the rest of the data after one of those APIs is called. Then receiving a malformed frame that causes FRAME_SIZE_ERROR causes assertion failure. nghttp2 v1.68.1 adds missing state validation to avoid assertion failure. No known workarounds are available.
Remediation
Upgrade Debian:12 nghttp2 to version 1.52.0-1+deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-27135
- https://github.com/nghttp2/nghttp2/commit/5c7df8fa815ac1004d9ecb9d1f7595c4d37f46e1
- https://github.com/nghttp2/nghttp2/security/advisories/GHSA-6933-cjhr-5qg6
- http://www.openwall.com/lists/oss-security/2026/03/20/3
- https://lists.debian.org/debian-lts-announce/2026/05/msg00025.html
low severity
- Vulnerable module: openldap/libldap-2.5-0
- Introduced through: openldap/libldap-2.5-0@2.5.13+dfsg-5
Detailed paths
-
Introduced through: golang@1.20 › 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.
OpenLDAP Lightning Memory-Mapped Database (LMDB) versions up to and including 0.9.14, prior to commit 8e1fda8, contain a heap buffer underflow in the readline() function of mdb_load. When processing malformed input containing an embedded NUL byte, an unsigned offset calculation can underflow and cause an out-of-bounds read of one byte before the allocated heap buffer. This can cause mdb_load to crash, leading to a limited denial-of-service condition.
Remediation
There is no fixed version for Debian:12 openldap.
References
- https://security-tracker.debian.org/tracker/CVE-2026-22185
- https://seclists.org/fulldisclosure/2026/Jan/5
- https://seclists.org/fulldisclosure/2026/Jan/8
- https://www.openldap.org/
- https://www.vulncheck.com/advisories/openldap-lmdb-mdb-load-heap-buffer-underflow-in-readline
- https://bugs.openldap.org/show_bug.cgi?id=10421
low severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2+deb12u2
- Fixed in: 1:9.2p1-2+deb12u8
Detailed paths
-
Introduced through: golang@1.20 › openssh/openssh-client@1:9.2p1-2+deb12u2
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 in OpenSSH before 10.1 allows control characters in usernames that originate from certain possibly untrusted sources, potentially leading to code execution when a ProxyCommand is used. The untrusted sources are the command line and %-sequence expansion of a configuration file. (A configuration file that provides a complete literal username is not categorized as an untrusted source.)
Remediation
Upgrade Debian:12 openssh to version 1:9.2p1-2+deb12u8 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-61984
- https://marc.info/?l=openssh-unix-dev&m=175974522032149&w=2
- https://www.openssh.com/releasenotes.html#10.1p1
- https://www.openwall.com/lists/oss-security/2025/10/06/1
- https://dgl.cx/2025/10/bash-a-newline-ssh-proxycommand-cve-2025-61984
- http://www.openwall.com/lists/oss-security/2025/10/07/1
- http://www.openwall.com/lists/oss-security/2025/10/12/1
- https://www.vicarius.io/vsociety/posts/cve-2025-61984-detection-script-remote-code-execution-vulnerability-affecting-openssh
- https://www.vicarius.io/vsociety/posts/cve-2025-61984-mitigation-script-remote-code-execution-vulnerability-affecting-openssh
low severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2+deb12u2
- Fixed in: 1:9.2p1-2+deb12u8
Detailed paths
-
Introduced through: golang@1.20 › openssh/openssh-client@1:9.2p1-2+deb12u2
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 in OpenSSH before 10.1 allows the '\0' character in an ssh:// URI, potentially leading to code execution when a ProxyCommand is used.
Remediation
Upgrade Debian:12 openssh to version 1:9.2p1-2+deb12u8 or higher.
References
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.11-1~deb12u2 and openssl/libssl3@3.0.11-1~deb12u2
- Fixed in: 3.0.13-1~deb12u1
Detailed paths
-
Introduced through: golang@1.20 › openssl@3.0.11-1~deb12u2
-
Introduced through: golang@1.20 › openssl/libssl3@3.0.11-1~deb12u2
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 invalid RSA public keys may take a long time.
Impact summary: Applications that use the function EVP_PKEY_public_check() to check RSA public keys may experience long delays. Where the key that is being checked has been obtained from an untrusted source this may lead to a Denial of Service.
When function EVP_PKEY_public_check() is called on RSA public keys, a computation is done to confirm that the RSA modulus, n, is composite. For valid RSA keys, n is a product of two or more large primes and this computation completes quickly. However, if n is an overly large prime, then this computation would take a long time.
An application that calls EVP_PKEY_public_check() and supplies an RSA key obtained from an untrusted source could be vulnerable to a Denial of Service attack.
The function EVP_PKEY_public_check() is not called from other OpenSSL functions however it is called from the OpenSSL pkey command line application. For that reason that application is also vulnerable if used with the '-pubin' and '-check' options on untrusted data.
The OpenSSL SSL/TLS implementation is not affected by this issue.
The OpenSSL 3.0 and 3.1 FIPS providers are affected by this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.13-1~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-6237
- http://www.openwall.com/lists/oss-security/2024/03/11/1
- https://security.netapp.com/advisory/ntap-20240531-0007/
- https://github.com/openssl/openssl/commit/0b0f7abfb37350794a4b8960fafc292cd5d1b84d
- https://github.com/openssl/openssl/commit/18c02492138d1eb8b6548cb26e7b625fb2414a2a
- https://github.com/openssl/openssl/commit/a830f551557d3d66a84bbb18a5b889c640c36294
- https://www.openssl.org/news/secadv/20240115.txt
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
- https://cert-portal.siemens.com/productcert/html/ssa-331112.html
- https://cert-portal.siemens.com/productcert/html/ssa-769027.html
- https://cert-portal.siemens.com/productcert/html/ssa-915275.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.11-1~deb12u2 and openssl/libssl3@3.0.11-1~deb12u2
- Fixed in: 3.0.16-1~deb12u1
Detailed paths
-
Introduced through: golang@1.20 › openssl@3.0.11-1~deb12u2
-
Introduced through: golang@1.20 › openssl/libssl3@3.0.11-1~deb12u2
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 timing side-channel which could potentially allow recovering the private key exists in the ECDSA signature computation.
Impact summary: A timing side-channel in ECDSA signature computations could allow recovering the private key by an attacker. However, measuring the timing would require either local access to the signing application or a very fast network connection with low latency.
There is a timing signal of around 300 nanoseconds when the top word of the inverted ECDSA nonce value is zero. This can happen with significant probability only for some of the supported elliptic curves. In particular the NIST P-521 curve is affected. To be able to measure this leak, the attacker process must either be located in the same physical computer or must have a very fast network connection with low latency. For that reason the severity of this vulnerability is Low.
The FIPS modules in 3.4, 3.3, 3.2, 3.1 and 3.0 are affected by this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.16-1~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-13176
- https://github.com/openssl/openssl/commit/07272b05b04836a762b4baa874958af51d513844
- https://github.com/openssl/openssl/commit/2af62e74fb59bc469506bc37eb2990ea408d9467
- https://github.com/openssl/openssl/commit/392dcb336405a0c94486aa6655057f59fd3a0902
- https://github.com/openssl/openssl/commit/4b1cb94a734a7d4ec363ac0a215a25c181e11f65
- https://github.com/openssl/openssl/commit/77c608f4c8857e63e98e66444e2e761c9627916f
- https://github.openssl.org/openssl/extended-releases/commit/0d5fd1ab987f7571e2c955d8d8b638fc0fb54ded
- https://github.openssl.org/openssl/extended-releases/commit/a2639000db19878d5d89586ae7b725080592ae86
- https://openssl-library.org/news/secadv/20250120.txt
- http://www.openwall.com/lists/oss-security/2025/01/20/2
- https://security.netapp.com/advisory/ntap-20250124-0005/
- https://security.netapp.com/advisory/ntap-20250418-0010/
- https://lists.debian.org/debian-lts-announce/2025/05/msg00028.html
- https://security.netapp.com/advisory/ntap-20250502-0006/
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.11-1~deb12u2 and openssl/libssl3@3.0.11-1~deb12u2
- Fixed in: 3.0.14-1~deb12u1
Detailed paths
-
Introduced through: golang@1.20 › openssl@3.0.11-1~deb12u2
-
Introduced through: golang@1.20 › openssl/libssl3@3.0.11-1~deb12u2
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
Upgrade Debian:12 openssl to version 3.0.14-1~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-2511
- http://www.openwall.com/lists/oss-security/2024/04/08/5
- https://security.netapp.com/advisory/ntap-20240503-0013/
- https://lists.debian.org/debian-lts-announce/2024/10/msg00033.html
- https://lists.debian.org/debian-lts-announce/2024/11/msg00000.html
- https://github.com/openssl/openssl/commit/7e4d731b1c07201ad9374c1cd9ac5263bdf35bce
- https://github.com/openssl/openssl/commit/b52867a9f618bb955bed2a3ce3db4d4f97ed8e5d
- https://github.com/openssl/openssl/commit/e9d7083e241670332e0443da0f0d4ffb52829f08
- https://github.openssl.org/openssl/extended-releases/commit/5f8d25770ae6437db119dfc951e207271a326640
- https://www.openssl.org/news/secadv/20240408.txt
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
- https://cert-portal.siemens.com/productcert/html/ssa-354112.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-613116.html
- https://cert-portal.siemens.com/productcert/html/ssa-769027.html
- https://cert-portal.siemens.com/productcert/html/ssa-915275.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.11-1~deb12u2 and openssl/libssl3@3.0.11-1~deb12u2
- Fixed in: 3.0.14-1~deb12u1
Detailed paths
-
Introduced through: golang@1.20 › openssl@3.0.11-1~deb12u2
-
Introduced through: golang@1.20 › openssl/libssl3@3.0.11-1~deb12u2
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 DSA keys or parameters may be very slow.
Impact summary: Applications that use the functions EVP_PKEY_param_check() or EVP_PKEY_public_check() to check a DSA public key or DSA parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service.
The functions EVP_PKEY_param_check() or EVP_PKEY_public_check() perform
various checks on DSA parameters. Some of those computations take a long time
if the modulus (p parameter) is too large.
Trying to use a very large modulus is slow and OpenSSL will not allow using public keys with a modulus which is over 10,000 bits in length for signature verification. However the key and parameter check functions do not limit the modulus size when performing the checks.
An application that calls EVP_PKEY_param_check() or EVP_PKEY_public_check() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack.
These functions are not called by OpenSSL itself on untrusted DSA keys so only applications that directly call these functions may be vulnerable.
Also vulnerable are the OpenSSL pkey and pkeyparam command line applications
when using the -check option.
The OpenSSL SSL/TLS implementation is not affected by this issue.
The OpenSSL 3.0 and 3.1 FIPS providers are affected by this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.14-1~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-4603
- http://www.openwall.com/lists/oss-security/2024/05/16/2
- https://security.netapp.com/advisory/ntap-20240621-0001/
- https://github.com/openssl/openssl/commit/3559e868e58005d15c6013a0c1fd832e51c73397
- https://github.com/openssl/openssl/commit/53ea06486d296b890d565fb971b2764fcd826e7e
- https://github.com/openssl/openssl/commit/9c39b3858091c152f52513c066ff2c5a47969f0d
- https://github.com/openssl/openssl/commit/da343d0605c826ef197aceedc67e8e04f065f740
- https://www.openssl.org/news/secadv/20240516.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.11-1~deb12u2 and openssl/libssl3@3.0.11-1~deb12u2
- Fixed in: 3.0.14-1~deb12u1
Detailed paths
-
Introduced through: golang@1.20 › openssl@3.0.11-1~deb12u2
-
Introduced through: golang@1.20 › openssl/libssl3@3.0.11-1~deb12u2
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: Calling the OpenSSL API function SSL_free_buffers may cause memory to be accessed that was previously freed in some situations
Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, only applications that directly call the SSL_free_buffers function are affected by this issue. Applications that do not call this function are not vulnerable. Our investigations indicate that this function is rarely used by applications.
The SSL_free_buffers function is used to free the internal OpenSSL buffer used when processing an incoming record from the network. The call is only expected to succeed if the buffer is not currently in use. However, two scenarios have been identified where the buffer is freed even when still in use.
The first scenario occurs where a record header has been received from the network and processed by OpenSSL, but the full record body has not yet arrived. In this case calling SSL_free_buffers will succeed even though a record has only been partially processed and the buffer is still in use.
The second scenario occurs where a full record containing application data has been received and processed by OpenSSL but the application has only read part of this data. Again a call to SSL_free_buffers will succeed even though the buffer is still in use.
While these scenarios could occur accidentally during normal operation a malicious attacker could attempt to engineer a stituation where this occurs. We are not aware of this issue being actively exploited.
The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.14-1~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-4741
- https://github.com/openssl/openssl/commit/704f725b96aa373ee45ecfb23f6abfe8be8d9177
- https://github.com/openssl/openssl/commit/b3f0eb0a295f58f16ba43ba99dad70d4ee5c437d
- https://github.com/openssl/openssl/commit/c88c3de51020c37e8706bf7a682a162593053aac
- https://github.com/openssl/openssl/commit/e5093133c35ca82874ad83697af76f4b0f7e3bd8
- https://github.openssl.org/openssl/extended-releases/commit/f7a045f3143fc6da2ee66bf52d8df04829590dd4
- https://www.openssl.org/news/secadv/20240528.txt
- https://lists.debian.org/debian-lts-announce/2024/10/msg00033.html
- https://lists.debian.org/debian-lts-announce/2024/11/msg00000.html
- https://security.netapp.com/advisory/ntap-20240621-0004/
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.11-1~deb12u2 and openssl/libssl3@3.0.11-1~deb12u2
- Fixed in: 3.0.15-1~deb12u1
Detailed paths
-
Introduced through: golang@1.20 › openssl@3.0.11-1~deb12u2
-
Introduced through: golang@1.20 › openssl/libssl3@3.0.11-1~deb12u2
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: Calling the OpenSSL API function SSL_select_next_proto with an empty supported client protocols buffer may cause a crash or memory contents to be sent to the peer.
Impact summary: A buffer overread can have a range of potential consequences such as unexpected application beahviour or a crash. In particular this issue could result in up to 255 bytes of arbitrary private data from memory being sent to the peer leading to a loss of confidentiality. However, only applications that directly call the SSL_select_next_proto function with a 0 length list of supported client protocols are affected by this issue. This would normally never be a valid scenario and is typically not under attacker control but may occur by accident in the case of a configuration or programming error in the calling application.
The OpenSSL API function SSL_select_next_proto is typically used by TLS applications that support ALPN (Application Layer Protocol Negotiation) or NPN (Next Protocol Negotiation). NPN is older, was never standardised and is deprecated in favour of ALPN. We believe that ALPN is significantly more widely deployed than NPN. The SSL_select_next_proto function accepts a list of protocols from the server and a list of protocols from the client and returns the first protocol that appears in the server list that also appears in the client list. In the case of no overlap between the two lists it returns the first item in the client list. In either case it will signal whether an overlap between the two lists was found. In the case where SSL_select_next_proto is called with a zero length client list it fails to notice this condition and returns the memory immediately following the client list pointer (and reports that there was no overlap in the lists).
This function is typically called from a server side application callback for ALPN or a client side application callback for NPN. In the case of ALPN the list of protocols supplied by the client is guaranteed by libssl to never be zero in length. The list of server protocols comes from the application and should never normally be expected to be of zero length. In this case if the SSL_select_next_proto function has been called as expected (with the list supplied by the client passed in the client/client_len parameters), then the application will not be vulnerable to this issue. If the application has accidentally been configured with a zero length server list, and has accidentally passed that zero length server list in the client/client_len parameters, and has additionally failed to correctly handle a "no overlap" response (which would normally result in a handshake failure in ALPN) then it will be vulnerable to this problem.
In the case of NPN, the protocol permits the client to opportunistically select a protocol when there is no overlap. OpenSSL returns the first client protocol in the no overlap case in support of this. The list of client protocols comes from the application and should never normally be expected to be of zero length. However if the SSL_select_next_proto function is accidentally called with a client_len of 0 then an invalid memory pointer will be returned instead. If the application uses this output as the opportunistic protocol then the loss of confidentiality will occur.
This issue has been assessed as Low severity because applications are most likely to be vulnerable if they are using NPN instead of ALPN - but NPN is not widely used. It also requires an application configuration or programming error. Finally, this issue would not typically be under attacker control making active exploitation unlikely.
The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.
Due to the low severity of this issue we are not issuing new releases of OpenSSL at this time. The fix will be included in the next releases when they become available.
Remediation
Upgrade Debian:12 openssl to version 3.0.15-1~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-5535
- http://www.openwall.com/lists/oss-security/2024/08/15/1
- http://www.openwall.com/lists/oss-security/2024/06/27/1
- http://www.openwall.com/lists/oss-security/2024/06/28/4
- https://security.netapp.com/advisory/ntap-20240712-0005/
- https://lists.debian.org/debian-lts-announce/2024/10/msg00033.html
- https://lists.debian.org/debian-lts-announce/2024/11/msg00000.html
- https://security.netapp.com/advisory/ntap-20241025-0006/
- https://security.netapp.com/advisory/ntap-20241025-0010/
- https://github.com/openssl/openssl/commit/4ada436a1946cbb24db5ab4ca082b69c1bc10f37
- https://github.com/openssl/openssl/commit/99fb785a5f85315b95288921a321a935ea29a51e
- https://github.com/openssl/openssl/commit/cf6f91f6121f4db167405db2f0de410a456f260c
- https://github.com/openssl/openssl/commit/e86ac436f0bd54d4517745483e2315650fae7b2c
- https://github.openssl.org/openssl/extended-releases/commit/9947251413065a05189a63c9b7a6c1d4e224c21c
- https://github.openssl.org/openssl/extended-releases/commit/b78ec0824da857223486660177d3b1f255c65d87
- https://www.openssl.org/news/secadv/20240627.txt
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
- https://cert-portal.siemens.com/productcert/html/ssa-277137.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-613116.html
- https://cert-portal.siemens.com/productcert/html/ssa-769027.html
- https://cert-portal.siemens.com/productcert/html/ssa-915275.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.11-1~deb12u2 and openssl/libssl3@3.0.11-1~deb12u2
- Fixed in: 3.0.15-1~deb12u1
Detailed paths
-
Introduced through: golang@1.20 › openssl@3.0.11-1~deb12u2
-
Introduced through: golang@1.20 › openssl/libssl3@3.0.11-1~deb12u2
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: Use of the low-level GF(2^m) elliptic curve APIs with untrusted explicit values for the field polynomial can lead to out-of-bounds memory reads or writes.
Impact summary: Out of bound memory writes can lead to an application crash or even a possibility of a remote code execution, however, in all the protocols involving Elliptic Curve Cryptography that we're aware of, either only "named curves" are supported, or, if explicit curve parameters are supported, they specify an X9.62 encoding of binary (GF(2^m)) curves that can't represent problematic input values. Thus the likelihood of existence of a vulnerable application is low.
In particular, the X9.62 encoding is used for ECC keys in X.509 certificates, so problematic inputs cannot occur in the context of processing X.509 certificates. Any problematic use-cases would have to be using an "exotic" curve encoding.
The affected APIs include: EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(), and various supporting BN_GF2m_*() functions.
Applications working with "exotic" explicit binary (GF(2^m)) curve parameters, that make it possible to represent invalid field polynomials with a zero constant term, via the above or similar APIs, may terminate abruptly as a result of reading or writing outside of array bounds. Remote code execution cannot easily be ruled out.
The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.15-1~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-9143
- https://github.com/openssl/openssl/commit/72ae83ad214d2eef262461365a1975707f862712
- https://github.com/openssl/openssl/commit/bc7e04d7c8d509fb78fc0e285aa948fb0da04700
- https://github.com/openssl/openssl/commit/c0d3e4d32d2805f49bec30547f225bc4d092e1f4
- https://github.com/openssl/openssl/commit/fdf6723362ca51bd883295efe206cb5b1cfa5154
- https://github.openssl.org/openssl/extended-releases/commit/8efc0cbaa8ebba8e116f7b81a876a4123594d86a
- https://github.openssl.org/openssl/extended-releases/commit/9d576994cec2b7aa37a91740ea7e680810957e41
- https://openssl-library.org/news/secadv/20241016.txt
- http://www.openwall.com/lists/oss-security/2024/10/16/1
- http://www.openwall.com/lists/oss-security/2024/10/23/1
- http://www.openwall.com/lists/oss-security/2024/10/24/1
- https://security.netapp.com/advisory/ntap-20241101-0001/
- https://lists.debian.org/debian-lts-announce/2024/10/msg00033.html
- https://lists.debian.org/debian-lts-announce/2024/11/msg00000.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
- https://cert-portal.siemens.com/productcert/html/ssa-277137.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-769027.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.11-1~deb12u2 and openssl/libssl3@3.0.11-1~deb12u2
- Fixed in: 3.0.18-1~deb12u2
Detailed paths
-
Introduced through: golang@1.20 › openssl@3.0.11-1~deb12u2
-
Introduced through: golang@1.20 › openssl/libssl3@3.0.11-1~deb12u2
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: Parsing CMS AuthEnvelopedData or EnvelopedData message with maliciously crafted AEAD parameters can trigger a stack buffer overflow.
Impact summary: A stack buffer overflow may lead to a crash, causing Denial of Service, or potentially remote code execution.
When parsing CMS (Auth)EnvelopedData structures that use AEAD ciphers such as AES-GCM, the IV (Initialization Vector) encoded in the ASN.1 parameters is copied into a fixed-size stack buffer without verifying that its length fits the destination. An attacker can supply a crafted CMS message with an oversized IV, causing a stack-based out-of-bounds write before any authentication or tag verification occurs.
Applications and services that parse untrusted CMS or PKCS#7 content using AEAD ciphers (e.g., S/MIME (Auth)EnvelopedData with AES-GCM) are vulnerable. Because the overflow occurs prior to authentication, no valid key material is required to trigger it. While exploitability to remote code execution depends on platform and toolchain mitigations, the stack-based write primitive represents a severe risk.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the CMS implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3 and 3.0 are vulnerable to this issue.
OpenSSL 1.1.1 and 1.0.2 are not affected by this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.18-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-15467
- https://github.com/openssl/openssl/commit/2c8f0e5fa9b6ee5508a0349e4572ddb74db5a703
- https://github.com/openssl/openssl/commit/5f26d4202f5b89664c5c3f3c62086276026ba9a9
- https://github.com/openssl/openssl/commit/6ced0fe6b10faa560e410e3ee8d6c82f06c65ea3
- https://github.com/openssl/openssl/commit/ce39170276daec87f55c39dad1f629b56344429e
- https://github.com/openssl/openssl/commit/d0071a0799f20cc8101730145349ed4487c268dc
- https://openssl-library.org/news/secadv/20260127.txt
- http://www.openwall.com/lists/oss-security/2026/01/27/10
- http://www.openwall.com/lists/oss-security/2026/02/25/6
- https://github.com/guiimoraes/CVE-2025-15467
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.11-1~deb12u2 and openssl/libssl3@3.0.11-1~deb12u2
Detailed paths
-
Introduced through: golang@1.20 › openssl@3.0.11-1~deb12u2
-
Introduced through: golang@1.20 › openssl/libssl3@3.0.11-1~deb12u2
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 3.0.0 through 3.3.2 on the PowerPC architecture is vulnerable to a Minerva attack, exploitable by measuring the time of signing of random messages using the EVP_DigestSign API, and then using the private key to extract the K value (nonce) from the signatures. Next, based on the bit size of the extracted nonce, one can compare the signing time of full-sized nonces to signatures that used smaller nonces, via statistical tests. There is a side-channel in the P-364 curve that allows private key extraction (also, there is a dependency between the bit size of K and the size of the side channel). NOTE: This CVE is disputed because the OpenSSL security policy explicitly notes that any side channels which require same physical system to be detected are outside of the threat model for the software. The timing signal is so small that it is infeasible to be detected without having the attacking process running on the same physical system.
Remediation
There is no fixed version for Debian:12 openssl.
References
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.11-1~deb12u2 and openssl/libssl3@3.0.11-1~deb12u2
- Fixed in: 3.0.18-1~deb12u2
Detailed paths
-
Introduced through: golang@1.20 › openssl@3.0.11-1~deb12u2
-
Introduced through: golang@1.20 › openssl/libssl3@3.0.11-1~deb12u2
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: Writing large, newline-free data into a BIO chain using the line-buffering filter where the next BIO performs short writes can trigger a heap-based out-of-bounds write.
Impact summary: This out-of-bounds write can cause memory corruption which typically results in a crash, leading to Denial of Service for an application.
The line-buffering BIO filter (BIO_f_linebuffer) is not used by default in TLS/SSL data paths. In OpenSSL command-line applications, it is typically only pushed onto stdout/stderr on VMS systems. Third-party applications that explicitly use this filter with a BIO chain that can short-write and that write large, newline-free data influenced by an attacker would be affected. However, the circumstances where this could happen are unlikely to be under attacker control, and BIO_f_linebuffer is unlikely to be handling non-curated data controlled by an attacker. For that reason the issue was assessed as Low severity.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the BIO implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.18-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-68160
- https://github.com/openssl/openssl/commit/384011202af92605d926fafe4a0bcd6b65d162ad
- https://github.com/openssl/openssl/commit/475c466ef2fbd8fc1df6fae1c3eed9c813fc8ff6
- https://github.com/openssl/openssl/commit/4c96fbba618e1940f038012506ee9e21d32ee12c
- https://github.com/openssl/openssl/commit/6845c3b6460a98b1ec4e463baa2ea1a63a32d7c0
- https://github.com/openssl/openssl/commit/68a7cd2e2816c3a02f4d45a2ce43fc04fac97096
- https://openssl-library.org/news/secadv/20260127.txt
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.11-1~deb12u2 and openssl/libssl3@3.0.11-1~deb12u2
- Fixed in: 3.0.18-1~deb12u2
Detailed paths
-
Introduced through: golang@1.20 › openssl@3.0.11-1~deb12u2
-
Introduced through: golang@1.20 › openssl/libssl3@3.0.11-1~deb12u2
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: When using the low-level OCB API directly with AES-NI or<br>other hardware-accelerated code paths, inputs whose length is not a multiple<br>of 16 bytes can leave the final partial block unencrypted and unauthenticated.<br><br>Impact summary: The trailing 1-15 bytes of a message may be exposed in<br>cleartext on encryption and are not covered by the authentication tag,<br>allowing an attacker to read or tamper with those bytes without detection.<br><br>The low-level OCB encrypt and decrypt routines in the hardware-accelerated<br>stream path process full 16-byte blocks but do not advance the input/output<br>pointers. The subsequent tail-handling code then operates on the original<br>base pointers, effectively reprocessing the beginning of the buffer while<br>leaving the actual trailing bytes unprocessed. The authentication checksum<br>also excludes the true tail bytes.<br><br>However, typical OpenSSL consumers using EVP are not affected because the<br>higher-level EVP and provider OCB implementations split inputs so that full<br>blocks and trailing partial blocks are processed in separate calls, avoiding<br>the problematic code path. Additionally, TLS does not use OCB ciphersuites.<br>The vulnerability only affects applications that call the low-level<br>CRYPTO_ocb128_encrypt() or CRYPTO_ocb128_decrypt() functions directly with<br>non-block-aligned lengths in a single call on hardware-accelerated builds.<br>For these reasons the issue was assessed as Low severity.<br><br>The FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected<br>by this issue, as OCB mode is not a FIPS-approved algorithm.<br><br>OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.<br><br>OpenSSL 1.0.2 is not affected by this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.18-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-69418
- https://github.com/openssl/openssl/commit/372fc5c77529695b05b4f5b5187691a57ef5dffc
- https://github.com/openssl/openssl/commit/4016975d4469cd6b94927c607f7c511385f928d8
- https://github.com/openssl/openssl/commit/52d23c86a54adab5ee9f80e48b242b52c4cc2347
- https://github.com/openssl/openssl/commit/a7589230356d908c0eca4b969ec4f62106f4f5ae
- https://github.com/openssl/openssl/commit/ed40856d7d4ba6cb42779b6770666a65f19cb977
- https://openssl-library.org/news/secadv/20260127.txt
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.11-1~deb12u2 and openssl/libssl3@3.0.11-1~deb12u2
- Fixed in: 3.0.18-1~deb12u2
Detailed paths
-
Introduced through: golang@1.20 › openssl@3.0.11-1~deb12u2
-
Introduced through: golang@1.20 › openssl/libssl3@3.0.11-1~deb12u2
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: Calling PKCS12_get_friendlyname() function on a maliciously crafted PKCS#12 file with a BMPString (UTF-16BE) friendly name containing non-ASCII BMP code point can trigger a one byte write before the allocated buffer.
Impact summary: The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service.
The OPENSSL_uni2utf8() function performs a two-pass conversion of a PKCS#12 BMPString (UTF-16BE) to UTF-8. In the second pass, when emitting UTF-8 bytes, the helper function bmp_to_utf8() incorrectly forwards the remaining UTF-16 source byte count as the destination buffer capacity to UTF8_putc(). For BMP code points above U+07FF, UTF-8 requires three bytes, but the forwarded capacity can be just two bytes. UTF8_putc() then returns -1, and this negative value is added to the output length without validation, causing the length to become negative. The subsequent trailing NUL byte is then written at a negative offset, causing write outside of heap allocated buffer.
The vulnerability is reachable via the public PKCS12_get_friendlyname() API when parsing attacker-controlled PKCS#12 files. While PKCS12_parse() uses a different code path that avoids this issue, PKCS12_get_friendlyname() directly invokes the vulnerable function. Exploitation requires an attacker to provide a malicious PKCS#12 file to be parsed by the application and the attacker can just trigger a one zero byte write before the allocated buffer. For that reason the issue was assessed as Low severity according to our Security Policy.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#12 implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.
OpenSSL 1.0.2 is not affected by this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.18-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-69419
- https://github.com/openssl/openssl/commit/41be0f216404f14457bbf3b9cc488dba60b49296
- https://github.com/openssl/openssl/commit/7e9cac9832e4705b91987c2474ed06a37a93cecb
- https://github.com/openssl/openssl/commit/a26a90d38edec3748566129d824e664b54bee2e2
- https://github.com/openssl/openssl/commit/cda12de3bc0e333ea8d2c6fd15001dbdaf280015
- https://github.com/openssl/openssl/commit/ff628933755075446bca8307e8417c14d164b535
- https://openssl-library.org/news/secadv/20260127.txt
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.11-1~deb12u2 and openssl/libssl3@3.0.11-1~deb12u2
- Fixed in: 3.0.18-1~deb12u2
Detailed paths
-
Introduced through: golang@1.20 › openssl@3.0.11-1~deb12u2
-
Introduced through: golang@1.20 › openssl/libssl3@3.0.11-1~deb12u2
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 type confusion vulnerability exists in the TimeStamp Response verification code where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing a malformed TimeStamp Response file.
Impact summary: An application calling TS_RESP_verify_response() with a malformed TimeStamp Response can be caused to dereference an invalid or NULL pointer when reading, resulting in a Denial of Service.
The functions ossl_ess_get_signing_cert() and ossl_ess_get_signing_cert_v2() access the signing cert attribute value without validating its type. When the type is not V_ASN1_SEQUENCE, this results in accessing invalid memory through the ASN1_TYPE union, causing a crash.
Exploiting this vulnerability requires an attacker to provide a malformed TimeStamp Response to an application that verifies timestamp responses. The TimeStamp protocol (RFC 3161) is not widely used and the impact of the exploit is just a Denial of Service. For these reasons the issue was assessed as Low severity.
The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the TimeStamp Response implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.
OpenSSL 1.0.2 is not affected by this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.18-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-69420
- https://github.com/openssl/openssl/commit/27c7012c91cc986a598d7540f3079dfde2416eb9
- https://github.com/openssl/openssl/commit/4e254b48ad93cc092be3dd62d97015f33f73133a
- https://github.com/openssl/openssl/commit/564fd9c73787f25693bf9e75faf7bf6bb1305d4e
- https://github.com/openssl/openssl/commit/5eb0770ffcf11b785cf374ff3c19196245e54f1b
- https://github.com/openssl/openssl/commit/a99349ebfc519999edc50620abe24d599b9eb085
- https://openssl-library.org/news/secadv/20260127.txt
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.11-1~deb12u2 and openssl/libssl3@3.0.11-1~deb12u2
- Fixed in: 3.0.17-1~deb12u3
Detailed paths
-
Introduced through: golang@1.20 › openssl@3.0.11-1~deb12u2
-
Introduced through: golang@1.20 › openssl/libssl3@3.0.11-1~deb12u2
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: An application trying to decrypt CMS messages encrypted using password based encryption can trigger an out-of-bounds read and write.
Impact summary: This out-of-bounds read may trigger a crash which leads to Denial of Service for an application. The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service or Execution of attacker-supplied code.
Although the consequences of a successful exploit of this vulnerability could be severe, the probability that the attacker would be able to perform it is low. Besides, password based (PWRI) encryption support in CMS messages is very rarely used. For that reason the issue was assessed as Moderate severity according to our Security Policy.
The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as the CMS implementation is outside the OpenSSL FIPS module boundary.
Remediation
Upgrade Debian:12 openssl to version 3.0.17-1~deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-9230
- https://github.com/openssl/openssl/commit/5965ea5dd6960f36d8b7f74f8eac67a8eb8f2b45
- https://github.com/openssl/openssl/commit/9e91358f365dee6c446dcdcdb01c04d2743fd280
- https://github.com/openssl/openssl/commit/a79c4ce559c6a3a8fd4109e9f33c1185d5bf2def
- https://github.com/openssl/openssl/commit/b5282d677551afda7d20e9c00e09561b547b2dfd
- https://github.com/openssl/openssl/commit/bae259a211ada6315dc50900686daaaaaa55f482
- https://github.openssl.org/openssl/extended-releases/commit/c2b96348bfa662f25f4fabf81958ae822063dae3
- https://github.openssl.org/openssl/extended-releases/commit/dfbaf161d8dafc1132dd88cd48ad990ed9b4c8ba
- https://openssl-library.org/news/secadv/20250930.txt
- https://lists.debian.org/debian-lts-announce/2025/10/msg00001.html
- http://www.openwall.com/lists/oss-security/2025/09/30/5
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-089022.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
- https://cert-portal.siemens.com/productcert/html/ssa-485750.html
- https://cert-portal.siemens.com/productcert/html/ssa-253495.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.11-1~deb12u2 and openssl/libssl3@3.0.11-1~deb12u2
- Fixed in: 3.0.17-1~deb12u3
Detailed paths
-
Introduced through: golang@1.20 › openssl@3.0.11-1~deb12u2
-
Introduced through: golang@1.20 › openssl/libssl3@3.0.11-1~deb12u2
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: An application using the OpenSSL HTTP client API functions may trigger an out-of-bounds read if the 'no_proxy' environment variable is set and the host portion of the authority component of the HTTP URL is an IPv6 address.
Impact summary: An out-of-bounds read can trigger a crash which leads to Denial of Service for an application.
The OpenSSL HTTP client API functions can be used directly by applications but they are also used by the OCSP client functions and CMP (Certificate Management Protocol) client implementation in OpenSSL. However the URLs used by these implementations are unlikely to be controlled by an attacker.
In this vulnerable code the out of bounds read can only trigger a crash. Furthermore the vulnerability requires an attacker-controlled URL to be passed from an application to the OpenSSL function and the user has to have a 'no_proxy' environment variable set. For the aforementioned reasons the issue was assessed as Low severity.
The vulnerable code was introduced in the following patch releases: 3.0.16, 3.1.8, 3.2.4, 3.3.3, 3.4.0 and 3.5.0.
The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as the HTTP client implementation is outside the OpenSSL FIPS module boundary.
Remediation
Upgrade Debian:12 openssl to version 3.0.17-1~deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-9232
- https://github.com/openssl/openssl/commit/2b4ec20e47959170422922eaff25346d362dcb35
- https://github.com/openssl/openssl/commit/654dc11d23468a74fc8ea4672b702dd3feb7be4b
- https://github.com/openssl/openssl/commit/7cf21a30513c9e43c4bc3836c237cf086e194af3
- https://github.com/openssl/openssl/commit/89e790ac431125a4849992858490bed6b225eadf
- https://github.com/openssl/openssl/commit/bbf38c034cdabd0a13330abcc4855c866f53d2e0
- https://openssl-library.org/news/secadv/20250930.txt
- http://www.openwall.com/lists/oss-security/2025/09/30/5
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-089022.html
- https://cert-portal.siemens.com/productcert/html/ssa-485750.html
- https://cert-portal.siemens.com/productcert/html/ssa-253495.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.11-1~deb12u2 and openssl/libssl3@3.0.11-1~deb12u2
- Fixed in: 3.0.18-1~deb12u2
Detailed paths
-
Introduced through: golang@1.20 › openssl@3.0.11-1~deb12u2
-
Introduced through: golang@1.20 › openssl/libssl3@3.0.11-1~deb12u2
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: An invalid or NULL pointer dereference can happen in an application processing a malformed PKCS#12 file.
Impact summary: An application processing a malformed PKCS#12 file can be caused to dereference an invalid or NULL pointer on memory read, resulting in a Denial of Service.
A type confusion vulnerability exists in PKCS#12 parsing code where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid pointer read.
The location is constrained to a 1-byte address space, meaning any attempted pointer manipulation can only target addresses between 0x00 and 0xFF. This range corresponds to the zero page, which is unmapped on most modern operating systems and will reliably result in a crash, leading only to a Denial of Service. Exploiting this issue also requires a user or application to process a maliciously crafted PKCS#12 file. It is uncommon to accept untrusted PKCS#12 files in applications as they are usually used to store private keys which are trusted by definition. For these reasons, the issue was assessed as Low severity.
The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS12 implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.
OpenSSL 1.0.2 is not affected by this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.18-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-22795
- https://github.com/openssl/openssl/commit/2502e7b7d4c0cf4f972a881641fe09edc67aeec4
- https://github.com/openssl/openssl/commit/572844beca95068394c916626a6d3a490f831a49
- https://github.com/openssl/openssl/commit/7bbca05be55b129651d9df4bdb92becc45002c12
- https://github.com/openssl/openssl/commit/eeee3cbd4d682095ed431052f00403004596373e
- https://github.com/openssl/openssl/commit/ef2fb66ec571564d64d1c74a12e388a2a54d05d2
- https://openssl-library.org/news/secadv/20260127.txt
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.11-1~deb12u2 and openssl/libssl3@3.0.11-1~deb12u2
- Fixed in: 3.0.18-1~deb12u2
Detailed paths
-
Introduced through: golang@1.20 › openssl@3.0.11-1~deb12u2
-
Introduced through: golang@1.20 › openssl/libssl3@3.0.11-1~deb12u2
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 type confusion vulnerability exists in the signature verification of signed PKCS#7 data where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing malformed PKCS#7 data.
Impact summary: An application performing signature verification of PKCS#7 data or calling directly the PKCS7_digest_from_attributes() function can be caused to dereference an invalid or NULL pointer when reading, resulting in a Denial of Service.
The function PKCS7_digest_from_attributes() accesses the message digest attribute value without validating its type. When the type is not V_ASN1_OCTET_STRING, this results in accessing invalid memory through the ASN1_TYPE union, causing a crash.
Exploiting this vulnerability requires an attacker to provide a malformed signed PKCS#7 to an application that verifies it. The impact of the exploit is just a Denial of Service, the PKCS7 API is legacy and applications should be using the CMS API instead. For these reasons the issue was assessed as Low severity.
The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#7 parsing implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.18-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-22796
- https://github.com/openssl/openssl/commit/2502e7b7d4c0cf4f972a881641fe09edc67aeec4
- https://github.com/openssl/openssl/commit/572844beca95068394c916626a6d3a490f831a49
- https://github.com/openssl/openssl/commit/7bbca05be55b129651d9df4bdb92becc45002c12
- https://github.com/openssl/openssl/commit/eeee3cbd4d682095ed431052f00403004596373e
- https://github.com/openssl/openssl/commit/ef2fb66ec571564d64d1c74a12e388a2a54d05d2
- https://openssl-library.org/news/secadv/20260127.txt
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.11-1~deb12u2 and openssl/libssl3@3.0.11-1~deb12u2
- Fixed in: 3.0.19-1~deb12u2
Detailed paths
-
Introduced through: golang@1.20 › openssl@3.0.11-1~deb12u2
-
Introduced through: golang@1.20 › openssl/libssl3@3.0.11-1~deb12u2
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: Applications using RSASVE key encapsulation to establish a secret encryption key can send contents of an uninitialized memory buffer to a malicious peer.
Impact summary: The uninitialized buffer might contain sensitive data from the previous execution of the application process which leads to sensitive data leakage to an attacker.
RSA_public_encrypt() returns the number of bytes written on success and -1 on error. The affected code tests only whether the return value is non-zero. As a result, if RSA encryption fails, encapsulation can still return success to the caller, set the output lengths, and leave the caller to use the contents of the ciphertext buffer as if a valid KEM ciphertext had been produced.
If applications use EVP_PKEY_encapsulate() with RSA/RSASVE on an attacker-supplied invalid RSA public key without first validating that key, then this may cause stale or uninitialized contents of the caller-provided ciphertext buffer to be disclosed to the attacker in place of the KEM ciphertext.
As a workaround calling EVP_PKEY_public_check() or EVP_PKEY_public_check_quick() before EVP_PKEY_encapsulate() will mitigate the issue.
The FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.1 and 3.0 are affected by this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.19-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-31790
- https://github.com/openssl/openssl/commit/001e01db3e996e13ffc72386fe79d03a6683b5ac
- https://github.com/openssl/openssl/commit/abd8b2eec7e3f3fda60ecfb68498b246b52af482
- https://github.com/openssl/openssl/commit/b922e24e5b23ffb9cb9e14cadff23d91e9f7e406
- https://github.com/openssl/openssl/commit/d5f8e71cd0a54e961d0c3b174348f8308486f790
- https://github.com/openssl/openssl/commit/eed200f58cd8645ed77e46b7e9f764e284df379e
- https://openssl-library.org/news/secadv/20260407.txt
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
low severity
new
- Vulnerable module: perl
- Introduced through: perl@5.36.0-7+deb12u1, perl/libperl5.36@5.36.0-7+deb12u1 and others
Detailed paths
-
Introduced through: golang@1.20 › perl@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/libperl5.36@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/perl-base@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/perl-modules-5.36@5.36.0-7+deb12u1
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.
IO::Uncompress::Unzip versions before 2.215 for Perl propagate uncaught exception when parsing zip header with malformed DOS date.
_dosToUnixTime() decodes the local-file-header last-modification date field and calls Time::Local::timelocal() without an eval guard. A header whose date field decodes to an out-of-range month, day, or hour causes timelocal() to die.
The exception propagates out of IO::Uncompress::Unzip->new($file) where callers expect undef plus $UnzipError.
Remediation
There is no fixed version for Debian:12 perl.
References
- https://security-tracker.debian.org/tracker/CVE-2025-15649
- https://github.com/pmqs/IO-Compress/commit/fd28c1d2374eee9811f6d0c5bddc0957abdf1da8.patch
- https://github.com/pmqs/IO-Compress/issues/65
- https://metacpan.org/release/PMQS/IO-Compress-2.215/changes
- http://www.openwall.com/lists/oss-security/2026/05/27/1
low severity
- Vulnerable module: perl
- Introduced through: perl@5.36.0-7+deb12u1, perl/libperl5.36@5.36.0-7+deb12u1 and others
- Fixed in: 5.36.0-7+deb12u3
Detailed paths
-
Introduced through: golang@1.20 › perl@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/libperl5.36@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/perl-base@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/perl-modules-5.36@5.36.0-7+deb12u1
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.
Perl threads have a working directory race condition where file operations may target unintended paths.
If a directory handle is open at thread creation, the process-wide current working directory is temporarily changed in order to clone that handle for the new thread, which is visible from any third (or more) thread already running.
This may lead to unintended operations such as loading code or accessing files from unexpected locations, which a local attacker may be able to exploit.
The bug was introduced in commit 11a11ecf4bea72b17d250cfb43c897be1341861e and released in Perl version 5.13.6
Remediation
Upgrade Debian:12 perl to version 5.36.0-7+deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-40909
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098226
- https://github.com/Perl/perl5/commit/11a11ecf4bea72b17d250cfb43c897be1341861e
- https://github.com/Perl/perl5/commit/918bfff86ca8d6d4e4ec5b30994451e0bd74aba9.patch
- https://github.com/Perl/perl5/issues/10387
- https://github.com/Perl/perl5/issues/23010
- https://perldoc.perl.org/5.14.0/perl5136delta#Directory-handles-not-copied-to-threads
- https://www.openwall.com/lists/oss-security/2025/05/22/2
- http://www.openwall.com/lists/oss-security/2025/05/23/1
- http://www.openwall.com/lists/oss-security/2025/05/30/4
- http://www.openwall.com/lists/oss-security/2025/06/02/2
- http://www.openwall.com/lists/oss-security/2025/06/02/5
- http://www.openwall.com/lists/oss-security/2025/06/02/6
- http://www.openwall.com/lists/oss-security/2025/06/02/7
- http://www.openwall.com/lists/oss-security/2025/06/03/1
- http://seclists.org/fulldisclosure/2025/Sep/53
- http://seclists.org/fulldisclosure/2025/Sep/54
- http://seclists.org/fulldisclosure/2025/Sep/55
- https://lists.debian.org/debian-lts-announce/2026/04/msg00018.html
low severity
new
- Vulnerable module: perl
- Introduced through: perl@5.36.0-7+deb12u1, perl/libperl5.36@5.36.0-7+deb12u1 and others
Detailed paths
-
Introduced through: golang@1.20 › perl@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/libperl5.36@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/perl-base@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/perl-modules-5.36@5.36.0-7+deb12u1
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.
IO::Uncompress::Unzip versions before 2.220 for Perl allow CPU exhaustion via per-byte read loop in fastForward.
fastForward() compares length $offset (the digit count of the offset, 1 to 19) against the chunk size $c instead of $offset itself, so $c shrinks from 16 KiB to 1-19 bytes per iteration.
Extracting a named entry from an attacker supplied zip via IO::Uncompress::Unzip->new($zip, Name => $target) drives a per-byte read loop scaling with the entry's compressed size, up to the non-Zip64 4 GiB cap.
Remediation
There is no fixed version for Debian:12 perl.
References
low severity
new
- Vulnerable module: perl
- Introduced through: perl@5.36.0-7+deb12u1, perl/libperl5.36@5.36.0-7+deb12u1 and others
Detailed paths
-
Introduced through: golang@1.20 › perl@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/libperl5.36@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/perl-base@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/perl-modules-5.36@5.36.0-7+deb12u1
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.
IO::Compress versions from 2.207 before 2.220 for Perl ship a zipdetails CLI tool that crashes with undefined subroutine on Info-ZIP Unix Extra Field with 8-byte UID or GID.
When decode_ux() in bin/zipdetails handles an Info-ZIP Unix Extra Field (tag 0x7875) with UID Size or GID Size set to 8, causing zipdetails to decode an 8-byte UID or GID value, it dispatches through decodeLitteEndian(), which calls a misnamed helper unpackValueQ. The actual function defined in the same file is unpackValue_Q (with underscore); the call raises 'Undefined subroutine &main::unpackValueQ' and the script exits with status 255.
Library callers of IO::Compress and IO::Uncompress are not affected; the defect is in the bundled CLI tool.
Remediation
There is no fixed version for Debian:12 perl.
References
low severity
new
- Vulnerable module: perl
- Introduced through: perl@5.36.0-7+deb12u1, perl/libperl5.36@5.36.0-7+deb12u1 and others
Detailed paths
-
Introduced through: golang@1.20 › perl@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/libperl5.36@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/perl-base@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/perl-modules-5.36@5.36.0-7+deb12u1
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.
IO::Compress versions before 2.220 for Perl can execute arbitrary code in File::GlobMapper via an attacker-controlled output glob.
_parseOutputGlob() wraps the caller-supplied output glob string in double quotes and stores it in the parser state; _getFiles() then runs the stored expression through eval STRING. A literal double quote in the output glob closes the dquote wrapper, and the characters that follow are evaluated as Perl.
Arbitrary Perl in the output glob executes at the calling process's privilege.
Remediation
There is no fixed version for Debian:12 perl.
References
low severity
new
- Vulnerable module: perl
- Introduced through: perl@5.36.0-7+deb12u1, perl/libperl5.36@5.36.0-7+deb12u1 and others
Detailed paths
-
Introduced through: golang@1.20 › perl@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/libperl5.36@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/perl-base@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/perl-modules-5.36@5.36.0-7+deb12u1
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 versions before 0.093 for Perl do not validate CRLF in HTTP request lines or control field header values.
The unvalidated inputs are the method and URI in the request line, the URL host that becomes the Host: header, and HTTP/1.1 control data field values.
An attacker who controls one of these inputs, for example a user supplied URL passed to a webhook or URL fetch endpoint, can inject additional headers and smuggle requests to the upstream server.
Remediation
There is no fixed version for Debian:12 perl.
References
low severity
- Vulnerable module: perl
- Introduced through: perl@5.36.0-7+deb12u1, perl/libperl5.36@5.36.0-7+deb12u1 and others
- Fixed in: 5.36.0-7+deb12u2
Detailed paths
-
Introduced through: golang@1.20 › perl@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/libperl5.36@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/perl-base@5.36.0-7+deb12u1
-
Introduced through: golang@1.20 › perl/perl-modules-5.36@5.36.0-7+deb12u1
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 heap buffer overflow vulnerability was discovered in Perl.
Release branches 5.34, 5.36, 5.38 and 5.40 are affected, including development versions from 5.33.1 through 5.41.10.
When there are non-ASCII bytes in the left-hand-side of the tr operator, S_do_trans_invmap can overflow the destination pointer d.
$ perl -e '$_ = "\x{FF}" x 1000000; tr/\xFF/\x{100}/;' Segmentation fault (core dumped)
It is believed that this vulnerability can enable Denial of Service and possibly Code Execution attacks on platforms that lack sufficient defenses.
Remediation
Upgrade Debian:12 perl to version 5.36.0-7+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-56406
- https://github.com/Perl/perl5/commit/87f42aa0e0096e9a346c9672aa3a0bd3bef8c1dd.patch
- https://metacpan.org/release/SHAY/perl-5.38.4/changes
- https://metacpan.org/release/SHAY/perl-5.40.2/changes
- http://www.openwall.com/lists/oss-security/2025/04/13/3
- http://www.openwall.com/lists/oss-security/2025/04/13/4
- http://www.openwall.com/lists/oss-security/2025/04/13/5
low severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u2
Detailed paths
-
Introduced through: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-6597
- https://lists.debian.org/debian-lts-announce/2024/11/msg00005.html
- https://lists.debian.org/debian-lts-announce/2024/12/msg00000.html
- http://www.openwall.com/lists/oss-security/2024/03/20/5
- https://github.com/python/cpython/commit/02a9259c717738dfe6b463c44d7e17f2b6d2cb3a
- https://github.com/python/cpython/commit/5585334d772b253a01a6730e8202ffb1607c3d25
- https://github.com/python/cpython/commit/6ceb8aeda504b079fef7a57b8d81472f15cdd9a5
- https://github.com/python/cpython/commit/81c16cd94ec38d61aa478b9a452436dc3b1b524d
- https://github.com/python/cpython/commit/8eaeefe49d179ca4908d052745e3bb8b6f238f82
- https://github.com/python/cpython/commit/d54e22a669ae6e987199bb5d2c69bb5a46b0083b
- https://github.com/python/cpython/issues/91133
- https://lists.debian.org/debian-lts-announce/2024/03/msg00025.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/T3IGRX54M7RNCQOXVQO5KQKTGWCOABIM/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/U5VHWS52HGD743C47UMCSAK2A773M2YE/
- https://mail.python.org/archives/list/security-announce@python.org/thread/Q5C6ATFC67K53XFV4KE45325S7NS62LD/
low severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u3
Detailed paths
-
Introduced through: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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.
A defect was discovered in the Python “ssl” module where there is a memory race condition with the ssl.SSLContext methods “cert_store_stats()” and “get_ca_certs()”. The race condition can be triggered if the methods are called at the same time as certificates are loaded into the SSLContext, such as during the TLS handshake with a certificate directory configured. This issue is fixed in CPython 3.10.14, 3.11.9, 3.12.3, and 3.13.0a5.
Remediation
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-0397
- https://security.netapp.com/advisory/ntap-20250411-0006/
- https://lists.debian.org/debian-lts-announce/2024/12/msg00000.html
- http://www.openwall.com/lists/oss-security/2024/06/17/2
- https://github.com/python/cpython/commit/01c37f1d0714f5822d34063ca7180b595abf589d
- https://github.com/python/cpython/commit/29c97287d205bf2f410f4895ebce3f43b5160524
- https://github.com/python/cpython/commit/37324b421b72b7bc9934e27aba85d48d4773002e
- https://github.com/python/cpython/commit/542f3272f56f31ed04e74c40635a913fbc12d286
- https://github.com/python/cpython/commit/b228655c227b2ca298a8ffac44d14ce3d22f6faa
- https://github.com/python/cpython/commit/bce693111bff906ccf9281c22371331aaff766ab
- https://github.com/python/cpython/issues/114572
- https://github.com/python/cpython/pull/114573
- https://mail.python.org/archives/list/security-announce@python.org/thread/BMAK5BCGKYWNJOACVUSLUF6SFGBIM4VP/
low severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u2
Detailed paths
-
Introduced through: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-0450
- https://security.netapp.com/advisory/ntap-20250411-0005/
- https://lists.debian.org/debian-lts-announce/2024/11/msg00005.html
- https://lists.debian.org/debian-lts-announce/2024/12/msg00000.html
- http://www.openwall.com/lists/oss-security/2024/03/20/5
- https://github.com/python/cpython/commit/30fe5d853b56138dbec62432d370a1f99409fc85
- https://github.com/python/cpython/commit/66363b9a7b9fe7c99eba3a185b74c5fdbf842eba
- https://github.com/python/cpython/commit/70497218351ba44bffc8b571201ecb5652d84675
- https://github.com/python/cpython/commit/a2c59992e9e8d35baba9695eb186ad6c6ff85c51
- https://github.com/python/cpython/commit/a956e510f6336d5ae111ba429a61c3ade30a7549
- https://github.com/python/cpython/commit/d05bac0b74153beb541b88b4fca33bf053990183
- https://github.com/python/cpython/commit/fa181fcf2156f703347b03a3b1966ce47be8ab3b
- https://github.com/python/cpython/issues/109858
- https://lists.debian.org/debian-lts-announce/2024/03/msg00024.html
- https://lists.debian.org/debian-lts-announce/2024/03/msg00025.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/T3IGRX54M7RNCQOXVQO5KQKTGWCOABIM/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/U5VHWS52HGD743C47UMCSAK2A773M2YE/
- https://mail.python.org/archives/list/security-announce@python.org/thread/XELNUX2L3IOHBTFU7RQHCY6OUVEWZ2FG/
- https://www.bamsoftware.com/hacks/zipbomb/
low severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u5
Detailed paths
-
Introduced through: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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 urllib.parse.urlsplit() and urlparse() functions improperly validated bracketed hosts ([]), allowing hosts that weren't IPv6 or IPvFuture. This behavior was not conformant to RFC 3986 and potentially enabled SSRF if a URL is processed by more than one URL parser.
Remediation
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-11168
- https://github.com/python/cpython/commit/29f348e232e82938ba2165843c448c2b291504c5
- https://github.com/python/cpython/commit/b2171a2fd41416cf68afd67460578631d755a550
- https://github.com/python/cpython/issues/103848
- https://github.com/python/cpython/pull/103849
- https://mail.python.org/archives/list/security-announce@python.org/thread/XPWB6XVZ5G5KGEI63M4AWLIEUF5BPH4T/
- https://github.com/python/cpython/commit/634ded45545ce8cbd6fd5d49785613dd7fa9b89e
- https://github.com/python/cpython/commit/ddca2953191c67a12b1f19d6bca41016c6ae7132
- https://security.netapp.com/advisory/ntap-20250411-0004/
- https://lists.debian.org/debian-lts-announce/2024/12/msg00000.html
low severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u3
Detailed paths
-
Introduced through: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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 “ipaddress” module contained incorrect information about whether certain IPv4 and IPv6 addresses were designated as “globally reachable” or “private”. This affected the is_private and is_global properties of the ipaddress.IPv4Address, ipaddress.IPv4Network, ipaddress.IPv6Address, and ipaddress.IPv6Network classes, where values wouldn’t be returned in accordance with the latest information from the IANA Special-Purpose Address Registries.
CPython 3.12.4 and 3.13.0a6 contain updated information from these registries and thus have the intended behavior.
Remediation
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-4032
- https://lists.debian.org/debian-lts-announce/2024/12/msg00000.html
- http://www.openwall.com/lists/oss-security/2024/06/17/3
- https://github.com/python/cpython/commit/22adf29da8d99933ffed8647d3e0726edd16f7f8
- https://github.com/python/cpython/commit/40d75c2b7f5c67e254d0a025e0f2e2c7ada7f69f
- https://github.com/python/cpython/commit/895f7e2ac23eff4743143beef0f0c5ac71ea27d3
- https://github.com/python/cpython/commit/ba431579efdcbaed7a96f2ac4ea0775879a332fb
- https://github.com/python/cpython/commit/c62c9e518b784fe44432a3f4fc265fb95b651906
- https://github.com/python/cpython/commit/f86b17ac511e68192ba71f27e752321a3252cee3
- https://github.com/python/cpython/issues/113171
- https://github.com/python/cpython/pull/113179
- https://mail.python.org/archives/list/security-announce@python.org/thread/NRUHDUS2IV2USIZM2CVMSFL6SCKU3RZA/
- https://security.netapp.com/advisory/ntap-20240726-0004/
- https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml
- https://www.iana.org/assignments/iana-ipv6-special-registry/iana-ipv6-special-registry.xhtml
low severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u5
Detailed paths
-
Introduced through: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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.
There is a MEDIUM severity vulnerability affecting CPython.
The email module didn’t properly quote newlines for email headers when serializing an email message allowing for header injection when an email is serialized.
Remediation
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-6923
- https://github.com/python/cpython/issues/121650
- https://github.com/python/cpython/pull/122233
- https://mail.python.org/archives/list/security-announce@python.org/thread/QH3BUOE2DYQBWP7NAQ7UNHPPOELKISRW/
- https://github.com/python/cpython/commit/4766d1200fdf8b6728137aa2927a297e224d5fa7
- https://github.com/python/cpython/commit/4aaa4259b5a6e664b7316a4d60bdec7ee0f124d0
- https://github.com/python/cpython/commit/06f28dc236708f72871c64d4bc4b4ea144c50147
- https://github.com/python/cpython/commit/b158a76ce094897c870fb6b3de62887b7ccc33f1
- https://github.com/python/cpython/commit/f7be505d137a22528cb0fc004422c0081d5d90e6
- https://github.com/python/cpython/commit/f7c0f09e69e950cf3c5ada9dbde93898eb975533
- http://www.openwall.com/lists/oss-security/2024/08/01/3
- http://www.openwall.com/lists/oss-security/2024/08/02/2
- https://security.netapp.com/advisory/ntap-20240926-0003/
- https://lists.debian.org/debian-lts-announce/2025/01/msg00005.html
- https://github.com/python/cpython/commit/097633981879b3c9de9a1dd120d3aa585ecc2384
- https://lists.debian.org/debian-lts-announce/2024/12/msg00000.html
low severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u3
Detailed paths
-
Introduced through: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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.
There is a HIGH severity vulnerability affecting the CPython "zipfile" module affecting "zipfile.Path". Note that the more common API "zipfile.ZipFile" class is unaffected.
When iterating over names of entries in a zip archive (for example, methods of "zipfile.Path" like "namelist()", "iterdir()", etc) the process can be put into an infinite loop with a maliciously crafted zip archive. This defect applies when reading only metadata or extracting the contents of the zip archive. Programs that are not handling user-controlled zip archives are not affected.
Remediation
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-8088
- https://github.com/python/cpython/commit/795f2597a4be988e2bb19b69ff9958e981cb894e
- https://github.com/python/cpython/commit/8c7348939d8a3ecd79d630075f6be1b0c5b41f64
- https://github.com/python/cpython/commit/dcc5182f27c1500006a1ef78e10613bb45788dea
- https://github.com/python/cpython/issues/122905
- https://github.com/python/cpython/pull/122906
- https://mail.python.org/archives/list/security-announce@python.org/thread/GNFCKVI4TCATKQLALJ5SN4L4CSPSMILU/
- https://github.com/python/cpython/commit/e0264a61119d551658d9445af38323ba94fc16db
- https://github.com/python/cpython/issues/123270
- https://github.com/python/cpython/commit/2231286d78d328c2f575e0b05b16fe447d1656d6
- https://github.com/python/cpython/commit/7e8883a3f04d308302361aeffc73e0e9837f19d4
- https://github.com/python/cpython/commit/95b073bddefa6243effa08e131e297c0383e7f6a
- https://github.com/python/cpython/commit/7bc367e464ce50b956dd232c1dfa1cad4e7fb814
- https://github.com/python/cpython/commit/962055268ed4f2ca1d717bfc8b6385de50a23ab7
- https://github.com/python/cpython/commit/fc0b8259e693caa8400fa8b6ac1e494e47ea7798
- https://github.com/python/cpython/commit/0aa1ee22ab6e204e9d3d0e9dd63ea648ed691ef1
- http://www.openwall.com/lists/oss-security/2024/08/22/1
- http://www.openwall.com/lists/oss-security/2024/08/22/4
- http://www.openwall.com/lists/oss-security/2024/08/23/1
- http://www.openwall.com/lists/oss-security/2024/08/23/2
- https://security.netapp.com/advisory/ntap-20241011-0010/
- https://github.com/python/cpython/commit/9cd03263100ddb1657826cc4a71470786cab3932
- https://lists.debian.org/debian-lts-announce/2024/12/msg00000.html
low severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u6
Detailed paths
-
Introduced through: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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 Python standard library functions urllib.parse.urlsplit and urlparse accepted domain names that included square brackets which isn't valid according to RFC 3986. Square brackets are only meant to be used as delimiters for specifying IPv6 and IPvFuture hosts in URLs. This could result in differential parsing across the Python URL parser and other specification-compliant URL parsers.
Remediation
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u6 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-0938
- https://github.com/python/cpython/issues/105704
- https://github.com/python/cpython/pull/129418
- https://github.com/python/cpython/commit/d89a5f6a6e65511a5f6e0618c4c30a7aa5aba56a
- https://mail.python.org/archives/list/security-announce@python.org/thread/K4EUG6EKV6JYFIC24BASYOZS4M5XOQIB/
- https://github.com/python/cpython/commit/90e526ae67b172ed7c6c56e7edad36263b0f9403
- https://github.com/python/cpython/commit/a7084f6075c9595ba60119ce8c62f1496f50c568
- https://github.com/python/cpython/commit/526617ed68cde460236c973e5d0a8bad4de896ba
- https://github.com/python/cpython/commit/b8b4b713c5f8ec0958c7ef8d29d6711889bc94ab
- https://github.com/python/cpython/commit/ff4e5c25666f63544071a6b075ae8b25c98b7a32
- https://security.netapp.com/advisory/ntap-20250314-0002/
- https://lists.debian.org/debian-lts-announce/2025/03/msg00013.html
low severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u7
Detailed paths
-
Introduced through: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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.
When folding a long comment in an email header containing exclusively unfoldable characters, the parenthesis would not be preserved. This could be used for injecting headers into email messages where addresses are user-controlled and not sanitized.
Remediation
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-11468
- https://github.com/python/cpython/issues/143935
- https://github.com/python/cpython/pull/143936
- https://mail.python.org/archives/list/security-announce@python.org/thread/FELSEOLBI2QR6YLG6Q7VYF7FWSGQTKLI/
- https://github.com/python/cpython/commit/17d1490aa97bd6b98a42b1a9b324ead84e7fd8a2
- https://github.com/python/cpython/commit/61614a5e5056e4f61ced65008d4576f3df34acb6
- https://github.com/python/cpython/commit/e9970f077240c7c670e8a6fc6662f2b30d3b6ad0
- https://github.com/python/cpython/commit/f738386838021c762efea6c9802c82de65e87796
- https://github.com/python/cpython/commit/a76e4cd62dd68e7cbe86e37e6ed988495a646b66
- https://github.com/python/cpython/commit/003b8315669b9f08b1010a49071f73f15f818094
low severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u7
Detailed paths
-
Introduced through: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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.
User-controlled data URLs parsed by urllib.request.DataHandler allow injecting headers through newlines in the data URL mediatype.
Remediation
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-15282
- https://github.com/python/cpython/issues/143925
- https://github.com/python/cpython/pull/143926
- https://mail.python.org/archives/list/security-announce@python.org/thread/X66HL7SISGJT33J53OHXMZT4DFLMHVKF/
- https://github.com/python/cpython/commit/f25509e78e8be6ea73c811ac2b8c928c28841b9f
- https://github.com/python/cpython/commit/05356b1cc153108aaf27f3b72ce438af4aa218c0
- https://github.com/python/cpython/commit/34d76b00dabde81a793bd06dd8ecb057838c4b38
- https://github.com/python/cpython/commit/3f396ca9d7bbe2a50ea6b8c9b27c0082884d9f80
- https://github.com/python/cpython/commit/4ed11d3cd288e6b90196a15c5a825a45d318fe47
- https://github.com/python/cpython/commit/a35ca3be5842505dab74dc0b90b89cde0405017a
low severity
- 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: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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 imaplib module, when passed a user-controlled command, can have additional commands injected using newlines. Mitigation rejects commands containing control characters.
Remediation
There is no fixed version for Debian:12 python3.11.
References
- https://security-tracker.debian.org/tracker/CVE-2025-15366
- https://github.com/python/cpython/issues/143921
- https://github.com/python/cpython/pull/143922
- https://mail.python.org/archives/list/security-announce@python.org/thread/DD7C7JZJYTBXMDOWKCEIEBJLBRU64OMR/
- https://github.com/python/cpython/commit/6262704b134db2a4ba12e85ecfbd968534f28b45
low severity
- 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: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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 poplib module, when passed a user-controlled command, can have additional commands injected using newlines. Mitigation rejects commands containing control characters.
Remediation
There is no fixed version for Debian:12 python3.11.
References
- https://security-tracker.debian.org/tracker/CVE-2025-15367
- https://github.com/python/cpython/issues/143923
- https://github.com/python/cpython/pull/143924
- https://mail.python.org/archives/list/security-announce@python.org/thread/CBFBOWVGGUJFSGITQCCBZS4GEYYZ7ZNE/
- https://github.com/python/cpython/commit/b234a2b67539f787e191d2ef19a7cbdce32874e7
low severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u6
Detailed paths
-
Introduced through: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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.
During an address list folding when a separating comma ends up on a folded line and that line is to be unicode-encoded then the separator itself is also unicode-encoded. Expected behavior is that the separating comma remains a plan comma. This can result in the address header being misinterpreted by some mail servers.
Remediation
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u6 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-1795
- https://github.com/python/cpython/issues/100884
- https://github.com/python/cpython/pull/100885
- https://github.com/python/cpython/pull/119099
- https://github.com/python/cpython/commit/09fab93c3d857496c0bd162797fab816c311ee48
- https://github.com/python/cpython/commit/70754d21c288535e86070ca7a6e90dcb670b8593
- https://github.com/python/cpython/commit/9148b77e0af91cdacaa7fe3dfac09635c3fe9a74
- https://mail.python.org/archives/list/security-announce@python.org/thread/MB62IZMEC3UM6SGHP5LET5JX2Y7H4ZUR/
- https://github.com/python/cpython/commit/a4ef689ce670684ec132204b1cd03720c8e0a03d
- https://github.com/python/cpython/commit/d4df3c55e4c5513947f907f24766b34d2ae8c090
- https://lists.debian.org/debian-lts-announce/2025/03/msg00013.html
low severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u7
Detailed paths
-
Introduced through: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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.
There is an issue in CPython when using bytes.decode("unicode_escape", error="ignore|replace"). If you are not using the "unicode_escape" encoding or an error handler your usage is not affected. To work-around this issue you may stop using the error= handler and instead wrap the bytes.decode() call in a try-except catching the DecodeError.
Remediation
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-4516
- https://github.com/python/cpython/commit/69b4387f78f413e8c47572a85b3478c47eba8142
- https://github.com/python/cpython/commit/9f69a58623bd01349a18ba0c7a9cb1dad6a51e8e
- https://github.com/python/cpython/issues/133767
- https://github.com/python/cpython/pull/129648
- https://mail.python.org/archives/list/security-announce@python.org/thread/L75IPBBTSCYEF56I2M4KIW353BB3AY74/
- http://www.openwall.com/lists/oss-security/2025/05/16/4
- http://www.openwall.com/lists/oss-security/2025/05/19/1
- https://github.com/python/cpython/commit/4398b788ffc1f954a2c552da285477d42a571292
- https://github.com/python/cpython/commit/6279eb8c076d89d3739a6edb393e43c7929b429d
- https://github.com/python/cpython/commit/73b3040f592436385007918887b7e2132aa8431f
- https://github.com/python/cpython/commit/8d35fd1b34935221aff23a1ab69a429dd156be77
- https://github.com/python/cpython/commit/ab9893c40609935e0d40a6d2a7307ea51aec598b
low severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u7
Detailed paths
-
Introduced through: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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 html.parser.HTMLParser class had worse-case quadratic complexity when processing certain crafted malformed inputs potentially leading to amplified denial-of-service.
Remediation
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-6069
- https://github.com/python/cpython/commit/4455cbabf991e202185a25a631af206f60bbc949
- https://github.com/python/cpython/commit/6eb6c5dbfb528bd07d77b60fd71fd05d81d45c41
- https://github.com/python/cpython/commit/d851f8e258c7328814943e923a7df81bca15df4b
- https://github.com/python/cpython/issues/135462
- https://github.com/python/cpython/pull/135464
- https://mail.python.org/archives/list/security-announce@python.org/thread/K5PIYLR6EP3WR7ZOKKYQUWEDNQVUXOYM/
- https://github.com/python/cpython/commit/8d1b3dfa09135affbbf27fb8babcf3c11415df49
- https://github.com/python/cpython/commit/ab0893fd5c579d9cea30841680e6d35fc478afb5
- https://github.com/python/cpython/commit/f3c6f882cddc8dc30320d2e73edf019e201394fc
- https://github.com/python/cpython/commit/fdc9d214c01cb4588f540cfa03726bbf2a33fc15
low severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u7
Detailed paths
-
Introduced through: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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.
There is a defect in the CPython “tarfile” module affecting the “TarFile” extraction and entry enumeration APIs. The tar implementation would process tar archives with negative offsets without error, resulting in an infinite loop and deadlock during the parsing of maliciously crafted tar archives.
This vulnerability can be mitigated by including the following patch after importing the “tarfile” module: https://gist.github.com/sethmlarson/1716ac5b82b73dbcbf23ad2eff8b33e1
Remediation
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-8194
- https://github.com/python/cpython/issues/130577
- https://github.com/python/cpython/pull/137027
- https://mail.python.org/archives/list/security-announce@python.org/thread/ZULLF3IZ726XP5EY7XJ7YIN3K5MDYR2D/
- https://github.com/python/cpython/commit/7040aa54f14676938970e10c5f74ea93cd56aa38
- https://github.com/python/cpython/commit/cdae923ffe187d6ef916c0f665a31249619193fe
- https://gist.github.com/sethmlarson/1716ac5b82b73dbcbf23ad2eff8b33e1
- https://github.com/python/cpython/commit/c9d9f78feb1467e73fd29356c040bde1c104f29f
- https://github.com/python/cpython/commit/fbc2a0ca9ac8aff6887f8ddf79b87b4510277227
- https://github.com/python/cpython/commit/57f5981d6260ed21266e0c26951b8564cc252bc2
- https://github.com/python/cpython/commit/73f03e4808206f71eb6b92c579505a220942ef19
- https://github.com/python/cpython/commit/b4ec17488eedec36d3c05fec127df71c0071f6cb
- http://www.openwall.com/lists/oss-security/2025/07/28/1
- http://www.openwall.com/lists/oss-security/2025/07/28/2
low severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u7
Detailed paths
-
Introduced through: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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 'zipfile' module would not check the validity of the ZIP64 End of Central Directory (EOCD) Locator record offset value would not be used to locate the ZIP64 EOCD record, instead the ZIP64 EOCD record would be assumed to be the previous record in the ZIP archive. This could be abused to create ZIP archives that are handled differently by the 'zipfile' module compared to other ZIP implementations.
Remediation maintains this behavior, but checks that the offset specified in the ZIP64 EOCD Locator record matches the expected value.
Remediation
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-8291
- https://github.com/python/cpython/pull/139702
- https://mail.python.org/archives/list/security-announce@python.org/thread/QECOPWMTH4VPPJAXAH2BGTA4XADOP62G/
- https://github.com/python/cpython/commit/162997bb70e067668c039700141770687bc8f267
- https://github.com/python/cpython/commit/333d4a6f4967d3ace91492a39ededbcf3faa76a6
- https://github.com/python/cpython/issues/139700
- https://github.com/python/cpython/commit/1d29afb0d6218aa8fb5e1e4a6133a4778d89bb46
- https://github.com/python/cpython/commit/76437ac248ad8ca44e9bf697b02b1e2241df2196
- https://github.com/python/cpython/commit/8392b2f0d35678407d9ce7d95655a5b77de161b4
- https://github.com/python/cpython/commit/bca11ae7d575d87ed93f5dd6a313be6246e3e388
- https://github.com/python/cpython/commit/d11e69d6203080e3ec450446bfed0516727b85c3
- https://github.com/google/security-research/security/advisories/GHSA-hhv7-p4pg-wm6p
- https://github.com/psf/advisory-database/blob/main/advisories/python/PSF-2025-12.json
low severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u7
Detailed paths
-
Introduced through: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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.
When using http.cookies.Morsel, user-controlled cookie values and parameters can allow injecting HTTP headers into messages. Patch rejects all control characters within cookie names, values, and parameters.
Remediation
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-0672
- https://github.com/python/cpython/issues/143919
- https://github.com/python/cpython/pull/143920
- https://mail.python.org/archives/list/security-announce@python.org/thread/6VFLQQEIX673KXKFUZXCUNE5AZOGZ45M/
- https://github.com/python/cpython/commit/95746b3a13a985787ef53b977129041971ed7f70
- https://github.com/python/cpython/commit/712452e6f1d4b9f7f8c4c92ebfcaac1705faa440
- https://github.com/python/cpython/commit/62700107418eb2cca3fc88da036a243ea975f172
- https://github.com/python/cpython/commit/7852d72b653fea0199acf5fc2a84f6f8b84eba8d
- https://github.com/python/cpython/commit/918387e4912d12ffc166c8f2a38df92b6ec756ca
- https://github.com/python/cpython/commit/b1869ff648bbee0717221d09e6deff46617f3e85
low severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u7
Detailed paths
-
Introduced through: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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.
User-controlled header names and values containing newlines can allow injecting HTTP headers.
Remediation
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-0865
- https://github.com/python/cpython/issues/143916
- https://github.com/python/cpython/pull/143917
- https://mail.python.org/archives/list/security-announce@python.org/thread/BJ6QPHNSHJTS3A7CFV6IBMCAP2DWRVNT/
- https://github.com/python/cpython/commit/22e4d55285cee52bc4dbe061324e5f30bd4dee58
- https://github.com/python/cpython/commit/23e3c0ae867cca0130e441e776c9955b9027c510
- https://github.com/python/cpython/commit/2f840249550e082dc351743f474ba56da10478d2
- https://github.com/python/cpython/commit/4802b96a2cde58570c24c13ef3289490980961c5
- https://github.com/python/cpython/commit/e4846a93ac07a8ae9aa18203af0dd13d6e7a6995
- https://github.com/python/cpython/commit/f7fceed79ca1bceae8dbe5ba5bc8928564da7211
- https://github.com/python/cpython/commit/66da7bf6fe7b81e3ecc9c0a25bd47d4616c8d1a6
- https://github.com/python/cpython/commit/83ecd18779f286d872f68bfce175651e407d9fff
- https://github.com/python/cpython/commit/bfba660085767f8c2d582134e9d511a85eda04cf
- https://github.com/python/cpython/commit/286e3ac39984fe85a17f4ab39c64d382137aae5f
- https://github.com/python/cpython/commit/8bb044d29310bb05d15086cdaa8bf64867d61a97
- https://github.com/python/cpython/commit/c592227ffb48679af9845a45dbb0875d975bb219
low severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u7
Detailed paths
-
Introduced through: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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, specifically the "BytesGenerator" class, didn’t properly quote newlines for email headers when serializing an email message allowing for header injection when an email is serialized. This is only applicable if using "LiteralHeader" writing headers that don't respect email folding rules, the new behavior will reject the incorrectly folded headers in "BytesGenerator".
Remediation
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-1299
- https://cve.org/CVERecord?id=CVE-2024-6923
- https://github.com/python/cpython/commit/052e55e7d44718fe46cbba0ca995cb8fcc359413
- https://github.com/python/cpython/issues/144125
- https://github.com/python/cpython/pull/144126
- https://mail.python.org/archives/list/security-announce@python.org/thread/6ZZULGALJTITEAGEXLDJE2C6FORDXPBT/
- https://github.com/python/cpython/commit/0a925ab591c45d6638f37b5e57796f36fa0e56d8
- https://github.com/python/cpython/commit/7877fe424415bc4a13045e62a90a7277413d8cb9
- https://github.com/python/cpython/commit/842ce19a0c0b58d61591e8f6a708c38db1fb94e4
- https://github.com/python/cpython/commit/8cdf6204f4ae821f32993f8fc6bad0d318f95f36
- https://github.com/python/cpython/commit/e417f05ad77a4c30ddc07f99e90fc0cef43e831a
low severity
- 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: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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.
CR/LF bytes were not rejected by HTTP client proxy tunnel headers or host.
Remediation
There is no fixed version for Debian:12 python3.11.
References
- https://security-tracker.debian.org/tracker/CVE-2026-1502
- https://github.com/python/cpython/commit/05ed7ce7ae9e17c23a04085b2539fe6d6d3cef69
- https://github.com/python/cpython/issues/146211
- https://github.com/python/cpython/pull/146212
- https://mail.python.org/archives/list/security-announce@python.org/thread/2IVPAEQWUJBCTQZEJEVTYCIKSMQPGRZ3/
- http://www.openwall.com/lists/oss-security/2026/04/11/4
- https://github.com/python/cpython/commit/b1cf9016335cb637c5a425032e8274a224f4b2ed
- https://github.com/python/cpython/commit/9e071c9b28c17f347f81b388a003d4eeb3c7a8dd
- https://github.com/python/cpython/commit/c00c386faa579ad71196d33408644478488e43ec
low severity
- 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: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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 import hook in CPython that handles legacy *.pyc files (SourcelessFileLoader) is incorrectly handled in FileLoader (a base class) and so does not use io.open_code() to read the .pyc files. sys.audit handlers for this audit event therefore do not fire.
Remediation
There is no fixed version for Debian:12 python3.11.
References
- https://security-tracker.debian.org/tracker/CVE-2026-2297
- https://github.com/python/cpython/commit/482d6f8bdba9da3725d272e8bb4a2d25fb6a603e
- https://github.com/python/cpython/commit/a51b1b512de1d56b3714b65628a2eae2b07e535e
- https://github.com/python/cpython/commit/e58e9802b9bec5cdbf48fc9bf1da5f4fda482e86
- https://github.com/python/cpython/issues/145506
- https://github.com/python/cpython/pull/145507
- http://www.openwall.com/lists/oss-security/2026/03/05/6
- https://github.com/python/cpython/commit/69ddd9bb2cc4bd69b1565647c18659c6a789ccd9
- https://github.com/python/cpython/commit/876858c9f65d9ab656c7fa639f268ce7856d89dd
low severity
new
- 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: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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.
unicodedata.normalize() can take excessive CPU time when processing specially crafted Unicode input containing long runs of combining characters with alternating Canonical Combining Class values. This affects all normalization forms.
Remediation
There is no fixed version for Debian:12 python3.11.
References
- https://security-tracker.debian.org/tracker/CVE-2026-3276
- https://github.com/python/cpython/issues/149079
- https://github.com/python/cpython/pull/149080
- https://mail.python.org/archives/list/security-announce@python.org/thread/PP5HB4K7727OBBM76KA2ILID76K3OZGZ/
- http://www.openwall.com/lists/oss-security/2026/06/03/15
- https://github.com/python/cpython/commit/6b505d1f41f8f3ea0fe5a4786d3a8fff1875cfc0
- https://github.com/python/cpython/commit/991224b1e8311c85f198f6dd8208bf8cff7fc26f
- https://github.com/python/cpython/commit/ba785b88add96acbf403d65cb157fb2743a33a32
- https://github.com/python/cpython/commit/c5512bd7c1dc28055660565275012766941d3066
low severity
- 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: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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.
When calling base64.b64decode() or related functions the decoding process would stop after encountering the first padded quad regardless of whether there was more information to be processed. This can lead to data being accepted which may be processed differently by other implementations. Use "validate=True" to enable stricter processing of base64 data.
Remediation
There is no fixed version for Debian:12 python3.11.
References
- https://security-tracker.debian.org/tracker/CVE-2026-3446
- https://github.com/python/cpython/commit/1f9958f909c1b41a4ffc0b613ef8ec8fa5e7c474
- https://github.com/python/cpython/commit/4561f6418a691b3e89aef0901f53fe0dfb7f7c0e
- https://github.com/python/cpython/commit/e31c55121620189a0d1a07b689762d8ca9c1b7fa
- https://github.com/python/cpython/issues/145264
- https://github.com/python/cpython/pull/145267
- https://mail.python.org/archives/list/security-announce@python.org/thread/F5ZT5ICGJ6CKXVUJ34YBVY7WOZ5SHG53/
low severity
- 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: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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.
DISPUTED: The project has clarified that the documentation was incorrect, and that pkgutil.get_data() has the same security model as open(). The documentation has been updated to clarify this point. There is no vulnerability in the function if following the intended security model.
pkgutil.get_data() did not validate the resource argument as documented, allowing path traversals.
Remediation
There is no fixed version for Debian:12 python3.11.
References
- https://security-tracker.debian.org/tracker/CVE-2026-3479
- https://github.com/python/cpython/issues/146121
- https://github.com/python/cpython/pull/146122
- https://mail.python.org/archives/list/security-announce@python.org/thread/WYLLVQOOCKGK73JM7Z7ZSNOJC4N7BAWY/
- https://github.com/python/cpython/commit/bcdf231946b1da8bdfbab4c05539bb0cc964a1c7
- https://github.com/python/cpython/commit/5af6ce3e7b643a30a02d22245c1e3f4a8bc0a1fe
- https://github.com/python/cpython/commit/cf59bf76470f3d75ad47d80ffb8ce76b64b5e943
- https://github.com/python/cpython/commit/d786d59a8f7196bb630100a869f28ad13436b59c
low severity
- 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: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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.
Use-after-free (UAF) was possible in the lzma.LZMADecompressor, bz2.BZ2Decompressor, and gzip.GzipFile when a memory allocation fails with a MemoryError and the decompression instance is re-used. This scenario can be triggered if the process is under memory pressure. The fix cleans up the dangling pointer in this specific error condition.
The vulnerability is only present if the program re-uses decompressor instances across multiple decompression calls even after a MemoryError is raised during decompression. Using the helper functions to one-shot decompress data such as lzma.decompress(), bz2.decompress(), gzip.decompress(), and zlib.decompress() are not affected as a new decompressor instance is used per call. If the decompressor instance is not re-used after an error condition, this usage is similarly not vulnerable.
Remediation
There is no fixed version for Debian:12 python3.11.
References
- https://security-tracker.debian.org/tracker/CVE-2026-6100
- https://github.com/python/cpython/commit/6a5f79c8d7bbf22b083b240910c7a8781a59437d
- https://github.com/python/cpython/commit/8fc66aef6d7b3ae58f43f5c66f9366cc8cbbfcd2
- https://github.com/python/cpython/commit/c3cf71c3366fe49acb776a639405c0eea6169c20
- https://github.com/python/cpython/issues/148395
- https://github.com/python/cpython/pull/148396
- https://mail.python.org/archives/list/security-announce@python.org/thread/HTWB2Z6KT5QQX4RYEZAFININDHNOSIF3/
- http://www.openwall.com/lists/oss-security/2026/04/13/10
- https://github.com/python/cpython/commit/47128e64f98c3a20271138a98c2922bea2a3ee0e
- https://github.com/python/cpython/commit/e20c6c9667c99ecaab96e1a2b3767082841ffc8b
low severity
new
- 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: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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.
tarfile.data_filter could be bypassed using crafted link entries, including symlinks with empty or directory-like names, to redirect later archive members outside the intended extraction directory. This allowed a malicious tar archive to cause tarfile.extractall() to write files outside the destination directory, subject to the permissions of the extracting process.
Remediation
There is no fixed version for Debian:12 python3.11.
References
- https://security-tracker.debian.org/tracker/CVE-2026-7774
- https://github.com/python/cpython/issues/149486
- https://github.com/python/cpython/pull/149487
- https://mail.python.org/archives/list/security-announce@python.org/thread/4FU62L2M6RMMHT2QPGQNPEHHUND7CEX5/
- http://www.openwall.com/lists/oss-security/2026/06/04/9
low severity
new
- 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: golang@1.20 › python3.11@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: golang@1.20 › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: golang@1.20 › 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 ftpcp() function in Lib/ftplib.py was not updated when CVE-2021-4189 was fixed. While makepasv() was patched to replace server-supplied PASV host addresses with the actual peer address (getpeername()[0]), ftpcp() still calls parse227() directly and passes the raw attacker-controllable IP address and port to target.sendport(). This patch is related to CVE-2021-4189.
Remediation
There is no fixed version for Debian:12 python3.11.
References
low severity
- Vulnerable module: sed
- Introduced through: sed@4.9-1
- Fixed in: 4.9-1+deb12u1
Detailed paths
-
Introduced through: golang@1.20 › sed@4.9-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream sed package and not the sed package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
When sed is invoked with both -i (in-place edit) and --follow-symlinks, the function open_next_file() performs two separate, non-atomic filesystem operations on the same path:
- resolves symlink to its target and stores the resolved path for determining when output is written,
- opens the original symlink path (not the resolved one) to read the file. Between these two calls there is a race window. If an attacker atomically replaces the symlink with a different target during that window, sed will: read content from the new (attacker-chosen) symlink target and write the processed result to the path recorded in step 1. This can lead to arbitrary file overwrite with attacker-controlled content in the context of the sed process.
This issue was fixed in version 4.10.
Remediation
Upgrade Debian:12 sed to version 4.9-1+deb12u1 or higher.
References
low severity
- 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: golang@1.20 › shadow/login@1:4.13+dfsg1-1+b1
-
Introduced through: golang@1.20 › 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-utils (aka shadow) 4.4 through 4.17.0 establishes a default /etc/subuid behavior (e.g., uid 100000 through 165535 for the first user account) that can realistically conflict with the uids of users defined on locally administered networks, potentially leading to account takeover, e.g., by leveraging newuidmap for access to an NFS home directory (or same-host resources in the case of remote logins by these local network users). NOTE: it may also be argued that system administrators should not have assigned uids, within local networks, that are within the range that can occur in /etc/subuid.
Remediation
There is no fixed version for Debian:12 shadow.
References
low severity
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2
Detailed paths
-
Introduced through: golang@1.20 › 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.
An information disclosure issue in the zipfileInflate function in the zipfile extension in SQLite v3.51.1 and earlier allows attackers to obtain heap memory via supplying a crafted ZIP file.
Remediation
There is no fixed version for Debian:12 sqlite3.
References
low severity
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2
Detailed paths
-
Introduced through: golang@1.20 › 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.
An integer overflow exists in the FTS5 https://sqlite.org/fts5.html extension. It occurs when the size of an array of tombstone pointers is calculated and truncated into a 32-bit integer. A pointer to partially controlled data can then be written out of bounds.
Remediation
There is no fixed version for Debian:12 sqlite3.
References
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.19-1~deb12u1 and systemd/libudev1@252.19-1~deb12u1
- Fixed in: 252.39-1~deb12u2
Detailed paths
-
Introduced through: golang@1.20 › systemd/libsystemd0@252.19-1~deb12u1
-
Introduced through: golang@1.20 › systemd/libudev1@252.19-1~deb12u1
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, a system and service manager, (as PID 1) hits an assert and freezes execution when an unprivileged IPC API call is made with spurious data. On version v249 and older the effect is not an assert, but stack overwriting, with the attacker controlled content. From version v250 and newer this is not possible as the safety check causes an assert instead. This IPC call was added in v239, so versions older than that are not affected. Versions 260-rc1, 259.2, 258.5, and 257.11 contain patches. No known workarounds are available.
Remediation
Upgrade Debian:12 systemd to version 252.39-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-29111
- https://github.com/systemd/systemd/commit/1d22f706bd04f45f8422e17fbde3f56ece17758a
- https://github.com/systemd/systemd/commit/20021e7686426052e3a7505425d7e12085feb2a6
- https://github.com/systemd/systemd/commit/21167006574d6b83813c7596759b474f56562412
- https://github.com/systemd/systemd/commit/3cee294fe8cf4fa0eff933ab21416d099942cabd
- https://github.com/systemd/systemd/commit/42aee39107fbdd7db1ccd402a2151822b2805e9f
- https://github.com/systemd/systemd/commit/54588d2dedff54bfb6036670820650e4ea74628f
- https://github.com/systemd/systemd/commit/7ac3220213690e8a8d6d2a6e81e43bd1dce01d69
- https://github.com/systemd/systemd/commit/80acea4ef80a4bb78560ed970c34952299b890d6
- https://github.com/systemd/systemd/commit/b5fd14693057e5f2c9b4a49603be64ec3608ff6c
- https://github.com/systemd/systemd/commit/efa6ba2ab625aaa160ac435a09e6482fc63bdbe8
- https://github.com/systemd/systemd/security/advisories/GHSA-gx6q-6f99-m764
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.19-1~deb12u1 and systemd/libudev1@252.19-1~deb12u1
- Fixed in: 252.39-1~deb12u2
Detailed paths
-
Introduced through: golang@1.20 › systemd/libsystemd0@252.19-1~deb12u1
-
Introduced through: golang@1.20 › systemd/libudev1@252.19-1~deb12u1
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.
In udev in systemd before 260, local root execution can occur via malicious hardware devices and unsanitized kernel output.
Remediation
Upgrade Debian:12 systemd to version 252.39-1~deb12u2 or higher.
References
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.19-1~deb12u1 and systemd/libudev1@252.19-1~deb12u1
- Fixed in: 252.39-1~deb12u2
Detailed paths
-
Introduced through: golang@1.20 › systemd/libsystemd0@252.19-1~deb12u1
-
Introduced through: golang@1.20 › systemd/libudev1@252.19-1~deb12u1
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.
In nspawn in systemd 233 through 259 before 260, an escape-to-host action can occur via a crafted optional config file.
Remediation
Upgrade Debian:12 systemd to version 252.39-1~deb12u2 or higher.
References
low severity
- Vulnerable module: tar
- Introduced through: tar@1.34+dfsg-1.2
- Fixed in: 1.34+dfsg-1.2+deb12u1
Detailed paths
-
Introduced through: golang@1.20 › 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
- https://security-tracker.debian.org/tracker/CVE-2023-39804
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058079
- https://git.savannah.gnu.org/cgit/tar.git/commit/?id=a339f05cd269013fa133d2f148d73f6f7d4247e4
- https://git.savannah.gnu.org/cgit/tar.git/tree/src/xheader.c?h=release_1_34#n1723
- https://lists.debian.org/debian-lts-announce/2024/03/msg00008.html
low severity
- 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: golang@1.20 › util-linux/bsdutils@1:2.38.1-5+b1
-
Introduced through: golang@1.20 › util-linux/libblkid1@2.38.1-5+b1
-
Introduced through: golang@1.20 › util-linux/libmount1@2.38.1-5+b1
-
Introduced through: golang@1.20 › util-linux/libsmartcols1@2.38.1-5+b1
-
Introduced through: golang@1.20 › util-linux/libuuid1@2.38.1-5+b1
-
Introduced through: golang@1.20 › util-linux/mount@2.38.1-5+b1
-
Introduced through: golang@1.20 › util-linux/util-linux@2.38.1-5+b1
-
Introduced through: golang@1.20 › 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.
util-linux is a random collection of Linux utilities. Prior to version 2.41.4, a TOCTOU (Time-of-Check-Time-of-Use) vulnerability has been identified in the SUID binary /usr/bin/mount from util-linux. The mount binary, when setting up loop devices, validates the source file path with user privileges via fork() + setuid() + realpath(), but subsequently re-canonicalizes and opens it with root privileges (euid=0) without verifying that the path has not been replaced between both operations. Neither O_NOFOLLOW, nor inode comparison, nor post-open fstat() are employed. This allows a local unprivileged user to replace the source file with a symlink pointing to any root-owned file or device during the race window, causing the SUID binary to open and mount it as root. Exploitation requires an /etc/fstab entry with user,loop options whose path points to a directory where the attacker has write permission, and that /usr/bin/mount has the SUID bit set (the default configuration on virtually all Linux distributions). The impact is unauthorized read access to root-protected files and block devices, including backup images, disk volumes, and any file containing a valid filesystem. This issue has been patched in version 2.41.4.
Remediation
There is no fixed version for Debian:12 util-linux.
References
low severity
- 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: golang@1.20 › util-linux/libblkid1@2.38.1-5+b1
-
Introduced through: golang@1.20 › util-linux/libmount1@2.38.1-5+b1
-
Introduced through: golang@1.20 › util-linux/libsmartcols1@2.38.1-5+b1
-
Introduced through: golang@1.20 › util-linux/libuuid1@2.38.1-5+b1
-
Introduced through: golang@1.20 › util-linux/mount@2.38.1-5+b1
-
Introduced through: golang@1.20 › util-linux/util-linux@2.38.1-5+b1
-
Introduced through: golang@1.20 › 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
- https://security-tracker.debian.org/tracker/CVE-2024-28085
- http://seclists.org/fulldisclosure/2024/Mar/35
- http://www.openwall.com/lists/oss-security/2024/03/27/5
- http://www.openwall.com/lists/oss-security/2024/03/27/6
- http://www.openwall.com/lists/oss-security/2024/03/27/7
- http://www.openwall.com/lists/oss-security/2024/03/27/8
- http://www.openwall.com/lists/oss-security/2024/03/27/9
- http://www.openwall.com/lists/oss-security/2024/03/28/1
- http://www.openwall.com/lists/oss-security/2024/03/28/2
- http://www.openwall.com/lists/oss-security/2024/03/28/3
- https://github.com/skyler-ferrante/CVE-2024-28085
- https://github.com/util-linux/util-linux/security/advisories/GHSA-xv2h-c6ww-mrjq
- https://lists.debian.org/debian-lts-announce/2024/04/msg00005.html
- https://mirrors.edge.kernel.org/pub/linux/utils/util-linux/
- https://people.rit.edu/sjf5462/6831711781/wall_2_27_2024.txt
- https://security.netapp.com/advisory/ntap-20240531-0003/
- https://www.openwall.com/lists/oss-security/2024/03/27/5
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-202008.html
low severity
- Vulnerable module: wget/wget
- Introduced through: wget/wget@1.21.3-1+b2
Detailed paths
-
Introduced through: golang@1.20 › 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.
Applications that use Wget to access a remote resource using shorthand URLs and pass arbitrary user credentials in the URL are vulnerable. In these cases attackers can enter crafted credentials which will cause Wget to access an arbitrary host.
Remediation
There is no fixed version for Debian:12 wget.
References
- https://security-tracker.debian.org/tracker/CVE-2024-10524
- https://git.savannah.gnu.org/cgit/wget.git/commit/?id=c419542d956a2607bbce5df64b9d378a8588d778
- https://jfrog.com/blog/cve-2024-10524-wget-zero-day-vulnerability/
- https://seclists.org/oss-sec/2024/q4/107
- http://www.openwall.com/lists/oss-security/2024/11/18/6
- https://security.netapp.com/advisory/ntap-20250321-0007/
low severity
- Vulnerable module: xz-utils/liblzma5
- Introduced through: xz-utils/liblzma5@5.4.1-0.2
- Fixed in: 5.4.1-1
Detailed paths
-
Introduced through: golang@1.20 › xz-utils/liblzma5@5.4.1-0.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream xz-utils package and not the xz-utils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
XZ Utils provide a general-purpose data-compression library plus command-line tools. In XZ Utils 5.3.3alpha to 5.8.0, the multithreaded .xz decoder in liblzma has a bug where invalid input can at least result in a crash. The effects include heap use after free and writing to an address based on the null pointer plus an offset. Applications and libraries that use the lzma_stream_decoder_mt function are affected. The bug has been fixed in XZ Utils 5.8.1, and the fix has been committed to the v5.4, v5.6, v5.8, and master branches in the xz Git repository. No new release packages will be made from the old stable branches, but a standalone patch is available that applies to all affected releases.
Remediation
Upgrade Debian:12 xz-utils to version 5.4.1-1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-31115
- https://github.com/tukaani-project/xz/commit/d5a2ffe41bb77b918a8c96084885d4dbe4bf6480
- https://github.com/tukaani-project/xz/security/advisories/GHSA-6cc8-p5mm-29w2
- https://tukaani.org/xz/xz-cve-2025-31115.patch
- http://www.openwall.com/lists/oss-security/2025/04/03/1
- http://www.openwall.com/lists/oss-security/2025/04/03/2
- http://www.openwall.com/lists/oss-security/2025/04/03/3
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html