Vulnerabilities |
141 via 384 paths |
|---|---|
Dependencies |
165 |
Source |
Docker |
Target OS |
debian:12 |
critical severity
- Vulnerable module: zlib/zlib1g
- Introduced through: zlib/zlib1g@1:1.2.13.dfsg-1
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › zlib/zlib1g@1:1.2.13.dfsg-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream zlib package and not the zlib package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
MiniZip in zlib through 1.3 has an integer overflow and resultant heap-based buffer overflow in zipOpenNewFileInZip4_64 via a long filename, comment, or extra field. NOTE: MiniZip is not a supported part of the zlib product. NOTE: pyminizip through 0.2.6 is also vulnerable because it bundles an affected zlib version, and exposes the applicable MiniZip code through its compress API.
Remediation
There is no fixed version for Debian:12 zlib.
References
- 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
high severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u2
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › expat/libexpat1@2.5.0-1+deb12u2
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
medium severity
new
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u2
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › expat/libexpat1@2.5.0-1+deb12u2
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: python3.11
- Introduced through: python3.11@3.11.2-6+deb12u7, python3.11/libpython3.11-minimal@3.11.2-6+deb12u7 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › python3.11@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-minimal@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-stdlib@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/python3.11-minimal@3.11.2-6+deb12u7
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: util-linux
- Introduced through: util-linux@2.38.1-5+deb12u3, util-linux/bsdutils@1:2.38.1-5+deb12u3 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › util-linux@2.38.1-5+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › util-linux/bsdutils@1:2.38.1-5+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › util-linux/libblkid1@2.38.1-5+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › util-linux/libmount1@2.38.1-5+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › util-linux/libsmartcols1@2.38.1-5+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › util-linux/libuuid1@2.38.1-5+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › util-linux/mount@2.38.1-5+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › util-linux/util-linux-extra@2.38.1-5+deb12u3
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
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u14 and glibc/libc6@2.36-9+deb12u14
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › glibc/libc-bin@2.36-9+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › glibc/libc6@2.36-9+deb12u14
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+deb12u3, perl/libperl5.36@5.36.0-7+deb12u3 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › perl@5.36.0-7+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › perl/libperl5.36@5.36.0-7+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › perl/perl-base@5.36.0-7+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › perl/perl-modules-5.36@5.36.0-7+deb12u3
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: tar
- Introduced through: tar@1.34+dfsg-1.2+deb12u1
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › tar@1.34+dfsg-1.2+deb12u1
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+deb12u3, perl/libperl5.36@5.36.0-7+deb12u3 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › perl@5.36.0-7+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › perl/libperl5.36@5.36.0-7+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › perl/perl-base@5.36.0-7+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › perl/perl-modules-5.36@5.36.0-7+deb12u3
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+deb12u2
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › sqlite3/libsqlite3-0@3.40.1-2+deb12u2
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.5-0+deb12u3 and git/git-man@1:2.39.5-0+deb12u3
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › git@1:2.39.5-0+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › git/git-man@1:2.39.5-0+deb12u3
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+deb12u14 and glibc/libc6@2.36-9+deb12u14
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › glibc/libc-bin@2.36-9+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › glibc/libc6@2.36-9+deb12u14
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+deb12u3, perl/libperl5.36@5.36.0-7+deb12u3 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › perl@5.36.0-7+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › perl/libperl5.36@5.36.0-7+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › perl/perl-base@5.36.0-7+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › perl/perl-modules-5.36@5.36.0-7+deb12u3
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: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u2
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › expat/libexpat1@2.5.0-1+deb12u2
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: buildpack-deps@bookworm-scm › ncurses/libncursesw6@6.4-4
-
Introduced through: buildpack-deps@bookworm-scm › ncurses/libtinfo6@6.4-4
-
Introduced through: buildpack-deps@bookworm-scm › ncurses/ncurses-base@6.4-4
-
Introduced through: buildpack-deps@bookworm-scm › ncurses/ncurses-bin@6.4-4
NVD Description
Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
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
new
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2+deb12u2
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › sqlite3/libsqlite3-0@3.40.1-2+deb12u2
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.
SQLite before 3.53.2 contains memory corruption vulnerabilities in the FTS5 full-text search extension that allow attackers to cause process crashes, memory exhaustion, or arbitrary code execution by supplying a crafted database with malformed FTS5 page data. Attackers can trigger an out-of-bounds read in fts5LeafSeek() via an attacker-controlled loop bound and a heap buffer overflow write in fts5ChunkIterate() through a crafted continuation page causing an integer underflow, exploitable when an FTS5 MATCH query is executed against the malicious database.
Remediation
There is no fixed version for Debian:12 sqlite3.
References
low severity
new
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2+deb12u2
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › sqlite3/libsqlite3-0@3.40.1-2+deb12u2
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.
SQLite before 3.53.2 contains a heap-based buffer overflow vulnerability in the FTS5 full-text search extension that allows attackers to cause a crash or execute arbitrary code by supplying a crafted database with malicious continuation page metadata specifying a szLeaf value smaller than 4. Attackers can trigger an integer underflow in fts5ChunkIterate() causing an inflated remaining byte count during FTS5 MATCH query processing, leading to a heap buffer overflow of attacker-controlled data in applications compiled with SQLITE_ENABLE_FTS5.
Remediation
There is no fixed version for Debian:12 sqlite3.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10+deb12u14, curl/libcurl3-gnutls@7.88.1-10+deb12u14 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › curl@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl3-gnutls@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl4@7.88.1-10+deb12u14
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+deb12u14, curl/libcurl3-gnutls@7.88.1-10+deb12u14 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › curl@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl3-gnutls@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl4@7.88.1-10+deb12u14
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+deb12u2
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › expat/libexpat1@2.5.0-1+deb12u2
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.5-0+deb12u3 and git/git-man@1:2.39.5-0+deb12u3
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › git@1:2.39.5-0+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › git/git-man@1:2.39.5-0+deb12u3
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+deb12u14 and glibc/libc6@2.36-9+deb12u14
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › glibc/libc-bin@2.36-9+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › glibc/libc6@2.36-9+deb12u14
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+deb12u14 and glibc/libc6@2.36-9+deb12u14
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › glibc/libc-bin@2.36-9+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › glibc/libc6@2.36-9+deb12u14
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: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u5, krb5/libk5crypto3@1.20.1-2+deb12u5 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › krb5/libgssapi-krb5-2@1.20.1-2+deb12u5
-
Introduced through: buildpack-deps@bookworm-scm › krb5/libk5crypto3@1.20.1-2+deb12u5
-
Introduced through: buildpack-deps@bookworm-scm › krb5/libkrb5-3@1.20.1-2+deb12u5
-
Introduced through: buildpack-deps@bookworm-scm › krb5/libkrb5support0@1.20.1-2+deb12u5
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+deb12u1
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › libgcrypt20@1.10.1-3+deb12u1
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: buildpack-deps@bookworm-scm › openldap/libldap-2.5-0@2.5.13+dfsg-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
The nss_parse_ciphers function in libraries/libldap/tls_m.c in OpenLDAP does not properly parse OpenSSL-style multi-keyword mode cipher strings, which might cause a weaker than intended cipher to be used and allow remote attackers to have unspecified impact via unknown vectors.
Remediation
There is no fixed version for Debian:12 openldap.
References
- 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: buildpack-deps@bookworm-scm › openldap/libldap-2.5-0@2.5.13+dfsg-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability was found in openldap. This security flaw causes a null pointer dereference in ber_memalloc_x() function.
Remediation
There is no fixed version for Debian:12 openldap.
References
- 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: buildpack-deps@bookworm-scm › openldap/libldap-2.5-0@2.5.13+dfsg-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
contrib/slapd-modules/nops/nops.c in OpenLDAP through 2.4.45, when both the nops module and the memberof overlay are enabled, attempts to free a buffer that was allocated on the stack, which allows remote attackers to cause a denial of service (slapd crash) via a member MODDN operation.
Remediation
There is no fixed version for Debian:12 openldap.
References
- 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+deb12u3, perl/libperl5.36@5.36.0-7+deb12u3 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › perl@5.36.0-7+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › perl/libperl5.36@5.36.0-7+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › perl/perl-base@5.36.0-7+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › perl/perl-modules-5.36@5.36.0-7+deb12u3
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+deb12u3, perl/libperl5.36@5.36.0-7+deb12u3 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › perl@5.36.0-7+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › perl/libperl5.36@5.36.0-7+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › perl/perl-base@5.36.0-7+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › perl/perl-modules-5.36@5.36.0-7+deb12u3
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+deb12u7, python3.11/libpython3.11-minimal@3.11.2-6+deb12u7 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › python3.11@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-minimal@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-stdlib@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/python3.11-minimal@3.11.2-6+deb12u7
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+deb12u7, python3.11/libpython3.11-minimal@3.11.2-6+deb12u7 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › python3.11@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-minimal@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-stdlib@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/python3.11-minimal@3.11.2-6+deb12u7
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+deb12u7, python3.11/libpython3.11-minimal@3.11.2-6+deb12u7 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › python3.11@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-minimal@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-stdlib@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/python3.11-minimal@3.11.2-6+deb12u7
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
new
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6+deb12u7, python3.11/libpython3.11-minimal@3.11.2-6+deb12u7 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › python3.11@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-minimal@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-stdlib@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/python3.11-minimal@3.11.2-6+deb12u7
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
- https://github.com/python/cpython/commit/24b8f12544468e4cedf5bfbe25442fcd495391e4
- https://github.com/python/cpython/commit/3573b3b1ecbd99030a0b18658e1bfece771b2566
- https://github.com/python/cpython/commit/eeea765cb9d8f1fc3d8918b272ac3c477983f27a
- https://github.com/python/cpython/commit/fc9b11ff49cbc82e6f917d07a61517a2b5f3145f
low severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2+deb12u10
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › openssh/openssh-client@1:9.2p1-2+deb12u10
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: buildpack-deps@bookworm-scm › 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: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2+deb12u10
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › openssh/openssh-client@1:9.2p1-2+deb12u10
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: coreutils
- Introduced through: coreutils@9.1-1
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › coreutils@9.1-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream coreutils package and not the coreutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
chroot in GNU coreutils, when used with --userspec, allows local users to escape to the parent session via a crafted TIOCSTI ioctl call, which pushes characters to the terminal's input buffer.
Remediation
There is no fixed version for Debian:12 coreutils.
References
- 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+deb12u14, curl/libcurl3-gnutls@7.88.1-10+deb12u14 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › curl@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl3-gnutls@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl4@7.88.1-10+deb12u14
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: buildpack-deps@bookworm-scm › ncurses/libncursesw6@6.4-4
-
Introduced through: buildpack-deps@bookworm-scm › ncurses/libtinfo6@6.4-4
-
Introduced through: buildpack-deps@bookworm-scm › ncurses/ncurses-base@6.4-4
-
Introduced through: buildpack-deps@bookworm-scm › ncurses/ncurses-bin@6.4-4
NVD Description
Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
NCurse v6.4-20230418 was discovered to contain a segmentation fault via the component _nc_wrap_entry().
Remediation
There is no fixed version for Debian:12 ncurses.
References
- 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+deb12u10
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › openssh/openssh-client@1:9.2p1-2+deb12u10
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+deb12u2 and shadow/passwd@1:4.13+dfsg1-1+deb12u2
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › shadow/login@1:4.13+dfsg1-1+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › shadow/passwd@1:4.13+dfsg1-1+deb12u2
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: python3.11
- Introduced through: python3.11@3.11.2-6+deb12u7, python3.11/libpython3.11-minimal@3.11.2-6+deb12u7 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › python3.11@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-minimal@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-stdlib@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/python3.11-minimal@3.11.2-6+deb12u7
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
- Introduced through: util-linux@2.38.1-5+deb12u3, util-linux/bsdutils@1:2.38.1-5+deb12u3 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › util-linux@2.38.1-5+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › util-linux/bsdutils@1:2.38.1-5+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › util-linux/libblkid1@2.38.1-5+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › util-linux/libmount1@2.38.1-5+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › util-linux/libsmartcols1@2.38.1-5+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › util-linux/libuuid1@2.38.1-5+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › util-linux/mount@2.38.1-5+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › util-linux/util-linux-extra@2.38.1-5+deb12u3
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
- Introduced through: wget@1.21.3-1+deb12u1
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › wget@1.21.3-1+deb12u1
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: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2+deb12u10
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › openssh/openssh-client@1:9.2p1-2+deb12u10
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: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u2
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › expat/libexpat1@2.5.0-1+deb12u2
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+deb12u2
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › expat/libexpat1@2.5.0-1+deb12u2
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+deb12u2
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › expat/libexpat1@2.5.0-1+deb12u2
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+deb12u2
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › expat/libexpat1@2.5.0-1+deb12u2
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+deb12u2
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › expat/libexpat1@2.5.0-1+deb12u2
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/gcc-12-base
- Introduced through: gcc-12/gcc-12-base@12.2.0-14+deb12u1, gcc-12/libgcc-s1@12.2.0-14+deb12u1 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › gcc-12/gcc-12-base@12.2.0-14+deb12u1
-
Introduced through: buildpack-deps@bookworm-scm › gcc-12/libgcc-s1@12.2.0-14+deb12u1
-
Introduced through: buildpack-deps@bookworm-scm › gcc-12/libstdc++6@12.2.0-14+deb12u1
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+deb12u2
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › sqlite3/libsqlite3-0@3.40.1-2+deb12u2
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+deb12u1
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › tar@1.34+dfsg-1.2+deb12u1
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
- Introduced through: util-linux@2.38.1-5+deb12u3, util-linux/bsdutils@1:2.38.1-5+deb12u3 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › util-linux@2.38.1-5+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › util-linux/bsdutils@1:2.38.1-5+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › util-linux/libblkid1@2.38.1-5+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › util-linux/libmount1@2.38.1-5+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › util-linux/libsmartcols1@2.38.1-5+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › util-linux/libuuid1@2.38.1-5+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › util-linux/mount@2.38.1-5+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › util-linux/util-linux-extra@2.38.1-5+deb12u3
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: buildpack-deps@bookworm-scm › zlib/zlib1g@1:1.2.13.dfsg-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream zlib package and not the zlib package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
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: curl
- Introduced through: curl@7.88.1-10+deb12u14, curl/libcurl3-gnutls@7.88.1-10+deb12u14 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › curl@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl3-gnutls@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl4@7.88.1-10+deb12u14
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+deb12u14 and glibc/libc6@2.36-9+deb12u14
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › glibc/libc-bin@2.36-9+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › glibc/libc6@2.36-9+deb12u14
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+deb12u14 and glibc/libc6@2.36-9+deb12u14
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › glibc/libc-bin@2.36-9+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › glibc/libc6@2.36-9+deb12u14
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+deb12u10
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › openssh/openssh-client@1:9.2p1-2+deb12u10
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+deb12u10
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › openssh/openssh-client@1:9.2p1-2+deb12u10
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+deb12u10
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › openssh/openssh-client@1:9.2p1-2+deb12u10
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.39-1~deb12u2 and systemd/libudev1@252.39-1~deb12u2
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › systemd/libsystemd0@252.39-1~deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › systemd/libudev1@252.39-1~deb12u2
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.39-1~deb12u2 and systemd/libudev1@252.39-1~deb12u2
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › systemd/libsystemd0@252.39-1~deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › systemd/libudev1@252.39-1~deb12u2
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.39-1~deb12u2 and systemd/libudev1@252.39-1~deb12u2
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › systemd/libsystemd0@252.39-1~deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › systemd/libudev1@252.39-1~deb12u2
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-1
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › xz-utils/liblzma5@5.4.1-1
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: git
- Introduced through: git@1:2.39.5-0+deb12u3 and git/git-man@1:2.39.5-0+deb12u3
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › git@1:2.39.5-0+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › git/git-man@1:2.39.5-0+deb12u3
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
new
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u5, krb5/libk5crypto3@1.20.1-2+deb12u5 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › krb5/libgssapi-krb5-2@1.20.1-2+deb12u5
-
Introduced through: buildpack-deps@bookworm-scm › krb5/libk5crypto3@1.20.1-2+deb12u5
-
Introduced through: buildpack-deps@bookworm-scm › krb5/libkrb5-3@1.20.1-2+deb12u5
-
Introduced through: buildpack-deps@bookworm-scm › krb5/libkrb5support0@1.20.1-2+deb12u5
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 integer underflow vulnerability was found in MIT krb5 in the berval2tl_data() function in plugins/kdb/ldap/libkdb_ldap/ldap_principal2.c. The function performs an unsigned subtraction (bv_len - 2) without a prior bounds check. When bv_len is 0 or 1, the subtraction wraps to a large value which is then truncated to uint16_t, yielding 0xFFFE (65534) or 0xFFFF (65535). The subsequent malloc succeeds and memcpy reads up to 65534 bytes from a 0-1 byte buffer, resulting in a heap out-of-bounds read. The attack vector involves a malicious or compromised LDAP KDB backend returning a krbExtraData attribute with bv_len < 2, triggering the underflow when the KDC or kadmind reads principal data.
Remediation
There is no fixed version for Debian:12 krb5.
References
low severity
- Vulnerable module: coreutils
- Introduced through: coreutils@9.1-1
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › coreutils@9.1-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream coreutils package and not the coreutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
In GNU Coreutils through 8.29, chown-core.c in chown and chgrp does not prevent replacement of a plain file with a symlink during use of the POSIX "-R -L" options, which allows local users to modify the ownership of arbitrary files by leveraging a race condition.
Remediation
There is no fixed version for Debian:12 coreutils.
References
low severity
- Vulnerable module: gnupg2/dirmngr
- Introduced through: gnupg2/dirmngr@2.2.40-1.1+deb12u2, gnupg2/gnupg@2.2.40-1.1+deb12u2 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › gnupg2/dirmngr@2.2.40-1.1+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › gnupg2/gnupg@2.2.40-1.1+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › gnupg2/gnupg-l10n@2.2.40-1.1+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › gnupg2/gnupg-utils@2.2.40-1.1+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › gnupg2/gpg@2.2.40-1.1+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › gnupg2/gpg-agent@2.2.40-1.1+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › gnupg2/gpg-wks-client@2.2.40-1.1+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › gnupg2/gpg-wks-server@2.2.40-1.1+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › gnupg2/gpgconf@2.2.40-1.1+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › gnupg2/gpgsm@2.2.40-1.1+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › gnupg2/gpgv@2.2.40-1.1+deb12u2
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+deb12u2, gnupg2/gnupg@2.2.40-1.1+deb12u2 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › gnupg2/dirmngr@2.2.40-1.1+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › gnupg2/gnupg@2.2.40-1.1+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › gnupg2/gnupg-l10n@2.2.40-1.1+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › gnupg2/gnupg-utils@2.2.40-1.1+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › gnupg2/gpg@2.2.40-1.1+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › gnupg2/gpg-agent@2.2.40-1.1+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › gnupg2/gpg-wks-client@2.2.40-1.1+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › gnupg2/gpg-wks-server@2.2.40-1.1+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › gnupg2/gpgconf@2.2.40-1.1+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › gnupg2/gpgsm@2.2.40-1.1+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › gnupg2/gpgv@2.2.40-1.1+deb12u2
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: buildpack-deps@bookworm-scm › openldap/libldap-2.5-0@2.5.13+dfsg-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
slapd in OpenLDAP 2.4.45 and earlier creates a PID file after dropping privileges to a non-root account, which might allow local users to kill arbitrary processes by leveraging access to this non-root account for PID file modification before a root script executes a "kill cat /pathname" command, as demonstrated by openldap-initscript.
Remediation
There is no fixed version for Debian:12 openldap.
References
low severity
- Vulnerable module: pam/libpam-modules
- Introduced through: pam/libpam-modules@1.5.2-6+deb12u2, pam/libpam-modules-bin@1.5.2-6+deb12u2 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › pam/libpam-modules@1.5.2-6+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › pam/libpam-modules-bin@1.5.2-6+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › pam/libpam-runtime@1.5.2-6+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › pam/libpam0g@1.5.2-6+deb12u2
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: buildpack-deps@bookworm-scm › coreutils@9.1-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream coreutils package and not the coreutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
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.39-1~deb12u2 and systemd/libudev1@252.39-1~deb12u2
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › systemd/libsystemd0@252.39-1~deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › systemd/libudev1@252.39-1~deb12u2
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+deb12u14 and glibc/libc6@2.36-9+deb12u14
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › glibc/libc-bin@2.36-9+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › glibc/libc6@2.36-9+deb12u14
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+deb12u7
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › gnutls28/libgnutls30@3.7.9-2+deb12u7
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+deb12u10
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › openssh/openssh-client@1:9.2p1-2+deb12u10
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+deb12u2
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › sqlite3/libsqlite3-0@3.40.1-2+deb12u2
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: buildpack-deps@bookworm-scm › openldap/libldap-2.5-0@2.5.13+dfsg-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
libldap in certain third-party OpenLDAP packages has a certificate-validation flaw when the third-party package is asserting RFC6125 support. It considers CN even when there is a non-matching subjectAltName (SAN). This is fixed in, for example, openldap-2.4.46-10.el8 in Red Hat Enterprise Linux.
Remediation
There is no fixed version for Debian:12 openldap.
References
- 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: apt
- Introduced through: apt@2.6.1 and apt/libapt-pkg6.0@2.6.1
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › apt@2.6.1
-
Introduced through: buildpack-deps@bookworm-scm › 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: gnupg2/dirmngr
- Introduced through: gnupg2/dirmngr@2.2.40-1.1+deb12u2, gnupg2/gnupg@2.2.40-1.1+deb12u2 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › gnupg2/dirmngr@2.2.40-1.1+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › gnupg2/gnupg@2.2.40-1.1+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › gnupg2/gnupg-l10n@2.2.40-1.1+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › gnupg2/gnupg-utils@2.2.40-1.1+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › gnupg2/gpg@2.2.40-1.1+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › gnupg2/gpg-agent@2.2.40-1.1+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › gnupg2/gpg-wks-client@2.2.40-1.1+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › gnupg2/gpg-wks-server@2.2.40-1.1+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › gnupg2/gpgconf@2.2.40-1.1+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › gnupg2/gpgsm@2.2.40-1.1+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › gnupg2/gpgv@2.2.40-1.1+deb12u2
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: buildpack-deps@bookworm-scm › ncurses/libncursesw6@6.4-4
-
Introduced through: buildpack-deps@bookworm-scm › ncurses/libtinfo6@6.4-4
-
Introduced through: buildpack-deps@bookworm-scm › ncurses/ncurses-base@6.4-4
-
Introduced through: buildpack-deps@bookworm-scm › ncurses/ncurses-bin@6.4-4
NVD Description
Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
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+deb12u3, perl/libperl5.36@5.36.0-7+deb12u3 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › perl@5.36.0-7+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › perl/libperl5.36@5.36.0-7+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › perl/perl-base@5.36.0-7+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › perl/perl-modules-5.36@5.36.0-7+deb12u3
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: buildpack-deps@bookworm-scm › procps@2:4.0.2-3
-
Introduced through: buildpack-deps@bookworm-scm › procps/libproc2-0@2:4.0.2-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream procps package and not the procps package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
Under some circumstances, this weakness allows a user who has access to run the “ps” utility on a machine, the ability to write almost unlimited amounts of unfiltered data into the process heap.
Remediation
There is no fixed version for Debian:12 procps.
References
low severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6+deb12u7, python3.11/libpython3.11-minimal@3.11.2-6+deb12u7 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › python3.11@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-minimal@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-stdlib@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/python3.11-minimal@3.11.2-6+deb12u7
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
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6+deb12u7, python3.11/libpython3.11-minimal@3.11.2-6+deb12u7 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › python3.11@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-minimal@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-stdlib@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/python3.11-minimal@3.11.2-6+deb12u7
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: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.39-1~deb12u2 and systemd/libudev1@252.39-1~deb12u2
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › systemd/libsystemd0@252.39-1~deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › systemd/libudev1@252.39-1~deb12u2
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: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u2
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › expat/libexpat1@2.5.0-1+deb12u2
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
new
- Vulnerable module: bzip2/libbz2-1.0
- Introduced through: bzip2/libbz2-1.0@1.0.8-5+b1
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › 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+deb12u14, curl/libcurl3-gnutls@7.88.1-10+deb12u14 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › curl@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl3-gnutls@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl4@7.88.1-10+deb12u14
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+deb12u14, curl/libcurl3-gnutls@7.88.1-10+deb12u14 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › curl@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl3-gnutls@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl4@7.88.1-10+deb12u14
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+deb12u14, curl/libcurl3-gnutls@7.88.1-10+deb12u14 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › curl@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl3-gnutls@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl4@7.88.1-10+deb12u14
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+deb12u14, curl/libcurl3-gnutls@7.88.1-10+deb12u14 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › curl@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl3-gnutls@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl4@7.88.1-10+deb12u14
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+deb12u14, curl/libcurl3-gnutls@7.88.1-10+deb12u14 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › curl@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl3-gnutls@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl4@7.88.1-10+deb12u14
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+deb12u14, curl/libcurl3-gnutls@7.88.1-10+deb12u14 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › curl@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl3-gnutls@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl4@7.88.1-10+deb12u14
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+deb12u14, curl/libcurl3-gnutls@7.88.1-10+deb12u14 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › curl@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl3-gnutls@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl4@7.88.1-10+deb12u14
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+deb12u14, curl/libcurl3-gnutls@7.88.1-10+deb12u14 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › curl@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl3-gnutls@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl4@7.88.1-10+deb12u14
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+deb12u14, curl/libcurl3-gnutls@7.88.1-10+deb12u14 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › curl@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl3-gnutls@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl4@7.88.1-10+deb12u14
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+deb12u14, curl/libcurl3-gnutls@7.88.1-10+deb12u14 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › curl@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl3-gnutls@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl4@7.88.1-10+deb12u14
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+deb12u14, curl/libcurl3-gnutls@7.88.1-10+deb12u14 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › curl@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl3-gnutls@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl4@7.88.1-10+deb12u14
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+deb12u14, curl/libcurl3-gnutls@7.88.1-10+deb12u14 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › curl@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl3-gnutls@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl4@7.88.1-10+deb12u14
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+deb12u14, curl/libcurl3-gnutls@7.88.1-10+deb12u14 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › curl@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl3-gnutls@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl4@7.88.1-10+deb12u14
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+deb12u14, curl/libcurl3-gnutls@7.88.1-10+deb12u14 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › curl@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl3-gnutls@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl4@7.88.1-10+deb12u14
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+deb12u14, curl/libcurl3-gnutls@7.88.1-10+deb12u14 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › curl@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl3-gnutls@7.88.1-10+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › curl/libcurl4@7.88.1-10+deb12u14
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: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u2
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › expat/libexpat1@2.5.0-1+deb12u2
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+deb12u2
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › expat/libexpat1@2.5.0-1+deb12u2
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
- https://blog.hartwork.org/posts/expat-2-8-0-released/
- https://www.openwall.com/lists/oss-security/2026/04/26/1
- http://www.openwall.com/lists/oss-security/2026/04/26/1
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u14 and glibc/libc6@2.36-9+deb12u14
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › glibc/libc-bin@2.36-9+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › glibc/libc6@2.36-9+deb12u14
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+deb12u14 and glibc/libc6@2.36-9+deb12u14
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › glibc/libc-bin@2.36-9+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › glibc/libc6@2.36-9+deb12u14
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+deb12u14 and glibc/libc6@2.36-9+deb12u14
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › glibc/libc-bin@2.36-9+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › glibc/libc6@2.36-9+deb12u14
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+deb12u14 and glibc/libc6@2.36-9+deb12u14
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › glibc/libc-bin@2.36-9+deb12u14
-
Introduced through: buildpack-deps@bookworm-scm › glibc/libc6@2.36-9+deb12u14
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: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u5, krb5/libk5crypto3@1.20.1-2+deb12u5 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › krb5/libgssapi-krb5-2@1.20.1-2+deb12u5
-
Introduced through: buildpack-deps@bookworm-scm › krb5/libk5crypto3@1.20.1-2+deb12u5
-
Introduced through: buildpack-deps@bookworm-scm › krb5/libkrb5-3@1.20.1-2+deb12u5
-
Introduced through: buildpack-deps@bookworm-scm › krb5/libkrb5support0@1.20.1-2+deb12u5
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+deb12u5, krb5/libk5crypto3@1.20.1-2+deb12u5 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › krb5/libgssapi-krb5-2@1.20.1-2+deb12u5
-
Introduced through: buildpack-deps@bookworm-scm › krb5/libk5crypto3@1.20.1-2+deb12u5
-
Introduced through: buildpack-deps@bookworm-scm › krb5/libkrb5-3@1.20.1-2+deb12u5
-
Introduced through: buildpack-deps@bookworm-scm › krb5/libkrb5support0@1.20.1-2+deb12u5
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: libgcrypt20
- Introduced through: libgcrypt20@1.10.1-3+deb12u1
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › libgcrypt20@1.10.1-3+deb12u1
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: libtasn1-6
- Introduced through: libtasn1-6@4.19.0-2+deb12u1
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › libtasn1-6@4.19.0-2+deb12u1
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: openldap/libldap-2.5-0
- Introduced through: openldap/libldap-2.5-0@2.5.13+dfsg-5
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › openldap/libldap-2.5-0@2.5.13+dfsg-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
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: openssl
- Introduced through: openssl@3.0.20-1~deb12u2 and openssl/libssl3@3.0.20-1~deb12u2
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › openssl@3.0.20-1~deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › openssl/libssl3@3.0.20-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
new
- Vulnerable module: openssl
- Introduced through: openssl@3.0.20-1~deb12u2 and openssl/libssl3@3.0.20-1~deb12u2
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › openssl@3.0.20-1~deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › openssl/libssl3@3.0.20-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 attacker-controlled CMP (Certificate Management Protocol) server could trigger a NULL pointer dereference in a CMP client application.
Impact summary: A NULL pointer dereference causes a crash of the application and a Denial of Service.
An attacker controlling a CMP server (or acting as a man-in-the-middle) could craft a CMP response containing a CRMF (Certificate Request Message Format) CertRepMessage with an EncryptedValue structure where the symmAlg field has an algorithm OID but no parameters field. When the OpenSSL CMP client processes this response, the NULL dereference occurs, causing a crash of the CMP client.
Applications that process untrusted CMP/CRMF messages may be affected.
The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.
Remediation
There is no fixed version for Debian:12 openssl.
References
- https://security-tracker.debian.org/tracker/CVE-2026-42767
- https://github.com/openssl/security/commit/61a86a8cd73546c9fea916f3d304c1293e05c046
- https://github.com/openssl/security/commit/665d5254083affde9982efca7c41dd01cacc8774
- https://github.com/openssl/security/commit/810b722f772652ad48042bcc7ab07e3414b11d0f
- https://github.com/openssl/security/commit/b90ff3b1bd33b1c18e6a09936d097c2eddef8873
- https://github.com/openssl/security/commit/e6f912907fc2ec82a0fd07aae55172c5e5e3d90d
- https://github.com/openssl/openssl/commit/61a86a8cd73546c9fea916f3d304c1293e05c046
- https://github.com/openssl/openssl/commit/665d5254083affde9982efca7c41dd01cacc8774
- https://github.com/openssl/openssl/commit/810b722f772652ad48042bcc7ab07e3414b11d0f
- https://github.com/openssl/openssl/commit/b90ff3b1bd33b1c18e6a09936d097c2eddef8873
- https://github.com/openssl/openssl/commit/e6f912907fc2ec82a0fd07aae55172c5e5e3d90d
- https://openssl-library.org/news/secadv/20260609.txt
low severity
new
- Vulnerable module: pam/libpam-modules
- Introduced through: pam/libpam-modules@1.5.2-6+deb12u2, pam/libpam-modules-bin@1.5.2-6+deb12u2 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › pam/libpam-modules@1.5.2-6+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › pam/libpam-modules-bin@1.5.2-6+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › pam/libpam-runtime@1.5.2-6+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › pam/libpam0g@1.5.2-6+deb12u2
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 through 1.7.2 contains an observable timing discrepancy (CWE-208) in the pam_userdb module's plaintext-password comparison path in modules/pam_userdb/pam_userdb.c that allows a local or network-adjacent attacker able to repeatedly drive authentication through a calling service to recover the plaintext password of a target account by measuring response-timing differences. The comparison uses strncmp() (or strncasecmp() when PAM_ICASE_ARG is set) preceded by a length-equality check, so the time to reject a candidate depends on the index of the first differing byte and on whether the candidate's length matches the stored password, leaking the password length and individual prefix bytes. The vulnerable path is reached when the administrator configures pam_userdb with crypt=none, with an unrecognized crypt method, or without a crypt= argument, causing the module to store and compare credentials in plaintext.
Remediation
There is no fixed version for Debian:12 pam.
References
- https://security-tracker.debian.org/tracker/CVE-2026-54411
- https://cwe.mitre.org/data/definitions/208.html
- https://github.com/linux-pam/linux-pam
- https://github.com/linux-pam/linux-pam/blob/master/libpam/include/pam_inline.h
- https://github.com/linux-pam/linux-pam/blob/master/modules/pam_userdb/pam_userdb.c#L327
low severity
new
- Vulnerable module: perl
- Introduced through: perl@5.36.0-7+deb12u3, perl/libperl5.36@5.36.0-7+deb12u3 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › perl@5.36.0-7+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › perl/libperl5.36@5.36.0-7+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › perl/perl-base@5.36.0-7+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › perl/perl-modules-5.36@5.36.0-7+deb12u3
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
new
- Vulnerable module: perl
- Introduced through: perl@5.36.0-7+deb12u3, perl/libperl5.36@5.36.0-7+deb12u3 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › perl@5.36.0-7+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › perl/libperl5.36@5.36.0-7+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › perl/perl-base@5.36.0-7+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › perl/perl-modules-5.36@5.36.0-7+deb12u3
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.
Socket versions before 2.041 for Perl have an out-of-bounds heap read.
In Socket.xs, pack_ip_mreq_source() checks the length of its source argument before the argument is read, so the check tests the byte length carried over from the preceding multiaddr argument instead. Both addresses occupy a 4-byte field, so a valid multiaddr lets a source of any length pass the check, and the source is then copied into the 4-byte imr_sourceaddr field with a fixed-size copy. A source shorter than 4 bytes is not rejected, and the copy reads up to 3 bytes past the end of its buffer.
Calling pack_ip_mreq_source() with a source value shorter than 4 bytes copies adjacent heap memory into the returned packed structure.
Remediation
There is no fixed version for Debian:12 perl.
References
low severity
new
- Vulnerable module: perl
- Introduced through: perl@5.36.0-7+deb12u3, perl/libperl5.36@5.36.0-7+deb12u3 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › perl@5.36.0-7+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › perl/libperl5.36@5.36.0-7+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › perl/perl-base@5.36.0-7+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › perl/perl-modules-5.36@5.36.0-7+deb12u3
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+deb12u3, perl/libperl5.36@5.36.0-7+deb12u3 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › perl@5.36.0-7+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › perl/libperl5.36@5.36.0-7+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › perl/perl-base@5.36.0-7+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › perl/perl-modules-5.36@5.36.0-7+deb12u3
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+deb12u3, perl/libperl5.36@5.36.0-7+deb12u3 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › perl@5.36.0-7+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › perl/libperl5.36@5.36.0-7+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › perl/perl-base@5.36.0-7+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › perl/perl-modules-5.36@5.36.0-7+deb12u3
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+deb12u3, perl/libperl5.36@5.36.0-7+deb12u3 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › perl@5.36.0-7+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › perl/libperl5.36@5.36.0-7+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › perl/perl-base@5.36.0-7+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › perl/perl-modules-5.36@5.36.0-7+deb12u3
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: python3.11
- Introduced through: python3.11@3.11.2-6+deb12u7, python3.11/libpython3.11-minimal@3.11.2-6+deb12u7 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › python3.11@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-minimal@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-stdlib@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/python3.11-minimal@3.11.2-6+deb12u7
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+deb12u7, python3.11/libpython3.11-minimal@3.11.2-6+deb12u7 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › python3.11@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-minimal@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-stdlib@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/python3.11-minimal@3.11.2-6+deb12u7
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+deb12u7, python3.11/libpython3.11-minimal@3.11.2-6+deb12u7 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › python3.11@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-minimal@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-stdlib@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/python3.11-minimal@3.11.2-6+deb12u7
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+deb12u7, python3.11/libpython3.11-minimal@3.11.2-6+deb12u7 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › python3.11@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-minimal@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-stdlib@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/python3.11-minimal@3.11.2-6+deb12u7
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+deb12u7, python3.11/libpython3.11-minimal@3.11.2-6+deb12u7 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › python3.11@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-minimal@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-stdlib@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/python3.11-minimal@3.11.2-6+deb12u7
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
- https://github.com/python/cpython/commit/90748760d38ca3ac5fc6788a69becab905c95598
low severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6+deb12u7, python3.11/libpython3.11-minimal@3.11.2-6+deb12u7 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › python3.11@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-minimal@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-stdlib@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/python3.11-minimal@3.11.2-6+deb12u7
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+deb12u7, python3.11/libpython3.11-minimal@3.11.2-6+deb12u7 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › python3.11@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-minimal@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-stdlib@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/python3.11-minimal@3.11.2-6+deb12u7
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+deb12u7, python3.11/libpython3.11-minimal@3.11.2-6+deb12u7 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › python3.11@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-minimal@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-stdlib@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/python3.11-minimal@3.11.2-6+deb12u7
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+deb12u7, python3.11/libpython3.11-minimal@3.11.2-6+deb12u7 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › python3.11@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-minimal@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-stdlib@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/python3.11-minimal@3.11.2-6+deb12u7
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
- https://github.com/python/cpython/commit/0478bd83d82b255e0f29f613367a59d261e7eaa2
- https://github.com/python/cpython/commit/0d28f5e46e151718972dfabd91205444d0037b6d
- https://github.com/python/cpython/commit/578411982c16f753f4893532510099ef665117da
- https://github.com/python/cpython/commit/5cf47a248c35c375d610b87b2f72fd1ed454b558
- https://github.com/python/cpython/commit/74cca9a92fb7d653e404843a56b8bdc7b0afdbbf
low severity
new
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6+deb12u7, python3.11/libpython3.11-minimal@3.11.2-6+deb12u7 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › python3.11@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-minimal@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-stdlib@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/python3.11-minimal@3.11.2-6+deb12u7
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
- https://security-tracker.debian.org/tracker/CVE-2026-8328
- https://github.com/python/cpython/issues/87451
- https://github.com/python/cpython/pull/149648
- https://mail.python.org/archives/list/security-announce@python.org/thread/ITF2BAPBQEPYK3LDMPRSY435JGNHYNDP/
- https://github.com/python/cpython/commit/5dadc64673ce875ebfb24163907777dae0f6ca06
- https://github.com/python/cpython/commit/7d95a1dc7382b55cba7fdd6a110336077584a4f0
- https://github.com/python/cpython/commit/bb3446dda6c49b32e67c11dbbbf221b40be00763
- https://github.com/python/cpython/commit/c88704431ea3248ca769384c13856330976fac1d
- https://github.com/python/cpython/commit/eac4fe3b2c77693790a5ef7dfab127c1fee81bf9
low severity
new
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6+deb12u7, python3.11/libpython3.11-minimal@3.11.2-6+deb12u7 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › python3.11@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-minimal@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/libpython3.11-stdlib@3.11.2-6+deb12u7
-
Introduced through: buildpack-deps@bookworm-scm › python3.11/python3.11-minimal@3.11.2-6+deb12u7
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.
bz2.BZ2Decompressor objects could be reused after a decompression error. If an application caught the resulting OSError and retried with the same decompressor, crafted input could cause the decompressor to resume from an invalid internal state and perform out-of-bounds writes to a stack buffer. This could crash the process when processing untrusted data.
Remediation
There is no fixed version for Debian:12 python3.11.
References
- https://security-tracker.debian.org/tracker/CVE-2026-9669
- https://github.com/python/cpython/issues/150599
- https://github.com/python/cpython/pull/150600
- https://mail.python.org/archives/list/security-announce@python.org/thread/DBJZETMGUIFK7DVUWMOXHD3Z6IX2QPSX/
- http://www.openwall.com/lists/oss-security/2026/06/08/17
- https://github.com/python/cpython/commit/157a5df8cb5d82b33f918a7489e72ce95ceb12b6
- https://github.com/python/cpython/commit/5755d0f083949ff3c5bf3a37e673e24e306b036e
- https://github.com/python/cpython/commit/619a12b2e545391dc436b3af79dda22337382a6f
- https://github.com/python/cpython/commit/d3ca26983dfbccdf609f24ff5877dc3118e4702d
low severity
- Vulnerable module: shadow/login
- Introduced through: shadow/login@1:4.13+dfsg1-1+deb12u2 and shadow/passwd@1:4.13+dfsg1-1+deb12u2
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › shadow/login@1:4.13+dfsg1-1+deb12u2
-
Introduced through: buildpack-deps@bookworm-scm › shadow/passwd@1:4.13+dfsg1-1+deb12u2
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+deb12u2
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › sqlite3/libsqlite3-0@3.40.1-2+deb12u2
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+deb12u2
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › sqlite3/libsqlite3-0@3.40.1-2+deb12u2
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: util-linux
- Introduced through: util-linux@2.38.1-5+deb12u3, util-linux/bsdutils@1:2.38.1-5+deb12u3 and others
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › util-linux@2.38.1-5+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › util-linux/bsdutils@1:2.38.1-5+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › util-linux/libblkid1@2.38.1-5+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › util-linux/libmount1@2.38.1-5+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › util-linux/libsmartcols1@2.38.1-5+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › util-linux/libuuid1@2.38.1-5+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › util-linux/mount@2.38.1-5+deb12u3
-
Introduced through: buildpack-deps@bookworm-scm › util-linux/util-linux-extra@2.38.1-5+deb12u3
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: wget
- Introduced through: wget@1.21.3-1+deb12u1
Detailed paths
-
Introduced through: buildpack-deps@bookworm-scm › wget@1.21.3-1+deb12u1
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/