Vulnerabilities |
129 via 315 paths |
|---|---|
Dependencies |
146 |
Source |
Docker |
Target OS |
debian:12 |
critical severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.14+dfsg-1.3~deb12u1
- Fixed in: 2.9.14+dfsg-1.3~deb12u2
Detailed paths
-
Introduced through: postgres@12 › libxml2@2.9.14+dfsg-1.3~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
libxml2 before 2.12.10 and 2.13.x before 2.13.6 has a use-after-free in xmlSchemaIDCFillNodeTables and xmlSchemaBubbleIDCNodeTables in xmlschemas.c. To exploit this, a crafted XML document must be validated against an XML schema with certain identity constraints, or a crafted XML schema must be used.
Remediation
Upgrade Debian:12 libxml2 to version 2.9.14+dfsg-1.3~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-56171
- https://gitlab.gnome.org/GNOME/libxml2/-/issues/828
- https://security.netapp.com/advisory/ntap-20250328-0010/
- http://seclists.org/fulldisclosure/2025/Apr/13
- http://seclists.org/fulldisclosure/2025/Apr/10
- http://seclists.org/fulldisclosure/2025/Apr/11
- http://seclists.org/fulldisclosure/2025/Apr/12
- http://seclists.org/fulldisclosure/2025/Apr/4
- http://seclists.org/fulldisclosure/2025/Apr/5
- http://seclists.org/fulldisclosure/2025/Apr/8
- http://seclists.org/fulldisclosure/2025/Apr/9
- https://lists.debian.org/debian-lts-announce/2025/02/msg00028.html
critical severity
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2+deb12u1
- Fixed in: 3.40.1-2+deb12u2
Detailed paths
-
Introduced through: postgres@12 › sqlite3/libsqlite3-0@3.40.1-2+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
There exists a vulnerability in SQLite versions before 3.50.2 where the number of aggregate terms could exceed the number of columns available. This could lead to a memory corruption issue. We recommend upgrading to version 3.50.2 or above.
Remediation
Upgrade Debian:12 sqlite3 to version 3.40.1-2+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-6965
- https://www.sqlite.org/src/info/5508b56fd24016c13981ec280ecdd833007c9d8dd595edb295b984c2b487b5c8
- http://seclists.org/fulldisclosure/2025/Sep/49
- http://seclists.org/fulldisclosure/2025/Sep/53
- http://seclists.org/fulldisclosure/2025/Sep/56
- http://seclists.org/fulldisclosure/2025/Sep/57
- http://seclists.org/fulldisclosure/2025/Sep/58
- http://www.openwall.com/lists/oss-security/2025/09/06/1
critical severity
- Vulnerable module: zlib/zlib1g
- Introduced through: zlib/zlib1g@1:1.2.13.dfsg-1
Detailed paths
-
Introduced through: postgres@12 › zlib/zlib1g@1:1.2.13.dfsg-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream zlib package and not the zlib package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
MiniZip in zlib through 1.3 has an integer overflow and resultant heap-based buffer overflow in zipOpenNewFileInZip4_64 via a long filename, comment, or extra field. NOTE: MiniZip is not a supported part of the zlib product. NOTE: pyminizip through 0.2.6 is also vulnerable because it bundles an affected zlib version, and exposes the applicable MiniZip code through its compress API.
Remediation
There is no fixed version for Debian:12 zlib.
References
- https://security-tracker.debian.org/tracker/CVE-2023-45853
- http://www.openwall.com/lists/oss-security/2023/10/20/9
- http://www.openwall.com/lists/oss-security/2024/01/24/10
- https://chromium.googlesource.com/chromium/src/+/d709fb23806858847131027da95ef4c548813356
- https://chromium.googlesource.com/chromium/src/+/de29dd6c7151d3cd37cb4cf0036800ddfb1d8b61
- https://github.com/madler/zlib/blob/ac8f12c97d1afd9bafa9c710f827d40a407d3266/contrib/README.contrib#L1-L4
- https://github.com/madler/zlib/pull/843
- https://lists.debian.org/debian-lts-announce/2023/11/msg00026.html
- https://pypi.org/project/pyminizip/#history
- https://security.gentoo.org/glsa/202401-18
- https://security.netapp.com/advisory/ntap-20231130-0009/
- https://www.winimage.com/zLibDll/minizip.html
critical severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.14+dfsg-1.3~deb12u1
- Fixed in: 2.9.14+dfsg-1.3~deb12u3
Detailed paths
-
Introduced through: postgres@12 › libxml2@2.9.14+dfsg-1.3~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A use-after-free vulnerability was found in libxml2. This issue occurs when parsing XPath elements under certain circumstances when the XML schematron has the <sch:name path="..."/> schema elements. This flaw allows a malicious actor to craft a malicious XML document used as input for libxml, resulting in the program's crash using libxml or other possible undefined behaviors.
Remediation
Upgrade Debian:12 libxml2 to version 2.9.14+dfsg-1.3~deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-49794
- https://access.redhat.com/security/cve/CVE-2025-49794
- https://bugzilla.redhat.com/show_bug.cgi?id=2372373
- https://access.redhat.com/errata/RHSA-2025:10630
- https://access.redhat.com/errata/RHSA-2025:10698
- https://access.redhat.com/errata/RHSA-2025:10699
- https://access.redhat.com/errata/RHSA-2025:11580
- https://access.redhat.com/errata/RHSA-2025:12098
- https://access.redhat.com/errata/RHSA-2025:12099
- https://access.redhat.com/errata/RHSA-2025:12199
- https://access.redhat.com/errata/RHSA-2025:12239
- https://access.redhat.com/errata/RHSA-2025:12240
- https://access.redhat.com/errata/RHSA-2025:12241
- https://access.redhat.com/errata/RHSA-2025:12237
- https://access.redhat.com/errata/RHSA-2025:13335
- https://access.redhat.com/errata/RHSA-2025:15828
- https://access.redhat.com/errata/RHSA-2025:15827
- https://access.redhat.com/errata/RHSA-2025:18219
- https://access.redhat.com/errata/RHSA-2025:15397
- https://access.redhat.com/errata/RHSA-2025:18218
- https://access.redhat.com/errata/RHSA-2025:18217
- https://access.redhat.com/errata/RHSA-2025:18240
- https://access.redhat.com/errata/RHSA-2025:19020
- https://access.redhat.com/errata/RHSA-2025:19046
- https://access.redhat.com/errata/RHSA-2025:19041
- https://lists.debian.org/debian-lts-announce/2025/07/msg00014.html
- https://access.redhat.com/errata/RHSA-2025:19894
- https://access.redhat.com/errata/RHSA-2025:21913
- https://access.redhat.com/errata/RHSA-2026:0934
- https://gitlab.gnome.org/GNOME/libxml2/-/issues/931
critical severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.14+dfsg-1.3~deb12u1
- Fixed in: 2.9.14+dfsg-1.3~deb12u3
Detailed paths
-
Introduced through: postgres@12 › libxml2@2.9.14+dfsg-1.3~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability was found in libxml2. Processing certain sch:name elements from the input XML file can trigger a memory corruption issue. This flaw allows an attacker to craft a malicious XML input file that can lead libxml to crash, resulting in a denial of service or other possible undefined behavior due to sensitive data being corrupted in memory.
Remediation
Upgrade Debian:12 libxml2 to version 2.9.14+dfsg-1.3~deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-49796
- https://access.redhat.com/security/cve/CVE-2025-49796
- https://bugzilla.redhat.com/show_bug.cgi?id=2372385
- https://access.redhat.com/errata/RHSA-2025:10630
- https://access.redhat.com/errata/RHSA-2025:10698
- https://access.redhat.com/errata/RHSA-2025:10699
- https://access.redhat.com/errata/RHSA-2025:11580
- https://access.redhat.com/errata/RHSA-2025:12098
- https://access.redhat.com/errata/RHSA-2025:12099
- https://access.redhat.com/errata/RHSA-2025:12199
- https://access.redhat.com/errata/RHSA-2025:12239
- https://access.redhat.com/errata/RHSA-2025:12240
- https://access.redhat.com/errata/RHSA-2025:12241
- https://access.redhat.com/errata/RHSA-2025:12237
- https://access.redhat.com/errata/RHSA-2025:13267
- https://access.redhat.com/errata/RHSA-2025:13335
- https://access.redhat.com/errata/RHSA-2025:15828
- https://access.redhat.com/errata/RHSA-2025:15827
- https://access.redhat.com/errata/RHSA-2025:18219
- https://access.redhat.com/errata/RHSA-2025:15397
- https://access.redhat.com/errata/RHSA-2025:18218
- https://access.redhat.com/errata/RHSA-2025:18217
- https://access.redhat.com/errata/RHSA-2025:18240
- https://access.redhat.com/errata/RHSA-2025:19020
- https://access.redhat.com/errata/RHSA-2025:19046
- https://access.redhat.com/errata/RHSA-2025:19041
- https://lists.debian.org/debian-lts-announce/2025/07/msg00014.html
- https://access.redhat.com/errata/RHSA-2025:19894
- https://access.redhat.com/errata/RHSA-2025:21913
- https://access.redhat.com/errata/RHSA-2026:0934
- https://gitlab.gnome.org/GNOME/libxml2/-/issues/933
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u3
- Fixed in: 3.7.9-2+deb12u5
Detailed paths
-
Introduced through: postgres@12 › gnutls28/libgnutls30@3.7.9-2+deb12u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A flaw was found in GnuTLS. A double-free vulnerability exists in GnuTLS due to incorrect ownership handling in the export logic of Subject Alternative Name (SAN) entries containing an otherName. If the type-id OID is invalid or malformed, GnuTLS will call asn1_delete_structure() on an ASN.1 node it does not own, leading to a double-free condition when the parent function or caller later attempts to free the same structure.
This vulnerability can be triggered using only public GnuTLS APIs and may result in denial of service or memory corruption, depending on allocator behavior.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-32988
- https://access.redhat.com/security/cve/CVE-2025-32988
- https://bugzilla.redhat.com/show_bug.cgi?id=2359622
- https://access.redhat.com/errata/RHSA-2025:16115
- https://access.redhat.com/errata/RHSA-2025:16116
- https://access.redhat.com/errata/RHSA-2025:17348
- https://access.redhat.com/errata/RHSA-2025:17361
- https://access.redhat.com/errata/RHSA-2025:17415
- https://access.redhat.com/errata/RHSA-2025:19088
- https://lists.debian.org/debian-lts-announce/2025/08/msg00005.html
- http://www.openwall.com/lists/oss-security/2025/07/11/3
- https://access.redhat.com/errata/RHSA-2025:17181
- https://access.redhat.com/errata/RHSA-2025:22529
- https://lists.gnupg.org/pipermail/gnutls-help/2025-July/004883.html
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u3
- Fixed in: 3.7.9-2+deb12u5
Detailed paths
-
Introduced through: postgres@12 › gnutls28/libgnutls30@3.7.9-2+deb12u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A heap-buffer-overflow (off-by-one) flaw was found in the GnuTLS software in the template parsing logic within the certtool utility. When it reads certain settings from a template file, it allows an attacker to cause an out-of-bounds (OOB) NULL pointer write, resulting in memory corruption and a denial-of-service (DoS) that could potentially crash the system.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-32990
- https://access.redhat.com/security/cve/CVE-2025-32990
- https://bugzilla.redhat.com/show_bug.cgi?id=2359620
- https://access.redhat.com/errata/RHSA-2025:16115
- https://access.redhat.com/errata/RHSA-2025:16116
- https://access.redhat.com/errata/RHSA-2025:17348
- https://access.redhat.com/errata/RHSA-2025:17361
- https://access.redhat.com/errata/RHSA-2025:17415
- https://access.redhat.com/errata/RHSA-2025:19088
- https://lists.debian.org/debian-lts-announce/2025/08/msg00005.html
- http://www.openwall.com/lists/oss-security/2025/07/11/3
- https://access.redhat.com/errata/RHSA-2025:17181
- https://access.redhat.com/errata/RHSA-2025:22529
high severity
- Vulnerable module: perl
- Introduced through: perl@5.36.0-7+deb12u1, perl/libperl5.36@5.36.0-7+deb12u1 and others
- Fixed in: 5.36.0-7+deb12u3
Detailed paths
-
Introduced through: postgres@12 › perl@5.36.0-7+deb12u1
-
Introduced through: postgres@12 › perl/libperl5.36@5.36.0-7+deb12u1
-
Introduced through: postgres@12 › perl/perl-base@5.36.0-7+deb12u1
-
Introduced through: postgres@12 › perl/perl-modules-5.36@5.36.0-7+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
CPAN.pm before 2.35 does not verify TLS certificates when downloading distributions over HTTPS.
Remediation
Upgrade Debian:12 perl to version 5.36.0-7+deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-31484
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BM6UW55CNFUTNGD5ZRKGUKKKFDJGMFHL/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LEGCEOKFJVBJ2QQ6S2H4NAEWTUERC7SB/
- http://www.openwall.com/lists/oss-security/2023/04/29/1
- http://www.openwall.com/lists/oss-security/2023/05/03/3
- http://www.openwall.com/lists/oss-security/2023/05/03/5
- http://www.openwall.com/lists/oss-security/2023/05/07/2
- https://blog.hackeriet.no/perl-http-tiny-insecure-tls-default-affects-cpan-modules/
- https://github.com/andk/cpanpm/pull/175
- https://lists.debian.org/debian-lts-announce/2024/10/msg00017.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BM6UW55CNFUTNGD5ZRKGUKKKFDJGMFHL/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LEGCEOKFJVBJ2QQ6S2H4NAEWTUERC7SB/
- https://metacpan.org/dist/CPAN/changes
- https://security.netapp.com/advisory/ntap-20240621-0007/
- https://www.openwall.com/lists/oss-security/2023/04/18/14
high severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.14+dfsg-1.3~deb12u1
- Fixed in: 2.9.14+dfsg-1.3~deb12u2
Detailed paths
-
Introduced through: postgres@12 › libxml2@2.9.14+dfsg-1.3~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
xmlXIncludeAddNode in xinclude.c in libxml2 before 2.11.0 has a use-after-free.
Remediation
Upgrade Debian:12 libxml2 to version 2.9.14+dfsg-1.3~deb12u2 or higher.
References
high severity
- Vulnerable module: libxslt/libxslt1.1
- Introduced through: libxslt/libxslt1.1@1.1.35-1
- Fixed in: 1.1.35-1+deb12u1
Detailed paths
-
Introduced through: postgres@12 › libxslt/libxslt1.1@1.1.35-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxslt package and not the libxslt package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
xsltGetInheritedNsList in libxslt before 1.1.43 has a use-after-free issue related to exclusion of result prefixes.
Remediation
Upgrade Debian:12 libxslt to version 1.1.35-1+deb12u1 or higher.
References
high severity
- Vulnerable module: libxslt/libxslt1.1
- Introduced through: libxslt/libxslt1.1@1.1.35-1
- Fixed in: 1.1.35-1+deb12u1
Detailed paths
-
Introduced through: postgres@12 › libxslt/libxslt1.1@1.1.35-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxslt package and not the libxslt package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
numbers.c in libxslt before 1.1.43 has a use-after-free because, in nested XPath evaluations, an XPath context node can be modified but never restored. This is related to xsltNumberFormatGetValue, xsltEvalXPathPredicate, xsltEvalXPathStringNs, and xsltComputeSortResultInternal.
Remediation
Upgrade Debian:12 libxslt to version 1.1.35-1+deb12u1 or higher.
References
high severity
- Vulnerable module: pam/libpam-modules
- Introduced through: pam/libpam-modules@1.5.2-6+deb12u1, pam/libpam-modules-bin@1.5.2-6+deb12u1 and others
- Fixed in: 1.5.2-6+deb12u2
Detailed paths
-
Introduced through: postgres@12 › pam/libpam-modules@1.5.2-6+deb12u1
-
Introduced through: postgres@12 › pam/libpam-modules-bin@1.5.2-6+deb12u1
-
Introduced through: postgres@12 › pam/libpam-runtime@1.5.2-6+deb12u1
-
Introduced through: postgres@12 › pam/libpam0g@1.5.2-6+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream pam package and not the pam package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A flaw was found in linux-pam. The module pam_namespace may use access user-controlled paths without proper protection, allowing local users to elevate their privileges to root via multiple symlink attacks and race conditions.
Remediation
Upgrade Debian:12 pam to version 1.5.2-6+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-6020
- https://access.redhat.com/security/cve/CVE-2025-6020
- https://bugzilla.redhat.com/show_bug.cgi?id=2372512
- http://www.openwall.com/lists/oss-security/2025/06/17/1
- https://access.redhat.com/errata/RHSA-2025:9526
- https://access.redhat.com/errata/RHSA-2025:10024
- https://access.redhat.com/errata/RHSA-2025:10027
- https://access.redhat.com/errata/RHSA-2025:10180
- https://access.redhat.com/errata/RHSA-2025:10354
- https://access.redhat.com/errata/RHSA-2025:10357
- https://access.redhat.com/errata/RHSA-2025:10358
- https://access.redhat.com/errata/RHSA-2025:10359
- https://access.redhat.com/errata/RHSA-2025:10361
- https://access.redhat.com/errata/RHSA-2025:10362
- https://access.redhat.com/errata/RHSA-2025:10735
- https://access.redhat.com/errata/RHSA-2025:10823
- https://access.redhat.com/errata/RHSA-2025:11386
- https://access.redhat.com/errata/RHSA-2025:11487
- https://access.redhat.com/errata/RHSA-2025:14557
- https://access.redhat.com/errata/RHSA-2025:15099
- https://access.redhat.com/errata/RHSA-2025:15709
- https://access.redhat.com/errata/RHSA-2025:15828
- https://access.redhat.com/errata/RHSA-2025:15827
- https://access.redhat.com/errata/RHSA-2025:16524
- https://access.redhat.com/errata/RHSA-2025:18219
- https://lists.debian.org/debian-lts-announce/2025/09/msg00021.html
- https://access.redhat.com/errata/RHSA-2025:17181
- https://access.redhat.com/errata/RHSA-2025:20181
- https://access.redhat.com/errata/RHSA-2025:21885
- https://access.redhat.com/errata/RHSA-2025:22019
- https://access.redhat.com/errata/RHSA-2026:0934
- https://github.com/linux-pam/linux-pam/security/advisories/GHSA-f9p8-gjr4-j9gx
high severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.14+dfsg-1.3~deb12u1
- Fixed in: 2.9.14+dfsg-1.3~deb12u2
Detailed paths
-
Introduced through: postgres@12 › libxml2@2.9.14+dfsg-1.3~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
libxml2 before 2.12.10 and 2.13.x before 2.13.6 has a stack-based buffer overflow in xmlSnprintfElements in valid.c. To exploit this, DTD validation must occur for an untrusted document or untrusted DTD. NOTE: this is similar to CVE-2017-9047.
Remediation
Upgrade Debian:12 libxml2 to version 2.9.14+dfsg-1.3~deb12u2 or higher.
References
high severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.14+dfsg-1.3~deb12u1
- Fixed in: 2.9.14+dfsg-1.3~deb12u2
Detailed paths
-
Introduced through: postgres@12 › libxml2@2.9.14+dfsg-1.3~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
libxml2 before 2.12.10 and 2.13.x before 2.13.6 has a NULL pointer dereference in xmlPatMatch in pattern.c.
Remediation
Upgrade Debian:12 libxml2 to version 2.9.14+dfsg-1.3~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-27113
- https://gitlab.gnome.org/GNOME/libxml2/-/issues/861
- https://security.netapp.com/advisory/ntap-20250306-0004/
- http://seclists.org/fulldisclosure/2025/Apr/13
- http://seclists.org/fulldisclosure/2025/Apr/10
- http://seclists.org/fulldisclosure/2025/Apr/11
- http://seclists.org/fulldisclosure/2025/Apr/12
- http://seclists.org/fulldisclosure/2025/Apr/4
- http://seclists.org/fulldisclosure/2025/Apr/5
- http://seclists.org/fulldisclosure/2025/Apr/8
- http://seclists.org/fulldisclosure/2025/Apr/9
- https://lists.debian.org/debian-lts-announce/2025/02/msg00028.html
high severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.14+dfsg-1.3~deb12u1
- Fixed in: 2.9.14+dfsg-1.3~deb12u2
Detailed paths
-
Introduced through: postgres@12 › libxml2@2.9.14+dfsg-1.3~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
In libxml2 before 2.13.8 and 2.14.x before 2.14.2, xmlSchemaIDCFillNodeTables in xmlschemas.c has a heap-based buffer under-read. To exploit this, a crafted XML document must be validated against an XML schema with certain identity constraints, or a crafted XML schema must be used.
Remediation
Upgrade Debian:12 libxml2 to version 2.9.14+dfsg-1.3~deb12u2 or higher.
References
high severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.14+dfsg-1.3~deb12u1
- Fixed in: 2.9.14+dfsg-1.3~deb12u3
Detailed paths
-
Introduced through: postgres@12 › libxml2@2.9.14+dfsg-1.3~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A flaw was found in libxml2's xmlBuildQName function, where integer overflows in buffer size calculations can lead to a stack-based buffer overflow. This issue can result in memory corruption or a denial of service when processing crafted input.
Remediation
Upgrade Debian:12 libxml2 to version 2.9.14+dfsg-1.3~deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-6021
- https://access.redhat.com/errata/RHSA-2025:10630
- https://access.redhat.com/errata/RHSA-2025:10698
- https://access.redhat.com/errata/RHSA-2025:10699
- https://access.redhat.com/errata/RHSA-2025:11580
- https://access.redhat.com/errata/RHSA-2025:12098
- https://access.redhat.com/errata/RHSA-2025:12099
- https://access.redhat.com/errata/RHSA-2025:12199
- https://access.redhat.com/errata/RHSA-2025:12237
- https://access.redhat.com/errata/RHSA-2025:12239
- https://access.redhat.com/errata/RHSA-2025:12240
- https://access.redhat.com/errata/RHSA-2025:12241
- https://access.redhat.com/errata/RHSA-2025:13267
- https://access.redhat.com/errata/RHSA-2025:13289
- https://access.redhat.com/errata/RHSA-2025:13325
- https://access.redhat.com/errata/RHSA-2025:13335
- https://access.redhat.com/errata/RHSA-2025:13336
- https://access.redhat.com/errata/RHSA-2025:14059
- https://access.redhat.com/errata/RHSA-2025:14396
- https://access.redhat.com/errata/RHSA-2025:15308
- https://access.redhat.com/errata/RHSA-2025:15672
- https://access.redhat.com/security/cve/CVE-2025-6021
- https://bugzilla.redhat.com/show_bug.cgi?id=2372406
- https://access.redhat.com/errata/RHSA-2025:19020
- https://lists.debian.org/debian-lts-announce/2025/07/msg00014.html
- https://access.redhat.com/errata/RHSA-2025:11673
- https://gitlab.gnome.org/GNOME/libxml2/-/issues/926
high severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.14+dfsg-1.3~deb12u1
- Fixed in: 2.9.14+dfsg-1.3~deb12u2
Detailed paths
-
Introduced through: postgres@12 › libxml2@2.9.14+dfsg-1.3~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
In libxml2 before 2.13.8 and 2.14.x before 2.14.2, out-of-bounds memory access can occur in the Python API (Python bindings) because of an incorrect return value. This occurs in xmlPythonFileRead and xmlPythonFileReadRaw because of a difference between bytes and characters.
Remediation
Upgrade Debian:12 libxml2 to version 2.9.14+dfsg-1.3~deb12u2 or higher.
References
high severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.14+dfsg-1.3~deb12u1
- Fixed in: 2.9.14+dfsg-1.3~deb12u2
Detailed paths
-
Introduced through: postgres@12 › libxml2@2.9.14+dfsg-1.3~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
An issue was discovered in libxml2 before 2.11.7 and 2.12.x before 2.12.5. When using the XML Reader interface with DTD validation and XInclude expansion enabled, processing crafted XML documents can lead to an xmlValidatePopElement use-after-free.
Remediation
Upgrade Debian:12 libxml2 to version 2.9.14+dfsg-1.3~deb12u2 or higher.
References
high severity
- Vulnerable module: libxslt/libxslt1.1
- Introduced through: libxslt/libxslt1.1@1.1.35-1
- Fixed in: 1.1.35-1+deb12u2
Detailed paths
-
Introduced through: postgres@12 › libxslt/libxslt1.1@1.1.35-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxslt package and not the libxslt package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A flaw was found in the libxslt library. The same memory field, psvi, is used for both stylesheet and input data, which can lead to type confusion during XML transformations. This vulnerability allows an attacker to crash the application or corrupt memory. In some cases, it may lead to denial of service or unexpected behavior.
Remediation
Upgrade Debian:12 libxslt to version 1.1.35-1+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-7424
- https://access.redhat.com/security/cve/CVE-2025-7424
- https://bugzilla.redhat.com/show_bug.cgi?id=2379228
- https://lists.debian.org/debian-lts-announce/2025/09/msg00024.html
- http://seclists.org/fulldisclosure/2025/Aug/0
- http://seclists.org/fulldisclosure/2025/Jul/30
- http://seclists.org/fulldisclosure/2025/Jul/32
- http://seclists.org/fulldisclosure/2025/Jul/33
- http://seclists.org/fulldisclosure/2025/Jul/35
- http://seclists.org/fulldisclosure/2025/Jul/37
- http://www.openwall.com/lists/oss-security/2025/07/11/2
- https://gitlab.gnome.org/GNOME/libxslt/-/issues/139
high severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.15-1~deb12u1 and openssl/libssl3@3.0.15-1~deb12u1
- Fixed in: 3.0.18-1~deb12u2
Detailed paths
-
Introduced through: postgres@12 › openssl@3.0.15-1~deb12u1
-
Introduced through: postgres@12 › openssl/libssl3@3.0.15-1~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
Issue summary: Processing a malformed PKCS#12 file can trigger a NULL pointer dereference in the PKCS12_item_decrypt_d2i_ex() function.
Impact summary: A NULL pointer dereference can trigger a crash which leads to Denial of Service for an application processing PKCS#12 files.
The PKCS12_item_decrypt_d2i_ex() function does not check whether the oct parameter is NULL before dereferencing it. When called from PKCS12_unpack_p7encdata() with a malformed PKCS#12 file, this parameter can be NULL, causing a crash. The vulnerability is limited to Denial of Service and cannot be escalated to achieve code execution or memory disclosure.
Exploiting this issue requires an attacker to provide a malformed PKCS#12 file to an application that processes it. For that reason the issue was assessed as Low severity according to our Security Policy.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#12 implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.18-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-69421
- https://github.com/openssl/openssl/commit/3524a29271f8191b8fd8a5257eb05173982a097b
- https://github.com/openssl/openssl/commit/36ecb4960872a4ce04bf6f1e1f4e78d75ec0c0c7
- https://github.com/openssl/openssl/commit/4bbc8d41a72c842ce4077a8a3eccd1109aaf74bd
- https://github.com/openssl/openssl/commit/643986985cd1c21221f941129d76fe0c2785aeb3
- https://github.com/openssl/openssl/commit/a2dbc539f0f9cc63832709fa5aa33ad9495eb19c
- https://openssl-library.org/news/secadv/20260127.txt
high severity
- Vulnerable module: gnupg2/dirmngr
- Introduced through: gnupg2/dirmngr@2.2.40-1.1, gnupg2/gnupg@2.2.40-1.1 and others
- Fixed in: 2.2.40-1.1+deb12u2
Detailed paths
-
Introduced through: postgres@12 › gnupg2/dirmngr@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gnupg@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gnupg-l10n@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gnupg-utils@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gpg@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gpg-agent@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gpg-wks-client@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gpg-wks-server@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gpgconf@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gpgsm@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gpgv@2.2.40-1.1
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnupg2 package and not the gnupg2 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
In GnuPG before 2.4.9, armor_filter in g10/armor.c has two increments of an index variable where one is intended, leading to an out-of-bounds write for crafted input. (For ExtendedLTS, 2.2.51 and later are fixed versions.)
Remediation
Upgrade Debian:12 gnupg2 to version 2.2.40-1.1+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-68973
- https://github.com/gpg/gnupg/blob/ff30683418695f5d2cc9e6cf8c9418e09378ebe4/g10/armor.c#L1305-L1306
- https://github.com/gpg/gnupg/commit/115d138ba599328005c5321c0ef9f00355838ca9
- https://github.com/gpg/gnupg/compare/gnupg-2.2.50...gnupg-2.2.51
- https://media.ccc.de/v/39c3-to-sign-or-not-to-sign-practical-vulnerabilities-i
- https://news.ycombinator.com/item?id=46403200
- https://www.openwall.com/lists/oss-security/2025/12/28/5
- http://www.openwall.com/lists/oss-security/2025/12/29/11
- https://lists.debian.org/debian-lts-announce/2026/01/msg00008.html
- https://gpg.fail/memcpy
high severity
- Vulnerable module: icu/libicu72
- Introduced through: icu/libicu72@72.1-3
- Fixed in: 72.1-3+deb12u1
Detailed paths
-
Introduced through: postgres@12 › icu/libicu72@72.1-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream icu package and not the icu package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A stack buffer overflow was found in Internationl components for unicode (ICU ). While running the genrb binary, the 'subtag' struct overflowed at the SRBRoot::addTag function. This issue may lead to memory corruption and local arbitrary code execution.
Remediation
Upgrade Debian:12 icu to version 72.1-3+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-5222
- https://access.redhat.com/errata/RHSA-2025:11888
- https://access.redhat.com/errata/RHSA-2025:12083
- https://access.redhat.com/errata/RHSA-2025:12331
- https://access.redhat.com/errata/RHSA-2025:12332
- https://access.redhat.com/errata/RHSA-2025:12333
- https://access.redhat.com/security/cve/CVE-2025-5222
- https://bugzilla.redhat.com/show_bug.cgi?id=2368600
- https://lists.debian.org/debian-lts-announce/2025/06/msg00015.html
medium severity
new
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.33-1~deb12u1 and systemd/libudev1@252.33-1~deb12u1
Detailed paths
-
Introduced through: postgres@12 › systemd/libsystemd0@252.33-1~deb12u1
-
Introduced through: postgres@12 › systemd/libudev1@252.33-1~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A flaw was found in systemd. The systemd-machined service contains an Improper Access Control vulnerability due to insufficient validation of the class parameter in the RegisterMachine D-Bus (Desktop Bus) method. A local unprivileged user can exploit this by attempting to register a machine with a specific class value, which may leave behind a usable, attacker-controlled machine object. This allows the attacker to invoke methods on the privileged object, leading to the execution of arbitrary commands with root privileges on the host system.
Remediation
There is no fixed version for Debian:12 systemd.
References
medium severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u3
- Fixed in: 3.7.9-2+deb12u5
Detailed paths
-
Introduced through: postgres@12 › gnutls28/libgnutls30@3.7.9-2+deb12u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A NULL pointer dereference flaw was found in the GnuTLS software in _gnutls_figure_common_ciphersuite().
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-6395
- https://access.redhat.com/security/cve/CVE-2025-6395
- https://bugzilla.redhat.com/show_bug.cgi?id=2376755
- https://access.redhat.com/errata/RHSA-2025:16115
- https://access.redhat.com/errata/RHSA-2025:16116
- https://access.redhat.com/errata/RHSA-2025:17348
- https://access.redhat.com/errata/RHSA-2025:17361
- https://access.redhat.com/errata/RHSA-2025:17415
- https://access.redhat.com/errata/RHSA-2025:19088
- https://lists.debian.org/debian-lts-announce/2025/08/msg00005.html
- http://www.openwall.com/lists/oss-security/2025/07/11/3
- https://access.redhat.com/errata/RHSA-2025:17181
- https://access.redhat.com/errata/RHSA-2025:22529
medium severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.14+dfsg-1.3~deb12u1
- Fixed in: 2.9.14+dfsg-1.3~deb12u2
Detailed paths
-
Introduced through: postgres@12 › libxml2@2.9.14+dfsg-1.3~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
Xmlsoft Libxml2 v2.11.0 was discovered to contain an out-of-bounds read via the xmlSAX2StartElement() function at /libxml2/SAX2.c. This vulnerability allows attackers to cause a Denial of Service (DoS) via supplying a crafted XML file. NOTE: the vendor's position is that the product does not support the legacy SAX1 interface with custom callbacks; there is a crash even without crafted input.
Remediation
Upgrade Debian:12 libxml2 to version 2.9.14+dfsg-1.3~deb12u2 or higher.
References
medium severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.14+dfsg-1.3~deb12u1
- Fixed in: 2.9.14+dfsg-1.3~deb12u2
Detailed paths
-
Introduced through: postgres@12 › libxml2@2.9.14+dfsg-1.3~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
libxml2 through 2.11.5 has a use-after-free that can only occur after a certain memory allocation fails. This occurs in xmlUnlinkNode in tree.c. NOTE: the vendor's position is "I don't think these issues are critical enough to warrant a CVE ID ... because an attacker typically can't control when memory allocations fail."
Remediation
Upgrade Debian:12 libxml2 to version 2.9.14+dfsg-1.3~deb12u2 or higher.
References
medium severity
- Vulnerable module: libxslt/libxslt1.1
- Introduced through: libxslt/libxslt1.1@1.1.35-1
- Fixed in: 1.1.35-1+deb12u2
Detailed paths
-
Introduced through: postgres@12 › libxslt/libxslt1.1@1.1.35-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxslt package and not the libxslt package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
The issue was addressed with improved memory handling. This issue is fixed in macOS Ventura 13.6, tvOS 17, iOS 16.7 and iPadOS 16.7, macOS Monterey 12.7, watchOS 10, iOS 17 and iPadOS 17, macOS Sonoma 14. Processing web content may disclose sensitive information.
Remediation
Upgrade Debian:12 libxslt to version 1.1.35-1+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-40403
- https://lists.debian.org/debian-lts-announce/2025/09/msg00024.html
- http://seclists.org/fulldisclosure/2023/Oct/10
- http://seclists.org/fulldisclosure/2023/Oct/3
- http://seclists.org/fulldisclosure/2023/Oct/4
- http://seclists.org/fulldisclosure/2023/Oct/5
- http://seclists.org/fulldisclosure/2023/Oct/6
- http://seclists.org/fulldisclosure/2023/Oct/8
- http://seclists.org/fulldisclosure/2023/Oct/9
- https://support.apple.com/en-us/HT213927
- https://support.apple.com/en-us/HT213931
- https://support.apple.com/en-us/HT213932
- https://support.apple.com/en-us/HT213936
- https://support.apple.com/en-us/HT213937
- https://support.apple.com/en-us/HT213938
- https://support.apple.com/en-us/HT213940
- https://support.apple.com/kb/HT213931
- https://support.apple.com/kb/HT213932
- https://support.apple.com/kb/HT213936
- https://support.apple.com/kb/HT213937
- https://support.apple.com/kb/HT213938
- https://support.apple.com/kb/HT213940
medium severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u2, krb5/libk5crypto3@1.20.1-2+deb12u2 and others
- Fixed in: 1.20.1-2+deb12u4
Detailed paths
-
Introduced through: postgres@12 › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: postgres@12 › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: postgres@12 › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: postgres@12 › krb5/libkrb5support0@1.20.1-2+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability in the MIT Kerberos implementation allows GSSAPI-protected messages using RC4-HMAC-MD5 to be spoofed due to weaknesses in the MD5 checksum design. If RC4 is preferred over stronger encryption types, an attacker could exploit MD5 collisions to forge message integrity codes. This may lead to unauthorized message tampering.
Remediation
Upgrade Debian:12 krb5 to version 1.20.1-2+deb12u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-3576
- https://access.redhat.com/security/cve/CVE-2025-3576
- https://bugzilla.redhat.com/show_bug.cgi?id=2359465
- https://lists.debian.org/debian-lts-announce/2025/05/msg00047.html
- https://access.redhat.com/errata/RHSA-2025:8411
- https://access.redhat.com/errata/RHSA-2025:9418
- https://access.redhat.com/errata/RHSA-2025:9430
- https://access.redhat.com/errata/RHSA-2025:11487
- https://web.mit.edu/kerberos/krb5-1.22/krb5-1.22.html
- https://access.redhat.com/errata/RHSA-2025:13664
- https://access.redhat.com/errata/RHSA-2025:13777
- https://access.redhat.com/errata/RHSA-2025:15000
- https://access.redhat.com/errata/RHSA-2025:15002
- https://access.redhat.com/errata/RHSA-2025:15004
- https://access.redhat.com/errata/RHSA-2025:15001
- https://access.redhat.com/errata/RHSA-2025:15003
medium severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u2, krb5/libk5crypto3@1.20.1-2+deb12u2 and others
- Fixed in: 1.20.1-2+deb12u3
Detailed paths
-
Introduced through: postgres@12 › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: postgres@12 › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: postgres@12 › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: postgres@12 › krb5/libkrb5support0@1.20.1-2+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
Kerberos 5 (aka krb5) 1.21.2 contains a memory leak vulnerability in /krb5/src/kdc/ndr.c.
Remediation
Upgrade Debian:12 krb5 to version 1.20.1-2+deb12u3 or higher.
References
medium severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.14+dfsg-1.3~deb12u1
- Fixed in: 2.9.14+dfsg-1.3~deb12u5
Detailed paths
-
Introduced through: postgres@12 › libxml2@2.9.14+dfsg-1.3~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
Uncontrolled recursion in XPath evaluation in libxml2 up to and including version 2.9.14 allows a local attacker to cause a stack overflow via crafted expressions. XPath processing functions xmlXPathRunEval, xmlXPathCtxtCompile, and xmlXPathEvalExpr were resetting recursion depth to zero before making potentially recursive calls. When such functions were called recursively this could allow for uncontrolled recursion and lead to a stack overflow. These functions now preserve recursion depth across recursive calls, allowing recursion depth to be controlled.
Remediation
Upgrade Debian:12 libxml2 to version 2.9.14+dfsg-1.3~deb12u5 or higher.
References
medium severity
- Vulnerable module: pam/libpam-modules
- Introduced through: pam/libpam-modules@1.5.2-6+deb12u1, pam/libpam-modules-bin@1.5.2-6+deb12u1 and others
- Fixed in: 1.5.2-6+deb12u2
Detailed paths
-
Introduced through: postgres@12 › pam/libpam-modules@1.5.2-6+deb12u1
-
Introduced through: postgres@12 › pam/libpam-modules-bin@1.5.2-6+deb12u1
-
Introduced through: postgres@12 › pam/libpam-runtime@1.5.2-6+deb12u1
-
Introduced through: postgres@12 › pam/libpam0g@1.5.2-6+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream pam package and not the pam package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
linux-pam (aka Linux PAM) before 1.6.0 allows attackers to cause a denial of service (blocked login process) via mkfifo because the openat call (for protect_dir) lacks O_DIRECTORY.
Remediation
Upgrade Debian:12 pam to version 1.5.2-6+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-22365
- http://www.openwall.com/lists/oss-security/2024/01/18/3
- https://github.com/linux-pam/linux-pam
- https://github.com/linux-pam/linux-pam/commit/031bb5a5d0d950253b68138b498dc93be69a64cb
- https://github.com/linux-pam/linux-pam/releases/tag/v1.6.0
- https://lists.debian.org/debian-lts-announce/2025/09/msg00021.html
medium severity
- Vulnerable module: shadow/login
- Introduced through: shadow/login@1:4.13+dfsg1-1+b1 and shadow/passwd@1:4.13+dfsg1-1+b1
- Fixed in: 1:4.13+dfsg1-1+deb12u1
Detailed paths
-
Introduced through: postgres@12 › shadow/login@1:4.13+dfsg1-1+b1
-
Introduced through: postgres@12 › shadow/passwd@1:4.13+dfsg1-1+b1
NVD Description
Note: Versions mentioned in the description apply only to the upstream shadow package and not the shadow package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A flaw was found in shadow-utils. When asking for a new password, shadow-utils asks the password twice. If the password fails on the second attempt, shadow-utils fails in cleaning the buffer used to store the first entry. This may allow an attacker with enough access to retrieve the password from the memory.
Remediation
Upgrade Debian:12 shadow to version 1:4.13+dfsg1-1+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-4641
- https://access.redhat.com/errata/RHSA-2023:6632
- https://access.redhat.com/errata/RHSA-2023:7112
- https://access.redhat.com/errata/RHSA-2024:0417
- https://access.redhat.com/errata/RHSA-2024:2577
- https://access.redhat.com/security/cve/CVE-2023-4641
- https://bugzilla.redhat.com/show_bug.cgi?id=2215945
- https://lists.debian.org/debian-lts-announce/2025/04/msg00026.html
medium severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u3
- Fixed in: 3.7.9-2+deb12u6
Detailed paths
-
Introduced through: postgres@12 › gnutls28/libgnutls30@3.7.9-2+deb12u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A flaw was found in GnuTLS. This vulnerability allows a denial of service (DoS) by excessive CPU (Central Processing Unit) and memory consumption via specially crafted malicious certificates containing a large number of name constraints and subject alternative names (SANs).
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u6 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-14831
- https://access.redhat.com/security/cve/CVE-2025-14831
- https://bugzilla.redhat.com/show_bug.cgi?id=2423177
- https://access.redhat.com/errata/RHSA-2026:3477
- https://access.redhat.com/errata/RHSA-2026:4188
- https://gitlab.com/gnutls/gnutls/-/issues/1773
- https://access.redhat.com/errata/RHSA-2026:4655
- https://access.redhat.com/errata/RHSA-2026:4943
- https://access.redhat.com/errata/RHSA-2026:5585
- https://access.redhat.com/errata/RHSA-2026:5606
medium severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u3
- Fixed in: 3.7.9-2+deb12u4
Detailed paths
-
Introduced through: postgres@12 › gnutls28/libgnutls30@3.7.9-2+deb12u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A flaw was found in GnuTLS, which relies on libtasn1 for ASN.1 data processing. Due to an inefficient algorithm in libtasn1, decoding certain DER-encoded certificate data can take excessive time, leading to increased resource consumption. This flaw allows a remote attacker to send a specially crafted certificate, causing GnuTLS to become unresponsive or slow, resulting in a denial-of-service condition.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-12243
- https://access.redhat.com/security/cve/CVE-2024-12243
- https://bugzilla.redhat.com/show_bug.cgi?id=2344615
- https://gitlab.com/gnutls/libtasn1/-/issues/52
- https://lists.debian.org/debian-lts-announce/2025/02/msg00027.html
- https://access.redhat.com/errata/RHSA-2025:4051
- https://access.redhat.com/errata/RHSA-2025:7076
- https://access.redhat.com/errata/RHSA-2025:8020
- https://security.netapp.com/advisory/ntap-20250523-0002/
- https://access.redhat.com/errata/RHSA-2025:8385
- https://access.redhat.com/errata/RHSA-2025:17361
- https://gitlab.com/gnutls/gnutls/-/issues/1553
medium severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u3
- Fixed in: 3.7.9-2+deb12u5
Detailed paths
-
Introduced through: postgres@12 › gnutls28/libgnutls30@3.7.9-2+deb12u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A heap-buffer-overread vulnerability was found in GnuTLS in how it handles the Certificate Transparency (CT) Signed Certificate Timestamp (SCT) extension during X.509 certificate parsing. This flaw allows a malicious user to create a certificate containing a malformed SCT extension (OID 1.3.6.1.4.1.11129.2.4.2) that contains sensitive data. This issue leads to the exposure of confidential information when GnuTLS verifies certificates from certain websites when the certificate (SCT) is not checked correctly.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-32989
- https://access.redhat.com/security/cve/CVE-2025-32989
- https://bugzilla.redhat.com/show_bug.cgi?id=2359621
- https://access.redhat.com/errata/RHSA-2025:16115
- https://access.redhat.com/errata/RHSA-2025:16116
- https://access.redhat.com/errata/RHSA-2025:17348
- https://access.redhat.com/errata/RHSA-2025:17361
- https://access.redhat.com/errata/RHSA-2025:19088
- http://www.openwall.com/lists/oss-security/2025/07/11/3
- https://access.redhat.com/errata/RHSA-2025:17181
- https://access.redhat.com/errata/RHSA-2025:22529
medium severity
- Vulnerable module: libtasn1-6
- Introduced through: libtasn1-6@4.19.0-2
- Fixed in: 4.19.0-2+deb12u1
Detailed paths
-
Introduced through: postgres@12 › libtasn1-6@4.19.0-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libtasn1-6 package and not the libtasn1-6 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A flaw in libtasn1 causes inefficient handling of specific certificate data. When processing a large number of elements in a certificate, libtasn1 takes much longer than expected, which can slow down or even crash the system. This flaw allows an attacker to send a specially crafted certificate, causing a denial of service attack.
Remediation
Upgrade Debian:12 libtasn1-6 to version 4.19.0-2+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-12133
- https://access.redhat.com/security/cve/CVE-2024-12133
- https://bugzilla.redhat.com/show_bug.cgi?id=2344611
- https://gitlab.com/gnutls/libtasn1/-/issues/52
- http://www.openwall.com/lists/oss-security/2025/02/06/6
- https://lists.debian.org/debian-lts-announce/2025/02/msg00025.html
- https://access.redhat.com/errata/RHSA-2025:4049
- https://access.redhat.com/errata/RHSA-2025:7077
- https://access.redhat.com/errata/RHSA-2025:8021
- https://security.netapp.com/advisory/ntap-20250523-0003/
- https://access.redhat.com/errata/RHSA-2025:8385
- https://access.redhat.com/errata/RHSA-2025:17347
- https://gitlab.com/gnutls/libtasn1/-/blob/master/doc/security/CVE-2024-12133.md
medium severity
- Vulnerable module: gcc-12/gcc-12-base
- Introduced through: gcc-12/gcc-12-base@12.2.0-14, gcc-12/libgcc-s1@12.2.0-14 and others
- Fixed in: 12.2.0-14+deb12u1
Detailed paths
-
Introduced through: postgres@12 › gcc-12/gcc-12-base@12.2.0-14
-
Introduced through: postgres@12 › gcc-12/libgcc-s1@12.2.0-14
-
Introduced through: postgres@12 › gcc-12/libstdc++6@12.2.0-14
NVD Description
Note: Versions mentioned in the description apply only to the upstream gcc-12 package and not the gcc-12 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
DISPUTEDA failure in the -fstack-protector feature in GCC-based toolchains that target AArch64 allows an attacker to exploit an existing buffer overflow in dynamically-sized local variables in your application without this being detected. This stack-protector failure only applies to C99-style dynamically-sized local variables or those created using alloca(). The stack-protector operates as intended for statically-sized local variables.
The default behavior when the stack-protector detects an overflow is to terminate your application, resulting in controlled loss of availability. An attacker who can exploit a buffer overflow without triggering the stack-protector might be able to change program flow control to cause an uncontrolled loss of availability or to go further and affect confidentiality or integrity. NOTE: The GCC project argues that this is a missed hardening bug and not a vulnerability by itself.
Remediation
Upgrade Debian:12 gcc-12 to version 12.2.0-14+deb12u1 or higher.
References
medium severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.33-1~deb12u1 and systemd/libudev1@252.33-1~deb12u1
- Fixed in: 252.38-1~deb12u1
Detailed paths
-
Introduced through: postgres@12 › systemd/libsystemd0@252.33-1~deb12u1
-
Introduced through: postgres@12 › systemd/libudev1@252.33-1~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability was found in systemd-coredump. This flaw allows an attacker to force a SUID process to crash and replace it with a non-SUID binary to access the original's privileged process coredump, allowing the attacker to read sensitive data, such as /etc/shadow content, loaded by the original process.
A SUID binary or process has a special type of permission, which allows the process to run with the file owner's permissions, regardless of the user executing the binary. This allows the process to access more restricted data than unprivileged users or processes would be able to. An attacker can leverage this flaw by forcing a SUID process to crash and force the Linux kernel to recycle the process PID before systemd-coredump can analyze the /proc/pid/auxv file. If the attacker wins the race condition, they gain access to the original's SUID process coredump file. They can read sensitive content loaded into memory by the original binary, affecting data confidentiality.
Remediation
Upgrade Debian:12 systemd to version 252.38-1~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-4598
- https://access.redhat.com/security/cve/CVE-2025-4598
- https://bugzilla.redhat.com/show_bug.cgi?id=2369242
- https://www.openwall.com/lists/oss-security/2025/05/29/3
- http://www.openwall.com/lists/oss-security/2025/06/05/1
- http://www.openwall.com/lists/oss-security/2025/06/05/3
- https://blogs.oracle.com/linux/post/analysis-of-cve-2025-4598
- https://ciq.com/blog/the-real-danger-of-systemd-coredump-cve-2025-4598/
- https://www.openwall.com/lists/oss-security/2025/08/18/3
- http://seclists.org/fulldisclosure/2025/Jun/9
- https://lists.debian.org/debian-lts-announce/2025/07/msg00022.html
- http://www.openwall.com/lists/oss-security/2025/08/18/3
- https://access.redhat.com/errata/RHSA-2025:22660
- https://access.redhat.com/errata/RHSA-2025:22868
- https://access.redhat.com/errata/RHSA-2025:23234
- https://access.redhat.com/errata/RHSA-2025:23227
- https://access.redhat.com/errata/RHSA-2026:0414
- https://access.redhat.com/errata/RHSA-2026:1652
medium severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u3
- Fixed in: 3.7.9-2+deb12u6
Detailed paths
-
Introduced through: postgres@12 › gnutls28/libgnutls30@3.7.9-2+deb12u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A flaw was found in the GnuTLS library, specifically in the gnutls_pkcs11_token_init() function that handles PKCS#11 token initialization. When a token label longer than expected is processed, the function writes past the end of a fixed-size stack buffer. This programming error can cause the application using GnuTLS to crash or, in certain conditions, be exploited for code execution. As a result, systems or applications relying on GnuTLS may be vulnerable to a denial of service or local privilege escalation attacks.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u6 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-9820
- https://access.redhat.com/security/cve/CVE-2025-9820
- https://bugzilla.redhat.com/show_bug.cgi?id=2392528
- https://gitlab.com/gnutls/gnutls/-/commit/1d56f96f6ab5034d677136b9d50b5a75dff0faf5
- https://gitlab.com/gnutls/gnutls/-/issues/1732
- https://www.gnutls.org/security-new.html#GNUTLS-SA-2025-11-18
- http://www.openwall.com/lists/oss-security/2025/11/20/2
- https://access.redhat.com/errata/RHSA-2026:3477
- https://access.redhat.com/errata/RHSA-2026:4188
- https://access.redhat.com/errata/RHSA-2026:4655
- https://access.redhat.com/errata/RHSA-2026:4943
- https://access.redhat.com/errata/RHSA-2026:5585
- https://access.redhat.com/errata/RHSA-2026:5606
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u9, glibc/libc-l10n@2.36-9+deb12u9 and others
Detailed paths
-
Introduced through: postgres@12 › glibc/libc-bin@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/libc-l10n@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/libc6@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/locales@2.36-9+deb12u9
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
- Vulnerable module: tar
- Introduced through: tar@1.34+dfsg-1.2+deb12u1
Detailed paths
-
Introduced through: postgres@12 › 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
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2+deb12u1
Detailed paths
-
Introduced through: postgres@12 › sqlite3/libsqlite3-0@3.40.1-2+deb12u1
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: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u9, glibc/libc-l10n@2.36-9+deb12u9 and others
Detailed paths
-
Introduced through: postgres@12 › glibc/libc-bin@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/libc-l10n@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/libc6@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/locales@2.36-9+deb12u9
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
GNU Libc current is affected by: Re-mapping current loaded library with malicious ELF file. The impact is: In worst case attacker may evaluate privileges. The component is: libld. The attack vector is: Attacker sends 2 ELF files to victim and asks to run ldd on it. ldd execute code. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat.
Remediation
There is no fixed version for Debian:12 glibc.
References
- https://security-tracker.debian.org/tracker/CVE-2019-1010023
- https://support.f5.com/csp/article/K11932200?utm_source=f5support&utm_medium=RSS
- https://sourceware.org/bugzilla/show_bug.cgi?id=22851
- http://www.securityfocus.com/bid/109167
- https://ubuntu.com/security/CVE-2019-1010023
- https://support.f5.com/csp/article/K11932200?utm_source=f5support&%3Butm_medium=RSS
low severity
- Vulnerable module: perl
- Introduced through: perl@5.36.0-7+deb12u1, perl/libperl5.36@5.36.0-7+deb12u1 and others
Detailed paths
-
Introduced through: postgres@12 › perl@5.36.0-7+deb12u1
-
Introduced through: postgres@12 › perl/libperl5.36@5.36.0-7+deb12u1
-
Introduced through: postgres@12 › perl/perl-base@5.36.0-7+deb12u1
-
Introduced through: postgres@12 › perl/perl-modules-5.36@5.36.0-7+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
HTTP::Tiny before 0.083, a Perl core module since 5.13.9 and available standalone on CPAN, has an insecure default TLS configuration where users must opt in to verify certificates.
Remediation
There is no fixed version for Debian:12 perl.
References
- https://security-tracker.debian.org/tracker/CVE-2023-31486
- https://security.netapp.com/advisory/ntap-20241129-0011/
- http://www.openwall.com/lists/oss-security/2023/04/29/1
- http://www.openwall.com/lists/oss-security/2023/05/03/3
- http://www.openwall.com/lists/oss-security/2023/05/03/5
- http://www.openwall.com/lists/oss-security/2023/05/07/2
- https://blog.hackeriet.no/perl-http-tiny-insecure-tls-default-affects-cpan-modules/
- https://github.com/chansen/p5-http-tiny/pull/153
- https://hackeriet.github.io/cpan-http-tiny-overview/
- https://www.openwall.com/lists/oss-security/2023/04/18/14
- https://www.openwall.com/lists/oss-security/2023/05/03/4
- https://www.reddit.com/r/perl/comments/111tadi/psa_httptiny_disabled_ssl_verification_by_default/
low severity
new
- Vulnerable module: ncurses/libncursesw6
- Introduced through: ncurses/libncursesw6@6.4-4, ncurses/libtinfo6@6.4-4 and others
Detailed paths
-
Introduced through: postgres@12 › ncurses/libncursesw6@6.4-4
-
Introduced through: postgres@12 › ncurses/libtinfo6@6.4-4
-
Introduced through: postgres@12 › ncurses/ncurses-base@6.4-4
-
Introduced through: postgres@12 › 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
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u9, glibc/libc-l10n@2.36-9+deb12u9 and others
Detailed paths
-
Introduced through: postgres@12 › glibc/libc-bin@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/libc-l10n@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/libc6@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/locales@2.36-9+deb12u9
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+deb12u9, glibc/libc-l10n@2.36-9+deb12u9 and others
Detailed paths
-
Introduced through: postgres@12 › glibc/libc-bin@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/libc-l10n@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/libc6@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/locales@2.36-9+deb12u9
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+deb12u2, krb5/libk5crypto3@1.20.1-2+deb12u2 and others
Detailed paths
-
Introduced through: postgres@12 › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: postgres@12 › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: postgres@12 › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: postgres@12 › krb5/libkrb5support0@1.20.1-2+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
An issue was discovered in MIT Kerberos 5 (aka krb5) through 1.16. There is a variable "dbentry->n_key_data" in kadmin/dbutil/dump.c that can store 16-bit data but unknowingly the developer has assigned a "u4" variable to it, which is for 32-bit data. An attacker can use this vulnerability to affect other artifacts of the database as we know that a Kerberos database dump file contains trusted data.
Remediation
There is no fixed version for Debian:12 krb5.
References
- https://security-tracker.debian.org/tracker/CVE-2018-5709
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5709
- https://github.com/poojamnit/Kerberos-V5-1.16-Vulnerabilities/tree/master/Integer%20Overflow
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772@%3Cdev.mina.apache.org%3E
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2018-5709
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772%40%3Cdev.mina.apache.org%3E
low severity
- Vulnerable module: libgcrypt20
- Introduced through: libgcrypt20@1.10.1-3
Detailed paths
-
Introduced through: postgres@12 › libgcrypt20@1.10.1-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream libgcrypt20 package and not the libgcrypt20 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
cipher/elgamal.c in Libgcrypt through 1.8.2, when used to encrypt messages directly, improperly encodes plaintexts, which allows attackers to obtain sensitive information by reading ciphertext data (i.e., it does not have semantic security in face of a ciphertext-only attack). The Decisional Diffie-Hellman (DDH) assumption does not hold for Libgcrypt's ElGamal implementation.
Remediation
There is no fixed version for Debian:12 libgcrypt20.
References
- https://security-tracker.debian.org/tracker/CVE-2018-6829
- https://github.com/weikengchen/attack-on-libgcrypt-elgamal
- https://github.com/weikengchen/attack-on-libgcrypt-elgamal/wiki
- https://lists.gnupg.org/pipermail/gcrypt-devel/2018-February/004394.html
- https://www.oracle.com/security-alerts/cpujan2020.html
low severity
- Vulnerable module: openldap/libldap-2.5-0
- Introduced through: openldap/libldap-2.5-0@2.5.13+dfsg-5
Detailed paths
-
Introduced through: postgres@12 › 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: postgres@12 › 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: postgres@12 › 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
- Vulnerable module: coreutils
- Introduced through: coreutils@9.1-1
Detailed paths
-
Introduced through: postgres@12 › 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: ncurses/libncursesw6
- Introduced through: ncurses/libncursesw6@6.4-4, ncurses/libtinfo6@6.4-4 and others
Detailed paths
-
Introduced through: postgres@12 › ncurses/libncursesw6@6.4-4
-
Introduced through: postgres@12 › ncurses/libtinfo6@6.4-4
-
Introduced through: postgres@12 › ncurses/ncurses-base@6.4-4
-
Introduced through: postgres@12 › 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: libxml2
- Introduced through: libxml2@2.9.14+dfsg-1.3~deb12u1
Detailed paths
-
Introduced through: postgres@12 › libxml2@2.9.14+dfsg-1.3~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A flaw was identified in the interactive shell of the xmllint utility, part of the libxml2 project, where memory allocated for user input is not properly released under certain conditions. When a user submits input consisting only of whitespace, the program skips command execution but fails to free the allocated buffer. Repeating this action causes memory to continuously accumulate. Over time, this can exhaust system memory and terminate the xmllint process, creating a denial-of-service condition on the local system.
Remediation
There is no fixed version for Debian:12 libxml2.
References
low severity
- Vulnerable module: shadow/login
- Introduced through: shadow/login@1:4.13+dfsg1-1+b1 and shadow/passwd@1:4.13+dfsg1-1+b1
Detailed paths
-
Introduced through: postgres@12 › shadow/login@1:4.13+dfsg1-1+b1
-
Introduced through: postgres@12 › shadow/passwd@1:4.13+dfsg1-1+b1
NVD Description
Note: Versions mentioned in the description apply only to the upstream shadow package and not the shadow package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
initscripts in rPath Linux 1 sets insecure permissions for the /var/log/btmp file, which allows local users to obtain sensitive information regarding authentication attempts. NOTE: because sshd detects the insecure permissions and does not log certain events, this also prevents sshd from logging failed authentication attempts by remote attackers.
Remediation
There is no fixed version for Debian:12 shadow.
References
- https://security-tracker.debian.org/tracker/CVE-2007-5686
- http://www.securityfocus.com/archive/1/482129/100/100/threaded
- http://www.securityfocus.com/archive/1/482857/100/0/threaded
- https://issues.rpath.com/browse/RPL-1825
- http://secunia.com/advisories/27215
- http://www.securityfocus.com/bid/26048
- http://www.vupen.com/english/advisories/2007/3474
low severity
- Vulnerable module: 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: postgres@12 › util-linux@2.38.1-5+deb12u3
-
Introduced through: postgres@12 › util-linux/bsdutils@1:2.38.1-5+deb12u3
-
Introduced through: postgres@12 › util-linux/libblkid1@2.38.1-5+deb12u3
-
Introduced through: postgres@12 › util-linux/libmount1@2.38.1-5+deb12u3
-
Introduced through: postgres@12 › util-linux/libsmartcols1@2.38.1-5+deb12u3
-
Introduced through: postgres@12 › util-linux/libuuid1@2.38.1-5+deb12u3
-
Introduced through: postgres@12 › util-linux/mount@2.38.1-5+deb12u3
-
Introduced through: postgres@12 › 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
low severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.14+dfsg-1.3~deb12u1
Detailed paths
-
Introduced through: postgres@12 › libxml2@2.9.14+dfsg-1.3~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A flaw was found in libxml2, an XML parsing library. This uncontrolled recursion vulnerability occurs in the xmlCatalogXMLResolveURI function when an XML catalog contains a delegate URI entry that references itself. A remote attacker could exploit this configuration-dependent issue by providing a specially crafted XML catalog, leading to infinite recursion and call stack exhaustion. This ultimately results in a segmentation fault, causing a Denial of Service (DoS) by crashing affected applications.
Remediation
There is no fixed version for Debian:12 libxml2.
References
low severity
- Vulnerable module: gcc-12/gcc-12-base
- Introduced through: gcc-12/gcc-12-base@12.2.0-14, gcc-12/libgcc-s1@12.2.0-14 and others
Detailed paths
-
Introduced through: postgres@12 › gcc-12/gcc-12-base@12.2.0-14
-
Introduced through: postgres@12 › gcc-12/libgcc-s1@12.2.0-14
-
Introduced through: postgres@12 › gcc-12/libstdc++6@12.2.0-14
NVD Description
Note: Versions mentioned in the description apply only to the upstream gcc-12 package and not the gcc-12 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
libiberty/rust-demangle.c in GNU GCC 11.2 allows stack consumption in demangle_const, as demonstrated by nm-new.
Remediation
There is no fixed version for Debian:12 gcc-12.
References
- 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: libxslt/libxslt1.1
- Introduced through: libxslt/libxslt1.1@1.1.35-1
Detailed paths
-
Introduced through: postgres@12 › libxslt/libxslt1.1@1.1.35-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxslt package and not the libxslt package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A use-after-free vulnerability was found in libxslt while parsing xsl nodes that may lead to the dereference of expired pointers and application crash.
Remediation
There is no fixed version for Debian:12 libxslt.
References
low severity
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2+deb12u1
Detailed paths
-
Introduced through: postgres@12 › sqlite3/libsqlite3-0@3.40.1-2+deb12u1
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: 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: postgres@12 › util-linux@2.38.1-5+deb12u3
-
Introduced through: postgres@12 › util-linux/bsdutils@1:2.38.1-5+deb12u3
-
Introduced through: postgres@12 › util-linux/libblkid1@2.38.1-5+deb12u3
-
Introduced through: postgres@12 › util-linux/libmount1@2.38.1-5+deb12u3
-
Introduced through: postgres@12 › util-linux/libsmartcols1@2.38.1-5+deb12u3
-
Introduced through: postgres@12 › util-linux/libuuid1@2.38.1-5+deb12u3
-
Introduced through: postgres@12 › util-linux/mount@2.38.1-5+deb12u3
-
Introduced through: postgres@12 › 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: postgres@12 › 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: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u9, glibc/libc-l10n@2.36-9+deb12u9 and others
Detailed paths
-
Introduced through: postgres@12 › glibc/libc-bin@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/libc-l10n@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/libc6@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/locales@2.36-9+deb12u9
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+deb12u9, glibc/libc-l10n@2.36-9+deb12u9 and others
Detailed paths
-
Introduced through: postgres@12 › glibc/libc-bin@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/libc-l10n@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/libc6@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/locales@2.36-9+deb12u9
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: libxslt/libxslt1.1
- Introduced through: libxslt/libxslt1.1@1.1.35-1
Detailed paths
-
Introduced through: postgres@12 › libxslt/libxslt1.1@1.1.35-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxslt package and not the libxslt package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
In libxslt 1.1.29 and earlier, the EXSLT math.random function was not initialized with a random seed during startup, which could cause usage of this function to produce predictable outputs.
Remediation
There is no fixed version for Debian:12 libxslt.
References
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.33-1~deb12u1 and systemd/libudev1@252.33-1~deb12u1
Detailed paths
-
Introduced through: postgres@12 › systemd/libsystemd0@252.33-1~deb12u1
-
Introduced through: postgres@12 › systemd/libudev1@252.33-1~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
An issue was discovered in systemd 253. An attacker can modify a sealed log file such that, in some views, not all existing and sealed log messages are displayed. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability."
Remediation
There is no fixed version for Debian:12 systemd.
References
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.33-1~deb12u1 and systemd/libudev1@252.33-1~deb12u1
Detailed paths
-
Introduced through: postgres@12 › systemd/libsystemd0@252.33-1~deb12u1
-
Introduced through: postgres@12 › systemd/libudev1@252.33-1~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
An issue was discovered in systemd 253. An attacker can truncate a sealed log file and then resume log sealing such that checking the integrity shows no error, despite modifications. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability."
Remediation
There is no fixed version for Debian:12 systemd.
References
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.33-1~deb12u1 and systemd/libudev1@252.33-1~deb12u1
Detailed paths
-
Introduced through: postgres@12 › systemd/libsystemd0@252.33-1~deb12u1
-
Introduced through: postgres@12 › systemd/libudev1@252.33-1~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
An issue was discovered in systemd 253. An attacker can modify the contents of past events in a sealed log file and then adjust the file such that checking the integrity shows no error, despite modifications. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability."
Remediation
There is no fixed version for Debian:12 systemd.
References
low severity
- Vulnerable module: coreutils
- Introduced through: coreutils@9.1-1
Detailed paths
-
Introduced through: postgres@12 › coreutils@9.1-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream coreutils package and not the coreutils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
In GNU Coreutils through 8.29, chown-core.c in chown and chgrp does not prevent replacement of a plain file with a symlink during use of the POSIX "-R -L" options, which allows local users to modify the ownership of arbitrary files by leveraging a race condition.
Remediation
There is no fixed version for Debian:12 coreutils.
References
low severity
- Vulnerable module: gnupg2/dirmngr
- Introduced through: gnupg2/dirmngr@2.2.40-1.1, gnupg2/gnupg@2.2.40-1.1 and others
Detailed paths
-
Introduced through: postgres@12 › gnupg2/dirmngr@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gnupg@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gnupg-l10n@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gnupg-utils@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gpg@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gpg-agent@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gpg-wks-client@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gpg-wks-server@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gpgconf@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gpgsm@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gpgv@2.2.40-1.1
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnupg2 package and not the gnupg2 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
In GnuPG before 2.5.5, if a user chooses to import a certificate with certain crafted subkey data that lacks a valid backsig or that has incorrect usage flags, the user loses the ability to verify signatures made from certain other signing keys, aka a "verification DoS."
Remediation
There is no fixed version for Debian:12 gnupg2.
References
low severity
- Vulnerable module: gnupg2/dirmngr
- Introduced through: gnupg2/dirmngr@2.2.40-1.1, gnupg2/gnupg@2.2.40-1.1 and others
Detailed paths
-
Introduced through: postgres@12 › gnupg2/dirmngr@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gnupg@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gnupg-l10n@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gnupg-utils@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gpg@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gpg-agent@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gpg-wks-client@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gpg-wks-server@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gpgconf@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gpgsm@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gpgv@2.2.40-1.1
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnupg2 package and not the gnupg2 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
In GnuPG through 2.4.8, if a signed message has \f at the end of a plaintext line, an adversary can construct a modified message that places additional text after the signed material, such that signature verification of the modified message succeeds (although an "invalid armor" message is printed during verification). This is related to use of \f as a marker to denote truncation of a long plaintext line.
Remediation
There is no fixed version for Debian:12 gnupg2.
References
low severity
- Vulnerable module: openldap/libldap-2.5-0
- Introduced through: openldap/libldap-2.5-0@2.5.13+dfsg-5
Detailed paths
-
Introduced through: postgres@12 › openldap/libldap-2.5-0@2.5.13+dfsg-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
slapd in OpenLDAP 2.4.45 and earlier creates a PID file after dropping privileges to a non-root account, which might allow local users to kill arbitrary processes by leveraging access to this non-root account for PID file modification before a root script executes a "kill cat /pathname" command, as demonstrated by openldap-initscript.
Remediation
There is no fixed version for Debian:12 openldap.
References
low severity
- Vulnerable module: pam/libpam-modules
- Introduced through: pam/libpam-modules@1.5.2-6+deb12u1, pam/libpam-modules-bin@1.5.2-6+deb12u1 and others
Detailed paths
-
Introduced through: postgres@12 › pam/libpam-modules@1.5.2-6+deb12u1
-
Introduced through: postgres@12 › pam/libpam-modules-bin@1.5.2-6+deb12u1
-
Introduced through: postgres@12 › pam/libpam-runtime@1.5.2-6+deb12u1
-
Introduced through: postgres@12 › pam/libpam0g@1.5.2-6+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream pam package and not the pam package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability was found in PAM. The secret information is stored in memory, where the attacker can trigger the victim program to execute by sending characters to its standard input (stdin). As this occurs, the attacker can train the branch predictor to execute an ROP chain speculatively. This flaw could result in leaked passwords, such as those found in /etc/shadow while performing authentications.
Remediation
There is no fixed version for Debian:12 pam.
References
- https://security-tracker.debian.org/tracker/CVE-2024-10041
- https://access.redhat.com/security/cve/CVE-2024-10041
- https://bugzilla.redhat.com/show_bug.cgi?id=2319212
- https://access.redhat.com/errata/RHSA-2024:9941
- https://access.redhat.com/errata/RHSA-2024:10379
- https://access.redhat.com/errata/RHSA-2024:11250
low severity
- Vulnerable module: coreutils
- Introduced through: coreutils@9.1-1
Detailed paths
-
Introduced through: postgres@12 › 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://cgit.git.savannah.gnu.org/cgit/coreutils.git/commit/?id=8c9602e3a145e9596dc1a63c6ed67865814b6633
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.33-1~deb12u1 and systemd/libudev1@252.33-1~deb12u1
Detailed paths
-
Introduced through: postgres@12 › systemd/libsystemd0@252.33-1~deb12u1
-
Introduced through: postgres@12 › systemd/libudev1@252.33-1~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
systemd, when updating file permissions, allows local users to change the permissions and SELinux security contexts for arbitrary files via a symlink attack on unspecified files.
Remediation
There is no fixed version for Debian:12 systemd.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u9, glibc/libc-l10n@2.36-9+deb12u9 and others
Detailed paths
-
Introduced through: postgres@12 › glibc/libc-bin@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/libc-l10n@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/libc6@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/locales@2.36-9+deb12u9
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+deb12u3
Detailed paths
-
Introduced through: postgres@12 › gnutls28/libgnutls30@3.7.9-2+deb12u3
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: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2+deb12u1
Detailed paths
-
Introduced through: postgres@12 › sqlite3/libsqlite3-0@3.40.1-2+deb12u1
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: postgres@12 › 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: postgres@12 › apt@2.6.1
-
Introduced through: postgres@12 › 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: libxml2
- Introduced through: libxml2@2.9.14+dfsg-1.3~deb12u1
Detailed paths
-
Introduced through: postgres@12 › libxml2@2.9.14+dfsg-1.3~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A flaw was identified in the RelaxNG parser of libxml2 related to how external schema inclusions are handled. The parser does not enforce a limit on inclusion depth when resolving nested <include> directives. Specially crafted or overly complex schemas can cause excessive recursion during parsing. This may lead to stack exhaustion and application crashes, creating a denial-of-service risk.
Remediation
There is no fixed version for Debian:12 libxml2.
References
low severity
- Vulnerable module: gnupg2/dirmngr
- Introduced through: gnupg2/dirmngr@2.2.40-1.1, gnupg2/gnupg@2.2.40-1.1 and others
Detailed paths
-
Introduced through: postgres@12 › gnupg2/dirmngr@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gnupg@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gnupg-l10n@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gnupg-utils@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gpg@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gpg-agent@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gpg-wks-client@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gpg-wks-server@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gpgconf@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gpgsm@2.2.40-1.1
-
Introduced through: postgres@12 › gnupg2/gpgv@2.2.40-1.1
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnupg2 package and not the gnupg2 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB.
Remediation
There is no fixed version for Debian:12 gnupg2.
References
- https://security-tracker.debian.org/tracker/CVE-2022-3219
- https://access.redhat.com/security/cve/CVE-2022-3219
- https://bugzilla.redhat.com/show_bug.cgi?id=2127010
- https://dev.gnupg.org/D556
- https://dev.gnupg.org/T5993
- https://marc.info/?l=oss-security&m=165696590211434&w=4
- https://security.netapp.com/advisory/ntap-20230324-0001/
low severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.14+dfsg-1.3~deb12u1
Detailed paths
-
Introduced through: postgres@12 › libxml2@2.9.14+dfsg-1.3~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability was found in libxml2 up to 2.14.5. It has been declared as problematic. This vulnerability affects the function xmlParseSGMLCatalog of the component xmlcatalog. The manipulation leads to uncontrolled recursion. Attacking locally is a requirement. The exploit has been disclosed to the public and may be used. The real existence of this vulnerability is still doubted at the moment. The code maintainer explains, that "[t]he issue can only be triggered with untrusted SGML catalogs and it makes absolutely no sense to use untrusted catalogs. I also doubt that anyone is still using SGML catalogs at all."
Remediation
There is no fixed version for Debian:12 libxml2.
References
- https://security-tracker.debian.org/tracker/CVE-2025-8732
- https://drive.google.com/file/d/1woIeYVcSQB_NwfEhaVnX6MedpWJ_nqWl/view?usp=drive_link
- https://gitlab.gnome.org/GNOME/libxml2/-/issues/958
- https://gitlab.gnome.org/GNOME/libxml2/-/issues/958#note_2505853
- https://vuldb.com/?ctiid.319228
- https://vuldb.com/?id.319228
- https://vuldb.com/?submit.622285
low severity
- Vulnerable module: ncurses/libncursesw6
- Introduced through: ncurses/libncursesw6@6.4-4, ncurses/libtinfo6@6.4-4 and others
Detailed paths
-
Introduced through: postgres@12 › ncurses/libncursesw6@6.4-4
-
Introduced through: postgres@12 › ncurses/libtinfo6@6.4-4
-
Introduced through: postgres@12 › ncurses/ncurses-base@6.4-4
-
Introduced through: postgres@12 › 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/
low severity
- Vulnerable module: perl
- Introduced through: perl@5.36.0-7+deb12u1, perl/libperl5.36@5.36.0-7+deb12u1 and others
Detailed paths
-
Introduced through: postgres@12 › perl@5.36.0-7+deb12u1
-
Introduced through: postgres@12 › perl/libperl5.36@5.36.0-7+deb12u1
-
Introduced through: postgres@12 › perl/perl-base@5.36.0-7+deb12u1
-
Introduced through: postgres@12 › perl/perl-modules-5.36@5.36.0-7+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
_is_safe in the File::Temp module for Perl does not properly handle symlinks.
Remediation
There is no fixed version for Debian:12 perl.
References
- https://security-tracker.debian.org/tracker/CVE-2011-4116
- https://github.com/Perl-Toolchain-Gang/File-Temp/issues/14
- https://rt.cpan.org/Public/Bug/Display.html?id=69106
- https://seclists.org/oss-sec/2011/q4/238
- http://www.openwall.com/lists/oss-security/2011/11/04/2
- http://www.openwall.com/lists/oss-security/2011/11/04/4
low severity
- Vulnerable module: shadow/login
- Introduced through: shadow/login@1:4.13+dfsg1-1+b1 and shadow/passwd@1:4.13+dfsg1-1+b1
- Fixed in: 1:4.13+dfsg1-1+deb12u1
Detailed paths
-
Introduced through: postgres@12 › shadow/login@1:4.13+dfsg1-1+b1
-
Introduced through: postgres@12 › shadow/passwd@1:4.13+dfsg1-1+b1
NVD Description
Note: Versions mentioned in the description apply only to the upstream shadow package and not the shadow package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
In Shadow 4.13, it is possible to inject control characters into fields provided to the SUID program chfn (change finger). Although it is not possible to exploit this directly (e.g., adding a new user fails because \n is in the block list), it is possible to misrepresent the /etc/passwd file when viewed. Use of \r manipulations and Unicode characters to work around blocking of the : character make it possible to give the impression that a new user has been added. In other words, an adversary may be able to convince a system administrator to take the system offline (an indirect, social-engineered denial of service) by demonstrating that "cat /etc/passwd" shows a rogue user account.
Remediation
Upgrade Debian:12 shadow to version 1:4.13+dfsg1-1+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-29383
- https://github.com/shadow-maint/shadow/commit/e5905c4b84d4fb90aefcd96ee618411ebfac663d
- https://github.com/shadow-maint/shadow/pull/687
- https://lists.debian.org/debian-lts-announce/2025/04/msg00026.html
- https://www.trustwave.com/en-us/resources/blogs/spiderlabs-blog/cve-2023-29383-abusing-linux-chfn-to-misrepresent-etc-passwd/
- https://www.trustwave.com/en-us/resources/security-resources/security-advisories/?fid=31797
low severity
- Vulnerable module: libxslt/libxslt1.1
- Introduced through: libxslt/libxslt1.1@1.1.35-1
Detailed paths
-
Introduced through: postgres@12 › libxslt/libxslt1.1@1.1.35-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxslt package and not the libxslt package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A flaw was found in the exsltFuncResultComp() function of libxslt, which handles EXSLT <func:result> elements during stylesheet parsing. Due to improper type handling, the function may treat an XML document node as a regular XML element node, resulting in a type confusion. This can cause unexpected memory reads and potential crashes. While difficult to exploit, the flaw could lead to application instability or denial of service.
Remediation
There is no fixed version for Debian:12 libxslt.
References
low severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.14+dfsg-1.3~deb12u1
Detailed paths
-
Introduced through: postgres@12 › libxml2@2.9.14+dfsg-1.3~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A flaw was found in the libxml2 library. This uncontrolled resource consumption vulnerability occurs when processing XML catalogs that contain repeated <nextCatalog> elements pointing to the same downstream catalog. A remote attacker can exploit this by supplying crafted catalogs, causing the parser to redundantly traverse catalog chains. This leads to excessive CPU consumption and degrades application availability, resulting in a denial-of-service condition.
Remediation
There is no fixed version for Debian:12 libxml2.
References
low severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.14+dfsg-1.3~deb12u1
- Fixed in: 2.9.14+dfsg-1.3~deb12u3
Detailed paths
-
Introduced through: postgres@12 › libxml2@2.9.14+dfsg-1.3~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A flaw was found in the interactive shell of the xmllint command-line tool, used for parsing XML files. When a user inputs an overly long command, the program does not check the input size properly, which can cause it to crash. This issue might allow attackers to run harmful code in rare configurations without modern protections.
Remediation
Upgrade Debian:12 libxml2 to version 2.9.14+dfsg-1.3~deb12u3 or higher.
References
low severity
- Vulnerable module: dpkg
- Introduced through: dpkg@1.21.22
Detailed paths
-
Introduced through: postgres@12 › dpkg@1.21.22
NVD Description
Note: Versions mentioned in the description apply only to the upstream dpkg package and not the dpkg package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
It was discovered that dpkg-deb does not properly sanitize directory permissions when extracting a control member into a temporary directory, which is documented as being a safe operation even on untrusted data. This may result in leaving temporary files behind on cleanup. Given automated and repeated execution of dpkg-deb commands on adversarial .deb packages or with well compressible files, placed inside a directory with permissions not allowing removal by a non-root user, this can end up in a DoS scenario due to causing disk quota exhaustion or disk full conditions.
Remediation
There is no fixed version for Debian:12 dpkg.
References
low severity
new
- Vulnerable module: dpkg
- Introduced through: dpkg@1.21.22
Detailed paths
-
Introduced through: postgres@12 › dpkg@1.21.22
NVD Description
Note: Versions mentioned in the description apply only to the upstream dpkg package and not the dpkg package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
It was discovered that dpkg-deb (a component of dpkg, the Debian package management system) does not properly validate the end of the data stream when uncompressing a zstd-compressed .deb archive, which may result in denial of service (infinite loop spinning the CPU).
Remediation
There is no fixed version for Debian:12 dpkg.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u9, glibc/libc-l10n@2.36-9+deb12u9 and others
- Fixed in: 2.36-9+deb12u10
Detailed paths
-
Introduced through: postgres@12 › glibc/libc-bin@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/libc-l10n@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/libc6@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/locales@2.36-9+deb12u9
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
When the assert() function in the GNU C Library versions 2.13 to 2.40 fails, it does not allocate enough space for the assertion failure message string and size information, which may lead to a buffer overflow if the message string size aligns to page size.
Remediation
Upgrade Debian:12 glibc to version 2.36-9+deb12u10 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-0395
- https://sourceware.org/bugzilla/show_bug.cgi?id=32582
- https://sourceware.org/git/?p=glibc.git;a=blob;f=advisories/GLIBC-SA-2025-0001
- https://sourceware.org/pipermail/libc-announce/2025/000044.html
- https://www.openwall.com/lists/oss-security/2025/01/22/4
- http://www.openwall.com/lists/oss-security/2025/01/22/4
- http://www.openwall.com/lists/oss-security/2025/01/23/2
- https://security.netapp.com/advisory/ntap-20250228-0006/
- http://www.openwall.com/lists/oss-security/2025/04/13/1
- http://www.openwall.com/lists/oss-security/2025/04/24/7
- https://lists.debian.org/debian-lts-announce/2025/04/msg00039.html
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u9, glibc/libc-l10n@2.36-9+deb12u9 and others
Detailed paths
-
Introduced through: postgres@12 › glibc/libc-bin@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/libc-l10n@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/libc6@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/locales@2.36-9+deb12u9
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
Calling wordexp with WRDE_REUSE in conjunction with WRDE_APPEND in the GNU C Library version 2.0 to version 2.42 may cause the interface to return uninitialized memory in the we_wordv member, which on subsequent calls to wordfree may abort the process.
Remediation
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+deb12u9, glibc/libc-l10n@2.36-9+deb12u9 and others
- Fixed in: 2.36-9+deb12u11
Detailed paths
-
Introduced through: postgres@12 › glibc/libc-bin@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/libc-l10n@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/libc6@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/locales@2.36-9+deb12u9
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
Untrusted LD_LIBRARY_PATH environment variable vulnerability in the GNU C Library version 2.27 to 2.38 allows attacker controlled loading of dynamically shared library in statically compiled setuid binaries that call dlopen (including internal dlopen calls after setlocale or calls to NSS functions such as getaddrinfo).
Remediation
Upgrade Debian:12 glibc to version 2.36-9+deb12u11 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-4802
- https://sourceware.org/bugzilla/show_bug.cgi?id=32976
- https://sourceware.org/cgit/glibc/commit/?id=1e18586c5820e329f741d5c710275e165581380e
- http://www.openwall.com/lists/oss-security/2025/05/16/7
- http://www.openwall.com/lists/oss-security/2025/05/17/2
- https://lists.debian.org/debian-lts-announce/2025/05/msg00033.html
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u9, glibc/libc-l10n@2.36-9+deb12u9 and others
- Fixed in: 2.36-9+deb12u13
Detailed paths
-
Introduced through: postgres@12 › glibc/libc-bin@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/libc-l10n@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/libc6@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/locales@2.36-9+deb12u9
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
The regcomp function in the GNU C library version from 2.4 to 2.41 is subject to a double free if some previous allocation fails. It can be accomplished either by a malloc failure or by using an interposed malloc that injects random malloc failures. The double free can allow buffer manipulation depending of how the regex is constructed. This issue affects all architectures and ABIs supported by the GNU C library.
Remediation
Upgrade Debian:12 glibc to version 2.36-9+deb12u13 or higher.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u9, glibc/libc-l10n@2.36-9+deb12u9 and others
Detailed paths
-
Introduced through: postgres@12 › glibc/libc-bin@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/libc-l10n@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/libc6@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/locales@2.36-9+deb12u9
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
Passing too large an alignment to the memalign suite of functions (memalign, posix_memalign, aligned_alloc) in the GNU C Library version 2.30 to 2.42 may result in an integer overflow, which could consequently result in a heap corruption.
Note that the attacker must have control over both, the size as well as the alignment arguments of the memalign function to be able to exploit this. The size parameter must be close enough to PTRDIFF_MAX so as to overflow size_t along with the large alignment argument. This limits the malicious inputs for the alignment for memalign to the range [1<<62+ 1, 1<<63] and exactly 1<<63 for posix_memalign and aligned_alloc.
Typically the alignment argument passed to such functions is a known constrained quantity (e.g. page size, block size, struct sizes) and is not attacker controlled, because of which this may not be easily exploitable in practice. An application bug could potentially result in the input alignment being too large, e.g. due to a different buffer overflow or integer overflow in the application or its dependent libraries, but that is again an uncommon usage pattern given typical sources of alignments.
Remediation
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+deb12u9, glibc/libc-l10n@2.36-9+deb12u9 and others
Detailed paths
-
Introduced through: postgres@12 › glibc/libc-bin@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/libc-l10n@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/libc6@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/locales@2.36-9+deb12u9
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
Calling getnetbyaddr or getnetbyaddr_r with a configured nsswitch.conf that specifies the library's DNS backend for networks and queries for a zero-valued network in the GNU C Library version 2.0 to version 2.42 can leak stack contents to the configured DNS resolver.
Remediation
There is no fixed version for Debian:12 glibc.
References
low severity
new
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u9, glibc/libc-l10n@2.36-9+deb12u9 and others
Detailed paths
-
Introduced through: postgres@12 › glibc/libc-bin@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/libc-l10n@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/libc6@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/locales@2.36-9+deb12u9
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
Calling gethostbyaddr or gethostbyaddr_r with a configured nsswitch.conf that specifies the library's DNS backend in the GNU C Library version 2.34 to version 2.43 could, with a crafted response from the configured DNS server, result in a violation of the DNS specification that causes the application to treat a non-answer section of the DNS response as a valid answer.
Remediation
There is no fixed version for Debian:12 glibc.
References
low severity
new
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u9, glibc/libc-l10n@2.36-9+deb12u9 and others
Detailed paths
-
Introduced through: postgres@12 › glibc/libc-bin@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/libc-l10n@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/libc6@2.36-9+deb12u9
-
Introduced through: postgres@12 › glibc/locales@2.36-9+deb12u9
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
Calling gethostbyaddr or gethostbyaddr_r with a configured nsswitch.conf that specifies the library's DNS backend in the GNU C library version 2.34 to version 2.43 could result in an invalid DNS hostname being returned to the caller in violation of the DNS specification.
Remediation
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+deb12u2, krb5/libk5crypto3@1.20.1-2+deb12u2 and others
Detailed paths
-
Introduced through: postgres@12 › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: postgres@12 › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: postgres@12 › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: postgres@12 › krb5/libkrb5support0@1.20.1-2+deb12u2
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+deb12u2, krb5/libk5crypto3@1.20.1-2+deb12u2 and others
- Fixed in: 1.20.1-2+deb12u3
Detailed paths
-
Introduced through: postgres@12 › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: postgres@12 › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: postgres@12 › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: postgres@12 › krb5/libkrb5support0@1.20.1-2+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
In MIT Kerberos 5 (aka krb5) before 1.22 (with incremental propagation), there is an integer overflow for a large update size to resize() in kdb_log.c. An authenticated attacker can cause an out-of-bounds write and kadmind daemon crash.
Remediation
Upgrade Debian:12 krb5 to version 1.20.1-2+deb12u3 or higher.
References
low severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u2, krb5/libk5crypto3@1.20.1-2+deb12u2 and others
Detailed paths
-
Introduced through: postgres@12 › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: postgres@12 › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: postgres@12 › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: postgres@12 › krb5/libkrb5support0@1.20.1-2+deb12u2
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: libcap2
- Introduced through: libcap2@1:2.66-4
- Fixed in: 1:2.66-4+deb12u1
Detailed paths
-
Introduced through: postgres@12 › libcap2@1:2.66-4
NVD Description
Note: Versions mentioned in the description apply only to the upstream libcap2 package and not the libcap2 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
The PAM module pam_cap.so of libcap configuration supports group names starting with “@”, during actual parsing, configurations not starting with “@” are incorrectly recognized as group names. This may result in nonintended users being granted an inherited capability set, potentially leading to security risks. Attackers can exploit this vulnerability to achieve local privilege escalation on systems where /etc/security/capability.conf is used to configure user inherited privileges by constructing specific usernames.
Remediation
Upgrade Debian:12 libcap2 to version 1:2.66-4+deb12u1 or higher.
References
low severity
- Vulnerable module: libgcrypt20
- Introduced through: libgcrypt20@1.10.1-3
Detailed paths
-
Introduced through: postgres@12 › libgcrypt20@1.10.1-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream libgcrypt20 package and not the libgcrypt20 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A timing-based side-channel flaw was found in libgcrypt's RSA implementation. This issue may allow a remote attacker to initiate a Bleichenbacher-style attack, which can lead to the decryption of RSA ciphertexts.
Remediation
There is no fixed version for Debian:12 libgcrypt20.
References
- https://security-tracker.debian.org/tracker/CVE-2024-2236
- https://access.redhat.com/errata/RHSA-2024:9404
- https://bugzilla.redhat.com/show_bug.cgi?id=2268268
- https://access.redhat.com/errata/RHSA-2025:3534
- https://access.redhat.com/errata/RHSA-2025:3530
- https://access.redhat.com/security/cve/CVE-2024-2236
- https://bugzilla.redhat.com/show_bug.cgi?id=2245218
low severity
- Vulnerable module: libtasn1-6
- Introduced through: libtasn1-6@4.19.0-2
Detailed paths
-
Introduced through: postgres@12 › libtasn1-6@4.19.0-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libtasn1-6 package and not the libtasn1-6 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
Stack-based buffer overflow in libtasn1 version: v4.20.0. The function fails to validate the size of input data resulting in a buffer overflow in asn1_expend_octet_string.
Remediation
There is no fixed version for Debian:12 libtasn1-6.
References
low severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.14+dfsg-1.3~deb12u1
- Fixed in: 2.9.14+dfsg-1.3~deb12u2
Detailed paths
-
Introduced through: postgres@12 › libxml2@2.9.14+dfsg-1.3~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
An issue was discovered in xmllint (from libxml2) before 2.11.8 and 2.12.x before 2.12.7. Formatting error messages with xmllint --htmlout can result in a buffer over-read in xmlHTMLPrintFileContext in xmllint.c.
Remediation
Upgrade Debian:12 libxml2 to version 2.9.14+dfsg-1.3~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-34459
- https://lists.debian.org/debian-lts-announce/2025/07/msg00014.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/5HVUXKYTBWT3G5DEEQX62STJQBY367NL/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/INKSSLW5VMZIXHRPZBAW4TJUX5SQKARG/
- https://gitlab.gnome.org/GNOME/libxml2/-/issues/720
- https://gitlab.gnome.org/GNOME/libxml2/-/releases/v2.11.8
- https://gitlab.gnome.org/GNOME/libxml2/-/releases/v2.12.7
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/5HVUXKYTBWT3G5DEEQX62STJQBY367NL/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/INKSSLW5VMZIXHRPZBAW4TJUX5SQKARG/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VRDJCNQP32LV56KESUQ5SNZKAJWSZZRI/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VRDJCNQP32LV56KESUQ5SNZKAJWSZZRI/
low severity
- Vulnerable module: llvm-toolchain-16/libllvm16
- Introduced through: llvm-toolchain-16/libllvm16@1:16.0.6-15~deb12u1
Detailed paths
-
Introduced through: postgres@12 › llvm-toolchain-16/libllvm16@1:16.0.6-15~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream llvm-toolchain-16 package and not the llvm-toolchain-16 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
LLVM before 18.1.3 generates code in which the LR register can be overwritten without data being saved to the stack, and thus there can sometimes be an exploitable error in the flow of control. This affects the ARM backend and can be demonstrated with Clang. NOTE: the vendor perspective is "we don't have strong objections for a CVE to be created ... It does seem that the likelihood of this miscompile enabling an exploit remains very low, because the miscompile resulting in this JOP gadget is such that the function is most likely to crash on most valid inputs to the function. So, if this function is covered by any testing, the miscompile is most likely to be discovered before the binary is shipped to production."
Remediation
There is no fixed version for Debian:12 llvm-toolchain-16.
References
low severity
- Vulnerable module: llvm-toolchain-16/libllvm16
- Introduced through: llvm-toolchain-16/libllvm16@1:16.0.6-15~deb12u1
Detailed paths
-
Introduced through: postgres@12 › llvm-toolchain-16/libllvm16@1:16.0.6-15~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream llvm-toolchain-16 package and not the llvm-toolchain-16 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
When using Arm Cortex-M Security Extensions (CMSE), Secure stack contents can be leaked to Non-secure state via floating-point registers when a Secure to Non-secure function call is made that returns a floating-point value and when this is the first use of floating-point since entering Secure state. This allows an attacker to read a limited quantity of Secure stack contents with an impact on confidentiality. This issue is specific to code generated using LLVM-based compilers.
Remediation
There is no fixed version for Debian:12 llvm-toolchain-16.
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: postgres@12 › 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.15-1~deb12u1 and openssl/libssl3@3.0.15-1~deb12u1
- Fixed in: 3.0.16-1~deb12u1
Detailed paths
-
Introduced through: postgres@12 › openssl@3.0.15-1~deb12u1
-
Introduced through: postgres@12 › openssl/libssl3@3.0.15-1~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
Issue summary: A timing side-channel which could potentially allow recovering the private key exists in the ECDSA signature computation.
Impact summary: A timing side-channel in ECDSA signature computations could allow recovering the private key by an attacker. However, measuring the timing would require either local access to the signing application or a very fast network connection with low latency.
There is a timing signal of around 300 nanoseconds when the top word of the inverted ECDSA nonce value is zero. This can happen with significant probability only for some of the supported elliptic curves. In particular the NIST P-521 curve is affected. To be able to measure this leak, the attacker process must either be located in the same physical computer or must have a very fast network connection with low latency. For that reason the severity of this vulnerability is Low.
The FIPS modules in 3.4, 3.3, 3.2, 3.1 and 3.0 are affected by this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.16-1~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-13176
- https://github.com/openssl/openssl/commit/07272b05b04836a762b4baa874958af51d513844
- https://github.com/openssl/openssl/commit/2af62e74fb59bc469506bc37eb2990ea408d9467
- https://github.com/openssl/openssl/commit/392dcb336405a0c94486aa6655057f59fd3a0902
- https://github.com/openssl/openssl/commit/4b1cb94a734a7d4ec363ac0a215a25c181e11f65
- https://github.com/openssl/openssl/commit/77c608f4c8857e63e98e66444e2e761c9627916f
- https://github.openssl.org/openssl/extended-releases/commit/0d5fd1ab987f7571e2c955d8d8b638fc0fb54ded
- https://github.openssl.org/openssl/extended-releases/commit/a2639000db19878d5d89586ae7b725080592ae86
- https://openssl-library.org/news/secadv/20250120.txt
- http://www.openwall.com/lists/oss-security/2025/01/20/2
- https://security.netapp.com/advisory/ntap-20250124-0005/
- https://security.netapp.com/advisory/ntap-20250418-0010/
- https://lists.debian.org/debian-lts-announce/2025/05/msg00028.html
- https://security.netapp.com/advisory/ntap-20250502-0006/
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.15-1~deb12u1 and openssl/libssl3@3.0.15-1~deb12u1
- Fixed in: 3.0.18-1~deb12u2
Detailed paths
-
Introduced through: postgres@12 › openssl@3.0.15-1~deb12u1
-
Introduced through: postgres@12 › openssl/libssl3@3.0.15-1~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
Issue summary: Parsing CMS AuthEnvelopedData or EnvelopedData message with maliciously crafted AEAD parameters can trigger a stack buffer overflow.
Impact summary: A stack buffer overflow may lead to a crash, causing Denial of Service, or potentially remote code execution.
When parsing CMS (Auth)EnvelopedData structures that use AEAD ciphers such as AES-GCM, the IV (Initialization Vector) encoded in the ASN.1 parameters is copied into a fixed-size stack buffer without verifying that its length fits the destination. An attacker can supply a crafted CMS message with an oversized IV, causing a stack-based out-of-bounds write before any authentication or tag verification occurs.
Applications and services that parse untrusted CMS or PKCS#7 content using AEAD ciphers (e.g., S/MIME (Auth)EnvelopedData with AES-GCM) are vulnerable. Because the overflow occurs prior to authentication, no valid key material is required to trigger it. While exploitability to remote code execution depends on platform and toolchain mitigations, the stack-based write primitive represents a severe risk.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the CMS implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3 and 3.0 are vulnerable to this issue.
OpenSSL 1.1.1 and 1.0.2 are not affected by this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.18-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-15467
- https://github.com/openssl/openssl/commit/2c8f0e5fa9b6ee5508a0349e4572ddb74db5a703
- https://github.com/openssl/openssl/commit/5f26d4202f5b89664c5c3f3c62086276026ba9a9
- https://github.com/openssl/openssl/commit/6ced0fe6b10faa560e410e3ee8d6c82f06c65ea3
- https://github.com/openssl/openssl/commit/ce39170276daec87f55c39dad1f629b56344429e
- https://github.com/openssl/openssl/commit/d0071a0799f20cc8101730145349ed4487c268dc
- https://openssl-library.org/news/secadv/20260127.txt
- http://www.openwall.com/lists/oss-security/2026/01/27/10
- http://www.openwall.com/lists/oss-security/2026/02/25/6
- https://github.com/guiimoraes/CVE-2025-15467
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.15-1~deb12u1 and openssl/libssl3@3.0.15-1~deb12u1
Detailed paths
-
Introduced through: postgres@12 › openssl@3.0.15-1~deb12u1
-
Introduced through: postgres@12 › openssl/libssl3@3.0.15-1~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
OpenSSL 3.0.0 through 3.3.2 on the PowerPC architecture is vulnerable to a Minerva attack, exploitable by measuring the time of signing of random messages using the EVP_DigestSign API, and then using the private key to extract the K value (nonce) from the signatures. Next, based on the bit size of the extracted nonce, one can compare the signing time of full-sized nonces to signatures that used smaller nonces, via statistical tests. There is a side-channel in the P-364 curve that allows private key extraction (also, there is a dependency between the bit size of K and the size of the side channel). NOTE: This CVE is disputed because the OpenSSL security policy explicitly notes that any side channels which require same physical system to be detected are outside of the threat model for the software. The timing signal is so small that it is infeasible to be detected without having the attacking process running on the same physical system.
Remediation
There is no fixed version for Debian:12 openssl.
References
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.15-1~deb12u1 and openssl/libssl3@3.0.15-1~deb12u1
- Fixed in: 3.0.18-1~deb12u2
Detailed paths
-
Introduced through: postgres@12 › openssl@3.0.15-1~deb12u1
-
Introduced through: postgres@12 › openssl/libssl3@3.0.15-1~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
Issue summary: Writing large, newline-free data into a BIO chain using the line-buffering filter where the next BIO performs short writes can trigger a heap-based out-of-bounds write.
Impact summary: This out-of-bounds write can cause memory corruption which typically results in a crash, leading to Denial of Service for an application.
The line-buffering BIO filter (BIO_f_linebuffer) is not used by default in TLS/SSL data paths. In OpenSSL command-line applications, it is typically only pushed onto stdout/stderr on VMS systems. Third-party applications that explicitly use this filter with a BIO chain that can short-write and that write large, newline-free data influenced by an attacker would be affected. However, the circumstances where this could happen are unlikely to be under attacker control, and BIO_f_linebuffer is unlikely to be handling non-curated data controlled by an attacker. For that reason the issue was assessed as Low severity.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the BIO implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.18-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-68160
- https://github.com/openssl/openssl/commit/384011202af92605d926fafe4a0bcd6b65d162ad
- https://github.com/openssl/openssl/commit/475c466ef2fbd8fc1df6fae1c3eed9c813fc8ff6
- https://github.com/openssl/openssl/commit/4c96fbba618e1940f038012506ee9e21d32ee12c
- https://github.com/openssl/openssl/commit/6845c3b6460a98b1ec4e463baa2ea1a63a32d7c0
- https://github.com/openssl/openssl/commit/68a7cd2e2816c3a02f4d45a2ce43fc04fac97096
- https://openssl-library.org/news/secadv/20260127.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.15-1~deb12u1 and openssl/libssl3@3.0.15-1~deb12u1
- Fixed in: 3.0.18-1~deb12u2
Detailed paths
-
Introduced through: postgres@12 › openssl@3.0.15-1~deb12u1
-
Introduced through: postgres@12 › openssl/libssl3@3.0.15-1~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
Issue summary: When using the low-level OCB API directly with AES-NI or<br>other hardware-accelerated code paths, inputs whose length is not a multiple<br>of 16 bytes can leave the final partial block unencrypted and unauthenticated.<br><br>Impact summary: The trailing 1-15 bytes of a message may be exposed in<br>cleartext on encryption and are not covered by the authentication tag,<br>allowing an attacker to read or tamper with those bytes without detection.<br><br>The low-level OCB encrypt and decrypt routines in the hardware-accelerated<br>stream path process full 16-byte blocks but do not advance the input/output<br>pointers. The subsequent tail-handling code then operates on the original<br>base pointers, effectively reprocessing the beginning of the buffer while<br>leaving the actual trailing bytes unprocessed. The authentication checksum<br>also excludes the true tail bytes.<br><br>However, typical OpenSSL consumers using EVP are not affected because the<br>higher-level EVP and provider OCB implementations split inputs so that full<br>blocks and trailing partial blocks are processed in separate calls, avoiding<br>the problematic code path. Additionally, TLS does not use OCB ciphersuites.<br>The vulnerability only affects applications that call the low-level<br>CRYPTO_ocb128_encrypt() or CRYPTO_ocb128_decrypt() functions directly with<br>non-block-aligned lengths in a single call on hardware-accelerated builds.<br>For these reasons the issue was assessed as Low severity.<br><br>The FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected<br>by this issue, as OCB mode is not a FIPS-approved algorithm.<br><br>OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.<br><br>OpenSSL 1.0.2 is not affected by this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.18-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-69418
- https://github.com/openssl/openssl/commit/372fc5c77529695b05b4f5b5187691a57ef5dffc
- https://github.com/openssl/openssl/commit/4016975d4469cd6b94927c607f7c511385f928d8
- https://github.com/openssl/openssl/commit/52d23c86a54adab5ee9f80e48b242b52c4cc2347
- https://github.com/openssl/openssl/commit/a7589230356d908c0eca4b969ec4f62106f4f5ae
- https://github.com/openssl/openssl/commit/ed40856d7d4ba6cb42779b6770666a65f19cb977
- https://openssl-library.org/news/secadv/20260127.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.15-1~deb12u1 and openssl/libssl3@3.0.15-1~deb12u1
- Fixed in: 3.0.18-1~deb12u2
Detailed paths
-
Introduced through: postgres@12 › openssl@3.0.15-1~deb12u1
-
Introduced through: postgres@12 › openssl/libssl3@3.0.15-1~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
Issue summary: Calling PKCS12_get_friendlyname() function on a maliciously crafted PKCS#12 file with a BMPString (UTF-16BE) friendly name containing non-ASCII BMP code point can trigger a one byte write before the allocated buffer.
Impact summary: The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service.
The OPENSSL_uni2utf8() function performs a two-pass conversion of a PKCS#12 BMPString (UTF-16BE) to UTF-8. In the second pass, when emitting UTF-8 bytes, the helper function bmp_to_utf8() incorrectly forwards the remaining UTF-16 source byte count as the destination buffer capacity to UTF8_putc(). For BMP code points above U+07FF, UTF-8 requires three bytes, but the forwarded capacity can be just two bytes. UTF8_putc() then returns -1, and this negative value is added to the output length without validation, causing the length to become negative. The subsequent trailing NUL byte is then written at a negative offset, causing write outside of heap allocated buffer.
The vulnerability is reachable via the public PKCS12_get_friendlyname() API when parsing attacker-controlled PKCS#12 files. While PKCS12_parse() uses a different code path that avoids this issue, PKCS12_get_friendlyname() directly invokes the vulnerable function. Exploitation requires an attacker to provide a malicious PKCS#12 file to be parsed by the application and the attacker can just trigger a one zero byte write before the allocated buffer. For that reason the issue was assessed as Low severity according to our Security Policy.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#12 implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.
OpenSSL 1.0.2 is not affected by this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.18-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-69419
- https://github.com/openssl/openssl/commit/41be0f216404f14457bbf3b9cc488dba60b49296
- https://github.com/openssl/openssl/commit/7e9cac9832e4705b91987c2474ed06a37a93cecb
- https://github.com/openssl/openssl/commit/a26a90d38edec3748566129d824e664b54bee2e2
- https://github.com/openssl/openssl/commit/cda12de3bc0e333ea8d2c6fd15001dbdaf280015
- https://github.com/openssl/openssl/commit/ff628933755075446bca8307e8417c14d164b535
- https://openssl-library.org/news/secadv/20260127.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.15-1~deb12u1 and openssl/libssl3@3.0.15-1~deb12u1
- Fixed in: 3.0.18-1~deb12u2
Detailed paths
-
Introduced through: postgres@12 › openssl@3.0.15-1~deb12u1
-
Introduced through: postgres@12 › openssl/libssl3@3.0.15-1~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
Issue summary: A type confusion vulnerability exists in the TimeStamp Response verification code where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing a malformed TimeStamp Response file.
Impact summary: An application calling TS_RESP_verify_response() with a malformed TimeStamp Response can be caused to dereference an invalid or NULL pointer when reading, resulting in a Denial of Service.
The functions ossl_ess_get_signing_cert() and ossl_ess_get_signing_cert_v2() access the signing cert attribute value without validating its type. When the type is not V_ASN1_SEQUENCE, this results in accessing invalid memory through the ASN1_TYPE union, causing a crash.
Exploiting this vulnerability requires an attacker to provide a malformed TimeStamp Response to an application that verifies timestamp responses. The TimeStamp protocol (RFC 3161) is not widely used and the impact of the exploit is just a Denial of Service. For these reasons the issue was assessed as Low severity.
The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the TimeStamp Response implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.
OpenSSL 1.0.2 is not affected by this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.18-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-69420
- https://github.com/openssl/openssl/commit/27c7012c91cc986a598d7540f3079dfde2416eb9
- https://github.com/openssl/openssl/commit/4e254b48ad93cc092be3dd62d97015f33f73133a
- https://github.com/openssl/openssl/commit/564fd9c73787f25693bf9e75faf7bf6bb1305d4e
- https://github.com/openssl/openssl/commit/5eb0770ffcf11b785cf374ff3c19196245e54f1b
- https://github.com/openssl/openssl/commit/a99349ebfc519999edc50620abe24d599b9eb085
- https://openssl-library.org/news/secadv/20260127.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.15-1~deb12u1 and openssl/libssl3@3.0.15-1~deb12u1
- Fixed in: 3.0.17-1~deb12u3
Detailed paths
-
Introduced through: postgres@12 › openssl@3.0.15-1~deb12u1
-
Introduced through: postgres@12 › openssl/libssl3@3.0.15-1~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
Issue summary: An application trying to decrypt CMS messages encrypted using password based encryption can trigger an out-of-bounds read and write.
Impact summary: This out-of-bounds read may trigger a crash which leads to Denial of Service for an application. The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service or Execution of attacker-supplied code.
Although the consequences of a successful exploit of this vulnerability could be severe, the probability that the attacker would be able to perform it is low. Besides, password based (PWRI) encryption support in CMS messages is very rarely used. For that reason the issue was assessed as Moderate severity according to our Security Policy.
The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as the CMS implementation is outside the OpenSSL FIPS module boundary.
Remediation
Upgrade Debian:12 openssl to version 3.0.17-1~deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-9230
- https://github.com/openssl/openssl/commit/5965ea5dd6960f36d8b7f74f8eac67a8eb8f2b45
- https://github.com/openssl/openssl/commit/9e91358f365dee6c446dcdcdb01c04d2743fd280
- https://github.com/openssl/openssl/commit/a79c4ce559c6a3a8fd4109e9f33c1185d5bf2def
- https://github.com/openssl/openssl/commit/b5282d677551afda7d20e9c00e09561b547b2dfd
- https://github.com/openssl/openssl/commit/bae259a211ada6315dc50900686daaaaaa55f482
- https://github.openssl.org/openssl/extended-releases/commit/c2b96348bfa662f25f4fabf81958ae822063dae3
- https://github.openssl.org/openssl/extended-releases/commit/dfbaf161d8dafc1132dd88cd48ad990ed9b4c8ba
- https://openssl-library.org/news/secadv/20250930.txt
- https://lists.debian.org/debian-lts-announce/2025/10/msg00001.html
- http://www.openwall.com/lists/oss-security/2025/09/30/5
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.15-1~deb12u1 and openssl/libssl3@3.0.15-1~deb12u1
- Fixed in: 3.0.17-1~deb12u3
Detailed paths
-
Introduced through: postgres@12 › openssl@3.0.15-1~deb12u1
-
Introduced through: postgres@12 › openssl/libssl3@3.0.15-1~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
Issue summary: An application using the OpenSSL HTTP client API functions may trigger an out-of-bounds read if the 'no_proxy' environment variable is set and the host portion of the authority component of the HTTP URL is an IPv6 address.
Impact summary: An out-of-bounds read can trigger a crash which leads to Denial of Service for an application.
The OpenSSL HTTP client API functions can be used directly by applications but they are also used by the OCSP client functions and CMP (Certificate Management Protocol) client implementation in OpenSSL. However the URLs used by these implementations are unlikely to be controlled by an attacker.
In this vulnerable code the out of bounds read can only trigger a crash. Furthermore the vulnerability requires an attacker-controlled URL to be passed from an application to the OpenSSL function and the user has to have a 'no_proxy' environment variable set. For the aforementioned reasons the issue was assessed as Low severity.
The vulnerable code was introduced in the following patch releases: 3.0.16, 3.1.8, 3.2.4, 3.3.3, 3.4.0 and 3.5.0.
The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as the HTTP client implementation is outside the OpenSSL FIPS module boundary.
Remediation
Upgrade Debian:12 openssl to version 3.0.17-1~deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-9232
- https://github.com/openssl/openssl/commit/2b4ec20e47959170422922eaff25346d362dcb35
- https://github.com/openssl/openssl/commit/654dc11d23468a74fc8ea4672b702dd3feb7be4b
- https://github.com/openssl/openssl/commit/7cf21a30513c9e43c4bc3836c237cf086e194af3
- https://github.com/openssl/openssl/commit/89e790ac431125a4849992858490bed6b225eadf
- https://github.com/openssl/openssl/commit/bbf38c034cdabd0a13330abcc4855c866f53d2e0
- https://openssl-library.org/news/secadv/20250930.txt
- http://www.openwall.com/lists/oss-security/2025/09/30/5
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.15-1~deb12u1 and openssl/libssl3@3.0.15-1~deb12u1
- Fixed in: 3.0.18-1~deb12u2
Detailed paths
-
Introduced through: postgres@12 › openssl@3.0.15-1~deb12u1
-
Introduced through: postgres@12 › openssl/libssl3@3.0.15-1~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
Issue summary: An invalid or NULL pointer dereference can happen in an application processing a malformed PKCS#12 file.
Impact summary: An application processing a malformed PKCS#12 file can be caused to dereference an invalid or NULL pointer on memory read, resulting in a Denial of Service.
A type confusion vulnerability exists in PKCS#12 parsing code where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid pointer read.
The location is constrained to a 1-byte address space, meaning any attempted pointer manipulation can only target addresses between 0x00 and 0xFF. This range corresponds to the zero page, which is unmapped on most modern operating systems and will reliably result in a crash, leading only to a Denial of Service. Exploiting this issue also requires a user or application to process a maliciously crafted PKCS#12 file. It is uncommon to accept untrusted PKCS#12 files in applications as they are usually used to store private keys which are trusted by definition. For these reasons, the issue was assessed as Low severity.
The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS12 implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.
OpenSSL 1.0.2 is not affected by this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.18-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-22795
- https://github.com/openssl/openssl/commit/2502e7b7d4c0cf4f972a881641fe09edc67aeec4
- https://github.com/openssl/openssl/commit/572844beca95068394c916626a6d3a490f831a49
- https://github.com/openssl/openssl/commit/7bbca05be55b129651d9df4bdb92becc45002c12
- https://github.com/openssl/openssl/commit/eeee3cbd4d682095ed431052f00403004596373e
- https://github.com/openssl/openssl/commit/ef2fb66ec571564d64d1c74a12e388a2a54d05d2
- https://openssl-library.org/news/secadv/20260127.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.15-1~deb12u1 and openssl/libssl3@3.0.15-1~deb12u1
- Fixed in: 3.0.18-1~deb12u2
Detailed paths
-
Introduced through: postgres@12 › openssl@3.0.15-1~deb12u1
-
Introduced through: postgres@12 › openssl/libssl3@3.0.15-1~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
Issue summary: A type confusion vulnerability exists in the signature verification of signed PKCS#7 data where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing malformed PKCS#7 data.
Impact summary: An application performing signature verification of PKCS#7 data or calling directly the PKCS7_digest_from_attributes() function can be caused to dereference an invalid or NULL pointer when reading, resulting in a Denial of Service.
The function PKCS7_digest_from_attributes() accesses the message digest attribute value without validating its type. When the type is not V_ASN1_OCTET_STRING, this results in accessing invalid memory through the ASN1_TYPE union, causing a crash.
Exploiting this vulnerability requires an attacker to provide a malformed signed PKCS#7 to an application that verifies it. The impact of the exploit is just a Denial of Service, the PKCS7 API is legacy and applications should be using the CMS API instead. For these reasons the issue was assessed as Low severity.
The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#7 parsing implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.18-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-22796
- https://github.com/openssl/openssl/commit/2502e7b7d4c0cf4f972a881641fe09edc67aeec4
- https://github.com/openssl/openssl/commit/572844beca95068394c916626a6d3a490f831a49
- https://github.com/openssl/openssl/commit/7bbca05be55b129651d9df4bdb92becc45002c12
- https://github.com/openssl/openssl/commit/eeee3cbd4d682095ed431052f00403004596373e
- https://github.com/openssl/openssl/commit/ef2fb66ec571564d64d1c74a12e388a2a54d05d2
- https://openssl-library.org/news/secadv/20260127.txt
low severity
- Vulnerable module: perl
- Introduced through: perl@5.36.0-7+deb12u1, perl/libperl5.36@5.36.0-7+deb12u1 and others
- Fixed in: 5.36.0-7+deb12u3
Detailed paths
-
Introduced through: postgres@12 › perl@5.36.0-7+deb12u1
-
Introduced through: postgres@12 › perl/libperl5.36@5.36.0-7+deb12u1
-
Introduced through: postgres@12 › perl/perl-base@5.36.0-7+deb12u1
-
Introduced through: postgres@12 › perl/perl-modules-5.36@5.36.0-7+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
Perl threads have a working directory race condition where file operations may target unintended paths.
If a directory handle is open at thread creation, the process-wide current working directory is temporarily changed in order to clone that handle for the new thread, which is visible from any third (or more) thread already running.
This may lead to unintended operations such as loading code or accessing files from unexpected locations, which a local attacker may be able to exploit.
The bug was introduced in commit 11a11ecf4bea72b17d250cfb43c897be1341861e and released in Perl version 5.13.6
Remediation
Upgrade Debian:12 perl to version 5.36.0-7+deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-40909
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098226
- https://github.com/Perl/perl5/commit/11a11ecf4bea72b17d250cfb43c897be1341861e
- https://github.com/Perl/perl5/commit/918bfff86ca8d6d4e4ec5b30994451e0bd74aba9.patch
- https://github.com/Perl/perl5/issues/10387
- https://github.com/Perl/perl5/issues/23010
- https://perldoc.perl.org/5.14.0/perl5136delta#Directory-handles-not-copied-to-threads
- https://www.openwall.com/lists/oss-security/2025/05/22/2
- http://www.openwall.com/lists/oss-security/2025/05/23/1
- http://www.openwall.com/lists/oss-security/2025/05/30/4
- http://www.openwall.com/lists/oss-security/2025/06/02/2
- http://www.openwall.com/lists/oss-security/2025/06/02/5
- http://www.openwall.com/lists/oss-security/2025/06/02/6
- http://www.openwall.com/lists/oss-security/2025/06/02/7
- http://www.openwall.com/lists/oss-security/2025/06/03/1
- http://seclists.org/fulldisclosure/2025/Sep/53
- http://seclists.org/fulldisclosure/2025/Sep/54
- http://seclists.org/fulldisclosure/2025/Sep/55
low severity
- Vulnerable module: perl
- Introduced through: perl@5.36.0-7+deb12u1, perl/libperl5.36@5.36.0-7+deb12u1 and others
- Fixed in: 5.36.0-7+deb12u2
Detailed paths
-
Introduced through: postgres@12 › perl@5.36.0-7+deb12u1
-
Introduced through: postgres@12 › perl/libperl5.36@5.36.0-7+deb12u1
-
Introduced through: postgres@12 › perl/perl-base@5.36.0-7+deb12u1
-
Introduced through: postgres@12 › perl/perl-modules-5.36@5.36.0-7+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A heap buffer overflow vulnerability was discovered in Perl.
Release branches 5.34, 5.36, 5.38 and 5.40 are affected, including development versions from 5.33.1 through 5.41.10.
When there are non-ASCII bytes in the left-hand-side of the tr operator, S_do_trans_invmap can overflow the destination pointer d.
$ perl -e '$_ = "\x{FF}" x 1000000; tr/\xFF/\x{100}/;' Segmentation fault (core dumped)
It is believed that this vulnerability can enable Denial of Service and possibly Code Execution attacks on platforms that lack sufficient defenses.
Remediation
Upgrade Debian:12 perl to version 5.36.0-7+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-56406
- https://github.com/Perl/perl5/commit/87f42aa0e0096e9a346c9672aa3a0bd3bef8c1dd.patch
- https://metacpan.org/release/SHAY/perl-5.38.4/changes
- https://metacpan.org/release/SHAY/perl-5.40.2/changes
- http://www.openwall.com/lists/oss-security/2025/04/13/3
- http://www.openwall.com/lists/oss-security/2025/04/13/4
- http://www.openwall.com/lists/oss-security/2025/04/13/5
low severity
- Vulnerable module: shadow/login
- Introduced through: shadow/login@1:4.13+dfsg1-1+b1 and shadow/passwd@1:4.13+dfsg1-1+b1
Detailed paths
-
Introduced through: postgres@12 › shadow/login@1:4.13+dfsg1-1+b1
-
Introduced through: postgres@12 › shadow/passwd@1:4.13+dfsg1-1+b1
NVD Description
Note: Versions mentioned in the description apply only to the upstream shadow package and not the shadow package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
shadow-utils (aka shadow) 4.4 through 4.17.0 establishes a default /etc/subuid behavior (e.g., uid 100000 through 165535 for the first user account) that can realistically conflict with the uids of users defined on locally administered networks, potentially leading to account takeover, e.g., by leveraging newuidmap for access to an NFS home directory (or same-host resources in the case of remote logins by these local network users). NOTE: it may also be argued that system administrators should not have assigned uids, within local networks, that are within the range that can occur in /etc/subuid.
Remediation
There is no fixed version for Debian:12 shadow.
References
low severity
new
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2+deb12u1
Detailed paths
-
Introduced through: postgres@12 › sqlite3/libsqlite3-0@3.40.1-2+deb12u1
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+deb12u1
Detailed paths
-
Introduced through: postgres@12 › sqlite3/libsqlite3-0@3.40.1-2+deb12u1
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
new
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.33-1~deb12u1 and systemd/libudev1@252.33-1~deb12u1
Detailed paths
-
Introduced through: postgres@12 › systemd/libsystemd0@252.33-1~deb12u1
-
Introduced through: postgres@12 › systemd/libudev1@252.33-1~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
systemd, a system and service manager, (as PID 1) hits an assert and freezes execution when an unprivileged IPC API call is made with spurious data. On version v249 and older the effect is not an assert, but stack overwriting, with the attacker controlled content. From version v250 and newer this is not possible as the safety check causes an assert instead. This IPC call was added in v239, so versions older than that are not affected. Versions 260-rc1, 259.2, 258.5, and 257.11 contain patches. No known workarounds are available.
Remediation
There is no fixed version for Debian:12 systemd.
References
- https://security-tracker.debian.org/tracker/CVE-2026-29111
- https://github.com/systemd/systemd/commit/1d22f706bd04f45f8422e17fbde3f56ece17758a
- https://github.com/systemd/systemd/commit/20021e7686426052e3a7505425d7e12085feb2a6
- https://github.com/systemd/systemd/commit/21167006574d6b83813c7596759b474f56562412
- https://github.com/systemd/systemd/commit/3cee294fe8cf4fa0eff933ab21416d099942cabd
- https://github.com/systemd/systemd/commit/42aee39107fbdd7db1ccd402a2151822b2805e9f
- https://github.com/systemd/systemd/commit/54588d2dedff54bfb6036670820650e4ea74628f
- https://github.com/systemd/systemd/commit/7ac3220213690e8a8d6d2a6e81e43bd1dce01d69
- https://github.com/systemd/systemd/commit/80acea4ef80a4bb78560ed970c34952299b890d6
- https://github.com/systemd/systemd/commit/b5fd14693057e5f2c9b4a49603be64ec3608ff6c
- https://github.com/systemd/systemd/commit/efa6ba2ab625aaa160ac435a09e6482fc63bdbe8
- https://github.com/systemd/systemd/security/advisories/GHSA-gx6q-6f99-m764
low severity
- Vulnerable module: 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: postgres@12 › util-linux@2.38.1-5+deb12u3
-
Introduced through: postgres@12 › util-linux/bsdutils@1:2.38.1-5+deb12u3
-
Introduced through: postgres@12 › util-linux/libblkid1@2.38.1-5+deb12u3
-
Introduced through: postgres@12 › util-linux/libmount1@2.38.1-5+deb12u3
-
Introduced through: postgres@12 › util-linux/libsmartcols1@2.38.1-5+deb12u3
-
Introduced through: postgres@12 › util-linux/libuuid1@2.38.1-5+deb12u3
-
Introduced through: postgres@12 › util-linux/mount@2.38.1-5+deb12u3
-
Introduced through: postgres@12 › util-linux/util-linux-extra@2.38.1-5+deb12u3
NVD Description
This vulnerability has not been analyzed by NVD yet.
Remediation
There is no fixed version for Debian:12 util-linux.
References
low severity
- Vulnerable module: xz-utils
- Introduced through: xz-utils@5.4.1-0.2 and xz-utils/liblzma5@5.4.1-0.2
- Fixed in: 5.4.1-1
Detailed paths
-
Introduced through: postgres@12 › xz-utils@5.4.1-0.2
-
Introduced through: postgres@12 › xz-utils/liblzma5@5.4.1-0.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream xz-utils package and not the xz-utils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
XZ Utils provide a general-purpose data-compression library plus command-line tools. In XZ Utils 5.3.3alpha to 5.8.0, the multithreaded .xz decoder in liblzma has a bug where invalid input can at least result in a crash. The effects include heap use after free and writing to an address based on the null pointer plus an offset. Applications and libraries that use the lzma_stream_decoder_mt function are affected. The bug has been fixed in XZ Utils 5.8.1, and the fix has been committed to the v5.4, v5.6, v5.8, and master branches in the xz Git repository. No new release packages will be made from the old stable branches, but a standalone patch is available that applies to all affected releases.
Remediation
Upgrade Debian:12 xz-utils to version 5.4.1-1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-31115
- https://github.com/tukaani-project/xz/commit/d5a2ffe41bb77b918a8c96084885d4dbe4bf6480
- https://github.com/tukaani-project/xz/security/advisories/GHSA-6cc8-p5mm-29w2
- https://tukaani.org/xz/xz-cve-2025-31115.patch
- http://www.openwall.com/lists/oss-security/2025/04/03/1
- http://www.openwall.com/lists/oss-security/2025/04/03/2
- http://www.openwall.com/lists/oss-security/2025/04/03/3