Vulnerabilities |
511 via 792 paths |
|---|---|
Dependencies |
143 |
Source |
Docker |
Target OS |
debian:11 |
critical severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
- Fixed in: 7.74.0-1.3+deb11u5
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
When doing HTTP(S) transfers, libcurl might erroneously use the read callback (CURLOPT_READFUNCTION) to ask for data to send, even when the CURLOPT_POSTFIELDS option has been set, if the same handle previously was used to issue a PUT request which used that callback. This flaw may surprise the application and cause it to misbehave and either send off the wrong data or use memory after free or similar in the subsequent POST request. The problem exists in the logic for a reused handle when it is changed from a PUT to a POST.
Remediation
Upgrade Debian:11 curl to version 7.74.0-1.3+deb11u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-32221
- http://seclists.org/fulldisclosure/2023/Jan/19
- http://seclists.org/fulldisclosure/2023/Jan/20
- http://www.openwall.com/lists/oss-security/2023/05/17/4
- https://hackerone.com/reports/1704017
- https://lists.debian.org/debian-lts-announce/2023/01/msg00028.html
- https://security.gentoo.org/glsa/202212-01
- https://security.netapp.com/advisory/ntap-20230110-0006/
- https://security.netapp.com/advisory/ntap-20230208-0002/
- https://support.apple.com/kb/HT213604
- https://support.apple.com/kb/HT213605
- https://www.debian.org/security/2023/dsa-5330
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-892048.html
critical severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
- Fixed in: 7.74.0-1.3+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
When curl < 7.84.0 saves cookies, alt-svc and hsts data to local files, it makes the operation atomic by finalizing the operation with a rename from a temporary name to the final target file name.In that rename operation, it might accidentally widen the permissions for the target file, leaving the updated file accessible to more users than intended.
Remediation
Upgrade Debian:11 curl to version 7.74.0-1.3+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-32207
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BEV6BR4MTI3CEWK2YU2HQZUW5FAS3FEY/
- http://seclists.org/fulldisclosure/2022/Oct/28
- http://seclists.org/fulldisclosure/2022/Oct/41
- https://hackerone.com/reports/1573634
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BEV6BR4MTI3CEWK2YU2HQZUW5FAS3FEY/
- https://security.gentoo.org/glsa/202212-01
- https://security.netapp.com/advisory/ntap-20220915-0003/
- https://support.apple.com/kb/HT213488
- https://www.debian.org/security/2022/dsa-5197
- https://cert-portal.siemens.com/productcert/html/ssa-146325.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-419740.html
- https://cert-portal.siemens.com/productcert/html/ssa-558014.html
- https://cert-portal.siemens.com/productcert/html/ssa-942865.html
critical severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
- Fixed in: 7.74.0-1.3+deb11u10
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
This flaw makes curl overflow a heap based buffer in the SOCKS5 proxy handshake.
When curl is asked to pass along the host name to the SOCKS5 proxy to allow that to resolve the address instead of it getting done by curl itself, the maximum length that host name can be is 255 bytes.
If the host name is detected to be longer, curl switches to local name resolving and instead passes on the resolved address only. Due to this bug, the local variable that means "let the host resolve the name" could get the wrong value during a slow SOCKS5 handshake, and contrary to the intention, copy the too long host name to the target buffer instead of copying just the resolved address there.
The target buffer being a heap based buffer, and the host name coming from the URL that curl has been told to operate with.
Remediation
Upgrade Debian:11 curl to version 7.74.0-1.3+deb11u10 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-38545
- https://github.com/UTsweetyfish/CVE-2023-38545
- https://github.com/bcdannyboy/CVE-2023-38545
- https://github.com/dbrugman/CVE-2023-38545-POC
- http://seclists.org/fulldisclosure/2024/Jan/34
- http://seclists.org/fulldisclosure/2024/Jan/37
- http://seclists.org/fulldisclosure/2024/Jan/38
- https://curl.se/docs/CVE-2023-38545.html
- https://forum.vmssoftware.com/viewtopic.php?f=8&t=8868
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OGMXNRNSJ4ETDK6FRNU3J7SABXPWCHSQ/
- https://security.netapp.com/advisory/ntap-20231027-0009/
- https://security.netapp.com/advisory/ntap-20240201-0005/
- https://support.apple.com/kb/HT214036
- https://support.apple.com/kb/HT214057
- https://support.apple.com/kb/HT214058
- https://support.apple.com/kb/HT214063
- https://www.secpod.com/blog/high-severity-heap-buffer-overflow-vulnerability/
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-093430.html
- https://cert-portal.siemens.com/productcert/html/ssa-507364.html
- https://cert-portal.siemens.com/productcert/html/ssa-832273.html
- https://cert-portal.siemens.com/productcert/html/ssa-943925.html
- https://github.com/d0rb/CVE-2023-38545
critical severity
- Vulnerable module: db5.3/libdb5.3
- Introduced through: db5.3/libdb5.3@5.3.28+dfsg1-0.8
Detailed paths
-
Introduced through: nginx@1.21 › db5.3/libdb5.3@5.3.28+dfsg1-0.8
NVD Description
Note: Versions mentioned in the description apply only to the upstream db5.3 package and not the db5.3 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
SQLite3 from 3.6.0 to and including 3.27.2 is vulnerable to heap out-of-bound read in the rtreenode() function when handling invalid rtree tables.
Remediation
There is no fixed version for Debian:11 db5.3.
References
- https://security-tracker.debian.org/tracker/CVE-2019-8457
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-8457
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OPKYSWCOM3CL66RI76TYVIG6TJ263RXH/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SJPFGA45DI4F5MCF2OAACGH3HQOF4G3M/
- https://www.oracle.com/security-alerts/cpujan2020.html
- https://www.oracle.com/security-alerts/cpujul2020.html
- https://www.sqlite.org/releaselog/3_28_0.html
- https://www.sqlite.org/src/info/90acdbfce9c08858
- https://www.oracle.com/security-alerts/cpuapr2020.html
- https://security.netapp.com/advisory/ntap-20190606-0002/
- http://lists.opensuse.org/opensuse-security-announce/2019-06/msg00074.html
- https://www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.html
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2019-8457
- https://usn.ubuntu.com/4004-1/
- https://usn.ubuntu.com/4004-2/
- https://usn.ubuntu.com/4019-1/
- https://usn.ubuntu.com/4019-2/
- https://kc.mcafee.com/corporate/index?page=content&id=SB10365
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/OPKYSWCOM3CL66RI76TYVIG6TJ263RXH/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/SJPFGA45DI4F5MCF2OAACGH3HQOF4G3M/
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
critical severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.10-2+deb11u3
- Fixed in: 2.2.10-2+deb11u6
Detailed paths
-
Introduced through: nginx@1.21 › expat/libexpat1@2.2.10-2+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
An issue was discovered in libexpat before 2.6.3. dtdCopy in xmlparse.c can have an integer overflow for nDefaultAtts on 32-bit platforms (where UINT_MAX equals SIZE_MAX).
Remediation
Upgrade Debian:11 expat to version 2.2.10-2+deb11u6 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-45491
- https://github.com/libexpat/libexpat/issues/888
- https://github.com/libexpat/libexpat/pull/891
- https://security.netapp.com/advisory/ntap-20241018-0003/
- https://lists.debian.org/debian-lts-announce/2024/09/msg00036.html
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-613116.html
critical severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.10-2+deb11u3
- Fixed in: 2.2.10-2+deb11u6
Detailed paths
-
Introduced through: nginx@1.21 › expat/libexpat1@2.2.10-2+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
An issue was discovered in libexpat before 2.6.3. nextScaffoldPart in xmlparse.c can have an integer overflow for m_groupSize on 32-bit platforms (where UINT_MAX equals SIZE_MAX).
Remediation
Upgrade Debian:11 expat to version 2.2.10-2+deb11u6 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-45492
- https://github.com/libexpat/libexpat/issues/889
- https://github.com/libexpat/libexpat/pull/892
- https://security.netapp.com/advisory/ntap-20241018-0005/
- https://lists.debian.org/debian-lts-announce/2024/09/msg00036.html
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-613116.html
critical severity
- Vulnerable module: freetype/libfreetype6
- Introduced through: freetype/libfreetype6@2.10.4+dfsg-1
- Fixed in: 2.10.4+dfsg-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › freetype/libfreetype6@2.10.4+dfsg-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream freetype package and not the freetype package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
FreeType commit 1e2eb65048f75c64b68708efed6ce904c31f3b2f was discovered to contain a heap buffer overflow via the function sfnt_init_face.
Remediation
Upgrade Debian:11 freetype to version 2.10.4+dfsg-1+deb11u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-27404
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/EFPNRKDLCXHZVYYQLQMP44UHLU32GA6Z/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/FDU2FOEMCEF6WVR6ZBIH5MT5O7FAK6UP/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/IWQ7IB2A75MEHM63WEUXBYEC7OR5SGDY/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NYVC2NPKKXKP3TWJWG4ONYWNO6ZPHLA5/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TCEMWCM46PKM4U5ENRASPKQD6JDOLKRU/
- https://gitlab.freedesktop.org/freetype/freetype/-/issues/1138
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/EFPNRKDLCXHZVYYQLQMP44UHLU32GA6Z/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FDU2FOEMCEF6WVR6ZBIH5MT5O7FAK6UP/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/IWQ7IB2A75MEHM63WEUXBYEC7OR5SGDY/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/NYVC2NPKKXKP3TWJWG4ONYWNO6ZPHLA5/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/TCEMWCM46PKM4U5ENRASPKQD6JDOLKRU/
- https://security.gentoo.org/glsa/202402-06
critical severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.1-5
- Fixed in: 3.7.1-5+deb11u10
Detailed paths
-
Introduced through: nginx@1.21 › gnutls28/libgnutls30@3.7.1-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw was found in gnutls. Servers configured with RSA-PSK (Rivest–Shamir–Adleman – Pre-Shared Key) wrongfully matched usernames containing a NUL character with truncated usernames. A remote attacker could exploit this by sending a specially crafted username, leading to an authentication bypass. This vulnerability allows an attacker to gain unauthorized access by circumventing the authentication process.
Remediation
Upgrade Debian:11 gnutls28 to version 3.7.1-5+deb11u10 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-42010
- https://www.gnutls.org/security-new.html#GNUTLS-SA-2026-04-29-4
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-42010.json
- https://access.redhat.com/errata/RHSA-2026:67857
- https://access.redhat.com/errata/RHSA-2026:72502
- https://access.redhat.com/errata/RHSA-2026:74674
- https://access.redhat.com/errata/RHSA-2026:82304
- https://access.redhat.com/errata/RHSA-2026:82322
- https://access.redhat.com/errata/RHSA-2026:82347
- https://access.redhat.com/errata/RHSA-2026:82354
- https://access.redhat.com/errata/RHSA-2026:82372
- https://access.redhat.com/errata/RHSA-2026:82857
- https://access.redhat.com/errata/RHSA-2026:82888
- https://access.redhat.com/errata/RHSA-2026:13274
- https://access.redhat.com/errata/RHSA-2026:20611
- https://access.redhat.com/errata/RHSA-2026:20612
- https://access.redhat.com/errata/RHSA-2026:20613
- https://access.redhat.com/errata/RHSA-2026:26319
- https://access.redhat.com/errata/RHSA-2026:26409
- https://access.redhat.com/errata/RHSA-2026:29197
- https://access.redhat.com/errata/RHSA-2026:30004
- https://access.redhat.com/errata/RHSA-2026:30849
- https://access.redhat.com/errata/RHSA-2026:30850
- https://access.redhat.com/errata/RHSA-2026:32962
- https://access.redhat.com/errata/RHSA-2026:33125
- https://access.redhat.com/errata/RHSA-2026:34764
- https://access.redhat.com/errata/RHSA-2026:34788
- https://access.redhat.com/errata/RHSA-2026:34790
- https://access.redhat.com/errata/RHSA-2026:36004
- https://access.redhat.com/errata/RHSA-2026:36005
- https://access.redhat.com/errata/RHSA-2026:36006
- https://access.redhat.com/errata/RHSA-2026:40762
- https://access.redhat.com/errata/RHSA-2026:41921
- https://access.redhat.com/errata/RHSA-2026:56853
- https://access.redhat.com/errata/RHSA-2026:57483
- https://access.redhat.com/errata/RHSA-2026:58981
- https://access.redhat.com/errata/RHSA-2026:59831
- https://access.redhat.com/errata/RHSA-2026:60019
- https://access.redhat.com/errata/RHSA-2026:62409
- https://access.redhat.com/errata/RHSA-2026:65839
- https://access.redhat.com/security/cve/CVE-2026-42010
- https://bugzilla.redhat.com/show_bug.cgi?id=2467289
critical severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.10+dfsg-6.7+deb11u2
- Fixed in: 2.9.10+dfsg-6.7+deb11u6
Detailed paths
-
Introduced through: nginx@1.21 › libxml2@2.9.10+dfsg-6.7+deb11u2
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:11 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:11 libxml2 to version 2.9.10+dfsg-6.7+deb11u6 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: zlib/zlib1g
- Introduced through: zlib/zlib1g@1:1.2.11.dfsg-2+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › zlib/zlib1g@1:1.2.11.dfsg-2+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream zlib package and not the zlib package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
MiniZip in zlib through 1.3 has an integer overflow and resultant heap-based buffer overflow in zipOpenNewFileInZip4_64 via a long filename, comment, or extra field. NOTE: MiniZip is not a supported part of the zlib product. NOTE: pyminizip through 0.2.6 is also vulnerable because it bundles an affected zlib version, and exposes the applicable MiniZip code through its compress API.
Remediation
There is no fixed version for Debian:11 zlib.
References
- 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
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-470355.html
- https://cert-portal.siemens.com/productcert/html/ssa-769027.html
critical severity
- Vulnerable module: zlib/zlib1g
- Introduced through: zlib/zlib1g@1:1.2.11.dfsg-2+deb11u1
- Fixed in: 1:1.2.11.dfsg-2+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › zlib/zlib1g@1:1.2.11.dfsg-2+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream zlib package and not the zlib package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
zlib through 1.2.12 has a heap-based buffer over-read or buffer overflow in inflate in inflate.c via a large gzip header extra field. NOTE: only applications that call inflateGetHeader are affected. Some common applications bundle the affected zlib source code but may be unable to call inflateGetHeader (e.g., see the nodejs/node reference).
Remediation
Upgrade Debian:11 zlib to version 1:1.2.11.dfsg-2+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-37434
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JWN4VE3JQR4O2SOUS5TXNLANRPMHWV4I/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NMBOJ77A7T7PQCARMDUK75TE6LLESZ3O/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PAVPQNCG3XRLCLNSQRM3KAN5ZFMVXVTY/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/X5U7OTKZSHY2I3ZFJSR2SHFHW72RKGDK/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YRQAI7H4M4RQZ2IWZUEEXECBE5D56BH2/
- https://github.com/madler/zlib/commit/1eb7682f845ac9e9bf9ae35bbfb3bad5dacbd91d
- http://seclists.org/fulldisclosure/2022/Oct/37
- http://seclists.org/fulldisclosure/2022/Oct/38
- http://seclists.org/fulldisclosure/2022/Oct/41
- http://seclists.org/fulldisclosure/2022/Oct/42
- http://www.openwall.com/lists/oss-security/2022/08/05/2
- http://www.openwall.com/lists/oss-security/2022/08/09/1
- https://github.com/ivd38/zlib_overflow
- https://github.com/madler/zlib/blob/21767c654d31d2dccdde4330529775c6c5fd5389/zlib.h#L1062-L1063
- https://github.com/madler/zlib/commit/eff308af425b67093bab25f80f1ae950166bece1
- https://github.com/nodejs/node/blob/75b68c6e4db515f76df73af476eccf382bbcb00a/deps/zlib/inflate.c#L762-L764
- https://lists.debian.org/debian-lts-announce/2022/09/msg00012.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/JWN4VE3JQR4O2SOUS5TXNLANRPMHWV4I/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/NMBOJ77A7T7PQCARMDUK75TE6LLESZ3O/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PAVPQNCG3XRLCLNSQRM3KAN5ZFMVXVTY/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/X5U7OTKZSHY2I3ZFJSR2SHFHW72RKGDK/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/YRQAI7H4M4RQZ2IWZUEEXECBE5D56BH2/
- https://security.netapp.com/advisory/ntap-20220901-0005/
- https://security.netapp.com/advisory/ntap-20230427-0007/
- https://support.apple.com/kb/HT213488
- https://support.apple.com/kb/HT213489
- https://support.apple.com/kb/HT213490
- https://support.apple.com/kb/HT213491
- https://support.apple.com/kb/HT213493
- https://support.apple.com/kb/HT213494
- https://www.debian.org/security/2022/dsa-5218
- https://cert-portal.siemens.com/productcert/html/ssa-150063.html
- https://cert-portal.siemens.com/productcert/html/ssa-202008.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-470355.html
- https://cert-portal.siemens.com/productcert/html/ssa-561322.html
- https://github.com/curl/curl/issues/9271
critical severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A cleartext transmission of sensitive information vulnerability exists in curl <v7.88.0 that could cause HSTS functionality fail when multiple URLs are requested serially. Using its HSTS support, curl can be instructed to use HTTPS instead of usingan insecure clear-text HTTP step even when HTTP is provided in the URL. ThisHSTS mechanism would however surprisingly be ignored by subsequent transferswhen done on the same command line because the state would not be properlycarried on.
Remediation
There is no fixed version for Debian:11 curl.
References
critical severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
- Fixed in: 7.74.0-1.3+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
When sending data to an MQTT server, libcurl <= 7.73.0 and 7.78.0 could in some circumstances erroneously keep a pointer to an already freed memory area and both use that again in a subsequent call to send data and also free it again.
Remediation
Upgrade Debian:11 curl to version 7.74.0-1.3+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2021-22945
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RWLEC6YVEM2HWUBX67SDGPSY4CQB72OE/
- https://hackerone.com/reports/1269242
- https://www.oracle.com/security-alerts/cpuoct2021.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/APOAK4X73EJTAPTSVT7IRVDMUWVXNWGD/
- http://seclists.org/fulldisclosure/2022/Mar/29
- https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/APOAK4X73EJTAPTSVT7IRVDMUWVXNWGD/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/RWLEC6YVEM2HWUBX67SDGPSY4CQB72OE/
- https://security.gentoo.org/glsa/202212-01
- https://security.netapp.com/advisory/ntap-20211029-0003/
- https://support.apple.com/kb/HT213183
- https://www.debian.org/security/2022/dsa-5197
- https://cert-portal.siemens.com/productcert/html/ssa-389290.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
critical severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.1-5
- Fixed in: 3.7.1-5+deb11u10
Detailed paths
-
Introduced through: nginx@1.21 › gnutls28/libgnutls30@3.7.1-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw in GnuTLS DTLS handshake parsing allows malformed fragments with zero length and non-zero offset, leading to an integer underflow during reassembly and resulting in an out-of-bounds read. This issue is remotely exploitable and may cause information disclosure or denial of service.
Remediation
Upgrade Debian:11 gnutls28 to version 3.7.1-5+deb11u10 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-33845
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-33845.json
- https://access.redhat.com/errata/RHSA-2026:72502
- https://access.redhat.com/errata/RHSA-2026:74674
- https://access.redhat.com/errata/RHSA-2026:82304
- https://access.redhat.com/errata/RHSA-2026:82322
- https://access.redhat.com/errata/RHSA-2026:82347
- https://access.redhat.com/errata/RHSA-2026:82354
- https://access.redhat.com/errata/RHSA-2026:82372
- https://access.redhat.com/errata/RHSA-2026:82857
- https://access.redhat.com/errata/RHSA-2026:82888
- https://access.redhat.com/errata/RHSA-2026:13274
- https://access.redhat.com/errata/RHSA-2026:20611
- https://access.redhat.com/errata/RHSA-2026:20612
- https://access.redhat.com/errata/RHSA-2026:20613
- https://access.redhat.com/errata/RHSA-2026:26319
- https://access.redhat.com/errata/RHSA-2026:26409
- https://access.redhat.com/errata/RHSA-2026:29197
- https://access.redhat.com/errata/RHSA-2026:30004
- https://access.redhat.com/errata/RHSA-2026:30849
- https://access.redhat.com/errata/RHSA-2026:30850
- https://access.redhat.com/errata/RHSA-2026:32962
- https://access.redhat.com/errata/RHSA-2026:33125
- https://access.redhat.com/errata/RHSA-2026:34372
- https://access.redhat.com/errata/RHSA-2026:36004
- https://access.redhat.com/errata/RHSA-2026:36005
- https://access.redhat.com/errata/RHSA-2026:36006
- https://access.redhat.com/errata/RHSA-2026:41921
- https://access.redhat.com/errata/RHSA-2026:56786
- https://access.redhat.com/errata/RHSA-2026:56853
- https://access.redhat.com/errata/RHSA-2026:56911
- https://access.redhat.com/errata/RHSA-2026:57402
- https://access.redhat.com/errata/RHSA-2026:57483
- https://access.redhat.com/errata/RHSA-2026:58981
- https://access.redhat.com/errata/RHSA-2026:59831
- https://access.redhat.com/errata/RHSA-2026:60019
- https://access.redhat.com/errata/RHSA-2026:65839
- https://access.redhat.com/security/cve/CVE-2026-33845
- https://bugzilla.redhat.com/show_bug.cgi?id=2450624
critical severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.18.3-6+deb11u1, krb5/libk5crypto3@1.18.3-6+deb11u1 and others
- Fixed in: 1.18.3-6+deb11u5
Detailed paths
-
Introduced through: nginx@1.21 › krb5/libgssapi-krb5-2@1.18.3-6+deb11u1
-
Introduced through: nginx@1.21 › krb5/libk5crypto3@1.18.3-6+deb11u1
-
Introduced through: nginx@1.21 › krb5/libkrb5-3@1.18.3-6+deb11u1
-
Introduced through: nginx@1.21 › krb5/libkrb5support0@1.18.3-6+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
In MIT Kerberos 5 (aka krb5) before 1.21.3, an attacker can cause invalid memory reads during GSS message token handling by sending message tokens with invalid length fields.
Remediation
Upgrade Debian:11 krb5 to version 1.18.3-6+deb11u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-37371
- https://security.netapp.com/advisory/ntap-20241108-0009/
- https://security.netapp.com/advisory/ntap-20250124-0010/
- https://github.com/krb5/krb5/commit/55fbf435edbe2e92dd8101669b1ce7144bc96fef
- https://web.mit.edu/kerberos/www/advisories/
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
critical severity
- Vulnerable module: libtasn1-6
- Introduced through: libtasn1-6@4.16.0-2
- Fixed in: 4.16.0-2+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › libtasn1-6@4.16.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:11 relevant fixed versions and status.
GNU Libtasn1 before 4.19.0 has an ETYPE_OK off-by-one array size check that affects asn1_encode_simple_der.
Remediation
Upgrade Debian:11 libtasn1-6 to version 4.16.0-2+deb11u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2021-46848
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/AV4SHDJF2XLB4CUPTBPQQ6CLGZ5LKXPZ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ECM2ELTVRYV4BZ5L5GMIRQE27RFHPAQ6/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OGO7XST4EIJGX4B2ITZCYSWM24534BSU/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/V5LWOGF7QRMNFRUCZY6TDYQJVFI6MOQ2/
- https://bugs.gentoo.org/866237
- https://gitlab.com/gnutls/libtasn1/-/commit/44a700d2051a666235748970c2df047ff207aeb5
- https://gitlab.com/gnutls/libtasn1/-/issues/32
- https://lists.debian.org/debian-lts-announce/2023/01/msg00003.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/AV4SHDJF2XLB4CUPTBPQQ6CLGZ5LKXPZ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ECM2ELTVRYV4BZ5L5GMIRQE27RFHPAQ6/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/OGO7XST4EIJGX4B2ITZCYSWM24534BSU/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/V5LWOGF7QRMNFRUCZY6TDYQJVFI6MOQ2/
- https://security.netapp.com/advisory/ntap-20221118-0006/
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
critical severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.10+dfsg-6.7+deb11u2
- Fixed in: 2.9.10+dfsg-6.7+deb11u8
Detailed paths
-
Introduced through: nginx@1.21 › libxml2@2.9.10+dfsg-6.7+deb11u2
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:11 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:11 libxml2 to version 2.9.10+dfsg-6.7+deb11u8 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
- https://access.redhat.com/errata/RHSA-2026:7519
- https://cert-portal.siemens.com/productcert/html/ssa-577017.html
- https://cert-portal.siemens.com/productcert/html/ssa-253495.html
- https://access.redhat.com/errata/RHSA-2026:62549
- https://access.redhat.com/errata/RHSA-2026:67857
critical severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.10+dfsg-6.7+deb11u2
- Fixed in: 2.9.10+dfsg-6.7+deb11u8
Detailed paths
-
Introduced through: nginx@1.21 › libxml2@2.9.10+dfsg-6.7+deb11u2
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:11 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:11 libxml2 to version 2.9.10+dfsg-6.7+deb11u8 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
- https://access.redhat.com/errata/RHSA-2026:7519
- https://cert-portal.siemens.com/productcert/html/ssa-577017.html
- https://cert-portal.siemens.com/productcert/html/ssa-253495.html
- https://access.redhat.com/errata/RHSA-2026:62549
- https://access.redhat.com/errata/RHSA-2026:67857
critical severity
- Vulnerable module: pcre2/libpcre2-8-0
- Introduced through: pcre2/libpcre2-8-0@10.36-2
- Fixed in: 10.36-2+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › pcre2/libpcre2-8-0@10.36-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream pcre2 package and not the pcre2 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
An out-of-bounds read vulnerability was discovered in the PCRE2 library in the get_recurse_data_length() function of the pcre2_jit_compile.c file. This issue affects recursions in JIT-compiled regular expressions caused by duplicate data transfers.
Remediation
Upgrade Debian:11 pcre2 to version 10.36-2+deb11u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-1587
- https://bugzilla.redhat.com/show_bug.cgi?id=2077983,
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DWNG2NS3GINO6LQYUVC4BZLUQPJ3DYHA/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JXINO3KKI5DICQ45E2FKD6MKVMGJLEKJ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KAX7767BCUFC7JMDGP7GOQ5GIZCAUGBB/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/M2GLQQUEY5VFM57CFYXVIFOXN2HUZPDM/
- https://bugzilla.redhat.com/show_bug.cgi?id=2077983%2C
- https://github.com/PCRE2Project/pcre2/commit/03654e751e7f0700693526b67dfcadda6b42c9d0
- https://lists.debian.org/debian-lts-announce/2023/03/msg00014.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/DWNG2NS3GINO6LQYUVC4BZLUQPJ3DYHA/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/JXINO3KKI5DICQ45E2FKD6MKVMGJLEKJ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/KAX7767BCUFC7JMDGP7GOQ5GIZCAUGBB/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/M2GLQQUEY5VFM57CFYXVIFOXN2HUZPDM/
- https://security.netapp.com/advisory/ntap-20221028-0009/
critical severity
- Vulnerable module: pcre2/libpcre2-8-0
- Introduced through: pcre2/libpcre2-8-0@10.36-2
- Fixed in: 10.36-2+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › pcre2/libpcre2-8-0@10.36-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream pcre2 package and not the pcre2 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
An out-of-bounds read vulnerability was discovered in the PCRE2 library in the compile_xclass_matchingpath() function of the pcre2_jit_compile.c file. This involves a unicode property matching issue in JIT-compiled regular expressions. The issue occurs because the character was not fully read in case-less matching within JIT.
Remediation
Upgrade Debian:11 pcre2 to version 10.36-2+deb11u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-1586
- https://bugzilla.redhat.com/show_bug.cgi?id=2077976,
- https://github.com/PCRE2Project/pcre2/commit/50a51cb7e67268e6ad417eb07c9de9bfea5cc55a,
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DWNG2NS3GINO6LQYUVC4BZLUQPJ3DYHA/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JXINO3KKI5DICQ45E2FKD6MKVMGJLEKJ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KAX7767BCUFC7JMDGP7GOQ5GIZCAUGBB/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/M2GLQQUEY5VFM57CFYXVIFOXN2HUZPDM/
- https://bugzilla.redhat.com/show_bug.cgi?id=2077976
- https://github.com/PCRE2Project/pcre2/commit/50a51cb7e67268e6ad417eb07c9de9bfea5cc55a
- https://bugzilla.redhat.com/show_bug.cgi?id=2077976%2C
- https://github.com/PCRE2Project/pcre2/commit/50a51cb7e67268e6ad417eb07c9de9bfea5cc55a%2C
- https://github.com/PCRE2Project/pcre2/commit/d4fa336fbcc388f89095b184ba6d99422cfc676c
- https://lists.debian.org/debian-lts-announce/2023/03/msg00014.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/DWNG2NS3GINO6LQYUVC4BZLUQPJ3DYHA/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/JXINO3KKI5DICQ45E2FKD6MKVMGJLEKJ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/KAX7767BCUFC7JMDGP7GOQ5GIZCAUGBB/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/M2GLQQUEY5VFM57CFYXVIFOXN2HUZPDM/
- https://security.netapp.com/advisory/ntap-20221028-0009/
critical severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.32.1-4+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › perl/perl-base@5.32.1-4+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Perl versions before 5.40.5-RC1, from 5.41.0 before 5.42.3-RC1, from 5.43.0 before 5.43.10 produce silently incorrect regular expression matches when an alternation of more than 65535 fixed string branches is compiled into a trie in Perl_study_chunk.
When such branches are combined into a trie, the delta between the first branch and the shared tail is stored in a 16-bit field. A branch count above 65535 overflows the field, and the trie's match decision table is truncated with no warning or error.
A pattern of this shape produces false positive matches (matching strings it should not) and false negative matches (failing to match strings it should). When such a pattern gates an access or filtering decision, the result is wrong.
Remediation
There is no fixed version for Debian:11 perl.
References
critical severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.32.1-4+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › perl/perl-base@5.32.1-4+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Archive::Tar versions before 3.08 for Perl extract symlinks with attacker controlled targets outside the extraction directory.
_make_special_file() passes the tar header's linkname to symlink() without validating it against absolute paths or .. segments. The secure-extract mode check that guards regular file extraction does not cover the symlink target.
A subsequent open through the extracted name reads or writes the attacker chosen path.
Remediation
There is no fixed version for Debian:11 perl.
References
- https://security-tracker.debian.org/tracker/CVE-2026-42496
- https://github.com/jib/archive-tar-new/commit/17c873492a05eddc0de18c1485e0b2cccd5a9158.patch
- https://metacpan.org/release/BINGOS/Archive-Tar-3.08/changes
- https://www.cve.org/CVERecord?id=CVE-2026-42497
- https://access.redhat.com/errata/RHSA-2026:30851
- https://access.redhat.com/errata/RHSA-2026:30852
- https://access.redhat.com/errata/RHSA-2026:30856
- https://access.redhat.com/errata/RHSA-2026:30857
- https://access.redhat.com/security/cve/CVE-2026-42496
- https://bugzilla.redhat.com/show_bug.cgi?id=2481314
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-42496.json
high severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
- Fixed in: 7.74.0-1.3+deb11u8
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A vulnerability in input validation exists in curl <8.0 during communication using the TELNET protocol may allow an attacker to pass on maliciously crafted user name and "telnet options" during server negotiation. The lack of proper input scrubbing allows an attacker to send content or perform option negotiation without the application's intent. This vulnerability could be exploited if an application allows user input, thereby enabling attackers to execute arbitrary code on the system.
Remediation
Upgrade Debian:11 curl to version 7.74.0-1.3+deb11u8 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-27533
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/36NBD5YLJXXEDZLDGNFCERWRYJQ6LAQW/
- https://hackerone.com/reports/1891474
- https://lists.debian.org/debian-lts-announce/2023/04/msg00025.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/36NBD5YLJXXEDZLDGNFCERWRYJQ6LAQW/
- https://security.gentoo.org/glsa/202310-12
- https://security.netapp.com/advisory/ntap-20230420-0011/
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-943925.html
high severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
- Fixed in: 7.74.0-1.3+deb11u8
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A path traversal vulnerability exists in curl <8.0.0 SFTP implementation causes the tilde () character to be wrongly replaced when used as a prefix in the first path element, in addition to its intended use as the first element to indicate a path relative to the user's home directory. Attackers can exploit this flaw to bypass filtering or execute arbitrary code by crafting a path like /2/foo while accessing a server with a specific user.
Remediation
Upgrade Debian:11 curl to version 7.74.0-1.3+deb11u8 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-27534
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/36NBD5YLJXXEDZLDGNFCERWRYJQ6LAQW/
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-806742.html
- https://cert-portal.siemens.com/productcert/html/ssa-943925.html
- https://hackerone.com/reports/1892351
- https://lists.debian.org/debian-lts-announce/2024/03/msg00016.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/36NBD5YLJXXEDZLDGNFCERWRYJQ6LAQW/
- https://security.gentoo.org/glsa/202310-12
- https://security.netapp.com/advisory/ntap-20230420-0012/
high severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.18.3-6+deb11u1, krb5/libk5crypto3@1.18.3-6+deb11u1 and others
- Fixed in: 1.18.3-6+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › krb5/libgssapi-krb5-2@1.18.3-6+deb11u1
-
Introduced through: nginx@1.21 › krb5/libk5crypto3@1.18.3-6+deb11u1
-
Introduced through: nginx@1.21 › krb5/libkrb5-3@1.18.3-6+deb11u1
-
Introduced through: nginx@1.21 › krb5/libkrb5support0@1.18.3-6+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
PAC parsing in MIT Kerberos 5 (aka krb5) before 1.19.4 and 1.20.x before 1.20.1 has integer overflows that may lead to remote code execution (in KDC, kadmind, or a GSS or Kerberos application server) on 32-bit platforms (which have a resultant heap-based buffer overflow), and cause a denial of service on other platforms. This occurs in krb5_pac_parse in lib/krb5/krb/pac.c. Heimdal before 7.7.1 has "a similar bug."
Remediation
Upgrade Debian:11 krb5 to version 1.18.3-6+deb11u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-42898
- https://bugzilla.samba.org/show_bug.cgi?id=15203
- https://github.com/heimdal/heimdal/security/advisories/GHSA-64mq-fvfj-5x3c
- https://github.com/krb5/krb5/commit/ea92d2f0fcceb54a70910fa32e9a0d7a5afc3583
- https://security.gentoo.org/glsa/202309-06
- https://security.gentoo.org/glsa/202310-06
- https://security.netapp.com/advisory/ntap-20230216-0008/
- https://security.netapp.com/advisory/ntap-20230223-0001/
- https://web.mit.edu/kerberos/advisories/
- https://web.mit.edu/kerberos/krb5-1.19/
- https://web.mit.edu/kerberos/krb5-1.20/README-1.20.1.txt
- https://www.samba.org/samba/security/CVE-2022-42898.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
high severity
- Vulnerable module: libssh2/libssh2-1
- Introduced through: libssh2/libssh2-1@1.9.0-2
Detailed paths
-
Introduced through: nginx@1.21 › libssh2/libssh2-1@1.9.0-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libssh2 package and not the libssh2 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libssh2 through 1.11.1, fixed in commit 5e47761, contains a double-free vulnerability in the sftp_open() function in src/sftp.c that allows a malicious SSH server to corrupt the heap of any authenticated client opening an SFTP session. When a server responds to SSH_FXP_OPEN with SSH_FXP_STATUS containing FX_OK, the response data buffer is freed, and if a subsequent sftp_packet_require() call returns a specific error such as LIBSSH2_ERROR_CHANNEL_PACKET_EXCEEDED, the same pointer is freed a second time, enabling tcache dup conditions on glibc systems that allow overlapping allocations and function pointer overwrites.
Remediation
There is no fixed version for Debian:11 libssh2.
References
high severity
- Vulnerable module: libwebp/libwebp6
- Introduced through: libwebp/libwebp6@0.6.1-2.1
- Fixed in: 0.6.1-2.1+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › libwebp/libwebp6@0.6.1-2.1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libwebp package and not the libwebp package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Heap buffer overflow in libwebp in Google Chrome prior to 116.0.5845.187 and libwebp 1.3.2 allowed a remote attacker to perform an out of bounds memory write via a crafted HTML page. (Chromium security severity: Critical)
Remediation
Upgrade Debian:11 libwebp to version 0.6.1-2.1+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-4863
- https://www.vicarius.io/vsociety/posts/zero-day-webp-vulnerability-cve-2023-4863
- http://www.openwall.com/lists/oss-security/2023/09/21/4
- http://www.openwall.com/lists/oss-security/2023/09/22/1
- http://www.openwall.com/lists/oss-security/2023/09/22/3
- http://www.openwall.com/lists/oss-security/2023/09/22/4
- http://www.openwall.com/lists/oss-security/2023/09/22/5
- http://www.openwall.com/lists/oss-security/2023/09/22/6
- http://www.openwall.com/lists/oss-security/2023/09/22/7
- http://www.openwall.com/lists/oss-security/2023/09/22/8
- http://www.openwall.com/lists/oss-security/2023/09/26/1
- http://www.openwall.com/lists/oss-security/2023/09/26/7
- http://www.openwall.com/lists/oss-security/2023/09/28/1
- http://www.openwall.com/lists/oss-security/2023/09/28/2
- http://www.openwall.com/lists/oss-security/2023/09/28/4
- https://adamcaudill.com/2023/09/14/whose-cve-is-it-anyway/
- https://blog.isosceles.com/the-webp-0day/
- https://bugzilla.suse.com/show_bug.cgi?id=1215231
- https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-desktop_11.html
- https://crbug.com/1479274
- https://en.bandisoft.com/honeyview/history/
- https://github.com/webmproject/libwebp/commit/902bc9190331343b2017211debcec8d2ab87e17a
- https://github.com/webmproject/libwebp/releases/tag/v1.3.2
- https://lists.debian.org/debian-lts-announce/2023/09/msg00015.html
- https://lists.debian.org/debian-lts-announce/2023/09/msg00016.html
- https://lists.debian.org/debian-lts-announce/2023/09/msg00017.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/6T655QF7CQ3DYAMPFV7IECQYGDEUIVVT/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/FYYKLG6CRGEDTNRBSU26EEWAO6D6U645/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KUQ7CTX3W372X3UY56VVNAHCH6H2F4X3/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OZDGWWMJREPAGKWCJKSCM4WYLANSKIFX/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PYZV7TMKF4QHZ54SFJX54BDN52VHGGCX/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WHOLML7N2G5KCAZXFWC5IDFFHSQS5SDB/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WTRUIS3564P7ZLM2S2IH4Y4KZ327LI4I/
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-4863
- https://news.ycombinator.com/item?id=37478403
- https://security.gentoo.org/glsa/202309-05
- https://security.gentoo.org/glsa/202401-10
- https://security.netapp.com/advisory/ntap-20230929-0011/
- https://sethmlarson.dev/security-developer-in-residence-weekly-report-16
- https://stackdiary.com/critical-vulnerability-in-webp-codec-cve-2023-4863/
- https://www.bentley.com/advisories/be-2023-0001/
- https://www.bleepingcomputer.com/news/google/google-fixes-another-chrome-zero-day-bug-exploited-in-attacks/
- https://www.debian.org/security/2023/dsa-5496
- https://www.debian.org/security/2023/dsa-5497
- https://www.debian.org/security/2023/dsa-5498
- https://www.mozilla.org/en-US/security/advisories/mfsa2023-40/
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-4863
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- https://github.com/caoweiquan322/NotEnough
high severity
- Vulnerable module: libxpm/libxpm4
- Introduced through: libxpm/libxpm4@1:3.5.12-1
- Fixed in: 1:3.5.12-1.1~deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › libxpm/libxpm4@1:3.5.12-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxpm package and not the libxpm package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw was found in libXpm. When processing files with .Z or .gz extensions, the library calls external programs to compress and uncompress files, relying on the PATH environment variable to find these programs, which could allow a malicious user to execute other programs by manipulating the PATH environment variable.
Remediation
Upgrade Debian:11 libxpm to version 1:3.5.12-1.1~deb11u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-4883
- https://bugzilla.redhat.com/show_bug.cgi?id=2160213
- https://gitlab.freedesktop.org/xorg/lib/libxpm/-/commit/515294bb8023a45ff91669
- https://gitlab.freedesktop.org/xorg/lib/libxpm/-/merge_requests/9
- https://lists.debian.org/debian-lts-announce/2023/06/msg00021.html
- https://lists.x.org/archives/xorg-announce/2023-January/003312.html
high severity
- Vulnerable module: libxslt/libxslt1.1
- Introduced through: libxslt/libxslt1.1@1.1.34-4
- Fixed in: 1.1.34-4+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › libxslt/libxslt1.1@1.1.34-4
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:11 relevant fixed versions and status.
Use after free in Blink XSLT in Google Chrome prior to 91.0.4472.164 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Remediation
Upgrade Debian:11 libxslt to version 1.1.34-4+deb11u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2021-30560
- https://chromereleases.googleblog.com/2021/07/stable-channel-update-for-desktop.html
- https://crbug.com/1219209
- https://lists.debian.org/debian-lts-announce/2022/09/msg00010.html
- https://security.gentoo.org/glsa/202310-23
- https://www.debian.org/security/2022/dsa-5216
high severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u4
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libtiff 4.5.0 is vulnerable to Buffer Overflow via extractContigSamplesBytes() at /libtiff/tools/tiffcrop.c:3215.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u4 or higher.
References
high severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A vulnerability was found in LibTIFF. It has been classified as critical. This affects the function TIFFReadRGBATileExt of the file libtiff/tif_getimage.c. The manipulation leads to integer overflow. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The name of the patch is 227500897dfb07fb7d27f7aa570050e62617e3be. It is recommended to apply a patch to fix this issue. The identifier VDB-213549 was assigned to this vulnerability.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-3970
- https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=53137
- https://gitlab.com/libtiff/libtiff/-/commit/227500897dfb07fb7d27f7aa570050e62617e3be
- https://lists.debian.org/debian-lts-announce/2023/01/msg00018.html
- https://oss-fuzz.com/download?testcase_id=5738253143900160
- https://security.netapp.com/advisory/ntap-20221215-0009/
- https://support.apple.com/kb/HT213841
- https://support.apple.com/kb/HT213843
- https://vuldb.com/?id.213549
high severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u7
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw was found in Libtiff. This vulnerability is a "write-what-where" condition, triggered when the library processes a specially crafted TIFF image file.
By providing an abnormally large image height value in the file's metadata, an attacker can trick the library into writing attacker-controlled color data to an arbitrary memory location. This memory corruption can be exploited to cause a denial of service (application crash) or to achieve arbitrary code execution with the permissions of the user.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-9900
- https://access.redhat.com/security/cve/CVE-2025-9900
- https://bugzilla.redhat.com/show_bug.cgi?id=2392784
- https://access.redhat.com/errata/RHSA-2025:17651
- https://access.redhat.com/errata/RHSA-2025:17675
- https://access.redhat.com/errata/RHSA-2025:17710
- https://access.redhat.com/errata/RHSA-2025:17738
- https://access.redhat.com/errata/RHSA-2025:17739
- https://access.redhat.com/errata/RHSA-2025:17740
- https://access.redhat.com/errata/RHSA-2025:19113
- https://access.redhat.com/errata/RHSA-2025:19156
- https://access.redhat.com/errata/RHSA-2025:19276
- https://lists.debian.org/debian-lts-announce/2025/09/msg00031.html
- http://www.openwall.com/lists/oss-security/2025/09/26/3
- https://access.redhat.com/errata/RHSA-2025:19906
- https://gitlab.com/libtiff/libtiff/-/issues/704
- https://gitlab.com/libtiff/libtiff/-/merge_requests/732
- https://libtiff.gitlab.io/libtiff/releases/v4.7.1.html
- https://access.redhat.com/errata/RHSA-2025:19947
- https://access.redhat.com/errata/RHSA-2025:20956
- https://access.redhat.com/errata/RHSA-2025:20998
- https://access.redhat.com/errata/RHSA-2025:21061
- https://access.redhat.com/errata/RHSA-2025:21062
- https://access.redhat.com/errata/RHSA-2025:21060
- https://access.redhat.com/errata/RHSA-2025:21407
- https://access.redhat.com/errata/RHSA-2025:21506
- https://access.redhat.com/errata/RHSA-2025:21507
- https://access.redhat.com/errata/RHSA-2025:21508
- https://access.redhat.com/errata/RHSA-2025:21994
- https://access.redhat.com/errata/RHSA-2025:23078
- https://access.redhat.com/errata/RHSA-2025:23079
- https://access.redhat.com/errata/RHSA-2025:23080
- https://access.redhat.com/errata/RHSA-2026:0001
- https://access.redhat.com/errata/RHSA-2026:0078
- https://access.redhat.com/errata/RHSA-2026:0076
- https://access.redhat.com/errata/RHSA-2026:0077
- https://access.redhat.com/errata/RHSA-2026:3461
- https://access.redhat.com/errata/RHSA-2026:3462
- https://access.redhat.com/errata/RHSA-2026:7504
- https://github.com/SexyShoelessGodofWar/LibTiff-4.7.0-Write-What-Where?tab=readme-ov-file
high severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.32.1-4+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › perl/perl-base@5.32.1-4+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Perl versions before 5.40.5-RC1, from 5.41.0 before 5.42.3-RC1, from 5.43.0 before 5.43.11 have an integer overflow in S_measure_struct leading to an out-of-bounds heap read in pack and unpack.
S_measure_struct adds each item's size times its repeat count to a running total with no overflow check, so a large repeat count in a pack or unpack template wraps the signed SSize_t total negative. The @, X, and x position codes then guard their moves with a signed length comparison that passes when the length is negative, advancing the buffer pointer out of bounds.
A template derived from untrusted input can read heap memory past the buffer and return it to the caller.
Remediation
There is no fixed version for Debian:11 perl.
References
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.1-5
- Fixed in: 3.7.1-5+deb11u8
Detailed paths
-
Introduced through: nginx@1.21 › gnutls28/libgnutls30@3.7.1-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw was found in GnuTLS. 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:11 gnutls28 to version 3.7.1-5+deb11u8 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-32988
- https://access.redhat.com/security/cve/CVE-2025-32988
- https://bugzilla.redhat.com/show_bug.cgi?id=2359622
- https://access.redhat.com/errata/RHSA-2025:16115
- https://access.redhat.com/errata/RHSA-2025:16116
- https://access.redhat.com/errata/RHSA-2025:17348
- https://access.redhat.com/errata/RHSA-2025:17361
- https://access.redhat.com/errata/RHSA-2025:17415
- https://access.redhat.com/errata/RHSA-2025:19088
- https://lists.debian.org/debian-lts-announce/2025/08/msg00005.html
- http://www.openwall.com/lists/oss-security/2025/07/11/3
- https://access.redhat.com/errata/RHSA-2025:17181
- https://access.redhat.com/errata/RHSA-2025:22529
- https://lists.gnupg.org/pipermail/gnutls-help/2025-July/004883.html
- https://access.redhat.com/errata/RHSA-2026:7477
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.1-5
- Fixed in: 3.7.1-5+deb11u8
Detailed paths
-
Introduced through: nginx@1.21 › gnutls28/libgnutls30@3.7.1-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A 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:11 gnutls28 to version 3.7.1-5+deb11u8 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-32990
- https://access.redhat.com/security/cve/CVE-2025-32990
- https://bugzilla.redhat.com/show_bug.cgi?id=2359620
- https://access.redhat.com/errata/RHSA-2025:16115
- https://access.redhat.com/errata/RHSA-2025:16116
- https://access.redhat.com/errata/RHSA-2025:17348
- https://access.redhat.com/errata/RHSA-2025:17361
- https://access.redhat.com/errata/RHSA-2025:17415
- https://access.redhat.com/errata/RHSA-2025:19088
- https://lists.debian.org/debian-lts-announce/2025/08/msg00005.html
- http://www.openwall.com/lists/oss-security/2025/07/11/3
- https://access.redhat.com/errata/RHSA-2025:17181
- https://access.redhat.com/errata/RHSA-2025:22529
- https://lists.gnupg.org/pipermail/gnutls-help/2025-July/004883.html
- https://access.redhat.com/errata/RHSA-2026:7477
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.1-5
- Fixed in: 3.7.1-5+deb11u10
Detailed paths
-
Introduced through: nginx@1.21 › gnutls28/libgnutls30@3.7.1-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw was found in libgnutls. A remote attacker, by sending an extremely short premaster secret during an RSA key exchange to a server using an RSA key backed by a PKCS#11 token, could trigger a short heap overread. This memory corruption vulnerability could lead to information disclosure.
Remediation
Upgrade Debian:11 gnutls28 to version 3.7.1-5+deb11u10 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-5260
- https://access.redhat.com/security/cve/CVE-2026-5260
- https://bugzilla.redhat.com/show_bug.cgi?id=2467450
- https://access.redhat.com/errata/RHSA-2026:20611
- https://access.redhat.com/errata/RHSA-2026:20613
- https://access.redhat.com/errata/RHSA-2026:20612
- https://access.redhat.com/errata/RHSA-2026:13274
- https://access.redhat.com/errata/RHSA-2026:26319
- https://access.redhat.com/errata/RHSA-2026:26409
- https://access.redhat.com/errata/RHSA-2026:29197
- https://access.redhat.com/errata/RHSA-2026:30004
- https://access.redhat.com/errata/RHSA-2026:30849
- https://access.redhat.com/errata/RHSA-2026:30850
- https://access.redhat.com/errata/RHSA-2026:32962
- https://access.redhat.com/errata/RHSA-2026:33125
- https://access.redhat.com/errata/RHSA-2026:40762
- https://access.redhat.com/errata/RHSA-2026:41921
- https://www.gnutls.org/security-new.html#GNUTLS-SA-2026-04-29-10
- https://access.redhat.com/errata/RHSA-2026:58981
- https://access.redhat.com/errata/RHSA-2026:57483
- https://access.redhat.com/errata/RHSA-2026:56853
- https://access.redhat.com/errata/RHSA-2026:59831
- https://access.redhat.com/errata/RHSA-2026:60019
- https://access.redhat.com/errata/RHSA-2026:67837
- https://access.redhat.com/errata/RHSA-2026:72502
- https://access.redhat.com/errata/RHSA-2026:74674
- https://access.redhat.com/errata/RHSA-2026:82304
- https://access.redhat.com/errata/RHSA-2026:82322
- https://access.redhat.com/errata/RHSA-2026:82347
- https://access.redhat.com/errata/RHSA-2026:82354
- https://access.redhat.com/errata/RHSA-2026:82372
- https://access.redhat.com/errata/RHSA-2026:82857
- https://access.redhat.com/errata/RHSA-2026:82888
- https://access.redhat.com/errata/RHSA-2026:77320
- https://access.redhat.com/errata/RHSA-2026:82811
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.1-5
- Fixed in: 3.7.1-5+deb11u10
Detailed paths
-
Introduced through: nginx@1.21 › gnutls28/libgnutls30@3.7.1-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw was found in gnutls. When validating certificates, an oversized Subject Alternative Name (SAN) could cause the validation process to incorrectly fall back to checking the Common Name (CN) field. This could allow a remote attacker to bypass proper certificate validation, potentially leading to spoofing or man-in-the-middle attacks.
Remediation
Upgrade Debian:11 gnutls28 to version 3.7.1-5+deb11u10 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-42013
- https://access.redhat.com/security/cve/CVE-2026-42013
- https://bugzilla.redhat.com/show_bug.cgi?id=2467448
- https://access.redhat.com/errata/RHSA-2026:20611
- https://access.redhat.com/errata/RHSA-2026:20613
- https://access.redhat.com/errata/RHSA-2026:20612
- https://access.redhat.com/errata/RHSA-2026:13274
- https://access.redhat.com/errata/RHSA-2026:26319
- https://access.redhat.com/errata/RHSA-2026:26409
- https://access.redhat.com/errata/RHSA-2026:29197
- https://access.redhat.com/errata/RHSA-2026:30004
- https://access.redhat.com/errata/RHSA-2026:30849
- https://access.redhat.com/errata/RHSA-2026:30850
- https://access.redhat.com/errata/RHSA-2026:32962
- https://access.redhat.com/errata/RHSA-2026:33125
- https://access.redhat.com/errata/RHSA-2026:40762
- https://access.redhat.com/errata/RHSA-2026:41921
- https://access.redhat.com/errata/RHSA-2026:43575
- https://www.gnutls.org/security-new.html#GNUTLS-SA-2026-04-29-8
- https://access.redhat.com/errata/RHSA-2026:58981
- https://access.redhat.com/errata/RHSA-2026:57483
- https://access.redhat.com/errata/RHSA-2026:56853
- https://access.redhat.com/errata/RHSA-2026:59831
- https://access.redhat.com/errata/RHSA-2026:60019
- https://access.redhat.com/errata/RHSA-2026:72502
- https://access.redhat.com/errata/RHSA-2026:74674
- https://access.redhat.com/errata/RHSA-2026:82304
- https://access.redhat.com/errata/RHSA-2026:82322
- https://access.redhat.com/errata/RHSA-2026:82347
- https://access.redhat.com/errata/RHSA-2026:82354
- https://access.redhat.com/errata/RHSA-2026:82372
- https://access.redhat.com/errata/RHSA-2026:82857
- https://access.redhat.com/errata/RHSA-2026:82888
high severity
- Vulnerable module: nginx
- Introduced through: nginx@1.21.6-1~bullseye
Detailed paths
-
Introduced through: nginx@1.21 › nginx@1.21.6-1~bullseye
NVD Description
Note: Versions mentioned in the description apply only to the upstream nginx package and not the nginx package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
NGINX Plus and NGINX Open Source have a vulnerability in the ngx_http_slice_module module. When the slice directive and unnamed regex captures are configured or when a background cache update happens, unauthenticated attackers can send requests that may cause uninitialized memory access in the NGINX worker process, leading to limited disclosure of memory or a restart.
Impact: This vulnerability may allow remote, unauthenticated attackers to have limited control to disclose memory contents or restart the NGINX worker process. There is no control plane exposure; this is a data plane issue only. Note: The ngx_http_slice_module module is not enabled by default; it's enabled with the --with-http_slice_module configuration parameter.
Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
Remediation
There is no fixed version for Debian:11 nginx.
References
high severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
- Fixed in: 7.74.0-1.3+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
An improper authentication vulnerability exists in curl 7.33.0 to and including 7.82.0 which might allow reuse OAUTH2-authenticated connections without properly making sure that the connection was authenticated with the same credentials as set for this transfer. This affects SASL-enabled protocols: SMPTP(S), IMAP(S), POP3(S) and LDAP(S) (openldap only).
Remediation
Upgrade Debian:11 curl to version 7.74.0-1.3+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-22576
- https://lists.debian.org/debian-lts-announce/2022/08/msg00017.html
- https://security.gentoo.org/glsa/202212-01
- https://security.netapp.com/advisory/ntap-20220609-0008/
- https://www.debian.org/security/2022/dsa-5197
- https://cert-portal.siemens.com/productcert/html/ssa-146325.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://hackerone.com/reports/1526328
high severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.10-2+deb11u3
- Fixed in: 2.2.10-2+deb11u4
Detailed paths
-
Introduced through: nginx@1.21 › expat/libexpat1@2.2.10-2+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libexpat before 2.4.9 has a use-after-free in the doContent function in xmlparse.c.
Remediation
Upgrade Debian:11 expat to version 2.2.10-2+deb11u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-40674
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GSVZN3IJ6OCPSJL7AEX3ZHSHAHFOGESK/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/J2IGJNHFV53PYST7VQV3T4NHVYAMXA36/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LQB6FJAM5YQ35SF5B2MN25Y2FX56EOEZ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WE2ZKEPGFCZ7R6DRVH3K6RBJPT42ZBEG/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XCGBVQQ47URGJAZWHCISHDWF6QBTV2LE/
- https://github.com/libexpat/libexpat/pull/629
- https://github.com/libexpat/libexpat/pull/640
- https://lists.debian.org/debian-lts-announce/2022/09/msg00029.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/GSVZN3IJ6OCPSJL7AEX3ZHSHAHFOGESK/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/J2IGJNHFV53PYST7VQV3T4NHVYAMXA36/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LQB6FJAM5YQ35SF5B2MN25Y2FX56EOEZ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WE2ZKEPGFCZ7R6DRVH3K6RBJPT42ZBEG/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/XCGBVQQ47URGJAZWHCISHDWF6QBTV2LE/
- https://security.gentoo.org/glsa/202209-24
- https://security.gentoo.org/glsa/202211-06
- https://security.netapp.com/advisory/ntap-20221028-0008/
- https://www.debian.org/security/2022/dsa-5236
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-558014.html
- https://cert-portal.siemens.com/productcert/html/ssa-892048.html
high severity
- Vulnerable module: freetype/libfreetype6
- Introduced through: freetype/libfreetype6@2.10.4+dfsg-1
- Fixed in: 2.10.4+dfsg-1+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › freetype/libfreetype6@2.10.4+dfsg-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream freetype package and not the freetype package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
An out of bounds write exists in FreeType versions 2.13.0 and below (newer versions of FreeType are not vulnerable) when attempting to parse font subglyph structures related to TrueType GX and variable font files. The vulnerable code assigns a signed short value to an unsigned long and then adds a static value causing it to wrap around and allocate too small of a heap buffer. The code then writes up to 6 signed long integers out of bounds relative to this buffer. This may result in arbitrary code execution. This vulnerability may have been exploited in the wild.
Remediation
Upgrade Debian:11 freetype to version 2.10.4+dfsg-1+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-27363
- https://www.facebook.com/security/advisories/cve-2025-27363
- http://www.openwall.com/lists/oss-security/2025/03/13/1
- http://www.openwall.com/lists/oss-security/2025/03/13/11
- http://www.openwall.com/lists/oss-security/2025/03/13/12
- http://www.openwall.com/lists/oss-security/2025/03/13/2
- http://www.openwall.com/lists/oss-security/2025/03/13/3
- http://www.openwall.com/lists/oss-security/2025/03/13/8
- http://www.openwall.com/lists/oss-security/2025/03/14/1
- http://www.openwall.com/lists/oss-security/2025/03/14/2
- http://www.openwall.com/lists/oss-security/2025/03/14/3
- http://www.openwall.com/lists/oss-security/2025/03/14/4
- http://www.openwall.com/lists/oss-security/2025/05/06/3
- https://lists.debian.org/debian-lts-announce/2025/03/msg00030.html
- https://source.android.com/docs/security/bulletin/2025-05-01
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-27363
- http://www.openwall.com/lists/oss-security/2026/04/16/5
- http://www.openwall.com/lists/oss-security/2026/04/19/3
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- https://github.com/tin-z/CVE-2025-27363
high severity
- Vulnerable module: libpng1.6/libpng16-16
- Introduced through: libpng1.6/libpng16-16@1.6.37-3
- Fixed in: 1.6.37-3+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › libpng1.6/libpng16-16@1.6.37-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. Prior to 1.6.55, an out-of-bounds read vulnerability exists in the png_set_quantize() API function. When the function is called with no histogram and the number of colors in the palette is more than twice the maximum supported by the user's display, certain palettes will cause the function to enter into an infinite loop that reads past the end of an internal heap-allocated buffer. The images that trigger this vulnerability are valid per the PNG specification. This vulnerability is fixed in 1.6.55.
Remediation
Upgrade Debian:11 libpng1.6 to version 1.6.37-3+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-25646
- https://github.com/pnggroup/libpng/commit/01d03b8453eb30ade759cd45c707e5a1c7277d88
- http://www.openwall.com/lists/oss-security/2026/02/09/7
- https://access.redhat.com/errata/RHSA-2026:10097
- https://access.redhat.com/errata/RHSA-2026:12274
- https://access.redhat.com/errata/RHSA-2026:14773
- https://access.redhat.com/errata/RHSA-2026:15087
- https://access.redhat.com/errata/RHSA-2026:16174
- https://access.redhat.com/errata/RHSA-2026:17596
- https://access.redhat.com/errata/RHSA-2026:3031
- https://access.redhat.com/errata/RHSA-2026:3405
- https://access.redhat.com/errata/RHSA-2026:3551
- https://access.redhat.com/errata/RHSA-2026:3573
- https://access.redhat.com/errata/RHSA-2026:3574
- https://access.redhat.com/errata/RHSA-2026:3575
- https://access.redhat.com/errata/RHSA-2026:3576
- https://access.redhat.com/errata/RHSA-2026:3577
- https://access.redhat.com/errata/RHSA-2026:3968
- https://access.redhat.com/errata/RHSA-2026:3969
- https://access.redhat.com/errata/RHSA-2026:4221
- https://access.redhat.com/errata/RHSA-2026:4222
- https://access.redhat.com/errata/RHSA-2026:4306
- https://access.redhat.com/errata/RHSA-2026:4501
- https://access.redhat.com/errata/RHSA-2026:4728
- https://access.redhat.com/errata/RHSA-2026:4729
- https://access.redhat.com/errata/RHSA-2026:4730
- https://access.redhat.com/errata/RHSA-2026:4731
- https://access.redhat.com/errata/RHSA-2026:4732
- https://access.redhat.com/errata/RHSA-2026:4756
- https://access.redhat.com/errata/RHSA-2026:5606
- https://access.redhat.com/errata/RHSA-2026:6439
- https://access.redhat.com/errata/RHSA-2026:6445
- https://access.redhat.com/errata/RHSA-2026:6466
- https://access.redhat.com/errata/RHSA-2026:6467
- https://access.redhat.com/errata/RHSA-2026:6468
- https://access.redhat.com/errata/RHSA-2026:6469
- https://access.redhat.com/errata/RHSA-2026:6553
- https://access.redhat.com/errata/RHSA-2026:6732
- https://access.redhat.com/errata/RHSA-2026:7032
- https://access.redhat.com/errata/RHSA-2026:7033
- https://access.redhat.com/errata/RHSA-2026:7034
- https://access.redhat.com/errata/RHSA-2026:7035
- https://access.redhat.com/errata/RHSA-2026:7036
- https://access.redhat.com/errata/RHSA-2026:7239
- https://access.redhat.com/errata/RHSA-2026:7243
- https://access.redhat.com/errata/RHSA-2026:8746
- https://access.redhat.com/errata/RHSA-2026:8747
- https://access.redhat.com/errata/RHSA-2026:8748
- https://access.redhat.com/errata/RHSA-2026:9254
- https://access.redhat.com/errata/RHSA-2026:9255
- https://access.redhat.com/errata/RHSA-2026:9683
- https://access.redhat.com/errata/RHSA-2026:9686
- https://access.redhat.com/errata/RHSA-2026:9687
- https://access.redhat.com/errata/RHSA-2026:9689
- https://access.redhat.com/security/cve/CVE-2026-25646
- https://bugzilla.redhat.com/show_bug.cgi?id=2438542
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-25646.json
- https://github.com/pnggroup/libpng/security/advisories/GHSA-g8hp-mq4h-rqm3
high severity
- Vulnerable module: nginx
- Introduced through: nginx@1.21.6-1~bullseye
Detailed paths
-
Introduced through: nginx@1.21 › nginx@1.21.6-1~bullseye
NVD Description
Note: Versions mentioned in the description apply only to the upstream nginx package and not the nginx package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A vulnerability exists in NGINX Plus and NGINX Open Source when a map directive uses regex matching and a string expression references the map's regex capture variables before referencing the map output variable. Alternatively, the same result could be achieved by using a non-cacheable variable in a string expression under certain conditions. An unauthenticated attacker along with conditions beyond their control can exploit this vulnerability by sending crafted HTTP requests. This may cause a heap buffer overflow in the NGINX worker process leading to a restart. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR.
Impact: This vulnerability may allow remote attackers to cause a denial-of-service (DoS) on the NGINX system or to possibly trigger a code execution. There is no control plane exposure; this is a data plane issue only.
Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
Remediation
There is no fixed version for Debian:11 nginx.
References
high severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
- Fixed in: 1.1.1w-0+deb11u7
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Issue summary: An uncommon configuration of clients performing DANE TLSA-based server authentication, when paired with uncommon server DANE TLSA records, may result in a use-after-free and/or double-free on the client side.
Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of arbitrary code.
However, the issue only affects clients that make use of TLSA records with both the PKIX-TA(0/PKIX-EE(1) certificate usages and the DANE-TA(2) certificate usage.
By far the most common deployment of DANE is in SMTP MTAs for which RFC7672 recommends that clients treat as 'unusable' any TLSA records that have the PKIX certificate usages. These SMTP (or other similar) clients are not vulnerable to this issue. Conversely, any clients that support only the PKIX usages, and ignore the DANE-TA(2) usage are also not vulnerable.
The client would also need to be communicating with a server that publishes a TLSA RRset with both types of TLSA records.
No FIPS modules are affected by this issue, the problem code is outside the FIPS module boundary.
Remediation
Upgrade Debian:11 openssl to version 1.1.1w-0+deb11u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-28387
- https://github.com/openssl/openssl/commit/07e727d304746edb49a98ee8f6ab00256e1f012b
- https://github.com/openssl/openssl/commit/258a8f63b26995ba357f4326da00e19e29c6acbe
- https://github.com/openssl/openssl/commit/444958deaf450aea819171f97ae69eaedede42c3
- https://github.com/openssl/openssl/commit/7a4e08cee62a728d32e60b0de89e6764339df0a7
- https://github.com/openssl/openssl/commit/ec03fa050b3346997ed9c5fef3d0e16ad7db8177
- https://openssl-library.org/news/secadv/20260407.txt
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
high severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.32.1-4+deb11u2
- Fixed in: 5.32.1-4+deb11u4
Detailed paths
-
Introduced through: nginx@1.21 › perl/perl-base@5.32.1-4+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
CPAN.pm before 2.35 does not verify TLS certificates when downloading distributions over HTTPS.
Remediation
Upgrade Debian:11 perl to version 5.32.1-4+deb11u4 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: e2fsprogs
- Introduced through: e2fsprogs@1.46.2-2, e2fsprogs/libcom-err2@1.46.2-2 and others
- Fixed in: 1.46.2-2+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › e2fsprogs@1.46.2-2
-
Introduced through: nginx@1.21 › e2fsprogs/libcom-err2@1.46.2-2
-
Introduced through: nginx@1.21 › e2fsprogs/libext2fs2@1.46.2-2
-
Introduced through: nginx@1.21 › e2fsprogs/libss2@1.46.2-2
-
Introduced through: nginx@1.21 › e2fsprogs/logsave@1.46.2-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream e2fsprogs package and not the e2fsprogs package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
An out-of-bounds read/write vulnerability was found in e2fsprogs 1.46.5. This issue leads to a segmentation fault and possibly arbitrary code execution via a specially crafted filesystem.
Remediation
Upgrade Debian:11 e2fsprogs to version 1.46.2-2+deb11u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-1304
- https://access.redhat.com/errata/RHSA-2022:7720
- https://access.redhat.com/errata/RHSA-2022:8361
- https://access.redhat.com/security/cve/CVE-2022-1304
- https://lists.debian.org/debian-lts-announce/2024/10/msg00001.html
- https://security.netapp.com/advisory/ntap-20241122-0010/
- https://bugzilla.redhat.com/show_bug.cgi?id=2069726
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-419740.html
high severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.10-2+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › expat/libexpat1@2.2.10-2+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libexpat before 2.8.4 lacks handler call depth tracking with custom encoding callbacks. Thus, a use-after-free can occur. NOTE: this is similar to CVE-2026-50219, CVE-2026-56131 and CVE-2026-56412.
Remediation
There is no fixed version for Debian:11 expat.
References
high severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
- Fixed in: 2.31-13+deb11u4
Detailed paths
-
Introduced through: nginx@1.21 › glibc/libc-bin@2.31-13+deb11u3
-
Introduced through: nginx@1.21 › glibc/libc6@2.31-13+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw was found in glibc. An off-by-one buffer overflow and underflow in getcwd() may lead to memory corruption when the size of the buffer is exactly 1. A local attacker who can control the input buffer and size passed to getcwd() in a setuid program could use this flaw to potentially execute arbitrary code and escalate their privileges on the system.
Remediation
Upgrade Debian:11 glibc to version 2.31-13+deb11u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2021-3999
- https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=23e0e8f5f1fb5ed150253d986ecccdc90c2dcd5e
- https://access.redhat.com/errata/RHSA-2022:0896
- https://access.redhat.com/security/cve/CVE-2021-3999
- https://bugzilla.redhat.com/show_bug.cgi?id=2024637
- https://lists.debian.org/debian-lts-announce/2022/10/msg00021.html
- https://security.netapp.com/advisory/ntap-20221104-0001/
- https://sourceware.org/bugzilla/show_bug.cgi?id=28769
- https://sourceware.org/git/gitweb.cgi?p=glibc.git%3Bh=23e0e8f5f1fb5ed150253d986ecccdc90c2dcd5e
- https://www.openwall.com/lists/oss-security/2022/01/24/4
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-831302.html
high severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
- Fixed in: 2.31-13+deb11u7
Detailed paths
-
Introduced through: nginx@1.21 › glibc/libc-bin@2.31-13+deb11u3
-
Introduced through: nginx@1.21 › glibc/libc6@2.31-13+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A buffer overflow was discovered in the GNU C Library's dynamic loader ld.so while processing the GLIBC_TUNABLES environment variable. This issue could allow a local attacker to use maliciously crafted GLIBC_TUNABLES environment variables when launching binaries with SUID permission to execute code with elevated privileges.
Remediation
Upgrade Debian:11 glibc to version 2.31-13+deb11u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-4911
- http://packetstormsecurity.com/files/174986/glibc-ld.so-Local-Privilege-Escalation.html
- http://packetstormsecurity.com/files/176288/Glibc-Tunables-Privilege-Escalation.html
- http://seclists.org/fulldisclosure/2023/Oct/11
- http://www.openwall.com/lists/oss-security/2023/10/03/2
- http://www.openwall.com/lists/oss-security/2023/10/03/3
- http://www.openwall.com/lists/oss-security/2023/10/05/1
- http://www.openwall.com/lists/oss-security/2023/10/13/11
- http://www.openwall.com/lists/oss-security/2023/10/14/3
- http://www.openwall.com/lists/oss-security/2023/10/14/5
- http://www.openwall.com/lists/oss-security/2023/10/14/6
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4DBUQRRPB47TC3NJOUIBVWUGFHBJAFDL/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DFG4P76UHHZEWQ26FWBXG76N2QLKKPZA/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NDAQWHTSVOCOZ5K6KPIWKRT3JX4RTZUR/
- https://security.gentoo.org/glsa/202310-03
- https://security.netapp.com/advisory/ntap-20231013-0006/
- https://www.debian.org/security/2023/dsa-5514
- https://access.redhat.com/errata/RHBA-2024:2413
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-4911
- https://www.exploit-db.com/exploits/52479
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-794697.html
- https://cert-portal.siemens.com/productcert/html/ssa-831302.html
- https://access.redhat.com/errata/RHSA-2023:5453
- https://access.redhat.com/errata/RHSA-2023:5454
- https://access.redhat.com/errata/RHSA-2023:5455
- https://access.redhat.com/errata/RHSA-2023:5476
- https://access.redhat.com/errata/RHSA-2024:0033
- https://access.redhat.com/security/cve/CVE-2023-4911
- https://bugzilla.redhat.com/show_bug.cgi?id=2238352
- https://www.qualys.com/2023/10/03/cve-2023-4911/looney-tunables-local-privilege-escalation-glibc-ld-so.txt
- https://www.qualys.com/cve-2023-4911/
- https://github.com/projectdiscovery/nuclei-templates/blob/main/code/cves/2023/CVE-2023-4911.yaml
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- https://github.com/KernelKrise/CVE-2023-4911
high severity
- Vulnerable module: libpng1.6/libpng16-16
- Introduced through: libpng1.6/libpng16-16@1.6.37-3
- Fixed in: 1.6.37-3+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › libpng1.6/libpng16-16@1.6.37-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From 1.6.26 to 1.6.53, there is an integer truncation in the libpng simplified write API functions png_write_image_16bit and png_write_image_8bit causes heap buffer over-read when the caller provides a negative row stride (for bottom-up image layouts) or a stride exceeding 65535 bytes. The bug was introduced in libpng 1.6.26 (October 2016) by casts added to silence compiler warnings on 16-bit systems. This vulnerability is fixed in 1.6.54.
Remediation
Upgrade Debian:11 libpng1.6 to version 1.6.37-3+deb11u2 or higher.
References
high severity
- Vulnerable module: libx11/libx11-6
- Introduced through: libx11/libx11-6@2:1.7.2-1 and libx11/libx11-data@2:1.7.2-1
- Fixed in: 2:1.7.2-1+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › libx11/libx11-6@2:1.7.2-1
-
Introduced through: nginx@1.21 › libx11/libx11-data@2:1.7.2-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libx11 package and not the libx11 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A vulnerability was found in libX11 due to an integer overflow within the XCreateImage() function. This flaw allows a local user to trigger an integer overflow and execute arbitrary code with elevated privileges.
Remediation
Upgrade Debian:11 libx11 to version 2:1.7.2-1+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-43787
- http://www.openwall.com/lists/oss-security/2024/01/24/9
- https://jfrog.com/blog/xorg-libx11-vulns-cve-2023-43786-cve-2023-43787-part-two/
- https://security.netapp.com/advisory/ntap-20231103-0006/
- https://access.redhat.com/errata/RHSA-2024:2145
- https://access.redhat.com/errata/RHSA-2024:2973
- https://access.redhat.com/security/cve/CVE-2023-43787
- https://bugzilla.redhat.com/show_bug.cgi?id=2242254
- https://lists.debian.org/debian-lts-announce/2023/10/msg00005.html
high severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.10+dfsg-6.7+deb11u2
- Fixed in: 2.9.10+dfsg-6.7+deb11u6
Detailed paths
-
Introduced through: nginx@1.21 › libxml2@2.9.10+dfsg-6.7+deb11u2
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:11 relevant fixed versions and status.
xmlXIncludeAddNode in xinclude.c in libxml2 before 2.11.0 has a use-after-free.
Remediation
Upgrade Debian:11 libxml2 to version 2.9.10+dfsg-6.7+deb11u6 or higher.
References
high severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.10+dfsg-6.7+deb11u2
- Fixed in: 2.9.10+dfsg-6.7+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › libxml2@2.9.10+dfsg-6.7+deb11u2
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:11 relevant fixed versions and status.
An issue was discovered in libxml2 before 2.10.3. Certain invalid XML entity definitions can corrupt a hash table key, potentially leading to subsequent logic errors. In one case, a double-free can be provoked.
Remediation
Upgrade Debian:11 libxml2 to version 2.9.10+dfsg-6.7+deb11u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-40304
- http://seclists.org/fulldisclosure/2022/Dec/21
- http://seclists.org/fulldisclosure/2022/Dec/24
- http://seclists.org/fulldisclosure/2022/Dec/25
- http://seclists.org/fulldisclosure/2022/Dec/26
- http://seclists.org/fulldisclosure/2022/Dec/27
- https://gitlab.gnome.org/GNOME/libxml2/-/commit/1b41ec4e9433b05bb0376be4725804c54ef1d80b
- https://gitlab.gnome.org/GNOME/libxml2/-/tags
- https://gitlab.gnome.org/GNOME/libxml2/-/tags/v2.10.3
- https://security.netapp.com/advisory/ntap-20221209-0003/
- https://support.apple.com/kb/HT213531
- https://support.apple.com/kb/HT213533
- https://support.apple.com/kb/HT213534
- https://support.apple.com/kb/HT213535
- https://support.apple.com/kb/HT213536
- https://cert-portal.siemens.com/productcert/html/ssa-337522.html
- https://cert-portal.siemens.com/productcert/html/ssa-341067.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-556635.html
- https://cert-portal.siemens.com/productcert/html/ssa-625862.html
- https://cert-portal.siemens.com/productcert/html/ssa-769027.html
high severity
- Vulnerable module: libxslt/libxslt1.1
- Introduced through: libxslt/libxslt1.1@1.1.34-4
- Fixed in: 1.1.34-4+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › libxslt/libxslt1.1@1.1.34-4
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:11 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:11 libxslt to version 1.1.34-4+deb11u2 or higher.
References
high severity
- Vulnerable module: libxslt/libxslt1.1
- Introduced through: libxslt/libxslt1.1@1.1.34-4
- Fixed in: 1.1.34-4+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › libxslt/libxslt1.1@1.1.34-4
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:11 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:11 libxslt to version 1.1.34-4+deb11u2 or higher.
References
high severity
- Vulnerable module: ncurses/libtinfo6
- Introduced through: ncurses/libtinfo6@6.2+20201114-2, ncurses/ncurses-base@6.2+20201114-2 and others
- Fixed in: 6.2+20201114-2+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › ncurses/libtinfo6@6.2+20201114-2
-
Introduced through: nginx@1.21 › ncurses/ncurses-base@6.2+20201114-2
-
Introduced through: nginx@1.21 › ncurses/ncurses-bin@6.2+20201114-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
ncurses before 6.4 20230408, when used by a setuid application, allows local users to trigger security-relevant memory corruption via malformed data in a terminfo database file that is found in $HOME/.terminfo or reached via the TERMINFO or TERM environment variable.
Remediation
Upgrade Debian:11 ncurses to version 6.2+20201114-2+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-29491
- http://ncurses.scripts.mit.edu/?p=ncurses.git;a=commit;h=eb51b1ea1f75a0ec17c9c5937cb28df1e8eeec56
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LU4MYMKFEZQ5VSCVLRIZGDQOUW3T44GT/
- http://ncurses.scripts.mit.edu/?p=ncurses.git%3Ba=commit%3Bh=eb51b1ea1f75a0ec17c9c5937cb28df1e8eeec56
- http://www.openwall.com/lists/oss-security/2023/04/19/10
- http://www.openwall.com/lists/oss-security/2023/04/19/11
- https://lists.debian.org/debian-lts-announce/2023/12/msg00004.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LU4MYMKFEZQ5VSCVLRIZGDQOUW3T44GT/
- https://security.netapp.com/advisory/ntap-20230517-0009/
- https://support.apple.com/kb/HT213843
- https://support.apple.com/kb/HT213844
- https://support.apple.com/kb/HT213845
- https://www.openwall.com/lists/oss-security/2023/04/12/5
- https://www.openwall.com/lists/oss-security/2023/04/13/4
- https://cert-portal.siemens.com/productcert/html/ssa-202008.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
high severity
- Vulnerable module: pam/libpam-modules
- Introduced through: pam/libpam-modules@1.4.0-9+deb11u1, pam/libpam-modules-bin@1.4.0-9+deb11u1 and others
- Fixed in: 1.4.0-9+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › pam/libpam-modules@1.4.0-9+deb11u1
-
Introduced through: nginx@1.21 › pam/libpam-modules-bin@1.4.0-9+deb11u1
-
Introduced through: nginx@1.21 › pam/libpam-runtime@1.4.0-9+deb11u1
-
Introduced through: nginx@1.21 › pam/libpam0g@1.4.0-9+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream pam package and not the pam package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
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:11 pam to version 1.4.0-9+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-6020
- https://access.redhat.com/security/cve/CVE-2025-6020
- https://bugzilla.redhat.com/show_bug.cgi?id=2372512
- http://www.openwall.com/lists/oss-security/2025/06/17/1
- https://access.redhat.com/errata/RHSA-2025:9526
- https://access.redhat.com/errata/RHSA-2025:10024
- https://access.redhat.com/errata/RHSA-2025:10027
- https://access.redhat.com/errata/RHSA-2025:10180
- https://access.redhat.com/errata/RHSA-2025:10354
- https://access.redhat.com/errata/RHSA-2025:10357
- https://access.redhat.com/errata/RHSA-2025:10358
- https://access.redhat.com/errata/RHSA-2025:10359
- https://access.redhat.com/errata/RHSA-2025:10361
- https://access.redhat.com/errata/RHSA-2025:10362
- https://access.redhat.com/errata/RHSA-2025:10735
- https://access.redhat.com/errata/RHSA-2025:10823
- https://access.redhat.com/errata/RHSA-2025:11386
- https://access.redhat.com/errata/RHSA-2025:11487
- https://access.redhat.com/errata/RHSA-2025:14557
- https://access.redhat.com/errata/RHSA-2025:15099
- https://access.redhat.com/errata/RHSA-2025:15709
- https://access.redhat.com/errata/RHSA-2025:15828
- https://access.redhat.com/errata/RHSA-2025:15827
- https://access.redhat.com/errata/RHSA-2025:16524
- https://access.redhat.com/errata/RHSA-2025:18219
- https://lists.debian.org/debian-lts-announce/2025/09/msg00021.html
- https://access.redhat.com/errata/RHSA-2025:17181
- https://access.redhat.com/errata/RHSA-2025:20181
- https://access.redhat.com/errata/RHSA-2025:21885
- https://access.redhat.com/errata/RHSA-2025:22019
- https://access.redhat.com/errata/RHSA-2026:0934
- https://github.com/linux-pam/linux-pam/security/advisories/GHSA-f9p8-gjr4-j9gx
- https://cert-portal.siemens.com/productcert/html/ssa-577017.html
high severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.32.1-4+deb11u2
- Fixed in: 5.32.1-4+deb11u4
Detailed paths
-
Introduced through: nginx@1.21 › perl/perl-base@5.32.1-4+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
CPAN 2.28 allows Signature Verification Bypass.
Remediation
Upgrade Debian:11 perl to version 5.32.1-4+deb11u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2020-16156
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SD6RYOJII7HRJ6WVORFNVTYNOFY5JDXN/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SZ32AJIV4RHJMLWLU5QULGKMMIHYOMDC/
- https://lists.debian.org/debian-lts-announce/2024/10/msg00017.html
- http://blogs.perl.org/users/neilb/2021/11/addressing-cpan-vulnerabilities-related-to-checksums.html
- https://blog.hackeriet.no/cpan-signature-verification-vulnerabilities/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/SD6RYOJII7HRJ6WVORFNVTYNOFY5JDXN/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/SZ32AJIV4RHJMLWLU5QULGKMMIHYOMDC/
- https://metacpan.org/pod/distribution/CPAN/scripts/cpan
high severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.32.1-4+deb11u2
- Fixed in: 5.32.1-4+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › perl/perl-base@5.32.1-4+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A vulnerability was found in perl 5.30.0 through 5.38.0. This issue occurs when a crafted regular expression is compiled by perl, which can allow an attacker controlled byte buffer overflow in a heap allocated buffer.
Remediation
Upgrade Debian:11 perl to version 5.32.1-4+deb11u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-47038
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GNEEWAACXQCEEAKSG7XX2D5YDRWLCIZJ/
- https://perldoc.perl.org/perl5382delta#CVE-2023-47038-Write-past-buffer-end-via-illegal-user-defined-Unicode-property
- https://github.com/Perl/perl5/commit/12c313ce49b36160a7ca2e9b07ad5bd92ee4a010
- https://github.com/Perl/perl5/commit/7047915eef37fccd93e7cd985c29fe6be54650b6
- https://github.com/Perl/perl5/commit/ff1f9f59360afeebd6f75ca1502f5c3ebf077da3
- https://github.com/aquasecurity/trivy/discussions/8400
- https://ubuntu.com/security/CVE-2023-47100
- https://www.suse.com/security/cve/CVE-2023-47100.html
- https://access.redhat.com/errata/RHSA-2024:2228
- https://access.redhat.com/errata/RHSA-2024:3128
- https://access.redhat.com/security/cve/CVE-2023-47038
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056746
- https://bugzilla.redhat.com/show_bug.cgi?id=2249523
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UMDZZ4SCEW6FRWZDMXGAKZ35THTAWFG6/
high severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u8
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw was found in the libtiff library. A remote attacker could exploit a signed integer overflow vulnerability in the putcontig8bitYCbCr44tile function by providing a specially crafted TIFF file. This flaw can lead to an out-of-bounds heap write due to incorrect memory pointer calculations, potentially causing a denial of service (application crash) or arbitrary code execution.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u8 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-4775
- https://lists.debian.org/debian-lts-announce/2026/04/msg00016.html
- https://access.redhat.com/errata/RHSA-2026:33388
- https://access.redhat.com/errata/RHSA-2026:74674
- https://access.redhat.com/errata/RHSA-2026:12265
- https://access.redhat.com/errata/RHSA-2026:12271
- https://access.redhat.com/errata/RHSA-2026:14929
- https://access.redhat.com/errata/RHSA-2026:16055
- https://access.redhat.com/errata/RHSA-2026:19150
- https://access.redhat.com/errata/RHSA-2026:19363
- https://access.redhat.com/errata/RHSA-2026:19585
- https://access.redhat.com/errata/RHSA-2026:19586
- https://access.redhat.com/errata/RHSA-2026:19604
- https://access.redhat.com/errata/RHSA-2026:19608
- https://access.redhat.com/errata/RHSA-2026:19609
- https://access.redhat.com/errata/RHSA-2026:19657
- https://access.redhat.com/errata/RHSA-2026:19659
- https://access.redhat.com/errata/RHSA-2026:19702
- https://access.redhat.com/errata/RHSA-2026:20583
- https://access.redhat.com/errata/RHSA-2026:20585
- https://access.redhat.com/errata/RHSA-2026:20591
- https://access.redhat.com/errata/RHSA-2026:20592
- https://access.redhat.com/errata/RHSA-2026:24992
- https://access.redhat.com/errata/RHSA-2026:25096
- https://access.redhat.com/errata/RHSA-2026:25910
- https://access.redhat.com/errata/RHSA-2026:30078
- https://access.redhat.com/errata/RHSA-2026:30087
- https://access.redhat.com/errata/RHSA-2026:30088
- https://access.redhat.com/errata/RHSA-2026:30089
- https://access.redhat.com/errata/RHSA-2026:30349
- https://access.redhat.com/security/cve/CVE-2026-4775
- https://bugzilla.redhat.com/show_bug.cgi?id=2450768
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-4775.json
high severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.10+dfsg-6.7+deb11u2
- Fixed in: 2.9.10+dfsg-6.7+deb11u6
Detailed paths
-
Introduced through: nginx@1.21 › libxml2@2.9.10+dfsg-6.7+deb11u2
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:11 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:11 libxml2 to version 2.9.10+dfsg-6.7+deb11u6 or higher.
References
high severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
- Fixed in: 7.74.0-1.3+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A user can tell curl >= 7.20.0 and <= 7.78.0 to require a successful upgrade to TLS when speaking to an IMAP, POP3 or FTP server (--ssl-reqd on the command line orCURLOPT_USE_SSL set to CURLUSESSL_CONTROL or CURLUSESSL_ALL withlibcurl). This requirement could be bypassed if the server would return a properly crafted but perfectly legitimate response.This flaw would then make curl silently continue its operations withoutTLS contrary to the instructions and expectations, exposing possibly sensitive data in clear text over the network.
Remediation
Upgrade Debian:11 curl to version 7.74.0-1.3+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2021-22946
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RWLEC6YVEM2HWUBX67SDGPSY4CQB72OE/
- https://hackerone.com/reports/1334111
- https://www.oracle.com/security-alerts/cpuoct2021.html
- https://lists.debian.org/debian-lts-announce/2021/09/msg00022.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/APOAK4X73EJTAPTSVT7IRVDMUWVXNWGD/
- http://seclists.org/fulldisclosure/2022/Mar/29
- https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf
- https://lists.debian.org/debian-lts-announce/2022/08/msg00017.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/APOAK4X73EJTAPTSVT7IRVDMUWVXNWGD/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/RWLEC6YVEM2HWUBX67SDGPSY4CQB72OE/
- https://security.gentoo.org/glsa/202212-01
- https://security.netapp.com/advisory/ntap-20211029-0003/
- https://security.netapp.com/advisory/ntap-20220121-0008/
- https://support.apple.com/kb/HT213183
- https://www.debian.org/security/2022/dsa-5197
- https://www.oracle.com/security-alerts/cpuapr2022.html
- https://www.oracle.com/security-alerts/cpujan2022.html
- https://www.oracle.com/security-alerts/cpujul2022.html
- https://cert-portal.siemens.com/productcert/html/ssa-146325.html
- https://cert-portal.siemens.com/productcert/html/ssa-389290.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
high severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
In curl before 7.86.0, the HSTS check could be bypassed to trick it into staying with HTTP. Using its HSTS support, curl can be instructed to use HTTPS directly (instead of using an insecure cleartext HTTP step) even when HTTP is provided in the URL. This mechanism could be bypassed if the host name in the given URL uses IDN characters that get replaced with ASCII counterparts as part of the IDN conversion, e.g., using the character UTF-8 U+3002 (IDEOGRAPHIC FULL STOP) instead of the common ASCII full stop of U+002E (.). The earliest affected version is 7.77.0 2021-05-26.
Remediation
There is no fixed version for Debian:11 curl.
References
- https://security-tracker.debian.org/tracker/CVE-2022-42916
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/37YEVVC6NAF6H7UHH6YAUY5QEVY6LIH2/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HVU3IMZCKR4VE6KJ4GCWRL2ILLC6OV76/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/Q27V5YYMXUVI6PRZQVECON32XPVWTKDK/
- http://seclists.org/fulldisclosure/2023/Jan/19
- http://seclists.org/fulldisclosure/2023/Jan/20
- http://www.openwall.com/lists/oss-security/2022/12/21/1
- https://curl.se/docs/CVE-2022-42916.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/37YEVVC6NAF6H7UHH6YAUY5QEVY6LIH2/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HVU3IMZCKR4VE6KJ4GCWRL2ILLC6OV76/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/Q27V5YYMXUVI6PRZQVECON32XPVWTKDK/
- https://security.gentoo.org/glsa/202212-01
- https://security.netapp.com/advisory/ntap-20221209-0010/
- https://support.apple.com/kb/HT213604
- https://support.apple.com/kb/HT213605
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-892048.html
high severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A vulnerability exists in curl <7.87.0 HSTS check that could be bypassed to trick it to keep using HTTP. Using its HSTS support, curl can be instructed to use HTTPS instead of using an insecure clear-text HTTP step even when HTTP is provided in the URL. However, the HSTS mechanism could be bypassed if the host name in the given URL first uses IDN characters that get replaced to ASCII counterparts as part of the IDN conversion. Like using the character UTF-8 U+3002 (IDEOGRAPHIC FULL STOP) instead of the common ASCII full stop (U+002E) .. Then in a subsequent request, it does not detect the HSTS state and makes a clear text transfer. Because it would store the info IDN encoded but look for it IDN decoded.
Remediation
There is no fixed version for Debian:11 curl.
References
- https://security-tracker.debian.org/tracker/CVE-2022-43551
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TVWZW5CNSJ7UYAF2BGSYAWAEXDJYUBHA/
- https://hackerone.com/reports/1755083
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/TVWZW5CNSJ7UYAF2BGSYAWAEXDJYUBHA/
- https://security.gentoo.org/glsa/202310-12
- https://security.netapp.com/advisory/ntap-20230427-0007/
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-892048.html
high severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
- Fixed in: 7.74.0-1.3+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
An information disclosure vulnerability exists in curl 7.65.0 to 7.82.0 are vulnerable that by using an IPv6 address that was in the connection pool but with a different zone id it could reuse a connection instead.
Remediation
Upgrade Debian:11 curl to version 7.74.0-1.3+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-27775
- https://security.gentoo.org/glsa/202212-01
- https://security.netapp.com/advisory/ntap-20220609-0008/
- https://www.debian.org/security/2022/dsa-5197
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://hackerone.com/reports/1546268
high severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
- Fixed in: 7.74.0-1.3+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libcurl would reuse a previously created connection even when a TLS or SSHrelated option had been changed that should have prohibited reuse.libcurl keeps previously used connections in a connection pool for subsequenttransfers to reuse if one of them matches the setup. However, several TLS andSSH settings were left out from the configuration match checks, making themmatch too easily.
Remediation
Upgrade Debian:11 curl to version 7.74.0-1.3+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-27782
- http://www.openwall.com/lists/oss-security/2023/03/20/6
- https://lists.debian.org/debian-lts-announce/2022/08/msg00017.html
- https://security.gentoo.org/glsa/202212-01
- https://security.netapp.com/advisory/ntap-20220609-0009/
- https://www.debian.org/security/2022/dsa-5197
- https://cert-portal.siemens.com/productcert/html/ssa-146325.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://hackerone.com/reports/1555796
high severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
- Fixed in: 7.74.0-1.3+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libcurl provides the CURLOPT_CERTINFO option to allow applications torequest details to be returned about a server's certificate chain.Due to an erroneous function, a malicious server could make libcurl built withNSS get stuck in a never-ending busy-loop when trying to retrieve thatinformation.
Remediation
Upgrade Debian:11 curl to version 7.74.0-1.3+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-27781
- https://lists.debian.org/debian-lts-announce/2022/08/msg00017.html
- https://security.gentoo.org/glsa/202212-01
- https://security.netapp.com/advisory/ntap-20220609-0009/
- https://www.debian.org/security/2022/dsa-5197
- https://cert-portal.siemens.com/productcert/html/ssa-146325.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://hackerone.com/reports/1555441
high severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.10-2+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › expat/libexpat1@2.2.10-2+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
In libexpat before 2.8.1, the computational complexity of attribute name collision checks allows a denial of service via moderately sized crafted XML input.
Remediation
There is no fixed version for Debian:11 expat.
References
- https://security-tracker.debian.org/tracker/CVE-2026-45186
- https://github.com/libexpat/libexpat/pull/1216
- http://www.openwall.com/lists/oss-security/2026/05/11/16
- https://access.redhat.com/errata/RHSA-2026:22715
- https://access.redhat.com/errata/RHSA-2026:22721
- https://access.redhat.com/errata/RHSA-2026:23230
- https://access.redhat.com/errata/RHSA-2026:26319
- https://access.redhat.com/errata/RHSA-2026:27201
- https://access.redhat.com/errata/RHSA-2026:29197
- https://access.redhat.com/security/cve/CVE-2026-45186
- https://bugzilla.redhat.com/show_bug.cgi?id=2468575
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-45186.json
- https://access.redhat.com/errata/RHSA-2026:58981
high severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.10-2+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › expat/libexpat1@2.2.10-2+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Expat through 2.8.3 contains a denial of service vulnerability caused by quadratic algorithmic complexity in the storeAtts() function in xmlparse.c, where processing N specified attributes with non-normalized values triggers an O(N^2) linear scan of elementType->defaultAtts to determine CDATA status. A remote unauthenticated attacker can supply a single well-formed XML document of a few megabytes to an application parsing untrusted XML to cause excessive CPU consumption, resulting in denial of service without requiring authentication, external entity resolution, or non-default parser options.
Remediation
There is no fixed version for Debian:11 expat.
References
high severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.10-2+deb11u3
- Fixed in: 2.2.10-2+deb11u6
Detailed paths
-
Introduced through: nginx@1.21 › expat/libexpat1@2.2.10-2+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libexpat through 2.5.0 allows a denial of service (resource consumption) because many full reparsings are required in the case of a large token for which multiple buffer fills are needed.
Remediation
Upgrade Debian:11 expat to version 2.2.10-2+deb11u6 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-52425
- https://lists.debian.org/debian-lts-announce/2024/09/msg00036.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PNRIHC7DVVRAIWFRGV23Y6UZXFBXSQDB/
- http://www.openwall.com/lists/oss-security/2024/03/20/5
- https://github.com/libexpat/libexpat/pull/789
- https://lists.debian.org/debian-lts-announce/2024/04/msg00006.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PNRIHC7DVVRAIWFRGV23Y6UZXFBXSQDB/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WNUBSGZFEZOBHJFTAD42SAN4ATW2VEMV/
- https://security.netapp.com/advisory/ntap-20240614-0003/
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-784301.html
high severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.10-2+deb11u3
- Fixed in: 2.2.10-2+deb11u5
Detailed paths
-
Introduced through: nginx@1.21 › expat/libexpat1@2.2.10-2+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
In libexpat through 2.4.9, there is a use-after free caused by overeager destruction of a shared DTD in XML_ExternalEntityParserCreate in out-of-memory situations.
Remediation
Upgrade Debian:11 expat to version 2.2.10-2+deb11u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-43680
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/AJ5VY2VYXE4WTRGQ6LMGLF6FV3SY37YE/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BY4OPSIB33ETNUXZY2UPZ4NGQ3OKDY4D/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DPQVIF6TOJNY2T3ZZETFKR4G34FFREBQ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/FFCOMBSOJKLIKCGCJWHLJXO4EVYBG7AR/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/IUJ2BULJTZ2BMSKQHB6US674P55UCWWS/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XG5XOOB7CD55CEE6OJYKSACSIMQ4RWQ6/
- http://www.openwall.com/lists/oss-security/2023/12/28/5
- http://www.openwall.com/lists/oss-security/2024/01/03/5
- https://github.com/libexpat/libexpat/issues/649
- https://github.com/libexpat/libexpat/pull/616
- https://github.com/libexpat/libexpat/pull/650
- https://lists.debian.org/debian-lts-announce/2022/10/msg00033.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/AJ5VY2VYXE4WTRGQ6LMGLF6FV3SY37YE/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BY4OPSIB33ETNUXZY2UPZ4NGQ3OKDY4D/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/DPQVIF6TOJNY2T3ZZETFKR4G34FFREBQ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FFCOMBSOJKLIKCGCJWHLJXO4EVYBG7AR/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/IUJ2BULJTZ2BMSKQHB6US674P55UCWWS/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/XG5XOOB7CD55CEE6OJYKSACSIMQ4RWQ6/
- https://security.gentoo.org/glsa/202210-38
- https://security.netapp.com/advisory/ntap-20221118-0007/
- https://www.debian.org/security/2022/dsa-5266
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-892048.html
high severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.10-2+deb11u3
- Fixed in: 2.2.10-2+deb11u6
Detailed paths
-
Introduced through: nginx@1.21 › expat/libexpat1@2.2.10-2+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
An issue was discovered in libexpat before 2.6.3. xmlparse.c does not reject a negative length for XML_ParseBuffer.
Remediation
Upgrade Debian:11 expat to version 2.2.10-2+deb11u6 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-45490
- https://github.com/libexpat/libexpat/issues/887
- https://github.com/libexpat/libexpat/pull/890
- https://security.netapp.com/advisory/ntap-20241018-0004/
- http://seclists.org/fulldisclosure/2024/Dec/10
- http://seclists.org/fulldisclosure/2024/Dec/12
- http://seclists.org/fulldisclosure/2024/Dec/6
- http://seclists.org/fulldisclosure/2024/Dec/7
- http://seclists.org/fulldisclosure/2024/Dec/8
- https://lists.debian.org/debian-lts-announce/2024/09/msg00036.html
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-613116.html
high severity
- Vulnerable module: freetype/libfreetype6
- Introduced through: freetype/libfreetype6@2.10.4+dfsg-1
- Fixed in: 2.10.4+dfsg-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › freetype/libfreetype6@2.10.4+dfsg-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream freetype package and not the freetype package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
FreeType commit 22a0cccb4d9d002f33c1ba7a4b36812c7d4f46b5 was discovered to contain a segmentation violation via the function FT_Request_Size.
Remediation
Upgrade Debian:11 freetype to version 2.10.4+dfsg-1+deb11u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-27406
- http://freetype.com
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/EFPNRKDLCXHZVYYQLQMP44UHLU32GA6Z/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FDU2FOEMCEF6WVR6ZBIH5MT5O7FAK6UP/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/IWQ7IB2A75MEHM63WEUXBYEC7OR5SGDY/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/NYVC2NPKKXKP3TWJWG4ONYWNO6ZPHLA5/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/TCEMWCM46PKM4U5ENRASPKQD6JDOLKRU/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/EFPNRKDLCXHZVYYQLQMP44UHLU32GA6Z/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/FDU2FOEMCEF6WVR6ZBIH5MT5O7FAK6UP/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/IWQ7IB2A75MEHM63WEUXBYEC7OR5SGDY/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NYVC2NPKKXKP3TWJWG4ONYWNO6ZPHLA5/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TCEMWCM46PKM4U5ENRASPKQD6JDOLKRU/
- https://gitlab.freedesktop.org/freetype/freetype/-/issues/1140
- https://security.gentoo.org/glsa/202402-06
high severity
- Vulnerable module: freetype/libfreetype6
- Introduced through: freetype/libfreetype6@2.10.4+dfsg-1
- Fixed in: 2.10.4+dfsg-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › freetype/libfreetype6@2.10.4+dfsg-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream freetype package and not the freetype package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
FreeType commit 53dfdcd8198d2b3201a23c4bad9190519ba918db was discovered to contain a segmentation violation via the function FNT_Size_Request.
Remediation
Upgrade Debian:11 freetype to version 2.10.4+dfsg-1+deb11u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-27405
- http://freetype.com
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/EFPNRKDLCXHZVYYQLQMP44UHLU32GA6Z/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FDU2FOEMCEF6WVR6ZBIH5MT5O7FAK6UP/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/IWQ7IB2A75MEHM63WEUXBYEC7OR5SGDY/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/NYVC2NPKKXKP3TWJWG4ONYWNO6ZPHLA5/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/TCEMWCM46PKM4U5ENRASPKQD6JDOLKRU/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/EFPNRKDLCXHZVYYQLQMP44UHLU32GA6Z/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/FDU2FOEMCEF6WVR6ZBIH5MT5O7FAK6UP/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/IWQ7IB2A75MEHM63WEUXBYEC7OR5SGDY/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NYVC2NPKKXKP3TWJWG4ONYWNO6ZPHLA5/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TCEMWCM46PKM4U5ENRASPKQD6JDOLKRU/
- https://gitlab.freedesktop.org/freetype/freetype/-/issues/1139
- https://security.gentoo.org/glsa/202402-06
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.1-5
- Fixed in: 3.7.1-5+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › gnutls28/libgnutls30@3.7.1-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A vulnerability found in gnutls. This security flaw happens because of a double free error occurs during verification of pkcs7 signatures in gnutls_pkcs7_verify function.
Remediation
Upgrade Debian:11 gnutls28 to version 3.7.1-5+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-2509
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/6FL27JS3VM74YEQU7PGB62USO3KSBYZX/
- https://access.redhat.com/security/cve/CVE-2022-2509
- https://lists.debian.org/debian-lts-announce/2022/08/msg00002.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/6FL27JS3VM74YEQU7PGB62USO3KSBYZX/
- https://lists.gnupg.org/pipermail/gnutls-help/2022-July/004746.html
- https://www.debian.org/security/2022/dsa-5203
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.1-5
- Fixed in: 3.7.1-5+deb11u10
Detailed paths
-
Introduced through: nginx@1.21 › gnutls28/libgnutls30@3.7.1-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A heap buffer overflow vulnerability exists in the DTLS handshake fragment reassembly logic of GnuTLS. The issue arises in merge_handshake_packet() where incoming handshake fragments are matched and merged based solely on handshake type, without validating that the message_length field remains consistent across all fragments of the same logical message. An attacker can exploit this by sending crafted DTLS fragments with conflicting message_length values, causing the implementation to allocate a buffer based on a smaller initial fragment and subsequently write beyond its bounds using larger, inconsistent fragments. Because the merge operation does not enforce proper bounds checking against the allocated buffer size, this results in an out-of-bounds write on the heap. The vulnerability is remotely exploitable without authentication via the DTLS handshake path and can lead to application crashes or potential memory corruption.
Remediation
Upgrade Debian:11 gnutls28 to version 3.7.1-5+deb11u10 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-33846
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-33846.json
- https://access.redhat.com/errata/RHSA-2026:72502
- https://access.redhat.com/errata/RHSA-2026:74674
- https://access.redhat.com/errata/RHSA-2026:82304
- https://access.redhat.com/errata/RHSA-2026:82322
- https://access.redhat.com/errata/RHSA-2026:82347
- https://access.redhat.com/errata/RHSA-2026:82354
- https://access.redhat.com/errata/RHSA-2026:82372
- https://access.redhat.com/errata/RHSA-2026:82857
- https://access.redhat.com/errata/RHSA-2026:82888
- https://access.redhat.com/errata/RHSA-2026:13274
- https://access.redhat.com/errata/RHSA-2026:20611
- https://access.redhat.com/errata/RHSA-2026:20612
- https://access.redhat.com/errata/RHSA-2026:20613
- https://access.redhat.com/errata/RHSA-2026:26319
- https://access.redhat.com/errata/RHSA-2026:26409
- https://access.redhat.com/errata/RHSA-2026:29197
- https://access.redhat.com/errata/RHSA-2026:30004
- https://access.redhat.com/errata/RHSA-2026:30849
- https://access.redhat.com/errata/RHSA-2026:30850
- https://access.redhat.com/errata/RHSA-2026:32962
- https://access.redhat.com/errata/RHSA-2026:33125
- https://access.redhat.com/errata/RHSA-2026:34372
- https://access.redhat.com/errata/RHSA-2026:36004
- https://access.redhat.com/errata/RHSA-2026:36005
- https://access.redhat.com/errata/RHSA-2026:36006
- https://access.redhat.com/errata/RHSA-2026:41921
- https://access.redhat.com/errata/RHSA-2026:56786
- https://access.redhat.com/errata/RHSA-2026:56853
- https://access.redhat.com/errata/RHSA-2026:56911
- https://access.redhat.com/errata/RHSA-2026:57402
- https://access.redhat.com/errata/RHSA-2026:57483
- https://access.redhat.com/errata/RHSA-2026:58981
- https://access.redhat.com/errata/RHSA-2026:59831
- https://access.redhat.com/errata/RHSA-2026:60019
- https://access.redhat.com/errata/RHSA-2026:65839
- https://access.redhat.com/security/cve/CVE-2026-33846
- https://bugzilla.redhat.com/show_bug.cgi?id=2450625
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.1-5
- Fixed in: 3.7.1-5+deb11u5
Detailed paths
-
Introduced through: nginx@1.21 › gnutls28/libgnutls30@3.7.1-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A vulnerability was found in GnuTLS, where a cockpit (which uses gnuTLS) rejects a certificate chain with distributed trust. This issue occurs when validating a certificate chain with cockpit-certificate-ensure. This flaw allows an unauthenticated, remote client or attacker to initiate a denial of service attack.
Remediation
Upgrade Debian:11 gnutls28 to version 3.7.1-5+deb11u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-0567
- http://www.openwall.com/lists/oss-security/2024/01/19/3
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/7ZEIOLORQ7N6WRPFXZSYDL2MC4LP7VFV/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GNXKVR5YNUEBNHAHM5GSYKBZX4W2HMN2/
- https://security.netapp.com/advisory/ntap-20240202-0011/
- https://access.redhat.com/errata/RHSA-2024:0533
- https://access.redhat.com/errata/RHSA-2024:1082
- https://access.redhat.com/errata/RHSA-2024:1383
- https://access.redhat.com/errata/RHSA-2024:2094
- https://access.redhat.com/security/cve/CVE-2024-0567
- https://bugzilla.redhat.com/show_bug.cgi?id=2258544
- https://gitlab.com/gnutls/gnutls/-/issues/1521
- https://lists.gnupg.org/pipermail/gnutls-help/2024-January/004841.html
- https://cert-portal.siemens.com/productcert/html/ssa-794697.html
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.1-5
- Fixed in: 3.7.1-5+deb11u5
Detailed paths
-
Introduced through: nginx@1.21 › gnutls28/libgnutls30@3.7.1-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A vulnerability was found in GnuTLS. The response times to malformed ciphertexts in RSA-PSK ClientKeyExchange differ from the response times of ciphertexts with correct PKCS#1 v1.5 padding. This issue may allow a remote attacker to perform a timing side-channel attack in the RSA-PSK key exchange, potentially leading to the leakage of sensitive data. CVE-2024-0553 is designated as an incomplete resolution for CVE-2023-5981.
Remediation
Upgrade Debian:11 gnutls28 to version 3.7.1-5+deb11u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-0553
- http://www.openwall.com/lists/oss-security/2024/01/19/3
- https://lists.debian.org/debian-lts-announce/2024/02/msg00010.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/7ZEIOLORQ7N6WRPFXZSYDL2MC4LP7VFV/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GNXKVR5YNUEBNHAHM5GSYKBZX4W2HMN2/
- https://security.netapp.com/advisory/ntap-20240202-0011/
- https://access.redhat.com/errata/RHSA-2024:0533
- https://access.redhat.com/errata/RHSA-2024:0627
- https://access.redhat.com/errata/RHSA-2024:0796
- https://access.redhat.com/errata/RHSA-2024:1082
- https://access.redhat.com/errata/RHSA-2024:1108
- https://access.redhat.com/errata/RHSA-2024:1383
- https://access.redhat.com/errata/RHSA-2024:2094
- https://access.redhat.com/security/cve/CVE-2024-0553
- https://bugzilla.redhat.com/show_bug.cgi?id=2258412
- https://gitlab.com/gnutls/gnutls/-/issues/1522
- https://lists.gnupg.org/pipermail/gnutls-help/2024-January/004841.html
- https://cert-portal.siemens.com/productcert/html/ssa-794697.html
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.1-5
- Fixed in: 3.7.1-5+deb11u10
Detailed paths
-
Introduced through: nginx@1.21 › gnutls28/libgnutls30@3.7.1-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw was found in gnutls. A remote attacker could exploit an issue in the Datagram Transport Layer Security (DTLS) packet reordering logic. The comparator function, responsible for ordering DTLS packets by sequence numbers, did not correctly handle packets with duplicate sequence numbers. This could lead to unstable packet ordering or undefined behavior, resulting in a denial of service.
Remediation
Upgrade Debian:11 gnutls28 to version 3.7.1-5+deb11u10 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-42009
- https://www.gnutls.org/security-new.html#GNUTLS-SA-2026-04-29-2
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-42009.json
- https://access.redhat.com/errata/RHSA-2026:72502
- https://access.redhat.com/errata/RHSA-2026:74674
- https://access.redhat.com/errata/RHSA-2026:82304
- https://access.redhat.com/errata/RHSA-2026:82322
- https://access.redhat.com/errata/RHSA-2026:82347
- https://access.redhat.com/errata/RHSA-2026:82354
- https://access.redhat.com/errata/RHSA-2026:82372
- https://access.redhat.com/errata/RHSA-2026:82857
- https://access.redhat.com/errata/RHSA-2026:82888
- https://access.redhat.com/errata/RHSA-2026:13274
- https://access.redhat.com/errata/RHSA-2026:20611
- https://access.redhat.com/errata/RHSA-2026:20612
- https://access.redhat.com/errata/RHSA-2026:20613
- https://access.redhat.com/errata/RHSA-2026:26319
- https://access.redhat.com/errata/RHSA-2026:26409
- https://access.redhat.com/errata/RHSA-2026:29197
- https://access.redhat.com/errata/RHSA-2026:29794
- https://access.redhat.com/errata/RHSA-2026:30004
- https://access.redhat.com/errata/RHSA-2026:30849
- https://access.redhat.com/errata/RHSA-2026:30850
- https://access.redhat.com/errata/RHSA-2026:32962
- https://access.redhat.com/errata/RHSA-2026:33125
- https://access.redhat.com/errata/RHSA-2026:34372
- https://access.redhat.com/errata/RHSA-2026:34764
- https://access.redhat.com/errata/RHSA-2026:34788
- https://access.redhat.com/errata/RHSA-2026:36004
- https://access.redhat.com/errata/RHSA-2026:36005
- https://access.redhat.com/errata/RHSA-2026:36006
- https://access.redhat.com/errata/RHSA-2026:40762
- https://access.redhat.com/errata/RHSA-2026:41921
- https://access.redhat.com/errata/RHSA-2026:56786
- https://access.redhat.com/errata/RHSA-2026:56853
- https://access.redhat.com/errata/RHSA-2026:56911
- https://access.redhat.com/errata/RHSA-2026:57483
- https://access.redhat.com/errata/RHSA-2026:58981
- https://access.redhat.com/errata/RHSA-2026:59831
- https://access.redhat.com/errata/RHSA-2026:60019
- https://access.redhat.com/errata/RHSA-2026:65839
- https://access.redhat.com/security/cve/CVE-2026-42009
- https://bugzilla.redhat.com/show_bug.cgi?id=2467279
high severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.18.3-6+deb11u1, krb5/libk5crypto3@1.18.3-6+deb11u1 and others
- Fixed in: 1.18.3-6+deb11u5
Detailed paths
-
Introduced through: nginx@1.21 › krb5/libgssapi-krb5-2@1.18.3-6+deb11u1
-
Introduced through: nginx@1.21 › krb5/libk5crypto3@1.18.3-6+deb11u1
-
Introduced through: nginx@1.21 › krb5/libkrb5-3@1.18.3-6+deb11u1
-
Introduced through: nginx@1.21 › krb5/libkrb5support0@1.18.3-6+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
In MIT Kerberos 5 (aka krb5) before 1.21.3, an attacker can modify the plaintext Extra Count field of a confidential GSS krb5 wrap token, causing the unwrapped token to appear truncated to the application.
Remediation
Upgrade Debian:11 krb5 to version 1.18.3-6+deb11u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-37370
- https://security.netapp.com/advisory/ntap-20241108-0007/
- https://github.com/krb5/krb5/commit/55fbf435edbe2e92dd8101669b1ce7144bc96fef
- https://web.mit.edu/kerberos/www/advisories/
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
high severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.18.3-6+deb11u1, krb5/libk5crypto3@1.18.3-6+deb11u1 and others
- Fixed in: 1.18.3-6+deb11u8
Detailed paths
-
Introduced through: nginx@1.21 › krb5/libgssapi-krb5-2@1.18.3-6+deb11u1
-
Introduced through: nginx@1.21 › krb5/libk5crypto3@1.18.3-6+deb11u1
-
Introduced through: nginx@1.21 › krb5/libkrb5-3@1.18.3-6+deb11u1
-
Introduced through: nginx@1.21 › krb5/libkrb5support0@1.18.3-6+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
In MIT Kerberos 5 (aka krb5) before 1.22.3, there is a NULL pointer dereference if an application calls gss_accept_sec_context() on a system with a NegoEx mechanism registered in /etc/gss/mech. An unauthenticated remote attacker can trigger this, causing the process to terminate in parse_nego_message.
Remediation
Upgrade Debian:11 krb5 to version 1.18.3-6+deb11u8 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-40355
- https://github.com/krb5/krb5/commit/2e75f0d9362fb979f5fc92829431a590a130929f
- https://web.mit.edu/kerberos/advisories/
- https://cems.fun/2026/04/27/krb5-two-unauthenticated-network-vulnerabilities.html
- https://cert-portal.siemens.com/productcert/html/ssa-019113.html
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html
high severity
- Vulnerable module: libgd2/libgd3
- Introduced through: libgd2/libgd3@2.3.0-2
- Fixed in: 2.3.0-2+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › libgd2/libgd3@2.3.0-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libgd2 package and not the libgd2 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
gdImageGd2Ptr in gd_gd2.c in the GD Graphics Library (aka LibGD) through 2.3.2 has a double free. NOTE: the vendor's position is "The GD2 image format is a proprietary image format of libgd. It has to be regarded as being obsolete, and should only be used for development and testing purposes.
Remediation
Upgrade Debian:11 libgd2 to version 2.3.0-2+deb11u1 or higher.
References
high severity
- Vulnerable module: libssh2/libssh2-1
- Introduced through: libssh2/libssh2-1@1.9.0-2
Detailed paths
-
Introduced through: nginx@1.21 › libssh2/libssh2-1@1.9.0-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libssh2 package and not the libssh2 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libssh2 through 1.11.1, fixed in commit a13bb6c, contains a missing bounds check vulnerability that allows a malicious SSH server to trigger an arbitrary-length heap out-of-bounds read and a free of an uninitialized pointer via the publickey subsystem. In libssh2_publickey_list_fetch(), the version 1 response parser reads a server-controlled comment_len value and advances the parse pointer without verifying sufficient bytes remain in the buffer, causing the out-of-bounds read to leak heap pointers from adjacent allocations defeating ASLR, followed by heap allocator state corruption when the error cleanup path frees an uninitialized pointer from a non-zeroed realloc() region.
Remediation
There is no fixed version for Debian:11 libssh2.
References
high severity
- Vulnerable module: libssh2/libssh2-1
- Introduced through: libssh2/libssh2-1@1.9.0-2
- Fixed in: 1.9.0-2+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › libssh2/libssh2-1@1.9.0-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libssh2 package and not the libssh2 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
An issue was discovered in function _libssh2_packet_add in libssh2 1.10.0 allows attackers to access out of bounds memory.
Remediation
Upgrade Debian:11 libssh2 to version 1.9.0-2+deb11u1 or higher.
References
high severity
- Vulnerable module: libtirpc/libtirpc-common
- Introduced through: libtirpc/libtirpc-common@1.3.1-1 and libtirpc/libtirpc3@1.3.1-1
- Fixed in: 1.3.1-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › libtirpc/libtirpc-common@1.3.1-1
-
Introduced through: nginx@1.21 › libtirpc/libtirpc3@1.3.1-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libtirpc package and not the libtirpc package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
In libtirpc before 1.3.3rc1, remote attackers could exhaust the file descriptors of a process that uses libtirpc because idle TCP connections are mishandled. This can, in turn, lead to an svc_run infinite loop without accepting new connections.
Remediation
Upgrade Debian:11 libtirpc to version 1.3.1-1+deb11u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2021-46828
- http://git.linux-nfs.org/?p=steved/libtirpc.git;a=commit;h=86529758570cef4c73fb9b9c4104fdc510f701ed
- http://git.linux-nfs.org/?p=steved/libtirpc.git%3Ba=commit%3Bh=86529758570cef4c73fb9b9c4104fdc510f701ed
- https://lists.debian.org/debian-lts-announce/2022/08/msg00004.html
- https://security.gentoo.org/glsa/202210-33
- https://security.netapp.com/advisory/ntap-20221007-0004/
- https://www.debian.org/security/2022/dsa-5200
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-558014.html
- https://cert-portal.siemens.com/productcert/html/ssa-561322.html
high severity
- Vulnerable module: libwebp/libwebp6
- Introduced through: libwebp/libwebp6@0.6.1-2.1
- Fixed in: 0.6.1-2.1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › libwebp/libwebp6@0.6.1-2.1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libwebp package and not the libwebp package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
There exists a use after free/double free in libwebp. An attacker can use the ApplyFiltersAndEncode() function and loop through to free best.bw and assign best = trial pointer. The second loop will then return 0 because of an Out of memory error in VP8 encoder, the pointer is still assigned to trial and the AddressSanitizer will attempt a double free.
Remediation
Upgrade Debian:11 libwebp to version 0.6.1-2.1+deb11u1 or higher.
References
high severity
- Vulnerable module: libx11/libx11-6
- Introduced through: libx11/libx11-6@2:1.7.2-1 and libx11/libx11-data@2:1.7.2-1
- Fixed in: 2:1.7.2-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › libx11/libx11-6@2:1.7.2-1
-
Introduced through: nginx@1.21 › libx11/libx11-data@2:1.7.2-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libx11 package and not the libx11 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A vulnerability was found in libX11. The security flaw occurs because the functions in src/InitExt.c in libX11 do not check that the values provided for the Request, Event, or Error IDs are within the bounds of the arrays that those functions write to, using those IDs as array indexes. They trust that they were called with values provided by an Xserver adhering to the bounds specified in the X11 protocol, as all X servers provided by X.Org do. As the protocol only specifies a single byte for these values, an out-of-bounds value provided by a malicious server (or a malicious proxy-in-the-middle) can only overwrite other portions of the Display structure and not write outside the bounds of the Display structure itself, possibly causing the client to crash with this memory corruption.
Remediation
Upgrade Debian:11 libx11 to version 2:1.7.2-1+deb11u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-3138
- https://access.redhat.com/security/cve/CVE-2023-3138
- https://gitlab.freedesktop.org/xorg/lib/libx11/-/commit/304a654a0d57bf0f00d8998185f0360332cfa36c
- https://lists.x.org/archives/xorg-announce/2023-June/003406.html
- https://lists.x.org/archives/xorg-announce/2023-June/003407.html
- https://security.netapp.com/advisory/ntap-20231208-0008/
high severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.10+dfsg-6.7+deb11u2
- Fixed in: 2.9.10+dfsg-6.7+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › libxml2@2.9.10+dfsg-6.7+deb11u2
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:11 relevant fixed versions and status.
An issue was discovered in libxml2 before 2.10.3. When parsing a multi-gigabyte XML document with the XML_PARSE_HUGE parser option enabled, several integer counters can overflow. This results in an attempt to access an array at a negative 2GB offset, typically leading to a segmentation fault.
Remediation
Upgrade Debian:11 libxml2 to version 2.9.10+dfsg-6.7+deb11u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-40303
- http://seclists.org/fulldisclosure/2022/Dec/21
- http://seclists.org/fulldisclosure/2022/Dec/24
- http://seclists.org/fulldisclosure/2022/Dec/25
- http://seclists.org/fulldisclosure/2022/Dec/26
- http://seclists.org/fulldisclosure/2022/Dec/27
- https://gitlab.gnome.org/GNOME/libxml2/-/commit/c846986356fc149915a74972bf198abc266bc2c0
- https://gitlab.gnome.org/GNOME/libxml2/-/tags/v2.10.3
- https://security.netapp.com/advisory/ntap-20221209-0003/
- https://support.apple.com/kb/HT213531
- https://support.apple.com/kb/HT213533
- https://support.apple.com/kb/HT213534
- https://support.apple.com/kb/HT213535
- https://support.apple.com/kb/HT213536
- https://cert-portal.siemens.com/productcert/html/ssa-337522.html
- https://cert-portal.siemens.com/productcert/html/ssa-341067.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-556635.html
- https://cert-portal.siemens.com/productcert/html/ssa-625862.html
- https://cert-portal.siemens.com/productcert/html/ssa-769027.html
high severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.10+dfsg-6.7+deb11u2
- Fixed in: 2.9.10+dfsg-6.7+deb11u5
Detailed paths
-
Introduced through: nginx@1.21 › libxml2@2.9.10+dfsg-6.7+deb11u2
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:11 relevant fixed versions and status.
NULL Pointer Dereference allows attackers to cause a denial of service (or application crash). This only applies when lxml is used together with libxml2 2.9.10 through 2.9.14. libxml2 2.9.9 and earlier are not affected. It allows triggering crashes through forged input data, given a vulnerable code sequence in the application. The vulnerability is caused by the iterwalk function (also used by the canonicalize function). Such code shouldn't be in wide-spread use, given that parsing + iterwalk would usually be replaced with the more efficient iterparse function. However, an XML converter that serialises to C14N would also be vulnerable, for example, and there are legitimate use cases for this code sequence. If untrusted input is received (also remotely) and processed via iterwalk function, a crash can be triggered.
Remediation
Upgrade Debian:11 libxml2 to version 2.9.10+dfsg-6.7+deb11u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-2309
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HGYC6L7ENH5VEGN3YWFBYMGKX6WNS7HZ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/URHHSIBTPTALXMECRLAC2EVDNAFSR5NO/
- https://lists.debian.org/debian-lts-announce/2024/09/msg00021.html
- https://github.com/lxml/lxml/commit/86368e9cf70a0ad23cccd5ee32de847149af0c6f
- https://huntr.dev/bounties/8264e74f-edda-4c40-9956-49de635105ba
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HGYC6L7ENH5VEGN3YWFBYMGKX6WNS7HZ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/URHHSIBTPTALXMECRLAC2EVDNAFSR5NO/
- https://security.gentoo.org/glsa/202208-06
- https://security.netapp.com/advisory/ntap-20220915-0006/
high severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.10+dfsg-6.7+deb11u2
- Fixed in: 2.9.10+dfsg-6.7+deb11u6
Detailed paths
-
Introduced through: nginx@1.21 › libxml2@2.9.10+dfsg-6.7+deb11u2
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:11 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:11 libxml2 to version 2.9.10+dfsg-6.7+deb11u6 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.10+dfsg-6.7+deb11u2
- Fixed in: 2.9.10+dfsg-6.7+deb11u7
Detailed paths
-
Introduced through: nginx@1.21 › libxml2@2.9.10+dfsg-6.7+deb11u2
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:11 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:11 libxml2 to version 2.9.10+dfsg-6.7+deb11u7 or higher.
References
high severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.10+dfsg-6.7+deb11u2
- Fixed in: 2.9.10+dfsg-6.7+deb11u8
Detailed paths
-
Introduced through: nginx@1.21 › libxml2@2.9.10+dfsg-6.7+deb11u2
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:11 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:11 libxml2 to version 2.9.10+dfsg-6.7+deb11u8 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://access.redhat.com/errata/RHSA-2026:7519
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
- https://gitlab.gnome.org/GNOME/libxml2/-/issues/926
high severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.10+dfsg-6.7+deb11u2
- Fixed in: 2.9.10+dfsg-6.7+deb11u7
Detailed paths
-
Introduced through: nginx@1.21 › libxml2@2.9.10+dfsg-6.7+deb11u2
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:11 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:11 libxml2 to version 2.9.10+dfsg-6.7+deb11u7 or higher.
References
high severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.10+dfsg-6.7+deb11u2
- Fixed in: 2.9.10+dfsg-6.7+deb11u6
Detailed paths
-
Introduced through: nginx@1.21 › libxml2@2.9.10+dfsg-6.7+deb11u2
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:11 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:11 libxml2 to version 2.9.10+dfsg-6.7+deb11u6 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-25062
- https://lists.debian.org/debian-lts-announce/2025/02/msg00028.html
- https://security.netapp.com/advisory/ntap-20241018-0009/
- https://gitlab.gnome.org/GNOME/libxml2/-/issues/604
- https://gitlab.gnome.org/GNOME/libxml2/-/tags
- https://cert-portal.siemens.com/productcert/html/ssa-784301.html
- https://cert-portal.siemens.com/productcert/html/ssa-794697.html
high severity
- Vulnerable module: libxpm/libxpm4
- Introduced through: libxpm/libxpm4@1:3.5.12-1
- Fixed in: 1:3.5.12-1.1~deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › libxpm/libxpm4@1:3.5.12-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxpm package and not the libxpm package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw was found in libXpm. When processing a file with width of 0 and a very large height, some parser functions will be called repeatedly and can lead to an infinite loop, resulting in a Denial of Service in the application linked to the library.
Remediation
Upgrade Debian:11 libxpm to version 1:3.5.12-1.1~deb11u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-44617
- https://bugzilla.redhat.com/show_bug.cgi?id=2160193
- https://gitlab.freedesktop.org/xorg/lib/libxpm/-/commit/f80fa6ae47ad4a5beacb28
- https://gitlab.freedesktop.org/xorg/lib/libxpm/-/merge_requests/9
- https://lists.debian.org/debian-lts-announce/2023/06/msg00021.html
- https://lists.x.org/archives/xorg-announce/2023-January/003312.html
high severity
- Vulnerable module: libxpm/libxpm4
- Introduced through: libxpm/libxpm4@1:3.5.12-1
- Fixed in: 1:3.5.12-1.1~deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › libxpm/libxpm4@1:3.5.12-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxpm package and not the libxpm package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw was found in libXpm. This issue occurs when parsing a file with a comment not closed; the end-of-file condition will not be detected, leading to an infinite loop and resulting in a Denial of Service in the application linked to the library.
Remediation
Upgrade Debian:11 libxpm to version 1:3.5.12-1.1~deb11u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-46285
- http://www.openwall.com/lists/oss-security/2023/10/03/1
- http://www.openwall.com/lists/oss-security/2023/10/03/10
- https://bugzilla.redhat.com/show_bug.cgi?id=2160092
- https://gitlab.freedesktop.org/xorg/lib/libxpm/-/commit/a3a7c6dcc3b629d7650148
- https://gitlab.freedesktop.org/xorg/lib/libxpm/-/merge_requests/9
- https://lists.debian.org/debian-lts-announce/2023/06/msg00021.html
- https://lists.x.org/archives/xorg-announce/2023-January/003312.html
high severity
- Vulnerable module: libxslt/libxslt1.1
- Introduced through: libxslt/libxslt1.1@1.1.34-4
- Fixed in: 1.1.34-4+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › libxslt/libxslt1.1@1.1.34-4
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:11 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:11 libxslt to version 1.1.34-4+deb11u3 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
- https://access.redhat.com/errata/RHBA-2025:12345
- https://access.redhat.com/errata/RHSA-2026:11015
high severity
- Vulnerable module: nghttp2/libnghttp2-14
- Introduced through: nghttp2/libnghttp2-14@1.43.0-1
- Fixed in: 1.43.0-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › nghttp2/libnghttp2-14@1.43.0-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream nghttp2 package and not the nghttp2 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.
Remediation
Upgrade Debian:11 nghttp2 to version 1.43.0-1+deb11u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-44487
- https://chaos.social/@icing/111210915918780532
- https://github.com/hyperium/hyper/issues/3337
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/2MBEPPC36UBVOZZNAXFHKLFGSLCMN5LI/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/3N4NJ7FR4X4FPZUGNTQAPSTVB2HB2Y4A/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BFQD3KUEMFBHPAPBGLWQC34L4OWL5HAZ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/CLB4TW7KALB3EEQWNWCN7OUIWWVWWCG2/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/E72T67UPDRXHIDLO3OROR25YAMN4GGW5/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FNA62Q767CFAFHBCDKYNPBMZWB7TWYVU/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HT7T2R4MQKLIF4ODV4BDLPARWFPCJ5CZ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/JIZSEFC3YKCGABA2BZW6ZJRMDZJMB7PJ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/JMEXY22BFG5Q64HQCM5CK2Q7KDKVV4TY/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/KSEGD2IWKNUO3DWY4KQGUQM5BISRWHQE/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LKYHSZQFDNR7RSA7LHVLLIAQMVYCUGBG/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LNMZJCDHGLJJLXO4OXWJMTVQRNWOC7UL/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VHUHTSXLXGXS7JYKBXTA3VINUPHTNGVU/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VSRDIV77HNKUSM7SJC5BKE5JSHLHU2NK/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WE2I52RHNNU42PX6NZ2RBUHSFFJ2LVZX/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WLPRQ5TWUQQXYWBJM7ECYDAIL2YVKIUH/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/X6QXN4ORIVF6XBW4WWFE7VNPVC74S45Y/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/XFOIBB4YFICHDM7IBOP7PWXW3FX4HLL2/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZB43REMKRQR62NJEI7I5NQ4FSXNLBKRT/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZKQSIKIAT5TJ3WSLU3RDBQ35YX4GY4V3/
- https://www.vicarius.io/vsociety/posts/rapid-reset-cve-2023-44487-dos-in-http2-understanding-the-root-cause
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZLU6U2R2IC2K64NDPNMV55AUAO65MAF4/
- http://www.openwall.com/lists/oss-security/2023/10/10/6
- http://www.openwall.com/lists/oss-security/2023/10/10/7
- https://github.com/grpc/grpc/releases/tag/v1.59.2
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/2MBEPPC36UBVOZZNAXFHKLFGSLCMN5LI/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3N4NJ7FR4X4FPZUGNTQAPSTVB2HB2Y4A/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BFQD3KUEMFBHPAPBGLWQC34L4OWL5HAZ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/CLB4TW7KALB3EEQWNWCN7OUIWWVWWCG2/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/E72T67UPDRXHIDLO3OROR25YAMN4GGW5/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/FNA62Q767CFAFHBCDKYNPBMZWB7TWYVU/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HT7T2R4MQKLIF4ODV4BDLPARWFPCJ5CZ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JIZSEFC3YKCGABA2BZW6ZJRMDZJMB7PJ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JMEXY22BFG5Q64HQCM5CK2Q7KDKVV4TY/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KSEGD2IWKNUO3DWY4KQGUQM5BISRWHQE/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LKYHSZQFDNR7RSA7LHVLLIAQMVYCUGBG/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LNMZJCDHGLJJLXO4OXWJMTVQRNWOC7UL/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VHUHTSXLXGXS7JYKBXTA3VINUPHTNGVU/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VSRDIV77HNKUSM7SJC5BKE5JSHLHU2NK/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WE2I52RHNNU42PX6NZ2RBUHSFFJ2LVZX/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WLPRQ5TWUQQXYWBJM7ECYDAIL2YVKIUH/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/X6QXN4ORIVF6XBW4WWFE7VNPVC74S45Y/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XFOIBB4YFICHDM7IBOP7PWXW3FX4HLL2/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZB43REMKRQR62NJEI7I5NQ4FSXNLBKRT/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZKQSIKIAT5TJ3WSLU3RDBQ35YX4GY4V3/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZLU6U2R2IC2K64NDPNMV55AUAO65MAF4/
- https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-http2-reset-d8Kf32vZ
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-44487
- http://www.openwall.com/lists/oss-security/2025/08/13/6
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-341067.html
- https://cert-portal.siemens.com/productcert/html/ssa-784301.html
- https://cert-portal.siemens.com/productcert/html/ssa-832273.html
- https://cert-portal.siemens.com/productcert/html/ssa-915275.html
- http://www.openwall.com/lists/oss-security/2023/10/13/4
- http://www.openwall.com/lists/oss-security/2023/10/13/9
- http://www.openwall.com/lists/oss-security/2023/10/18/4
- http://www.openwall.com/lists/oss-security/2023/10/18/8
- http://www.openwall.com/lists/oss-security/2023/10/19/6
- http://www.openwall.com/lists/oss-security/2023/10/20/8
- https://access.redhat.com/security/cve/cve-2023-44487
- https://arstechnica.com/security/2023/10/how-ddosers-used-the-http-2-protocol-to-deliver-attacks-of-unprecedented-size/
- https://aws.amazon.com/security/security-bulletins/AWS-2023-011/
- https://blog.cloudflare.com/technical-breakdown-http2-rapid-reset-ddos-attack/
- https://blog.cloudflare.com/zero-day-rapid-reset-http2-record-breaking-ddos-attack/
- https://blog.litespeedtech.com/2023/10/11/rapid-reset-http-2-vulnerablilty/
- https://blog.qualys.com/vulnerabilities-threat-research/2023/10/10/cve-2023-44487-http-2-rapid-reset-attack
- https://blog.vespa.ai/cve-2023-44487/
- https://bugzilla.proxmox.com/show_bug.cgi?id=4988
- https://bugzilla.redhat.com/show_bug.cgi?id=2242803
- https://bugzilla.suse.com/show_bug.cgi?id=1216123
- https://cgit.freebsd.org/ports/commit/?id=c64c329c2c1752f46b73e3e6ce9f4329be6629f9
- https://cloud.google.com/blog/products/identity-security/google-cloud-mitigated-largest-ddos-attack-peaking-above-398-million-rps/
- https://cloud.google.com/blog/products/identity-security/how-it-works-the-novel-http2-rapid-reset-ddos-attack
- https://community.traefik.io/t/is-traefik-vulnerable-to-cve-2023-44487/20125
- https://discuss.hashicorp.com/t/hcsec-2023-32-vault-consul-and-boundary-affected-by-http-2-rapid-reset-denial-of-service-vulnerability-cve-2023-44487/59715
- https://edg.io/lp/blog/resets-leaks-ddos-and-the-tale-of-a-hidden-cve
- https://forums.swift.org/t/swift-nio-http2-security-update-cve-2023-44487-http-2-dos/67764
- https://gist.github.com/adulau/7c2bfb8e9cdbe4b35a5e131c66a0c088
- https://github.com/Azure/AKS/issues/3947
- https://github.com/Kong/kong/discussions/11741
- https://github.com/advisories/GHSA-qppj-fm5r-hxr3
- https://github.com/advisories/GHSA-vx74-f528-fxqg
- https://github.com/advisories/GHSA-xpw8-rcwv-8f8p
- https://github.com/akka/akka-http/issues/4323
- https://github.com/alibaba/tengine/issues/1872
- https://github.com/apache/apisix/issues/10320
- https://github.com/apache/httpd-site/pull/10
- https://github.com/apache/httpd/blob/afcdbeebbff4b0c50ea26cdd16e178c0d1f24152/modules/http2/h2_mplx.c#L1101-L1113
- https://github.com/apache/tomcat/tree/main/java/org/apache/coyote/http2
- https://github.com/apache/trafficserver/pull/10564
- https://github.com/arkrwn/PoC/tree/main/CVE-2023-44487
- https://github.com/bcdannyboy/CVE-2023-44487
- https://github.com/caddyserver/caddy/issues/5877
- https://github.com/caddyserver/caddy/releases/tag/v2.7.5
- https://github.com/dotnet/announcements/issues/277
- https://github.com/dotnet/core/blob/e4613450ea0da7fd2fc6b61dfb2c1c1dec1ce9ec/release-notes/6.0/6.0.23/6.0.23.md?plain=1#L73
- https://github.com/eclipse/jetty.project/issues/10679
- https://github.com/envoyproxy/envoy/pull/30055
- https://github.com/etcd-io/etcd/issues/16740
- https://github.com/facebook/proxygen/pull/466
- https://github.com/golang/go/issues/63417
- https://github.com/grpc/grpc-go/pull/6703
- https://github.com/h2o/h2o/pull/3291
- https://github.com/h2o/h2o/security/advisories/GHSA-2m7v-gc89-fjqf
- https://github.com/haproxy/haproxy/issues/2312
- https://github.com/icing/mod_h2/blob/0a864782af0a942aa2ad4ed960a6b32cd35bcf0a/mod_http2/README.md?plain=1#L239-L244
- https://github.com/junkurihara/rust-rpxy/issues/97
- https://github.com/kazu-yamamoto/http2/commit/f61d41a502bd0f60eb24e1ce14edc7b6df6722a1
- https://github.com/kazu-yamamoto/http2/issues/93
- https://github.com/kubernetes/kubernetes/pull/121120
- https://github.com/line/armeria/pull/5232
- https://github.com/linkerd/website/pull/1695/commits/4b9c6836471bc8270ab48aae6fd2181bc73fd632
- https://github.com/micrictor/http2-rst-stream
- https://github.com/microsoft/CBL-Mariner/pull/6381
- https://github.com/netty/netty/commit/58f75f665aa81a8cbcf6ffa74820042a285c5e61
- https://github.com/nghttp2/nghttp2/pull/1961
- https://github.com/nghttp2/nghttp2/releases/tag/v1.57.0
- https://github.com/ninenines/cowboy/issues/1615
- https://github.com/nodejs/node/pull/50121
- https://github.com/openresty/openresty/issues/930
- https://github.com/opensearch-project/data-prepper/issues/3474
- https://github.com/oqtane/oqtane.framework/discussions/3367
- https://github.com/projectcontour/contour/pull/5826
- https://github.com/tempesta-tech/tempesta/issues/1986
- https://github.com/varnishcache/varnish-cache/issues/3996
- https://groups.google.com/g/golang-announce/c/iNNxDTCjZvo
- https://istio.io/latest/news/security/istio-security-2023-004/
- https://linkerd.io/2023/10/12/linkerd-cve-2023-44487/
- https://lists.apache.org/thread/5py8h42mxfsn8l1wy6o41xwhsjlsd87q
- https://lists.debian.org/debian-lts-announce/2023/10/msg00020.html
- https://lists.debian.org/debian-lts-announce/2023/10/msg00023.html
- https://lists.debian.org/debian-lts-announce/2023/10/msg00024.html
- https://lists.debian.org/debian-lts-announce/2023/10/msg00045.html
- https://lists.debian.org/debian-lts-announce/2023/10/msg00047.html
- https://lists.debian.org/debian-lts-announce/2023/11/msg00001.html
- https://lists.debian.org/debian-lts-announce/2023/11/msg00012.html
- https://lists.w3.org/Archives/Public/ietf-http-wg/2023OctDec/0025.html
- https://mailman.nginx.org/pipermail/nginx-devel/2023-October/S36Q5HBXR7CAIMPLLPRSSSYR4PCMWILK.html
- https://martinthomson.github.io/h2-stream-limits/draft-thomson-httpbis-h2-stream-limits.html
- https://msrc.microsoft.com/blog/2023/10/microsoft-response-to-distributed-denial-of-service-ddos-attacks-against-http/2/
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-44487
- https://my.f5.com/manage/s/article/K000137106
- https://netty.io/news/2023/10/10/4-1-100-Final.html
- https://news.ycombinator.com/item?id=37830987
- https://news.ycombinator.com/item?id=37830998
- https://news.ycombinator.com/item?id=37831062
- https://news.ycombinator.com/item?id=37837043
- https://openssf.org/blog/2023/10/10/http-2-rapid-reset-vulnerability-highlights-need-for-rapid-response/
- https://seanmonstar.com/post/730794151136935936/hyper-http2-rapid-reset-unaffected
- https://security.gentoo.org/glsa/202311-09
- https://security.netapp.com/advisory/ntap-20231016-0001/
- https://security.netapp.com/advisory/ntap-20240426-0007/
- https://security.netapp.com/advisory/ntap-20240621-0006/
- https://security.netapp.com/advisory/ntap-20240621-0007/
- https://security.paloaltonetworks.com/CVE-2023-44487
- https://tomcat.apache.org/security-10.html#Fixed_in_Apache_Tomcat_10.1.14
- https://ubuntu.com/security/CVE-2023-44487
- https://www.bleepingcomputer.com/news/security/new-http-2-rapid-reset-zero-day-attack-breaks-ddos-records/
- https://www.cisa.gov/news-events/alerts/2023/10/10/http2-rapid-reset-vulnerability-cve-2023-44487
- https://www.darkreading.com/cloud/internet-wide-zero-day-bug-fuels-largest-ever-ddos-event
- https://www.debian.org/security/2023/dsa-5521
- https://www.debian.org/security/2023/dsa-5522
- https://www.debian.org/security/2023/dsa-5540
- https://www.debian.org/security/2023/dsa-5549
- https://www.debian.org/security/2023/dsa-5558
- https://www.debian.org/security/2023/dsa-5570
- https://www.haproxy.com/blog/haproxy-is-not-affected-by-the-http-2-rapid-reset-attack-cve-2023-44487
- https://www.netlify.com/blog/netlify-successfully-mitigates-cve-2023-44487/
- https://www.nginx.com/blog/http-2-rapid-reset-attack-impacting-f5-nginx-products/
- https://www.openwall.com/lists/oss-security/2023/10/10/6
- https://www.phoronix.com/news/HTTP2-Rapid-Reset-Attack
- https://www.theregister.com/2023/10/10/http2_rapid_reset_zeroday/
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- https://github.com/threatlabindonesia/CVE-2023-44487-HTTP-2-Rapid-Reset-Exploit-PoC
- https://www.exploit-db.com/exploits/52426
high severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
- Fixed in: 1.1.1w-0+deb11u5
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Issue summary: Processing a 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:11 openssl to version 1.1.1w-0+deb11u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-69421
- https://github.com/openssl/openssl/commit/3524a29271f8191b8fd8a5257eb05173982a097b
- https://github.com/openssl/openssl/commit/36ecb4960872a4ce04bf6f1e1f4e78d75ec0c0c7
- https://github.com/openssl/openssl/commit/4bbc8d41a72c842ce4077a8a3eccd1109aaf74bd
- https://github.com/openssl/openssl/commit/643986985cd1c21221f941129d76fe0c2785aeb3
- https://github.com/openssl/openssl/commit/a2dbc539f0f9cc63832709fa5aa33ad9495eb19c
- https://openssl-library.org/news/secadv/20260127.txt
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
high severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
- Fixed in: 1.1.1w-0+deb11u7
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Issue summary: When a delta CRL that contains a Delta CRL Indicator extension is processed a NULL pointer dereference might happen if the required CRL Number extension is missing.
Impact summary: A NULL pointer dereference can trigger a crash which leads to a Denial of Service for an application.
When CRL processing and delta CRL processing is enabled during X.509 certificate verification, the delta CRL processing does not check whether the CRL Number extension is NULL before dereferencing it. When a malformed delta CRL file is being processed, this parameter can be NULL, causing a NULL pointer dereference.
Exploiting this issue requires the X509_V_FLAG_USE_DELTAS flag to be enabled in the verification context, the certificate being verified to contain a freshestCRL extension or the base CRL to have the EXFLAG_FRESHEST flag set, and an attacker to provide a malformed CRL to an application that processes it.
The vulnerability is limited to Denial of Service and cannot be escalated to achieve code execution or memory disclosure. For that reason the issue was assessed as Low severity according to our Security Policy.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.
Remediation
Upgrade Debian:11 openssl to version 1.1.1w-0+deb11u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-28388
- https://github.com/openssl/openssl/commit/59c3b3158553ab53275bbbccca5cb305d591cf2e
- https://github.com/openssl/openssl/commit/5a0b4930779cd2408880979db765db919da55139
- https://github.com/openssl/openssl/commit/602542f2c0c2d5edb47128f93eac10b62aeeefb3
- https://github.com/openssl/openssl/commit/a9d187dd1000130100fa7ab915f8513532cb3bb8
- https://github.com/openssl/openssl/commit/d3a901e8d9f021f3e67d6cfbc12e768129862726
- https://openssl-library.org/news/secadv/20260407.txt
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
high severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
- Fixed in: 1.1.1w-0+deb11u7
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Issue summary: During processing of a crafted CMS EnvelopedData message with KeyAgreeRecipientInfo a NULL pointer dereference can happen.
Impact summary: Applications that process attacker-controlled CMS data may crash before authentication or cryptographic operations occur resulting in Denial of Service.
When a CMS EnvelopedData message that uses KeyAgreeRecipientInfo is processed, the optional parameters field of KeyEncryptionAlgorithmIdentifier is examined without checking for its presence. This results in a NULL pointer dereference if the field is missing.
Applications and services that call CMS_decrypt() on untrusted input (e.g., S/MIME processing or CMS-based protocols) are vulnerable.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.
Remediation
Upgrade Debian:11 openssl to version 1.1.1w-0+deb11u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-28389
- https://github.com/openssl/openssl/commit/16cea4188e0ea567deb4f93f85902247e67384f5
- https://github.com/openssl/openssl/commit/785cbf7ea3b5a6f5adf0c1ccb92b79d89c35c616
- https://github.com/openssl/openssl/commit/7b5274e812400cacb6f3be4c2df5340923fa807f
- https://github.com/openssl/openssl/commit/c6725634e089eb2b634b10ede33944be7248172a
- https://github.com/openssl/openssl/commit/f80f83bc5fd036bc47d773e8b15a001e2b4ce686
- https://openssl-library.org/news/secadv/20260407.txt
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
high severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
- Fixed in: 1.1.1w-0+deb11u7
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Issue summary: During processing of a crafted CMS EnvelopedData message with KeyTransportRecipientInfo a NULL pointer dereference can happen.
Impact summary: Applications that process attacker-controlled CMS data may crash before authentication or cryptographic operations occur resulting in Denial of Service.
When a CMS EnvelopedData message that uses KeyTransportRecipientInfo with RSA-OAEP encryption is processed, the optional parameters field of RSA-OAEP SourceFunc algorithm identifier is examined without checking for its presence. This results in a NULL pointer dereference if the field is missing.
Applications and services that call CMS_decrypt() on untrusted input (e.g., S/MIME processing or CMS-based protocols) are vulnerable.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.
Remediation
Upgrade Debian:11 openssl to version 1.1.1w-0+deb11u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-28390
- https://github.com/openssl/openssl/commit/01194a8f1941115cd0383bfa91c736dd3993c8bc
- https://github.com/openssl/openssl/commit/2e39b7a6993be445fddb9fbce316fa756e0397b6
- https://github.com/openssl/openssl/commit/af2a5fecd3e71a29e7568f9c1453dec5cebbaff4
- https://github.com/openssl/openssl/commit/ea7b4ea4f9f853521ba34830cbcadc970d2e0788
- https://github.com/openssl/openssl/commit/fd2f1a6cf53b9ceeca723a001aa4b825d7c7ee75
- https://openssl-library.org/news/secadv/20260407.txt
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
high severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
- Fixed in: 1.1.1n-0+deb11u4
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload data. If the function succeeds then the "name_out", "header" and "data" arguments are populated with pointers to buffers containing the relevant decoded data. The caller is responsible for freeing those buffers. It is possible to construct a PEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex() will return a failure code but will populate the header argument with a pointer to a buffer that has already been freed. If the caller also frees this buffer then a double free will occur. This will most likely lead to a crash. This could be exploited by an attacker who has the ability to supply malicious PEM files for parsing to achieve a denial of service attack.
The functions PEM_read_bio() and PEM_read() are simple wrappers around PEM_read_bio_ex() and therefore these functions are also directly affected.
These functions are also called indirectly by a number of other OpenSSL functions including PEM_X509_INFO_read_bio_ex() and SSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL internal uses of these functions are not vulnerable because the caller does not free the header argument if PEM_read_bio_ex() returns a failure code. These locations include the PEM_read_bio_TYPE() functions as well as the decoders introduced in OpenSSL 3.0.
The OpenSSL asn1parse command line application is also impacted by this issue.
Remediation
Upgrade Debian:11 openssl to version 1.1.1n-0+deb11u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-4450
- https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2023-0003
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=63bcf189be73a9cc1264059bed6f57974be74a83
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=bbcf509bd046b34cca19c766bbddc31683d0858b
- https://security.gentoo.org/glsa/202402-08
- https://www.openssl.org/news/secadv/20230207.txt
- https://cert-portal.siemens.com/productcert/html/ssa-203374.html
- https://cert-portal.siemens.com/productcert/html/ssa-337522.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-556635.html
- https://cert-portal.siemens.com/productcert/html/ssa-561322.html
- https://cert-portal.siemens.com/productcert/html/ssa-625862.html
- https://cert-portal.siemens.com/productcert/html/ssa-699386.html
- https://cert-portal.siemens.com/productcert/html/ssa-769027.html
- https://cert-portal.siemens.com/productcert/html/ssa-794697.html
- https://cert-portal.siemens.com/productcert/html/ssa-879734.html
- https://cert-portal.siemens.com/productcert/html/ssa-943925.html
high severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
- Fixed in: 1.1.1n-0+deb11u5
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A security vulnerability has been identified in all supported versions
of OpenSSL related to the verification of X.509 certificate chains that include policy constraints. Attackers may be able to exploit this vulnerability by creating a malicious certificate chain that triggers exponential use of computational resources, leading to a denial-of-service (DoS) attack on affected systems.
Policy processing is disabled by default but can be enabled by passing
the -policy' argument to the command line utilities or by calling the X509_VERIFY_PARAM_set1_policies()' function.
Remediation
Upgrade Debian:11 openssl to version 1.1.1n-0+deb11u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-0464
- https://security.netapp.com/advisory/ntap-20230406-0006/
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=2017771e2db3e2b96f89bbe8766c3209f6a99545
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=2dcd4f1e3115f38cefa43e3efbe9b801c27e642e
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=879f7080d7e141f415c79eaa3a8ac4a3dad0348b
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=959c59c7a0164117e7f8366466a32bb1f8d77ff1
- https://lists.debian.org/debian-lts-announce/2023/06/msg00011.html
- https://security.gentoo.org/glsa/202402-08
- https://security.netapp.com/advisory/ntap-20240621-0006/
- https://www.couchbase.com/alerts/
- https://www.debian.org/security/2023/dsa-5417
- https://www.openssl.org/news/secadv/20230322.txt
- https://cert-portal.siemens.com/productcert/html/ssa-028723.html
- https://cert-portal.siemens.com/productcert/html/ssa-077170.html
- https://cert-portal.siemens.com/productcert/html/ssa-337522.html
- https://cert-portal.siemens.com/productcert/html/ssa-341067.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-556635.html
- https://cert-portal.siemens.com/productcert/html/ssa-625862.html
- https://cert-portal.siemens.com/productcert/html/ssa-769027.html
- https://cert-portal.siemens.com/productcert/html/ssa-794697.html
- https://cert-portal.siemens.com/productcert/html/ssa-879734.html
high severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
- Fixed in: 1.1.1n-0+deb11u4
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
The public API function BIO_new_NDEF is a helper function used for streaming ASN.1 data via a BIO. It is primarily used internally to OpenSSL to support the SMIME, CMS and PKCS7 streaming capabilities, but may also be called directly by end user applications.
The function receives a BIO from the caller, prepends a new BIO_f_asn1 filter BIO onto the front of it to form a BIO chain, and then returns the new head of the BIO chain to the caller. Under certain conditions, for example if a CMS recipient public key is invalid, the new filter BIO is freed and the function returns a NULL result indicating a failure. However, in this case, the BIO chain is not properly cleaned up and the BIO passed by the caller still retains internal pointers to the previously freed filter BIO. If the caller then goes on to call BIO_pop() on the BIO then a use-after-free will occur. This will most likely result in a crash.
This scenario occurs directly in the internal function B64_write_ASN1() which may cause BIO_new_NDEF() to be called and will subsequently call BIO_pop() on the BIO. This internal function is in turn called by the public API functions PEM_write_bio_ASN1_stream, PEM_write_bio_CMS_stream, PEM_write_bio_PKCS7_stream, SMIME_write_ASN1, SMIME_write_CMS and SMIME_write_PKCS7.
Other public API functions that may be impacted by this include i2d_ASN1_bio_stream, BIO_new_CMS, BIO_new_PKCS7, i2d_CMS_bio_stream and i2d_PKCS7_bio_stream.
The OpenSSL cms and smime command line applications are similarly affected.
Remediation
Upgrade Debian:11 openssl to version 1.1.1n-0+deb11u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-0215
- https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2023-0003
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=8818064ce3c3c0f1b740a5aaba2a987e75bfbafd
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=9816136fe31d92ace4037d5da5257f763aeeb4eb
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=c3829dd8825c654652201e16f8a0a0c46ee3f344
- https://security.gentoo.org/glsa/202402-08
- https://security.netapp.com/advisory/ntap-20230427-0007/
- https://security.netapp.com/advisory/ntap-20230427-0009/
- https://security.netapp.com/advisory/ntap-20240621-0006/
- https://www.openssl.org/news/secadv/20230207.txt
- https://cert-portal.siemens.com/productcert/html/ssa-203374.html
- https://cert-portal.siemens.com/productcert/html/ssa-337522.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-556635.html
- https://cert-portal.siemens.com/productcert/html/ssa-561322.html
- https://cert-portal.siemens.com/productcert/html/ssa-625862.html
- https://cert-portal.siemens.com/productcert/html/ssa-769027.html
- https://cert-portal.siemens.com/productcert/html/ssa-794697.html
- https://cert-portal.siemens.com/productcert/html/ssa-879734.html
- https://cert-portal.siemens.com/productcert/html/ssa-943925.html
high severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.32.1-4+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › perl/perl-base@5.32.1-4+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Archive::Tar versions before 3.08 for Perl extract hardlinks to attacker controlled paths outside the extraction directory.
_make_special_file() passes the tar header's linkname to link() without validating it against absolute paths or .. segments, creating a hardlink that shares the victim file's inode.
A subsequent write through the extracted name modifies the victim file, and the post-extraction chmod, chown, and utime block in _extract_file() (guarded only against symlinks via -l) applies the tar header's mode, owner, and timestamps to the shared inode during extraction alone.
Remediation
There is no fixed version for Debian:11 perl.
References
high severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.32.1-4+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › perl/perl-base@5.32.1-4+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Archive::Tar versions before 3.10 for Perl allow memory exhaustion via attacker controlled entry size field in tar header.
_read_tar() reads each entry's payload with $handle->read($$data, $block), where $block is derived from the entry's 12-byte size field in the tar header with no upper bound on that value.
A crafted header declaring a multi-gigabyte size causes Perl to allocate a scalar of that size.
Remediation
There is no fixed version for Debian:11 perl.
References
high severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@247.3-7 and systemd/libudev1@247.3-7
- Fixed in: 247.3-7+deb11u6
Detailed paths
-
Introduced through: nginx@1.21 › systemd/libsystemd0@247.3-7
-
Introduced through: nginx@1.21 › systemd/libudev1@247.3-7
NVD Description
Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of service (CPU consumption) via one or more DNSSEC responses, aka the "KeyTrap" issue. One of the concerns is that, when there is a zone with many DNSKEY and RRSIG records, the protocol specification implies that an algorithm must evaluate all combinations of DNSKEY and RRSIG records.
Remediation
Upgrade Debian:11 systemd to version 247.3-7+deb11u6 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-50387
- https://datatracker.ietf.org/doc/html/rfc4035
- https://lists.debian.org/debian-lts-announce/2024/11/msg00035.html
- https://lists.debian.org/debian-lts-announce/2024/09/msg00001.html
- http://www.openwall.com/lists/oss-security/2024/02/16/2
- http://www.openwall.com/lists/oss-security/2024/02/16/3
- https://access.redhat.com/security/cve/CVE-2023-50387
- https://bugzilla.suse.com/show_bug.cgi?id=1219823
- https://docs.powerdns.com/recursor/security-advisories/powerdns-advisory-2024-01.html
- https://gitlab.nic.cz/knot/knot-resolver/-/releases/v5.7.1
- https://kb.isc.org/docs/cve-2023-50387
- https://lists.debian.org/debian-lts-announce/2024/02/msg00006.html
- https://lists.debian.org/debian-lts-announce/2024/05/msg00011.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/6FV5O347JTX7P5OZA6NGO4MKTXRXMKOZ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BUIP7T7Z4T3UHLXFWG6XIVDP4GYPD3AI/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HVRDSJVZKMCXKKPP6PNR62T7RWZ3YSDZ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/IGSLGKUAQTW5JPPZCMF5YPEYALLRUZZ6/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PNNHZSZPG2E7NBMBNYPGHCFI4V4XRWNQ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/RGS7JN6FZXUSTC2XKQHH27574XOULYYJ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/SVYA42BLXUCIDLD35YIJPJSHDIADNYMP/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/TEXGOYGW7DBS3N2QSSQONZ4ENIRQEAPG/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/UQESRWMJCF4JEYJEAKLRM6CT55GLJAB7/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZDZFMEKQTZ4L7RY46FCENWFB5MDT263R/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BUIP7T7Z4T3UHLXFWG6XIVDP4GYPD3AI/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HVRDSJVZKMCXKKPP6PNR62T7RWZ3YSDZ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RGS7JN6FZXUSTC2XKQHH27574XOULYYJ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZDZFMEKQTZ4L7RY46FCENWFB5MDT263R/
- https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2024q1/017430.html
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-50387
- https://news.ycombinator.com/item?id=39367411
- https://news.ycombinator.com/item?id=39372384
- https://nlnetlabs.nl/news/2024/Feb/13/unbound-1.19.1-released/
- https://security.netapp.com/advisory/ntap-20240307-0007/
- https://www.athene-center.de/aktuelles/key-trap
- https://www.athene-center.de/fileadmin/content/PDF/Technical_Report_KeyTrap.pdf
- https://www.isc.org/blogs/2024-bind-security-release/
- https://www.securityweek.com/keytrap-dns-attack-could-disable-large-parts-of-internet-researchers/
- https://www.theregister.com/2024/02/13/dnssec_vulnerability_internet/
- https://github.com/knqyf263/CVE-2023-50387
high severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@247.3-7 and systemd/libudev1@247.3-7
- Fixed in: 247.3-7+deb11u6
Detailed paths
-
Introduced through: nginx@1.21 › systemd/libsystemd0@247.3-7
-
Introduced through: nginx@1.21 › systemd/libudev1@247.3-7
NVD Description
Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
The Closest Encloser Proof aspect of the DNS protocol (in RFC 5155 when RFC 9276 guidance is skipped) allows remote attackers to cause a denial of service (CPU consumption for SHA-1 computations) via DNSSEC responses in a random subdomain attack, aka the "NSEC3" issue. The RFC 5155 specification implies that an algorithm must perform thousands of iterations of a hash function in certain situations.
Remediation
Upgrade Debian:11 systemd to version 247.3-7+deb11u6 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-50868
- http://www.openwall.com/lists/oss-security/2024/02/16/2
- http://www.openwall.com/lists/oss-security/2024/02/16/3
- https://access.redhat.com/security/cve/CVE-2023-50868
- https://bugzilla.suse.com/show_bug.cgi?id=1219826
- https://datatracker.ietf.org/doc/html/rfc5155
- https://docs.powerdns.com/recursor/security-advisories/powerdns-advisory-2024-01.html
- https://gitlab.nic.cz/knot/knot-resolver/-/releases/v5.7.1
- https://kb.isc.org/docs/cve-2023-50868
- https://lists.debian.org/debian-lts-announce/2024/02/msg00006.html
- https://lists.debian.org/debian-lts-announce/2024/05/msg00011.html
- https://lists.debian.org/debian-lts-announce/2024/09/msg00001.html
- https://lists.debian.org/debian-lts-announce/2024/11/msg00035.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/6FV5O347JTX7P5OZA6NGO4MKTXRXMKOZ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BUIP7T7Z4T3UHLXFWG6XIVDP4GYPD3AI/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HVRDSJVZKMCXKKPP6PNR62T7RWZ3YSDZ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/IGSLGKUAQTW5JPPZCMF5YPEYALLRUZZ6/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PNNHZSZPG2E7NBMBNYPGHCFI4V4XRWNQ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/RGS7JN6FZXUSTC2XKQHH27574XOULYYJ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/SVYA42BLXUCIDLD35YIJPJSHDIADNYMP/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/TEXGOYGW7DBS3N2QSSQONZ4ENIRQEAPG/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/UQESRWMJCF4JEYJEAKLRM6CT55GLJAB7/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZDZFMEKQTZ4L7RY46FCENWFB5MDT263R/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BUIP7T7Z4T3UHLXFWG6XIVDP4GYPD3AI/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HVRDSJVZKMCXKKPP6PNR62T7RWZ3YSDZ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZDZFMEKQTZ4L7RY46FCENWFB5MDT263R/
- https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2024q1/017430.html
- https://nlnetlabs.nl/news/2024/Feb/13/unbound-1.19.1-released/
- https://security.netapp.com/advisory/ntap-20240307-0008/
- https://www.isc.org/blogs/2024-bind-security-release/
high severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u6
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A null pointer dereference flaw was found in Libtiff via tif_dirinfo.c. This issue may allow an attacker to trigger memory allocation failures through certain means, such as restricting the heap space size or injecting faults, causing a segmentation fault. This can cause an application crash, eventually leading to a denial of service.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u6 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-7006
- https://access.redhat.com/security/cve/CVE-2024-7006
- https://bugzilla.redhat.com/show_bug.cgi?id=2302996
- https://access.redhat.com/errata/RHSA-2024:6360
- https://access.redhat.com/errata/RHSA-2024:8833
- https://access.redhat.com/errata/RHSA-2024:8914
- https://security.netapp.com/advisory/ntap-20240920-0001/
- https://lists.debian.org/debian-lts-announce/2025/01/msg00019.html
high severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u6
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A segment fault (SEGV) flaw was found in libtiff that could be triggered by passing a crafted tiff file to the TIFFReadRGBATileExt() API. This flaw allows a remote attacker to cause a heap-buffer overflow, leading to a denial of service.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u6 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-52356
- https://access.redhat.com/errata/RHSA-2024:5079
- http://seclists.org/fulldisclosure/2024/Jul/16
- http://seclists.org/fulldisclosure/2024/Jul/17
- http://seclists.org/fulldisclosure/2024/Jul/18
- http://seclists.org/fulldisclosure/2024/Jul/19
- http://seclists.org/fulldisclosure/2024/Jul/20
- http://seclists.org/fulldisclosure/2024/Jul/21
- http://seclists.org/fulldisclosure/2024/Jul/22
- http://seclists.org/fulldisclosure/2024/Jul/23
- https://lists.debian.org/debian-lts-announce/2024/03/msg00011.html
- https://support.apple.com/kb/HT214116
- https://support.apple.com/kb/HT214117
- https://support.apple.com/kb/HT214118
- https://support.apple.com/kb/HT214119
- https://support.apple.com/kb/HT214120
- https://support.apple.com/kb/HT214122
- https://support.apple.com/kb/HT214123
- https://support.apple.com/kb/HT214124
- https://lists.debian.org/debian-lts-announce/2025/01/msg00019.html
- https://access.redhat.com/errata/RHSA-2025:20801
- https://access.redhat.com/errata/RHSA-2025:21994
- https://access.redhat.com/errata/RHSA-2025:23078
- https://access.redhat.com/errata/RHSA-2025:23079
- https://access.redhat.com/errata/RHSA-2025:23080
- https://access.redhat.com/errata/RHSA-2026:3461
- https://access.redhat.com/errata/RHSA-2026:3462
- https://access.redhat.com/errata/RHSA-2026:5958
- https://access.redhat.com/errata/RHSA-2026:7081
- https://access.redhat.com/errata/RHSA-2026:7304
- https://access.redhat.com/errata/RHSA-2026:7335
- https://access.redhat.com/errata/RHSA-2026:8747
- https://access.redhat.com/errata/RHSA-2026:8746
- https://access.redhat.com/errata/RHSA-2026:8748
- https://access.redhat.com/errata/RHSA-2026:16174
- https://access.redhat.com/errata/RHSA-2026:25096
- https://access.redhat.com/security/cve/CVE-2023-52356
- https://bugzilla.redhat.com/show_bug.cgi?id=2251344
- https://gitlab.com/libtiff/libtiff/-/issues/622
- https://gitlab.com/libtiff/libtiff/-/merge_requests/546
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.1-5
- Fixed in: 3.7.1-5+deb11u10
Detailed paths
-
Introduced through: nginx@1.21 › gnutls28/libgnutls30@3.7.1-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw was found in gnutls. This vulnerability occurs because permitted name constraints were incorrectly ignored when previous Certificate Authorities (CAs) only had excluded name constraints. A remote attacker could exploit this to bypass critical name constraint checks during certificate validation. This bypass could lead to the acceptance of invalid certificates, potentially enabling spoofing or man-in-the-middle attacks against affected systems.
Remediation
Upgrade Debian:11 gnutls28 to version 3.7.1-5+deb11u10 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-42011
- https://access.redhat.com/security/cve/CVE-2026-42011
- https://bugzilla.redhat.com/show_bug.cgi?id=2467437
- https://access.redhat.com/errata/RHSA-2026:13274
- https://access.redhat.com/errata/RHSA-2026:20611
- https://access.redhat.com/errata/RHSA-2026:20613
- https://access.redhat.com/errata/RHSA-2026:20612
- https://access.redhat.com/errata/RHSA-2026:26319
- https://access.redhat.com/errata/RHSA-2026:26409
- https://access.redhat.com/errata/RHSA-2026:29197
- https://access.redhat.com/errata/RHSA-2026:30004
- https://access.redhat.com/errata/RHSA-2026:30849
- https://access.redhat.com/errata/RHSA-2026:30850
- https://access.redhat.com/errata/RHSA-2026:32962
- https://access.redhat.com/errata/RHSA-2026:33125
- https://access.redhat.com/errata/RHSA-2026:40762
- https://access.redhat.com/errata/RHSA-2026:41921
- https://access.redhat.com/errata/RHSA-2026:43575
- https://www.gnutls.org/security-new.html#GNUTLS-SA-2026-04-29-6
- https://access.redhat.com/errata/RHSA-2026:58981
- https://access.redhat.com/errata/RHSA-2026:57483
- https://access.redhat.com/errata/RHSA-2026:56853
- https://access.redhat.com/errata/RHSA-2026:59831
- https://access.redhat.com/errata/RHSA-2026:60019
- https://access.redhat.com/errata/RHSA-2026:72502
- https://access.redhat.com/errata/RHSA-2026:74674
- https://access.redhat.com/errata/RHSA-2026:82304
- https://access.redhat.com/errata/RHSA-2026:82322
- https://access.redhat.com/errata/RHSA-2026:82347
- https://access.redhat.com/errata/RHSA-2026:82354
- https://access.redhat.com/errata/RHSA-2026:82372
- https://access.redhat.com/errata/RHSA-2026:82857
- https://access.redhat.com/errata/RHSA-2026:82888
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.1-5
- Fixed in: 3.7.1-5+deb11u10
Detailed paths
-
Introduced through: nginx@1.21 › gnutls28/libgnutls30@3.7.1-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw was found in gnutls. This vulnerability occurs because gnutls performs case-sensitive comparisons of nameConstraints labels, specifically for dNSName (DNS) or rfc822Name (email) constraints within excludedSubtrees or permittedSubtrees. A remote attacker can exploit this by crafting a leaf certificate with casing differences in the Subject Alternative Name (SAN), leading to a policy bypass where a certificate that should be rejected is instead accepted. This could result in unauthorized access or information disclosure.
Remediation
Upgrade Debian:11 gnutls28 to version 3.7.1-5+deb11u10 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-3833
- https://access.redhat.com/errata/RHSA-2026:13274
- https://access.redhat.com/security/cve/CVE-2026-3833
- https://bugzilla.redhat.com/show_bug.cgi?id=2445763
- https://access.redhat.com/errata/RHSA-2026:20611
- https://access.redhat.com/errata/RHSA-2026:20613
- https://access.redhat.com/errata/RHSA-2026:20612
- https://access.redhat.com/errata/RHSA-2026:26319
- https://access.redhat.com/errata/RHSA-2026:26409
- https://access.redhat.com/errata/RHSA-2026:29197
- https://access.redhat.com/errata/RHSA-2026:30004
- https://access.redhat.com/errata/RHSA-2026:30849
- https://access.redhat.com/errata/RHSA-2026:30850
- https://access.redhat.com/errata/RHSA-2026:32962
- https://access.redhat.com/errata/RHSA-2026:33125
- https://access.redhat.com/errata/RHSA-2026:41921
- https://access.redhat.com/errata/RHSA-2026:43575
- https://access.redhat.com/errata/RHSA-2026:58981
- https://access.redhat.com/errata/RHSA-2026:57402
- https://access.redhat.com/errata/RHSA-2026:59831
- https://access.redhat.com/errata/RHSA-2026:60019
- https://access.redhat.com/errata/RHSA-2026:62549
- https://access.redhat.com/errata/RHSA-2026:62409
- https://access.redhat.com/errata/RHSA-2026:65851
- https://access.redhat.com/errata/RHSA-2026:65839
- https://access.redhat.com/errata/RHSA-2026:67857
- https://access.redhat.com/errata/RHSA-2026:72502
- https://access.redhat.com/errata/RHSA-2026:74674
- https://access.redhat.com/errata/RHSA-2026:82304
- https://access.redhat.com/errata/RHSA-2026:82322
- https://access.redhat.com/errata/RHSA-2026:82347
- https://access.redhat.com/errata/RHSA-2026:82354
- https://access.redhat.com/errata/RHSA-2026:82372
- https://access.redhat.com/errata/RHSA-2026:82857
- https://access.redhat.com/errata/RHSA-2026:82888
- https://gitlab.com/gnutls/gnutls/-/issues/1803
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.1-5
- Fixed in: 3.7.1-5+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › gnutls28/libgnutls30@3.7.1-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A timing side-channel in the handling of RSA ClientKeyExchange messages was discovered in GnuTLS. This side-channel can be sufficient to recover the key encrypted in the RSA ciphertext across a network in a Bleichenbacher style attack. To achieve a successful decryption the attacker would need to send a large amount of specially crafted messages to the vulnerable server. By recovering the secret from the ClientKeyExchange message, the attacker would be able to decrypt the application data exchanged over that connection.
Remediation
Upgrade Debian:11 gnutls28 to version 3.7.1-5+deb11u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-0361
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UFIA3X4IZ3CW7SRQ2UHNHNPMRIAWF2FI/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WS4KVDOG6QTALWHC2QE4Y7VPDRMLTRWQ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/Z634YBXAJ5VLDI62IOPBVP5K6YFHAWCY/
- https://access.redhat.com/security/cve/CVE-2023-0361
- https://github.com/tlsfuzzer/tlsfuzzer/pull/679
- https://gitlab.com/gnutls/gnutls/-/issues/1050
- https://lists.debian.org/debian-lts-announce/2023/02/msg00015.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/UFIA3X4IZ3CW7SRQ2UHNHNPMRIAWF2FI/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WS4KVDOG6QTALWHC2QE4Y7VPDRMLTRWQ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/Z634YBXAJ5VLDI62IOPBVP5K6YFHAWCY/
- https://security.netapp.com/advisory/ntap-20230324-0005/
- https://security.netapp.com/advisory/ntap-20230725-0005/
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-806742.html
high severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
- Fixed in: 1.1.1n-0+deb11u4
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING.
When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network.
Remediation
Upgrade Debian:11 openssl to version 1.1.1n-0+deb11u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-0286
- https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2023-0003
- https://ftp.openbsd.org/pub/OpenBSD/LibreSSL/libressl-3.6.2-relnotes.txt
- https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/018_x509.patch.sig
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=2c6c9d439b484e1ba9830d8454a34fa4f80fdfe9
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=2f7530077e0ef79d98718138716bc51ca0cad658
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=fd2af07dc083a350c959147097003a14a5e8ac4d
- https://security.gentoo.org/glsa/202402-08
- https://www.openssl.org/news/secadv/20230207.txt
- https://cert-portal.siemens.com/productcert/html/ssa-028723.html
- https://cert-portal.siemens.com/productcert/html/ssa-203374.html
- https://cert-portal.siemens.com/productcert/html/ssa-264815.html
- https://cert-portal.siemens.com/productcert/html/ssa-337522.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-455250.html
- https://cert-portal.siemens.com/productcert/html/ssa-556635.html
- https://cert-portal.siemens.com/productcert/html/ssa-561322.html
- https://cert-portal.siemens.com/productcert/html/ssa-625862.html
- https://cert-portal.siemens.com/productcert/html/ssa-769027.html
- https://cert-portal.siemens.com/productcert/html/ssa-794697.html
- https://cert-portal.siemens.com/productcert/html/ssa-879734.html
- https://cert-portal.siemens.com/productcert/html/ssa-943925.html
high severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
- Fixed in: 1.1.1n-0+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
In addition to the c_rehash shell command injection identified in CVE-2022-1292, further circumstances where the c_rehash script does not properly sanitise shell metacharacters to prevent command injection were found by code review. When the CVE-2022-1292 was fixed it was not discovered that there are other places in the script where the file names of certificates being hashed were possibly passed to a command executed through the shell. This script is distributed by some operating systems in a manner where it is automatically executed. On such operating systems, an attacker could execute arbitrary commands with the privileges of the script. Use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool. Fixed in OpenSSL 3.0.4 (Affected 3.0.0,3.0.1,3.0.2,3.0.3). Fixed in OpenSSL 1.1.1p (Affected 1.1.1-1.1.1o). Fixed in OpenSSL 1.0.2zf (Affected 1.0.2-1.0.2ze).
Remediation
Upgrade Debian:11 openssl to version 1.1.1n-0+deb11u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-2068
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=2c9c35870601b4a44d86ddbf512b38df38285cfa
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=7a9c027159fe9e1bbc2cd38a8a2914bff0d5abd9
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=9639817dac8bbbaa64d09efad7464ccc405527c7
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/6WZZBKUHQFGSKGNXXKICSRPL7AMVW5M5/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VCMNWKERPBKOEBNL7CLTTX3ZZCZLH7XA/
- https://gitlab.com/fraf0/cve-2022-1292-re_score-analysis
- http://seclists.org/fulldisclosure/2024/Nov/0
- https://cert-portal.siemens.com/productcert/pdf/ssa-332410.pdf
- https://git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=2c9c35870601b4a44d86ddbf512b38df38285cfa
- https://git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=7a9c027159fe9e1bbc2cd38a8a2914bff0d5abd9
- https://git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=9639817dac8bbbaa64d09efad7464ccc405527c7
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/6WZZBKUHQFGSKGNXXKICSRPL7AMVW5M5/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VCMNWKERPBKOEBNL7CLTTX3ZZCZLH7XA/
- https://security.netapp.com/advisory/ntap-20220707-0008/
- https://www.debian.org/security/2022/dsa-5169
- https://www.openssl.org/news/secadv/20220621.txt
- https://cert-portal.siemens.com/productcert/html/ssa-146325.html
- https://cert-portal.siemens.com/productcert/html/ssa-332410.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-794697.html
high severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw was found in libtiff. A remote attacker could exploit this vulnerability by providing a specially crafted PixarLog-compressed TIFF image. This issue occurs when decoding Pixarlog codec images with the PIXARLOGDATAFMT_8BITABGR output format and a specific stride value, leading to a heap-based buffer overflow. This could potentially result in arbitrary code execution or a denial of service (DoS).
Remediation
There is no fixed version for Debian:11 tiff.
References
- https://security-tracker.debian.org/tracker/CVE-2026-12912
- https://gitlab.com/libtiff/libtiff/-/merge_requests/873
- https://gitlab.com/libtiff/libtiff/-/work_items/824
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-12912.json
- https://access.redhat.com/errata/RHSA-2026:69292
- https://access.redhat.com/errata/RHSA-2026:73909
- https://access.redhat.com/errata/RHSA-2026:73959
- https://access.redhat.com/errata/RHSA-2026:73960
- https://access.redhat.com/errata/RHSA-2026:73961
- https://access.redhat.com/errata/RHSA-2026:73962
- https://access.redhat.com/errata/RHSA-2026:74458
- https://access.redhat.com/errata/RHSA-2026:74459
- https://access.redhat.com/errata/RHSA-2026:74460
- https://access.redhat.com/errata/RHSA-2026:74461
- https://access.redhat.com/errata/RHSA-2026:74462
- https://access.redhat.com/errata/RHSA-2026:74463
- https://access.redhat.com/errata/RHSA-2026:74674
- https://access.redhat.com/errata/RHSA-2026:83550
- https://access.redhat.com/errata/RHSA-2026:34890
- https://access.redhat.com/errata/RHSA-2026:41892
- https://access.redhat.com/errata/RHSA-2026:42668
- https://access.redhat.com/errata/RHSA-2026:47183
- https://access.redhat.com/errata/RHSA-2026:47184
- https://access.redhat.com/errata/RHSA-2026:49671
- https://access.redhat.com/errata/RHSA-2026:50774
- https://access.redhat.com/errata/RHSA-2026:54638
- https://access.redhat.com/errata/RHSA-2026:54640
- https://access.redhat.com/errata/RHSA-2026:54642
- https://access.redhat.com/errata/RHSA-2026:58545
- https://access.redhat.com/errata/RHSA-2026:58553
- https://access.redhat.com/errata/RHSA-2026:58554
- https://access.redhat.com/errata/RHSA-2026:58556
- https://access.redhat.com/errata/RHSA-2026:61657
- https://access.redhat.com/security/cve/CVE-2026-12912
- https://bugzilla.redhat.com/show_bug.cgi?id=2492871
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.1-5
- Fixed in: 3.7.1-5+deb11u10
Detailed paths
-
Introduced through: nginx@1.21 › gnutls28/libgnutls30@3.7.1-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw was found in gnutls. A remote attacker could exploit this vulnerability by presenting a specially crafted certificate that contains Uniform Resource Identifier (URI) or Service (SRV) Subject Alternative Names (SANs). This could cause the certificate validation process to incorrectly fall back to checking DNS hostnames against the Common Name (CN), potentially allowing the attacker to spoof legitimate services or intercept sensitive information.
Remediation
Upgrade Debian:11 gnutls28 to version 3.7.1-5+deb11u10 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-42012
- https://access.redhat.com/security/cve/CVE-2026-42012
- https://bugzilla.redhat.com/show_bug.cgi?id=2467441
- https://access.redhat.com/errata/RHSA-2026:20611
- https://access.redhat.com/errata/RHSA-2026:20613
- https://access.redhat.com/errata/RHSA-2026:20612
- https://access.redhat.com/errata/RHSA-2026:13274
- https://access.redhat.com/errata/RHSA-2026:26319
- https://access.redhat.com/errata/RHSA-2026:26409
- https://access.redhat.com/errata/RHSA-2026:29197
- https://access.redhat.com/errata/RHSA-2026:30004
- https://access.redhat.com/errata/RHSA-2026:30849
- https://access.redhat.com/errata/RHSA-2026:30850
- https://access.redhat.com/errata/RHSA-2026:32962
- https://access.redhat.com/errata/RHSA-2026:33125
- https://access.redhat.com/errata/RHSA-2026:41921
- https://access.redhat.com/errata/RHSA-2026:43575
- https://www.gnutls.org/security-new.html#GNUTLS-SA-2026-04-29-7
- https://access.redhat.com/errata/RHSA-2026:58981
- https://access.redhat.com/errata/RHSA-2026:72502
- https://access.redhat.com/errata/RHSA-2026:74674
- https://access.redhat.com/errata/RHSA-2026:82304
- https://access.redhat.com/errata/RHSA-2026:82322
- https://access.redhat.com/errata/RHSA-2026:82347
- https://access.redhat.com/errata/RHSA-2026:82354
- https://access.redhat.com/errata/RHSA-2026:82372
- https://access.redhat.com/errata/RHSA-2026:82857
- https://access.redhat.com/errata/RHSA-2026:82888
high severity
- Vulnerable module: libpng1.6/libpng16-16
- Introduced through: libpng1.6/libpng16-16@1.6.37-3
- Fixed in: 1.6.37-3+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › libpng1.6/libpng16-16@1.6.37-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From 1.6.51 to 1.6.53, there is a heap buffer over-read in the libpng simplified API function png_image_finish_read when processing interlaced 16-bit PNGs with 8-bit output format and non-minimal row stride. This is a regression introduced by the fix for CVE-2025-65018. This vulnerability is fixed in 1.6.54.
Remediation
Upgrade Debian:11 libpng1.6 to version 1.6.37-3+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-22695
- https://github.com/pnggroup/libpng/commit/218612ddd6b17944e21eda56caf8b4bf7779d1ea
- https://github.com/pnggroup/libpng/commit/e4f7ad4ea2
- https://github.com/pnggroup/libpng/issues/778
- https://github.com/pnggroup/libpng/security/advisories/GHSA-mmq5-27w3-rxpp
high severity
- Vulnerable module: ncurses/libtinfo6
- Introduced through: ncurses/libtinfo6@6.2+20201114-2, ncurses/ncurses-base@6.2+20201114-2 and others
- Fixed in: 6.2+20201114-2+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › ncurses/libtinfo6@6.2+20201114-2
-
Introduced through: nginx@1.21 › ncurses/ncurses-base@6.2+20201114-2
-
Introduced through: nginx@1.21 › ncurses/ncurses-bin@6.2+20201114-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
ncurses 6.3 before patch 20220416 has an out-of-bounds read and segmentation violation in convert_strings in tinfo/read_entry.c in the terminfo library.
Remediation
Upgrade Debian:11 ncurses to version 6.2+20201114-2+deb11u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-29458
- http://seclists.org/fulldisclosure/2022/Oct/28
- http://seclists.org/fulldisclosure/2022/Oct/41
- https://lists.debian.org/debian-lts-announce/2022/10/msg00037.html
- https://lists.gnu.org/archive/html/bug-ncurses/2022-04/msg00014.html
- https://lists.gnu.org/archive/html/bug-ncurses/2022-04/msg00016.html
- https://support.apple.com/kb/HT213488
high severity
- Vulnerable module: gnupg2/gpgv
- Introduced through: gnupg2/gpgv@2.2.27-2+deb11u1
- Fixed in: 2.2.27-2+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › gnupg2/gpgv@2.2.27-2+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnupg2 package and not the gnupg2 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
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:11 gnupg2 to version 2.2.27-2+deb11u3 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/libicu67
- Introduced through: icu/libicu67@67.1-7
- Fixed in: 67.1-7+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › icu/libicu67@67.1-7
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:11 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:11 icu to version 67.1-7+deb11u1 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
- https://unicode-org.atlassian.net/jira/software/c/projects/ICU/issues/ICU-22957
- https://access.redhat.com/errata/RHSA-2026:54581
- https://cert-portal.siemens.com/productcert/html/ssa-585531.html
- https://access.redhat.com/errata/RHSA-2026:54544
- https://access.redhat.com/errata/RHSA-2026:54553
- https://access.redhat.com/errata/RHSA-2026:56786
- https://access.redhat.com/errata/RHSA-2026:56853
- https://access.redhat.com/errata/RHSA-2026:56911
- https://access.redhat.com/errata/RHSA-2026:60019
- https://access.redhat.com/errata/RHSA-2026:65839
high severity
- Vulnerable module: libssh2/libssh2-1
- Introduced through: libssh2/libssh2-1@1.9.0-2
Detailed paths
-
Introduced through: nginx@1.21 › libssh2/libssh2-1@1.9.0-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libssh2 package and not the libssh2 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libssh2 through 1.11.1 reads an attacker-controlled 32-bit attribute count from a publickey-subsystem response and uses it in the allocation num_attrs * sizeof(libssh2_publickey_attribute) without bounds checking, so on 32-bit platforms the multiplication overflows to an undersized buffer. A malicious SSH server can then drive the attribute-parsing loop to write past the allocation, causing a heap buffer overflow in a connecting libssh2 client.
Remediation
There is no fixed version for Debian:11 libssh2.
References
- https://security-tracker.debian.org/tracker/CVE-2026-58050
- https://github.com/bikini/exploitarium/tree/main/libssh2-publickey-list-calc-poc
- https://github.com/libssh2/libssh2/blob/master/src/publickey.c
- https://www.vulncheck.com/advisories/libssh2-integer-overflow-in-publickey-subsystem-attribute-allocation
medium severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@247.3-7 and systemd/libudev1@247.3-7
- Fixed in: 247.3-7+deb11u8
Detailed paths
-
Introduced through: nginx@1.21 › systemd/libsystemd0@247.3-7
-
Introduced through: nginx@1.21 › systemd/libudev1@247.3-7
NVD Description
Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw was found in systemd. The systemd-machined service contains an Improper Access Control vulnerability due to insufficient validation of the class parameter in the RegisterMachine D-Bus (Desktop Bus) method. A local unprivileged user can exploit this by attempting to register a machine with a specific class value, which may leave behind a usable, attacker-controlled machine object. This allows the attacker to invoke methods on the privileged object, leading to the execution of arbitrary commands with root privileges on the host system.
Remediation
Upgrade Debian:11 systemd to version 247.3-7+deb11u8 or higher.
References
medium severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.1-5
- Fixed in: 3.7.1-5+deb11u10
Detailed paths
-
Introduced through: nginx@1.21 › gnutls28/libgnutls30@3.7.1-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw was found in GnuTLS. The gnutls_pkcs11_token_set_pin function, used for changing the Security Officer PIN, can lead to a use-after-free vulnerability. This occurs when an attacker attempts to change the PIN with a NULL old PIN for a token that lacks a protected authentication path.
Remediation
Upgrade Debian:11 gnutls28 to version 3.7.1-5+deb11u10 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-42014
- https://access.redhat.com/errata/RHSA-2026:20611
- https://access.redhat.com/errata/RHSA-2026:20612
- https://access.redhat.com/errata/RHSA-2026:20613
- https://access.redhat.com/security/cve/CVE-2026-42014
- https://bugzilla.redhat.com/show_bug.cgi?id=2467451
- https://gitlab.com/gnutls/gnutls/-/issues/1766
- https://www.gnutls.org/security-new.html#GNUTLS-SA-2026-04-29-9
- https://access.redhat.com/errata/RHSA-2026:13274
- https://access.redhat.com/errata/RHSA-2026:26319
- https://access.redhat.com/errata/RHSA-2026:26409
- https://access.redhat.com/errata/RHSA-2026:29197
- https://access.redhat.com/errata/RHSA-2026:30004
- https://access.redhat.com/errata/RHSA-2026:30849
- https://access.redhat.com/errata/RHSA-2026:30850
- https://access.redhat.com/errata/RHSA-2026:32962
- https://access.redhat.com/errata/RHSA-2026:33125
- https://access.redhat.com/errata/RHSA-2026:41921
- https://access.redhat.com/errata/RHSA-2026:43575
- https://access.redhat.com/errata/RHSA-2026:58981
- https://access.redhat.com/errata/RHSA-2026:72502
- https://access.redhat.com/errata/RHSA-2026:74674
- https://access.redhat.com/errata/RHSA-2026:82304
- https://access.redhat.com/errata/RHSA-2026:82322
- https://access.redhat.com/errata/RHSA-2026:82347
- https://access.redhat.com/errata/RHSA-2026:82354
- https://access.redhat.com/errata/RHSA-2026:82372
- https://access.redhat.com/errata/RHSA-2026:82857
- https://access.redhat.com/errata/RHSA-2026:82888
medium severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
- Fixed in: 7.74.0-1.3+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
curl < 7.84.0 supports "chained" HTTP compression algorithms, meaning that a serverresponse can be compressed multiple times and potentially with different algorithms. The number of acceptable "links" in this "decompression chain" was unbounded, allowing a malicious server to insert a virtually unlimited number of compression steps.The use of such a decompression chain could result in a "malloc bomb", makingcurl end up spending enormous amounts of allocated heap memory, or trying toand returning out of memory errors.
Remediation
Upgrade Debian:11 curl to version 7.74.0-1.3+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-32206
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BEV6BR4MTI3CEWK2YU2HQZUW5FAS3FEY/
- http://seclists.org/fulldisclosure/2022/Oct/28
- http://seclists.org/fulldisclosure/2022/Oct/41
- http://www.openwall.com/lists/oss-security/2023/02/15/3
- https://cert-portal.siemens.com/productcert/pdf/ssa-333517.pdf
- https://hackerone.com/reports/1570651
- https://lists.debian.org/debian-lts-announce/2022/08/msg00017.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BEV6BR4MTI3CEWK2YU2HQZUW5FAS3FEY/
- https://security.gentoo.org/glsa/202212-01
- https://security.netapp.com/advisory/ntap-20220915-0003/
- https://support.apple.com/kb/HT213488
- https://www.debian.org/security/2022/dsa-5197
- https://cert-portal.siemens.com/productcert/html/ssa-333517.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-419740.html
- https://cert-portal.siemens.com/productcert/html/ssa-558014.html
- https://cert-portal.siemens.com/productcert/html/ssa-942865.html
medium severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
- Fixed in: 7.74.0-1.3+deb11u7
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
An allocation of resources without limits or throttling vulnerability exists in curl <v7.88.0 based on the "chained" HTTP compression algorithms, meaning that a server response can be compressed multiple times and potentially with differentalgorithms. The number of acceptable "links" in this "decompression chain" wascapped, but the cap was implemented on a per-header basis allowing a maliciousserver to insert a virtually unlimited number of compression steps simply byusing many headers. The use of such a decompression chain could result in a "malloc bomb", making curl end up spending enormous amounts of allocated heap memory, or trying to and returning out of memory errors.
Remediation
Upgrade Debian:11 curl to version 7.74.0-1.3+deb11u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-23916
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BQKE6TXYDHOTFHLTBZ5X73GTKI7II5KO/
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://hackerone.com/reports/1826048
- https://lists.debian.org/debian-lts-announce/2023/02/msg00035.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BQKE6TXYDHOTFHLTBZ5X73GTKI7II5KO/
- https://security.gentoo.org/glsa/202310-12
- https://security.netapp.com/advisory/ntap-20230309-0006/
- https://www.debian.org/security/2023/dsa-5365
medium severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A cleartext transmission of sensitive information vulnerability exists in curl <v7.88.0 that could cause HSTS functionality to behave incorrectly when multiple URLs are requested in parallel. Using its HSTS support, curl can be instructed to use HTTPS instead of using an insecure clear-text HTTP step even when HTTP is provided in the URL. This HSTS mechanism would however surprisingly fail when multiple transfers are done in parallel as the HSTS cache file gets overwritten by the most recentlycompleted transfer. A later HTTP-only transfer to the earlier host name would then not get upgraded properly to HSTS.
Remediation
There is no fixed version for Debian:11 curl.
References
medium severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
- Fixed in: 7.74.0-1.3+deb11u11
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
This flaw allows a malicious HTTP server to set "super cookies" in curl that are then passed back to more origins than what is otherwise allowed or possible. This allows a site to set cookies that then would get sent to different and unrelated sites and domains.
It could do this by exploiting a mixed case flaw in curl's function that
verifies a given cookie domain against the Public Suffix List (PSL). For
example a cookie could be set with domain=co.UK when the URL used a lower
case hostname curl.co.uk, even though co.uk is listed as a PSL domain.
Remediation
Upgrade Debian:11 curl to version 7.74.0-1.3+deb11u11 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-46218
- https://curl.se/docs/CVE-2023-46218.html
- https://hackerone.com/reports/2212193
- https://lists.debian.org/debian-lts-announce/2023/12/msg00015.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3ZX3VW67N4ACRAPMV2QS2LVYGD7H2MVE/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UOGXU25FMMT2X6UUITQ7EZZYMJ42YWWD/
- https://security.netapp.com/advisory/ntap-20240125-0007/
- https://www.debian.org/security/2023/dsa-5587
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-093430.html
- https://cert-portal.siemens.com/productcert/html/ssa-202008.html
- https://cert-portal.siemens.com/productcert/html/ssa-331112.html
medium severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
When curl is asked to use HSTS, the expiry time for a subdomain might overwrite a parent domain's cache entry, making it end sooner or later than otherwise intended.
This affects curl using applications that enable HSTS and use URLs with the
insecure HTTP:// scheme and perform transfers with hosts like
x.example.com as well as example.com where the first host is a subdomain
of the second host.
(The HSTS cache either needs to have been populated manually or there needs to have been previous HTTPS accesses done as the cache needs to have entries for the domains involved to trigger this problem.)
When x.example.com responds with Strict-Transport-Security: headers, this
bug can make the subdomain's expiry timeout bleed over and get set for the
parent domain example.com in curl's HSTS cache.
The result of a triggered bug is that HTTP accesses to example.com get
converted to HTTPS for a different period of time than what was asked for by
the origin server. If example.com for example stops supporting HTTPS at its
expiry time, curl might then fail to access http://example.com until the
(wrongly set) timeout expires. This bug can also expire the parent's entry
earlier, thus making curl inadvertently switch back to insecure HTTP earlier
than otherwise intended.
Remediation
There is no fixed version for Debian:11 curl.
References
- https://security-tracker.debian.org/tracker/CVE-2024-9681
- https://curl.se/docs/CVE-2024-9681.html
- https://curl.se/docs/CVE-2024-9681.json
- https://hackerone.com/reports/2764830
- http://www.openwall.com/lists/oss-security/2024/11/06/2
- https://security.netapp.com/advisory/ntap-20241213-0006/
- http://seclists.org/fulldisclosure/2025/Apr/13
- http://seclists.org/fulldisclosure/2025/Apr/10
- http://seclists.org/fulldisclosure/2025/Apr/11
- http://seclists.org/fulldisclosure/2025/Apr/12
- http://seclists.org/fulldisclosure/2025/Apr/4
- http://seclists.org/fulldisclosure/2025/Apr/5
- http://seclists.org/fulldisclosure/2025/Apr/8
- http://seclists.org/fulldisclosure/2025/Apr/9
medium severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
- Fixed in: 7.74.0-1.3+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A insufficiently protected credentials vulnerability in fixed in curl 7.83.0 might leak authentication or cookie header data on HTTP redirects to the same host but another port number.
Remediation
Upgrade Debian:11 curl to version 7.74.0-1.3+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-27776
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/7N5ZBWLNNPZKFK7Q4KEHGCJ2YELQEUJP/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DKKOQXPYLMBSEVDHFS32BPBR3ZQJKY5B/
- https://hackerone.com/reports/1547048
- https://lists.debian.org/debian-lts-announce/2022/08/msg00017.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/7N5ZBWLNNPZKFK7Q4KEHGCJ2YELQEUJP/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/DKKOQXPYLMBSEVDHFS32BPBR3ZQJKY5B/
- https://security.gentoo.org/glsa/202212-01
- https://security.netapp.com/advisory/ntap-20220609-0008/
- https://www.debian.org/security/2022/dsa-5197
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
medium severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
- Fixed in: 7.74.0-1.3+deb11u13
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libcurl's ASN1 parser code has the GTime2str() function, used for parsing an
ASN.1 Generalized Time field. If given an syntactically incorrect field, the
parser might end up using -1 for the length of the time fraction, leading to
a strlen() getting performed on a pointer to a heap buffer area that is not
(purposely) null terminated.
This flaw most likely leads to a crash, but can also lead to heap contents getting returned to the application when CURLINFO_CERTINFO is used.
Remediation
Upgrade Debian:11 curl to version 7.74.0-1.3+deb11u13 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-7264
- https://curl.se/docs/CVE-2024-7264.html
- https://curl.se/docs/CVE-2024-7264.json
- https://hackerone.com/reports/2629968
- https://github.com/curl/curl/commit/27959ecce75cdb2809c0bdb3286e60e08fadb519
- https://security.netapp.com/advisory/ntap-20240828-0008/
- https://security.netapp.com/advisory/ntap-20241025-0006/
- https://security.netapp.com/advisory/ntap-20241025-0010/
- http://www.openwall.com/lists/oss-security/2024/07/31/1
- https://cert-portal.siemens.com/productcert/html/ssa-089022.html
- https://cert-portal.siemens.com/productcert/html/ssa-355557.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
medium severity
- Vulnerable module: gnupg2/gpgv
- Introduced through: gnupg2/gpgv@2.2.27-2+deb11u1
- Fixed in: 2.2.27-2+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › gnupg2/gpgv@2.2.27-2+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnupg2 package and not the gnupg2 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
GnuPG through 2.3.6, in unusual situations where an attacker possesses any secret-key information from a victim's keyring and other constraints (e.g., use of GPGME) are met, allows signature forgery via injection into the status line.
Remediation
Upgrade Debian:11 gnupg2 to version 2.2.27-2+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-34903
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/FRLWJQ76A4UKHI3Q36BKSJKS4LFLQO33/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NPTAR76EIZY7NQFENSOZO7U473257OVZ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VN63GBTMRWO36Y7BKA2WQHROAKCXKCBL/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VU64FUVG2PRZBSHFOQRSP7KDVEIZ23OS/
- http://www.openwall.com/lists/oss-security/2022/07/02/1
- https://bugs.debian.org/1014157
- https://dev.gnupg.org/T6027
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FRLWJQ76A4UKHI3Q36BKSJKS4LFLQO33/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/NPTAR76EIZY7NQFENSOZO7U473257OVZ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VN63GBTMRWO36Y7BKA2WQHROAKCXKCBL/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VU64FUVG2PRZBSHFOQRSP7KDVEIZ23OS/
- https://security.netapp.com/advisory/ntap-20220826-0005/
- https://www.debian.org/security/2022/dsa-5174
- https://www.openwall.com/lists/oss-security/2022/06/30/1
medium severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.1-5
- Fixed in: 3.7.1-5+deb11u8
Detailed paths
-
Introduced through: nginx@1.21 › gnutls28/libgnutls30@3.7.1-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A NULL pointer dereference flaw was found in the GnuTLS software in _gnutls_figure_common_ciphersuite().
Remediation
Upgrade Debian:11 gnutls28 to version 3.7.1-5+deb11u8 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-6395
- https://access.redhat.com/security/cve/CVE-2025-6395
- https://bugzilla.redhat.com/show_bug.cgi?id=2376755
- https://access.redhat.com/errata/RHSA-2025:16115
- https://access.redhat.com/errata/RHSA-2025:16116
- https://access.redhat.com/errata/RHSA-2025:17348
- https://access.redhat.com/errata/RHSA-2025:17361
- https://access.redhat.com/errata/RHSA-2025:17415
- https://access.redhat.com/errata/RHSA-2025:19088
- https://lists.debian.org/debian-lts-announce/2025/08/msg00005.html
- http://www.openwall.com/lists/oss-security/2025/07/11/3
- https://access.redhat.com/errata/RHSA-2025:17181
- https://access.redhat.com/errata/RHSA-2025:22529
- https://gitlab.com/gnutls/gnutls/-/issues/1718
- https://lists.gnupg.org/pipermail/gnutls-help/2025-July/004883.html
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
medium severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.1-5
- Fixed in: 3.7.1-5+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › gnutls28/libgnutls30@3.7.1-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A NULL pointer dereference flaw was found in GnuTLS. As Nettle's hash update functions internally call memcpy, providing zero-length input may cause undefined behavior. This flaw leads to a denial of service after authentication in rare circumstances.
Remediation
Upgrade Debian:11 gnutls28 to version 3.7.1-5+deb11u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2021-4209
- https://access.redhat.com/security/cve/CVE-2021-4209
- https://bugzilla.redhat.com/show_bug.cgi?id=2044156
- https://gitlab.com/gnutls/gnutls/-/commit/3db352734472d851318944db13be73da61300568
- https://gitlab.com/gnutls/gnutls/-/issues/1306
- https://gitlab.com/gnutls/gnutls/-/merge_requests/1503
- https://security.netapp.com/advisory/ntap-20220915-0005/
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
medium severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.18.3-6+deb11u1, krb5/libk5crypto3@1.18.3-6+deb11u1 and others
- Fixed in: 1.18.3-6+deb11u4
Detailed paths
-
Introduced through: nginx@1.21 › krb5/libgssapi-krb5-2@1.18.3-6+deb11u1
-
Introduced through: nginx@1.21 › krb5/libk5crypto3@1.18.3-6+deb11u1
-
Introduced through: nginx@1.21 › krb5/libkrb5-3@1.18.3-6+deb11u1
-
Introduced through: nginx@1.21 › krb5/libkrb5support0@1.18.3-6+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
lib/kadm5/kadm_rpc_xdr.c in MIT Kerberos 5 (aka krb5) before 1.20.2 and 1.21.x before 1.21.1 frees an uninitialized pointer. A remote authenticated user can trigger a kadmind crash. This occurs because _xdr_kadm5_principal_ent_rec does not validate the relationship between n_key_data and the key_data array count.
Remediation
Upgrade Debian:11 krb5 to version 1.18.3-6+deb11u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-36054
- https://github.com/krb5/krb5/commit/ef08b09c9459551aabbe7924fb176f1583053cdd
- https://github.com/krb5/krb5/compare/krb5-1.20.1-final...krb5-1.20.2-final
- https://github.com/krb5/krb5/compare/krb5-1.21-final...krb5-1.21.1-final
- https://lists.debian.org/debian-lts-announce/2023/10/msg00031.html
- https://security.netapp.com/advisory/ntap-20230908-0004/
- https://web.mit.edu/kerberos/www/advisories/
medium severity
- Vulnerable module: libgd2/libgd3
- Introduced through: libgd2/libgd3@2.3.0-2
- Fixed in: 2.3.0-2+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › libgd2/libgd3@2.3.0-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libgd2 package and not the libgd2 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
read_header_tga in gd_tga.c in the GD Graphics Library (aka LibGD) through 2.3.2 allows remote attackers to cause a denial of service (out-of-bounds read) via a crafted TGA file.
Remediation
Upgrade Debian:11 libgd2 to version 2.3.0-2+deb11u1 or higher.
References
medium severity
- Vulnerable module: libgd2/libgd3
- Introduced through: libgd2/libgd3@2.3.0-2
- Fixed in: 2.3.0-2+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › libgd2/libgd3@2.3.0-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libgd2 package and not the libgd2 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
The GD Graphics Library (aka LibGD) through 2.3.2 has an out-of-bounds read because of the lack of certain gdGetBuf and gdPutBuf return value checks.
Remediation
Upgrade Debian:11 libgd2 to version 2.3.0-2+deb11u1 or higher.
References
medium severity
- Vulnerable module: libssh2/libssh2-1
- Introduced through: libssh2/libssh2-1@1.9.0-2
Detailed paths
-
Introduced through: nginx@1.21 › libssh2/libssh2-1@1.9.0-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libssh2 package and not the libssh2 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libssh2 through 1.11.1, fixed in commit 2dae302, contains an out-of-bounds heap read vulnerability in the sftp_symlink() function in src/sftp.c that allows a malicious SSH server or man-in-the-middle attacker to disclose heap memory contents or cause a crash by sending a crafted SSH_FXP_NAME response. Attackers can supply a link_len value larger than the actual packet data in SSH_FXP_NAME responses for SFTP READLINK and REALPATH operations, triggering a heap buffer over-read of up to target_len minus one bytes due to the missing validation of available packet buffer size before the memcpy operation.
Remediation
There is no fixed version for Debian:11 libssh2.
References
- https://security-tracker.debian.org/tracker/CVE-2025-15661
- https://github.com/libssh2/libssh2/commit/2dae3024897e1898d389835151f4e9606227721d
- https://github.com/libssh2/libssh2/pull/1705
- https://github.com/libssh2/libssh2/pull/1717
- https://www.vulncheck.com/advisories/libssh2-heap-buffer-over-read-via-sftp-symlink-in-sftp-c
medium severity
- Vulnerable module: libssh2/libssh2-1
- Introduced through: libssh2/libssh2-1@1.9.0-2
Detailed paths
-
Introduced through: nginx@1.21 › libssh2/libssh2-1@1.9.0-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libssh2 package and not the libssh2 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libssh2 through 1.11.1 grows its publickey list with SSH2_REALLOC but does not zero-initialize new entries before parsing populates them, so a parse failure reaching the cleanup path leaves libssh2_publickey_list_free operating on an uninitialized entry. A malicious SSH server offering the publickey subsystem can use a malformed response to make cleanup free an uninitialized, attacker-influenceable attrs pointer in a connecting libssh2 client.
Remediation
There is no fixed version for Debian:11 libssh2.
References
- https://security-tracker.debian.org/tracker/CVE-2026-58051
- https://github.com/bikini/exploitarium/tree/main/libssh2-publickey-list-calc-poc
- https://github.com/libssh2/libssh2/blob/master/src/publickey.c
- https://www.vulncheck.com/advisories/libssh2-free-of-uninitialized-pointer-in-publickey-list-cleanup
medium severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.10+dfsg-6.7+deb11u2
- Fixed in: 2.9.10+dfsg-6.7+deb11u4
Detailed paths
-
Introduced through: nginx@1.21 › libxml2@2.9.10+dfsg-6.7+deb11u2
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:11 relevant fixed versions and status.
An issue was discovered in libxml2 before 2.10.4. When hashing empty dict strings in a crafted XML document, xmlDictComputeFastKey in dict.c can produce non-deterministic values, leading to various logic and memory errors, such as a double free. This behavior occurs because there is an attempt to use the first byte of an empty string, and any value is possible (not solely the '\0' value).
Remediation
Upgrade Debian:11 libxml2 to version 2.9.10+dfsg-6.7+deb11u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-29469
- https://gitlab.gnome.org/GNOME/libxml2/-/issues/510
- https://gitlab.gnome.org/GNOME/libxml2/-/releases/v2.10.4
- https://lists.debian.org/debian-lts-announce/2023/04/msg00031.html
- https://security.netapp.com/advisory/ntap-20230601-0006/
- https://cert-portal.siemens.com/productcert/html/ssa-341067.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-556635.html
- https://cert-portal.siemens.com/productcert/html/ssa-625862.html
- https://cert-portal.siemens.com/productcert/html/ssa-769027.html
medium severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.10+dfsg-6.7+deb11u2
- Fixed in: 2.9.10+dfsg-6.7+deb11u4
Detailed paths
-
Introduced through: nginx@1.21 › libxml2@2.9.10+dfsg-6.7+deb11u2
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:11 relevant fixed versions and status.
In libxml2 before 2.10.4, parsing of certain invalid XSD schemas can lead to a NULL pointer dereference and subsequently a segfault. This occurs in xmlSchemaFixupComplexType in xmlschemas.c.
Remediation
Upgrade Debian:11 libxml2 to version 2.9.10+dfsg-6.7+deb11u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-28484
- https://gitlab.gnome.org/GNOME/libxml2/-/issues/491
- https://gitlab.gnome.org/GNOME/libxml2/-/releases/v2.10.4
- https://lists.debian.org/debian-lts-announce/2023/04/msg00031.html
- https://security.netapp.com/advisory/ntap-20230601-0006/
- https://security.netapp.com/advisory/ntap-20240201-0005/
- https://cert-portal.siemens.com/productcert/html/ssa-341067.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-556635.html
- https://cert-portal.siemens.com/productcert/html/ssa-625862.html
- https://cert-portal.siemens.com/productcert/html/ssa-769027.html
medium severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.10+dfsg-6.7+deb11u2
- Fixed in: 2.9.10+dfsg-6.7+deb11u6
Detailed paths
-
Introduced through: nginx@1.21 › libxml2@2.9.10+dfsg-6.7+deb11u2
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:11 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:11 libxml2 to version 2.9.10+dfsg-6.7+deb11u6 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-39615
- https://lists.debian.org/debian-lts-announce/2025/02/msg00028.html
- https://gitlab.gnome.org/GNOME/libxml2/-/issues/535
- https://cert-portal.siemens.com/productcert/html/ssa-341067.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-556635.html
- https://cert-portal.siemens.com/productcert/html/ssa-784301.html
medium severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.10+dfsg-6.7+deb11u2
- Fixed in: 2.9.10+dfsg-6.7+deb11u6
Detailed paths
-
Introduced through: nginx@1.21 › libxml2@2.9.10+dfsg-6.7+deb11u2
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:11 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:11 libxml2 to version 2.9.10+dfsg-6.7+deb11u6 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-45322
- https://lists.debian.org/debian-lts-announce/2025/02/msg00028.html
- http://www.openwall.com/lists/oss-security/2023/10/06/5
- https://gitlab.gnome.org/GNOME/libxml2/-/issues/344
- https://gitlab.gnome.org/GNOME/libxml2/-/issues/583
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
medium severity
- Vulnerable module: libxslt/libxslt1.1
- Introduced through: libxslt/libxslt1.1@1.1.34-4
- Fixed in: 1.1.34-4+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › libxslt/libxslt1.1@1.1.34-4
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:11 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:11 libxslt to version 1.1.34-4+deb11u3 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: nginx
- Introduced through: nginx@1.21.6-1~bullseye
Detailed paths
-
Introduced through: nginx@1.21 › nginx@1.21.6-1~bullseye
NVD Description
Note: Versions mentioned in the description apply only to the upstream nginx package and not the nginx package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
NGINX Plus and NGINX Open Source have a vulnerability in the ngx_http_ssi_module module. This vulnerability may exist when the Server-Side Includes (SSI), proxy_pass, and proxy_buffering off directives are configured. With this configuration, an unauthenticated attacker with man-in-the-middle (MITM) ability to control responses from an upstream server may be able to cause a use-after-free in the NGINX worker process. This issue may lead to limited modification of memory or a restart of the NGINX worker process.
Impact: This vulnerability may allow remote attackers to have limited control to modify memory contents or restart the NGINX worker process. There is no control plane exposure; this is a data plane issue only.
Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
Remediation
There is no fixed version for Debian:11 nginx.
References
medium severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
- Fixed in: 1.1.1n-0+deb11u5
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Issue summary: Processing some specially crafted ASN.1 object identifiers or data containing them may be very slow.
Impact summary: Applications that use OBJ_obj2txt() directly, or use any of the OpenSSL subsystems OCSP, PKCS7/SMIME, CMS, CMP/CRMF or TS with no message size limit may experience notable to very long delays when processing those messages, which may lead to a Denial of Service.
An OBJECT IDENTIFIER is composed of a series of numbers - sub-identifiers - most of which have no size limit. OBJ_obj2txt() may be used to translate an ASN.1 OBJECT IDENTIFIER given in DER encoding form (using the OpenSSL type ASN1_OBJECT) to its canonical numeric text form, which are the sub-identifiers of the OBJECT IDENTIFIER in decimal form, separated by periods.
When one of the sub-identifiers in the OBJECT IDENTIFIER is very large (these are sizes that are seen as absurdly large, taking up tens or hundreds of KiBs), the translation to a decimal number in text may take a very long time. The time complexity is O(n^2) with 'n' being the size of the sub-identifiers in bytes (*).
With OpenSSL 3.0, support to fetch cryptographic algorithms using names / identifiers in string form was introduced. This includes using OBJECT IDENTIFIERs in canonical numeric text form as identifiers for fetching algorithms.
Such OBJECT IDENTIFIERs may be received through the ASN.1 structure AlgorithmIdentifier, which is commonly used in multiple protocols to specify what cryptographic algorithm should be used to sign or verify, encrypt or decrypt, or digest passed data.
Applications that call OBJ_obj2txt() directly with untrusted data are affected, with any version of OpenSSL. If the use is for the mere purpose of display, the severity is considered low.
In OpenSSL 3.0 and newer, this affects the subsystems OCSP, PKCS7/SMIME, CMS, CMP/CRMF or TS. It also impacts anything that processes X.509 certificates, including simple things like verifying its signature.
The impact on TLS is relatively low, because all versions of OpenSSL have a 100KiB limit on the peer's certificate chain. Additionally, this only impacts clients, or servers that have explicitly enabled client authentication.
In OpenSSL 1.1.1 and 1.0.2, this only affects displaying diverse objects, such as X.509 certificates. This is assumed to not happen in such a way that it would cause a Denial of Service, so these versions are considered not affected by this issue in such a way that it would be cause for concern, and the severity is therefore considered low.
Remediation
Upgrade Debian:11 openssl to version 1.1.1n-0+deb11u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-2650
- http://www.openwall.com/lists/oss-security/2023/05/30/1
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=423a2bc737a908ad0c77bda470b2b59dc879936b
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=853c5e56ee0b8650c73140816bb8b91d6163422c
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=9e209944b35cf82368071f160a744b6178f9b098
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=db779b0e10b047f2585615e0b8f2acdf21f8544a
- https://lists.debian.org/debian-lts-announce/2023/06/msg00011.html
- https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2023-0009
- https://security.gentoo.org/glsa/202402-08
- https://security.netapp.com/advisory/ntap-20230703-0001/
- https://security.netapp.com/advisory/ntap-20231027-0009/
- https://www.debian.org/security/2023/dsa-5417
- https://www.openssl.org/news/secadv/20230530.txt
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-699386.html
- https://cert-portal.siemens.com/productcert/html/ssa-943925.html
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u6
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw was found in libtiff. A specially crafted tiff file can lead to a segmentation fault due to a buffer overflow in the Fax3Encode function in libtiff/tif_fax3.c, resulting in a denial of service.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u6 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-3618
- https://access.redhat.com/security/cve/CVE-2023-3618
- https://bugzilla.redhat.com/show_bug.cgi?id=2215865
- https://lists.debian.org/debian-lts-announce/2023/07/msg00034.html
- https://lists.debian.org/debian-lts-announce/2025/01/msg00019.html
- https://security.netapp.com/advisory/ntap-20230824-0012/
- https://support.apple.com/kb/HT214036
- https://support.apple.com/kb/HT214037
- https://support.apple.com/kb/HT214038
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Divide By Zero error in tiffcrop in libtiff 4.4.0 allows attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit f3a5e010.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-2056
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4TSS7MJ7OO7JO5BNKCRYSFU7UAYOKLA2/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OXUMJXVEAYFWRO3U3YHKSULHIVDOLEQS/
- https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-2056.json
- https://gitlab.com/libtiff/libtiff/-/issues/415
- https://gitlab.com/libtiff/libtiff/-/merge_requests/346
- https://lists.debian.org/debian-lts-announce/2023/01/msg00018.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4TSS7MJ7OO7JO5BNKCRYSFU7UAYOKLA2/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/OXUMJXVEAYFWRO3U3YHKSULHIVDOLEQS/
- https://security.netapp.com/advisory/ntap-20220826-0001/
- https://www.debian.org/security/2023/dsa-5333
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Divide By Zero error in tiffcrop in libtiff 4.4.0 allows attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit f3a5e010.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-2057
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4TSS7MJ7OO7JO5BNKCRYSFU7UAYOKLA2/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OXUMJXVEAYFWRO3U3YHKSULHIVDOLEQS/
- https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-2057.json
- https://gitlab.com/libtiff/libtiff/-/issues/427
- https://gitlab.com/libtiff/libtiff/-/merge_requests/346
- https://lists.debian.org/debian-lts-announce/2023/01/msg00018.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4TSS7MJ7OO7JO5BNKCRYSFU7UAYOKLA2/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/OXUMJXVEAYFWRO3U3YHKSULHIVDOLEQS/
- https://security.netapp.com/advisory/ntap-20220826-0001/
- https://www.debian.org/security/2023/dsa-5333
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Divide By Zero error in tiffcrop in libtiff 4.4.0 allows attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit f3a5e010.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-2058
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4TSS7MJ7OO7JO5BNKCRYSFU7UAYOKLA2/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OXUMJXVEAYFWRO3U3YHKSULHIVDOLEQS/
- https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-2058.json
- https://gitlab.com/libtiff/libtiff/-/issues/428
- https://gitlab.com/libtiff/libtiff/-/merge_requests/346
- https://lists.debian.org/debian-lts-announce/2023/01/msg00018.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4TSS7MJ7OO7JO5BNKCRYSFU7UAYOKLA2/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/OXUMJXVEAYFWRO3U3YHKSULHIVDOLEQS/
- https://security.netapp.com/advisory/ntap-20220826-0001/
- https://www.debian.org/security/2023/dsa-5333
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
There is a double free or corruption in rotateImage() at tiffcrop.c:8839 found in libtiff 4.4.0rc1
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-2519
- https://access.redhat.com/errata/RHSA-2023:0095
- https://access.redhat.com/errata/RHSA-2023:0302
- https://access.redhat.com/security/cve/CVE-2022-2519
- https://bugzilla.redhat.com/show_bug.cgi?id=2122789
- https://gitlab.com/libtiff/libtiff/-/issues/423
- https://gitlab.com/libtiff/libtiff/-/merge_requests/378
- https://www.debian.org/security/2023/dsa-5333
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw was found in libtiff 4.4.0rc1. There is a sysmalloc assertion fail in rotateImage() at tiffcrop.c:8621 that can cause program crash when reading a crafted input.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-2520
- https://access.redhat.com/errata/RHSA-2023:0095
- https://access.redhat.com/errata/RHSA-2023:0302
- https://access.redhat.com/security/cve/CVE-2022-2520
- https://bugzilla.redhat.com/show_bug.cgi?id=2122792
- https://gitlab.com/libtiff/libtiff/-/issues/424
- https://gitlab.com/libtiff/libtiff/-/merge_requests/378
- https://www.debian.org/security/2023/dsa-5333
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u5
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
LibTIFF is vulnerable to an integer overflow. This flaw allows remote attackers to cause a denial of service (application crash) or possibly execute an arbitrary code via a crafted tiff image, which triggers a heap-based buffer overflow.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u5 or higher.
References
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u5
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A vulnerability was found in libtiff due to multiple potential integer overflows in raw2tiff.c. This flaw allows remote attackers to cause a denial of service or possibly execute an arbitrary code via a crafted tiff image, which triggers a heap-based buffer overflow.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u5 or higher.
References
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u6
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A NULL pointer dereference in TIFFClose() is caused by a failure to open an output file (non-existent path or a path that requires permissions like /dev/null) while specifying zones.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u6 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-3316
- https://gitlab.com/libtiff/libtiff/-/issues/515
- https://gitlab.com/libtiff/libtiff/-/merge_requests/468
- https://lists.debian.org/debian-lts-announce/2023/07/msg00034.html
- https://lists.debian.org/debian-lts-announce/2025/01/msg00019.html
- https://research.jfrog.com/vulnerabilities/libtiff-nullderef-dos-xray-522144/
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
LibTIFF 4.4.0 has an out-of-bounds read in writeSingleSection in tools/tiffcrop.c:7345, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit e8131125.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-3599
- https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-3599.json
- https://gitlab.com/libtiff/libtiff/-/commit/e813112545942107551433d61afd16ac094ff246
- https://gitlab.com/libtiff/libtiff/-/issues/398
- https://lists.debian.org/debian-lts-announce/2023/01/msg00018.html
- https://security.netapp.com/advisory/ntap-20230110-0001/
- https://www.debian.org/security/2023/dsa-5333
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A stack overflow was discovered in the _TIFFVGetField function of Tiffsplit v4.4.0. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted TIFF file parsed by the "tiffsplit" or "tiffcrop" utilities.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-34526
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/FC6LWPAEKYJ57LSHX4SBFMLRMLOZTHIJ/
- https://gitlab.com/libtiff/libtiff/-/issues/433
- https://gitlab.com/libtiff/libtiff/-/issues/486
- https://lists.debian.org/debian-lts-announce/2023/01/msg00018.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FC6LWPAEKYJ57LSHX4SBFMLRMLOZTHIJ/
- https://security.netapp.com/advisory/ntap-20220930-0002/
- https://www.debian.org/security/2023/dsa-5333
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
LibTIFF 4.4.0 has an out-of-bounds write in _TIFFmemset in libtiff/tif_unix.c:340 when called from processCropSelections, tools/tiffcrop.c:7619, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit 236b7191.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-3626
- https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-3626.json
- https://gitlab.com/libtiff/libtiff/-/commit/236b7191f04c60d09ee836ae13b50f812c841047
- https://gitlab.com/libtiff/libtiff/-/issues/426
- https://lists.debian.org/debian-lts-announce/2023/01/msg00018.html
- https://security.netapp.com/advisory/ntap-20230110-0001/
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
LibTIFF 4.4.0 has an out-of-bounds write in _TIFFmemcpy in libtiff/tif_unix.c:346 when called from extractImageSection, tools/tiffcrop.c:6826, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit 236b7191.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-3597
- https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-3597.json
- https://gitlab.com/libtiff/libtiff/-/commit/236b7191f04c60d09ee836ae13b50f812c841047
- https://gitlab.com/libtiff/libtiff/-/issues/413
- https://lists.debian.org/debian-lts-announce/2023/01/msg00018.html
- https://security.netapp.com/advisory/ntap-20230110-0001/
- https://www.debian.org/security/2023/dsa-5333
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
LibTIFF 4.4.0 has an out-of-bounds write in _TIFFmemcpy in libtiff/tif_unix.c:346 when called from extractImageSection, tools/tiffcrop.c:6860, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit 236b7191.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-3627
- https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-3627.json
- https://gitlab.com/libtiff/libtiff/-/commit/236b7191f04c60d09ee836ae13b50f812c841047
- https://gitlab.com/libtiff/libtiff/-/issues/411
- https://lists.debian.org/debian-lts-announce/2023/01/msg00018.html
- https://security.netapp.com/advisory/ntap-20230110-0001/
- https://www.debian.org/security/2023/dsa-5333
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
LibTIFF 4.4.0 has an out-of-bounds write in extractContigSamplesShifted24bits in tools/tiffcrop.c:3604, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit cfbb883b.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-3598
- https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-3598.json
- https://gitlab.com/libtiff/libtiff/-/commit/cfbb883bf6ea7bedcb04177cc4e52d304522fdff
- https://gitlab.com/libtiff/libtiff/-/issues/435
- https://lists.debian.org/debian-lts-announce/2023/01/msg00018.html
- https://security.netapp.com/advisory/ntap-20230110-0001/
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
It was found in libtiff 4.4.0rc1 that there is an invalid pointer free operation in TIFFClose() at tif_close.c:131 called by tiffcrop.c:2522 that can cause a program crash and denial of service while processing crafted input.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-2521
- https://access.redhat.com/errata/RHSA-2023:0095
- https://access.redhat.com/errata/RHSA-2023:0302
- https://access.redhat.com/security/cve/CVE-2022-2521
- https://bugzilla.redhat.com/show_bug.cgi?id=2122799
- https://gitlab.com/libtiff/libtiff/-/issues/422
- https://gitlab.com/libtiff/libtiff/-/merge_requests/378
- https://www.debian.org/security/2023/dsa-5333
medium severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.10+dfsg-6.7+deb11u2
- Fixed in: 2.9.10+dfsg-6.7+deb11u10
Detailed paths
-
Introduced through: nginx@1.21 › libxml2@2.9.10+dfsg-6.7+deb11u2
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:11 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
Upgrade Debian:11 libxml2 to version 2.9.10+dfsg-6.7+deb11u10 or higher.
References
medium severity
- Vulnerable module: p11-kit/libp11-kit0
- Introduced through: p11-kit/libp11-kit0@0.23.22-1
Detailed paths
-
Introduced through: nginx@1.21 › p11-kit/libp11-kit0@0.23.22-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream p11-kit package and not the p11-kit package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw was found in p11-kit. A local attacker, or one with equivalent access to a reachable RPC channel, could exploit an integer overflow vulnerability. By sending specially crafted messages, the attacker can cause the system to miscalculate memory allocation for nested attributes. This leads to a memory corruption issue, specifically a heap out-of-bounds write, which can crash the p11-kit RPC parsing process, resulting in a Denial of Service (DoS). This vulnerability is only exploitable on 32 bit systems.
Remediation
There is no fixed version for Debian:11 p11-kit.
References
medium severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.10+dfsg-6.7+deb11u2
- Fixed in: 2.9.10+dfsg-6.7+deb11u5
Detailed paths
-
Introduced through: nginx@1.21 › libxml2@2.9.10+dfsg-6.7+deb11u2
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:11 relevant fixed versions and status.
Possible cross-site scripting vulnerability in libxml after commit 960f0e2.
Remediation
Upgrade Debian:11 libxml2 to version 2.9.10+dfsg-6.7+deb11u5 or higher.
References
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A stack buffer overflow flaw was found in Libtiffs' tiffcp.c in main() function. This flaw allows an attacker to pass a crafted TIFF file to the tiffcp tool, triggering a stack buffer overflow issue, possibly corrupting the memory, and causing a crash that leads to a denial of service.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-1355
- https://access.redhat.com/errata/RHSA-2022:7585
- https://access.redhat.com/errata/RHSA-2022:8194
- https://access.redhat.com/security/cve/CVE-2022-1355
- https://bugzilla.redhat.com/show_bug.cgi?id=2074415
- https://gitlab.com/libtiff/libtiff/-/issues/400
- https://gitlab.com/libtiff/libtiff/-/merge_requests/323
- https://lists.debian.org/debian-lts-announce/2023/01/msg00018.html
- https://security.gentoo.org/glsa/202210-10
- https://security.netapp.com/advisory/ntap-20221014-0007/
- https://www.debian.org/security/2023/dsa-5333
medium severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
- Fixed in: 7.74.0-1.3+deb11u8
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
An authentication bypass vulnerability exists in libcurl <8.0.0 in the FTP connection reuse feature that can result in wrong credentials being used during subsequent transfers. Previously created connections are kept in a connection pool for reuse if they match the current setup. However, certain FTP settings such as CURLOPT_FTP_ACCOUNT, CURLOPT_FTP_ALTERNATIVE_TO_USER, CURLOPT_FTP_SSL_CCC, and CURLOPT_USE_SSL were not included in the configuration match checks, causing them to match too easily. This could lead to libcurl using the wrong credentials when performing a transfer, potentially allowing unauthorized access to sensitive information.
Remediation
Upgrade Debian:11 curl to version 7.74.0-1.3+deb11u8 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-27535
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/36NBD5YLJXXEDZLDGNFCERWRYJQ6LAQW/
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-806742.html
- https://cert-portal.siemens.com/productcert/html/ssa-943925.html
- https://hackerone.com/reports/1892780
- https://lists.debian.org/debian-lts-announce/2023/04/msg00025.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/36NBD5YLJXXEDZLDGNFCERWRYJQ6LAQW/
- https://security.gentoo.org/glsa/202310-12
- https://security.netapp.com/advisory/ntap-20230420-0010/
medium severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
- Fixed in: 7.74.0-1.3+deb11u8
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
An authentication bypass vulnerability exists libcurl <8.0.0 in the connection reuse feature which can reuse previously established connections with incorrect user permissions due to a failure to check for changes in the CURLOPT_GSSAPI_DELEGATION option. This vulnerability affects krb5/kerberos/negotiate/GSSAPI transfers and could potentially result in unauthorized access to sensitive information. The safest option is to not reuse connections if the CURLOPT_GSSAPI_DELEGATION option has been changed.
Remediation
Upgrade Debian:11 curl to version 7.74.0-1.3+deb11u8 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-27536
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/36NBD5YLJXXEDZLDGNFCERWRYJQ6LAQW/
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-806742.html
- https://cert-portal.siemens.com/productcert/html/ssa-943925.html
- https://hackerone.com/reports/1895135
- https://lists.debian.org/debian-lts-announce/2023/04/msg00025.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/36NBD5YLJXXEDZLDGNFCERWRYJQ6LAQW/
- https://security.gentoo.org/glsa/202310-12
- https://security.netapp.com/advisory/ntap-20230420-0010/
medium severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
- Fixed in: 7.74.0-1.3+deb11u9
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
An improper certificate validation vulnerability exists in curl <v8.1.0 in the way it supports matching of wildcard patterns when listed as "Subject Alternative Name" in TLS server certificates. curl can be built to use its own name matching function for TLS rather than one provided by a TLS library. This private wildcard matching function would match IDN (International Domain Name) hosts incorrectly and could as a result accept patterns that otherwise should mismatch. IDN hostnames are converted to puny code before used for certificate checks. Puny coded names always start with xn-- and should not be allowed to pattern match, but the wildcard check in curl could still check for x*, which would match even though the IDN name most likely contained nothing even resembling an x.
Remediation
Upgrade Debian:11 curl to version 7.74.0-1.3+deb11u9 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-28321
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/F4I75RDGX5ULSSCBE5BF3P5I5SFO7ULQ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/Z2LIWHWKOVH24COGGBCVOWDXXIUPKOMK/
- http://seclists.org/fulldisclosure/2023/Jul/47
- http://seclists.org/fulldisclosure/2023/Jul/48
- http://seclists.org/fulldisclosure/2023/Jul/52
- https://hackerone.com/reports/1950627
- https://lists.debian.org/debian-lts-announce/2023/10/msg00016.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/F4I75RDGX5ULSSCBE5BF3P5I5SFO7ULQ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/Z2LIWHWKOVH24COGGBCVOWDXXIUPKOMK/
- https://security.gentoo.org/glsa/202310-12
- https://security.netapp.com/advisory/ntap-20230609-0009/
- https://support.apple.com/kb/HT213843
- https://support.apple.com/kb/HT213844
- https://support.apple.com/kb/HT213845
medium severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
- Fixed in: 7.74.0-1.3+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
When curl >= 7.20.0 and <= 7.78.0 connects to an IMAP or POP3 server to retrieve data using STARTTLS to upgrade to TLS security, the server can respond and send back multiple responses at once that curl caches. curl would then upgrade to TLS but not flush the in-queue of cached responses but instead continue using and trustingthe responses it got before the TLS handshake as if they were authenticated.Using this flaw, it allows a Man-In-The-Middle attacker to first inject the fake responses, then pass-through the TLS traffic from the legitimate server and trick curl into sending data back to the user thinking the attacker's injected data comes from the TLS-protected server.
Remediation
Upgrade Debian:11 curl to version 7.74.0-1.3+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2021-22947
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RWLEC6YVEM2HWUBX67SDGPSY4CQB72OE/
- https://hackerone.com/reports/1334763
- https://www.oracle.com/security-alerts/cpuoct2021.html
- https://lists.debian.org/debian-lts-announce/2021/09/msg00022.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/APOAK4X73EJTAPTSVT7IRVDMUWVXNWGD/
- http://seclists.org/fulldisclosure/2022/Mar/29
- https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf
- https://lists.debian.org/debian-lts-announce/2022/08/msg00017.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/APOAK4X73EJTAPTSVT7IRVDMUWVXNWGD/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/RWLEC6YVEM2HWUBX67SDGPSY4CQB72OE/
- https://security.gentoo.org/glsa/202212-01
- https://security.netapp.com/advisory/ntap-20211029-0003/
- https://support.apple.com/kb/HT213183
- https://www.debian.org/security/2022/dsa-5197
- https://www.oracle.com/security-alerts/cpuapr2022.html
- https://www.oracle.com/security-alerts/cpujan2022.html
- https://www.oracle.com/security-alerts/cpujul2022.html
- https://cert-portal.siemens.com/productcert/html/ssa-389290.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
medium severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
- Fixed in: 7.74.0-1.3+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
When curl < 7.84.0 does FTP transfers secured by krb5, it handles message verification failures wrongly. This flaw makes it possible for a Man-In-The-Middle attack to go unnoticed and even allows it to inject data to the client.
Remediation
Upgrade Debian:11 curl to version 7.74.0-1.3+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-32208
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BEV6BR4MTI3CEWK2YU2HQZUW5FAS3FEY/
- http://seclists.org/fulldisclosure/2022/Oct/28
- http://seclists.org/fulldisclosure/2022/Oct/41
- https://hackerone.com/reports/1590071
- https://lists.debian.org/debian-lts-announce/2022/08/msg00017.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BEV6BR4MTI3CEWK2YU2HQZUW5FAS3FEY/
- https://security.gentoo.org/glsa/202212-01
- https://security.netapp.com/advisory/ntap-20220915-0003/
- https://support.apple.com/kb/HT213488
- https://www.debian.org/security/2022/dsa-5197
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-419740.html
- https://cert-portal.siemens.com/productcert/html/ssa-558014.html
- https://cert-portal.siemens.com/productcert/html/ssa-942865.html
medium severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
- Fixed in: 7.74.0-1.3+deb11u5
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A use after free vulnerability exists in curl <7.87.0. Curl can be asked to tunnel virtually all protocols it supports through an HTTP proxy. HTTP proxies can (and often do) deny such tunnel operations. When getting denied to tunnel the specific protocols SMB or TELNET, curl would use a heap-allocated struct after it had been freed, in its transfer shutdown code path.
Remediation
Upgrade Debian:11 curl to version 7.74.0-1.3+deb11u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-43552
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-892048.html
- http://seclists.org/fulldisclosure/2023/Mar/17
- https://hackerone.com/reports/1764858
- https://security.gentoo.org/glsa/202310-12
- https://security.netapp.com/advisory/ntap-20230214-0002/
- https://support.apple.com/kb/HT213670
medium severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.10-2+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › expat/libexpat1@2.2.10-2+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libexpat before 2.8.2 lacks handler call depth tracking for calls to XML_GetBuffer, XML_Parse, XML_ParseBuffer, XML_ParserFree, or XML_ParserReset from within handlers in cases of a policy violation. Thus, a use-after-free can occur,
Remediation
There is no fixed version for Debian:11 expat.
References
medium severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › glibc/libc-bin@2.31-13+deb11u3
-
Introduced through: nginx@1.21 › glibc/libc6@2.31-13+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw has been identified in glibc. In an uncommon situation, the gaih_inet function may use memory that has been freed, resulting in an application crash. This issue is only exploitable when the getaddrinfo function is called and the hosts database in /etc/nsswitch.conf is configured with SUCCESS=continue or SUCCESS=merge.
Remediation
There is no fixed version for Debian:11 glibc.
References
- https://security-tracker.debian.org/tracker/CVE-2023-4813
- http://www.openwall.com/lists/oss-security/2023/10/03/8
- https://security.netapp.com/advisory/ntap-20231110-0003/
- https://access.redhat.com/errata/RHBA-2024:2413
- https://access.redhat.com/errata/RHSA-2023:5453
- https://access.redhat.com/errata/RHSA-2023:5455
- https://access.redhat.com/errata/RHSA-2023:7409
- https://access.redhat.com/security/cve/CVE-2023-4813
- https://bugzilla.redhat.com/show_bug.cgi?id=2237798
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
medium severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.1-5
- Fixed in: 3.7.1-5+deb11u4
Detailed paths
-
Introduced through: nginx@1.21 › gnutls28/libgnutls30@3.7.1-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A vulnerability was found that the response times to malformed ciphertexts in RSA-PSK ClientKeyExchange differ from response times of ciphertexts with correct PKCS#1 v1.5 padding.
Remediation
Upgrade Debian:11 gnutls28 to version 3.7.1-5+deb11u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-5981
- http://www.openwall.com/lists/oss-security/2024/01/19/3
- https://lists.debian.org/debian-lts-announce/2023/11/msg00016.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/7ZEIOLORQ7N6WRPFXZSYDL2MC4LP7VFV/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GNXKVR5YNUEBNHAHM5GSYKBZX4W2HMN2/
- https://access.redhat.com/errata/RHSA-2024:0155
- https://access.redhat.com/errata/RHSA-2024:0319
- https://access.redhat.com/errata/RHSA-2024:0399
- https://access.redhat.com/errata/RHSA-2024:0451
- https://access.redhat.com/errata/RHSA-2024:0533
- https://access.redhat.com/errata/RHSA-2024:1383
- https://access.redhat.com/errata/RHSA-2024:2094
- https://access.redhat.com/security/cve/CVE-2023-5981
- https://bugzilla.redhat.com/show_bug.cgi?id=2248445
- https://gnutls.org/security-new.html#GNUTLS-SA-2023-10-23
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
medium severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.18.3-6+deb11u1, krb5/libk5crypto3@1.18.3-6+deb11u1 and others
- Fixed in: 1.18.3-6+deb11u7
Detailed paths
-
Introduced through: nginx@1.21 › krb5/libgssapi-krb5-2@1.18.3-6+deb11u1
-
Introduced through: nginx@1.21 › krb5/libk5crypto3@1.18.3-6+deb11u1
-
Introduced through: nginx@1.21 › krb5/libkrb5-3@1.18.3-6+deb11u1
-
Introduced through: nginx@1.21 › krb5/libkrb5support0@1.18.3-6+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
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:11 krb5 to version 1.18.3-6+deb11u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-3576
- https://access.redhat.com/security/cve/CVE-2025-3576
- https://bugzilla.redhat.com/show_bug.cgi?id=2359465
- https://lists.debian.org/debian-lts-announce/2025/05/msg00047.html
- https://access.redhat.com/errata/RHSA-2025:8411
- https://access.redhat.com/errata/RHSA-2025:9418
- https://access.redhat.com/errata/RHSA-2025:9430
- https://access.redhat.com/errata/RHSA-2025:11487
- https://web.mit.edu/kerberos/krb5-1.22/krb5-1.22.html
- https://access.redhat.com/errata/RHSA-2025:13664
- https://access.redhat.com/errata/RHSA-2025:13777
- https://access.redhat.com/errata/RHSA-2025:15000
- https://access.redhat.com/errata/RHSA-2025:15002
- https://access.redhat.com/errata/RHSA-2025:15004
- https://access.redhat.com/errata/RHSA-2025:15001
- https://access.redhat.com/errata/RHSA-2025:15003
- https://cert-portal.siemens.com/productcert/html/ssa-577017.html
medium severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.10+dfsg-6.7+deb11u2
- Fixed in: 2.9.10+dfsg-6.7+deb11u10
Detailed paths
-
Introduced through: nginx@1.21 › libxml2@2.9.10+dfsg-6.7+deb11u2
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:11 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
Upgrade Debian:11 libxml2 to version 2.9.10+dfsg-6.7+deb11u10 or higher.
References
medium severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
- Fixed in: 1.1.1n-0+deb11u4
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A timing based side channel exists in the OpenSSL RSA Decryption implementation which could be sufficient to recover a plaintext across a network in a Bleichenbacher style attack. To achieve a successful decryption an attacker would have to be able to send a very large number of trial messages for decryption. The vulnerability affects all RSA padding modes: PKCS#1 v1.5, RSA-OEAP and RSASVE.
For example, in a TLS connection, RSA is commonly used by a client to send an encrypted pre-master secret to the server. An attacker that had observed a genuine connection between a client and a server could use this flaw to send trial messages to the server and record the time taken to process them. After a sufficiently large number of messages the attacker could recover the pre-master secret used for the original connection and thus be able to decrypt the application data sent over that connection.
Remediation
Upgrade Debian:11 openssl to version 1.1.1n-0+deb11u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-4304
- https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2023-0003
- https://security.gentoo.org/glsa/202402-08
- https://www.openssl.org/news/secadv/20230207.txt
- https://cert-portal.siemens.com/productcert/html/ssa-203374.html
- https://cert-portal.siemens.com/productcert/html/ssa-264814.html
- https://cert-portal.siemens.com/productcert/html/ssa-337522.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-556635.html
- https://cert-portal.siemens.com/productcert/html/ssa-561322.html
- https://cert-portal.siemens.com/productcert/html/ssa-625862.html
- https://cert-portal.siemens.com/productcert/html/ssa-699386.html
- https://cert-portal.siemens.com/productcert/html/ssa-769027.html
- https://cert-portal.siemens.com/productcert/html/ssa-794697.html
- https://cert-portal.siemens.com/productcert/html/ssa-879734.html
- https://cert-portal.siemens.com/productcert/html/ssa-943925.html
medium severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@247.3-7 and systemd/libudev1@247.3-7
- Fixed in: 247.3-7+deb11u6
Detailed paths
-
Introduced through: nginx@1.21 › systemd/libsystemd0@247.3-7
-
Introduced through: nginx@1.21 › systemd/libudev1@247.3-7
NVD Description
Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A vulnerability was found in systemd-resolved. This issue may allow systemd-resolved to accept records of DNSSEC-signed domains even when they have no signature, allowing man-in-the-middles (or the upstream DNS resolver) to manipulate records.
Remediation
Upgrade Debian:11 systemd to version 247.3-7+deb11u6 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-7008
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4GMDEG5PKONWNHOEYSUDRT6JEOISRMN2/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QHNBXGKJWISJETTTDTZKTBFIBJUOSLKL/
- https://security.netapp.com/advisory/ntap-20241122-0004/
- https://lists.debian.org/debian-lts-announce/2024/09/msg00001.html
- https://access.redhat.com/errata/RHSA-2024:2463
- https://access.redhat.com/errata/RHSA-2024:3203
- https://access.redhat.com/security/cve/CVE-2023-7008
- https://bugzilla.redhat.com/show_bug.cgi?id=2222261
- https://bugzilla.redhat.com/show_bug.cgi?id=2222672
- https://github.com/systemd/systemd/issues/25676
- https://cert-portal.siemens.com/productcert/html/ssa-794697.html
medium severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
- Fixed in: 7.74.0-1.3+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
An insufficiently protected credentials vulnerability exists in curl 4.9 to and include curl 7.82.0 are affected that could allow an attacker to extract credentials when follows HTTP(S) redirects is used with authentication could leak credentials to other services that exist on different protocols or port numbers.
Remediation
Upgrade Debian:11 curl to version 7.74.0-1.3+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-27774
- https://lists.debian.org/debian-lts-announce/2023/01/msg00028.html
- https://security.gentoo.org/glsa/202212-01
- https://security.netapp.com/advisory/ntap-20220609-0008/
- https://www.debian.org/security/2022/dsa-5197
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://hackerone.com/reports/1543773
medium severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
- Fixed in: 7.74.0-1.3+deb11u8
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
An authentication bypass vulnerability exists in libcurl prior to v8.0.0 where it reuses a previously established SSH connection despite the fact that an SSH option was modified, which should have prevented reuse. libcurl maintains a pool of previously used connections to reuse them for subsequent transfers if the configurations match. However, two SSH settings were omitted from the configuration check, allowing them to match easily, potentially leading to the reuse of an inappropriate connection.
Remediation
Upgrade Debian:11 curl to version 7.74.0-1.3+deb11u8 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-27538
- https://curl.se/docs/CVE-2023-27538.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/36NBD5YLJXXEDZLDGNFCERWRYJQ6LAQW/
- https://hackerone.com/reports/1898475
- https://lists.debian.org/debian-lts-announce/2023/04/msg00025.html
- https://security.gentoo.org/glsa/202310-12
- https://security.netapp.com/advisory/ntap-20230420-0010/
- https://cert-portal.siemens.com/productcert/html/ssa-077170.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-943925.html
medium severity
- Vulnerable module: libx11/libx11-6
- Introduced through: libx11/libx11-6@2:1.7.2-1 and libx11/libx11-data@2:1.7.2-1
- Fixed in: 2:1.7.2-1+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › libx11/libx11-6@2:1.7.2-1
-
Introduced through: nginx@1.21 › libx11/libx11-data@2:1.7.2-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libx11 package and not the libx11 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A vulnerability was found in libX11 due to an infinite loop within the PutSubImage() function. This flaw allows a local user to consume all available system resources and cause a denial of service condition.
Remediation
Upgrade Debian:11 libx11 to version 2:1.7.2-1+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-43786
- http://www.openwall.com/lists/oss-security/2024/01/24/9
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/63IBRFLQVZSMOAZBZOBKFWJP26ILRAGQ/
- https://security.netapp.com/advisory/ntap-20231103-0006/
- https://access.redhat.com/errata/RHSA-2024:2145
- https://access.redhat.com/errata/RHSA-2024:2973
- https://access.redhat.com/security/cve/CVE-2023-43786
- https://bugzilla.redhat.com/show_bug.cgi?id=2242253
- https://lists.debian.org/debian-lts-announce/2023/10/msg00005.html
medium severity
- Vulnerable module: libx11/libx11-6
- Introduced through: libx11/libx11-6@2:1.7.2-1 and libx11/libx11-data@2:1.7.2-1
- Fixed in: 2:1.7.2-1+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › libx11/libx11-6@2:1.7.2-1
-
Introduced through: nginx@1.21 › libx11/libx11-data@2:1.7.2-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libx11 package and not the libx11 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A vulnerability was found in libX11 due to a boundary condition within the _XkbReadKeySyms() function. This flaw allows a local user to trigger an out-of-bounds read error and read the contents of memory on the system.
Remediation
Upgrade Debian:11 libx11 to version 2:1.7.2-1+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-43785
- https://security.netapp.com/advisory/ntap-20231103-0006/
- https://access.redhat.com/errata/RHSA-2024:2145
- https://access.redhat.com/errata/RHSA-2024:2973
- https://access.redhat.com/security/cve/CVE-2023-43785
- https://bugzilla.redhat.com/show_bug.cgi?id=2242252
- https://lists.debian.org/debian-lts-announce/2023/10/msg00004.html
medium severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.10+dfsg-6.7+deb11u2
- Fixed in: 2.9.10+dfsg-6.7+deb11u9
Detailed paths
-
Introduced through: nginx@1.21 › libxml2@2.9.10+dfsg-6.7+deb11u2
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:11 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:11 libxml2 to version 2.9.10+dfsg-6.7+deb11u9 or higher.
References
medium severity
- Vulnerable module: libxpm/libxpm4
- Introduced through: libxpm/libxpm4@1:3.5.12-1
- Fixed in: 1:3.5.12-1.1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › libxpm/libxpm4@1:3.5.12-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxpm package and not the libxpm package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A vulnerability was found in libXpm where a vulnerability exists due to a boundary condition, a local user can trigger an out-of-bounds read error and read contents of memory on the system.
Remediation
Upgrade Debian:11 libxpm to version 1:3.5.12-1.1+deb11u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-43789
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/63IBRFLQVZSMOAZBZOBKFWJP26ILRAGQ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/I3KFUQT42R7TB4D7RISNSBQFJGLTQGUL/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TFAJTBNO3PAIA6EGZR4PN62H6RLKNDTE/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZECBCLDYUGLDSVV75ECPIBW7JXOB3747/
- https://lists.debian.org/debian-lts-announce/2023/10/msg00005.html
- https://access.redhat.com/errata/RHSA-2024:2146
- https://access.redhat.com/errata/RHSA-2024:2217
- https://access.redhat.com/errata/RHSA-2024:2974
- https://access.redhat.com/errata/RHSA-2024:3022
- https://access.redhat.com/security/cve/CVE-2023-43789
- https://bugzilla.redhat.com/show_bug.cgi?id=2242249
medium severity
- Vulnerable module: libxpm/libxpm4
- Introduced through: libxpm/libxpm4@1:3.5.12-1
- Fixed in: 1:3.5.12-1.1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › libxpm/libxpm4@1:3.5.12-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxpm package and not the libxpm package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A vulnerability was found in libXpm due to a boundary condition within the XpmCreateXpmImageFromBuffer() function. This flaw allows a local attacker to trigger an out-of-bounds read error and read the contents of memory on the system.
Remediation
Upgrade Debian:11 libxpm to version 1:3.5.12-1.1+deb11u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-43788
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/63IBRFLQVZSMOAZBZOBKFWJP26ILRAGQ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/I3KFUQT42R7TB4D7RISNSBQFJGLTQGUL/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TFAJTBNO3PAIA6EGZR4PN62H6RLKNDTE/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/V6FARGWN7VWXXWPXYNEEDJLRR3EWFZ3T/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZECBCLDYUGLDSVV75ECPIBW7JXOB3747/
- https://access.redhat.com/errata/RHSA-2024:2146
- https://access.redhat.com/errata/RHSA-2024:2217
- https://access.redhat.com/errata/RHSA-2024:2974
- https://access.redhat.com/errata/RHSA-2024:3022
- https://access.redhat.com/security/cve/CVE-2023-43788
- https://bugzilla.redhat.com/show_bug.cgi?id=2242248
- https://lists.debian.org/debian-lts-announce/2023/10/msg00005.html
medium severity
- Vulnerable module: libxslt/libxslt1.1
- Introduced through: libxslt/libxslt1.1@1.1.34-4
Detailed paths
-
Introduced through: nginx@1.21 › libxslt/libxslt1.1@1.1.34-4
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:11 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:11 libxslt.
References
- https://security-tracker.debian.org/tracker/CVE-2025-10911
- https://access.redhat.com/security/cve/CVE-2025-10911
- https://bugzilla.redhat.com/show_bug.cgi?id=2397838
- https://gitlab.gnome.org/GNOME/libxslt/-/issues/144
- https://gitlab.gnome.org/GNOME/libxslt/-/merge_requests/77
- https://access.redhat.com/errata/RHSA-2026:11015
- https://access.redhat.com/errata/RHSA-2026:26355
- https://access.redhat.com/errata/RHSA-2026:28243
- https://access.redhat.com/errata/RHSA-2026:28584
- https://access.redhat.com/errata/RHSA-2026:29807
- https://access.redhat.com/errata/RHSA-2026:29809
- https://access.redhat.com/errata/RHSA-2026:29811
- https://access.redhat.com/errata/RHSA-2026:29814
- https://access.redhat.com/errata/RHSA-2026:29975
- https://access.redhat.com/errata/RHSA-2026:29976
- https://access.redhat.com/errata/RHSA-2026:30847
- https://access.redhat.com/errata/RHSA-2026:33313
- https://access.redhat.com/errata/RHSA-2026:44481
- https://access.redhat.com/errata/RHSA-2026:58981
- https://access.redhat.com/errata/RHSA-2026:74674
medium severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
- Fixed in: 1.1.1w-0+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Issue summary: Processing a maliciously formatted PKCS12 file may lead OpenSSL to crash leading to a potential Denial of Service attack
Impact summary: Applications loading files in the PKCS12 format from untrusted sources might terminate abruptly.
A file in PKCS12 format can contain certificates and keys and may come from an untrusted source. The PKCS12 specification allows certain fields to be NULL, but OpenSSL does not correctly check for this case. This can lead to a NULL pointer dereference that results in OpenSSL crashing. If an application processes PKCS12 files from an untrusted source using the OpenSSL APIs then that application will be vulnerable to this issue.
OpenSSL APIs that are vulnerable to this are: PKCS12_parse(), PKCS12_unpack_p7data(), PKCS12_unpack_p7encdata(), PKCS12_unpack_authsafes() and PKCS12_newpass().
We have also fixed a similar issue in SMIME_write_PKCS7(). However since this function is related to writing data we do not consider it security significant.
The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue.
Remediation
Upgrade Debian:11 openssl to version 1.1.1w-0+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-0727
- http://www.openwall.com/lists/oss-security/2024/03/11/1
- https://security.netapp.com/advisory/ntap-20240208-0006/
- https://lists.debian.org/debian-lts-announce/2024/10/msg00033.html
- https://lists.debian.org/debian-lts-announce/2024/11/msg00000.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
- https://cert-portal.siemens.com/productcert/html/ssa-277137.html
- https://cert-portal.siemens.com/productcert/html/ssa-331112.html
- https://cert-portal.siemens.com/productcert/html/ssa-769027.html
- https://cert-portal.siemens.com/productcert/html/ssa-915275.html
- https://github.com/openssl/openssl/commit/09df4395b5071217b76dc7d3d2e630eb8c5a79c2
- https://github.com/openssl/openssl/commit/775acfdbd0c6af9ac855f34969cdab0c0c90844a
- https://github.com/openssl/openssl/commit/d135eeab8a5dbf72b3da5240bab9ddb7678dbd2c
- https://github.openssl.org/openssl/extended-releases/commit/03b3941d60c4bce58fab69a0c22377ab439bc0e8
- https://github.openssl.org/openssl/extended-releases/commit/aebaa5883e31122b404e450732dc833dc9dee539
- https://www.openssl.org/news/secadv/20240125.txt
medium severity
- Vulnerable module: pam/libpam-modules
- Introduced through: pam/libpam-modules@1.4.0-9+deb11u1, pam/libpam-modules-bin@1.4.0-9+deb11u1 and others
- Fixed in: 1.4.0-9+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › pam/libpam-modules@1.4.0-9+deb11u1
-
Introduced through: nginx@1.21 › pam/libpam-modules-bin@1.4.0-9+deb11u1
-
Introduced through: nginx@1.21 › pam/libpam-runtime@1.4.0-9+deb11u1
-
Introduced through: nginx@1.21 › pam/libpam0g@1.4.0-9+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream pam package and not the pam package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
linux-pam (aka Linux PAM) before 1.6.0 allows attackers to cause a denial of service (blocked login process) via mkfifo because the openat call (for protect_dir) lacks O_DIRECTORY.
Remediation
Upgrade Debian:11 pam to version 1.4.0-9+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-22365
- https://lists.debian.org/debian-lts-announce/2025/09/msg00021.html
- https://cert-portal.siemens.com/productcert/html/ssa-577017.html
- https://cert-portal.siemens.com/productcert/html/ssa-794697.html
- http://www.openwall.com/lists/oss-security/2024/01/18/3
- https://github.com/linux-pam/linux-pam
- https://github.com/linux-pam/linux-pam/commit/031bb5a5d0d950253b68138b498dc93be69a64cb
- https://github.com/linux-pam/linux-pam/releases/tag/v1.6.0
medium severity
- Vulnerable module: shadow/login
- Introduced through: shadow/login@1:4.8.1-1 and shadow/passwd@1:4.8.1-1
- Fixed in: 1:4.8.1-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › shadow/login@1:4.8.1-1
-
Introduced through: nginx@1.21 › shadow/passwd@1:4.8.1-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream shadow package and not the shadow package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw was found in shadow-utils. When asking for a new password, shadow-utils asks the password twice. If the password fails on the second attempt, shadow-utils fails in cleaning the buffer used to store the first entry. This may allow an attacker with enough access to retrieve the password from the memory.
Remediation
Upgrade Debian:11 shadow to version 1:4.8.1-1+deb11u1 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: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@247.3-7 and systemd/libudev1@247.3-7
- Fixed in: 247.3-7+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › systemd/libsystemd0@247.3-7
-
Introduced through: nginx@1.21 › systemd/libudev1@247.3-7
NVD Description
Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A vulnerability was found in systemd. This security flaw can cause a local information leak due to systemd-coredump not respecting the fs.suid_dumpable kernel setting.
Remediation
Upgrade Debian:11 systemd to version 247.3-7+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-4415
- https://security.netapp.com/advisory/ntap-20230216-0010/
- http://seclists.org/fulldisclosure/2025/Jun/9
- https://github.com/systemd/systemd/commit/b7641425659243c09473cd8fb3aef2c0d4a3eb9c
- https://www.openwall.com/lists/oss-security/2022/12/21/3
medium severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@247.3-7 and systemd/libudev1@247.3-7
- Fixed in: 247.3-7+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › systemd/libsystemd0@247.3-7
-
Introduced through: nginx@1.21 › systemd/libudev1@247.3-7
NVD Description
Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
An off-by-one Error issue was discovered in Systemd in format_timespan() function of time-util.c. An attacker could supply specific values for time and accuracy that leads to buffer overrun in format_timespan(), leading to a Denial of Service.
Remediation
Upgrade Debian:11 systemd to version 247.3-7+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-3821
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RVBQC2VLSDVQAPJTEMTREXDL4HYLXG2P/
- https://bugzilla.redhat.com/show_bug.cgi?id=2139327
- https://github.com/systemd/systemd/commit/9102c625a673a3246d7e73d8737f3494446bad4e
- https://github.com/systemd/systemd/issues/23928
- https://github.com/systemd/systemd/pull/23933
- https://lists.debian.org/debian-lts-announce/2023/06/msg00036.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/RVBQC2VLSDVQAPJTEMTREXDL4HYLXG2P/
- https://security.gentoo.org/glsa/202305-15
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
medium severity
- Vulnerable module: tar
- Introduced through: tar@1.34+dfsg-1
- Fixed in: 1.34+dfsg-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › tar@1.34+dfsg-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tar package and not the tar package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
GNU Tar through 1.34 has a one-byte out-of-bounds read that results in use of uninitialized memory for a conditional jump. Exploitation to change the flow of control has not been demonstrated. The issue occurs in from_header in list.c via a V7 archive in which mtime has approximately 11 whitespace characters.
Remediation
Upgrade Debian:11 tar to version 1.34+dfsg-1+deb11u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-48303
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/CRY7VEL4AIG3GLIEVCTOXRZNSVYDYYUD/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/X5VQYCO52Z7GAVCLRYUITN7KXHLRZQS4/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/CRY7VEL4AIG3GLIEVCTOXRZNSVYDYYUD/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/X5VQYCO52Z7GAVCLRYUITN7KXHLRZQS4/
- https://savannah.gnu.org/bugs/?62387
- https://savannah.gnu.org/patch/?10307
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-806742.html
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u4
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libtiff 4.5.0 is vulnerable to Buffer Overflow via extractContigSamplesShifted8bits() at /libtiff/tools/tiffcrop.c:3753.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u4 or higher.
References
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u6
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libtiff 4.5.0 is vulnerable to Buffer Overflow in uv_encode() when libtiff reads a corrupted little-endian TIFF file and specifies the output to be big-endian.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u6 or higher.
References
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u6
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libtiff 4.5.0 is vulnerable to Buffer Overflow via /libtiff/tools/tiffcrop.c:8499. Incorrect updating of buffer size after rotateImage() in tiffcrop cause heap-buffer-overflow and SEGV.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u6 or higher.
References
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libtiff's tiffcrop utility has a improper input validation flaw that can lead to out of bounds read and ultimately cause a crash if an attacker is able to supply a crafted file to tiffcrop.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u3 or higher.
References
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libtiff's tiffcrop tool has a uint32_t underflow which leads to out of bounds read and write in the extractContigSamples8bits routine. An attacker who supplies a crafted file to tiffcrop could trigger this flaw, most likely by tricking a user into opening the crafted file with tiffcrop. Triggering this flaw could cause a crash or potentially further exploitation.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u3 or higher.
References
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libtiff's tiffcrop utility has a uint32_t underflow that can lead to out of bounds read and write. An attacker who supplies a crafted file to tiffcrop (likely via tricking a user to run tiffcrop on it with certain parameters) could cause a crash or in some cases, further exploitation.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u3 or higher.
References
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u5
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A memory leak flaw was found in Libtiff's tiffcrop utility. This issue occurs when tiffcrop operates on a TIFF image file, allowing an attacker to pass a crafted TIFF image file to tiffcrop utility, which causes this memory leak issue, resulting an application crash, eventually leading to a denial of service.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u5 or higher.
References
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u6
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A null pointer dereference issue was found in Libtiff's tif_dir.c file. This issue may allow an attacker to pass a crafted TIFF image file to the tiffcp utility which triggers a runtime error that causes undefined behavior. This will result in an application crash, eventually leading to a denial of service.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u6 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-2908
- https://access.redhat.com/security/cve/CVE-2023-2908
- https://bugzilla.redhat.com/show_bug.cgi?id=2218830
- https://gitlab.com/libtiff/libtiff/-/commit/9bd48f0dbd64fb94dc2b5b05238fde0bfdd4ff3f
- https://gitlab.com/libtiff/libtiff/-/merge_requests/479
- https://lists.debian.org/debian-lts-announce/2023/07/msg00034.html
- https://lists.debian.org/debian-lts-announce/2025/01/msg00019.html
- https://security.netapp.com/advisory/ntap-20230731-0004/
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A heap buffer overflow flaw was found in Libtiffs' tiffinfo.c in TIFFReadRawDataStriped() function. This flaw allows an attacker to pass a crafted TIFF file to the tiffinfo tool, triggering a heap buffer overflow issue and causing a crash that leads to a denial of service.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-1354
- https://access.redhat.com/errata/RHSA-2022:8194
- https://access.redhat.com/security/cve/CVE-2022-1354
- https://bugzilla.redhat.com/show_bug.cgi?id=2074404
- https://gitlab.com/libtiff/libtiff/-/commit/87f580f39011109b3bb5f6eca13fac543a542798
- https://gitlab.com/libtiff/libtiff/-/issues/319
- https://lists.debian.org/debian-lts-announce/2023/01/msg00018.html
- https://security.gentoo.org/glsa/202210-10
- https://security.netapp.com/advisory/ntap-20221014-0007/
- https://www.debian.org/security/2023/dsa-5333
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
LibTIFF master branch has an out-of-bounds read in LZWDecode in libtiff/tif_lzw.c:624, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit b4e79bfa.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-1623
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/C7IWZTB4J2N4F5OR5QY4VHDSKWKZSWN3/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UXAFOP6QQRNZD3HPZ6BMCEZZOM4YIZMK/
- https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-1623.json
- https://gitlab.com/libtiff/libtiff/-/commit/b4e79bfa0c7d2d08f6f1e7ec38143fc8cb11394a
- https://gitlab.com/libtiff/libtiff/-/issues/410
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/C7IWZTB4J2N4F5OR5QY4VHDSKWKZSWN3/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/UXAFOP6QQRNZD3HPZ6BMCEZZOM4YIZMK/
- https://security.gentoo.org/glsa/202210-10
- https://security.netapp.com/advisory/ntap-20220616-0005/
- https://www.debian.org/security/2023/dsa-5333
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
LibTIFF master branch has an out-of-bounds read in LZWDecode in libtiff/tif_lzw.c:619, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit b4e79bfa.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-1622
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/C7IWZTB4J2N4F5OR5QY4VHDSKWKZSWN3/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UXAFOP6QQRNZD3HPZ6BMCEZZOM4YIZMK/
- http://seclists.org/fulldisclosure/2022/Oct/28
- http://seclists.org/fulldisclosure/2022/Oct/39
- http://seclists.org/fulldisclosure/2022/Oct/41
- https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-1622.json
- https://gitlab.com/libtiff/libtiff/-/commit/b4e79bfa0c7d2d08f6f1e7ec38143fc8cb11394a
- https://gitlab.com/libtiff/libtiff/-/issues/410
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/C7IWZTB4J2N4F5OR5QY4VHDSKWKZSWN3/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/UXAFOP6QQRNZD3HPZ6BMCEZZOM4YIZMK/
- https://security.netapp.com/advisory/ntap-20220616-0005/
- https://support.apple.com/kb/HT213443
- https://support.apple.com/kb/HT213444
- https://support.apple.com/kb/HT213446
- https://support.apple.com/kb/HT213486
- https://support.apple.com/kb/HT213487
- https://support.apple.com/kb/HT213488
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
LibTIFF 4.4.0 has an out-of-bounds read in extractImageSection in tools/tiffcrop.c:6905, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit 48d6ece8.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-2953
- https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-2953.json
- https://gitlab.com/libtiff/libtiff/-/commit/48d6ece8389b01129e7d357f0985c8f938ce3da3
- https://gitlab.com/libtiff/libtiff/-/issues/414
- https://security.netapp.com/advisory/ntap-20221014-0008/
- https://www.debian.org/security/2023/dsa-5333
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u4
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
LibTIFF 4.4.0 has an out-of-bounds read in tiffcrop in tools/tiffcrop.c:3488, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit afaabc3e.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-0795
- https://gitlab.com/gitlab-org/cves/-/blob/master/2023/CVE-2023-0795.json
- https://gitlab.com/libtiff/libtiff/-/commit/afaabc3e50d4e5d80a94143f7e3c997e7e410f68
- https://gitlab.com/libtiff/libtiff/-/issues/493
- https://lists.debian.org/debian-lts-announce/2023/02/msg00026.html
- https://security.gentoo.org/glsa/202305-31
- https://security.netapp.com/advisory/ntap-20230316-0003/
- https://www.debian.org/security/2023/dsa-5361
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u4
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
LibTIFF 4.4.0 has an out-of-bounds read in tiffcrop in libtiff/tif_unix.c:368, invoked by tools/tiffcrop.c:2903 and tools/tiffcrop.c:6921, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit afaabc3e.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-0797
- https://gitlab.com/gitlab-org/cves/-/blob/master/2023/CVE-2023-0797.json
- https://gitlab.com/libtiff/libtiff/-/commit/afaabc3e50d4e5d80a94143f7e3c997e7e410f68
- https://gitlab.com/libtiff/libtiff/-/issues/495
- https://lists.debian.org/debian-lts-announce/2023/02/msg00026.html
- https://security.gentoo.org/glsa/202305-31
- https://www.debian.org/security/2023/dsa-5361
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u4
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
LibTIFF 4.4.0 has an out-of-bounds read in tiffcrop in tools/tiffcrop.c:3592, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit afaabc3e.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-0796
- https://gitlab.com/gitlab-org/cves/-/blob/master/2023/CVE-2023-0796.json
- https://gitlab.com/libtiff/libtiff/-/commit/afaabc3e50d4e5d80a94143f7e3c997e7e410f68
- https://gitlab.com/libtiff/libtiff/-/issues/499
- https://lists.debian.org/debian-lts-announce/2023/02/msg00026.html
- https://security.gentoo.org/glsa/202305-31
- https://security.netapp.com/advisory/ntap-20230316-0003/
- https://www.debian.org/security/2023/dsa-5361
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u4
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
LibTIFF 4.4.0 has an out-of-bounds read in tiffcrop in tools/tiffcrop.c:3400, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit afaabc3e.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-0798
- https://gitlab.com/gitlab-org/cves/-/blob/master/2023/CVE-2023-0798.json
- https://gitlab.com/libtiff/libtiff/-/commit/afaabc3e50d4e5d80a94143f7e3c997e7e410f68
- https://gitlab.com/libtiff/libtiff/-/issues/492
- https://lists.debian.org/debian-lts-announce/2023/02/msg00026.html
- https://security.gentoo.org/glsa/202305-31
- https://security.netapp.com/advisory/ntap-20230316-0003/
- https://www.debian.org/security/2023/dsa-5361
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
LibTIFF 4.4.0 has an out-of-bounds read in tiffcp in tools/tiffcp.c:948, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit e8131125.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-4645
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/2ZTFA6GGOKFPIQNHDBMXYUR4XUXUJESE/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BA6GRCAQ7NR2OK5N44UQRGUJBIYKWJJH/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OLM763GGZVVOAXIQXG6YGTYJ5VFYNECQ/
- https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-4645.json
- https://gitlab.com/libtiff/libtiff/-/commit/e813112545942107551433d61afd16ac094ff246
- https://gitlab.com/libtiff/libtiff/-/issues/277
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/2ZTFA6GGOKFPIQNHDBMXYUR4XUXUJESE/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BA6GRCAQ7NR2OK5N44UQRGUJBIYKWJJH/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/OLM763GGZVVOAXIQXG6YGTYJ5VFYNECQ/
- https://security.netapp.com/advisory/ntap-20230331-0001/
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Multiple heap buffer overflows in tiffcrop.c utility in libtiff library Version 4.4.0 allows attacker to trigger unsafe or out of bounds memory access via crafted TIFF image file which could result into application crash, potential information disclosure or any other context-dependent impact
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-3570
- https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-3570.json
- https://gitlab.com/libtiff/libtiff/-/commit/bd94a9b383d8755a27b5a1bc27660b8ad10b094c
- https://gitlab.com/libtiff/libtiff/-/issues/381
- https://gitlab.com/libtiff/libtiff/-/issues/386
- https://lists.debian.org/debian-lts-announce/2023/01/msg00018.html
- https://security.netapp.com/advisory/ntap-20230203-0002/
- https://www.debian.org/security/2023/dsa-5333
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
processCropSelections in tools/tiffcrop.c in LibTIFF through 4.5.0 has a heap-based buffer overflow (e.g., "WRITE of size 307203") via a crafted TIFF image.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-48281
- https://gitlab.com/libtiff/libtiff/-/commit/d1b6b9c1b3cae2d9e37754506c1ad8f4f7b646b5
- https://gitlab.com/libtiff/libtiff/-/issues/488
- https://lists.debian.org/debian-lts-announce/2023/01/msg00037.html
- https://security.gentoo.org/glsa/202305-31
- https://security.netapp.com/advisory/ntap-20230302-0004/
- https://www.debian.org/security/2023/dsa-5333
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u4
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
LibTIFF 4.4.0 has an out-of-bounds write in tiffcrop in tools/tiffcrop.c:3724, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit 33aee127.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-0802
- https://gitlab.com/gitlab-org/cves/-/blob/master/2023/CVE-2023-0802.json
- https://gitlab.com/libtiff/libtiff/-/commit/33aee1275d9d1384791d2206776eb8152d397f00
- https://gitlab.com/libtiff/libtiff/-/issues/500
- https://lists.debian.org/debian-lts-announce/2023/02/msg00026.html
- https://security.gentoo.org/glsa/202305-31
- https://security.netapp.com/advisory/ntap-20230316-0002/
- https://www.debian.org/security/2023/dsa-5361
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u4
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
LibTIFF 4.4.0 has an out-of-bounds write in tiffcrop in tools/tiffcrop.c:3502, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit 33aee127.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-0800
- https://gitlab.com/gitlab-org/cves/-/blob/master/2023/CVE-2023-0800.json
- https://gitlab.com/libtiff/libtiff/-/commit/33aee1275d9d1384791d2206776eb8152d397f00
- https://gitlab.com/libtiff/libtiff/-/issues/496
- https://lists.debian.org/debian-lts-announce/2023/02/msg00026.html
- https://security.gentoo.org/glsa/202305-31
- https://security.netapp.com/advisory/ntap-20230316-0002/
- https://www.debian.org/security/2023/dsa-5361
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u4
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
LibTIFF 4.4.0 has an out-of-bounds write in tiffcrop in tools/tiffcrop.c:3609, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit 33aee127.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-0804
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/FBF3UUFSB6NB3NFTQSKOOIZGXJP3T34Z/
- https://gitlab.com/gitlab-org/cves/-/blob/master/2023/CVE-2023-0804.json
- https://gitlab.com/libtiff/libtiff/-/commit/33aee1275d9d1384791d2206776eb8152d397f00
- https://gitlab.com/libtiff/libtiff/-/issues/497
- https://lists.debian.org/debian-lts-announce/2023/02/msg00026.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FBF3UUFSB6NB3NFTQSKOOIZGXJP3T34Z/
- https://security.gentoo.org/glsa/202305-31
- https://security.netapp.com/advisory/ntap-20230324-0009/
- https://www.debian.org/security/2023/dsa-5361
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u4
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
LibTIFF 4.4.0 has an out-of-bounds write in tiffcrop in libtiff/tif_unix.c:368, invoked by tools/tiffcrop.c:2903 and tools/tiffcrop.c:6778, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit 33aee127.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-0801
- https://gitlab.com/gitlab-org/cves/-/blob/master/2023/CVE-2023-0801.json
- https://gitlab.com/libtiff/libtiff/-/commit/33aee1275d9d1384791d2206776eb8152d397f00
- https://gitlab.com/libtiff/libtiff/-/issues/498
- https://lists.debian.org/debian-lts-announce/2023/02/msg00026.html
- https://security.gentoo.org/glsa/202305-31
- https://security.netapp.com/advisory/ntap-20230316-0002/
- https://www.debian.org/security/2023/dsa-5361
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u4
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
LibTIFF 4.4.0 has an out-of-bounds write in tiffcrop in tools/tiffcrop.c:3516, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit 33aee127.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-0803
- https://gitlab.com/gitlab-org/cves/-/blob/master/2023/CVE-2023-0803.json
- https://gitlab.com/libtiff/libtiff/-/commit/33aee1275d9d1384791d2206776eb8152d397f00
- https://gitlab.com/libtiff/libtiff/-/issues/501
- https://lists.debian.org/debian-lts-announce/2023/02/msg00026.html
- https://security.gentoo.org/glsa/202305-31
- https://security.netapp.com/advisory/ntap-20230316-0002/
- https://www.debian.org/security/2023/dsa-5361
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A vulnerability was found in the libtiff library. This flaw causes a heap buffer overflow issue via the TIFFTAG_INKNAMES and TIFFTAG_NUMBEROFINKS values.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-30774
- http://seclists.org/fulldisclosure/2023/Oct/24
- https://access.redhat.com/security/cve/CVE-2023-30774
- https://bugzilla.redhat.com/show_bug.cgi?id=2187139
- https://gitlab.com/libtiff/libtiff/-/issues/463
- https://security.netapp.com/advisory/ntap-20230703-0002/
- https://support.apple.com/kb/HT213984
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Buffer Overflow vulnerability found in Libtiff V.4.0.7 allows a local attacker to cause a denial of service via the tiffcp function in tiffcp.c.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u3 or higher.
References
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u6
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
loadImage() in tools/tiffcrop.c in LibTIFF through 4.5.0 has a heap-based use after free via a crafted TIFF image.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u6 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-26965
- https://gitlab.com/libtiff/libtiff/-/merge_requests/472
- https://lists.debian.org/debian-lts-announce/2023/07/msg00034.html
- https://lists.debian.org/debian-lts-announce/2025/01/msg00019.html
- https://security.netapp.com/advisory/ntap-20230706-0009/
medium severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u4
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
LibTIFF 4.4.0 has an out-of-bounds read in tiffcrop in tools/tiffcrop.c:3701, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit afaabc3e.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-0799
- https://gitlab.com/gitlab-org/cves/-/blob/master/2023/CVE-2023-0799.json
- https://gitlab.com/libtiff/libtiff/-/commit/afaabc3e50d4e5d80a94143f7e3c997e7e410f68
- https://gitlab.com/libtiff/libtiff/-/issues/494
- https://lists.debian.org/debian-lts-announce/2023/02/msg00026.html
- https://security.gentoo.org/glsa/202305-31
- https://security.netapp.com/advisory/ntap-20230316-0003/
- https://www.debian.org/security/2023/dsa-5361
medium severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
When saving HSTS data to an excessively long file name, curl could end up removing all contents, making subsequent requests using that file unaware of the HSTS status they should otherwise use.
Remediation
There is no fixed version for Debian:11 curl.
References
- https://security-tracker.debian.org/tracker/CVE-2023-46219
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3ZX3VW67N4ACRAPMV2QS2LVYGD7H2MVE/
- https://curl.se/docs/CVE-2023-46219.html
- https://hackerone.com/reports/2236133
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UOGXU25FMMT2X6UUITQ7EZZYMJ42YWWD/
- https://security.netapp.com/advisory/ntap-20240119-0007/
- https://www.debian.org/security/2023/dsa-5587
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-093430.html
- https://cert-portal.siemens.com/productcert/html/ssa-331112.html
medium severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.1-5
- Fixed in: 3.7.1-5+deb11u9
Detailed paths
-
Introduced through: nginx@1.21 › gnutls28/libgnutls30@3.7.1-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw was found in GnuTLS. 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:11 gnutls28 to version 3.7.1-5+deb11u9 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-14831
- https://access.redhat.com/security/cve/CVE-2025-14831
- https://bugzilla.redhat.com/show_bug.cgi?id=2423177
- https://access.redhat.com/errata/RHSA-2026:3477
- https://access.redhat.com/errata/RHSA-2026:4188
- https://gitlab.com/gnutls/gnutls/-/issues/1773
- https://access.redhat.com/errata/RHSA-2026:4655
- https://access.redhat.com/errata/RHSA-2026:4943
- https://access.redhat.com/errata/RHSA-2026:5585
- https://access.redhat.com/errata/RHSA-2026:5606
- https://access.redhat.com/errata/RHSA-2026:6630
- https://access.redhat.com/errata/RHSA-2026:6618
- https://access.redhat.com/errata/RHSA-2026:6737
- https://access.redhat.com/errata/RHSA-2026:6738
- https://access.redhat.com/errata/RHSA-2026:7329
- https://access.redhat.com/errata/RHSA-2026:7335
- https://access.redhat.com/errata/RHSA-2026:8747
- https://access.redhat.com/errata/RHSA-2026:8746
- https://access.redhat.com/errata/RHSA-2026:8748
- https://access.redhat.com/errata/RHSA-2026:7477
- https://access.redhat.com/errata/RHSA-2026:13812
- https://access.redhat.com/errata/RHSA-2026:16174
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
- https://access.redhat.com/errata/RHSA-2026:16008
- https://access.redhat.com/errata/RHSA-2026:16009
- https://access.redhat.com/errata/RHSA-2026:25096
- https://access.redhat.com/errata/RHSA-2026:30849
- https://access.redhat.com/errata/RHSA-2026:30850
- https://access.redhat.com/errata/RHSA-2026:33125
- https://access.redhat.com/errata/RHSA-2026:82347
- https://access.redhat.com/errata/RHSA-2026:82354
- https://access.redhat.com/errata/RHSA-2026:82372
- https://access.redhat.com/errata/RHSA-2026:82857
medium severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.1-5
- Fixed in: 3.7.1-5+deb11u7
Detailed paths
-
Introduced through: nginx@1.21 › gnutls28/libgnutls30@3.7.1-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw was found in GnuTLS, 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:11 gnutls28 to version 3.7.1-5+deb11u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-12243
- https://access.redhat.com/security/cve/CVE-2024-12243
- https://bugzilla.redhat.com/show_bug.cgi?id=2344615
- https://gitlab.com/gnutls/libtasn1/-/issues/52
- https://lists.debian.org/debian-lts-announce/2025/02/msg00027.html
- https://access.redhat.com/errata/RHSA-2025:4051
- https://access.redhat.com/errata/RHSA-2025:7076
- https://access.redhat.com/errata/RHSA-2025:8020
- https://security.netapp.com/advisory/ntap-20250523-0002/
- https://access.redhat.com/errata/RHSA-2025:8385
- https://access.redhat.com/errata/RHSA-2025:17361
- https://gitlab.com/gnutls/gnutls/-/issues/1553
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-202008.html
medium severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.1-5
- Fixed in: 3.7.1-5+deb11u10
Detailed paths
-
Introduced through: nginx@1.21 › gnutls28/libgnutls30@3.7.1-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw was found in gnutls. An off-by-one error exists in the PKCS#12 bag element bounds check. This vulnerability allows an remote attacker to write past the internal array of a PKCS#12 bag when appending to a bag that already contains 32 elements. This memory corruption could lead to a denial of service (DoS) or potentially other unspecified impacts.
Remediation
Upgrade Debian:11 gnutls28 to version 3.7.1-5+deb11u10 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-42015
- https://access.redhat.com/security/cve/CVE-2026-42015
- https://bugzilla.redhat.com/show_bug.cgi?id=2467678
- https://access.redhat.com/errata/RHSA-2026:20611
- https://access.redhat.com/errata/RHSA-2026:20613
- https://access.redhat.com/errata/RHSA-2026:20612
- https://access.redhat.com/errata/RHSA-2026:13274
- https://access.redhat.com/errata/RHSA-2026:26319
- https://access.redhat.com/errata/RHSA-2026:26409
- https://access.redhat.com/errata/RHSA-2026:29197
- https://access.redhat.com/errata/RHSA-2026:30004
- https://access.redhat.com/errata/RHSA-2026:30849
- https://access.redhat.com/errata/RHSA-2026:30850
- https://access.redhat.com/errata/RHSA-2026:32962
- https://access.redhat.com/errata/RHSA-2026:33125
- https://access.redhat.com/errata/RHSA-2026:41921
- https://access.redhat.com/errata/RHSA-2026:43575
- https://www.gnutls.org/security-new.html#GNUTLS-SA-2026-04-29-11
- https://access.redhat.com/errata/RHSA-2026:58981
- https://access.redhat.com/errata/RHSA-2026:72502
- https://access.redhat.com/errata/RHSA-2026:74674
- https://access.redhat.com/errata/RHSA-2026:82304
- https://access.redhat.com/errata/RHSA-2026:82322
- https://access.redhat.com/errata/RHSA-2026:82347
- https://access.redhat.com/errata/RHSA-2026:82354
- https://access.redhat.com/errata/RHSA-2026:82372
- https://access.redhat.com/errata/RHSA-2026:82857
- https://access.redhat.com/errata/RHSA-2026:82888
medium severity
- Vulnerable module: libtasn1-6
- Introduced through: libtasn1-6@4.16.0-2
- Fixed in: 4.16.0-2+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › libtasn1-6@4.16.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:11 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:11 libtasn1-6 to version 4.16.0-2+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-12133
- https://access.redhat.com/security/cve/CVE-2024-12133
- https://bugzilla.redhat.com/show_bug.cgi?id=2344611
- https://gitlab.com/gnutls/libtasn1/-/issues/52
- http://www.openwall.com/lists/oss-security/2025/02/06/6
- https://lists.debian.org/debian-lts-announce/2025/02/msg00025.html
- https://access.redhat.com/errata/RHSA-2025:4049
- https://access.redhat.com/errata/RHSA-2025:7077
- https://access.redhat.com/errata/RHSA-2025:8021
- https://security.netapp.com/advisory/ntap-20250523-0003/
- https://access.redhat.com/errata/RHSA-2025:8385
- https://access.redhat.com/errata/RHSA-2025:17347
- https://gitlab.com/gnutls/libtasn1/-/blob/master/doc/security/CVE-2024-12133.md
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-202008.html
- https://access.redhat.com/errata/RHSA-2026:30849
- https://access.redhat.com/errata/RHSA-2026:30850
- https://access.redhat.com/errata/RHSA-2026:33125
medium severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
- Fixed in: 1.1.1v-0~deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Issue summary: Checking excessively long DH keys or parameters may be very slow.
Impact summary: Applications that use the functions DH_check(), DH_check_ex() or EVP_PKEY_param_check() to check a DH key or DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service.
The function DH_check() performs various checks on DH parameters. After fixing CVE-2023-3446 it was discovered that a large q parameter value can also trigger an overly long computation during some of these checks. A correct q value, if present, cannot be larger than the modulus p parameter, thus it is unnecessary to perform these checks if q is larger than p.
An application that calls DH_check() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack.
The function DH_check() is itself called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_ex() and EVP_PKEY_param_check().
Also vulnerable are the OpenSSL dhparam and pkeyparam command line applications when using the "-check" option.
The OpenSSL SSL/TLS implementation is not affected by this issue.
The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.
Remediation
Upgrade Debian:11 openssl to version 1.1.1v-0~deb11u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-3817
- http://seclists.org/fulldisclosure/2023/Jul/43
- http://www.openwall.com/lists/oss-security/2023/07/31/1
- http://www.openwall.com/lists/oss-security/2023/09/22/11
- http://www.openwall.com/lists/oss-security/2023/09/22/9
- http://www.openwall.com/lists/oss-security/2023/11/06/2
- https://lists.debian.org/debian-lts-announce/2023/08/msg00019.html
- https://security.gentoo.org/glsa/202402-08
- https://security.netapp.com/advisory/ntap-20230818-0014/
- https://security.netapp.com/advisory/ntap-20231027-0008/
- https://security.netapp.com/advisory/ntap-20240621-0006/
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=6a1eb62c29db6cb5eec707f9338aee00f44e26f5
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=869ad69aadd985c7b8ca6f4e5dd0eb274c9f3644
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=9002fd07327a91f35ba6c1307e71fa6fd4409b7f
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=91ddeba0f2269b017dc06c46c993a788974b1aa5
- https://www.openssl.org/news/secadv/20230731.txt
- https://cert-portal.siemens.com/productcert/html/ssa-099606.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-915275.html
- https://cert-portal.siemens.com/productcert/html/ssa-943925.html
medium severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
- Fixed in: 1.1.1n-0+deb11u5
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Applications that use a non-default option when verifying certificates may be vulnerable to an attack from a malicious CA to circumvent certain checks.
Invalid certificate policies in leaf certificates are silently ignored by OpenSSL and other certificate policy checks are skipped for that certificate. A malicious CA could use this to deliberately assert invalid certificate policies in order to circumvent policy checking on the certificate altogether.
Policy processing is disabled by default but can be enabled by passing
the -policy' argument to the command line utilities or by calling the X509_VERIFY_PARAM_set1_policies()' function.
Remediation
Upgrade Debian:11 openssl to version 1.1.1n-0+deb11u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-0465
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=10325176f3d3e98c6e2b3bf5ab1e3b334de6947a
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=1dd43e0709fece299b15208f36cc7c76209ba0bb
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=b013765abfa80036dc779dd0e50602c57bb3bf95
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=facfb1ab745646e97a1920977ae4a9965ea61d5c
- https://lists.debian.org/debian-lts-announce/2023/06/msg00011.html
- https://security.gentoo.org/glsa/202402-08
- https://security.netapp.com/advisory/ntap-20230414-0001/
- https://www.debian.org/security/2023/dsa-5417
- https://www.openssl.org/news/secadv/20230328.txt
- https://cert-portal.siemens.com/productcert/html/ssa-337522.html
- https://cert-portal.siemens.com/productcert/html/ssa-341067.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-556635.html
- https://cert-portal.siemens.com/productcert/html/ssa-625862.html
- https://cert-portal.siemens.com/productcert/html/ssa-769027.html
- https://cert-portal.siemens.com/productcert/html/ssa-794697.html
- https://cert-portal.siemens.com/productcert/html/ssa-879734.html
medium severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
- Fixed in: 1.1.1n-0+deb11u5
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
The function X509_VERIFY_PARAM_add0_policy() is documented to implicitly enable the certificate policy check when doing certificate verification. However the implementation of the function does not enable the check which allows certificates with invalid or incorrect policies to pass the certificate verification.
As suddenly enabling the policy check could break existing deployments it was decided to keep the existing behavior of the X509_VERIFY_PARAM_add0_policy() function.
Instead the applications that require OpenSSL to perform certificate policy check need to use X509_VERIFY_PARAM_set1_policies() or explicitly enable the policy check by calling X509_VERIFY_PARAM_set_flags() with the X509_V_FLAG_POLICY_CHECK flag argument.
Certificate policy checks are disabled by default in OpenSSL and are not commonly used by applications.
Remediation
Upgrade Debian:11 openssl to version 1.1.1n-0+deb11u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-0466
- http://www.openwall.com/lists/oss-security/2023/09/28/4
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=0d16b7e99aafc0b4a6d729eec65a411a7e025f0a
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=51e8a84ce742db0f6c70510d0159dad8f7825908
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=73398dea26de9899fb4baa94098ad0a61f435c72
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=fc814a30fc4f0bc54fcea7d9a7462f5457aab061
- https://lists.debian.org/debian-lts-announce/2023/06/msg00011.html
- https://security.gentoo.org/glsa/202402-08
- https://security.netapp.com/advisory/ntap-20230414-0001/
- https://www.debian.org/security/2023/dsa-5417
- https://www.openssl.org/news/secadv/20230328.txt
- https://cert-portal.siemens.com/productcert/html/ssa-337522.html
- https://cert-portal.siemens.com/productcert/html/ssa-341067.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-556635.html
- https://cert-portal.siemens.com/productcert/html/ssa-625862.html
- https://cert-portal.siemens.com/productcert/html/ssa-769027.html
- https://cert-portal.siemens.com/productcert/html/ssa-794697.html
- https://cert-portal.siemens.com/productcert/html/ssa-879734.html
medium severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
- Fixed in: 1.1.1w-0+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Issue summary: Generating excessively long X9.42 DH keys or checking excessively long X9.42 DH keys or parameters may be very slow.
Impact summary: Applications that use the functions DH_generate_key() to generate an X9.42 DH key may experience long delays. Likewise, applications that use DH_check_pub_key(), DH_check_pub_key_ex() or EVP_PKEY_public_check() to check an X9.42 DH key or X9.42 DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service.
While DH_check() performs all the necessary checks (as of CVE-2023-3817), DH_check_pub_key() doesn't make any of these checks, and is therefore vulnerable for excessively large P and Q parameters.
Likewise, while DH_generate_key() performs a check for an excessively large P, it doesn't check for an excessively large Q.
An application that calls DH_generate_key() or DH_check_pub_key() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack.
DH_generate_key() and DH_check_pub_key() are also called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_pub_key_ex(), EVP_PKEY_public_check(), and EVP_PKEY_generate().
Also vulnerable are the OpenSSL pkey command line application when using the "-pubcheck" option, as well as the OpenSSL genpkey command line application.
The OpenSSL SSL/TLS implementation is not affected by this issue.
The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.
Remediation
Upgrade Debian:11 openssl to version 1.1.1w-0+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-5678
- http://www.openwall.com/lists/oss-security/2023/11/06/2
- http://www.openwall.com/lists/oss-security/2024/03/11/1
- https://security.netapp.com/advisory/ntap-20231130-0010/
- https://lists.debian.org/debian-lts-announce/2024/10/msg00033.html
- https://lists.debian.org/debian-lts-announce/2024/11/msg00000.html
- https://cert-portal.siemens.com/productcert/html/ssa-093430.html
- https://cert-portal.siemens.com/productcert/html/ssa-128433.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
- https://cert-portal.siemens.com/productcert/html/ssa-277137.html
- https://cert-portal.siemens.com/productcert/html/ssa-331112.html
- https://cert-portal.siemens.com/productcert/html/ssa-341067.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-556635.html
- https://cert-portal.siemens.com/productcert/html/ssa-613116.html
- https://cert-portal.siemens.com/productcert/html/ssa-769027.html
- https://cert-portal.siemens.com/productcert/html/ssa-794697.html
- https://cert-portal.siemens.com/productcert/html/ssa-915275.html
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=34efaef6c103d636ab507a0cc34dca4d3aecc055
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=710fee740904b6290fef0dd5536fbcedbc38ff0c
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=db925ae2e65d0d925adef429afc37f75bd1c2017
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=ddeb4b6c6d527e54ce9a99cba785c0f7776e54b6
- https://www.openssl.org/news/secadv/20231106.txt
medium severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
- Fixed in: 1.1.1v-0~deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Issue summary: Checking excessively long DH keys or parameters may be very slow.
Impact summary: Applications that use the functions DH_check(), DH_check_ex() or EVP_PKEY_param_check() to check a DH key or DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service.
The function DH_check() performs various checks on DH parameters. One of those checks confirms that the modulus ('p' parameter) is not too large. Trying to use a very large modulus is slow and OpenSSL will not normally use a modulus which is over 10,000 bits in length.
However the DH_check() function checks numerous aspects of the key or parameters that have been supplied. Some of those checks use the supplied modulus value even if it has already been found to be too large.
An application that calls DH_check() and supplies a key or parameters obtained from an untrusted source could be vulernable to a Denial of Service attack.
The function DH_check() is itself called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_ex() and EVP_PKEY_param_check().
Also vulnerable are the OpenSSL dhparam and pkeyparam command line applications when using the '-check' option.
The OpenSSL SSL/TLS implementation is not affected by this issue. The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.
Remediation
Upgrade Debian:11 openssl to version 1.1.1v-0~deb11u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-3446
- http://www.openwall.com/lists/oss-security/2023/07/19/4
- http://www.openwall.com/lists/oss-security/2023/07/19/5
- http://www.openwall.com/lists/oss-security/2023/07/19/6
- http://www.openwall.com/lists/oss-security/2023/07/31/1
- http://www.openwall.com/lists/oss-security/2024/05/16/1
- https://lists.debian.org/debian-lts-announce/2023/08/msg00019.html
- https://security.gentoo.org/glsa/202402-08
- https://security.netapp.com/advisory/ntap-20230803-0011/
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=1fa20cf2f506113c761777127a38bce5068740eb
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=8780a896543a654e757db1b9396383f9d8095528
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=9a0a4d3c1e7138915563c0df4fe6a3f9377b839c
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=fc9867c1e03c22ebf56943be205202e576aabf23
- https://www.openssl.org/news/secadv/20230719.txt
- https://cert-portal.siemens.com/productcert/html/ssa-099606.html
- https://cert-portal.siemens.com/productcert/html/ssa-277137.html
- https://cert-portal.siemens.com/productcert/html/ssa-341067.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-556635.html
- https://cert-portal.siemens.com/productcert/html/ssa-769027.html
- https://cert-portal.siemens.com/productcert/html/ssa-794697.html
- https://cert-portal.siemens.com/productcert/html/ssa-915275.html
- https://cert-portal.siemens.com/productcert/html/ssa-943925.html
medium severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
- Fixed in: 1.1.1n-0+deb11u4
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
AES OCB mode for 32-bit x86 platforms using the AES-NI assembly optimised implementation will not encrypt the entirety of the data under some circumstances. This could reveal sixteen bytes of data that was preexisting in the memory that wasn't written. In the special case of "in place" encryption, sixteen bytes of the plaintext would be revealed. Since OpenSSL does not support OCB based cipher suites for TLS and DTLS, they are both unaffected. Fixed in OpenSSL 3.0.5 (Affected 3.0.0-3.0.4). Fixed in OpenSSL 1.1.1q (Affected 1.1.1-1.1.1p).
Remediation
Upgrade Debian:11 openssl to version 1.1.1n-0+deb11u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-2097
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=919925673d6c9cfed3c1085497f5dfbbed5fc431
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=a98f339ddd7e8f487d6e0088d4a9a42324885a93
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/R6CK57NBQFTPUMXAPJURCGXUYT76NQAK/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/V6567JERRHHJW2GNGJGKDRNHR7SNPZK7/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VCMNWKERPBKOEBNL7CLTTX3ZZCZLH7XA/
- https://cert-portal.siemens.com/productcert/pdf/ssa-332410.pdf
- https://git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=919925673d6c9cfed3c1085497f5dfbbed5fc431
- https://git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=a98f339ddd7e8f487d6e0088d4a9a42324885a93
- https://lists.debian.org/debian-lts-announce/2023/02/msg00019.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/R6CK57NBQFTPUMXAPJURCGXUYT76NQAK/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/V6567JERRHHJW2GNGJGKDRNHR7SNPZK7/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VCMNWKERPBKOEBNL7CLTTX3ZZCZLH7XA/
- https://security.gentoo.org/glsa/202210-02
- https://security.netapp.com/advisory/ntap-20220715-0011/
- https://security.netapp.com/advisory/ntap-20230420-0008/
- https://security.netapp.com/advisory/ntap-20240621-0006/
- https://www.debian.org/security/2023/dsa-5343
- https://www.openssl.org/news/secadv/20220705.txt
- https://cert-portal.siemens.com/productcert/html/ssa-332410.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-625862.html
- https://cert-portal.siemens.com/productcert/html/ssa-794697.html
- https://cert-portal.siemens.com/productcert/html/ssa-879734.html
medium severity
- Vulnerable module: util-linux
- Introduced through: util-linux@2.36.1-8+deb11u1, util-linux/bsdutils@1:2.36.1-8+deb11u1 and others
Detailed paths
-
Introduced through: nginx@1.21 › util-linux@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/bsdutils@1:2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/libblkid1@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/libmount1@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/libsmartcols1@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/libuuid1@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/mount@2.36.1-8+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream util-linux package and not the util-linux package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw was found in util-linux. Improper hostname canonicalization in the login(1) utility, when invoked with the -h option, can modify the supplied remote hostname before setting PAM_RHOST. A remote attacker could exploit this by providing a specially crafted hostname, potentially bypassing host-based Pluggable Authentication Modules (PAM) access control rules that rely on fully qualified domain names. This could lead to unauthorized access.
Remediation
There is no fixed version for Debian:11 util-linux.
References
medium severity
- Vulnerable module: util-linux
- Introduced through: util-linux@2.36.1-8+deb11u1, util-linux/bsdutils@1:2.36.1-8+deb11u1 and others
Detailed paths
-
Introduced through: nginx@1.21 › util-linux@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/bsdutils@1:2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/libblkid1@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/libmount1@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/libsmartcols1@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/libuuid1@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/mount@2.36.1-8+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream util-linux package and not the util-linux package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw was found in the libblkid library of util-linux. During nested partition probing, the BSD, Minix, Solaris x86, and UnixWare partition probers cache a raw pointer to a parent partition entry in a dynamically allocated array. When subsequent partition additions cause the array to be reallocated, this pointer becomes stale, leading to a heap use-after-free read. An attacker who can present a crafted block device image (for example, via USB insertion or a loop-mounted disk image) can trigger this flaw without user interaction, as libblkid is invoked automatically by udev/udisks as root on block-device hot-plug events. This could lead to limited information disclosure or denial of service.
Remediation
There is no fixed version for Debian:11 util-linux.
References
- https://security-tracker.debian.org/tracker/CVE-2026-13595
- https://access.redhat.com/errata/RHSA-2026:26573
- https://access.redhat.com/security/cve/CVE-2026-13595
- https://bugzilla.redhat.com/show_bug.cgi?id=2494101
- https://github.com/util-linux/util-linux/commit/c0186f14fbdb02f64c8e0ba701ce727ea764ff4c
medium severity
- Vulnerable module: xz-utils/liblzma5
- Introduced through: xz-utils/liblzma5@5.2.5-2.1~deb11u1
- Fixed in: 5.2.5-2.1~deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › xz-utils/liblzma5@5.2.5-2.1~deb11u1
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:11 relevant fixed versions and status.
XZ Utils provide a general-purpose data-compression library plus command-line tools. Prior to version 5.8.3, if lzma_index_decoder() was used to decode an Index that contained no Records, the resulting lzma_index was left in a state where where a subsequent lzma_index_append() would allocate too little memory, and a buffer overflow would occur. This issue has been patched in version 5.8.3.
Remediation
Upgrade Debian:11 xz-utils to version 5.2.5-2.1~deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-34743
- https://github.com/tukaani-project/xz/commit/c8c22869e780ff57c96b46939c3d79ff99395f87
- https://github.com/tukaani-project/xz/releases/tag/v5.8.3
- https://github.com/tukaani-project/xz/security/advisories/GHSA-x872-m794-cxhv
- http://www.openwall.com/lists/oss-security/2026/03/31/13
- https://lists.debian.org/debian-lts-announce/2026/07/msg00034.html
medium severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@247.3-7 and systemd/libudev1@247.3-7
- Fixed in: 247.3-7+deb11u7
Detailed paths
-
Introduced through: nginx@1.21 › systemd/libsystemd0@247.3-7
-
Introduced through: nginx@1.21 › systemd/libudev1@247.3-7
NVD Description
Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A vulnerability was found in systemd-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:11 systemd to version 247.3-7+deb11u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-4598
- https://access.redhat.com/security/cve/CVE-2025-4598
- https://bugzilla.redhat.com/show_bug.cgi?id=2369242
- https://www.openwall.com/lists/oss-security/2025/05/29/3
- http://www.openwall.com/lists/oss-security/2025/06/05/1
- http://www.openwall.com/lists/oss-security/2025/06/05/3
- https://blogs.oracle.com/linux/post/analysis-of-cve-2025-4598
- https://ciq.com/blog/the-real-danger-of-systemd-coredump-cve-2025-4598/
- https://www.openwall.com/lists/oss-security/2025/08/18/3
- http://seclists.org/fulldisclosure/2025/Jun/9
- https://lists.debian.org/debian-lts-announce/2025/07/msg00022.html
- http://www.openwall.com/lists/oss-security/2025/08/18/3
- https://access.redhat.com/errata/RHSA-2025:22660
- https://access.redhat.com/errata/RHSA-2025:22868
- https://access.redhat.com/errata/RHSA-2025:23234
- https://access.redhat.com/errata/RHSA-2025:23227
- https://access.redhat.com/errata/RHSA-2026:0414
- https://access.redhat.com/errata/RHSA-2026:1652
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://access.redhat.com/errata/RHSA-2026:18153
medium severity
- Vulnerable module: libpng1.6/libpng16-16
- Introduced through: libpng1.6/libpng16-16@1.6.37-3
- Fixed in: 1.6.37-3+deb11u4
Detailed paths
-
Introduced through: nginx@1.21 › libpng1.6/libpng16-16@1.6.37-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From 1.0.9 to before 1.6.57, passing a pointer obtained from png_get_PLTE, png_get_tRNS, or png_get_hIST back into the corresponding setter on the same png_struct/png_info pair causes the setter to read from freed memory and copy its contents into the replacement buffer. The setter frees the internal buffer before copying from the caller-supplied pointer, which now dangles. The freed region may contain stale data (producing silently corrupted chunk metadata) or data from subsequent heap allocations (leaking unrelated heap contents into the chunk struct). This vulnerability is fixed in 1.6.57.
Remediation
Upgrade Debian:11 libpng1.6 to version 1.6.37-3+deb11u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-34757
- https://github.com/pnggroup/libpng/commit/398cbe3df03f4e11bb031e07f416dfdde3684e8a
- https://github.com/pnggroup/libpng/commit/55d20aaa322c9274491cda82c5cd4f99b48c6bcc
- https://github.com/pnggroup/libpng/issues/836
- https://github.com/pnggroup/libpng/issues/837
- https://github.com/pnggroup/libpng/security/advisories/GHSA-6fr7-g8h7-v645
- https://lists.debian.org/debian-lts-announce/2026/05/msg00017.html
medium severity
- Vulnerable module: tar
- Introduced through: tar@1.34+dfsg-1
Detailed paths
-
Introduced through: nginx@1.21 › tar@1.34+dfsg-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tar package and not the tar package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw was found in GNU tar. When extracting an archive with the --one-top-level option, hardlink targets are not confined to the designated top-level directory and may resolve relative to the extraction working directory. A crafted archive can create hardlinks that escape the intended boundary and, when combined with a preexisting symbolic link under the working directory, may allow writing outside that boundary during a single extraction.
Remediation
There is no fixed version for Debian:11 tar.
References
- https://security-tracker.debian.org/tracker/CVE-2026-18508
- https://access.redhat.com/errata/RHSA-2026:50807
- https://access.redhat.com/security/cve/CVE-2026-18508
- https://bugzilla.redhat.com/show_bug.cgi?id=2509843
- https://access.redhat.com/errata/RHSA-2026:61581
- https://access.redhat.com/errata/RHSA-2026:61783
- https://access.redhat.com/errata/RHSA-2026:61586
- https://access.redhat.com/errata/RHSA-2026:66018
- https://access.redhat.com/errata/RHSA-2026:70390
medium severity
- Vulnerable module: tar
- Introduced through: tar@1.34+dfsg-1
Detailed paths
-
Introduced through: nginx@1.21 › tar@1.34+dfsg-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tar package and not the tar package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A TOCTOU (Time-of-Check Time-of-Use) vulnerability in GNU tar's incremental dumpdir 'X' rename handling allows a local attacker with write access to a directory being backed up to influence the restore process if the attacker has access to the system where the restore is being performed. During restoration, files or directories may be created, renamed or overwritten outside the intended extraction directory. This could lead to unauthorized file modification or, in some cases, privilege escalation. Exploitation does not require the attacker to modify or craft the archive, and standard backup and restore workflows—including extracting into a newly created directory without using the -P option do not mitigate the issue.
Remediation
There is no fixed version for Debian:11 tar.
References
- https://security-tracker.debian.org/tracker/CVE-2026-18477
- https://access.redhat.com/errata/RHSA-2026:49361
- https://access.redhat.com/security/cve/CVE-2026-18477
- https://bugzilla.redhat.com/show_bug.cgi?id=2509735
- https://access.redhat.com/errata/RHSA-2026:61581
- https://access.redhat.com/errata/RHSA-2026:61783
- https://access.redhat.com/errata/RHSA-2026:61586
- https://access.redhat.com/errata/RHSA-2026:66018
- https://access.redhat.com/errata/RHSA-2026:70390
medium severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
- Fixed in: 7.74.0-1.3+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A malicious server can serve excessive amounts of Set-Cookie: headers in a HTTP response to curl and curl < 7.84.0 stores all of them. A sufficiently large amount of (big) cookies make subsequent HTTP requests to this, or other servers to which the cookies match, create requests that become larger than the threshold that curl uses internally to avoid sending crazy large requests (1048576 bytes) and instead returns an error.This denial state might remain for as long as the same cookies are kept, match and haven't expired. Due to cookie matching rules, a server on foo.example.com can set cookies that also would match for bar.example.com, making it it possible for a "sister server" to effectively cause a denial of service for a sibling site on the same second level domain using this method.
Remediation
Upgrade Debian:11 curl to version 7.74.0-1.3+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-32205
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BEV6BR4MTI3CEWK2YU2HQZUW5FAS3FEY/
- http://seclists.org/fulldisclosure/2022/Oct/28
- http://seclists.org/fulldisclosure/2022/Oct/41
- https://cert-portal.siemens.com/productcert/pdf/ssa-333517.pdf
- https://hackerone.com/reports/1569946
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BEV6BR4MTI3CEWK2YU2HQZUW5FAS3FEY/
- https://security.gentoo.org/glsa/202212-01
- https://security.netapp.com/advisory/ntap-20220915-0003/
- https://support.apple.com/kb/HT213488
- https://www.debian.org/security/2022/dsa-5197
- https://cert-portal.siemens.com/productcert/html/ssa-333517.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-419740.html
- https://cert-portal.siemens.com/productcert/html/ssa-558014.html
- https://cert-portal.siemens.com/productcert/html/ssa-942865.html
medium severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.1-5
- Fixed in: 3.7.1-5+deb11u9
Detailed paths
-
Introduced through: nginx@1.21 › gnutls28/libgnutls30@3.7.1-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw was found in 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:11 gnutls28 to version 3.7.1-5+deb11u9 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-9820
- https://access.redhat.com/security/cve/CVE-2025-9820
- https://bugzilla.redhat.com/show_bug.cgi?id=2392528
- https://gitlab.com/gnutls/gnutls/-/commit/1d56f96f6ab5034d677136b9d50b5a75dff0faf5
- https://gitlab.com/gnutls/gnutls/-/issues/1732
- https://www.gnutls.org/security-new.html#GNUTLS-SA-2025-11-18
- http://www.openwall.com/lists/oss-security/2025/11/20/2
- https://access.redhat.com/errata/RHSA-2026:3477
- https://access.redhat.com/errata/RHSA-2026:4188
- https://access.redhat.com/errata/RHSA-2026:4655
- https://access.redhat.com/errata/RHSA-2026:4943
- https://access.redhat.com/errata/RHSA-2026:5585
- https://access.redhat.com/errata/RHSA-2026:5606
- https://access.redhat.com/errata/RHSA-2026:7329
- https://access.redhat.com/errata/RHSA-2026:7477
- https://access.redhat.com/errata/RHSA-2026:13812
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
- https://access.redhat.com/errata/RHSA-2026:82347
- https://access.redhat.com/errata/RHSA-2026:82354
- https://access.redhat.com/errata/RHSA-2026:82372
- https://access.redhat.com/errata/RHSA-2026:82857
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › glibc/libc-bin@2.31-13+deb11u3
-
Introduced through: nginx@1.21 › glibc/libc6@2.31-13+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may bypass stack guard protection. The component is: nptl. The attack vector is: Exploit stack buffer overflow vulnerability and use this bypass vulnerability to bypass stack guard. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat.
Remediation
There is no fixed version for Debian:11 glibc.
References
low severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.32.1-4+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › perl/perl-base@5.32.1-4+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Perl versions before 5.40.5-RC1, from 5.41.0 before 5.42.3-RC1, from 5.43.0 before 5.43.11 have a heap buffer overflow when compiling regular expressions with a repeated fixed string on 32-bit builds.
Perl_study_chunk in regcomp_study.c checked the size of the joined substring buffer in characters rather than bytes. For a quantified fixed substring with a large minimum count, the byte length mincount * l could overflow SSize_t, producing an undersized SvGROW allocation; the subsequent copy writes past the end of the buffer.
A caller that compiles an attacker-controlled regular expression on a 32-bit perl build triggers a heap buffer overflow at compile time.
Remediation
There is no fixed version for Debian:11 perl.
References
low severity
- Vulnerable module: tar
- Introduced through: tar@1.34+dfsg-1
Detailed paths
-
Introduced through: nginx@1.21 › tar@1.34+dfsg-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tar package and not the tar package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Tar 1.15.1 does not properly warn the user when extracting setuid or setgid files, which may allow local users or remote attackers to gain privileges.
Remediation
There is no fixed version for Debian:11 tar.
References
- 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: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › glibc/libc-bin@2.31-13+deb11u3
-
Introduced through: nginx@1.21 › glibc/libc6@2.31-13+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
GNU Libc current is affected by: Re-mapping current loaded library with malicious ELF file. The impact is: In worst case attacker may evaluate privileges. The component is: libld. The attack vector is: Attacker sends 2 ELF files to victim and asks to run ldd on it. ldd execute code. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat.
Remediation
There is no fixed version for Debian:11 glibc.
References
- 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
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
low severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.32.1-4+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › perl/perl-base@5.32.1-4+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
HTTP::Tiny before 0.083, a Perl core module since 5.13.9 and available standalone on CPAN, has an insecure default TLS configuration where users must opt in to verify certificates.
Remediation
There is no fixed version for Debian:11 perl.
References
- https://security-tracker.debian.org/tracker/CVE-2023-31486
- https://security.netapp.com/advisory/ntap-20241129-0011/
- http://www.openwall.com/lists/oss-security/2023/04/29/1
- http://www.openwall.com/lists/oss-security/2023/05/03/3
- http://www.openwall.com/lists/oss-security/2023/05/03/5
- http://www.openwall.com/lists/oss-security/2023/05/07/2
- https://blog.hackeriet.no/perl-http-tiny-insecure-tls-default-affects-cpan-modules/
- https://github.com/chansen/p5-http-tiny/pull/153
- https://hackeriet.github.io/cpan-http-tiny-overview/
- https://www.openwall.com/lists/oss-security/2023/04/18/14
- https://www.openwall.com/lists/oss-security/2023/05/03/4
- https://www.reddit.com/r/perl/comments/111tadi/psa_httptiny_disabled_ssl_verification_by_default/
low severity
- Vulnerable module: bash/bash
- Introduced through: bash/bash@5.1-2+b3
Detailed paths
-
Introduced through: nginx@1.21 › bash/bash@5.1-2+b3
NVD Description
Note: Versions mentioned in the description apply only to the upstream bash package and not the bash package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw was found in the bash package, where a heap-buffer overflow can occur in valid parameter_transform. This issue may lead to memory problems.
Remediation
There is no fixed version for Debian:11 bash.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.10-2+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › expat/libexpat1@2.2.10-2+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
In libexpat before 2.7.4, the doContent function does not properly determine the buffer size bufSize because there is no integer overflow check for tag buffer reallocation.
Remediation
There is no fixed version for Debian:11 expat.
References
low severity
- Vulnerable module: freetype/libfreetype6
- Introduced through: freetype/libfreetype6@2.10.4+dfsg-1
Detailed paths
-
Introduced through: nginx@1.21 › freetype/libfreetype6@2.10.4+dfsg-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream freetype package and not the freetype package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
ftbench.c in FreeType Demo Programs through 2.12.1 has a heap-based buffer overflow.
Remediation
There is no fixed version for Debian:11 freetype.
References
low severity
- Vulnerable module: ncurses/libtinfo6
- Introduced through: ncurses/libtinfo6@6.2+20201114-2, ncurses/ncurses-base@6.2+20201114-2 and others
Detailed paths
-
Introduced through: nginx@1.21 › ncurses/libtinfo6@6.2+20201114-2
-
Introduced through: nginx@1.21 › ncurses/ncurses-base@6.2+20201114-2
-
Introduced through: nginx@1.21 › ncurses/ncurses-bin@6.2+20201114-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
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:11 ncurses.
References
- https://security-tracker.debian.org/tracker/CVE-2025-69720
- https://github.com/Cao-Wuhui/CVE-2025-69720
- https://invisible-island.net/archives/ncurses/6.5/
- https://invisible-island.net/ncurses/
- https://marc.info/?l=ncurses-bug&m=176539968328570&w=2
- https://marc.info/?l=ncurses-bug&m=176540731801330&w=2
- https://marc.info/?l=ncurses-bug&m=176545557728083&w=2
- https://cert-portal.siemens.com/productcert/html/ssa-253495.html
low severity
- Vulnerable module: pcre3/libpcre3
- Introduced through: pcre3/libpcre3@2:8.39-13
Detailed paths
-
Introduced through: nginx@1.21 › pcre3/libpcre3@2:8.39-13
NVD Description
Note: Versions mentioned in the description apply only to the upstream pcre3 package and not the pcre3 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Stack-based buffer overflow in the pcre32_copy_substring function in pcre_get.c in libpcre1 in PCRE 8.40 allows remote attackers to cause a denial of service (WRITE of size 4) or possibly have unspecified other impact via a crafted file.
Remediation
There is no fixed version for Debian:11 pcre3.
References
- https://security-tracker.debian.org/tracker/CVE-2017-7245
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7245
- https://security.gentoo.org/glsa/201710-25
- https://blogs.gentoo.org/ago/2017/03/20/libpcre-two-stack-based-buffer-overflow-write-in-pcre32_copy_substring-pcre_get-c/
- https://access.redhat.com/errata/RHSA-2018:2486
- http://www.securityfocus.com/bid/97067
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2017-7245
low severity
- Vulnerable module: pcre3/libpcre3
- Introduced through: pcre3/libpcre3@2:8.39-13
Detailed paths
-
Introduced through: nginx@1.21 › pcre3/libpcre3@2:8.39-13
NVD Description
Note: Versions mentioned in the description apply only to the upstream pcre3 package and not the pcre3 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Stack-based buffer overflow in the pcre32_copy_substring function in pcre_get.c in libpcre1 in PCRE 8.40 allows remote attackers to cause a denial of service (WRITE of size 268) or possibly have unspecified other impact via a crafted file.
Remediation
There is no fixed version for Debian:11 pcre3.
References
- https://security-tracker.debian.org/tracker/CVE-2017-7246
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7246
- https://security.gentoo.org/glsa/201710-25
- https://blogs.gentoo.org/ago/2017/03/20/libpcre-two-stack-based-buffer-overflow-write-in-pcre32_copy_substring-pcre_get-c/
- https://access.redhat.com/errata/RHSA-2018:2486
- http://www.securityfocus.com/bid/97067
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2017-7246
low severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A vulnerability was found in LibTIFF up to 4.7.0. It has been declared as critical. This vulnerability affects the function get_histogram of the file tools/tiffmedian.c. The manipulation leads to use after free. The attack needs to be approached locally. The exploit has been disclosed to the public and may be used. The patch is identified as fe10872e53efba9cc36c66ac4ab3b41a839d5172. It is recommended to apply a patch to fix this issue.
Remediation
There is no fixed version for Debian:11 tiff.
References
- https://security-tracker.debian.org/tracker/CVE-2025-8176
- http://www.libtiff.org/
- https://gitlab.com/libtiff/libtiff/-/commit/fe10872e53efba9cc36c66ac4ab3b41a839d5172
- https://gitlab.com/libtiff/libtiff/-/issues/707
- https://gitlab.com/libtiff/libtiff/-/merge_requests/727
- https://vuldb.com/?ctiid.317590
- https://vuldb.com/?id.317590
- https://vuldb.com/?submit.621796
low severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A vulnerability was found in LibTIFF up to 4.7.0. It has been rated as critical. This issue affects the function setrow of the file tools/thumbnail.c. The manipulation leads to buffer overflow. An attack has to be approached locally. The patch is named e8c9d6c616b19438695fd829e58ae4fde5bfbc22. It is recommended to apply a patch to fix this issue. This vulnerability only affects products that are no longer supported by the maintainer.
Remediation
There is no fixed version for Debian:11 tiff.
References
- https://security-tracker.debian.org/tracker/CVE-2025-8177
- http://www.libtiff.org/
- https://gitlab.com/libtiff/libtiff/-/commit/e8c9d6c616b19438695fd829e58ae4fde5bfbc22
- https://gitlab.com/libtiff/libtiff/-/merge_requests/737
- https://vuldb.com/?ctiid.317591
- https://vuldb.com/?id.317591
- https://gitlab.com/libtiff/libtiff/-/issues/715
- https://vuldb.com/?submit.621797
low severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Using libcurl, when a custom Host: header is first set for an HTTP request
and a second request is subsequently done using the same easy handle but
without the custom Host: header set, the second request would use stale
information and pass on cookies meant for the first host in the second
request. Leak them.
Remediation
There is no fixed version for Debian:11 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libcurl might in some circumstances reuse the wrong connection for SMB(S) transfers.
libcurl features a pool of recent connections so that subsequent requests can reuse an existing connection to avoid overhead.
When reusing a connection a range of criteria must be met. Due to a logical error in the code, a network transfer operation that was requested by an application could wrongfully reuse an existing SMB connection to the same server that was using a different "share" than the new subsequent transfer should.
This could in unlucky situations lead to the download of the wrong file or the upload of a file to the wrong place. When this happens, the same credentials are used and the server name is the same.
Remediation
There is no fixed version for Debian:11 curl.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.10-2+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › expat/libexpat1@2.2.10-2+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libexpat through 2.6.1 allows an XML Entity Expansion attack when there is isolated use of external parsers (created via XML_ExternalEntityParserCreate).
Remediation
There is no fixed version for Debian:11 expat.
References
- https://security-tracker.debian.org/tracker/CVE-2024-28757
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/FPLC6WDSRDUYS7F7JWAOVOHFNOUQ43DD/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VK2O34GH43NTHBZBN7G5Y6YKJKPUCTBE/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LKJ7V5F6LJCEQJXDBWGT27J7NAP3E3N7/
- http://www.openwall.com/lists/oss-security/2024/03/15/1
- https://github.com/libexpat/libexpat/issues/839
- https://github.com/libexpat/libexpat/pull/842
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FPLC6WDSRDUYS7F7JWAOVOHFNOUQ43DD/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LKJ7V5F6LJCEQJXDBWGT27J7NAP3E3N7/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VK2O34GH43NTHBZBN7G5Y6YKJKPUCTBE/
- https://security.netapp.com/advisory/ntap-20240322-0001/
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-784301.html
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.10-2+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › expat/libexpat1@2.2.10-2+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A stack overflow vulnerability exists in the libexpat library due to the way it handles recursive entity expansion in XML documents. When parsing an XML document with deeply nested entity references, libexpat can be forced to recurse indefinitely, exhausting the stack space and causing a crash. This issue could lead to denial of service (DoS) or, in some cases, exploitable memory corruption, depending on the environment and library usage.
Remediation
There is no fixed version for Debian:11 expat.
References
- https://security-tracker.debian.org/tracker/CVE-2024-8176
- https://access.redhat.com/security/cve/CVE-2024-8176
- https://bugzilla.redhat.com/show_bug.cgi?id=2310137
- https://github.com/libexpat/libexpat/issues/893
- http://www.openwall.com/lists/oss-security/2025/03/15/1
- https://blog.hartwork.org/posts/expat-2-7-0-released/
- https://bugzilla.suse.com/show_bug.cgi?id=1239618
- https://github.com/libexpat/libexpat/blob/R_2_7_0/expat/Changes#L40-L52
- https://gitlab.alpinelinux.org/alpine/aports/-/commit/d068c3ff36fc6f4789988a09c69b434db757db53
- https://ubuntu.com/security/CVE-2024-8176
- https://security.netapp.com/advisory/ntap-20250328-0009/
- https://access.redhat.com/errata/RHSA-2025:3531
- https://access.redhat.com/errata/RHSA-2025:3734
- https://access.redhat.com/errata/RHSA-2025:3913
- https://access.redhat.com/errata/RHSA-2025:4048
- https://access.redhat.com/errata/RHSA-2025:4447
- https://access.redhat.com/errata/RHSA-2025:4446
- https://access.redhat.com/errata/RHSA-2025:4448
- https://access.redhat.com/errata/RHSA-2025:4449
- https://www.kb.cert.org/vuls/id/760160
- https://access.redhat.com/errata/RHSA-2025:7444
- https://access.redhat.com/errata/RHSA-2025:7512
- https://access.redhat.com/errata/RHSA-2025:8385
- https://access.redhat.com/errata/RHSA-2025:13681
- http://seclists.org/fulldisclosure/2025/May/10
- http://seclists.org/fulldisclosure/2025/May/11
- http://seclists.org/fulldisclosure/2025/May/12
- http://seclists.org/fulldisclosure/2025/May/6
- http://seclists.org/fulldisclosure/2025/May/7
- http://seclists.org/fulldisclosure/2025/May/8
- http://www.openwall.com/lists/oss-security/2025/09/24/11
- https://access.redhat.com/errata/RHSA-2025:22033
- https://access.redhat.com/errata/RHSA-2025:22035
- https://access.redhat.com/errata/RHSA-2025:22034
- https://access.redhat.com/errata/RHSA-2025:22607
- https://access.redhat.com/errata/RHSA-2025:22785
- https://access.redhat.com/errata/RHSA-2025:22842
- https://access.redhat.com/errata/RHSA-2025:22871
- https://github.com/libexpat/libexpat/pull/973
- https://cert-portal.siemens.com/productcert/html/ssa-355557.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › glibc/libc-bin@2.31-13+deb11u3
-
Introduced through: nginx@1.21 › glibc/libc6@2.31-13+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
In the GNU C Library (aka glibc or libc6) through 2.29, check_dst_limits_calc_pos_1 in posix/regexec.c has Uncontrolled Recursion, as demonstrated by '(|)(\1\1)*' in grep, a different issue than CVE-2018-20796. NOTE: the software maintainer disputes that this is a vulnerability because the behavior occurs only with a crafted pattern
Remediation
There is no fixed version for Debian:11 glibc.
References
- 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: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › glibc/libc-bin@2.31-13+deb11u3
-
Introduced through: nginx@1.21 › glibc/libc6@2.31-13+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
In the GNU C Library (aka glibc or libc6) through 2.29, check_dst_limits_calc_pos_1 in posix/regexec.c has Uncontrolled Recursion, as demonstrated by '(\227|)(\1\1|t1|\\2537)+' in grep.
Remediation
There is no fixed version for Debian:11 glibc.
References
- 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: gzip
- Introduced through: gzip@1.10-4+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › gzip@1.10-4+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream gzip package and not the gzip package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
GNU gzip contains a global buffer overflow vulnerability in the LZH decompression logic caused by improper reuse of shared global state between different decompression formats within a single execution. GNU gzip maintains a global array that is shared across the LZ77, LZW, and LZH decompression routines and is not reinitialized between files processed in the same invocation. By decompressing a specially crafted LZW file followed by a specially crafted LZH file in a single gzip -d command, an attacker can poison the shared global state and subsequently trigger an out‑of‑bounds read in the LZH decoder. The LZH decompression logic follows stale values left in the shared array, causing reads past the end of the allocated global buffer.
This issue has been fixed in commits 63dbf6b3b9e6e781df1a6a64e609b10e23969681 and e7378c2d421be6a286922374425680bbe9ad8b7d.
Remediation
There is no fixed version for Debian:11 gzip.
References
- https://security-tracker.debian.org/tracker/CVE-2026-41992
- https://cert.pl/en/posts/2026/04/CVE-2026-41991/
- https://cgit.git.savannah.gnu.org/cgit/gzip.git/commit/?id=63dbf6b3b9e6e781df1a6a64e609b10e23969681
- https://www.gnu.org/software/gzip/
- http://www.openwall.com/lists/oss-security/2026/08/23/1
- http://www.openwall.com/lists/oss-security/2026/08/25/1
- http://www.openwall.com/lists/oss-security/2026/08/27/2
- https://cgit.git.savannah.gnu.org/cgit/gzip.git/commit/?id=e7378c2d421be6a286922374425680bbe9ad8b7d
low severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.18.3-6+deb11u1, krb5/libk5crypto3@1.18.3-6+deb11u1 and others
Detailed paths
-
Introduced through: nginx@1.21 › krb5/libgssapi-krb5-2@1.18.3-6+deb11u1
-
Introduced through: nginx@1.21 › krb5/libk5crypto3@1.18.3-6+deb11u1
-
Introduced through: nginx@1.21 › krb5/libkrb5-3@1.18.3-6+deb11u1
-
Introduced through: nginx@1.21 › krb5/libkrb5support0@1.18.3-6+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
An issue was discovered in MIT Kerberos 5 (aka krb5) through 1.16. There is a variable "dbentry->n_key_data" in kadmin/dbutil/dump.c that can store 16-bit data but unknowingly the developer has assigned a "u4" variable to it, which is for 32-bit data. An attacker can use this vulnerability to affect other artifacts of the database as we know that a Kerberos database dump file contains trusted data.
Remediation
There is no fixed version for Debian:11 krb5.
References
- 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.8.7-6
Detailed paths
-
Introduced through: nginx@1.21 › libgcrypt20@1.8.7-6
NVD Description
Note: Versions mentioned in the description apply only to the upstream libgcrypt20 package and not the libgcrypt20 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Libgcrypt before 1.8.8 and 1.9.x before 1.9.3 mishandles ElGamal encryption because it lacks exponent blinding to address a side-channel attack against mpi_powm, and the window size is not chosen appropriately. This, for example, affects use of ElGamal in OpenPGP.
Remediation
There is no fixed version for Debian:11 libgcrypt20.
References
- https://security-tracker.debian.org/tracker/CVE-2021-33560
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BKKTOIGFW2SGN3DO2UHHVZ7MJSYN4AAB/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/R7OAPCUGPF3VLA7QAJUQSL255D4ITVTL/
- https://dev.gnupg.org/rCe8b7f10be275bcedb5fc05ed4837a89bfd605c61
- https://dev.gnupg.org/T5305
- https://dev.gnupg.org/T5328
- https://dev.gnupg.org/T5466
- https://www.oracle.com/security-alerts/cpuoct2021.html
- https://lists.debian.org/debian-lts-announce/2021/06/msg00021.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BKKTOIGFW2SGN3DO2UHHVZ7MJSYN4AAB/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/R7OAPCUGPF3VLA7QAJUQSL255D4ITVTL/
- https://security.gentoo.org/glsa/202210-13
- https://www.oracle.com/security-alerts/cpuapr2022.html
- https://www.oracle.com/security-alerts/cpujan2022.html
- https://www.oracle.com/security-alerts/cpujul2022.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
low severity
- Vulnerable module: libgcrypt20
- Introduced through: libgcrypt20@1.8.7-6
Detailed paths
-
Introduced through: nginx@1.21 › libgcrypt20@1.8.7-6
NVD Description
Note: Versions mentioned in the description apply only to the upstream libgcrypt20 package and not the libgcrypt20 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
cipher/elgamal.c in Libgcrypt through 1.8.2, when used to encrypt messages directly, improperly encodes plaintexts, which allows attackers to obtain sensitive information by reading ciphertext data (i.e., it does not have semantic security in face of a ciphertext-only attack). The Decisional Diffie-Hellman (DDH) assumption does not hold for Libgcrypt's ElGamal implementation.
Remediation
There is no fixed version for Debian:11 libgcrypt20.
References
- 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: libzstd/libzstd1
- Introduced through: libzstd/libzstd1@1.4.8+dfsg-2.1
Detailed paths
-
Introduced through: nginx@1.21 › libzstd/libzstd1@1.4.8+dfsg-2.1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libzstd package and not the libzstd package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A vulnerability was found in zstd v1.4.10, where an attacker can supply empty string as an argument to the command line tool to cause buffer overrun.
Remediation
There is no fixed version for Debian:11 libzstd.
References
- https://security-tracker.debian.org/tracker/CVE-2022-4899
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/C63HAGVLQA6FJNDCHR7CNZZL6VSLILB2/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JEHRBBYYTPA4DETOM5XAKGCP37NUTLOA/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QYLDK6ODVC4LJSDULLX6Q2YHTFOWABCN/
- https://github.com/facebook/zstd/issues/3200
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/C63HAGVLQA6FJNDCHR7CNZZL6VSLILB2/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/JEHRBBYYTPA4DETOM5XAKGCP37NUTLOA/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/QYLDK6ODVC4LJSDULLX6Q2YHTFOWABCN/
- https://security.netapp.com/advisory/ntap-20230725-0005/
low severity
- Vulnerable module: nginx
- Introduced through: nginx@1.21.6-1~bullseye
Detailed paths
-
Introduced through: nginx@1.21 › nginx@1.21.6-1~bullseye
NVD Description
Note: Versions mentioned in the description apply only to the upstream nginx package and not the nginx package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.
Remediation
There is no fixed version for Debian:11 nginx.
References
- https://security-tracker.debian.org/tracker/CVE-2023-44487
- https://chaos.social/@icing/111210915918780532
- https://github.com/hyperium/hyper/issues/3337
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/2MBEPPC36UBVOZZNAXFHKLFGSLCMN5LI/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/3N4NJ7FR4X4FPZUGNTQAPSTVB2HB2Y4A/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BFQD3KUEMFBHPAPBGLWQC34L4OWL5HAZ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/CLB4TW7KALB3EEQWNWCN7OUIWWVWWCG2/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/E72T67UPDRXHIDLO3OROR25YAMN4GGW5/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FNA62Q767CFAFHBCDKYNPBMZWB7TWYVU/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HT7T2R4MQKLIF4ODV4BDLPARWFPCJ5CZ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/JIZSEFC3YKCGABA2BZW6ZJRMDZJMB7PJ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/JMEXY22BFG5Q64HQCM5CK2Q7KDKVV4TY/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/KSEGD2IWKNUO3DWY4KQGUQM5BISRWHQE/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LKYHSZQFDNR7RSA7LHVLLIAQMVYCUGBG/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LNMZJCDHGLJJLXO4OXWJMTVQRNWOC7UL/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VHUHTSXLXGXS7JYKBXTA3VINUPHTNGVU/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VSRDIV77HNKUSM7SJC5BKE5JSHLHU2NK/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WE2I52RHNNU42PX6NZ2RBUHSFFJ2LVZX/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WLPRQ5TWUQQXYWBJM7ECYDAIL2YVKIUH/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/X6QXN4ORIVF6XBW4WWFE7VNPVC74S45Y/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/XFOIBB4YFICHDM7IBOP7PWXW3FX4HLL2/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZB43REMKRQR62NJEI7I5NQ4FSXNLBKRT/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZKQSIKIAT5TJ3WSLU3RDBQ35YX4GY4V3/
- https://www.vicarius.io/vsociety/posts/rapid-reset-cve-2023-44487-dos-in-http2-understanding-the-root-cause
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZLU6U2R2IC2K64NDPNMV55AUAO65MAF4/
- http://www.openwall.com/lists/oss-security/2023/10/10/6
- http://www.openwall.com/lists/oss-security/2023/10/10/7
- https://github.com/grpc/grpc/releases/tag/v1.59.2
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/2MBEPPC36UBVOZZNAXFHKLFGSLCMN5LI/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3N4NJ7FR4X4FPZUGNTQAPSTVB2HB2Y4A/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BFQD3KUEMFBHPAPBGLWQC34L4OWL5HAZ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/CLB4TW7KALB3EEQWNWCN7OUIWWVWWCG2/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/E72T67UPDRXHIDLO3OROR25YAMN4GGW5/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/FNA62Q767CFAFHBCDKYNPBMZWB7TWYVU/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HT7T2R4MQKLIF4ODV4BDLPARWFPCJ5CZ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JIZSEFC3YKCGABA2BZW6ZJRMDZJMB7PJ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JMEXY22BFG5Q64HQCM5CK2Q7KDKVV4TY/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KSEGD2IWKNUO3DWY4KQGUQM5BISRWHQE/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LKYHSZQFDNR7RSA7LHVLLIAQMVYCUGBG/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LNMZJCDHGLJJLXO4OXWJMTVQRNWOC7UL/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VHUHTSXLXGXS7JYKBXTA3VINUPHTNGVU/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VSRDIV77HNKUSM7SJC5BKE5JSHLHU2NK/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WE2I52RHNNU42PX6NZ2RBUHSFFJ2LVZX/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WLPRQ5TWUQQXYWBJM7ECYDAIL2YVKIUH/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/X6QXN4ORIVF6XBW4WWFE7VNPVC74S45Y/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XFOIBB4YFICHDM7IBOP7PWXW3FX4HLL2/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZB43REMKRQR62NJEI7I5NQ4FSXNLBKRT/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZKQSIKIAT5TJ3WSLU3RDBQ35YX4GY4V3/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZLU6U2R2IC2K64NDPNMV55AUAO65MAF4/
- https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-http2-reset-d8Kf32vZ
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-44487
- http://www.openwall.com/lists/oss-security/2025/08/13/6
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-341067.html
- https://cert-portal.siemens.com/productcert/html/ssa-784301.html
- https://cert-portal.siemens.com/productcert/html/ssa-832273.html
- https://cert-portal.siemens.com/productcert/html/ssa-915275.html
- http://www.openwall.com/lists/oss-security/2023/10/13/4
- http://www.openwall.com/lists/oss-security/2023/10/13/9
- http://www.openwall.com/lists/oss-security/2023/10/18/4
- http://www.openwall.com/lists/oss-security/2023/10/18/8
- http://www.openwall.com/lists/oss-security/2023/10/19/6
- http://www.openwall.com/lists/oss-security/2023/10/20/8
- https://access.redhat.com/security/cve/cve-2023-44487
- https://arstechnica.com/security/2023/10/how-ddosers-used-the-http-2-protocol-to-deliver-attacks-of-unprecedented-size/
- https://aws.amazon.com/security/security-bulletins/AWS-2023-011/
- https://blog.cloudflare.com/technical-breakdown-http2-rapid-reset-ddos-attack/
- https://blog.cloudflare.com/zero-day-rapid-reset-http2-record-breaking-ddos-attack/
- https://blog.litespeedtech.com/2023/10/11/rapid-reset-http-2-vulnerablilty/
- https://blog.qualys.com/vulnerabilities-threat-research/2023/10/10/cve-2023-44487-http-2-rapid-reset-attack
- https://blog.vespa.ai/cve-2023-44487/
- https://bugzilla.proxmox.com/show_bug.cgi?id=4988
- https://bugzilla.redhat.com/show_bug.cgi?id=2242803
- https://bugzilla.suse.com/show_bug.cgi?id=1216123
- https://cgit.freebsd.org/ports/commit/?id=c64c329c2c1752f46b73e3e6ce9f4329be6629f9
- https://cloud.google.com/blog/products/identity-security/google-cloud-mitigated-largest-ddos-attack-peaking-above-398-million-rps/
- https://cloud.google.com/blog/products/identity-security/how-it-works-the-novel-http2-rapid-reset-ddos-attack
- https://community.traefik.io/t/is-traefik-vulnerable-to-cve-2023-44487/20125
- https://discuss.hashicorp.com/t/hcsec-2023-32-vault-consul-and-boundary-affected-by-http-2-rapid-reset-denial-of-service-vulnerability-cve-2023-44487/59715
- https://edg.io/lp/blog/resets-leaks-ddos-and-the-tale-of-a-hidden-cve
- https://forums.swift.org/t/swift-nio-http2-security-update-cve-2023-44487-http-2-dos/67764
- https://gist.github.com/adulau/7c2bfb8e9cdbe4b35a5e131c66a0c088
- https://github.com/Azure/AKS/issues/3947
- https://github.com/Kong/kong/discussions/11741
- https://github.com/advisories/GHSA-qppj-fm5r-hxr3
- https://github.com/advisories/GHSA-vx74-f528-fxqg
- https://github.com/advisories/GHSA-xpw8-rcwv-8f8p
- https://github.com/akka/akka-http/issues/4323
- https://github.com/alibaba/tengine/issues/1872
- https://github.com/apache/apisix/issues/10320
- https://github.com/apache/httpd-site/pull/10
- https://github.com/apache/httpd/blob/afcdbeebbff4b0c50ea26cdd16e178c0d1f24152/modules/http2/h2_mplx.c#L1101-L1113
- https://github.com/apache/tomcat/tree/main/java/org/apache/coyote/http2
- https://github.com/apache/trafficserver/pull/10564
- https://github.com/arkrwn/PoC/tree/main/CVE-2023-44487
- https://github.com/bcdannyboy/CVE-2023-44487
- https://github.com/caddyserver/caddy/issues/5877
- https://github.com/caddyserver/caddy/releases/tag/v2.7.5
- https://github.com/dotnet/announcements/issues/277
- https://github.com/dotnet/core/blob/e4613450ea0da7fd2fc6b61dfb2c1c1dec1ce9ec/release-notes/6.0/6.0.23/6.0.23.md?plain=1#L73
- https://github.com/eclipse/jetty.project/issues/10679
- https://github.com/envoyproxy/envoy/pull/30055
- https://github.com/etcd-io/etcd/issues/16740
- https://github.com/facebook/proxygen/pull/466
- https://github.com/golang/go/issues/63417
- https://github.com/grpc/grpc-go/pull/6703
- https://github.com/h2o/h2o/pull/3291
- https://github.com/h2o/h2o/security/advisories/GHSA-2m7v-gc89-fjqf
- https://github.com/haproxy/haproxy/issues/2312
- https://github.com/icing/mod_h2/blob/0a864782af0a942aa2ad4ed960a6b32cd35bcf0a/mod_http2/README.md?plain=1#L239-L244
- https://github.com/junkurihara/rust-rpxy/issues/97
- https://github.com/kazu-yamamoto/http2/commit/f61d41a502bd0f60eb24e1ce14edc7b6df6722a1
- https://github.com/kazu-yamamoto/http2/issues/93
- https://github.com/kubernetes/kubernetes/pull/121120
- https://github.com/line/armeria/pull/5232
- https://github.com/linkerd/website/pull/1695/commits/4b9c6836471bc8270ab48aae6fd2181bc73fd632
- https://github.com/micrictor/http2-rst-stream
- https://github.com/microsoft/CBL-Mariner/pull/6381
- https://github.com/netty/netty/commit/58f75f665aa81a8cbcf6ffa74820042a285c5e61
- https://github.com/nghttp2/nghttp2/pull/1961
- https://github.com/nghttp2/nghttp2/releases/tag/v1.57.0
- https://github.com/ninenines/cowboy/issues/1615
- https://github.com/nodejs/node/pull/50121
- https://github.com/openresty/openresty/issues/930
- https://github.com/opensearch-project/data-prepper/issues/3474
- https://github.com/oqtane/oqtane.framework/discussions/3367
- https://github.com/projectcontour/contour/pull/5826
- https://github.com/tempesta-tech/tempesta/issues/1986
- https://github.com/varnishcache/varnish-cache/issues/3996
- https://groups.google.com/g/golang-announce/c/iNNxDTCjZvo
- https://istio.io/latest/news/security/istio-security-2023-004/
- https://linkerd.io/2023/10/12/linkerd-cve-2023-44487/
- https://lists.apache.org/thread/5py8h42mxfsn8l1wy6o41xwhsjlsd87q
- https://lists.debian.org/debian-lts-announce/2023/10/msg00020.html
- https://lists.debian.org/debian-lts-announce/2023/10/msg00023.html
- https://lists.debian.org/debian-lts-announce/2023/10/msg00024.html
- https://lists.debian.org/debian-lts-announce/2023/10/msg00045.html
- https://lists.debian.org/debian-lts-announce/2023/10/msg00047.html
- https://lists.debian.org/debian-lts-announce/2023/11/msg00001.html
- https://lists.debian.org/debian-lts-announce/2023/11/msg00012.html
- https://lists.w3.org/Archives/Public/ietf-http-wg/2023OctDec/0025.html
- https://mailman.nginx.org/pipermail/nginx-devel/2023-October/S36Q5HBXR7CAIMPLLPRSSSYR4PCMWILK.html
- https://martinthomson.github.io/h2-stream-limits/draft-thomson-httpbis-h2-stream-limits.html
- https://msrc.microsoft.com/blog/2023/10/microsoft-response-to-distributed-denial-of-service-ddos-attacks-against-http/2/
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-44487
- https://my.f5.com/manage/s/article/K000137106
- https://netty.io/news/2023/10/10/4-1-100-Final.html
- https://news.ycombinator.com/item?id=37830987
- https://news.ycombinator.com/item?id=37830998
- https://news.ycombinator.com/item?id=37831062
- https://news.ycombinator.com/item?id=37837043
- https://openssf.org/blog/2023/10/10/http-2-rapid-reset-vulnerability-highlights-need-for-rapid-response/
- https://seanmonstar.com/post/730794151136935936/hyper-http2-rapid-reset-unaffected
- https://security.gentoo.org/glsa/202311-09
- https://security.netapp.com/advisory/ntap-20231016-0001/
- https://security.netapp.com/advisory/ntap-20240426-0007/
- https://security.netapp.com/advisory/ntap-20240621-0006/
- https://security.netapp.com/advisory/ntap-20240621-0007/
- https://security.paloaltonetworks.com/CVE-2023-44487
- https://tomcat.apache.org/security-10.html#Fixed_in_Apache_Tomcat_10.1.14
- https://ubuntu.com/security/CVE-2023-44487
- https://www.bleepingcomputer.com/news/security/new-http-2-rapid-reset-zero-day-attack-breaks-ddos-records/
- https://www.cisa.gov/news-events/alerts/2023/10/10/http2-rapid-reset-vulnerability-cve-2023-44487
- https://www.darkreading.com/cloud/internet-wide-zero-day-bug-fuels-largest-ever-ddos-event
- https://www.debian.org/security/2023/dsa-5521
- https://www.debian.org/security/2023/dsa-5522
- https://www.debian.org/security/2023/dsa-5540
- https://www.debian.org/security/2023/dsa-5549
- https://www.debian.org/security/2023/dsa-5558
- https://www.debian.org/security/2023/dsa-5570
- https://www.haproxy.com/blog/haproxy-is-not-affected-by-the-http-2-rapid-reset-attack-cve-2023-44487
- https://www.netlify.com/blog/netlify-successfully-mitigates-cve-2023-44487/
- https://www.nginx.com/blog/http-2-rapid-reset-attack-impacting-f5-nginx-products/
- https://www.openwall.com/lists/oss-security/2023/10/10/6
- https://www.phoronix.com/news/HTTP2-Rapid-Reset-Attack
- https://www.theregister.com/2023/10/10/http2_rapid_reset_zeroday/
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- https://github.com/threatlabindonesia/CVE-2023-44487-HTTP-2-Rapid-Reset-Exploit-PoC
- https://www.exploit-db.com/exploits/52426
low severity
- Vulnerable module: openldap/libldap-2.4-2
- Introduced through: openldap/libldap-2.4-2@2.4.57+dfsg-3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › openldap/libldap-2.4-2@2.4.57+dfsg-3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
The nss_parse_ciphers function in libraries/libldap/tls_m.c in OpenLDAP does not properly parse OpenSSL-style multi-keyword mode cipher strings, which might cause a weaker than intended cipher to be used and allow remote attackers to have unspecified impact via unknown vectors.
Remediation
There is no fixed version for Debian:11 openldap.
References
- 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.4-2
- Introduced through: openldap/libldap-2.4-2@2.4.57+dfsg-3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › openldap/libldap-2.4-2@2.4.57+dfsg-3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A vulnerability was found in openldap. This security flaw causes a null pointer dereference in ber_memalloc_x() function.
Remediation
There is no fixed version for Debian:11 openldap.
References
- 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
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-806742.html
low severity
- Vulnerable module: openldap/libldap-2.4-2
- Introduced through: openldap/libldap-2.4-2@2.4.57+dfsg-3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › openldap/libldap-2.4-2@2.4.57+dfsg-3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
contrib/slapd-modules/nops/nops.c in OpenLDAP through 2.4.45, when both the nops module and the memberof overlay are enabled, attempts to free a buffer that was allocated on the stack, which allows remote attackers to cause a denial of service (slapd crash) via a member MODDN operation.
Remediation
There is no fixed version for Debian:11 openldap.
References
- 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: pcre2/libpcre2-8-0
- Introduced through: pcre2/libpcre2-8-0@10.36-2
Detailed paths
-
Introduced through: nginx@1.21 › pcre2/libpcre2-8-0@10.36-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream pcre2 package and not the pcre2 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Integer overflow vulnerability in pcre2test before 10.41 allows attackers to cause a denial of service or other unspecified impacts via negative input.
Remediation
There is no fixed version for Debian:11 pcre2.
References
low severity
- Vulnerable module: pcre3/libpcre3
- Introduced through: pcre3/libpcre3@2:8.39-13
Detailed paths
-
Introduced through: nginx@1.21 › pcre3/libpcre3@2:8.39-13
NVD Description
Note: Versions mentioned in the description apply only to the upstream pcre3 package and not the pcre3 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libpcre in PCRE before 8.43 allows a subject buffer over-read in JIT when UTF is disabled, and \X or \R has more than one fixed quantifier, a related issue to CVE-2019-20454.
Remediation
There is no fixed version for Debian:11 pcre3.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2019-20838
- https://security-tracker.debian.org/tracker/CVE-2019-20838
- https://support.apple.com/kb/HT211931
- https://support.apple.com/kb/HT212147
- http://seclists.org/fulldisclosure/2020/Dec/32
- http://seclists.org/fulldisclosure/2021/Feb/14
- https://bugs.gentoo.org/717920
- https://www.pcre.org/original/changelog.txt
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772@%3Cdev.mina.apache.org%3E
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772%40%3Cdev.mina.apache.org%3E
low severity
- Vulnerable module: pcre3/libpcre3
- Introduced through: pcre3/libpcre3@2:8.39-13
Detailed paths
-
Introduced through: nginx@1.21 › pcre3/libpcre3@2:8.39-13
NVD Description
Note: Versions mentioned in the description apply only to the upstream pcre3 package and not the pcre3 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
In PCRE 8.41, the OP_KETRMAX feature in the match function in pcre_exec.c allows stack exhaustion (uncontrolled recursion) when processing a crafted regular expression.
Remediation
There is no fixed version for Debian:11 pcre3.
References
- https://security-tracker.debian.org/tracker/CVE-2017-11164
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-11164
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772@%3Cdev.mina.apache.org%3E
- http://openwall.com/lists/oss-security/2017/07/11/3
- http://www.securityfocus.com/bid/99575
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2017-11164
- http://www.openwall.com/lists/oss-security/2023/04/11/1
- http://www.openwall.com/lists/oss-security/2023/04/12/1
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772%40%3Cdev.mina.apache.org%3E
low severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
LibTIFF 4.0.8 has multiple memory leak vulnerabilities, which allow attackers to cause a denial of service (memory consumption), as demonstrated by tif_open.c, tif_lzw.c, and tif_aux.c. NOTE: Third parties were unable to reproduce the issue
Remediation
There is no fixed version for Debian:11 tiff.
References
- https://security-tracker.debian.org/tracker/CVE-2017-16232
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16232
- http://packetstormsecurity.com/files/150896/LibTIFF-4.0.8-Memory-Leak.html
- http://lists.opensuse.org/opensuse-security-announce/2018-01/msg00036.html
- http://lists.opensuse.org/opensuse-security-announce/2018-01/msg00041.html
- http://www.openwall.com/lists/oss-security/2017/11/01/11
- http://www.openwall.com/lists/oss-security/2017/11/01/3
- http://www.openwall.com/lists/oss-security/2017/11/01/7
- http://www.openwall.com/lists/oss-security/2017/11/01/8
- http://seclists.org/fulldisclosure/2018/Dec/32
- http://seclists.org/fulldisclosure/2018/Dec/47
- http://www.securityfocus.com/bid/101696
low severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
An out-of-memory flaw was found in libtiff that could be triggered by passing a crafted tiff file to the TIFFRasterScanlineSize64() API. This flaw allows a remote attacker to cause a denial of service via a crafted input with a size smaller than 379 KB.
Remediation
There is no fixed version for Debian:11 tiff.
References
- https://security-tracker.debian.org/tracker/CVE-2023-52355
- https://access.redhat.com/errata/RHSA-2025:20801
- https://access.redhat.com/errata/RHSA-2025:21994
- https://access.redhat.com/errata/RHSA-2025:23078
- https://access.redhat.com/errata/RHSA-2025:23079
- https://access.redhat.com/errata/RHSA-2025:23080
- https://access.redhat.com/errata/RHSA-2026:3461
- https://access.redhat.com/errata/RHSA-2026:3462
- https://access.redhat.com/errata/RHSA-2026:41892
- https://access.redhat.com/errata/RHSA-2026:43537
- https://access.redhat.com/errata/RHSA-2026:49671
- https://access.redhat.com/errata/RHSA-2026:73909
- https://access.redhat.com/errata/RHSA-2026:73959
- https://access.redhat.com/errata/RHSA-2026:73960
- https://access.redhat.com/errata/RHSA-2026:73961
- https://access.redhat.com/errata/RHSA-2026:73962
- https://access.redhat.com/errata/RHSA-2026:74458
- https://access.redhat.com/errata/RHSA-2026:74459
- https://access.redhat.com/errata/RHSA-2026:74460
- https://access.redhat.com/errata/RHSA-2026:74461
- https://access.redhat.com/errata/RHSA-2026:74462
- https://access.redhat.com/errata/RHSA-2026:74463
- https://access.redhat.com/errata/RHSA-2026:74674
- https://access.redhat.com/security/cve/CVE-2023-52355
- https://bugzilla.redhat.com/show_bug.cgi?id=2251326
- https://gitlab.com/libtiff/libtiff/-/issues/621
low severity
- Vulnerable module: libssh2/libssh2-1
- Introduced through: libssh2/libssh2-1@1.9.0-2
Detailed paths
-
Introduced through: nginx@1.21 › libssh2/libssh2-1@1.9.0-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libssh2 package and not the libssh2 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A security vulnerability has been detected in libssh2 up to 1.11.1. The impacted element is the function userauth_password of the file src/userauth.c. Such manipulation of the argument username_len/password_len leads to integer overflow. The attack may be launched remotely. The name of the patch is 256d04b60d80bf1190e96b0ad1e91b2174d744b1. A patch should be applied to remediate this issue.
Remediation
There is no fixed version for Debian:11 libssh2.
References
- https://security-tracker.debian.org/tracker/CVE-2026-7598
- https://github.com/libssh2/libssh2/
- https://github.com/libssh2/libssh2/commit/256d04b60d80bf1190e96b0ad1e91b2174d744b1
- https://github.com/libssh2/libssh2/pull/1858
- https://vuldb.com/vuln/360555
- https://vuldb.com/vuln/360555/cti
- https://access.redhat.com/errata/RHSA-2026:16736
- https://access.redhat.com/errata/RHSA-2026:61752
- https://access.redhat.com/errata/RHSA-2026:7021
- https://access.redhat.com/security/cve/CVE-2026-7598
- https://bugzilla.redhat.com/show_bug.cgi?id=2464597
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-7598.json
- https://vuldb.com/submit/805564
low severity
- Vulnerable module: nginx
- Introduced through: nginx@1.21.6-1~bullseye
Detailed paths
-
Introduced through: nginx@1.21 › nginx@1.21.6-1~bullseye
NVD Description
Note: Versions mentioned in the description apply only to the upstream nginx package and not the nginx package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
The default configuration of nginx, possibly 1.3.13 and earlier, uses world-readable permissions for the (1) access.log and (2) error.log files, which allows local users to obtain sensitive information by reading the files.
Remediation
There is no fixed version for Debian:11 nginx.
References
- https://security-tracker.debian.org/tracker/CVE-2013-0337
- http://security.gentoo.org/glsa/glsa-201310-04.xml
- http://www.openwall.com/lists/oss-security/2013/02/21/15
- http://www.openwall.com/lists/oss-security/2013/02/22/1
- http://www.openwall.com/lists/oss-security/2013/02/24/1
- http://secunia.com/advisories/55181
low severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libtiff up to v4.7.1 was discovered to contain a stack overflow via the readSeparateStripsIntoBuffer function.
Remediation
There is no fixed version for Debian:11 tiff.
References
- https://security-tracker.debian.org/tracker/CVE-2025-61144
- https://gist.github.com/optionGo/5ad17e96a0a40f03578dd6c9f8645952
- https://gitlab.com/libtiff/libtiff/-/commit/09f53a86cf26dfd961925227e59e180db617f26d
- https://gitlab.com/libtiff/libtiff/-/commit/88cf9dbb48f6e172629795ecffae35d5052f68aa
- https://gitlab.com/libtiff/libtiff/-/issues/740
- https://gitlab.com/libtiff/libtiff/-/merge_requests/757
low severity
- Vulnerable module: acl/libacl1
- Introduced through: acl/libacl1@2.2.53-10
Detailed paths
-
Introduced through: nginx@1.21 › acl/libacl1@2.2.53-10
NVD Description
Note: Versions mentioned in the description apply only to the upstream acl package and not the acl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
acl before version 2.4.0 contains a symlink traversal vulnerability in the libacl pathname-based functions acl_get_file(), acl_set_file(), acl_extended_file(), and acl_delete_def_file() that allows local attackers to escalate privileges by replacing any pathname component with a symbolic link. Attackers who control any component of a pathname processed by a privileged caller can redirect ACL read or write operations to arbitrary files or directories, enabling unauthorized manipulation of access control lists and local privilege escalation.
Remediation
There is no fixed version for Debian:11 acl.
References
- https://security-tracker.debian.org/tracker/CVE-2026-54369
- https://cgit.git.savannah.nongnu.org/cgit/acl.git/commit/?id=24a227d0ab8576612194f8a56c2314389adc74a5
- https://cgit.git.savannah.nongnu.org/cgit/acl.git/commit/?id=3589787cd589b34bdd9265936e17190b6d3f17d1
- https://www.vulncheck.com/advisories/acl-symlink-traversal-privilege-escalation-via-libacl-functions
- https://access.redhat.com/errata/RHSA-2026:34351
- https://access.redhat.com/errata/RHSA-2026:42736
- https://access.redhat.com/errata/RHSA-2026:42739
- https://access.redhat.com/errata/RHSA-2026:43420
- https://access.redhat.com/security/cve/CVE-2026-54369
- https://bugzilla.redhat.com/show_bug.cgi?id=2490277
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-54369.json
- https://access.redhat.com/errata/RHSA-2026:44481
- https://access.redhat.com/errata/RHSA-2026:46836
- https://access.redhat.com/errata/RHSA-2026:50205
- https://access.redhat.com/errata/RHSA-2026:53371
- https://access.redhat.com/errata/RHSA-2026:54769
- https://access.redhat.com/errata/RHSA-2026:58981
- https://access.redhat.com/errata/RHSA-2026:64805
- https://access.redhat.com/errata/RHSA-2026:67140
- https://access.redhat.com/errata/RHSA-2026:67142
- https://access.redhat.com/errata/RHSA-2026:67144
low severity
- Vulnerable module: attr/libattr1
- Introduced through: attr/libattr1@1:2.4.48-6
Detailed paths
-
Introduced through: nginx@1.21 › attr/libattr1@1:2.4.48-6
NVD Description
Note: Versions mentioned in the description apply only to the upstream attr package and not the attr package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
attr before version 2.6.0 contains a symlink traversal vulnerability in the getfattr and setfattr utilities that allows local attackers to escalate privileges by replacing a pathname component with a symbolic link during directory hierarchy traversal. Attackers who control a pathname component can redirect getfattr and setfattr operations to arbitrary files by substituting a symlink, leading to local privilege escalation when getfattr or setfattr is invoked by a privileged process over an attacker-controlled path.
Remediation
There is no fixed version for Debian:11 attr.
References
- https://security-tracker.debian.org/tracker/CVE-2026-54371
- https://cgit.git.savannah.nongnu.org/cgit/attr.git/commit/?id=49f79e947270f06940b9100fa638f85dddc4aa7f
- https://cgit.git.savannah.nongnu.org/cgit/attr.git/commit/?id=c440855d6b33446edf4b5eb1a2d892281f15a99b
- https://www.vulncheck.com/advisories/attr-symlink-traversal-privilege-escalation-via-getfattr-setfattr
- https://access.redhat.com/security/cve/CVE-2026-54371
- https://bugzilla.redhat.com/show_bug.cgi?id=2490283
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-54371.json
- https://access.redhat.com/errata/RHSA-2026:34889
- https://access.redhat.com/errata/RHSA-2026:56133
- https://access.redhat.com/errata/RHSA-2026:59380
- https://access.redhat.com/errata/RHSA-2026:60226
- https://access.redhat.com/errata/RHSA-2026:61783
- https://access.redhat.com/errata/RHSA-2026:63135
- https://access.redhat.com/errata/RHSA-2026:63138
- https://access.redhat.com/errata/RHSA-2026:66018
low severity
- Vulnerable module: coreutils/coreutils
- Introduced through: coreutils/coreutils@8.32-4+b1
Detailed paths
-
Introduced through: nginx@1.21 › coreutils/coreutils@8.32-4+b1
NVD Description
Note: Versions mentioned in the description apply only to the upstream coreutils package and not the coreutils package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
chroot in GNU coreutils, when used with --userspec, allows local users to escape to the parent session via a crafted TIOCSTI ioctl call, which pushes characters to the terminal's input buffer.
Remediation
There is no fixed version for Debian:11 coreutils.
References
- https://security-tracker.debian.org/tracker/CVE-2016-2781
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772@%3Cdev.mina.apache.org%3E
- http://www.openwall.com/lists/oss-security/2016/02/28/2
- http://www.openwall.com/lists/oss-security/2016/02/28/3
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2016-2781
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772%40%3Cdev.mina.apache.org%3E
low severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
When curl is instructed to download content using the metalink feature, thecontents is verified against a hash provided in the metalink XML file.The metalink XML file points out to the client how to get the same contentfrom a set of different URLs, potentially hosted by different servers and theclient can then download the file from one or several of them. In a serial orparallel manner.If one of the servers hosting the contents has been breached and the contentsof the specific file on that server is replaced with a modified payload, curlshould detect this when the hash of the file mismatches after a completeddownload. It should remove the contents and instead try getting the contentsfrom another URL. This is not done, and instead such a hash mismatch is onlymentioned in text and the potentially malicious content is kept in the file ondisk.
Remediation
There is no fixed version for Debian:11 curl.
References
- https://security-tracker.debian.org/tracker/CVE-2021-22922
- https://security.netapp.com/advisory/ntap-20210902-0003/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/FRUCW2UVNYUDZF72DQLFQR4PJEC6CF7V/
- https://hackerone.com/reports/1213175
- https://www.oracle.com/security-alerts/cpuoct2021.html
- https://lists.apache.org/thread.html/r61db8e7dcb56dc000a5387a88f7a473bacec5ee01b9ff3f55308aacc@%3Cdev.kafka.apache.org%3E
- https://lists.apache.org/thread.html/r61db8e7dcb56dc000a5387a88f7a473bacec5ee01b9ff3f55308aacc@%3Cusers.kafka.apache.org%3E
- https://lists.apache.org/thread.html/rbf4ce74b0d1fa9810dec50ba3ace0caeea677af7c27a97111c06ccb7@%3Cdev.kafka.apache.org%3E
- https://lists.apache.org/thread.html/rbf4ce74b0d1fa9810dec50ba3ace0caeea677af7c27a97111c06ccb7@%3Cusers.kafka.apache.org%3E
- https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf
- https://lists.apache.org/thread.html/r61db8e7dcb56dc000a5387a88f7a473bacec5ee01b9ff3f55308aacc%40%3Cdev.kafka.apache.org%3E
- https://lists.apache.org/thread.html/r61db8e7dcb56dc000a5387a88f7a473bacec5ee01b9ff3f55308aacc%40%3Cusers.kafka.apache.org%3E
- https://lists.apache.org/thread.html/rbf4ce74b0d1fa9810dec50ba3ace0caeea677af7c27a97111c06ccb7%40%3Cdev.kafka.apache.org%3E
- https://lists.apache.org/thread.html/rbf4ce74b0d1fa9810dec50ba3ace0caeea677af7c27a97111c06ccb7%40%3Cusers.kafka.apache.org%3E
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FRUCW2UVNYUDZF72DQLFQR4PJEC6CF7V/
- https://security.gentoo.org/glsa/202212-01
- https://cert-portal.siemens.com/productcert/html/ssa-389290.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
low severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libcurl might in some circumstances reuse the wrong connection when asked to do an authenticated HTTP(S) request after a Negotiate-authenticated one, when both use the same host.
libcurl features a pool of recent connections so that subsequent requests can reuse an existing connection to avoid overhead.
When reusing a connection a range of criteria must be met. Due to a logical error in the code, a request that was issued by an application could wrongfully reuse an existing connection to the same server that was authenticated using different credentials.
An application that first uses Negotiate authentication to a server with
user1:password1 and then does another operation to the same server asking
for any authentication method but for user2:password2 (while the previous
connection is still alive) - the second request gets confused and wrongly
reuses the same connection and sends the new request over that connection
thinking it uses a mix of user1's and user2's credentials when it is in fact
still using the connection authenticated for user1...
Remediation
There is no fixed version for Debian:11 curl.
References
low severity
- Vulnerable module: jbigkit/libjbig0
- Introduced through: jbigkit/libjbig0@2.1-3.1+b2
Detailed paths
-
Introduced through: nginx@1.21 › jbigkit/libjbig0@2.1-3.1+b2
NVD Description
Note: Versions mentioned in the description apply only to the upstream jbigkit package and not the jbigkit package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
In LibTIFF 4.0.8, there is a memory malloc failure in tif_jbig.c. A crafted TIFF document can lead to an abort resulting in a remote denial of service attack.
Remediation
There is no fixed version for Debian:11 jbigkit.
References
- https://security-tracker.debian.org/tracker/CVE-2017-9937
- http://bugzilla.maptools.org/show_bug.cgi?id=2707
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772@%3Cdev.mina.apache.org%3E
- http://www.securityfocus.com/bid/99304
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2017-9937
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772%40%3Cdev.mina.apache.org%3E
low severity
- Vulnerable module: libpng1.6/libpng16-16
- Introduced through: libpng1.6/libpng16-16@1.6.37-3
Detailed paths
-
Introduced through: nginx@1.21 › libpng1.6/libpng16-16@1.6.37-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
png_create_info_struct in png.c in libpng 1.6.36 has a memory leak, as demonstrated by pngcp. NOTE: a third party has stated "I don't think it is libpng's job to free this buffer.
Remediation
There is no fixed version for Debian:11 libpng1.6.
References
low severity
- Vulnerable module: ncurses/libtinfo6
- Introduced through: ncurses/libtinfo6@6.2+20201114-2, ncurses/ncurses-base@6.2+20201114-2 and others
Detailed paths
-
Introduced through: nginx@1.21 › ncurses/libtinfo6@6.2+20201114-2
-
Introduced through: nginx@1.21 › ncurses/ncurses-base@6.2+20201114-2
-
Introduced through: nginx@1.21 › ncurses/ncurses-bin@6.2+20201114-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
NCurse v6.4-20230418 was discovered to contain a segmentation fault via the component _nc_wrap_entry().
Remediation
There is no fixed version for Debian:11 ncurses.
References
- https://security-tracker.debian.org/tracker/CVE-2023-50495
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LU4MYMKFEZQ5VSCVLRIZGDQOUW3T44GT/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.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/
- https://cert-portal.siemens.com/productcert/html/ssa-794697.html
low severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A vulnerability classified as problematic was found in LibTIFF 4.3.0. Affected by this vulnerability is the TIFF File Handler of tiff2ps. Opening a malicious file leads to a denial of service. The attack can be launched remotely but requires user interaction. The exploit has been disclosed to the public and may be used.
Remediation
There is no fixed version for Debian:11 tiff.
References
- https://security-tracker.debian.org/tracker/CVE-2022-1210
- https://gitlab.com/libtiff/libtiff/-/issues/402
- https://gitlab.com/libtiff/libtiff/uploads/c3da94e53cf1e1e8e6d4d3780dc8c42f/example.tiff
- https://security.gentoo.org/glsa/202210-10
- https://security.netapp.com/advisory/ntap-20220513-0005/
- https://vuldb.com/?id.196363
low severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
An issue was discovered in function TIFFReadDirectory libtiff before 4.4.0 allows attackers to cause a denial of service via crafted TIFF file.
Remediation
There is no fixed version for Debian:11 tiff.
References
low severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
ijg-libjpeg before 9d, as used in tiff2pdf (from LibTIFF) and other products, does not check for a NULL pointer at a certain place in jpeg_fdct_16x16 in jfdctint.c.
Remediation
There is no fixed version for Debian:11 tiff.
References
- https://security-tracker.debian.org/tracker/CVE-2018-10126
- http://bugzilla.maptools.org/show_bug.cgi?id=2786
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772@%3Cdev.mina.apache.org%3E
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2018-10126
- https://gitlab.com/libtiff/libtiff/-/issues/128
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772%40%3Cdev.mina.apache.org%3E
low severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
An out-of-memory flaw was found in libtiff. Passing a crafted tiff file to TIFFOpen() API may allow a remote attacker to cause a denial of service via a craft input with size smaller than 379 KB.
Remediation
There is no fixed version for Debian:11 tiff.
References
- https://security-tracker.debian.org/tracker/CVE-2023-6277
- http://seclists.org/fulldisclosure/2024/Jul/16
- http://seclists.org/fulldisclosure/2024/Jul/17
- http://seclists.org/fulldisclosure/2024/Jul/18
- http://seclists.org/fulldisclosure/2024/Jul/19
- http://seclists.org/fulldisclosure/2024/Jul/20
- http://seclists.org/fulldisclosure/2024/Jul/21
- http://seclists.org/fulldisclosure/2024/Jul/22
- http://seclists.org/fulldisclosure/2024/Jul/23
- https://access.redhat.com/security/cve/CVE-2023-6277
- https://bugzilla.redhat.com/show_bug.cgi?id=2251311
- https://gitlab.com/libtiff/libtiff/-/issues/614
- https://gitlab.com/libtiff/libtiff/-/merge_requests/545
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WJIN6DTSL3VODZUGWEUXLEL5DR53EZMV/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/Y7ZGN2MZXJ6E57W3L4YBM3ZPAU3T7T5C/
- https://security.netapp.com/advisory/ntap-20240119-0002/
- https://support.apple.com/kb/HT214116
- https://support.apple.com/kb/HT214117
- https://support.apple.com/kb/HT214118
- https://support.apple.com/kb/HT214119
- https://support.apple.com/kb/HT214120
- https://support.apple.com/kb/HT214122
- https://support.apple.com/kb/HT214123
- https://support.apple.com/kb/HT214124
low severity
- Vulnerable module: acl/libacl1
- Introduced through: acl/libacl1@2.2.53-10
Detailed paths
-
Introduced through: nginx@1.21 › acl/libacl1@2.2.53-10
NVD Description
Note: Versions mentioned in the description apply only to the upstream acl package and not the acl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
acl before version 2.4.0 contains a time-of-check to time-of-use (TOCTOU) race condition vulnerability that allows local attackers to escalate privileges by replacing a pathname component with a symbolic link between an lstat() check and subsequent symlink-following operations such as stat(), chown(), chmod(), acl_get_file(), and acl_set_file(). Attackers who control a pathname component can redirect file access control list operations to arbitrary files when getfacl, setfacl, or chacl is invoked by a privileged process over an attacker-controlled path, resulting in local privilege escalation.
Remediation
There is no fixed version for Debian:11 acl.
References
- https://security-tracker.debian.org/tracker/CVE-2026-54370
- https://cgit.git.savannah.nongnu.org/cgit/acl.git/commit/?id=24a227d0ab8576612194f8a56c2314389adc74a5
- https://cgit.git.savannah.nongnu.org/cgit/acl.git/commit/?id=3589787cd589b34bdd9265936e17190b6d3f17d1
- https://www.vulncheck.com/advisories/acl-toctou-symlink-traversal-via-getfacl-setfacl-chacl
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.10-2+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › expat/libexpat1@2.2.10-2+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
expat before version 2.4.0 does not properly handle entities expansion unless an application developer uses the XML_SetEntityDeclHandler function, which allows remote attackers to cause a denial of service (resource consumption), send HTTP requests to intranet servers, or read arbitrary files via a crafted XML document, aka an XML External Entity (XXE) issue. NOTE: it could be argued that because expat already provides the ability to disable external entity expansion, the responsibility for resolving this issue lies with application developers; according to this argument, this entry should be REJECTed, and each affected application would need its own CVE.
Remediation
There is no fixed version for Debian:11 expat.
References
- https://security-tracker.debian.org/tracker/CVE-2013-0340
- https://support.apple.com/kb/HT212804
- https://support.apple.com/kb/HT212805
- https://support.apple.com/kb/HT212807
- https://support.apple.com/kb/HT212814
- https://support.apple.com/kb/HT212815
- https://support.apple.com/kb/HT212819
- http://seclists.org/fulldisclosure/2021/Sep/33
- http://seclists.org/fulldisclosure/2021/Sep/34
- http://seclists.org/fulldisclosure/2021/Sep/35
- http://seclists.org/fulldisclosure/2021/Sep/38
- http://seclists.org/fulldisclosure/2021/Sep/39
- http://seclists.org/fulldisclosure/2021/Sep/40
- https://security.gentoo.org/glsa/201701-21
- http://securitytracker.com/id?1028213
- https://lists.apache.org/thread.html/r41eca5f4f09e74436cbb05dec450fc2bef37b5d3e966aa7cc5fada6d@%3Cannounce.apache.org%3E
- https://lists.apache.org/thread.html/rfb2c193360436e230b85547e85a41bea0916916f96c501f5b6fc4702@%3Cusers.openoffice.apache.org%3E
- http://www.openwall.com/lists/oss-security/2021/10/07/4
- http://openwall.com/lists/oss-security/2013/02/22/3
- http://www.openwall.com/lists/oss-security/2013/04/12/6
- http://www.securityfocus.com/bid/58233
- https://github.com/libexpat/libexpat/blob/R_2_4_1/expat/Changes
- http://seclists.org/fulldisclosure/2021/Oct/61
- http://seclists.org/fulldisclosure/2021/Oct/62
- http://seclists.org/fulldisclosure/2021/Oct/63
- http://www.osvdb.org/90634
- https://lists.apache.org/thread.html/r41eca5f4f09e74436cbb05dec450fc2bef37b5d3e966aa7cc5fada6d%40%3Cannounce.apache.org%3E
- https://lists.apache.org/thread.html/rfb2c193360436e230b85547e85a41bea0916916f96c501f5b6fc4702%40%3Cusers.openoffice.apache.org%3E
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
low severity
- Vulnerable module: nginx
- Introduced through: nginx@1.21.6-1~bullseye
Detailed paths
-
Introduced through: nginx@1.21 › nginx@1.21.6-1~bullseye
NVD Description
Note: Versions mentioned in the description apply only to the upstream nginx package and not the nginx package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
nginx 0.7.64 writes data to a log file without sanitizing non-printable characters, which might allow remote attackers to modify a window's title, or possibly execute arbitrary commands or overwrite files, via an HTTP request containing an escape sequence for a terminal emulator.
Remediation
There is no fixed version for Debian:11 nginx.
References
low severity
- Vulnerable module: p11-kit/libp11-kit0
- Introduced through: p11-kit/libp11-kit0@0.23.22-1
Detailed paths
-
Introduced through: nginx@1.21 › p11-kit/libp11-kit0@0.23.22-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream p11-kit package and not the p11-kit package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw was found in p11-kit. The RPC message attribute parsing functions p11_rpc_message_get_attribute() and p11_rpc_message_get_attribute_array_value() form a mutually-recursive call chain with no recursion depth limit when processing nested CKA_WRAP_TEMPLATE, CKA_UNWRAP_TEMPLATE, and CKA_DERIVE_TEMPLATE attributes. An unauthenticated attacker with local access to the p11-kit RPC Unix domain socket can send a specially crafted request with deeply nested template attributes, causing stack exhaustion and crashing the p11-kit server process and its dependent services.
Remediation
There is no fixed version for Debian:11 p11-kit.
References
- https://security-tracker.debian.org/tracker/CVE-2026-13757
- https://access.redhat.com/errata/RHSA-2026:37469
- https://access.redhat.com/errata/RHSA-2026:38342
- https://access.redhat.com/errata/RHSA-2026:49668
- https://access.redhat.com/security/cve/CVE-2026-13757
- https://bugzilla.redhat.com/show_bug.cgi?id=2494556
- https://github.com/advisories/GHSA-p2wm-69qx-x25w
- https://access.redhat.com/errata/RHSA-2026:49667
- https://access.redhat.com/errata/RHSA-2026:53371
- https://access.redhat.com/errata/RHSA-2026:54387
- https://access.redhat.com/errata/RHSA-2026:54760
- https://access.redhat.com/errata/RHSA-2026:58981
- https://access.redhat.com/errata/RHSA-2026:72394
- https://access.redhat.com/errata/RHSA-2026:72395
- https://access.redhat.com/errata/RHSA-2026:72399
- https://access.redhat.com/errata/RHSA-2026:72470
- https://access.redhat.com/errata/RHSA-2026:72475
- https://access.redhat.com/errata/RHSA-2026:72476
- https://access.redhat.com/errata/RHSA-2026:72502
- https://access.redhat.com/errata/RHSA-2026:81201
- https://access.redhat.com/errata/RHSA-2026:82304
- https://access.redhat.com/errata/RHSA-2026:82322
- https://access.redhat.com/errata/RHSA-2026:82336
- https://access.redhat.com/errata/RHSA-2026:82347
- https://access.redhat.com/errata/RHSA-2026:82354
- https://access.redhat.com/errata/RHSA-2026:82372
- https://access.redhat.com/errata/RHSA-2026:82857
- https://access.redhat.com/errata/RHSA-2026:82888
low severity
- Vulnerable module: shadow/login
- Introduced through: shadow/login@1:4.8.1-1 and shadow/passwd@1:4.8.1-1
Detailed paths
-
Introduced through: nginx@1.21 › shadow/login@1:4.8.1-1
-
Introduced through: nginx@1.21 › shadow/passwd@1:4.8.1-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream shadow package and not the shadow package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
initscripts in rPath Linux 1 sets insecure permissions for the /var/log/btmp file, which allows local users to obtain sensitive information regarding authentication attempts. NOTE: because sshd detects the insecure permissions and does not log certain events, this also prevents sshd from logging failed authentication attempts by remote attackers.
Remediation
There is no fixed version for Debian:11 shadow.
References
- 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: coreutils/coreutils
- Introduced through: coreutils/coreutils@8.32-4+b1
Detailed paths
-
Introduced through: nginx@1.21 › coreutils/coreutils@8.32-4+b1
NVD Description
Note: Versions mentioned in the description apply only to the upstream coreutils package and not the coreutils package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
GNU coreutils unexpand is vulnerable to a heap-based buffer overflow due to an integer overflow during buffer allocation when processing large tab stop (-t) values. The multiplication used to calculate the allocation size can wrap around, resulting in an undersized buffer. When processing crafted input, subsequent writes exceed the allocated memory, leading to an out‑of‑bounds heap write.
When running GNU coreutils unexpand with attacker-provided large tab stop (-t) arguments, this behavior leads to a crash and potentially achieve a heap write primitive depending on memory layout.
This issue has been fixed in the commit b60a159fdc5bfcf9988d3a4cb6f53abe8ad5d35d
Remediation
There is no fixed version for Debian:11 coreutils.
References
low severity
- Vulnerable module: coreutils/coreutils
- Introduced through: coreutils/coreutils@8.32-4+b1
Detailed paths
-
Introduced through: nginx@1.21 › coreutils/coreutils@8.32-4+b1
NVD Description
Note: Versions mentioned in the description apply only to the upstream coreutils package and not the coreutils package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
GNU coreutils uniq is vulnerable to an out‑of‑bounds read due to incorrect handling of multibyte input when the -w (--check-chars) option is used. The find_field() function miscalculates the byte length of characters by repeatedly processing a fixed pointer instead of advancing through the input, resulting in an inflated length value. This incorrect length is later used in a memcmp operation, causing reads beyond the allocated buffer when processing crafted multibyte input.
When running GNU coreutils uniq with attacker-provided arguments, this behavior leads to a crash and potential adjacent heap memory exposure.
This issue has been fixed in the commit d64e35a8a4c0e4608321433e0d84d917e4e36371.
Remediation
There is no fixed version for Debian:11 coreutils.
References
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@247.3-7 and systemd/libudev1@247.3-7
Detailed paths
-
Introduced through: nginx@1.21 › systemd/libsystemd0@247.3-7
-
Introduced through: nginx@1.21 › systemd/libudev1@247.3-7
NVD Description
Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
An exploitable denial-of-service vulnerability exists in Systemd 245. A specially crafted DHCP FORCERENEW packet can cause a server running the DHCP client to be vulnerable to a DHCP ACK spoofing attack. An attacker can forge a pair of FORCERENEW and DCHP ACK packets to reconfigure the server.
Remediation
There is no fixed version for Debian:11 systemd.
References
- https://security-tracker.debian.org/tracker/CVE-2020-13529
- https://security.netapp.com/advisory/ntap-20210625-0005/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/42TMJVNYRY65B4QCJICBYOEIVZV3KUYI/
- https://security.gentoo.org/glsa/202107-48
- https://talosintelligence.com/vulnerability_reports/TALOS-2020-1142
- http://www.openwall.com/lists/oss-security/2021/08/04/2
- http://www.openwall.com/lists/oss-security/2021/08/17/3
- http://www.openwall.com/lists/oss-security/2021/09/07/3
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/42TMJVNYRY65B4QCJICBYOEIVZV3KUYI/
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
low severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw was found in tiffcrop, a program distributed by the libtiff package. A specially crafted tiff file can lead to an out-of-bounds read in the extractImageSection function in tools/tiffcrop.c, resulting in a denial of service and limited information disclosure. This issue affects libtiff versions 4.x.
Remediation
There is no fixed version for Debian:11 tiff.
References
low severity
- Vulnerable module: util-linux
- Introduced through: util-linux@2.36.1-8+deb11u1, util-linux/bsdutils@1:2.36.1-8+deb11u1 and others
Detailed paths
-
Introduced through: nginx@1.21 › util-linux@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/bsdutils@1:2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/libblkid1@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/libmount1@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/libsmartcols1@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/libuuid1@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/mount@2.36.1-8+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream util-linux package and not the util-linux package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw was found in 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:11 util-linux.
References
- https://security-tracker.debian.org/tracker/CVE-2025-14104
- https://access.redhat.com/security/cve/CVE-2025-14104
- https://bugzilla.redhat.com/show_bug.cgi?id=2419369
- https://access.redhat.com/errata/RHSA-2026:1696
- https://access.redhat.com/errata/RHSA-2026:1852
- https://access.redhat.com/errata/RHSA-2026:1913
- https://access.redhat.com/errata/RHSA-2026:2485
- https://access.redhat.com/errata/RHSA-2026:2563
- https://access.redhat.com/errata/RHSA-2026:2737
- https://access.redhat.com/errata/RHSA-2026:2800
- https://access.redhat.com/errata/RHSA-2026:3406
- https://access.redhat.com/errata/RHSA-2026:4943
- https://access.redhat.com/errata/RHSA-2026:7180
- https://access.redhat.com/errata/RHSA-2026:82347
- https://access.redhat.com/errata/RHSA-2026:82354
- https://access.redhat.com/errata/RHSA-2026:82372
- https://access.redhat.com/errata/RHSA-2026:82857
low severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A denial of service vulnerability exists in curl <v8.1.0 in the way libcurl provides several different backends for resolving host names, selected at build time. If it is built to use the synchronous resolver, it allows name resolves to time-out slow operations using alarm() and siglongjmp(). When doing this, libcurl used a global buffer that was not mutex protected and a multi-threaded application might therefore crash or otherwise misbehave.
Remediation
There is no fixed version for Debian:11 curl.
References
- https://security-tracker.debian.org/tracker/CVE-2023-28320
- http://seclists.org/fulldisclosure/2023/Jul/47
- http://seclists.org/fulldisclosure/2023/Jul/48
- http://seclists.org/fulldisclosure/2023/Jul/52
- https://hackerone.com/reports/1929597
- https://security.gentoo.org/glsa/202310-12
- https://security.netapp.com/advisory/ntap-20230609-0009/
- https://support.apple.com/kb/HT213843
- https://support.apple.com/kb/HT213844
- https://support.apple.com/kb/HT213845
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › glibc/libc-bin@2.31-13+deb11u3
-
Introduced through: nginx@1.21 › glibc/libc6@2.31-13+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw has been identified in glibc. In an extremely rare situation, the getaddrinfo function may access memory that has been freed, resulting in an application crash. This issue is only exploitable when a NSS module implements only the nss_gethostbyname2_r and nss_getcanonname_r hooks without implementing the nss*_gethostbyname3_r hook. The resolved name should return a large number of IPv6 and IPv4, and the call to the getaddrinfo function should have the AF_INET6 address family with AI_CANONNAME, AI_ALL and AI_V4MAPPED as flags.
Remediation
There is no fixed version for Debian:11 glibc.
References
- https://security-tracker.debian.org/tracker/CVE-2023-4806
- http://www.openwall.com/lists/oss-security/2023/10/03/4
- http://www.openwall.com/lists/oss-security/2023/10/03/5
- http://www.openwall.com/lists/oss-security/2023/10/03/6
- http://www.openwall.com/lists/oss-security/2023/10/03/8
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4DBUQRRPB47TC3NJOUIBVWUGFHBJAFDL/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DFG4P76UHHZEWQ26FWBXG76N2QLKKPZA/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NDAQWHTSVOCOZ5K6KPIWKRT3JX4RTZUR/
- https://security.gentoo.org/glsa/202310-03
- https://security.netapp.com/advisory/ntap-20240125-0008/
- https://access.redhat.com/errata/RHBA-2024:2413
- https://access.redhat.com/errata/RHSA-2023:5453
- https://access.redhat.com/errata/RHSA-2023:5455
- https://access.redhat.com/errata/RHSA-2023:7409
- https://access.redhat.com/security/cve/CVE-2023-4806
- https://bugzilla.redhat.com/show_bug.cgi?id=2237782
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-831302.html
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.10-2+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › expat/libexpat1@2.2.10-2+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
In libexpat through 2.7.3, a crafted file with an approximate size of 2 MiB can lead to dozens of seconds of processing time.
Remediation
There is no fixed version for Debian:11 expat.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.10-2+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › expat/libexpat1@2.2.10-2+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libexpat through 2.5.0 allows recursive XML Entity Expansion if XML_DTD is undefined at compile time.
Remediation
There is no fixed version for Debian:11 expat.
References
- https://security-tracker.debian.org/tracker/CVE-2023-52426
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PNRIHC7DVVRAIWFRGV23Y6UZXFBXSQDB/
- https://cwe.mitre.org/data/definitions/776.html
- https://github.com/libexpat/libexpat/commit/0f075ec8ecb5e43f8fdca5182f8cca4703da0404
- https://github.com/libexpat/libexpat/pull/777
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PNRIHC7DVVRAIWFRGV23Y6UZXFBXSQDB/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WNUBSGZFEZOBHJFTAD42SAN4ATW2VEMV/
- https://security.netapp.com/advisory/ntap-20240307-0005/
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-784301.html
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.10-2+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › expat/libexpat1@2.2.10-2+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libexpat before 2.7.5 allows an infinite loop while parsing DTD content.
Remediation
There is no fixed version for Debian:11 expat.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.10-2+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › expat/libexpat1@2.2.10-2+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libexpat before 2.7.5 allows a NULL pointer dereference with empty external parameter entity content.
Remediation
There is no fixed version for Debian:11 expat.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.10-2+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › expat/libexpat1@2.2.10-2+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libexpat before 2.7.5 allows a NULL pointer dereference in the function setContext on retry after an earlier ouf-of-memory condition.
Remediation
There is no fixed version for Debian:11 expat.
References
low severity
- Vulnerable module: libjpeg-turbo/libjpeg62-turbo
- Introduced through: libjpeg-turbo/libjpeg62-turbo@1:2.0.6-4
Detailed paths
-
Introduced through: nginx@1.21 › libjpeg-turbo/libjpeg62-turbo@1:2.0.6-4
NVD Description
Note: Versions mentioned in the description apply only to the upstream libjpeg-turbo package and not the libjpeg-turbo package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
The PPM reader in libjpeg-turbo through 2.0.90 mishandles use of tjLoadImage for loading a 16-bit binary PPM file into a grayscale buffer and loading a 16-bit binary PGM file into an RGB buffer. This is related to a heap-based buffer overflow in the get_word_rgb_row function in rdppm.c.
Remediation
There is no fixed version for Debian:11 libjpeg-turbo.
References
low severity
- Vulnerable module: libpng1.6/libpng16-16
- Introduced through: libpng1.6/libpng16-16@1.6.37-3
Detailed paths
-
Introduced through: nginx@1.21 › libpng1.6/libpng16-16@1.6.37-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A heap overflow flaw was found in libpngs' pngimage.c program. This flaw allows an attacker with local network access to pass a specially crafted PNG file to the pngimage utility, causing an application to crash, leading to a denial of service.
Remediation
There is no fixed version for Debian:11 libpng1.6.
References
low severity
- Vulnerable module: libxpm/libxpm4
- Introduced through: libxpm/libxpm4@1:3.5.12-1
Detailed paths
-
Introduced through: nginx@1.21 › libxpm/libxpm4@1:3.5.12-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxpm package and not the libxpm package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw was found in libXpm. A local user with low privileges could exploit an Out-of-Bounds Read vulnerability in the xpmNextWord() function by processing a specially crafted or very small XPM (X PixMap) image file. This improper validation of file boundaries can cause an internal pointer to read beyond the file's end, leading to application crashes and Denial of Service conditions.
Remediation
There is no fixed version for Debian:11 libxpm.
References
- https://security-tracker.debian.org/tracker/CVE-2026-4367
- https://access.redhat.com/security/cve/CVE-2026-4367
- https://bugzilla.redhat.com/show_bug.cgi?id=2448984
- https://gitlab.freedesktop.org/xorg/lib/libxpm/-/commit/5448e1bd
- https://seclists.org/oss-sec/2026/q2/192
- http://www.openwall.com/lists/oss-security/2026/04/21/3
- https://access.redhat.com/errata/RHSA-2026:30354
- https://access.redhat.com/errata/RHSA-2026:47072
low severity
- Vulnerable module: pcre3/libpcre3
- Introduced through: pcre3/libpcre3@2:8.39-13
Detailed paths
-
Introduced through: nginx@1.21 › pcre3/libpcre3@2:8.39-13
NVD Description
Note: Versions mentioned in the description apply only to the upstream pcre3 package and not the pcre3 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
In PCRE 8.41, after compiling, a pcretest load test PoC produces a crash overflow in the function match() in pcre_exec.c because of a self-recursive call. NOTE: third parties dispute the relevance of this report, noting that there are options that can be used to limit the amount of stack that is used
Remediation
There is no fixed version for Debian:11 pcre3.
References
- https://security-tracker.debian.org/tracker/CVE-2017-16231
- https://bugs.exim.org/show_bug.cgi?id=2047
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16231
- http://packetstormsecurity.com/files/150897/PCRE-8.41-Buffer-Overflow.html
- http://www.openwall.com/lists/oss-security/2017/11/01/11
- http://www.openwall.com/lists/oss-security/2017/11/01/3
- http://www.openwall.com/lists/oss-security/2017/11/01/7
- http://www.openwall.com/lists/oss-security/2017/11/01/8
- http://seclists.org/fulldisclosure/2018/Dec/33
- http://www.securityfocus.com/bid/101688
low severity
- Vulnerable module: tar
- Introduced through: tar@1.34+dfsg-1
Detailed paths
-
Introduced through: nginx@1.21 › tar@1.34+dfsg-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tar package and not the tar package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw was found in tar. A remote attacker could exploit this vulnerability by crafting a malicious archive, leading to hidden file injection with fully attacker-controlled content. This bypasses pre-extraction inspection mechanisms, potentially allowing an attacker to introduce malicious files onto a system without detection.
Remediation
There is no fixed version for Debian:11 tar.
References
- https://security-tracker.debian.org/tracker/CVE-2026-5704
- https://access.redhat.com/security/cve/CVE-2026-5704
- https://bugzilla.redhat.com/show_bug.cgi?id=2455360
- http://www.openwall.com/lists/oss-security/2026/04/11/10
- http://www.openwall.com/lists/oss-security/2026/04/11/11
- http://www.openwall.com/lists/oss-security/2026/04/12/2
- https://access.redhat.com/errata/RHSA-2026:61581
- https://access.redhat.com/errata/RHSA-2026:61783
- https://access.redhat.com/errata/RHSA-2026:61586
- https://access.redhat.com/errata/RHSA-2026:66018
- https://access.redhat.com/errata/RHSA-2026:66514
- https://access.redhat.com/errata/RHSA-2026:70390
low severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libtiff up to v4.7.1 was discovered to contain a NULL pointer dereference via the component libtiff/tif_open.c.
Remediation
There is no fixed version for Debian:11 tiff.
References
low severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A vulnerability was found in the libtiff library. This security flaw causes a heap buffer overflow in extractContigSamples32bits, tiffcrop.c.
Remediation
There is no fixed version for Debian:11 tiff.
References
low severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Out-of-bounds Read error in tiffcrop in libtiff 4.3.0 allows attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit 46dc8fcd.
Remediation
There is no fixed version for Debian:11 tiff.
References
- https://security-tracker.debian.org/tracker/CVE-2022-1056
- https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-1056.json
- https://gitlab.com/libtiff/libtiff/-/issues/391
- https://gitlab.com/libtiff/libtiff/-/merge_requests/307
- https://security.gentoo.org/glsa/202210-10
- https://security.netapp.com/advisory/ntap-20221228-0008/
low severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A heap-buffer-overflow vulnerability was found in LibTIFF, in extractImageSection() at tools/tiffcrop.c:7916 and tools/tiffcrop.c:7801. This flaw allows attackers to cause a denial of service via a crafted tiff file.
Remediation
There is no fixed version for Debian:11 tiff.
References
- https://security-tracker.debian.org/tracker/CVE-2023-3164
- https://access.redhat.com/security/cve/CVE-2023-4156
- https://bugzilla.redhat.com/show_bug.cgi?id=2215930
- https://access.redhat.com/security/cve/CVE-2023-3164
- https://bugzilla.redhat.com/show_bug.cgi?id=2213531
- https://gitlab.com/libtiff/libtiff/-/issues/542
low severity
- Vulnerable module: util-linux
- Introduced through: util-linux@2.36.1-8+deb11u1, util-linux/bsdutils@1:2.36.1-8+deb11u1 and others
Detailed paths
-
Introduced through: nginx@1.21 › util-linux@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/bsdutils@1:2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/libblkid1@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/libmount1@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/libsmartcols1@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/libuuid1@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/mount@2.36.1-8+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream util-linux package and not the util-linux package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw was found in the util-linux chfn and chsh utilities when compiled with Readline support. The Readline library uses an "INPUTRC" environment variable to get a path to the library config file. When the library cannot parse the specified file, it prints an error message containing data from the file. This flaw allows an unprivileged user to read root-owned files, potentially leading to privilege escalation. This flaw affects util-linux versions prior to 2.37.4.
Remediation
There is no fixed version for Debian:11 util-linux.
References
- 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/
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
low severity
- Vulnerable module: zlib/zlib1g
- Introduced through: zlib/zlib1g@1:1.2.11.dfsg-2+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › zlib/zlib1g@1:1.2.11.dfsg-2+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream zlib package and not the zlib package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
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:11 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: nghttp2/libnghttp2-14
- Introduced through: nghttp2/libnghttp2-14@1.43.0-1
Detailed paths
-
Introduced through: nginx@1.21 › nghttp2/libnghttp2-14@1.43.0-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream nghttp2 package and not the nghttp2 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
nghttp2's nghttpx proxy through 1.69.0 forwards an HTTP/1.1 Upgrade request that also carries a Content-Length header and body onto reusable keep-alive backend connections, re-adding the Upgrade and Connection headers while passing Content-Length verbatim. A backend that resolves the resulting ambiguous message in the attacker's favor enables HTTP request/response smuggling and cross-client response-queue poisoning.
Remediation
There is no fixed version for Debian:11 nghttp2.
References
- https://security-tracker.debian.org/tracker/CVE-2026-58055
- https://github.com/bikini/exploitarium/tree/main/nghttp2-nghttpx-upgrade-queue-poison-poc
- https://github.com/nghttp2/nghttp2/commit/ab28105c4a0197da24f8bfc414bc116055249e1e
- https://www.vulncheck.com/advisories/nghttp2-nghttpx-http-request-response-smuggling-via-upgrade-request-with-content-length
low severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Successfully using libcurl to do a transfer over a specific HTTP proxy
(proxyA) with Digest authentication and then changing the proxy host to
a second one (proxyB) for a second transfer, reusing the same handle, makes
libcurl wrongly pass on the Proxy-Authorization: header field meant for
proxyA, to proxyB.
Remediation
There is no fixed version for Debian:11 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
When curl is instructed to get content using the metalink feature, and a user name and password are used to download the metalink XML file, those same credentials are then subsequently passed on to each of the servers from which curl will download or try to download the contents from. Often contrary to the user's expectations and intentions and without telling the user it happened.
Remediation
There is no fixed version for Debian:11 curl.
References
- https://security-tracker.debian.org/tracker/CVE-2021-22923
- https://security.netapp.com/advisory/ntap-20210902-0003/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/FRUCW2UVNYUDZF72DQLFQR4PJEC6CF7V/
- https://hackerone.com/reports/1213181
- https://www.oracle.com/security-alerts/cpuoct2021.html
- https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FRUCW2UVNYUDZF72DQLFQR4PJEC6CF7V/
- https://security.gentoo.org/glsa/202212-01
- https://cert-portal.siemens.com/productcert/html/ssa-389290.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › glibc/libc-bin@2.31-13+deb11u3
-
Introduced through: nginx@1.21 › glibc/libc6@2.31-13+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may bypass ASLR using cache of thread stack and heap. The component is: glibc. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat.
Remediation
There is no fixed version for Debian:11 glibc.
References
- 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
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › glibc/libc-bin@2.31-13+deb11u3
-
Introduced through: nginx@1.21 › glibc/libc6@2.31-13+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may guess the heap addresses of pthread_created thread. The component is: glibc. NOTE: the vendor's position is "ASLR bypass itself is not a vulnerability.
Remediation
There is no fixed version for Debian:11 glibc.
References
- 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
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
low severity
- Vulnerable module: libpng1.6/libpng16-16
- Introduced through: libpng1.6/libpng16-16@1.6.37-3
Detailed paths
-
Introduced through: nginx@1.21 › libpng1.6/libpng16-16@1.6.37-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw has been found in pnggroup libpng up to 1.6.55. Affected by this vulnerability is the function do_pnm2png of the file contrib/pngminus/pnm2png.c of the component pnm2png. This manipulation of the argument width/height causes heap-based buffer overflow. The attack is restricted to local execution. The exploit has been published and may be used. The project was informed of the problem early through an issue report but has not responded yet.
Remediation
There is no fixed version for Debian:11 libpng1.6.
References
low severity
- Vulnerable module: libxslt/libxslt1.1
- Introduced through: libxslt/libxslt1.1@1.1.34-4
Detailed paths
-
Introduced through: nginx@1.21 › libxslt/libxslt1.1@1.1.34-4
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:11 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:11 libxslt.
References
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@247.3-7 and systemd/libudev1@247.3-7
Detailed paths
-
Introduced through: nginx@1.21 › systemd/libsystemd0@247.3-7
-
Introduced through: nginx@1.21 › systemd/libudev1@247.3-7
NVD Description
Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
An issue was discovered in systemd 253. An attacker can modify a sealed log file such that, in some views, not all existing and sealed log messages are displayed. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability."
Remediation
There is no fixed version for Debian:11 systemd.
References
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@247.3-7 and systemd/libudev1@247.3-7
Detailed paths
-
Introduced through: nginx@1.21 › systemd/libsystemd0@247.3-7
-
Introduced through: nginx@1.21 › systemd/libudev1@247.3-7
NVD Description
Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
An issue was discovered in systemd 253. An attacker can truncate a sealed log file and then resume log sealing such that checking the integrity shows no error, despite modifications. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability."
Remediation
There is no fixed version for Debian:11 systemd.
References
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@247.3-7 and systemd/libudev1@247.3-7
Detailed paths
-
Introduced through: nginx@1.21 › systemd/libsystemd0@247.3-7
-
Introduced through: nginx@1.21 › systemd/libudev1@247.3-7
NVD Description
Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
An issue was discovered in systemd 253. An attacker can modify the contents of past events in a sealed log file and then adjust the file such that checking the integrity shows no error, despite modifications. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability."
Remediation
There is no fixed version for Debian:11 systemd.
References
low severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A vulnerability was determined in LibTIFF up to 4.5.1. Affected by this issue is the function readSeparateStripsetoBuffer of the file tools/tiffcrop.c of the component tiffcrop. The manipulation leads to stack-based buffer overflow. Local access is required to approach this attack. The patch is identified as 8a7a48d7a645992ca83062b3a1873c951661e2b3. It is recommended to apply a patch to fix this issue.
Remediation
There is no fixed version for Debian:11 tiff.
References
low severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.18.3-6+deb11u1, krb5/libk5crypto3@1.18.3-6+deb11u1 and others
Detailed paths
-
Introduced through: nginx@1.21 › krb5/libgssapi-krb5-2@1.18.3-6+deb11u1
-
Introduced through: nginx@1.21 › krb5/libk5crypto3@1.18.3-6+deb11u1
-
Introduced through: nginx@1.21 › krb5/libkrb5-3@1.18.3-6+deb11u1
-
Introduced through: nginx@1.21 › krb5/libkrb5support0@1.18.3-6+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
An integer underflow vulnerability was found in MIT krb5 in the berval2tl_data() function in plugins/kdb/ldap/libkdb_ldap/ldap_principal2.c. The function performs an unsigned subtraction (bv_len - 2) without a prior bounds check. When bv_len is 0 or 1, the subtraction wraps to a large value which is then truncated to uint16_t, yielding 0xFFFE (65534) or 0xFFFF (65535). The subsequent malloc succeeds and memcpy reads up to 65534 bytes from a 0-1 byte buffer, resulting in a heap out-of-bounds read. The attack vector involves a malicious or compromised LDAP KDB backend returning a krbExtraData attribute with bv_len < 2, triggering the underflow when the KDC or kadmind reads principal data.
Remediation
There is no fixed version for Debian:11 krb5.
References
low severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libtiff up to v4.7.1 was discovered to contain a double free via the component tools/tiffcrop.c.
Remediation
There is no fixed version for Debian:11 tiff.
References
low severity
- Vulnerable module: gcc-10/gcc-10-base
- Introduced through: gcc-10/gcc-10-base@10.2.1-6, gcc-10/libgcc-s1@10.2.1-6 and others
Detailed paths
-
Introduced through: nginx@1.21 › gcc-10/gcc-10-base@10.2.1-6
-
Introduced through: nginx@1.21 › gcc-10/libgcc-s1@10.2.1-6
-
Introduced through: nginx@1.21 › gcc-10/libstdc++6@10.2.1-6
NVD Description
Note: Versions mentioned in the description apply only to the upstream gcc-10 package and not the gcc-10 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
DISPUTEDA failure in the -fstack-protector feature in GCC-based toolchains that target AArch64 allows an attacker to exploit an existing buffer overflow in dynamically-sized local variables in your application without this being detected. This stack-protector failure only applies to C99-style dynamically-sized local variables or those created using alloca(). The stack-protector operates as intended for statically-sized local variables.
The default behavior when the stack-protector detects an overflow is to terminate your application, resulting in controlled loss of availability. An attacker who can exploit a buffer overflow without triggering the stack-protector might be able to change program flow control to cause an uncontrolled loss of availability or to go further and affect confidentiality or integrity. NOTE: The GCC project argues that this is a missed hardening bug and not a vulnerability by itself.
Remediation
There is no fixed version for Debian:11 gcc-10.
References
- https://security-tracker.debian.org/tracker/CVE-2023-4039
- https://developer.arm.com/Arm%20Security%20Center/GCC%20Stack%20Protector%20Vulnerability%20AArch64
- https://github.com/metaredteam/external-disclosures/security/advisories/GHSA-x7ch-h5rf-w2mf
- https://cert-portal.siemens.com/productcert/html/ssa-355557.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
low severity
- Vulnerable module: gcc-9/gcc-9-base
- Introduced through: gcc-9/gcc-9-base@9.3.0-22
Detailed paths
-
Introduced through: nginx@1.21 › gcc-9/gcc-9-base@9.3.0-22
NVD Description
Note: Versions mentioned in the description apply only to the upstream gcc-9 package and not the gcc-9 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
DISPUTEDA failure in the -fstack-protector feature in GCC-based toolchains that target AArch64 allows an attacker to exploit an existing buffer overflow in dynamically-sized local variables in your application without this being detected. This stack-protector failure only applies to C99-style dynamically-sized local variables or those created using alloca(). The stack-protector operates as intended for statically-sized local variables.
The default behavior when the stack-protector detects an overflow is to terminate your application, resulting in controlled loss of availability. An attacker who can exploit a buffer overflow without triggering the stack-protector might be able to change program flow control to cause an uncontrolled loss of availability or to go further and affect confidentiality or integrity. NOTE: The GCC project argues that this is a missed hardening bug and not a vulnerability by itself.
Remediation
There is no fixed version for Debian:11 gcc-9.
References
- https://security-tracker.debian.org/tracker/CVE-2023-4039
- https://developer.arm.com/Arm%20Security%20Center/GCC%20Stack%20Protector%20Vulnerability%20AArch64
- https://github.com/metaredteam/external-disclosures/security/advisories/GHSA-x7ch-h5rf-w2mf
- https://cert-portal.siemens.com/productcert/html/ssa-355557.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
low severity
- Vulnerable module: coreutils/coreutils
- Introduced through: coreutils/coreutils@8.32-4+b1
Detailed paths
-
Introduced through: nginx@1.21 › coreutils/coreutils@8.32-4+b1
NVD Description
Note: Versions mentioned in the description apply only to the upstream coreutils package and not the coreutils package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
In GNU Coreutils through 8.29, chown-core.c in chown and chgrp does not prevent replacement of a plain file with a symlink during use of the POSIX "-R -L" options, which allows local users to modify the ownership of arbitrary files by leveraging a race condition.
Remediation
There is no fixed version for Debian:11 coreutils.
References
low severity
- Vulnerable module: gnupg2/gpgv
- Introduced through: gnupg2/gpgv@2.2.27-2+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › gnupg2/gpgv@2.2.27-2+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnupg2 package and not the gnupg2 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
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:11 gnupg2.
References
low severity
- Vulnerable module: gnupg2/gpgv
- Introduced through: gnupg2/gpgv@2.2.27-2+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › gnupg2/gpgv@2.2.27-2+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnupg2 package and not the gnupg2 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
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:11 gnupg2.
References
low severity
- Vulnerable module: openldap/libldap-2.4-2
- Introduced through: openldap/libldap-2.4-2@2.4.57+dfsg-3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › openldap/libldap-2.4-2@2.4.57+dfsg-3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
slapd in OpenLDAP 2.4.45 and earlier creates a PID file after dropping privileges to a non-root account, which might allow local users to kill arbitrary processes by leveraging access to this non-root account for PID file modification before a root script executes a "kill cat /pathname" command, as demonstrated by openldap-initscript.
Remediation
There is no fixed version for Debian:11 openldap.
References
low severity
- Vulnerable module: pam/libpam-modules
- Introduced through: pam/libpam-modules@1.4.0-9+deb11u1, pam/libpam-modules-bin@1.4.0-9+deb11u1 and others
Detailed paths
-
Introduced through: nginx@1.21 › pam/libpam-modules@1.4.0-9+deb11u1
-
Introduced through: nginx@1.21 › pam/libpam-modules-bin@1.4.0-9+deb11u1
-
Introduced through: nginx@1.21 › pam/libpam-runtime@1.4.0-9+deb11u1
-
Introduced through: nginx@1.21 › pam/libpam0g@1.4.0-9+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream pam package and not the pam package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
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:11 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: shadow/login
- Introduced through: shadow/login@1:4.8.1-1 and shadow/passwd@1:4.8.1-1
Detailed paths
-
Introduced through: nginx@1.21 › shadow/login@1:4.8.1-1
-
Introduced through: nginx@1.21 › shadow/passwd@1:4.8.1-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream shadow package and not the shadow package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
shadow: TOCTOU (time-of-check time-of-use) race condition when copying and removing directory trees
Remediation
There is no fixed version for Debian:11 shadow.
References
- https://security-tracker.debian.org/tracker/CVE-2013-4235
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772@%3Cdev.mina.apache.org%3E
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-4235
- https://access.redhat.com/security/cve/cve-2013-4235
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2013-4235
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772%40%3Cdev.mina.apache.org%3E
- https://security.gentoo.org/glsa/202210-26
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
low severity
- Vulnerable module: coreutils/coreutils
- Introduced through: coreutils/coreutils@8.32-4+b1
Detailed paths
-
Introduced through: nginx@1.21 › coreutils/coreutils@8.32-4+b1
NVD Description
Note: Versions mentioned in the description apply only to the upstream coreutils package and not the coreutils package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
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:11 coreutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-5278
- https://access.redhat.com/security/cve/CVE-2025-5278
- https://bugzilla.redhat.com/show_bug.cgi?id=2368764
- http://www.openwall.com/lists/oss-security/2025/05/27/2
- http://www.openwall.com/lists/oss-security/2025/05/29/1
- https://cgit.git.savannah.gnu.org/cgit/coreutils.git/tree/NEWS?id=8c9602e3a145e9596dc1a63c6ed67865814b6633#n14
- http://www.openwall.com/lists/oss-security/2025/05/29/2
- https://debbugs.gnu.org/cgi/bugreport.cgi?bug=78507
- https://access.redhat.com/errata/RHSA-2026:28911
- https://access.redhat.com/errata/RHSA-2026:33124
- https://access.redhat.com/errata/RHSA-2026:33313
- https://access.redhat.com/errata/RHSA-2026:33612
- https://access.redhat.com/errata/RHSA-2026:34102
- https://access.redhat.com/errata/RHSA-2026:39981
- https://access.redhat.com/errata/RHSA-2026:44481
- https://access.redhat.com/errata/RHSA-2026:46836
- https://access.redhat.com/errata/RHSA-2026:50205
- https://access.redhat.com/errata/RHSA-2026:58981
- https://access.redhat.com/errata/RHSA-2026:69964
- https://access.redhat.com/errata/RHSA-2026:72502
- https://access.redhat.com/errata/RHSA-2026:82304
- https://access.redhat.com/errata/RHSA-2026:82322
- https://access.redhat.com/errata/RHSA-2026:82347
- https://access.redhat.com/errata/RHSA-2026:82354
- https://access.redhat.com/errata/RHSA-2026:82372
- https://access.redhat.com/errata/RHSA-2026:82857
- https://access.redhat.com/errata/RHSA-2026:82888
- https://cgit.git.savannah.gnu.org/cgit/coreutils.git/commit/?id=8c9602e3a145e9596dc1a63c6ed67865814b6633
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@247.3-7 and systemd/libudev1@247.3-7
Detailed paths
-
Introduced through: nginx@1.21 › systemd/libsystemd0@247.3-7
-
Introduced through: nginx@1.21 › systemd/libudev1@247.3-7
NVD Description
Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
systemd, when updating file permissions, allows local users to change the permissions and SELinux security contexts for arbitrary files via a symlink attack on unspecified files.
Remediation
There is no fixed version for Debian:11 systemd.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › glibc/libc-bin@2.31-13+deb11u3
-
Introduced through: nginx@1.21 › glibc/libc6@2.31-13+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
The glob implementation in the GNU C Library (aka glibc or libc6) allows remote authenticated users to cause a denial of service (CPU and memory consumption) via crafted glob expressions that do not match any pathnames, as demonstrated by glob expressions in STAT commands to an FTP daemon, a different vulnerability than CVE-2010-2632.
Remediation
There is no fixed version for Debian:11 glibc.
References
- 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.1-5
Detailed paths
-
Introduced through: nginx@1.21 › gnutls28/libgnutls30@3.7.1-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
The SSL protocol, as used in certain configurations in Microsoft Windows and Microsoft Internet Explorer, Mozilla Firefox, Google Chrome, Opera, and other products, encrypts data by using CBC mode with chained initialization vectors, which allows man-in-the-middle attackers to obtain plaintext HTTP headers via a blockwise chosen-boundary attack (BCBA) on an HTTPS session, in conjunction with JavaScript code that uses (1) the HTML5 WebSocket API, (2) the Java URLConnection API, or (3) the Silverlight WebClient API, aka a "BEAST" attack.
Remediation
There is no fixed version for Debian:11 gnutls28.
References
- 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: openldap/libldap-2.4-2
- Introduced through: openldap/libldap-2.4-2@2.4.57+dfsg-3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › openldap/libldap-2.4-2@2.4.57+dfsg-3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libldap in certain third-party OpenLDAP packages has a certificate-validation flaw when the third-party package is asserting RFC6125 support. It considers CN even when there is a non-matching subjectAltName (SAN). This is fixed in, for example, openldap-2.4.46-10.el8 in Red Hat Enterprise Linux.
Remediation
There is no fixed version for Debian:11 openldap.
References
- 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.2.4 and apt/libapt-pkg6.0@2.2.4
Detailed paths
-
Introduced through: nginx@1.21 › apt@2.2.4
-
Introduced through: nginx@1.21 › apt/libapt-pkg6.0@2.2.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream apt package and not the apt package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
It was found that apt-key in apt, all versions, do not correctly validate gpg keys with the master keyring, leading to a potential man-in-the-middle attack.
Remediation
There is no fixed version for Debian:11 apt.
References
- 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: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
- Fixed in: 7.74.0-1.3+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
When curl is used to retrieve and parse cookies from a HTTP(S) server, itaccepts cookies using control codes that when later are sent back to a HTTPserver might make the server return 400 responses. Effectively allowing a"sister site" to deny service to all siblings.
Remediation
Upgrade Debian:11 curl to version 7.74.0-1.3+deb11u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-35252
- http://seclists.org/fulldisclosure/2023/Jan/20
- http://seclists.org/fulldisclosure/2023/Jan/21
- https://hackerone.com/reports/1613943
- https://lists.debian.org/debian-lts-announce/2023/01/msg00028.html
- https://security.gentoo.org/glsa/202212-01
- https://security.netapp.com/advisory/ntap-20220930-0005/
- https://support.apple.com/kb/HT213603
- https://support.apple.com/kb/HT213604
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-419740.html
- https://cert-portal.siemens.com/productcert/html/ssa-558014.html
- https://cert-portal.siemens.com/productcert/html/ssa-892048.html
- https://cert-portal.siemens.com/productcert/html/ssa-942865.html
low severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
- Fixed in: 7.74.0-1.3+deb11u9
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
An information disclosure vulnerability exists in curl <v8.1.0 when doing HTTP(S) transfers, libcurl might erroneously use the read callback (CURLOPT_READFUNCTION) to ask for data to send, even when the CURLOPT_POSTFIELDS option has been set, if the same handle previously wasused to issue a PUT request which used that callback. This flaw may surprise the application and cause it to misbehave and either send off the wrong data or use memory after free or similar in the second transfer. The problem exists in the logic for a reused handle when it is (expected to be) changed from a PUT to a POST.
Remediation
Upgrade Debian:11 curl to version 7.74.0-1.3+deb11u9 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-28322
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/F4I75RDGX5ULSSCBE5BF3P5I5SFO7ULQ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/Z2LIWHWKOVH24COGGBCVOWDXXIUPKOMK/
- http://seclists.org/fulldisclosure/2023/Jul/47
- http://seclists.org/fulldisclosure/2023/Jul/48
- http://seclists.org/fulldisclosure/2023/Jul/52
- https://hackerone.com/reports/1954658
- https://lists.debian.org/debian-lts-announce/2023/12/msg00015.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/F4I75RDGX5ULSSCBE5BF3P5I5SFO7ULQ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/Z2LIWHWKOVH24COGGBCVOWDXXIUPKOMK/
- https://security.gentoo.org/glsa/202310-12
- https://security.netapp.com/advisory/ntap-20230609-0009/
- https://support.apple.com/kb/HT213843
- https://support.apple.com/kb/HT213844
- https://support.apple.com/kb/HT213845
low severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
- Fixed in: 7.74.0-1.3+deb11u10
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
This flaw allows an attacker to insert cookies at will into a running program using libcurl, if the specific series of conditions are met.
libcurl performs transfers. In its API, an application creates "easy handles" that are the individual handles for single transfers.
libcurl provides a function call that duplicates en easy handle called curl_easy_duphandle.
If a transfer has cookies enabled when the handle is duplicated, the
cookie-enable state is also cloned - but without cloning the actual
cookies. If the source handle did not read any cookies from a specific file on
disk, the cloned version of the handle would instead store the file name as
none (using the four ASCII letters, no quotes).
Subsequent use of the cloned handle that does not explicitly set a source to
load cookies from would then inadvertently load cookies from a file named
none - if such a file exists and is readable in the current directory of the
program using libcurl. And if using the correct file format of course.
Remediation
Upgrade Debian:11 curl to version 7.74.0-1.3+deb11u10 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-38546
- https://lists.debian.org/debian-lts-announce/2023/10/msg00016.html
- http://seclists.org/fulldisclosure/2024/Jan/34
- http://seclists.org/fulldisclosure/2024/Jan/37
- http://seclists.org/fulldisclosure/2024/Jan/38
- https://curl.se/docs/CVE-2023-38546.html
- https://forum.vmssoftware.com/viewtopic.php?f=8&t=8868
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OGMXNRNSJ4ETDK6FRNU3J7SABXPWCHSQ/
- https://support.apple.com/kb/HT214036
- https://support.apple.com/kb/HT214057
- https://support.apple.com/kb/HT214058
- https://support.apple.com/kb/HT214063
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-093430.html
- https://cert-portal.siemens.com/productcert/html/ssa-832273.html
- https://cert-portal.siemens.com/productcert/html/ssa-943925.html
low severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
- Fixed in: 7.74.0-1.3+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libcurl keeps previously used connections in a connection pool for subsequenttransfers to reuse, if one of them matches the setup.Due to errors in the logic, the config matching function did not take 'issuercert' into account and it compared the involved paths case insensitively,which could lead to libcurl reusing wrong connections.File paths are, or can be, case sensitive on many systems but not all, and caneven vary depending on used file systems.The comparison also didn't include the 'issuer cert' which a transfer can setto qualify how to verify the server certificate.
Remediation
Upgrade Debian:11 curl to version 7.74.0-1.3+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2021-22924
- https://security.netapp.com/advisory/ntap-20210902-0003/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/FRUCW2UVNYUDZF72DQLFQR4PJEC6CF7V/
- https://hackerone.com/reports/1223565
- https://www.oracle.com/security-alerts/cpuoct2021.html
- https://lists.apache.org/thread.html/r61db8e7dcb56dc000a5387a88f7a473bacec5ee01b9ff3f55308aacc@%3Cdev.kafka.apache.org%3E
- https://lists.apache.org/thread.html/r61db8e7dcb56dc000a5387a88f7a473bacec5ee01b9ff3f55308aacc@%3Cusers.kafka.apache.org%3E
- https://lists.apache.org/thread.html/rbf4ce74b0d1fa9810dec50ba3ace0caeea677af7c27a97111c06ccb7@%3Cdev.kafka.apache.org%3E
- https://lists.apache.org/thread.html/rbf4ce74b0d1fa9810dec50ba3ace0caeea677af7c27a97111c06ccb7@%3Cusers.kafka.apache.org%3E
- https://lists.debian.org/debian-lts-announce/2021/08/msg00017.html
- https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf
- https://cert-portal.siemens.com/productcert/pdf/ssa-484086.pdf
- https://cert-portal.siemens.com/productcert/pdf/ssa-732250.pdf
- https://lists.apache.org/thread.html/r61db8e7dcb56dc000a5387a88f7a473bacec5ee01b9ff3f55308aacc%40%3Cdev.kafka.apache.org%3E
- https://lists.apache.org/thread.html/r61db8e7dcb56dc000a5387a88f7a473bacec5ee01b9ff3f55308aacc%40%3Cusers.kafka.apache.org%3E
- https://lists.apache.org/thread.html/rbf4ce74b0d1fa9810dec50ba3ace0caeea677af7c27a97111c06ccb7%40%3Cdev.kafka.apache.org%3E
- https://lists.apache.org/thread.html/rbf4ce74b0d1fa9810dec50ba3ace0caeea677af7c27a97111c06ccb7%40%3Cusers.kafka.apache.org%3E
- https://lists.debian.org/debian-lts-announce/2022/08/msg00017.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FRUCW2UVNYUDZF72DQLFQR4PJEC6CF7V/
- https://www.debian.org/security/2022/dsa-5197
- https://www.oracle.com/security-alerts/cpujan2022.html
- https://cert-portal.siemens.com/productcert/html/ssa-389290.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-484086.html
- https://cert-portal.siemens.com/productcert/html/ssa-732250.html
low severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.10+dfsg-6.7+deb11u2
- Fixed in: 2.9.10+dfsg-6.7+deb11u10
Detailed paths
-
Introduced through: nginx@1.21 › libxml2@2.9.10+dfsg-6.7+deb11u2
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:11 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
Upgrade Debian:11 libxml2 to version 2.9.10+dfsg-6.7+deb11u10 or higher.
References
low severity
- Vulnerable module: gnupg2/gpgv
- Introduced through: gnupg2/gpgv@2.2.27-2+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › gnupg2/gpgv@2.2.27-2+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnupg2 package and not the gnupg2 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB.
Remediation
There is no fixed version for Debian:11 gnupg2.
References
- 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: libsepol/libsepol1
- Introduced through: libsepol/libsepol1@3.1-1
- Fixed in: 3.1-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › libsepol/libsepol1@3.1-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libsepol package and not the libsepol package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
The CIL compiler in SELinux 3.2 has a heap-based buffer over-read in ebitmap_match_any (called indirectly from cil_check_neverallow). This occurs because there is sometimes a lack of checks for invalid statements in an optional block.
Remediation
Upgrade Debian:11 libsepol to version 3.1-1+deb11u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2021-36087
- https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=32675
- https://github.com/google/oss-fuzz-vulns/blob/main/vulns/selinux/OSV-2021-585.yaml
- https://github.com/SELinuxProject/selinux/commit/bad0a746e9f4cf260dedba5828d9645d50176aac
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/U7ZYR3PIJ75N6U2IONJWCKZ5L2NKJTGR/
- https://lore.kernel.org/selinux/CAEN2sdqJKHvDzPnxS-J8grU8fSf32DDtx=kyh84OsCq_Vm+yaQ@mail.gmail.com/T/
- https://security.netapp.com/advisory/ntap-20250207-0004/
- https://lists.debian.org/debian-lts-announce/2024/10/msg00021.html
- https://github.com/SELinuxProject/selinux/commit/340f0eb7f3673e8aacaf0a96cbfcd4d12a405521
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/U7ZYR3PIJ75N6U2IONJWCKZ5L2NKJTGR/
- https://lore.kernel.org/selinux/CAEN2sdqJKHvDzPnxS-J8grU8fSf32DDtx=kyh84OsCq_Vm+yaQ%40mail.gmail.com/T/
- https://cert-portal.siemens.com/productcert/html/ssa-202008.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
low severity
- Vulnerable module: libsepol/libsepol1
- Introduced through: libsepol/libsepol1@3.1-1
- Fixed in: 3.1-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › libsepol/libsepol1@3.1-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libsepol package and not the libsepol package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
The CIL compiler in SELinux 3.2 has a use-after-free in __cil_verify_classperms (called from __verify_map_perm_classperms and hashtab_map).
Remediation
Upgrade Debian:11 libsepol to version 3.1-1+deb11u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2021-36085
- https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=31124
- https://github.com/google/oss-fuzz-vulns/blob/main/vulns/selinux/OSV-2021-421.yaml
- https://github.com/SELinuxProject/selinux/commit/2d35fcc7e9e976a2346b1de20e54f8663e8a6cba
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/U7ZYR3PIJ75N6U2IONJWCKZ5L2NKJTGR/
- https://security.netapp.com/advisory/ntap-20250207-0004/
- https://lists.debian.org/debian-lts-announce/2024/10/msg00021.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/U7ZYR3PIJ75N6U2IONJWCKZ5L2NKJTGR/
- https://cert-portal.siemens.com/productcert/html/ssa-202008.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
low severity
- Vulnerable module: libsepol/libsepol1
- Introduced through: libsepol/libsepol1@3.1-1
- Fixed in: 3.1-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › libsepol/libsepol1@3.1-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libsepol package and not the libsepol package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
The CIL compiler in SELinux 3.2 has a use-after-free in __cil_verify_classperms (called from __cil_verify_classpermission and __cil_pre_verify_helper).
Remediation
Upgrade Debian:11 libsepol to version 3.1-1+deb11u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2021-36084
- https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=31065
- https://github.com/google/oss-fuzz-vulns/blob/main/vulns/selinux/OSV-2021-417.yaml
- https://github.com/SELinuxProject/selinux/commit/f34d3d30c8325e4847a6b696fe7a3936a8a361f3
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/U7ZYR3PIJ75N6U2IONJWCKZ5L2NKJTGR/
- https://security.netapp.com/advisory/ntap-20250207-0004/
- https://lists.debian.org/debian-lts-announce/2024/10/msg00021.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/U7ZYR3PIJ75N6U2IONJWCKZ5L2NKJTGR/
- https://cert-portal.siemens.com/productcert/html/ssa-202008.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
low severity
- Vulnerable module: libsepol/libsepol1
- Introduced through: libsepol/libsepol1@3.1-1
- Fixed in: 3.1-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › libsepol/libsepol1@3.1-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libsepol package and not the libsepol package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
The CIL compiler in SELinux 3.2 has a use-after-free in cil_reset_classpermission (called from cil_reset_classperms_set and cil_reset_classperms_list).
Remediation
Upgrade Debian:11 libsepol to version 3.1-1+deb11u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2021-36086
- https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=32177
- https://github.com/google/oss-fuzz-vulns/blob/main/vulns/selinux/OSV-2021-536.yaml
- https://github.com/SELinuxProject/selinux/commit/c49a8ea09501ad66e799ea41b8154b6770fec2c8
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/U7ZYR3PIJ75N6U2IONJWCKZ5L2NKJTGR/
- https://lists.debian.org/debian-lts-announce/2024/10/msg00021.html
- https://security.netapp.com/advisory/ntap-20250207-0004/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/U7ZYR3PIJ75N6U2IONJWCKZ5L2NKJTGR/
- https://cert-portal.siemens.com/productcert/html/ssa-202008.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
low severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.10+dfsg-6.7+deb11u2
- Fixed in: 2.9.10+dfsg-6.7+deb11u10
Detailed paths
-
Introduced through: nginx@1.21 › libxml2@2.9.10+dfsg-6.7+deb11u2
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:11 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
Upgrade Debian:11 libxml2 to version 2.9.10+dfsg-6.7+deb11u10 or higher.
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
- https://cert-portal.siemens.com/productcert/html/ssa-253495.html
low severity
- Vulnerable module: ncurses/libtinfo6
- Introduced through: ncurses/libtinfo6@6.2+20201114-2, ncurses/ncurses-base@6.2+20201114-2 and others
Detailed paths
-
Introduced through: nginx@1.21 › ncurses/libtinfo6@6.2+20201114-2
-
Introduced through: nginx@1.21 › ncurses/ncurses-base@6.2+20201114-2
-
Introduced through: nginx@1.21 › ncurses/ncurses-bin@6.2+20201114-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
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:11 ncurses.
References
- https://security-tracker.debian.org/tracker/CVE-2025-6141
- https://invisible-island.net/ncurses/NEWS.html#index-t20250329
- https://lists.gnu.org/archive/html/bug-ncurses/2025-03/msg00107.html
- https://lists.gnu.org/archive/html/bug-ncurses/2025-03/msg00109.html
- https://lists.gnu.org/archive/html/bug-ncurses/2025-03/msg00114.html
- https://vuldb.com/?ctiid.312610
- https://vuldb.com/?id.312610
- https://vuldb.com/?submit.593000
- https://www.gnu.org/
- https://cert-portal.siemens.com/productcert/html/ssa-089022.html
- https://cert-portal.siemens.com/productcert/html/ssa-253495.html
low severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.32.1-4+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › perl/perl-base@5.32.1-4+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
_is_safe in the File::Temp module for Perl does not properly handle symlinks.
Remediation
There is no fixed version for Debian:11 perl.
References
- 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.8.1-1 and shadow/passwd@1:4.8.1-1
- Fixed in: 1:4.8.1-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › shadow/login@1:4.8.1-1
-
Introduced through: nginx@1.21 › shadow/passwd@1:4.8.1-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream shadow package and not the shadow package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
In Shadow 4.13, it is possible to inject control characters into fields provided to the SUID program chfn (change finger). Although it is not possible to exploit this directly (e.g., adding a new user fails because \n is in the block list), it is possible to misrepresent the /etc/passwd file when viewed. Use of \r manipulations and Unicode characters to work around blocking of the : character make it possible to give the impression that a new user has been added. In other words, an adversary may be able to convince a system administrator to take the system offline (an indirect, social-engineered denial of service) by demonstrating that "cat /etc/passwd" shows a rogue user account.
Remediation
Upgrade Debian:11 shadow to version 1:4.8.1-1+deb11u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-29383
- https://lists.debian.org/debian-lts-announce/2025/04/msg00026.html
- https://github.com/shadow-maint/shadow/commit/e5905c4b84d4fb90aefcd96ee618411ebfac663d
- https://github.com/shadow-maint/shadow/pull/687
- 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
- https://cert-portal.siemens.com/productcert/html/ssa-202008.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@247.3-7 and systemd/libudev1@247.3-7
Detailed paths
-
Introduced through: nginx@1.21 › systemd/libsystemd0@247.3-7
-
Introduced through: nginx@1.21 › systemd/libudev1@247.3-7
NVD Description
Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
In systemd 259, systemd-journald can send ANSI escape sequences to the terminals of arbitrary users when a "logger -p emerg" command is executed, if ForwardToWall=yes is set.
Remediation
There is no fixed version for Debian:11 systemd.
References
low severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A weakness has been identified in LibTIFF 4.7.0. This affects the function main of the file tiffcrop.c of the component tiffcrop. Executing manipulation can lead to memory corruption. The attack can only be executed locally. The exploit has been made available to the public and could be exploited.
Remediation
There is no fixed version for Debian:11 tiff.
References
- https://security-tracker.debian.org/tracker/CVE-2025-8961
- http://www.libtiff.org/
- https://drive.google.com/file/d/15L4q2eD8GX3Aj3z6SWC3_FbqaM1ChUx2/view?usp=sharing
- https://gitlab.com/libtiff/libtiff/-/issues/721
- https://vuldb.com/?ctiid.319955
- https://vuldb.com/?id.319955
- https://vuldb.com/?submit.627957
- https://gitlab.com/libtiff/libtiff/-/issues/721#note_2670686960
low severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
An issue was found in the tiffcp utility distributed by the libtiff package where a crafted TIFF file on processing may cause a heap-based buffer overflow leads to an application crash.
Remediation
There is no fixed version for Debian:11 tiff.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
- Fixed in: 7.74.0-1.3+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
curl 7.7 through 7.76.1 suffers from an information disclosure when the -t command line option, known as CURLOPT_TELNETOPTIONS in libcurl, is used to send variable=content pairs to TELNET servers. Due to a flaw in the option parser for sending NEW_ENV variables, libcurl could be made to pass on uninitialized data from a stack based buffer to the server, resulting in potentially revealing sensitive internal information to the server using a clear-text network protocol.
Remediation
Upgrade Debian:11 curl to version 7.74.0-1.3+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2021-22898
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/FRUCW2UVNYUDZF72DQLFQR4PJEC6CF7V/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/POOC3UV7V6L4CJ5KA2PTWTNUV5Y72T3Q/
- https://curl.se/docs/CVE-2021-22898.html
- https://github.com/curl/curl/commit/39ce47f219b09c380b81f89fe54ac586c8db6bde
- https://hackerone.com/reports/1176461
- https://lists.apache.org/thread.html/rc713534b10f9daeee2e0990239fa407e2118e4aa9e88a7041177497c@%3Cissues.guacamole.apache.org%3E
- https://lists.debian.org/debian-lts-announce/2021/08/msg00017.html
- http://www.openwall.com/lists/oss-security/2021/07/21/4
- https://www.oracle.com//security-alerts/cpujul2021.html
- https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf
- https://lists.apache.org/thread.html/rc713534b10f9daeee2e0990239fa407e2118e4aa9e88a7041177497c%40%3Cissues.guacamole.apache.org%3E
- https://lists.debian.org/debian-lts-announce/2022/08/msg00017.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FRUCW2UVNYUDZF72DQLFQR4PJEC6CF7V/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/POOC3UV7V6L4CJ5KA2PTWTNUV5Y72T3Q/
- https://www.debian.org/security/2022/dsa-5197
- https://www.oracle.com/security-alerts/cpuapr2022.html
- https://www.oracle.com/security-alerts/cpujan2022.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
low severity
- Vulnerable module: libxslt/libxslt1.1
- Introduced through: libxslt/libxslt1.1@1.1.34-4
Detailed paths
-
Introduced through: nginx@1.21 › libxslt/libxslt1.1@1.1.34-4
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:11 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:11 libxslt.
References
- https://security-tracker.debian.org/tracker/CVE-2025-11731
- https://access.redhat.com/security/cve/CVE-2025-11731
- https://bugzilla.redhat.com/show_bug.cgi?id=2403688
- https://gitlab.gnome.org/GNOME/libxslt/-/merge_requests/78
- https://gitlab.gnome.org/GNOME/libxslt/-/issues/151
- https://access.redhat.com/errata/RHSA-2026:11015
low severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.10+dfsg-6.7+deb11u2
- Fixed in: 2.9.10+dfsg-6.7+deb11u10
Detailed paths
-
Introduced through: nginx@1.21 › libxml2@2.9.10+dfsg-6.7+deb11u2
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:11 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
Upgrade Debian:11 libxml2 to version 2.9.10+dfsg-6.7+deb11u10 or higher.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.10-2+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › expat/libexpat1@2.2.10-2+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
In libexpat before 2.7.4, XML_ExternalEntityParserCreate does not copy unknown encoding handler user data.
Remediation
There is no fixed version for Debian:11 expat.
References
low severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.10+dfsg-6.7+deb11u2
- Fixed in: 2.9.10+dfsg-6.7+deb11u8
Detailed paths
-
Introduced through: nginx@1.21 › libxml2@2.9.10+dfsg-6.7+deb11u2
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:11 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:11 libxml2 to version 2.9.10+dfsg-6.7+deb11u8 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-6170
- https://bugzilla.redhat.com/show_bug.cgi?id=2372952
- https://access.redhat.com/security/cve/CVE-2025-6170
- https://lists.debian.org/debian-lts-announce/2025/07/msg00014.html
- https://gitlab.gnome.org/GNOME/libxml2/-/issues/941
- https://access.redhat.com/errata/RHSA-2026:7519
- https://cert-portal.siemens.com/productcert/html/ssa-253495.html
- https://access.redhat.com/errata/RHSA-2026:36734
- https://access.redhat.com/errata/RHSA-2026:39304
- https://access.redhat.com/errata/RHSA-2026:39317
- https://access.redhat.com/errata/RHSA-2026:44481
- https://access.redhat.com/errata/RHSA-2026:46836
- https://access.redhat.com/errata/RHSA-2026:53371
- https://access.redhat.com/errata/RHSA-2026:58981
- https://access.redhat.com/errata/RHSA-2026:70596
- https://access.redhat.com/errata/RHSA-2026:70639
- https://access.redhat.com/errata/RHSA-2026:72394
- https://access.redhat.com/errata/RHSA-2026:72395
- https://access.redhat.com/errata/RHSA-2026:72399
- https://access.redhat.com/errata/RHSA-2026:72470
- https://access.redhat.com/errata/RHSA-2026:72475
- https://access.redhat.com/errata/RHSA-2026:72476
- https://access.redhat.com/errata/RHSA-2026:72502
- https://access.redhat.com/errata/RHSA-2026:73859
- https://access.redhat.com/errata/RHSA-2026:73909
- https://access.redhat.com/errata/RHSA-2026:73929
- https://access.redhat.com/errata/RHSA-2026:73930
- https://access.redhat.com/errata/RHSA-2026:73959
- https://access.redhat.com/errata/RHSA-2026:73960
- https://access.redhat.com/errata/RHSA-2026:73961
- https://access.redhat.com/errata/RHSA-2026:73962
- https://access.redhat.com/errata/RHSA-2026:74359
- https://access.redhat.com/errata/RHSA-2026:74360
- https://access.redhat.com/errata/RHSA-2026:74361
- https://access.redhat.com/errata/RHSA-2026:74362
- https://access.redhat.com/errata/RHSA-2026:74363
- https://access.redhat.com/errata/RHSA-2026:74364
- https://access.redhat.com/errata/RHSA-2026:74365
- https://access.redhat.com/errata/RHSA-2026:74450
- https://access.redhat.com/errata/RHSA-2026:74458
- https://access.redhat.com/errata/RHSA-2026:74459
- https://access.redhat.com/errata/RHSA-2026:74460
- https://access.redhat.com/errata/RHSA-2026:74461
- https://access.redhat.com/errata/RHSA-2026:74462
- https://access.redhat.com/errata/RHSA-2026:74463
- https://access.redhat.com/errata/RHSA-2026:74674
- https://access.redhat.com/errata/RHSA-2026:74677
- https://access.redhat.com/errata/RHSA-2026:74678
- https://access.redhat.com/errata/RHSA-2026:74679
- https://access.redhat.com/errata/RHSA-2026:74681
- https://access.redhat.com/errata/RHSA-2026:74683
- https://access.redhat.com/errata/RHSA-2026:74685
- https://access.redhat.com/errata/RHSA-2026:74687
- https://access.redhat.com/errata/RHSA-2026:74688
- https://access.redhat.com/errata/RHSA-2026:74771
- https://access.redhat.com/errata/RHSA-2026:75652
- https://access.redhat.com/errata/RHSA-2026:75654
- https://access.redhat.com/errata/RHSA-2026:75655
- https://access.redhat.com/errata/RHSA-2026:75657
- https://access.redhat.com/errata/RHSA-2026:75658
- https://access.redhat.com/errata/RHSA-2026:75659
- https://access.redhat.com/errata/RHSA-2026:75660
- https://access.redhat.com/errata/RHSA-2026:76042
- https://access.redhat.com/errata/RHSA-2026:79118
- https://access.redhat.com/errata/RHSA-2026:79120
- https://access.redhat.com/errata/RHSA-2026:79119
- https://access.redhat.com/errata/RHSA-2026:79121
- https://access.redhat.com/errata/RHSA-2026:80756
- https://access.redhat.com/errata/RHSA-2026:81127
- https://access.redhat.com/errata/RHSA-2026:82059
- https://access.redhat.com/errata/RHSA-2026:82061
- https://access.redhat.com/errata/RHSA-2026:82066
- https://access.redhat.com/errata/RHSA-2026:82304
- https://access.redhat.com/errata/RHSA-2026:82322
- https://access.redhat.com/errata/RHSA-2026:82336
- https://access.redhat.com/errata/RHSA-2026:82347
- https://access.redhat.com/errata/RHSA-2026:82354
- https://access.redhat.com/errata/RHSA-2026:82368
- https://access.redhat.com/errata/RHSA-2026:82371
- https://access.redhat.com/errata/RHSA-2026:82372
- https://access.redhat.com/errata/RHSA-2026:82415
- https://access.redhat.com/errata/RHSA-2026:82857
- https://access.redhat.com/errata/RHSA-2026:82888
low severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
- Fixed in: 4.2.0-1+deb11u7
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A vulnerability was found in LibTIFF up to 4.7.0. It has been declared as problematic. Affected by this vulnerability is the function t2p_read_tiff_init of the file tools/tiff2pdf.c of the component fax2ps. The manipulation leads to null pointer dereference. The attack needs to be approached locally. The complexity of an attack is rather high. The exploitation appears to be difficult. The patch is named 2ebfffb0e8836bfb1cd7d85c059cd285c59761a4. It is recommended to apply a patch to fix this issue.
Remediation
Upgrade Debian:11 tiff to version 4.2.0-1+deb11u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-13978
- http://www.libtiff.org/
- https://gitlab.com/libtiff/libtiff/-/commit/2ebfffb0e8836bfb1cd7d85c059cd285c59761a4
- https://gitlab.com/libtiff/libtiff/-/merge_requests/667
- https://vuldb.com/?ctiid.318355
- https://vuldb.com/?id.318355
- https://vuldb.com/?submit.624562
- https://lists.debian.org/debian-lts-announce/2025/09/msg00031.html
- https://gitlab.com/libtiff/libtiff/-/issues/649
low severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A vulnerability classified as problematic was found in libtiff 4.6.0. This vulnerability affects the function PS_Lvl2page of the file tools/tiff2ps.c of the component tiff2ps. The manipulation leads to null pointer dereference. It is possible to launch the attack on the local host. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The name of the patch is 6ba36f159fd396ad11bf6b7874554197736ecc8b. It is recommended to apply a patch to fix this issue. One of the maintainers explains, that "[t]his error only occurs if DEFER_STRILE_LOAD (defer-strile-load:BOOL=ON) or TIFFOpen( .. "rD") option is used."
Remediation
There is no fixed version for Debian:11 tiff.
References
- https://security-tracker.debian.org/tracker/CVE-2025-8534
- http://www.libtiff.org/
- https://drive.google.com/file/d/15JPA3kLYiYD-nRNJ8y8HmnYjhv9NE7k6/view?usp=drive_link
- https://gitlab.com/libtiff/libtiff/-/commit/6ba36f159fd396ad11bf6b7874554197736ecc8b
- https://gitlab.com/libtiff/libtiff/-/merge_requests/746
- https://vuldb.com/?ctiid.318664
- https://vuldb.com/?id.318664
- https://gitlab.com/libtiff/libtiff/-/issues/718
- https://vuldb.com/?submit.617831
low severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw has been found in LibTIFF 4.7.0. This affects the function _TIFFmallocExt/_TIFFCheckRealloc/TIFFHashSetNew/InitCCITTFax3 of the file tools/tiffcmp.c of the component tiffcmp. Executing manipulation can lead to memory leak. The attack is restricted to local execution. This attack is characterized by high complexity. It is indicated that the exploitability is difficult. The exploit has been published and may be used. There is ongoing doubt regarding the real existence of this vulnerability. This patch is called ed141286a37f6e5ddafb5069347ff5d587e7a4e0. It is best practice to apply a patch to resolve this issue. A researcher disputes the security impact of this issue, because "this is a memory leak on a command line tool that is about to exit anyway". In the reply the project maintainer declares this issue as "a simple 'bug' when leaving the command line tool and (...) not a security issue at all".
Remediation
There is no fixed version for Debian:11 tiff.
References
- https://security-tracker.debian.org/tracker/CVE-2025-9165
- http://www.libtiff.org/
- https://drive.google.com/file/d/1FWhmkzksH8-qU0ZM6seBzGNB3aPnX3G8/view?usp=sharing
- https://gitlab.com/libtiff/libtiff/-/commit/ed141286a37f6e5ddafb5069347ff5d587e7a4e0
- https://gitlab.com/libtiff/libtiff/-/issues/728
- https://gitlab.com/libtiff/libtiff/-/merge_requests/747
- https://vuldb.com/?ctiid.320543
- https://vuldb.com/?id.320543
- https://vuldb.com/?submit.630506
- https://vuldb.com/?submit.630507
- https://gitlab.com/libtiff/libtiff/-/issues/728#note_2709263214
low severity
- Vulnerable module: bzip2/libbz2-1.0
- Introduced through: bzip2/libbz2-1.0@1.0.8-4
Detailed paths
-
Introduced through: nginx@1.21 › bzip2/libbz2-1.0@1.0.8-4
NVD Description
Note: Versions mentioned in the description apply only to the upstream bzip2 package and not the bzip2 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
bzip2 contains an off‑by‑one error in the bzip2recover utility. When processing a specially crafted file, the application performs an out‑of‑bounds write to a global buffer, resulting in memory corruption and a crash (denial of service).
This issue was fixed in bzip2 patch 35d122a3df8b0cc4082a4d89fdc6ee99f375fe67
Remediation
There is no fixed version for Debian:11 bzip2.
References
- https://security-tracker.debian.org/tracker/CVE-2026-42250
- https://cert.pl/en/posts/2026/05/CVE-2026-42250/
- https://sourceware.org/bzip2/
- https://inbox.sourceware.org/bzip2-devel/20260528145407.293768-1-mark@klomp.org/
- https://sourceware.org/cgit/bzip2/commit/?id=35d122a3df8b0cc4082a4d89fdc6ee99f375fe67
low severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
When reusing a libcurl handle for sequential transfers driven by
environment-variable proxy configuration, libcurl fails to clear the proxy
authentication state between requests. Specifically, if the initial transfer
authenticates against proxyA using Digest auth, a subsequent transfer routed
through proxyB erroneously leaks the Proxy-Authorization: header intended
solely for proxyA.
Remediation
There is no fixed version for Debian:11 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Successfully using libcurl to do a transfer to a specific HTTP origin
(hostA) with Digest authentication and then changing the origin to a
different one (hostB) for a second transfer, reusing the same handle, makes
libcurl wrongly pass on the Authorization: header field meant for hostA,
to hostB.
Remediation
There is no fixed version for Debian:11 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
When libcurl is asked to perform automatic gzip decompression of
content-encoded HTTP responses with the CURLOPT_ACCEPT_ENCODING option,
using zlib 1.2.0.3 or older, an attacker-controlled integer overflow would
make libcurl perform a buffer overflow.
Remediation
There is no fixed version for Debian:11 curl.
References
- https://security-tracker.debian.org/tracker/CVE-2025-0725
- https://curl.se/docs/CVE-2025-0725.html
- https://curl.se/docs/CVE-2025-0725.json
- https://hackerone.com/reports/2956023
- http://www.openwall.com/lists/oss-security/2025/02/05/3
- http://www.openwall.com/lists/oss-security/2025/02/06/2
- http://www.openwall.com/lists/oss-security/2025/02/06/4
- https://security.netapp.com/advisory/ntap-20250306-0009/
- https://github.com/curl/curl/commit/76f83f0db23846e254d940ec7
- https://cert-portal.siemens.com/productcert/html/ssa-089022.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
low severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
- Fixed in: 7.74.0-1.3+deb11u14
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
When curl is told to use the Certificate Status Request TLS extension, often referred to as OCSP stapling, to verify that the server certificate is valid, it might fail to detect some OCSP problems and instead wrongly consider the response as fine. If the returned status reports another error than 'revoked' (like for example 'unauthorized') it is not treated as a bad certficate.
Remediation
Upgrade Debian:11 curl to version 7.74.0-1.3+deb11u14 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-8096
- https://curl.se/docs/CVE-2024-8096.html
- https://curl.se/docs/CVE-2024-8096.json
- https://hackerone.com/reports/2669852
- http://www.openwall.com/lists/oss-security/2024/09/11/1
- https://lists.debian.org/debian-lts-announce/2024/11/msg00008.html
- https://security.netapp.com/advisory/ntap-20241011-0005/
- https://cert-portal.siemens.com/productcert/html/ssa-089022.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
low severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
curl's code for managing SSH connections when SFTP was done using the wolfSSH powered backend was flawed and missed host verification mechanisms.
This prevents curl from detecting MITM attackers and more.
Remediation
There is no fixed version for Debian:11 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
When doing multi-threaded LDAPS transfers (LDAP over TLS) with libcurl, changing TLS options in one thread would inadvertently change them globally and therefore possibly also affect other concurrently setup transfers.
Disabling certificate verification for a specific transfer could unintentionally disable the feature for other threads as well.
Remediation
There is no fixed version for Debian:11 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
When doing SSH-based transfers using either SCP or SFTP, and setting the known_hosts file, libcurl could still mistakenly accept connecting to hosts not present in the specified file if they were added as recognized in the libssh global known_hosts file.
Remediation
There is no fixed version for Debian:11 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
When doing SSH-based transfers using either SCP or SFTP, and asked to do public key authentication, curl would wrongly still ask and authenticate using a locally running SSH agent.
Remediation
There is no fixed version for Debian:11 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libcurl can in some circumstances reuse the wrong connection when asked to do an Negotiate-authenticated HTTP or HTTPS request.
libcurl features a pool of recent connections so that subsequent requests can reuse an existing connection to avoid overhead.
When reusing a connection a range of criterion must first be met. Due to a logical error in the code, a request that was issued by an application could wrongfully reuse an existing connection to the same server that was authenticated using different credentials. One underlying reason being that Negotiate sometimes authenticates connections and not requests, contrary to how HTTP is designed to work.
An application that allows Negotiate authentication to a server (that responds
wanting Negotiate) with user1:password1 and then does another operation to
the same server also using Negotiate but with user2:password2 (while the
previous connection is still alive) - the second request wrongly reused the
same connection and since it then sees that the Negotiate negotiation is
already made, it sends the request over that connection thinking it uses
the user2 credentials when it is in fact still using the connection
authenticated for user1...
The set of authentication methods to use is set with CURLOPT_HTTPAUTH.
Applications can disable libcurl's reuse of connections and thus mitigate this
problem, by using one of the following libcurl options to alter how
connections are or are not reused: CURLOPT_FRESH_CONNECT,
CURLOPT_MAXCONNECTS and CURLMOPT_MAX_HOST_CONNECTIONS (if using the
curl_multi API).
Remediation
There is no fixed version for Debian:11 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
When an OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer performs a redirect to a second URL, curl could leak that token to the second hostname under some circumstances.
If the hostname that the first request is redirected to has information in the
used .netrc file, with either of the machine or default keywords, curl
would pass on the bearer token set for the first host also to the second one.
Remediation
There is no fixed version for Debian:11 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
curl would wrongly reuse an existing HTTP proxy connection doing CONNECT to a server, even if the new request uses different credentials for the HTTP proxy. The proper behavior is to create or use a separate connection.
Remediation
There is no fixed version for Debian:11 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
When asked to both use a .netrc file for credentials and to follow HTTP
redirects, libcurl could leak the password used for the first host to the
followed-to host under certain circumstances.
Remediation
There is no fixed version for Debian:11 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libcurl might in some circumstances reuse the wrong connection when asked to do Negotiate-authenticated ones, even when they are set to use different "services".
libcurl features a pool of recent connections so that subsequent requests can reuse an existing connection to avoid overhead.
When reusing a connection a range of criteria must be met. Due to a logical error in the code, a request that was issued by an application could wrongfully reuse an existing connection to the same server that was authenticated using different services.
Remediation
There is no fixed version for Debian:11 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw in curl’s cookie parsing logic allows a malicious HTTP server to set "super cookies" that bypass the Public Suffix List check. This enables an attacker-controlled origin to inject cookies that curl subsequently scopes and transmits to unrelated third-party domains.
Remediation
There is no fixed version for Debian:11 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libcurl would reuse a previously created connection even when some mTLS config related option had been changed that should have prohibited reuse.
libcurl keeps previously used connections in a connection pool for subsequent transfers to reuse if one of them matches the setup. However, some TLS settings related to client certificates were left out from the configuration match checks, making them match too easily. In particular options related to the private key.
Remediation
There is no fixed version for Debian:11 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
When a libcurl-based application performs transfers via SCP:// or SFTP://
and utilizes the CURLOPT_SSH_KEYFUNCTION callback, it may silently accept an
untrusted server. This vulnerability occurs when a server presents a host key
type that does not match the specific key type already recorded for that host
in the known_hosts file. Instead of rejecting the mismatch, the callback
mechanism fails to properly enforce the restriction, allowing the connection
to succeed without warning and risking a potential man-in-the-middle attack.
Remediation
There is no fixed version for Debian:11 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A vulnerability exists where a connection requiring TLS incorrectly reuses an existing unencrypted connection from the same connection pool. If an initial transfer is made in clear-text (via IMAP, SMTP, or POP3), a subsequent request to that same host bypasses the TLS requirement and instead transmit data unencrypted.
Remediation
There is no fixed version for Debian:11 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A vulnerability exists where a new transfer that uses STARTTLS to upgrade the connection might reuse an existing live connection even though the TLS configuration mismatches so it should not.
Remediation
There is no fixed version for Debian:11 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libcurl skips the certificate verification for a QUIC connection under certain conditions, when built to use wolfSSL. If told to use an unknown/bad cipher or curve, the error path accidentally skips the verification and returns OK, thus ignoring any certificate problems.
Remediation
There is no fixed version for Debian:11 curl.
References
- https://security-tracker.debian.org/tracker/CVE-2024-2379
- http://seclists.org/fulldisclosure/2024/Jul/18
- http://seclists.org/fulldisclosure/2024/Jul/19
- http://seclists.org/fulldisclosure/2024/Jul/20
- http://www.openwall.com/lists/oss-security/2024/03/27/2
- https://curl.se/docs/CVE-2024-2379.html
- https://curl.se/docs/CVE-2024-2379.json
- https://hackerone.com/reports/2410774
- https://security.netapp.com/advisory/ntap-20240531-0001/
- https://support.apple.com/kb/HT214118
- https://support.apple.com/kb/HT214119
- https://support.apple.com/kb/HT214120
- https://cert-portal.siemens.com/productcert/html/ssa-331112.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-417159.html
low severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
curl might erroneously pass on credentials for a first proxy to a second proxy.
This can happen when the following conditions are true:
- curl is setup to use specific different proxies for different URL schemes
- the first proxy needs credentials
- the second proxy uses no credentials
- while using the first proxy (using say
http://), curl is asked to follow a redirect to a URL using another scheme (sayhttps://), accessed using a second, different, proxy
Remediation
There is no fixed version for Debian:11 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
- Fixed in: 7.74.0-1.3+deb11u12
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
When an application tells libcurl it wants to allow HTTP/2 server push, and the amount of received headers for the push surpasses the maximum allowed limit (1000), libcurl aborts the server push. When aborting, libcurl inadvertently does not free all the previously allocated headers and instead leaks the memory. Further, this error condition fails silently and is therefore not easily detected by an application.
Remediation
Upgrade Debian:11 curl to version 7.74.0-1.3+deb11u12 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-2398
- http://seclists.org/fulldisclosure/2024/Jul/18
- http://seclists.org/fulldisclosure/2024/Jul/19
- http://seclists.org/fulldisclosure/2024/Jul/20
- http://www.openwall.com/lists/oss-security/2024/03/27/3
- https://curl.se/docs/CVE-2024-2398.html
- https://curl.se/docs/CVE-2024-2398.json
- https://hackerone.com/reports/2402845
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/2D44YLAUFJU6BZ4XFG2FYV7SBKXB5IZ6/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GMD6UYKCCRCYETWQZUJ65ZRFULT6SHLI/
- https://security.netapp.com/advisory/ntap-20240503-0009/
- https://support.apple.com/kb/HT214118
- https://support.apple.com/kb/HT214119
- https://support.apple.com/kb/HT214120
- https://cert-portal.siemens.com/productcert/html/ssa-331112.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-417159.html
low severity
- Vulnerable module: curl
- Introduced through: curl@7.74.0-1.3+deb11u1 and curl/libcurl4@7.74.0-1.3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › curl@7.74.0-1.3+deb11u1
-
Introduced through: nginx@1.21 › curl/libcurl4@7.74.0-1.3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
When an OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer performs a cross-protocol redirect to a second URL that uses an IMAP, LDAP, POP3 or SMTP scheme, curl might wrongly pass on the bearer token to the new target host.
Remediation
There is no fixed version for Debian:11 curl.
References
low severity
- Vulnerable module: diffutils
- Introduced through: diffutils@1:3.7-5
Detailed paths
-
Introduced through: nginx@1.21 › diffutils@1:3.7-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream diffutils package and not the diffutils package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
diff3 tool from GNU diffutils is vulnerable to a heap‑based buffer overflow due to multiple signed integer overflows in line‑mapping calculations. Incorrect arithmetic in mapping line ranges can result in corrupted values being used for memory allocation and loop bounds. When processing crafted diff output, these overflows may cause the application to allocate insufficient memory and subsequently perform out‑of‑bounds writes during internal processing. An attacker who can control the output of the diff program used by diff3 (e.g. via --diff-program pointing to a malicious script) can trigger out-of-bounds writes, resulting in a crash and potentially remote code execution depending on the environment.
This issue has been fixed in commit 9ff04d5b84743e331e80b589335a52c5480d1815
NOTE: The project maintainers claim that this is not a security issue. They state that the worst outcome this issue can cause is a crash of diff and that it cannot be used to escalate privileges.
Remediation
There is no fixed version for Debian:11 diffutils.
References
- https://security-tracker.debian.org/tracker/CVE-2026-53910
- https://cert.pl/en/posts/2026/07/CVE-2026-53910
- https://cgit.git.savannah.gnu.org/cgit/diffutils.git/commit/?id=73ed7ce85cc78effb94daf028c9af6b4e5252e50
- https://cgit.git.savannah.gnu.org/cgit/diffutils.git/commit/?id=9ff04d5b84743e331e80b589335a52c5480d1815
- https://git.savannah.gnu.org/cgit/diffutils.git/
low severity
- Vulnerable module: dpkg
- Introduced through: dpkg@1.20.10
- Fixed in: 1.20.14
Detailed paths
-
Introduced through: nginx@1.21 › dpkg@1.20.10
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:11 relevant fixed versions and status.
It was discovered that dpkg-deb does not properly sanitize directory permissions when extracting a control member into a temporary directory, which is documented as being a safe operation even on untrusted data. This may result in leaving temporary files behind on cleanup. Given automated and repeated execution of dpkg-deb commands on adversarial .deb packages or with well compressible files, placed inside a directory with permissions not allowing removal by a non-root user, this can end up in a DoS scenario due to causing disk quota exhaustion or disk full conditions.
Remediation
Upgrade Debian:11 dpkg to version 1.20.14 or higher.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.10-2+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › expat/libexpat1@2.2.10-2+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libexpat in Expat before 2.7.2 allows attackers to trigger large dynamic memory allocations via a small document that is submitted for parsing.
Remediation
There is no fixed version for Debian:11 expat.
References
- https://security-tracker.debian.org/tracker/CVE-2025-59375
- https://github.com/libexpat/libexpat/blob/676a4c531ec768732fac215da9730b5f50fbd2bf/expat/Changes#L45-L74
- https://github.com/libexpat/libexpat/blob/R_2_7_2/expat/Changes
- https://github.com/libexpat/libexpat/issues/1018
- https://github.com/libexpat/libexpat/pull/1034
- https://issues.oss-fuzz.com/issues/439133977
- http://www.openwall.com/lists/oss-security/2025/09/16/2
- http://www.openwall.com/lists/oss-security/2026/05/01/5
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-089022.html
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.10-2+deb11u3
- Fixed in: 2.2.10-2+deb11u7
Detailed paths
-
Introduced through: nginx@1.21 › expat/libexpat1@2.2.10-2+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
An issue was discovered in libexpat before 2.6.4. There is a crash within the XML_ResumeParser function because XML_StopParser can stop/suspend an unstarted parser.
Remediation
Upgrade Debian:11 expat to version 2.2.10-2+deb11u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-50602
- https://github.com/libexpat/libexpat/pull/915
- https://lists.debian.org/debian-lts-announce/2025/04/msg00040.html
- https://security.netapp.com/advisory/ntap-20250404-0008/
- https://cert-portal.siemens.com/productcert/html/ssa-202008.html
- https://cert-portal.siemens.com/productcert/html/ssa-355557.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.10-2+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › expat/libexpat1@2.2.10-2+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
In libexpat before 2.8.2, there is a heap-based buffer overflow in doProlog in xmlparse.c because scaffold backing array reallocation is mishandled when there is data-structure sharing across parsers.
Remediation
There is no fixed version for Debian:11 expat.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.10-2+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › expat/libexpat1@2.2.10-2+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libexpat before 2.8.0 uses insufficient entropy, and thus hash flooding can occur via a crafted XML document.
Remediation
There is no fixed version for Debian:11 expat.
References
- https://security-tracker.debian.org/tracker/CVE-2026-41080
- https://github.com/libexpat/libexpat/issues/47
- https://github.com/libexpat/libexpat/pull/1183
- https://blog.hartwork.org/posts/expat-2-8-0-released/
- https://www.openwall.com/lists/oss-security/2026/04/26/1
- http://www.openwall.com/lists/oss-security/2026/04/26/1
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.10-2+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › expat/libexpat1@2.2.10-2+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libexpat before 2.8.2 has an integer overflow in copyString.
Remediation
There is no fixed version for Debian:11 expat.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.10-2+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › expat/libexpat1@2.2.10-2+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libexpat before 2.8.2 has an integer overflow in getAttributeId.
Remediation
There is no fixed version for Debian:11 expat.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.10-2+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › expat/libexpat1@2.2.10-2+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libexpat before 2.8.2 has an integer overflow in storeAtts.
Remediation
There is no fixed version for Debian:11 expat.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.10-2+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › expat/libexpat1@2.2.10-2+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libexpat before 2.8.2 has an integer overflow in doProlog that is related to storeEntityValue and entity textLen.
Remediation
There is no fixed version for Debian:11 expat.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.10-2+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › expat/libexpat1@2.2.10-2+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
xmlwf in libexpat before 2.8.2 has an integer overflow in resolveSystemId.
Remediation
There is no fixed version for Debian:11 expat.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.10-2+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › expat/libexpat1@2.2.10-2+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
xmlwf in libexpat before 2.8.2 has an integer overflow in endDoctypeDecl via NOTATION declarations.
Remediation
There is no fixed version for Debian:11 expat.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.10-2+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › expat/libexpat1@2.2.10-2+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libexpat before 2.8.2 has an integer overflow in XML_ParseBuffer because it lacked a check that was present in XML_Parse.
Remediation
There is no fixed version for Debian:11 expat.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.10-2+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › expat/libexpat1@2.2.10-2+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libexpat before 2.8.2 has an integer overflow in addBinding.
Remediation
There is no fixed version for Debian:11 expat.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.10-2+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › expat/libexpat1@2.2.10-2+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
xmlwf in libexpat before 2.8.2 has an integer overflow for the output filename when -d outputDir is used.
Remediation
There is no fixed version for Debian:11 expat.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.10-2+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › expat/libexpat1@2.2.10-2+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libexpat before 2.8.3 has an out-of-bounds read and resultant infinite loop because low surrogates are treated the same as high surrogates during Unicode processing in the *_toUtf16 functions.
Remediation
There is no fixed version for Debian:11 expat.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.10-2+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › expat/libexpat1@2.2.10-2+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libexpat before 2.8.2 lacks handler call depth tracking for calls to XML_ResumeParser from within handlers in cases of a policy violation. Thus, a use-after-free can occur (similar to the CVE-2026-50219 situation).
Remediation
There is no fixed version for Debian:11 expat.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.10-2+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › expat/libexpat1@2.2.10-2+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
libexpat before 2.8.2 does not consider XML_TOK_DATA_CHARS in doCdataSection and thus lacks handler call depth tracking for various calls from within handlers in cases of a policy violation. Thus, a use-after-free can occur. NOTE: this issue exists because of an incomplete fix for CVE-2026-50219.
Remediation
There is no fixed version for Debian:11 expat.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
- Fixed in: 2.31-13+deb11u9
Detailed paths
-
Introduced through: nginx@1.21 › glibc/libc-bin@2.31-13+deb11u3
-
Introduced through: nginx@1.21 › glibc/libc6@2.31-13+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
The iconv() function in the GNU C Library versions 2.39 and older may overflow the output buffer passed to it by up to 4 bytes when converting strings to the ISO-2022-CN-EXT character set, which may be used to crash an application or overwrite a neighbouring variable.
Remediation
Upgrade Debian:11 glibc to version 2.31-13+deb11u9 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-2961
- https://www.ambionics.io/blog/iconv-cve-2024-2961-p1
- https://www.ambionics.io/blog/iconv-cve-2024-2961-p2
- https://www.ambionics.io/blog/iconv-cve-2024-2961-p3
- http://www.openwall.com/lists/oss-security/2024/04/17/9
- http://www.openwall.com/lists/oss-security/2024/04/18/4
- http://www.openwall.com/lists/oss-security/2024/04/24/2
- http://www.openwall.com/lists/oss-security/2024/05/27/1
- http://www.openwall.com/lists/oss-security/2024/05/27/2
- http://www.openwall.com/lists/oss-security/2024/05/27/3
- http://www.openwall.com/lists/oss-security/2024/05/27/4
- http://www.openwall.com/lists/oss-security/2024/05/27/5
- http://www.openwall.com/lists/oss-security/2024/05/27/6
- http://www.openwall.com/lists/oss-security/2024/07/22/5
- https://lists.debian.org/debian-lts-announce/2024/05/msg00001.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BTJFBGHDYG5PEIFD5WSSSKSFZ2AZWC5N/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/P3I4KYS6EU6S7QZ47WFNTPVAHFIUQNEL/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YAMJQI3Y6BHWV3CUTYBXOZONCUJNOB2Z/
- https://security.netapp.com/advisory/ntap-20240531-0002/
- https://sourceware.org/git/?p=glibc.git;a=blob;f=advisories/GLIBC-SA-2024-0004
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://github.com/ambionics/cnext-exploits
- https://github.com/projectdiscovery/nuclei-templates/blob/main/dast/cves/2024/CVE-2024-2961.yaml
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
- Fixed in: 2.31-13+deb11u10
Detailed paths
-
Introduced through: nginx@1.21 › glibc/libc-bin@2.31-13+deb11u3
-
Introduced through: nginx@1.21 › glibc/libc6@2.31-13+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
nscd: Stack-based buffer overflow in netgroup cache
If the Name Service Cache Daemon's (nscd) fixed size cache is exhausted by client requests then a subsequent client request for netgroup data may result in a stack-based buffer overflow. This flaw was introduced in glibc 2.15 when the cache was added to nscd.
This vulnerability is only present in the nscd binary.
Remediation
Upgrade Debian:11 glibc to version 2.31-13+deb11u10 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-33599
- http://www.openwall.com/lists/oss-security/2024/07/22/5
- https://lists.debian.org/debian-lts-announce/2024/06/msg00026.html
- https://security.netapp.com/advisory/ntap-20240524-0011/
- https://sourceware.org/git/?p=glibc.git;a=blob;f=advisories/GLIBC-SA-2024-0005
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
- Fixed in: 2.31-13+deb11u10
Detailed paths
-
Introduced through: nginx@1.21 › glibc/libc-bin@2.31-13+deb11u3
-
Introduced through: nginx@1.21 › glibc/libc6@2.31-13+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
nscd: Null pointer crashes after notfound response
If the Name Service Cache Daemon's (nscd) cache fails to add a not-found netgroup response to the cache, the client request can result in a null pointer dereference. This flaw was introduced in glibc 2.15 when the cache was added to nscd.
This vulnerability is only present in the nscd binary.
Remediation
Upgrade Debian:11 glibc to version 2.31-13+deb11u10 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-33600
- http://www.openwall.com/lists/oss-security/2024/07/22/5
- https://lists.debian.org/debian-lts-announce/2024/06/msg00026.html
- https://security.netapp.com/advisory/ntap-20240524-0013/
- https://sourceware.org/git/?p=glibc.git;a=blob;f=advisories/GLIBC-SA-2024-0006
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
- Fixed in: 2.31-13+deb11u10
Detailed paths
-
Introduced through: nginx@1.21 › glibc/libc-bin@2.31-13+deb11u3
-
Introduced through: nginx@1.21 › glibc/libc6@2.31-13+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
nscd: netgroup cache may terminate daemon on memory allocation failure
The Name Service Cache Daemon's (nscd) netgroup cache uses xmalloc or xrealloc and these functions may terminate the process due to a memory allocation failure resulting in a denial of service to the clients. The flaw was introduced in glibc 2.15 when the cache was added to nscd.
This vulnerability is only present in the nscd binary.
Remediation
Upgrade Debian:11 glibc to version 2.31-13+deb11u10 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-33601
- http://www.openwall.com/lists/oss-security/2024/07/22/5
- https://lists.debian.org/debian-lts-announce/2024/06/msg00026.html
- https://security.netapp.com/advisory/ntap-20240524-0014/
- https://sourceware.org/git/?p=glibc.git;a=blob;f=advisories/GLIBC-SA-2024-0007
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
- Fixed in: 2.31-13+deb11u10
Detailed paths
-
Introduced through: nginx@1.21 › glibc/libc-bin@2.31-13+deb11u3
-
Introduced through: nginx@1.21 › glibc/libc6@2.31-13+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
nscd: netgroup cache assumes NSS callback uses in-buffer strings
The Name Service Cache Daemon's (nscd) netgroup cache can corrupt memory when the NSS callback does not store all strings in the provided buffer. The flaw was introduced in glibc 2.15 when the cache was added to nscd.
This vulnerability is only present in the nscd binary.
Remediation
Upgrade Debian:11 glibc to version 2.31-13+deb11u10 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-33602
- http://www.openwall.com/lists/oss-security/2024/07/22/5
- https://lists.debian.org/debian-lts-announce/2024/06/msg00026.html
- https://security.netapp.com/advisory/ntap-20240524-0012/
- https://sourceware.org/git/?p=glibc.git;a=blob;f=advisories/GLIBC-SA-2024-0008
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
- Fixed in: 2.31-13+deb11u12
Detailed paths
-
Introduced through: nginx@1.21 › glibc/libc-bin@2.31-13+deb11u3
-
Introduced through: nginx@1.21 › glibc/libc6@2.31-13+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
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:11 glibc to version 2.31-13+deb11u12 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-0395
- https://sourceware.org/bugzilla/show_bug.cgi?id=32582
- https://sourceware.org/git/?p=glibc.git;a=blob;f=advisories/GLIBC-SA-2025-0001
- https://sourceware.org/pipermail/libc-announce/2025/000044.html
- https://www.openwall.com/lists/oss-security/2025/01/22/4
- http://www.openwall.com/lists/oss-security/2025/01/22/4
- http://www.openwall.com/lists/oss-security/2025/01/23/2
- https://security.netapp.com/advisory/ntap-20250228-0006/
- http://www.openwall.com/lists/oss-security/2025/04/13/1
- http://www.openwall.com/lists/oss-security/2025/04/24/7
- https://lists.debian.org/debian-lts-announce/2025/04/msg00039.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-577017.html
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
- Fixed in: 2.31-13+deb11u14
Detailed paths
-
Introduced through: nginx@1.21 › glibc/libc-bin@2.31-13+deb11u3
-
Introduced through: nginx@1.21 › glibc/libc6@2.31-13+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Calling wordexp with WRDE_REUSE in conjunction with WRDE_APPEND in the GNU C Library version 2.0 to version 2.42 may cause the interface to return uninitialized memory in the we_wordv member, which on subsequent calls to wordfree may abort the process.
Remediation
Upgrade Debian:11 glibc to version 2.31-13+deb11u14 or higher.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
- Fixed in: 2.31-13+deb11u13
Detailed paths
-
Introduced through: nginx@1.21 › glibc/libc-bin@2.31-13+deb11u3
-
Introduced through: nginx@1.21 › glibc/libc6@2.31-13+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
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:11 glibc to version 2.31-13+deb11u13 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.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
- Fixed in: 2.31-13+deb11u14
Detailed paths
-
Introduced through: nginx@1.21 › glibc/libc-bin@2.31-13+deb11u3
-
Introduced through: nginx@1.21 › glibc/libc6@2.31-13+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
The 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:11 glibc to version 2.31-13+deb11u14 or higher.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
- Fixed in: 2.31-13+deb11u14
Detailed paths
-
Introduced through: nginx@1.21 › glibc/libc-bin@2.31-13+deb11u3
-
Introduced through: nginx@1.21 › glibc/libc6@2.31-13+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Passing too large an alignment to the memalign suite of functions (memalign, posix_memalign, aligned_alloc) in the GNU C Library version 2.30 to 2.42 may result in an integer overflow, which could consequently result in a heap corruption.
Note that the attacker must have control over both, the size as well as the alignment arguments of the memalign function to be able to exploit this. The size parameter must be close enough to PTRDIFF_MAX so as to overflow size_t along with the large alignment argument. This limits the malicious inputs for the alignment for memalign to the range [1<<62+ 1, 1<<63] and exactly 1<<63 for posix_memalign and aligned_alloc.
Typically the alignment argument passed to such functions is a known constrained quantity (e.g. page size, block size, struct sizes) and is not attacker controlled, because of which this may not be easily exploitable in practice. An application bug could potentially result in the input alignment being too large, e.g. due to a different buffer overflow or integer overflow in the application or its dependent libraries, but that is again an uncommon usage pattern given typical sources of alignments.
Remediation
Upgrade Debian:11 glibc to version 2.31-13+deb11u14 or higher.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
- Fixed in: 2.31-13+deb11u14
Detailed paths
-
Introduced through: nginx@1.21 › glibc/libc-bin@2.31-13+deb11u3
-
Introduced through: nginx@1.21 › glibc/libc6@2.31-13+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Calling getnetbyaddr or getnetbyaddr_r with a configured nsswitch.conf that specifies the library's DNS backend for networks and queries for a zero-valued network in the GNU C Library version 2.0 to version 2.42 can leak stack contents to the configured DNS resolver.
Remediation
Upgrade Debian:11 glibc to version 2.31-13+deb11u14 or higher.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › glibc/libc-bin@2.31-13+deb11u3
-
Introduced through: nginx@1.21 › glibc/libc6@2.31-13+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Passing an effectively empty string to the ,ccs= syntax extension of the mode argument in the fopen function in the GNU C Library version 2.45 or earlier may result in a heap buffer overflow when the mode string input to the function is attacker controlled.
This usage pattern is not seen in applications in common GNU/Linux distributions and applications that process user-supplied values for ccs should not pass them through without validation.
Remediation
There is no fixed version for Debian:11 glibc.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › glibc/libc-bin@2.31-13+deb11u3
-
Introduced through: nginx@1.21 › glibc/libc6@2.31-13+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Calling strfmon and strfmon_l in the GNU C Library version 2.38 to 2.44 can write past the end of the caller-supplied output buffer when a conversion uses right-justified width padding.
Exploitation requires an application code path that calls strfmon or strfmon_l with right-justified width padding into a destination buffer that is large enough for the padding to succeed but too small for the internal memmove call. The field width or format may be attacker-influenced or a fixed susceptible pattern in the caller.
At the time of publication, no network-facing application impact is known.
Remediation
There is no fixed version for Debian:11 glibc.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › glibc/libc-bin@2.31-13+deb11u3
-
Introduced through: nginx@1.21 › glibc/libc6@2.31-13+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Calling tdelete on a sufficiently deep tree in the GNU C Library version 2.1 to 2.44 may write one pointer past the end of an alloca-allocated array on the stack, which may crash the application.
The tdelete implementation keeps an explicit stack of parent nodes for rebalancing, which is grown as needed while descending the tree. Two rebalancing branches push an additional entry without checking the capacity, and write past the array when the stack is exactly full. Triggering this requires a node at a depth of exactly 40 (or 40 plus a multiple of 20), which implies a tree with at least a million nodes, so an attacker must drive a large number of insertions and deletions through an application that uses tsearch and tdelete. The written value is a pointer into a tree node and is not directly attacker controlled. No affected application in common distributions has been identified.
Remediation
There is no fixed version for Debian:11 glibc.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
- Fixed in: 2.31-13+deb11u14
Detailed paths
-
Introduced through: nginx@1.21 › glibc/libc-bin@2.31-13+deb11u3
-
Introduced through: nginx@1.21 › glibc/libc6@2.31-13+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
The iconv() function in the GNU C Library versions 2.43 and earlier may crash due to an assertion failure when converting inputs from the IBM1390 or IBM1399 character sets, which may be used to remotely crash an application.
This vulnerability can be trivially mitigated by removing the IBM1390 and IBM1399 character sets from systems that do not need them.
Remediation
Upgrade Debian:11 glibc to version 2.31-13+deb11u14 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-4046
- https://sourceware.org/bugzilla/show_bug.cgi?id=33980
- https://sourceware.org/git/?p=glibc.git;a=blob_plain;f=advisories/GLIBC-SA-2026-0007;hb=HEAD
- https://inbox.sourceware.org/libc-announce/76814edf-cf7f-47ec-979d-2dce0a2c76bf@gotplt.org/T/#u
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › glibc/libc-bin@2.31-13+deb11u3
-
Introduced through: nginx@1.21 › glibc/libc6@2.31-13+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
The deprecated functions ns_printrrf, ns_printrr and fp_nquery in the GNU C Library version 2.2 and newer fail to enforce the caller-supplied buffer length, and can result in an out-of-bounds write when printing TSIG records.
Remediation
There is no fixed version for Debian:11 glibc.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › glibc/libc-bin@2.31-13+deb11u3
-
Introduced through: nginx@1.21 › glibc/libc6@2.31-13+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Calling the ungetwc function on a FILE stream with wide characters encoded in a character set that has overlaps between its single byte and multi-byte character encodings, in the GNU C Library version 2.43 or earlier, may result in an attempt to read bytes before an allocated buffer, potentially resulting in unintentional disclosure of neighboring data in the heap, or a program crash.
A bug in the wide character pushback implementation (_IO_wdefault_pbackfail in libio/wgenops.c) causes ungetwc() to operate on the regular character buffer (fp->_IO_read_ptr) instead of the actual wide-stream read pointer (fp->_wide_data->_IO_read_ptr). The program crash may happen in cases where fp->_IO_read_ptr is not initialized and hence points to NULL. The buffer under-read requires a special situation where the input character encoding is such that there are overlaps between single byte representations and multibyte representations in that encoding, resulting in spurious matches. The spurious match case is not possible in the standard Unicode character sets.
Remediation
There is no fixed version for Debian:11 glibc.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › glibc/libc-bin@2.31-13+deb11u3
-
Introduced through: nginx@1.21 › glibc/libc6@2.31-13+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
The deprecated functions ns_printrrf, ns_printrr and fp_nquery in the GNU C Library version 2.2 and newer fail to validate the RDATA content against the RDATA length in a DNS response when processing LOC, CERT, TKEY or TSIG records, which may allow an attacker to craft a DNS response, causing a target application to crash or read uninitialized memory.
These functions are for application debugging only and hence not in the path of code executed by the DNS resolver. Further, they have been deprecated since version 2.34 and should not be used by any new applications. Applications should consider porting away from these interfaces since they may be removed in future versions.
Remediation
There is no fixed version for Debian:11 glibc.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › glibc/libc-bin@2.31-13+deb11u3
-
Introduced through: nginx@1.21 › glibc/libc6@2.31-13+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Calling wordexp with WRDE_APPEND in the GNU C Library version 2.0 to version 2.43 can cause the interface to return invalid memory in the we_wordv member, which on subsequent calls to wordfree may abort the process.
Remediation
There is no fixed version for Debian:11 glibc.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › glibc/libc-bin@2.31-13+deb11u3
-
Introduced through: nginx@1.21 › glibc/libc6@2.31-13+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
When expanding paths that begin with a tilde (~) followed by a username, the internal parse_tilde function extracts the username to determine the user's home directory. The implementation allocates memory for this username directly on the stack using the strndupa macro. Because the size of this allocation was determined by the length of the user-supplied input without any bounds checks, passing an excessively long username e.g. thousands of characters, forces the thread to exhaust its stack space. Thus if an application passes untrusted, attacker-controlled input to the wordexp function, an attacker can trigger a stack clash.
Remediation
There is no fixed version for Debian:11 glibc.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › glibc/libc-bin@2.31-13+deb11u3
-
Introduced through: nginx@1.21 › glibc/libc6@2.31-13+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Converting crafted SHIFT_JISX0213 input to UCS-4 or the internal wide character encoding, for example with iconv, in the GNU C Library version 2.3 to 2.44 may result in the converter making no progress, causing the calling application to hang.
Some SHIFT_JISX0213 sequences decode to two code points. If the output buffer has room for only the first one, the converter stores the second in the conversion state and returns E2BIG, but it never clears that pending character after emitting it on the next call. The converter then keeps emitting the pending character without consuming further input, so an application that retries the conversion loops forever. The input must be attacker controlled and the application must convert it with an output buffer small enough to split the two code points. Only the SHIFT_JISX0213 character set is affected, which is not commonly used. The related defect in the EUC_JISX0213 converter is tracked separately as CVE-2026-80489.
Remediation
There is no fixed version for Debian:11 glibc.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › glibc/libc-bin@2.31-13+deb11u3
-
Introduced through: nginx@1.21 › glibc/libc6@2.31-13+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Converting crafted EUC_JISX0213 input to UCS-4 or the internal wide character encoding, for example with iconv, in the GNU C Library version 2.3 to 2.44 may result in the converter making no progress, causing the calling application to hang.
Some EUC_JISX0213 sequences decode to two code points. If the output buffer has room for only the first one, the converter stores the second in the conversion state and returns E2BIG, but it never clears that pending character after emitting it on the next call. The converter then keeps emitting the pending character without consuming further input, so an application that retries the conversion loops forever. The input must be attacker controlled and the application must convert it with an output buffer small enough to split the two code points. Only the EUC_JISX0213 character set is affected, which is not commonly used. The related defect in SHIFT_JISX0213 converter is tracked separately as CVE-2026-77117.
Remediation
There is no fixed version for Debian:11 glibc.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-13+deb11u3 and glibc/libc6@2.31-13+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › glibc/libc-bin@2.31-13+deb11u3
-
Introduced through: nginx@1.21 › glibc/libc6@2.31-13+deb11u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Calling the scanf family of functions with a %mc (malloc'd character match) in the GNU C Library version 2.7 to version 2.43 with a format width specifier with an explicit width greater than 1024 could result in a one byte heap buffer overflow.
Remediation
There is no fixed version for Debian:11 glibc.
References
low severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.1-5
- Fixed in: 3.7.1-5+deb11u6
Detailed paths
-
Introduced through: nginx@1.21 › gnutls28/libgnutls30@3.7.1-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw has been discovered in GnuTLS where an application crash can be induced when attempting to verify a specially crafted .pem bundle using the "certtool --verify-chain" command.
Remediation
Upgrade Debian:11 gnutls28 to version 3.7.1-5+deb11u6 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-28835
- http://www.openwall.com/lists/oss-security/2024/03/22/1
- http://www.openwall.com/lists/oss-security/2024/03/22/2
- https://security.netapp.com/advisory/ntap-20241122-0009/
- https://lists.debian.org/debian-lts-announce/2024/09/msg00019.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://access.redhat.com/errata/RHSA-2024:1879
- https://access.redhat.com/errata/RHSA-2024:2570
- https://access.redhat.com/errata/RHSA-2024:2889
- https://access.redhat.com/security/cve/CVE-2024-28835
- https://bugzilla.redhat.com/show_bug.cgi?id=2269084
- https://lists.gnupg.org/pipermail/gnutls-help/2024-March/004845.html
low severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.1-5
- Fixed in: 3.7.1-5+deb11u6
Detailed paths
-
Introduced through: nginx@1.21 › gnutls28/libgnutls30@3.7.1-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A flaw was found in GnuTLS. The Minerva attack is a cryptographic vulnerability that exploits deterministic behavior in systems like GnuTLS, leading to side-channel leaks. In specific scenarios, such as when using the GNUTLS_PRIVKEY_FLAG_REPRODUCIBLE flag, it can result in a noticeable step in nonce size from 513 to 512 bits, exposing a potential timing side-channel.
Remediation
Upgrade Debian:11 gnutls28 to version 3.7.1-5+deb11u6 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-28834
- http://www.openwall.com/lists/oss-security/2024/03/22/1
- http://www.openwall.com/lists/oss-security/2024/03/22/2
- https://people.redhat.com/~hkario/marvin/
- https://security.netapp.com/advisory/ntap-20240524-0004/
- https://lists.debian.org/debian-lts-announce/2024/09/msg00019.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://access.redhat.com/errata/RHSA-2024:1784
- https://access.redhat.com/errata/RHSA-2024:1879
- https://access.redhat.com/errata/RHSA-2024:1997
- https://access.redhat.com/errata/RHSA-2024:2044
- https://access.redhat.com/errata/RHSA-2024:2570
- https://access.redhat.com/errata/RHSA-2024:2889
- https://access.redhat.com/security/cve/CVE-2024-28834
- https://bugzilla.redhat.com/show_bug.cgi?id=2269228
- https://lists.gnupg.org/pipermail/gnutls-help/2024-March/004845.html
- https://minerva.crocs.fi.muni.cz/
low severity
- Vulnerable module: gzip
- Introduced through: gzip@1.10-4+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › gzip@1.10-4+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream gzip package and not the gzip package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
GNU gzip contains a vulnerability in the gzexe utility related to insecure temporary file handling. When the mktemp utility is not available in the user’s PATH, gzexe falls back to constructing a temporary file path based solely on the process ID (PID). This predictable filename is created without exclusive access or existence checks. A local attacker can pre‑create the predicted temporary file path as a symbolic link pointing to an arbitrary file writable by the victim. When gzexe runs, it follows the symlink and overwrites the target file, resulting in a time‑of‑check to time‑of‑use (TOCTOU) condition that allows arbitrary file overwrite.
This issue has been fixed in the commit 4e6f8b24ab823146ab8776f0b7fe486ab34d4269
Remediation
There is no fixed version for Debian:11 gzip.
References
low severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.18.3-6+deb11u1, krb5/libk5crypto3@1.18.3-6+deb11u1 and others
Detailed paths
-
Introduced through: nginx@1.21 › krb5/libgssapi-krb5-2@1.18.3-6+deb11u1
-
Introduced through: nginx@1.21 › krb5/libk5crypto3@1.18.3-6+deb11u1
-
Introduced through: nginx@1.21 › krb5/libkrb5-3@1.18.3-6+deb11u1
-
Introduced through: nginx@1.21 › krb5/libkrb5support0@1.18.3-6+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Kerberos 5 (aka krb5) 1.21.2 contains a memory leak vulnerability in /krb5/src/lib/gssapi/krb5/k5sealv3.c.
Remediation
There is no fixed version for Debian:11 krb5.
References
low severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.18.3-6+deb11u1, krb5/libk5crypto3@1.18.3-6+deb11u1 and others
- Fixed in: 1.18.3-6+deb11u6
Detailed paths
-
Introduced through: nginx@1.21 › krb5/libgssapi-krb5-2@1.18.3-6+deb11u1
-
Introduced through: nginx@1.21 › krb5/libk5crypto3@1.18.3-6+deb11u1
-
Introduced through: nginx@1.21 › krb5/libkrb5-3@1.18.3-6+deb11u1
-
Introduced through: nginx@1.21 › krb5/libkrb5support0@1.18.3-6+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
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:11 krb5 to version 1.18.3-6+deb11u6 or higher.
References
low severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.18.3-6+deb11u1, krb5/libk5crypto3@1.18.3-6+deb11u1 and others
- Fixed in: 1.18.3-6+deb11u8
Detailed paths
-
Introduced through: nginx@1.21 › krb5/libgssapi-krb5-2@1.18.3-6+deb11u1
-
Introduced through: nginx@1.21 › krb5/libk5crypto3@1.18.3-6+deb11u1
-
Introduced through: nginx@1.21 › krb5/libkrb5-3@1.18.3-6+deb11u1
-
Introduced through: nginx@1.21 › krb5/libkrb5support0@1.18.3-6+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
In MIT Kerberos 5 (aka krb5) before 1.22.3, there is an integer underflow and resultant out-of-bounds read if an application calls gss_accept_sec_context() on a system with a NegoEx mechanism registered in /etc/gss/mech. An unauthenticated remote attacker can trigger this, possibly causing the process to terminate in parse_message.
Remediation
Upgrade Debian:11 krb5 to version 1.18.3-6+deb11u8 or higher.
References
low severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.18.3-6+deb11u1, krb5/libk5crypto3@1.18.3-6+deb11u1 and others
Detailed paths
-
Introduced through: nginx@1.21 › krb5/libgssapi-krb5-2@1.18.3-6+deb11u1
-
Introduced through: nginx@1.21 › krb5/libk5crypto3@1.18.3-6+deb11u1
-
Introduced through: nginx@1.21 › krb5/libkrb5-3@1.18.3-6+deb11u1
-
Introduced through: nginx@1.21 › krb5/libkrb5support0@1.18.3-6+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Kerberos 5 (aka krb5) 1.21.2 contains a memory leak in /krb5/src/lib/rpc/pmap_rmt.c.
Remediation
There is no fixed version for Debian:11 krb5.
References
low severity
- Vulnerable module: libgcrypt20
- Introduced through: libgcrypt20@1.8.7-6
Detailed paths
-
Introduced through: nginx@1.21 › libgcrypt20@1.8.7-6
NVD Description
Note: Versions mentioned in the description apply only to the upstream libgcrypt20 package and not the libgcrypt20 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
A timing-based side-channel flaw was found in libgcrypt's RSA implementation. This issue may allow a remote attacker to initiate a Bleichenbacher-style attack, which can lead to the decryption of RSA ciphertexts.
Remediation
There is no fixed version for Debian:11 libgcrypt20.
References
- 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
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
low severity
- Vulnerable module: libgd2/libgd3
- Introduced through: libgd2/libgd3@2.3.0-2
- Fixed in: 2.3.0-2+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › libgd2/libgd3@2.3.0-2
NVD Description
This vulnerability has not been analyzed by NVD yet.
Remediation
Upgrade Debian:11 libgd2 to version 2.3.0-2+deb11u2 or higher.
References
low severity
- Vulnerable module: libpng1.6/libpng16-16
- Introduced through: libpng1.6/libpng16-16@1.6.37-3
Detailed paths
-
Introduced through: nginx@1.21 › libpng1.6/libpng16-16@1.6.37-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Buffer Overflow vulnerability in libpng 1.6.43-1.6.46 allows a local attacker to cause a denial of service via the pngimage with AddressSanitizer (ASan), the program leaks memory in various locations, eventually leading to high memory usage and causing the program to become unresponsive
Remediation
There is no fixed version for Debian:11 libpng1.6.
References
low severity
- Vulnerable module: libpng1.6/libpng16-16
- Introduced through: libpng1.6/libpng16-16@1.6.37-3
- Fixed in: 1.6.37-3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › libpng1.6/libpng16-16@1.6.37-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. Prior to 1.6.52, an out-of-bounds read vulnerability in libpng's simplified API allows reading up to 1012 bytes beyond the png_sRGB_base[512] array when processing valid palette PNG images with partial transparency and gamma correction. The PNG files that trigger this vulnerability are valid per the PNG specification; the bug is in libpng's internal state management. Upgrade to libpng 1.6.52 or later.
Remediation
Upgrade Debian:11 libpng1.6 to version 1.6.37-3+deb11u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-66293
- https://github.com/pnggroup/libpng/commit/788a624d7387a758ffd5c7ab010f1870dea753a1
- https://github.com/pnggroup/libpng/commit/a05a48b756de63e3234ea6b3b938b8f5f862484a
- https://github.com/pnggroup/libpng/security/advisories/GHSA-9mpm-9pxh-mg4f
- http://www.openwall.com/lists/oss-security/2025/12/03/6
- http://www.openwall.com/lists/oss-security/2025/12/03/7
- http://www.openwall.com/lists/oss-security/2025/12/03/8
- https://github.com/pnggroup/libpng/issues/764
low severity
- Vulnerable module: libpng1.6/libpng16-16
- Introduced through: libpng1.6/libpng16-16@1.6.37-3
- Fixed in: 1.6.37-3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › libpng1.6/libpng16-16@1.6.37-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From version 1.6.0 to before 1.6.51, there is a heap buffer overflow vulnerability in the libpng simplified API function png_image_finish_read when processing 16-bit interlaced PNGs with 8-bit output format. Attacker-crafted interlaced PNG files cause heap writes beyond allocated buffer bounds. This issue has been patched in version 1.6.51.
Remediation
Upgrade Debian:11 libpng1.6 to version 1.6.37-3+deb11u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-65018
- https://github.com/pnggroup/libpng/commit/16b5e3823918840aae65c0a6da57c78a5a496a4d
- https://github.com/pnggroup/libpng/commit/218612ddd6b17944e21eda56caf8b4bf7779d1ea
- https://github.com/pnggroup/libpng/pull/757
- https://github.com/pnggroup/libpng/issues/755
- https://github.com/pnggroup/libpng/security/advisories/GHSA-7wv6-48j4-hj3g
low severity
- Vulnerable module: libpng1.6/libpng16-16
- Introduced through: libpng1.6/libpng16-16@1.6.37-3
Detailed paths
-
Introduced through: nginx@1.21 › libpng1.6/libpng16-16@1.6.37-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
LIBPNG is a reference library for use in applications that process PNG (Portable Network Graphics) raster image files. In version 1.8.0, three inter-frame chunk discard paths in the push-mode APNG parser clear the chunk-header flag without consuming the chunk body and CRC, allowing attacker-controlled bytes inside an ignored ancillary chunk to be reinterpreted as a fresh chunk header on the next call to png_process_data. Commit faf06924688b62d7c1654b5ceddedbde66ffadb4 fixes the issue.
Remediation
There is no fixed version for Debian:11 libpng1.6.
References
low severity
- Vulnerable module: libpng1.6/libpng16-16
- Introduced through: libpng1.6/libpng16-16@1.6.37-3
Detailed paths
-
Introduced through: nginx@1.21 › libpng1.6/libpng16-16@1.6.37-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Buffer Overflow vulnerability in libpng 1.6.43-1.6.46 allows a local attacker to cause a denial of service via png_create_read_struct() function.
Remediation
There is no fixed version for Debian:11 libpng1.6.
References
low severity
- Vulnerable module: libpng1.6/libpng16-16
- Introduced through: libpng1.6/libpng16-16@1.6.37-3
- Fixed in: 1.6.37-3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › libpng1.6/libpng16-16@1.6.37-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. Prior to version 1.6.51, a heap buffer over-read vulnerability exists in libpng's png_do_quantize function when processing PNG files with malformed palette indices. The vulnerability occurs when palette_lookup array bounds are not validated against externally-supplied image data, allowing an attacker to craft a PNG file with out-of-range palette indices that trigger out-of-bounds memory access. This issue has been patched in version 1.6.51.
Remediation
Upgrade Debian:11 libpng1.6 to version 1.6.37-3+deb11u1 or higher.
References
low severity
- Vulnerable module: libpng1.6/libpng16-16
- Introduced through: libpng1.6/libpng16-16@1.6.37-3
- Fixed in: 1.6.37-3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › libpng1.6/libpng16-16@1.6.37-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From version 1.6.0 to before 1.6.51, an out-of-bounds read vulnerability exists in png_image_read_composite when processing palette images with PNG_FLAG_OPTIMIZE_ALPHA enabled. The palette compositing code in png_init_read_transformations incorrectly applies background compositing during premultiplication, violating the invariant component ≤ alpha × 257 required by the simplified PNG API. This issue has been patched in version 1.6.51.
Remediation
Upgrade Debian:11 libpng1.6 to version 1.6.37-3+deb11u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-64720
- https://github.com/pnggroup/libpng/commit/08da33b4c88cfcd36e5a706558a8d7e0e4773643
- https://github.com/pnggroup/libpng/issues/686
- https://github.com/pnggroup/libpng/pull/751
- https://github.com/pnggroup/libpng/security/advisories/GHSA-hfc7-ph9c-wcww
low severity
- Vulnerable module: libpng1.6/libpng16-16
- Introduced through: libpng1.6/libpng16-16@1.6.37-3
- Fixed in: 1.6.37-3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › libpng1.6/libpng16-16@1.6.37-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From version 1.6.0 to before 1.6.51, a heap buffer over-read vulnerability exists in libpng's png_write_image_8bit function when processing 8-bit images through the simplified write API with convert_to_8bit enabled. The vulnerability affects 8-bit grayscale+alpha, RGB/RGBA, and images with incomplete row data. A conditional guard incorrectly allows 8-bit input to enter code expecting 16-bit input, causing reads up to 2 bytes beyond allocated buffer boundaries. This issue has been patched in version 1.6.51.
Remediation
Upgrade Debian:11 libpng1.6 to version 1.6.37-3+deb11u1 or higher.
References
low severity
- Vulnerable module: libpng1.6/libpng16-16
- Introduced through: libpng1.6/libpng16-16@1.6.37-3
- Fixed in: 1.6.37-3+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › libpng1.6/libpng16-16@1.6.37-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. In versions 1.6.36 through 1.6.55, an out-of-bounds read and write exists in libpng's ARM/AArch64 Neon-optimized palette expansion path. When expanding 8-bit paletted rows to RGB or RGBA, the Neon loop processes a final partial chunk without verifying that enough input pixels remain. Because the implementation works backward from the end of the row, the final iteration dereferences pointers before the start of the row buffer (OOB read) and writes expanded pixel data to the same underflowed positions (OOB write). This is reachable via normal decoding of attacker-controlled PNG input if Neon is enabled. Version 1.6.56 fixes the issue.
Remediation
Upgrade Debian:11 libpng1.6 to version 1.6.37-3+deb11u3 or higher.
References
low severity
- Vulnerable module: libpng1.6/libpng16-16
- Introduced through: libpng1.6/libpng16-16@1.6.37-3
- Fixed in: 1.6.37-3+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › libpng1.6/libpng16-16@1.6.37-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. In versions 1.2.1 through 1.6.55, png_set_tRNS and png_set_PLTE each alias a heap-allocated buffer between png_struct and png_info, sharing a single allocation across two structs with independent lifetimes. The trans_alpha aliasing has been present since at least libpng 1.0, and the palette aliasing since at least 1.2.1. Both affect all prior release lines png_set_tRNS sets png_ptr->trans_alpha = info_ptr->trans_alpha (256-byte buffer) and png_set_PLTE sets info_ptr->palette = png_ptr->palette (768-byte buffer). In both cases, calling png_free_data (with PNG_FREE_TRNS or PNG_FREE_PLTE) frees the buffer through info_ptr while the corresponding png_ptr pointer remains dangling. Subsequent row-transform functions dereference and, in some code paths, write to the freed memory. A second call to png_set_tRNS or png_set_PLTE has the same effect, because both functions call png_free_data internally before reallocating the info_ptr buffer. Version 1.6.56 fixes the issue.
Remediation
Upgrade Debian:11 libpng1.6 to version 1.6.37-3+deb11u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-33416
- https://github.com/pnggroup/libpng/commit/23019269764e35ed8458e517f1897bd3c54820eb
- https://github.com/pnggroup/libpng/commit/7ea9eea884a2328cc7fdcb3c0c00246a50d90667
- https://github.com/pnggroup/libpng/commit/a3a21443ed12bfa1ef46fa0d4fb2b74a0fa34a25
- https://github.com/pnggroup/libpng/commit/c1b0318b393c90679e6fa5bc1d329fd5d5012ec1
- https://github.com/pnggroup/libpng/pull/824
- https://github.com/pnggroup/libpng/security/advisories/GHSA-m4pc-p4q3-4c7j
low severity
- Vulnerable module: libtasn1-6
- Introduced through: libtasn1-6@4.16.0-2
Detailed paths
-
Introduced through: nginx@1.21 › libtasn1-6@4.16.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:11 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:11 libtasn1-6.
References
low severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.10+dfsg-6.7+deb11u2
- Fixed in: 2.9.10+dfsg-6.7+deb11u8
Detailed paths
-
Introduced through: nginx@1.21 › libxml2@2.9.10+dfsg-6.7+deb11u2
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:11 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:11 libxml2 to version 2.9.10+dfsg-6.7+deb11u8 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://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VRDJCNQP32LV56KESUQ5SNZKAJWSZZRI/
- 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://cert-portal.siemens.com/productcert/html/ssa-398330.html
low severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.10+dfsg-6.7+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › libxml2@2.9.10+dfsg-6.7+deb11u2
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:11 relevant fixed versions and status.
Use After Free in libxml2's xmlParseInternalSubset from GNOME libxml2 version 2.9.11 to 2.11.0 allows a remote attacker to cause a denial-of-service via maliciously crafted XML input with improper entity resolution handling.
Remediation
There is no fixed version for Debian:11 libxml2.
References
low severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.10+dfsg-6.7+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › libxml2@2.9.10+dfsg-6.7+deb11u2
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:11 relevant fixed versions and status.
libxml2 is vulnerable to multiple stack-based buffer overflows in the xmlcatalog utility when running in --shell mode. The usershell() function processes user input using fixed-size stack buffers without proper bounds checking. By supplying an overly long input line, an attacker can overflow internal buffers (command, arg, and argv) during input parsing. This results in memory corruption within the stack frame. Successful exploitation may cause a crash or potentially allow arbitrary code execution in the context of the xmlcatalog process.
This issue has been fixed in the commit c2e233fc.
NOTE: The maintainers of this project did not agree that this issue is a vulnerability and considered it a bug.
Remediation
There is no fixed version for Debian:11 libxml2.
References
low severity
- Vulnerable module: nghttp2/libnghttp2-14
- Introduced through: nghttp2/libnghttp2-14@1.43.0-1
- Fixed in: 1.43.0-1+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › nghttp2/libnghttp2-14@1.43.0-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream nghttp2 package and not the nghttp2 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
nghttp2 is an implementation of the Hypertext Transfer Protocol version 2 in C. The nghttp2 library prior to version 1.61.0 keeps reading the unbounded number of HTTP/2 CONTINUATION frames even after a stream is reset to keep HPACK context in sync. This causes excessive CPU usage to decode HPACK stream. nghttp2 v1.61.0 mitigates this vulnerability by limiting the number of CONTINUATION frames it accepts per stream. There is no workaround for this vulnerability.
Remediation
Upgrade Debian:11 nghttp2 to version 1.43.0-1+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-28182
- https://lists.debian.org/debian-lts-announce/2024/09/msg00041.html
- https://www.kb.cert.org/vuls/id/421644
- http://www.openwall.com/lists/oss-security/2024/04/03/16
- https://github.com/nghttp2/nghttp2/commit/00201ecd8f982da3b67d4f6868af72a1b03b14e0
- https://github.com/nghttp2/nghttp2/commit/d71a4668c6bead55805d18810d633fbb98315af9
- https://github.com/nghttp2/nghttp2/security/advisories/GHSA-x6x3-gv8h-m57q
- https://lists.debian.org/debian-lts-announce/2024/04/msg00026.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/AGOME6ZXJG7664IPQNVE3DL67E3YP3HY/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/J6ZMXUGB66VAXDW5J6QSTHM5ET25FGSA/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PXJO2EASHM2OQQLGVDY5ZSO7UVDVHTDK/
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-784301.html
low severity
- Vulnerable module: nghttp2/libnghttp2-14
- Introduced through: nghttp2/libnghttp2-14@1.43.0-1
- Fixed in: 1.43.0-1+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › nghttp2/libnghttp2-14@1.43.0-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream nghttp2 package and not the nghttp2 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
nghttp2 is an implementation of the Hypertext Transfer Protocol version 2 in C. Prior to version 1.68.1, the nghttp2 library stops reading the incoming data when user facing public API nghttp2_session_terminate_session or nghttp2_session_terminate_session2 is called by the application. They might be called internally by the library when it detects the situation that is subject to connection error. Due to the missing internal state validation, the library keeps reading the rest of the data after one of those APIs is called. Then receiving a malformed frame that causes FRAME_SIZE_ERROR causes assertion failure. nghttp2 v1.68.1 adds missing state validation to avoid assertion failure. No known workarounds are available.
Remediation
Upgrade Debian:11 nghttp2 to version 1.43.0-1+deb11u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-27135
- https://github.com/nghttp2/nghttp2/commit/5c7df8fa815ac1004d9ecb9d1f7595c4d37f46e1
- https://github.com/nghttp2/nghttp2/security/advisories/GHSA-6933-cjhr-5qg6
- http://www.openwall.com/lists/oss-security/2026/03/20/3
- https://lists.debian.org/debian-lts-announce/2026/05/msg00025.html
- https://access.redhat.com/errata/RHSA-2026:10065
- https://access.redhat.com/errata/RHSA-2026:11768
- https://access.redhat.com/errata/RHSA-2026:13812
- https://access.redhat.com/errata/RHSA-2026:14773
- https://access.redhat.com/errata/RHSA-2026:14937
- https://access.redhat.com/errata/RHSA-2026:15087
- https://access.redhat.com/errata/RHSA-2026:16008
- https://access.redhat.com/errata/RHSA-2026:16009
- https://access.redhat.com/errata/RHSA-2026:16030
- https://access.redhat.com/errata/RHSA-2026:16174
- https://access.redhat.com/errata/RHSA-2026:17596
- https://access.redhat.com/errata/RHSA-2026:19724
- https://access.redhat.com/errata/RHSA-2026:19725
- https://access.redhat.com/errata/RHSA-2026:20040
- https://access.redhat.com/errata/RHSA-2026:20087
- https://access.redhat.com/errata/RHSA-2026:21656
- https://access.redhat.com/errata/RHSA-2026:21690
- https://access.redhat.com/errata/RHSA-2026:21695
- https://access.redhat.com/errata/RHSA-2026:25096
- https://access.redhat.com/errata/RHSA-2026:27200
- https://access.redhat.com/errata/RHSA-2026:27201
- https://access.redhat.com/errata/RHSA-2026:6190
- https://access.redhat.com/errata/RHSA-2026:7080
- https://access.redhat.com/errata/RHSA-2026:7123
- https://access.redhat.com/errata/RHSA-2026:7302
- https://access.redhat.com/errata/RHSA-2026:7310
- https://access.redhat.com/errata/RHSA-2026:7350
- https://access.redhat.com/errata/RHSA-2026:7666
- https://access.redhat.com/errata/RHSA-2026:7667
- https://access.redhat.com/errata/RHSA-2026:7668
- https://access.redhat.com/errata/RHSA-2026:7670
- https://access.redhat.com/errata/RHSA-2026:7675
- https://access.redhat.com/errata/RHSA-2026:7896
- https://access.redhat.com/errata/RHSA-2026:7983
- https://access.redhat.com/errata/RHSA-2026:8339
- https://access.redhat.com/errata/RHSA-2026:8538
- https://access.redhat.com/errata/RHSA-2026:8539
- https://access.redhat.com/errata/RHSA-2026:8540
- https://access.redhat.com/errata/RHSA-2026:8541
- https://access.redhat.com/errata/RHSA-2026:8545
- https://access.redhat.com/errata/RHSA-2026:8546
- https://access.redhat.com/errata/RHSA-2026:8547
- https://access.redhat.com/errata/RHSA-2026:8548
- https://access.redhat.com/errata/RHSA-2026:8868
- https://access.redhat.com/errata/RHSA-2026:9711
- https://access.redhat.com/errata/RHSA-2026:9832
- https://access.redhat.com/errata/RHSA-2026:9874
- https://access.redhat.com/security/cve/CVE-2026-27135
- https://bugzilla.redhat.com/show_bug.cgi?id=2448754
- https://cert-portal.siemens.com/productcert/html/ssa-019113.html
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-27135.json
low severity
- Vulnerable module: openldap/libldap-2.4-2
- Introduced through: openldap/libldap-2.4-2@2.4.57+dfsg-3+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › openldap/libldap-2.4-2@2.4.57+dfsg-3+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
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:11 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@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
- Fixed in: 1.1.1w-0+deb11u3
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Issue summary: 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:11 openssl to version 1.1.1w-0+deb11u3 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@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
- Fixed in: 1.1.1w-0+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Issue summary: Some non-default TLS server configurations can cause unbounded memory growth when processing TLSv1.3 sessions
Impact summary: An attacker may exploit certain server configurations to trigger unbounded memory growth that would lead to a Denial of Service
This problem can occur in TLSv1.3 if the non-default SSL_OP_NO_TICKET option is being used (but not if early_data support is also configured and the default anti-replay protection is in use). In this case, under certain conditions, the session cache can get into an incorrect state and it will fail to flush properly as it fills. The session cache will continue to grow in an unbounded manner. A malicious client could deliberately create the scenario for this failure to force a Denial of Service. It may also happen by accident in normal operation.
This issue only affects TLS servers supporting TLSv1.3. It does not affect TLS clients.
The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue. OpenSSL 1.0.2 is also not affected by this issue.
Remediation
Upgrade Debian:11 openssl to version 1.1.1w-0+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-2511
- http://www.openwall.com/lists/oss-security/2024/04/08/5
- https://security.netapp.com/advisory/ntap-20240503-0013/
- https://lists.debian.org/debian-lts-announce/2024/10/msg00033.html
- https://lists.debian.org/debian-lts-announce/2024/11/msg00000.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
- https://cert-portal.siemens.com/productcert/html/ssa-354112.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-613116.html
- https://cert-portal.siemens.com/productcert/html/ssa-769027.html
- https://cert-portal.siemens.com/productcert/html/ssa-915275.html
- https://github.com/openssl/openssl/commit/7e4d731b1c07201ad9374c1cd9ac5263bdf35bce
- https://github.com/openssl/openssl/commit/b52867a9f618bb955bed2a3ce3db4d4f97ed8e5d
- https://github.com/openssl/openssl/commit/e9d7083e241670332e0443da0f0d4ffb52829f08
- https://github.openssl.org/openssl/extended-releases/commit/5f8d25770ae6437db119dfc951e207271a326640
- https://www.openssl.org/news/secadv/20240408.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
- Fixed in: 1.1.1w-0+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause memory to be accessed that was previously freed in some situations
Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, only applications that directly call the SSL_free_buffers function are affected by this issue. Applications that do not call this function are not vulnerable. Our investigations indicate that this function is rarely used by applications.
The SSL_free_buffers function is used to free the internal OpenSSL buffer used when processing an incoming record from the network. The call is only expected to succeed if the buffer is not currently in use. However, two scenarios have been identified where the buffer is freed even when still in use.
The first scenario occurs where a record header has been received from the network and processed by OpenSSL, but the full record body has not yet arrived. In this case calling SSL_free_buffers will succeed even though a record has only been partially processed and the buffer is still in use.
The second scenario occurs where a full record containing application data has been received and processed by OpenSSL but the application has only read part of this data. Again a call to SSL_free_buffers will succeed even though the buffer is still in use.
While these scenarios could occur accidentally during normal operation a malicious attacker could attempt to engineer a stituation where this occurs. We are not aware of this issue being actively exploited.
The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.
Remediation
Upgrade Debian:11 openssl to version 1.1.1w-0+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-4741
- https://github.com/openssl/openssl/commit/704f725b96aa373ee45ecfb23f6abfe8be8d9177
- https://github.com/openssl/openssl/commit/b3f0eb0a295f58f16ba43ba99dad70d4ee5c437d
- https://github.com/openssl/openssl/commit/c88c3de51020c37e8706bf7a682a162593053aac
- https://github.com/openssl/openssl/commit/e5093133c35ca82874ad83697af76f4b0f7e3bd8
- https://github.openssl.org/openssl/extended-releases/commit/f7a045f3143fc6da2ee66bf52d8df04829590dd4
- https://www.openssl.org/news/secadv/20240528.txt
- https://lists.debian.org/debian-lts-announce/2024/10/msg00033.html
- https://lists.debian.org/debian-lts-announce/2024/11/msg00000.html
- https://security.netapp.com/advisory/ntap-20240621-0004/
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
- Fixed in: 1.1.1w-0+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Issue summary: Calling the OpenSSL API function SSL_select_next_proto with an empty supported client protocols buffer may cause a crash or memory contents to be sent to the peer.
Impact summary: A buffer overread can have a range of potential consequences such as unexpected application beahviour or a crash. In particular this issue could result in up to 255 bytes of arbitrary private data from memory being sent to the peer leading to a loss of confidentiality. However, only applications that directly call the SSL_select_next_proto function with a 0 length list of supported client protocols are affected by this issue. This would normally never be a valid scenario and is typically not under attacker control but may occur by accident in the case of a configuration or programming error in the calling application.
The OpenSSL API function SSL_select_next_proto is typically used by TLS applications that support ALPN (Application Layer Protocol Negotiation) or NPN (Next Protocol Negotiation). NPN is older, was never standardised and is deprecated in favour of ALPN. We believe that ALPN is significantly more widely deployed than NPN. The SSL_select_next_proto function accepts a list of protocols from the server and a list of protocols from the client and returns the first protocol that appears in the server list that also appears in the client list. In the case of no overlap between the two lists it returns the first item in the client list. In either case it will signal whether an overlap between the two lists was found. In the case where SSL_select_next_proto is called with a zero length client list it fails to notice this condition and returns the memory immediately following the client list pointer (and reports that there was no overlap in the lists).
This function is typically called from a server side application callback for ALPN or a client side application callback for NPN. In the case of ALPN the list of protocols supplied by the client is guaranteed by libssl to never be zero in length. The list of server protocols comes from the application and should never normally be expected to be of zero length. In this case if the SSL_select_next_proto function has been called as expected (with the list supplied by the client passed in the client/client_len parameters), then the application will not be vulnerable to this issue. If the application has accidentally been configured with a zero length server list, and has accidentally passed that zero length server list in the client/client_len parameters, and has additionally failed to correctly handle a "no overlap" response (which would normally result in a handshake failure in ALPN) then it will be vulnerable to this problem.
In the case of NPN, the protocol permits the client to opportunistically select a protocol when there is no overlap. OpenSSL returns the first client protocol in the no overlap case in support of this. The list of client protocols comes from the application and should never normally be expected to be of zero length. However if the SSL_select_next_proto function is accidentally called with a client_len of 0 then an invalid memory pointer will be returned instead. If the application uses this output as the opportunistic protocol then the loss of confidentiality will occur.
This issue has been assessed as Low severity because applications are most likely to be vulnerable if they are using NPN instead of ALPN - but NPN is not widely used. It also requires an application configuration or programming error. Finally, this issue would not typically be under attacker control making active exploitation unlikely.
The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.
Due to the low severity of this issue we are not issuing new releases of OpenSSL at this time. The fix will be included in the next releases when they become available.
Remediation
Upgrade Debian:11 openssl to version 1.1.1w-0+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-5535
- http://www.openwall.com/lists/oss-security/2024/08/15/1
- http://www.openwall.com/lists/oss-security/2024/06/27/1
- http://www.openwall.com/lists/oss-security/2024/06/28/4
- https://security.netapp.com/advisory/ntap-20240712-0005/
- https://lists.debian.org/debian-lts-announce/2024/10/msg00033.html
- https://lists.debian.org/debian-lts-announce/2024/11/msg00000.html
- https://security.netapp.com/advisory/ntap-20241025-0006/
- https://security.netapp.com/advisory/ntap-20241025-0010/
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
- https://cert-portal.siemens.com/productcert/html/ssa-277137.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-613116.html
- https://cert-portal.siemens.com/productcert/html/ssa-769027.html
- https://cert-portal.siemens.com/productcert/html/ssa-915275.html
- https://github.com/openssl/openssl/commit/4ada436a1946cbb24db5ab4ca082b69c1bc10f37
- https://github.com/openssl/openssl/commit/99fb785a5f85315b95288921a321a935ea29a51e
- https://github.com/openssl/openssl/commit/cf6f91f6121f4db167405db2f0de410a456f260c
- https://github.com/openssl/openssl/commit/e86ac436f0bd54d4517745483e2315650fae7b2c
- https://github.openssl.org/openssl/extended-releases/commit/9947251413065a05189a63c9b7a6c1d4e224c21c
- https://github.openssl.org/openssl/extended-releases/commit/b78ec0824da857223486660177d3b1f255c65d87
- https://www.openssl.org/news/secadv/20240627.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
- Fixed in: 1.1.1w-0+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted explicit values for the field polynomial can lead to out-of-bounds memory reads or writes.
Impact summary: Out of bound memory writes can lead to an application crash or even a possibility of a remote code execution, however, in all the protocols involving Elliptic Curve Cryptography that we're aware of, either only "named curves" are supported, or, if explicit curve parameters are supported, they specify an X9.62 encoding of binary (GF(2^m)) curves that can't represent problematic input values. Thus the likelihood of existence of a vulnerable application is low.
In particular, the X9.62 encoding is used for ECC keys in X.509 certificates, so problematic inputs cannot occur in the context of processing X.509 certificates. Any problematic use-cases would have to be using an "exotic" curve encoding.
The affected APIs include: EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(), and various supporting BN_GF2m_*() functions.
Applications working with "exotic" explicit binary (GF(2^m)) curve parameters, that make it possible to represent invalid field polynomials with a zero constant term, via the above or similar APIs, may terminate abruptly as a result of reading or writing outside of array bounds. Remote code execution cannot easily be ruled out.
The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.
Remediation
Upgrade Debian:11 openssl to version 1.1.1w-0+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-9143
- https://github.com/openssl/openssl/commit/72ae83ad214d2eef262461365a1975707f862712
- https://github.com/openssl/openssl/commit/bc7e04d7c8d509fb78fc0e285aa948fb0da04700
- https://github.com/openssl/openssl/commit/c0d3e4d32d2805f49bec30547f225bc4d092e1f4
- https://github.com/openssl/openssl/commit/fdf6723362ca51bd883295efe206cb5b1cfa5154
- https://github.openssl.org/openssl/extended-releases/commit/8efc0cbaa8ebba8e116f7b81a876a4123594d86a
- https://github.openssl.org/openssl/extended-releases/commit/9d576994cec2b7aa37a91740ea7e680810957e41
- https://openssl-library.org/news/secadv/20241016.txt
- http://www.openwall.com/lists/oss-security/2024/10/16/1
- http://www.openwall.com/lists/oss-security/2024/10/23/1
- http://www.openwall.com/lists/oss-security/2024/10/24/1
- https://security.netapp.com/advisory/ntap-20241101-0001/
- https://lists.debian.org/debian-lts-announce/2024/10/msg00033.html
- https://lists.debian.org/debian-lts-announce/2024/11/msg00000.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
- https://cert-portal.siemens.com/productcert/html/ssa-277137.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-769027.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
OpenSSL 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:11 openssl.
References
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
- Fixed in: 1.1.1w-0+deb11u5
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Issue summary: 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:11 openssl to version 1.1.1w-0+deb11u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-68160
- https://github.com/openssl/openssl/commit/384011202af92605d926fafe4a0bcd6b65d162ad
- https://github.com/openssl/openssl/commit/475c466ef2fbd8fc1df6fae1c3eed9c813fc8ff6
- https://github.com/openssl/openssl/commit/4c96fbba618e1940f038012506ee9e21d32ee12c
- https://github.com/openssl/openssl/commit/6845c3b6460a98b1ec4e463baa2ea1a63a32d7c0
- https://github.com/openssl/openssl/commit/68a7cd2e2816c3a02f4d45a2ce43fc04fac97096
- https://openssl-library.org/news/secadv/20260127.txt
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
- Fixed in: 1.1.1w-0+deb11u5
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Issue summary: 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:11 openssl to version 1.1.1w-0+deb11u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-69418
- https://github.com/openssl/openssl/commit/372fc5c77529695b05b4f5b5187691a57ef5dffc
- https://github.com/openssl/openssl/commit/4016975d4469cd6b94927c607f7c511385f928d8
- https://github.com/openssl/openssl/commit/52d23c86a54adab5ee9f80e48b242b52c4cc2347
- https://github.com/openssl/openssl/commit/a7589230356d908c0eca4b969ec4f62106f4f5ae
- https://github.com/openssl/openssl/commit/ed40856d7d4ba6cb42779b6770666a65f19cb977
- https://openssl-library.org/news/secadv/20260127.txt
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
- Fixed in: 1.1.1w-0+deb11u5
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Issue summary: 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:11 openssl to version 1.1.1w-0+deb11u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-69419
- https://github.com/openssl/openssl/commit/41be0f216404f14457bbf3b9cc488dba60b49296
- https://github.com/openssl/openssl/commit/7e9cac9832e4705b91987c2474ed06a37a93cecb
- https://github.com/openssl/openssl/commit/a26a90d38edec3748566129d824e664b54bee2e2
- https://github.com/openssl/openssl/commit/cda12de3bc0e333ea8d2c6fd15001dbdaf280015
- https://github.com/openssl/openssl/commit/ff628933755075446bca8307e8417c14d164b535
- https://openssl-library.org/news/secadv/20260127.txt
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
- Fixed in: 1.1.1w-0+deb11u5
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Issue summary: 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:11 openssl to version 1.1.1w-0+deb11u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-69420
- https://github.com/openssl/openssl/commit/27c7012c91cc986a598d7540f3079dfde2416eb9
- https://github.com/openssl/openssl/commit/4e254b48ad93cc092be3dd62d97015f33f73133a
- https://github.com/openssl/openssl/commit/564fd9c73787f25693bf9e75faf7bf6bb1305d4e
- https://github.com/openssl/openssl/commit/5eb0770ffcf11b785cf374ff3c19196245e54f1b
- https://github.com/openssl/openssl/commit/a99349ebfc519999edc50620abe24d599b9eb085
- https://openssl-library.org/news/secadv/20260127.txt
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
- Fixed in: 1.1.1w-0+deb11u4
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Issue summary: 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:11 openssl to version 1.1.1w-0+deb11u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-9230
- https://github.com/openssl/openssl/commit/5965ea5dd6960f36d8b7f74f8eac67a8eb8f2b45
- https://github.com/openssl/openssl/commit/9e91358f365dee6c446dcdcdb01c04d2743fd280
- https://github.com/openssl/openssl/commit/a79c4ce559c6a3a8fd4109e9f33c1185d5bf2def
- https://github.com/openssl/openssl/commit/b5282d677551afda7d20e9c00e09561b547b2dfd
- https://github.com/openssl/openssl/commit/bae259a211ada6315dc50900686daaaaaa55f482
- https://github.openssl.org/openssl/extended-releases/commit/c2b96348bfa662f25f4fabf81958ae822063dae3
- https://github.openssl.org/openssl/extended-releases/commit/dfbaf161d8dafc1132dd88cd48ad990ed9b4c8ba
- https://openssl-library.org/news/secadv/20250930.txt
- https://lists.debian.org/debian-lts-announce/2025/10/msg00001.html
- http://www.openwall.com/lists/oss-security/2025/09/30/5
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-089022.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
- https://cert-portal.siemens.com/productcert/html/ssa-485750.html
- https://cert-portal.siemens.com/productcert/html/ssa-253495.html
- https://cert-portal.siemens.com/productcert/html/ssa-585531.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
- Fixed in: 1.1.1w-0+deb11u5
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Issue summary: 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:11 openssl to version 1.1.1w-0+deb11u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-22795
- https://github.com/openssl/openssl/commit/2502e7b7d4c0cf4f972a881641fe09edc67aeec4
- https://github.com/openssl/openssl/commit/572844beca95068394c916626a6d3a490f831a49
- https://github.com/openssl/openssl/commit/7bbca05be55b129651d9df4bdb92becc45002c12
- https://github.com/openssl/openssl/commit/eeee3cbd4d682095ed431052f00403004596373e
- https://github.com/openssl/openssl/commit/ef2fb66ec571564d64d1c74a12e388a2a54d05d2
- https://openssl-library.org/news/secadv/20260127.txt
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
- Fixed in: 1.1.1w-0+deb11u5
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Issue summary: 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:11 openssl to version 1.1.1w-0+deb11u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-22796
- https://github.com/openssl/openssl/commit/2502e7b7d4c0cf4f972a881641fe09edc67aeec4
- https://github.com/openssl/openssl/commit/572844beca95068394c916626a6d3a490f831a49
- https://github.com/openssl/openssl/commit/7bbca05be55b129651d9df4bdb92becc45002c12
- https://github.com/openssl/openssl/commit/eeee3cbd4d682095ed431052f00403004596373e
- https://github.com/openssl/openssl/commit/ef2fb66ec571564d64d1c74a12e388a2a54d05d2
- https://openssl-library.org/news/secadv/20260127.txt
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
- Fixed in: 1.1.1w-0+deb11u8
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Issue summary: Parsing a crafted DER-encoded ASN.1 structure with a primitive element whose content exceeds 2 gigabytes in length may cause a heap buffer over-read on 64-bit Unix and Unix-like platforms.
Impact summary: The heap buffer over-read may crash the application (Denial of Service) or to load into the decoded ASN.1 object contents of memory beyond the end of the input buffer. More typically such ASN.1 elements would instead be truncated.
An integer truncation in OpenSSL's ASN.1 decoder causes the content length of an ASN.1 primitive element to be mishandled when it exceeds 2 gigabytes. In the worst case the truncated length is treated as a request to scan the binary content for a terminating zero byte, possibly causing OpenSSL to read either less than or beyond the end of the allocated buffer.
Applications that pass attacker-supplied data to d2i_X509(), d2i_PKCS7(), or any other d2i_* decoding function are affected. OpenSSL's own command-line tools are not vulnerable, as data read through the BIO layer is checked before it reaches the affected code. The issue only affects 64-bit Unix and Unix-like platforms; 32-bit platforms and 64-bit Windows are not affected.
The FIPS modules in 4.0, 3.6, 3.5, 3.4 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.
Remediation
Upgrade Debian:11 openssl to version 1.1.1w-0+deb11u8 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-34180
- https://github.com/openssl/security/commit/1c6908e4fa5fa568752221d8eaf561a809751e5d
- https://github.com/openssl/security/commit/cbe418ae978539cf14a398a207dba834c0e93e83
- https://github.com/openssl/security/commit/d93853c42110d6319e3df07842b488cb9f7ac5ff
- https://github.com/openssl/security/commit/da5d62af75f69d6fbf7803743d7c56ac75461e43
- https://github.com/openssl/security/commit/f696c73c3e61b8c502d040af62e690c060908a16
- https://github.com/openssl/openssl/commit/1c6908e4fa5fa568752221d8eaf561a809751e5d
- https://github.com/openssl/openssl/commit/cbe418ae978539cf14a398a207dba834c0e93e83
- https://github.com/openssl/openssl/commit/d93853c42110d6319e3df07842b488cb9f7ac5ff
- https://github.com/openssl/openssl/commit/da5d62af75f69d6fbf7803743d7c56ac75461e43
- https://github.com/openssl/openssl/commit/f696c73c3e61b8c502d040af62e690c060908a16
- https://openssl-library.org/news/secadv/20260609.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
- Fixed in: 1.1.1w-0+deb11u8
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Issue summary: A specially crafted password-encrypted CMS message can trigger a NULL pointer dereference during CMS decryption.
Impact summary: This NULL pointer dereference leads to an application crash and a Denial of Service.
The CMS PasswordRecipientInfo.keyDerivationAlgorithm field is defined as OPTIONAL in the ASN.1 specification and may therefore be absent in specially crafted inputs. During the password-based CMS decryption the OpenSSL CMS implementation dereferences this field without first checking whether it was present.
An attacker who supplies such a CMS message to an application performing password-based CMS decryption can trigger an application crash, leading to a Denial of Service.
Applications that process password-encrypted CMS messages may be affected.
The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.
Remediation
Upgrade Debian:11 openssl to version 1.1.1w-0+deb11u8 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-42766
- https://github.com/openssl/security/commit/056d06c1918fafbb98c1c85a02e4c47cc4e199ce
- https://github.com/openssl/security/commit/12bc26ffb3a2be728c9b86e1cae277de5b33dfa4
- https://github.com/openssl/security/commit/3ff64913615d648cfbb6a6f1cf5529ae7ea829d7
- https://github.com/openssl/security/commit/ab52d88cb5374876d59aee3c91f9e4ccce2b7ce4
- https://github.com/openssl/security/commit/da26f368732b83e40e9d356fe61c3d3aaab6d2e8
- https://github.com/openssl/openssl/commit/056d06c1918fafbb98c1c85a02e4c47cc4e199ce
- https://github.com/openssl/openssl/commit/12bc26ffb3a2be728c9b86e1cae277de5b33dfa4
- https://github.com/openssl/openssl/commit/3ff64913615d648cfbb6a6f1cf5529ae7ea829d7
- https://github.com/openssl/openssl/commit/ab52d88cb5374876d59aee3c91f9e4ccce2b7ce4
- https://github.com/openssl/openssl/commit/da26f368732b83e40e9d356fe61c3d3aaab6d2e8
- https://openssl-library.org/news/secadv/20260609.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
- Fixed in: 1.1.1w-0+deb11u8
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Issue summary: A specially crafted PKCS#7 or S/MIME signed message could trigger a use-after-free during PKCS#7 signature verification.
Impact summary: A use-after-free may result in process crashes, heap corruption, or potentially remote code execution.
When processing a PKCS#7 or S/MIME signed message, if the SignedData digestAlgorithms field is present as an empty ASN.1 SET, OpenSSL may incorrectly free a caller-owned BIO during PKCS7_verify(). A subsequent use of the BIO by the calling application results in a use-after-free condition.
In the common case this occurs when the application later calls BIO_free() on the BIO originally passed to PKCS7_verify(). Depending on allocator behavior and application-specific BIO usage patterns, this may result in a crash or other memory corruption. In some application contexts this may potentially be exploitable for remote code execution.
Applications that process PKCS#7 or S/MIME signed messages using OpenSSL PKCS#7 APIs may be affected. Applications using the CMS APIs for this processing are not affected.
The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.
Remediation
Upgrade Debian:11 openssl to version 1.1.1w-0+deb11u8 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-45447
- https://github.com/openssl/security/commit/3aad5eb7af4de4ee0633c30a8541a54d9bbde63c
- https://github.com/openssl/security/commit/7d4a980c62258c5910cc883936e0c8dbab4d75a8
- https://github.com/openssl/security/commit/9dfd688ad2290fc5075cacbc9bf0c9a93eefed54
- https://github.com/openssl/security/commit/a541ae8bfe849a30cc885e8780715c0f488e496c
- https://github.com/openssl/security/commit/c505d7559da5d5f9f2c3913c6883a5562ce7273e
- https://github.com/openssl/openssl/commit/3aad5eb7af4de4ee0633c30a8541a54d9bbde63c
- https://github.com/openssl/openssl/commit/7d4a980c62258c5910cc883936e0c8dbab4d75a8
- https://github.com/openssl/openssl/commit/9dfd688ad2290fc5075cacbc9bf0c9a93eefed54
- https://github.com/openssl/openssl/commit/a541ae8bfe849a30cc885e8780715c0f488e496c
- https://github.com/openssl/openssl/commit/c505d7559da5d5f9f2c3913c6883a5562ce7273e
- https://openssl-library.org/news/secadv/20260609.txt
- https://access.redhat.com/errata/RHSA-2026:25237
- https://access.redhat.com/errata/RHSA-2026:25239
- https://access.redhat.com/errata/RHSA-2026:26275
- https://access.redhat.com/errata/RHSA-2026:26319
- https://access.redhat.com/errata/RHSA-2026:29197
- https://access.redhat.com/errata/RHSA-2026:34102
- https://access.redhat.com/errata/RHSA-2026:35869
- https://access.redhat.com/errata/RHSA-2026:36215
- https://access.redhat.com/errata/RHSA-2026:36217
- https://access.redhat.com/errata/RHSA-2026:39009
- https://access.redhat.com/errata/RHSA-2026:39012
- https://access.redhat.com/errata/RHSA-2026:39981
- https://access.redhat.com/security/cve/CVE-2026-45447
- https://bugzilla.redhat.com/show_bug.cgi?id=2481898
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-45447.json
- https://access.redhat.com/errata/RHSA-2026:44438
- https://access.redhat.com/errata/RHSA-2026:47735
- https://access.redhat.com/errata/RHSA-2026:47737
- https://access.redhat.com/errata/RHSA-2026:58563
- https://access.redhat.com/errata/RHSA-2026:58981
- https://access.redhat.com/errata/RHSA-2026:59831
- https://access.redhat.com/errata/RHSA-2026:66524
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Issue summary: Receiving a DTLS record for a future epoch while a handshake is in progress causes OpenSSL to buffer far more memory than the record itself requires.
Impact summary: A peer can use a small amount of network traffic to make an OpenSSL DTLS endpoint retain a disproportionately large amount of memory, which may lead to a Denial of Service.
CWE: CWE-405: Asymmetric Resource Consumption (Amplification)
Description: While a DTLS handshake is in progress, a peer may legitimately have already moved on to the next epoch (for example, having sent its ChangeCipherSpec and Finished messages) before the local endpoint has processed the same transition, typically because of reordering on the underlying UDP transport. OpenSSL buffers such early records so that they can be processed once the local endpoint catches up.
Buffering a record currently retains the entire read buffer it arrived in, which is sized to hold the largest possible DTLS record (around 16 kilobytes), rather than just the bytes that make up the record itself. Up to 100 such records may be buffered per connection. As a result, a peer that sends a stream of small forged records claiming to belong to the next epoch can cause an OpenSSL DTLS endpoint to retain around 1.7 megabytes of memory, despite sending only a small fraction of that amount of data over the network.
An attacker therefore gains a memory amplification factor of around 1200, and can multiply the effect across as many associations as it is able to open, making this a remote memory exhaustion Denial of Service risk for DTLS servers. Since the memory retained per connection remains bounded, and any limit an application already places on the number of concurrent associations also bounds the total exposure, this issue has been assessed as Low severity.
FIPS impact: no
No FIPS modules are affected by this issue as the affected code is outside the OpenSSL FIPS module boundary.
OpenSSL 4.0, 3.6, 3.5, 3.4, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.
OpenSSL 4.0 users should upgrade to OpenSSL 4.0.2. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.4. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.8. OpenSSL 3.4 users should upgrade to OpenSSL 3.4.7. OpenSSL 3.0 users should upgrade to OpenSSL 3.0.22.
Premium support customers only: OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1zi OpenSSL 1.0.2 users should upgrade to OpenSSL 1.0.2zr
This issue was reported on 18 May 2026 by Amazon Web Services. The fix has been developed by Matt Caswell.
-- cut (non-publishing metadata for internal use) -- Reported by: Amazon Web Services Fixed by: Matt Caswell
Remediation
There is no fixed version for Debian:11 openssl.
References
- https://security-tracker.debian.org/tracker/CVE-2026-54874
- https://github.com/openssl/openssl/commit/4808b5d64176451f3d93d87d0ac9c81a9b13fb23
- https://github.com/openssl/openssl/commit/7110cb2f75806d0bf809eb2f90790d477900be40
- https://github.com/openssl/openssl/commit/a0c8ec557d9cac078f032d76cdf684fe743eb382
- https://github.com/openssl/openssl/commit/cc0c6710917cd5eec001b297355d2ba723505107
- https://github.com/openssl/openssl/commit/f52ffc11b90737ac89083909618dc2e1f42c561c
- https://openssl-library.org/news/secadv/20260825.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Issue summary: OpenSSL CMS decryption sizes the key-unwrap output buffer based on querying the unwrapped key size, but the AES-WRAP-PAD unwrap primitive can write and cleanse more bytes than that query reports, causing an 8-byte out-of-bounds heap write.
Impact summary: An attacker who supplies a crafted CMS message can trigger a deterministic 8-byte out-of-bounds heap write when the victim decrypts it with CMS_decrypt(), corrupting the heap and typically resulting in a Denial of Service.
CWE: CWE-787: Out-of-bounds Write
Description: The key-wrap OID is potentially attacker-controlled on the wire. CMS unwrapping allows both id-aesNNN-wrap-pad and id-aesNNN-wrap ciphers. An attacker can take a legitimate message and change a single OID byte to select the padded variant while leaving the message otherwise valid. Since the unwrap key is derived from the recipient's private operation (ECDH key agreement or ML-KEM decapsulation), the RFC 5649 integrity check cannot pass, and the decryption fails with integrity failure.
The write is a fixed-size (8-byte), fixed-value (zero) heap overflow immediately past the allocation, requires no special configuration, and is reachable from the public CMS_decrypt() function. The consequence is a heap corruption leading to a Denial of Service. The fix in the CMS code sizes the unwrap output buffer for the worst case so a failed unwrap cannot write past the allocation.
FIPS impact: no
As the CMS code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.
Remediation
There is no fixed version for Debian:11 openssl.
References
- https://security-tracker.debian.org/tracker/CVE-2026-63072
- https://github.com/openssl/openssl/commit/2a3dac874c8057c1f0186849bf1ede1ae7b6b756
- https://github.com/openssl/openssl/commit/87784ad619af36b8807c2044b3940006fccc1e42
- https://github.com/openssl/openssl/commit/9530a5fd1aacaeccdced4478ea2340a480613335
- https://github.com/openssl/openssl/commit/9ec2f6d2ae2bcad907cf7ee38584855bafe4979a
- https://github.com/openssl/openssl/commit/a0c8ec557d9cac078f032d76cdf684fe743eb382
- https://openssl-library.org/news/secadv/20260825.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Issue summary: The OpenSSL Certificate Management Protocol (CMP) caches additional certificates (extraCerts) sent in a CMP message, but never expunges them (for instance if they are invalid). If a server reuses an OSSL_CMP_CTX frequently, this cache of extraCerts may grow unboundedly, and a malicious client may flood a CMP server with requests driving this growth.
Impact summary: Users utilizing a CMP server that reuses a single OSSL_CMP_CTX for the lifetime of a server process may observe unbounded memory growth in the event a malicious client repeatedly sends requests containing unique extra certificates, which may lead to OOM conditions.
CWE: CWE-770: Allocation of Resources Without Limits or Throttling
Description: If a remote user sends CMP messages to a server with a list of extraCerts and the message is rejected, the extraCerts from the message remains in the server contexts untrusted certificate stack. This exposes servers with long lived ctx objects to Denial of Service attacks in which an attacker sends messages intending to be rejected with a large list of additional certificates repeatedly, forcing the server to store them indefinitely.
The issue was fixed by removing the added extra certs if the message is rejected, using the same method as when the context is configured to not do caching at all.
FIPS impact: no As the CMP code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.
Remediation
There is no fixed version for Debian:11 openssl.
References
- https://security-tracker.debian.org/tracker/CVE-2026-63074
- https://github.com/openssl/openssl/commit/01e567978a55fba18142a230380c31296049fae7
- https://github.com/openssl/openssl/commit/21a5d9658b0c66daace60e10ea18ff32a448de9f
- https://github.com/openssl/openssl/commit/74ae7f6df47a5767c1010b88c47507dfc5b32c46
- https://github.com/openssl/openssl/commit/75360af9650d4e0c82ba0050c5c9912cd79e54af
- https://github.com/openssl/openssl/commit/f636f9ca0fa1bae5b42f9e787f025c96fb09c43a
- https://openssl-library.org/news/secadv/20260825.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Issue summary: OpenSSL CMP password based protection verification only checks whether the protectionAlg parameter was not NULL and not its ASN.1 type, before treating it as a PBMParameter. A crafted message can contain a parameter of a different type, which is then dereferenced as an invalid pointer.
Impact summary: A remote, unauthenticated attacker can crash an application acting as a CMP server that accepts PBM-protected messages, or a CMP client talking to a malicious or intercepted CMP server, resulting in a Denial of Service.
CWE: CWE-476: NULL Pointer Dereference
Description: When verifying the password-based MAC protection of a CMP message, OpenSSL library reads the protectionAlg algorithm parameter with X509_ALGOR_get0(), which returns both the parameter type and its value pointer. The value is then cast to an ASN1_STRING and treated as the expected PBMParameter after only checking that pointer is not NULL. The parameter type returned by X509_ALGOR_get0() was never consulted.
This happens during protection verification, before any MAC is computed, so no knowledge of the PBM shared secret is required; the only precondition is that PBM verification is reachable. On the server side this is reached from OSSL_CMP_SRV_process_request() for any application that stands up a CMP server accepting PBM-protected messages, and on the client side from CMP response validation against a malicious or on-path (MITM) server. The reliable consequence is a denial of service; there is no memory disclosure, no controlled memory write, and no path to code execution. CMP is a specialized feature that an application must explicitly enable.
FIPS impact: no As the CMP code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.
Remediation
There is no fixed version for Debian:11 openssl.
References
- https://security-tracker.debian.org/tracker/CVE-2026-63076
- https://github.com/openssl/openssl/commit/37882aa2e0256e1072442a8f62f7db45b995c45b
- https://github.com/openssl/openssl/commit/a17cc8d612ecff6d94a9b7ca8b5283ddf5ff570e
- https://github.com/openssl/openssl/commit/a1f348ccb328c3afbd4ba6883f9b7c813c043259
- https://github.com/openssl/openssl/commit/a7af46a92d0ce19a90e669ef56d2576a07924226
- https://github.com/openssl/openssl/commit/cdacfff557389abfa9e4615abded2ec984517d6c
- https://openssl-library.org/news/secadv/20260825.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
- Fixed in: 1.1.1w-0+deb11u8
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Issue summary: A signed integer overflow when sizing the destination buffer for Unicode output in ASN1_mbstring_ncopy() can lead to a heap buffer overflow.
Impact summary: A heap buffer overflow may lead to a crash or possibly attacker controlled code execution or other undefined behaviour.
In ASN1_mbstring_copy() and ASN1_mbstring_ncopy() the destination size for Unicode output is computed in a signed int: by left shift of the input character count for BMPSTRING (UTF-16) and UNIVERSALSTRING (UTF-32), and by summing per-character byte counts for UTF8STRING. The calculation overflows when the input reaches around 2^30 characters. In the worst case (UNIVERSALSTRING at 2^30 characters) the size wraps to zero, OPENSSL_malloc(1) is called, and the subsequent character copy writes several gigabytes past the one-byte allocation.
X.509 certificate processing routes through ASN1_STRING_set_by_NID(), whose DIRSTRING_TYPE mask excludes UNIVERSALSTRING and whose per-NID size limits cap the input length; no network protocol or certificate-handling path in OpenSSL exercises the overflow. Triggering the bug requires an application that calls ASN1_mbstring_copy() or ASN1_mbstring_ncopy() directly, or registers a custom string type via ASN1_STRING_TABLE_add(), with attacker-controlled input on the order of half a gigabyte or more. For these reasons this issue was assigned Low severity.
The FIPS modules in 4.0, 3.6, 3.5, 3.4 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.
Remediation
Upgrade Debian:11 openssl to version 1.1.1w-0+deb11u8 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-7383
- https://github.com/openssl/security/commit/4f8d2bddaa2c8e06f9c33390ee1717059a6e4be6
- https://github.com/openssl/security/commit/80c15faaf78042bbb8654a0e234c50c381732f74
- https://github.com/openssl/security/commit/bd17511070fb39a67bfa19682affb765e706a974
- https://github.com/openssl/security/commit/c332adaced43bcbb85f97410597e951c11ec3083
- https://github.com/openssl/security/commit/d32350ae8ef7426718f5aa9e383d4b51398ee255
- https://github.com/openssl/openssl/commit/4f8d2bddaa2c8e06f9c33390ee1717059a6e4be6
- https://github.com/openssl/openssl/commit/80c15faaf78042bbb8654a0e234c50c381732f74
- https://github.com/openssl/openssl/commit/bd17511070fb39a67bfa19682affb765e706a974
- https://github.com/openssl/openssl/commit/c332adaced43bcbb85f97410597e951c11ec3083
- https://github.com/openssl/openssl/commit/d32350ae8ef7426718f5aa9e383d4b51398ee255
- https://openssl-library.org/news/secadv/20260609.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Issue summary: ChaCha20-Poly1305 and AES-OCB decryption with an empty ciphertext can report success without verifying the supplied authentication tag when the operation is finalized by calling the EVP_Cipher() function.
Impact summary: Applications calling EVP_Cipher() on an empty ciphertext and expecting the call to check the AEAD tag may accept forged messages.
CWE: CWE-354 (Improper Validation of Integrity Check Value)
Description: The EVP_Cipher() API call for AEAD ciphers behaves like a one shot encryption and decryption call. It also verifies the AEAD tag after the decryption operation. However for AES-OCB and ChaCha20-Poly1305 ciphers it skipped the AEAD tag verification when an empty ciphertext was passed to the function. The callers of this function might believe that a successful return indicates a valid AEAD tag for these ciphers, even when that has not truly been validated in this case.
FIPS impact: no The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this CVE as the affected algorithms are not FIPS approved and thus not implemented in the FIPS module.
Remediation
There is no fixed version for Debian:11 openssl.
References
- https://security-tracker.debian.org/tracker/CVE-2026-75803
- https://github.com/openssl/openssl/commit/119ab9555dc62275bbd71f6f49529b1a44feba42
- https://github.com/openssl/openssl/commit/3621257986e27e540bf96a11570929a6e5a9e05b
- https://github.com/openssl/openssl/commit/6c7aa6f8f6449b7fe0137ee8be65fcd239bd7d6a
- https://github.com/openssl/openssl/commit/bdeb0cd994d915342787f117ee75044f0dc36f34
- https://github.com/openssl/openssl/commit/bf95f5f772e9362f87b25cfa2f8cb15d984865b9
- https://openssl-library.org/news/secadv/20260825.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1n-0+deb11u2 and openssl/libssl1.1@1.1.1n-0+deb11u2
- Fixed in: 1.1.1w-0+deb11u8
Detailed paths
-
Introduced through: nginx@1.21 › openssl@1.1.1n-0+deb11u2
-
Introduced through: nginx@1.21 › openssl/libssl1.1@1.1.1n-0+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Issue summary: When CMS password-based decryption (RFC 3211 / PWRI key unwrap) processes attacker-supplied CMS data, an attacker-chosen stream-mode KEK cipher can trigger a heap out-of-bounds read in kek_unwrap_key().
Impact summary: A heap buffer over-read may trigger a crash which leads to Denial of Service for an application if the input buffer ends at a memory page boundary and the following page is unmapped. There is no information disclosure as the over-read bytes are not revealed to the attacker.
The key unwrapping function performs a check-byte test as specified in the RFC that reads 7 bytes from a heap allocation that is based on the wrapped key length from the message. There is a minimum length check based on the block length of the wrapping cipher. However the cipher is selected from an OID carried in the attacker's PWRI keyEncryptionAlgorithm with no requirement that the cipher be a block cipher. When an attacker selects a stream-mode cipher the guard will be ineffective and the allocated buffer containing the unwrapped key can be too small to fit the check-bytes specified in the RFC and a buffer over-read can happen.
Applications calling CMS_decrypt() or CMS_decrypt_set1_password() (equivalently openssl cms -decrypt -pwri_password ...) on untrusted CMS data are vulnerable to this issue. No password knowledge is required: the over-read happens during the unwrap attempt before any authentication succeeds.
The over-read is limited to a few bytes and is not written to output, so there is no information disclosure. Triggering a crash requires the allocation to border unmapped memory, which is unlikely with the normal allocator.
The FIPS modules are not affected by this issue.
Remediation
Upgrade Debian:11 openssl to version 1.1.1w-0+deb11u8 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-9076
- https://github.com/openssl/security/commit/05b066366842f930fadd9a6e94df98030af431bb
- https://github.com/openssl/security/commit/3d8d5bc1056b2f62da9fede23fedbf47e85187b0
- https://github.com/openssl/security/commit/715349a1d7c6db970e6815dafb90915f07307f98
- https://github.com/openssl/security/commit/77bf00ab13f6ff5e516535432f0328ed70ec0c26
- https://github.com/openssl/security/commit/eecbe330977e8d023aae1ca2d9bdbe983ef3fdc6
- https://github.com/openssl/openssl/commit/05b066366842f930fadd9a6e94df98030af431bb
- https://github.com/openssl/openssl/commit/3d8d5bc1056b2f62da9fede23fedbf47e85187b0
- https://github.com/openssl/openssl/commit/715349a1d7c6db970e6815dafb90915f07307f98
- https://github.com/openssl/openssl/commit/77bf00ab13f6ff5e516535432f0328ed70ec0c26
- https://github.com/openssl/openssl/commit/eecbe330977e8d023aae1ca2d9bdbe983ef3fdc6
- https://openssl-library.org/news/secadv/20260609.txt
low severity
- Vulnerable module: pam/libpam-modules
- Introduced through: pam/libpam-modules@1.4.0-9+deb11u1, pam/libpam-modules-bin@1.4.0-9+deb11u1 and others
Detailed paths
-
Introduced through: nginx@1.21 › pam/libpam-modules@1.4.0-9+deb11u1
-
Introduced through: nginx@1.21 › pam/libpam-modules-bin@1.4.0-9+deb11u1
-
Introduced through: nginx@1.21 › pam/libpam-runtime@1.4.0-9+deb11u1
-
Introduced through: nginx@1.21 › pam/libpam0g@1.4.0-9+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream pam package and not the pam package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Linux-PAM through 1.7.2 contains an observable timing discrepancy (CWE-208) in the pam_userdb module's plaintext-password comparison path in modules/pam_userdb/pam_userdb.c that allows a local or network-adjacent attacker able to repeatedly drive authentication through a calling service to recover the plaintext password of a target account by measuring response-timing differences.
Remediation
There is no fixed version for Debian:11 pam.
References
- https://security-tracker.debian.org/tracker/CVE-2026-54411
- https://cwe.mitre.org/data/definitions/208.html
- https://github.com/linux-pam/linux-pam
- https://github.com/linux-pam/linux-pam/blob/master/libpam/include/pam_inline.h
- https://github.com/linux-pam/linux-pam/blob/master/modules/pam_userdb/pam_userdb.c#L327
low severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.32.1-4+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › perl/perl-base@5.32.1-4+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
IO::Uncompress::Unzip versions before 2.215 for Perl propagate uncaught exception when parsing zip header with malformed DOS date.
_dosToUnixTime() decodes the local-file-header last-modification date field and calls Time::Local::timelocal() without an eval guard. A header whose date field decodes to an out-of-range month, day, or hour causes timelocal() to die.
The exception propagates out of IO::Uncompress::Unzip->new($file) where callers expect undef plus $UnzipError.
Remediation
There is no fixed version for Debian:11 perl.
References
- https://security-tracker.debian.org/tracker/CVE-2025-15649
- https://github.com/pmqs/IO-Compress/commit/fd28c1d2374eee9811f6d0c5bddc0957abdf1da8.patch
- https://github.com/pmqs/IO-Compress/issues/65
- https://metacpan.org/release/PMQS/IO-Compress-2.215/changes
- http://www.openwall.com/lists/oss-security/2026/05/27/1
low severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.32.1-4+deb11u2
- Fixed in: 5.32.1-4+deb11u5
Detailed paths
-
Introduced through: nginx@1.21 › perl/perl-base@5.32.1-4+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
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:11 perl to version 5.32.1-4+deb11u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-40909
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098226
- https://github.com/Perl/perl5/commit/11a11ecf4bea72b17d250cfb43c897be1341861e
- https://github.com/Perl/perl5/commit/918bfff86ca8d6d4e4ec5b30994451e0bd74aba9.patch
- https://github.com/Perl/perl5/issues/10387
- https://github.com/Perl/perl5/issues/23010
- https://perldoc.perl.org/5.14.0/perl5136delta#Directory-handles-not-copied-to-threads
- https://www.openwall.com/lists/oss-security/2025/05/22/2
- http://www.openwall.com/lists/oss-security/2025/05/23/1
- http://www.openwall.com/lists/oss-security/2025/05/30/4
- http://www.openwall.com/lists/oss-security/2025/06/02/2
- http://www.openwall.com/lists/oss-security/2025/06/02/5
- http://www.openwall.com/lists/oss-security/2025/06/02/6
- http://www.openwall.com/lists/oss-security/2025/06/02/7
- http://www.openwall.com/lists/oss-security/2025/06/03/1
- http://seclists.org/fulldisclosure/2025/Sep/53
- http://seclists.org/fulldisclosure/2025/Sep/54
- http://seclists.org/fulldisclosure/2025/Sep/55
- https://lists.debian.org/debian-lts-announce/2026/04/msg00018.html
low severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.32.1-4+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › perl/perl-base@5.32.1-4+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Socket versions before 2.041 for Perl have an out-of-bounds heap read.
In Socket.xs, pack_ip_mreq_source() checks the length of its source argument before the argument is read, so the check tests the byte length carried over from the preceding multiaddr argument instead. Both addresses occupy a 4-byte field, so a valid multiaddr lets a source of any length pass the check, and the source is then copied into the 4-byte imr_sourceaddr field with a fixed-size copy. A source shorter than 4 bytes is not rejected, and the copy reads up to 3 bytes past the end of its buffer.
Calling pack_ip_mreq_source() with a source value shorter than 4 bytes copies adjacent heap memory into the returned packed structure.
Remediation
There is no fixed version for Debian:11 perl.
References
low severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.32.1-4+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › perl/perl-base@5.32.1-4+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Perl versions through 5.45.1 have out-of-bounds heap reads and writes during regular expression matching via an undersized superlinear cache in S_regmatch.
The regex engine's superlinear cache holds one bit per subject position for each participating WHILEM node, so the bit count is the subject length plus one times the number of nodes. Nothing checks that product for positive overflow of the signed 32-bit count: a 286331153 byte subject matched against a pattern with 15 participating nodes stores the count as 14, leaving a two byte cache. The cache is then indexed from the real match position and node number, so reads go past the end of the allocation, and on failure CACHEsayNO sets a bit past it.
A caller that matches an attacker controlled subject of this size against a pattern of this shape can crash the process or corrupt heap memory.
Remediation
There is no fixed version for Debian:11 perl.
References
- https://security-tracker.debian.org/tracker/CVE-2026-15534
- https://github.com/Perl/perl5/commit/54cf3d44cbbedd17d774e9a37921963e8fd5d0cb.patch
- https://github.com/Perl/perl5/commit/568e6fd238867bb9e99fa3f47cba3169009239e0.patch
- http://www.openwall.com/lists/oss-security/2026/08/09/12
- http://www.openwall.com/lists/oss-security/2026/08/09/13
low severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.32.1-4+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › perl/perl-base@5.32.1-4+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Perl versions from 5.9.4 before 5.41.9 produce incorrect regular expression match results when a stale failure flag ends the Aho-Corasick prescan early in S_find_byclass.
The prescan walks the subject for positions where the full pattern could match, and the engine tries it from the leftmost one recorded. A failing transition sets the failed flag, and a later successful transition does not clear it, so the prescan reads the stale flag as a failure and stops before it can record a candidate that starts earlier. It takes a subject where one candidate is recorded and a later character then forces a fallback through a fail link that succeeds.
Example:
"ABCDE" =~ m/ABCF|BCDE|C/; # matches C at offset 2, not BCDE "ABCDE" =~ m/ABCF|BCDE|C(G)/; # no match, BCDE missed
An alternation like this can miss input it should match, or match it on the wrong branch, so an access or filtering decision made from the result can be wrong.
Remediation
There is no fixed version for Debian:11 perl.
References
low severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.32.1-4+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › perl/perl-base@5.32.1-4+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
IO::Uncompress::Unzip versions before 2.220 for Perl allow CPU exhaustion via per-byte read loop in fastForward.
fastForward() compares length $offset (the digit count of the offset, 1 to 19) against the chunk size $c instead of $offset itself, so $c shrinks from 16 KiB to 1-19 bytes per iteration.
Extracting a named entry from an attacker supplied zip via IO::Uncompress::Unzip->new($zip, Name => $target) drives a per-byte read loop scaling with the entry's compressed size, up to the non-Zip64 4 GiB cap.
Remediation
There is no fixed version for Debian:11 perl.
References
low severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.32.1-4+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › perl/perl-base@5.32.1-4+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
IO::Compress versions from 2.207 before 2.220 for Perl ship a zipdetails CLI tool that crashes with undefined subroutine on Info-ZIP Unix Extra Field with 8-byte UID or GID.
When decode_ux() in bin/zipdetails handles an Info-ZIP Unix Extra Field (tag 0x7875) with UID Size or GID Size set to 8, causing zipdetails to decode an 8-byte UID or GID value, it dispatches through decodeLitteEndian(), which calls a misnamed helper unpackValueQ. The actual function defined in the same file is unpackValue_Q (with underscore); the call raises 'Undefined subroutine &main::unpackValueQ' and the script exits with status 255.
Library callers of IO::Compress and IO::Uncompress are not affected; the defect is in the bundled CLI tool.
Remediation
There is no fixed version for Debian:11 perl.
References
low severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.32.1-4+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › perl/perl-base@5.32.1-4+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
IO::Compress versions before 2.220 for Perl can execute arbitrary code in File::GlobMapper via an attacker-controlled output glob.
_parseOutputGlob() wraps the caller-supplied output glob string in double quotes and stores it in the parser state; _getFiles() then runs the stored expression through eval STRING. A literal double quote in the output glob closes the dquote wrapper, and the characters that follow are evaluated as Perl.
Arbitrary Perl in the output glob executes at the calling process's privilege.
Remediation
There is no fixed version for Debian:11 perl.
References
- https://security-tracker.debian.org/tracker/CVE-2026-48962
- https://github.com/pmqs/IO-Compress/commit/f2db247bf90d4cc7ee2710be384946081f3b4610.patch
- https://metacpan.org/release/PMQS/IO-Compress-2.220/changes
- http://www.openwall.com/lists/oss-security/2026/05/27/4
- https://access.redhat.com/errata/RHSA-2026:29182
- https://access.redhat.com/errata/RHSA-2026:29210
- https://access.redhat.com/errata/RHSA-2026:29867
- https://access.redhat.com/errata/RHSA-2026:29941
- https://access.redhat.com/errata/RHSA-2026:30085
- https://access.redhat.com/errata/RHSA-2026:30086
- https://access.redhat.com/errata/RHSA-2026:30115
- https://access.redhat.com/errata/RHSA-2026:30843
- https://access.redhat.com/errata/RHSA-2026:30851
- https://access.redhat.com/errata/RHSA-2026:30858
- https://access.redhat.com/errata/RHSA-2026:30859
- https://access.redhat.com/errata/RHSA-2026:30860
- https://access.redhat.com/security/cve/CVE-2026-48962
- https://bugzilla.redhat.com/show_bug.cgi?id=2481767
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-48962.json
- https://access.redhat.com/errata/RHSA-2026:50262
low severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.32.1-4+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › perl/perl-base@5.32.1-4+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Storable versions before 3.41 for Perl have a signed integer overflow when deserializing a crafted SX_HOOK record.
retrieve_hook_common reads a signed 32-bit item count from an SX_HOOK record and calls av_extend with that count plus one. A count of I32_MAX wraps the addition to a negative value.
A crafted blob passed to thaw or retrieve triggers the overflow; av_extend receives the negative count and dies with a panic, terminating the deserialization.
Remediation
There is no fixed version for Debian:11 perl.
References
low severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.32.1-4+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › perl/perl-base@5.32.1-4+deb11u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
HTTP::Tiny versions before 0.093 for Perl do not validate CRLF in HTTP request lines or control field header values.
The unvalidated inputs are the method and URI in the request line, the URL host that becomes the Host: header, and HTTP/1.1 control data field values.
An attacker who controls one of these inputs, for example a user supplied URL passed to a webhook or URL fetch endpoint, can inject additional headers and smuggle requests to the upstream server.
Remediation
There is no fixed version for Debian:11 perl.
References
low severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.32.1-4+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › perl/perl-base@5.32.1-4+deb11u2
NVD Description
This vulnerability has not been analyzed by NVD yet.
Remediation
There is no fixed version for Debian:11 perl.
References
low severity
- Vulnerable module: sed
- Introduced through: sed@4.7-1
Detailed paths
-
Introduced through: nginx@1.21 › sed@4.7-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream sed package and not the sed package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
When sed is invoked with both -i (in-place edit) and --follow-symlinks, the function open_next_file() performs two separate, non-atomic filesystem operations on the same path:
- resolves symlink to its target and stores the resolved path for determining when output is written,
- opens the original symlink path (not the resolved one) to read the file. Between these two calls there is a race window. If an attacker atomically replaces the symlink with a different target during that window, sed will: read content from the new (attacker-chosen) symlink target and write the processed result to the path recorded in step 1. This can lead to arbitrary file overwrite with attacker-controlled content in the context of the sed process.
This issue was fixed in version 4.10.
Remediation
There is no fixed version for Debian:11 sed.
References
low severity
- Vulnerable module: shadow/login
- Introduced through: shadow/login@1:4.8.1-1 and shadow/passwd@1:4.8.1-1
Detailed paths
-
Introduced through: nginx@1.21 › shadow/login@1:4.8.1-1
-
Introduced through: nginx@1.21 › shadow/passwd@1:4.8.1-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream shadow package and not the shadow package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
shadow-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:11 shadow.
References
- https://security-tracker.debian.org/tracker/CVE-2024-56433
- https://github.com/shadow-maint/shadow/blob/e2512d5741d4a44bdd81a8c2d0029b6222728cf0/etc/login.defs#L238-L241
- https://github.com/shadow-maint/shadow/issues/1157
- https://github.com/shadow-maint/shadow/releases/tag/4.4
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@247.3-7 and systemd/libudev1@247.3-7
Detailed paths
-
Introduced through: nginx@1.21 › systemd/libsystemd0@247.3-7
-
Introduced through: nginx@1.21 › systemd/libudev1@247.3-7
NVD Description
Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
Local unprivileged users can terminate arbitrary local processes via a systemd-oomd IPC API due to a missing path traversal validation.
Remediation
There is no fixed version for Debian:11 systemd.
References
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@247.3-7 and systemd/libudev1@247.3-7
Detailed paths
-
Introduced through: nginx@1.21 › systemd/libsystemd0@247.3-7
-
Introduced through: nginx@1.21 › systemd/libudev1@247.3-7
NVD Description
Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
systemd-homed contains a local privilege escalation bug via arbitrary system group addition to a local, logged in, homed-managed user
Remediation
There is no fixed version for Debian:11 systemd.
References
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@247.3-7 and systemd/libudev1@247.3-7
- Fixed in: 247.3-7+deb11u8
Detailed paths
-
Introduced through: nginx@1.21 › systemd/libsystemd0@247.3-7
-
Introduced through: nginx@1.21 › systemd/libudev1@247.3-7
NVD Description
Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
systemd, a system and service manager, (as PID 1) hits an assert and freezes execution when an unprivileged IPC API call is made with spurious data. On version v249 and older the effect is not an assert, but stack overwriting, with the attacker controlled content. From version v250 and newer this is not possible as the safety check causes an assert instead. This IPC call was added in v239, so versions older than that are not affected. Versions 260-rc1, 259.2, 258.5, and 257.11 contain patches. No known workarounds are available.
Remediation
Upgrade Debian:11 systemd to version 247.3-7+deb11u8 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-29111
- https://github.com/systemd/systemd/commit/1d22f706bd04f45f8422e17fbde3f56ece17758a
- https://github.com/systemd/systemd/commit/20021e7686426052e3a7505425d7e12085feb2a6
- https://github.com/systemd/systemd/commit/21167006574d6b83813c7596759b474f56562412
- https://github.com/systemd/systemd/commit/3cee294fe8cf4fa0eff933ab21416d099942cabd
- https://github.com/systemd/systemd/commit/42aee39107fbdd7db1ccd402a2151822b2805e9f
- https://github.com/systemd/systemd/commit/54588d2dedff54bfb6036670820650e4ea74628f
- https://github.com/systemd/systemd/commit/7ac3220213690e8a8d6d2a6e81e43bd1dce01d69
- https://github.com/systemd/systemd/commit/80acea4ef80a4bb78560ed970c34952299b890d6
- https://github.com/systemd/systemd/commit/b5fd14693057e5f2c9b4a49603be64ec3608ff6c
- https://github.com/systemd/systemd/commit/efa6ba2ab625aaa160ac435a09e6482fc63bdbe8
- https://github.com/systemd/systemd/security/advisories/GHSA-gx6q-6f99-m764
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@247.3-7 and systemd/libudev1@247.3-7
- Fixed in: 247.3-7+deb11u8
Detailed paths
-
Introduced through: nginx@1.21 › systemd/libsystemd0@247.3-7
-
Introduced through: nginx@1.21 › systemd/libudev1@247.3-7
NVD Description
Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
In udev in systemd before 260, local root execution can occur via malicious hardware devices and unsanitized kernel output.
Remediation
Upgrade Debian:11 systemd to version 247.3-7+deb11u8 or higher.
References
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@247.3-7 and systemd/libudev1@247.3-7
- Fixed in: 247.3-7+deb11u8
Detailed paths
-
Introduced through: nginx@1.21 › systemd/libsystemd0@247.3-7
-
Introduced through: nginx@1.21 › systemd/libudev1@247.3-7
NVD Description
Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
In nspawn in systemd 233 through 259 before 260, an escape-to-host action can occur via a crafted optional config file.
Remediation
Upgrade Debian:11 systemd to version 247.3-7+deb11u8 or higher.
References
low severity
- Vulnerable module: tar
- Introduced through: tar@1.34+dfsg-1
- Fixed in: 1.34+dfsg-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › tar@1.34+dfsg-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tar package and not the tar package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
In GNU tar before 1.35, mishandled extension attributes in a PAX archive can lead to an application crash in xheader.c.
Remediation
Upgrade Debian:11 tar to version 1.34+dfsg-1+deb11u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-39804
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058079
- https://git.savannah.gnu.org/cgit/tar.git/commit/?id=a339f05cd269013fa133d2f148d73f6f7d4247e4
- https://git.savannah.gnu.org/cgit/tar.git/tree/src/xheader.c?h=release_1_34#n1723
- https://lists.debian.org/debian-lts-announce/2024/03/msg00008.html
low severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
This vulnerability has not been analyzed by NVD yet.
Remediation
There is no fixed version for Debian:11 tiff.
References
low severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
An issue in libtiff 85f2ac8e0b01cb7db2bbecf4a3b891bdbef67938 allows an attacker to execute arbitrary code via the process_command_opts() function in tools/tiffcrop.c
Remediation
There is no fixed version for Debian:11 tiff.
References
low severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
An issue in libtiff 85f2ac8e0b01cb7db2bbecf4a3b891bdbef67938 allows an attacker to execute arbitrary code via the libtiff/tools/thumbnail.c: main() component
Remediation
There is no fixed version for Debian:11 tiff.
References
low severity
- Vulnerable module: tiff/libtiff5
- Introduced through: tiff/libtiff5@4.2.0-1+deb11u1
Detailed paths
-
Introduced through: nginx@1.21 › tiff/libtiff5@4.2.0-1+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
An integer overflow in the libtiff rgb2ycbcr utility's cvtRaster() function when computing strip buffer sizes can result in an undersized heap allocation and subsequent heap-based buffer overflow during YCbCr conversion of a crafted TIFF image
Remediation
There is no fixed version for Debian:11 tiff.
References
low severity
- Vulnerable module: util-linux
- Introduced through: util-linux@2.36.1-8+deb11u1, util-linux/libblkid1@2.36.1-8+deb11u1 and others
- Fixed in: 2.36.1-8+deb11u2
Detailed paths
-
Introduced through: nginx@1.21 › util-linux@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/libblkid1@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/libmount1@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/libsmartcols1@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/libuuid1@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/mount@2.36.1-8+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream util-linux package and not the util-linux package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
wall in util-linux through 2.40, often installed with setgid tty permissions, allows escape sequences to be sent to other users' terminals through argv. (Specifically, escape sequences received from stdin are blocked, but escape sequences received from argv are not blocked.) There may be plausible scenarios where this leads to account takeover.
Remediation
Upgrade Debian:11 util-linux to version 2.36.1-8+deb11u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-28085
- http://seclists.org/fulldisclosure/2024/Mar/35
- http://www.openwall.com/lists/oss-security/2024/03/27/5
- http://www.openwall.com/lists/oss-security/2024/03/27/6
- http://www.openwall.com/lists/oss-security/2024/03/27/7
- http://www.openwall.com/lists/oss-security/2024/03/27/8
- http://www.openwall.com/lists/oss-security/2024/03/27/9
- http://www.openwall.com/lists/oss-security/2024/03/28/1
- http://www.openwall.com/lists/oss-security/2024/03/28/2
- http://www.openwall.com/lists/oss-security/2024/03/28/3
- https://github.com/skyler-ferrante/CVE-2024-28085
- https://github.com/util-linux/util-linux/security/advisories/GHSA-xv2h-c6ww-mrjq
- https://lists.debian.org/debian-lts-announce/2024/04/msg00005.html
- https://mirrors.edge.kernel.org/pub/linux/utils/util-linux/
- https://people.rit.edu/sjf5462/6831711781/wall_2_27_2024.txt
- https://security.netapp.com/advisory/ntap-20240531-0003/
- https://www.openwall.com/lists/oss-security/2024/03/27/5
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-202008.html
low severity
- Vulnerable module: util-linux
- Introduced through: util-linux@2.36.1-8+deb11u1, util-linux/bsdutils@1:2.36.1-8+deb11u1 and others
Detailed paths
-
Introduced through: nginx@1.21 › util-linux@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/bsdutils@1:2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/libblkid1@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/libmount1@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/libsmartcols1@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/libuuid1@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/mount@2.36.1-8+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream util-linux package and not the util-linux package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
util-linux is a random collection of Linux utilities. Before util-linux 2.41.4, parse_dos_extended() in libblkid/src/partitions/dos.c computes an extended-partition start sector with 32-bit addition and does not apply the extended-area bounds checks to the first two EBR entries. A local attacker who causes a crafted DOS extended-partition disk image or removable medium to be probed can wrap cur_start + start to sector zero and cause libblkid to report a false partition overlapping the MBR. This directly compromises the integrity of the reported partition metadata; disk modification or availability loss requires a separate downstream consumer to act on that metadata. This issue is fixed in 2.41.4.
Remediation
There is no fixed version for Debian:11 util-linux.
References
- https://security-tracker.debian.org/tracker/CVE-2026-53615
- https://github.com/util-linux/util-linux/commit/05c2dbadf34cc74192287f377904afaaf4061623
- https://github.com/util-linux/util-linux/commit/a2d858176b609ab5b8535021a3af9cd302d23d31
- https://github.com/util-linux/util-linux/commit/e9d544d013267ea86b70ee8ff78abd280e6641af
- https://github.com/util-linux/util-linux/releases/tag/v2.41.4
- https://github.com/util-linux/util-linux/security/advisories/GHSA-h4rw-gv36-wmp5
low severity
- Vulnerable module: util-linux
- Introduced through: util-linux@2.36.1-8+deb11u1, util-linux/bsdutils@1:2.36.1-8+deb11u1 and others
Detailed paths
-
Introduced through: nginx@1.21 › util-linux@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/bsdutils@1:2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/libblkid1@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/libmount1@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/libsmartcols1@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/libuuid1@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/mount@2.36.1-8+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream util-linux package and not the util-linux package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
util-linux is a random collection of Linux utilities. Prior to version 2.41.4, a TOCTOU (Time-of-Check-Time-of-Use) vulnerability has been identified in the SUID binary /usr/bin/mount from util-linux. The mount binary, when setting up loop devices, validates the source file path with user privileges via fork() + setuid() + realpath(), but subsequently re-canonicalizes and opens it with root privileges (euid=0) without verifying that the path has not been replaced between both operations. Neither O_NOFOLLOW, nor inode comparison, nor post-open fstat() are employed. This allows a local unprivileged user to replace the source file with a symlink pointing to any root-owned file or device during the race window, causing the SUID binary to open and mount it as root. Exploitation requires an /etc/fstab entry with user,loop options whose path points to a directory where the attacker has write permission, and that /usr/bin/mount has the SUID bit set (the default configuration on virtually all Linux distributions). The impact is unauthorized read access to root-protected files and block devices, including backup images, disk volumes, and any file containing a valid filesystem. This issue has been patched in version 2.41.4.
Remediation
There is no fixed version for Debian:11 util-linux.
References
low severity
- Vulnerable module: util-linux
- Introduced through: util-linux@2.36.1-8+deb11u1, util-linux/bsdutils@1:2.36.1-8+deb11u1 and others
Detailed paths
-
Introduced through: nginx@1.21 › util-linux@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/bsdutils@1:2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/libblkid1@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/libmount1@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/libsmartcols1@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/libuuid1@2.36.1-8+deb11u1
-
Introduced through: nginx@1.21 › util-linux/mount@2.36.1-8+deb11u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream util-linux package and not the util-linux package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
util-linux is a random collection of Linux utilities. In util-linux 2.17 through 2.41.6 and 2.42 through 2.42.3, and in 2.42.4 when the legacy mount(2) path is used without /proc, restricted non-root mount requests validate an /etc/fstab target before the mount operation re-resolves that pathname. A local low-privileged user authorized by an fstab user or users entry whose target has an attacker-writable ancestor can use renameat2(RENAME_EXCHANGE) to swap a path component and redirect an authorized mount to a root-owned location, such as mounting attacker-controlled content over /etc/sudoers.d, and thereby gain root privileges. Versions 2.41.5 and 2.42.2 pin targets for the new mount API, and 2.42.4 pins legacy targets through /proc/self/fd; the documented legacy fallback without /proc remains affected.
Remediation
There is no fixed version for Debian:11 util-linux.
References
- https://security-tracker.debian.org/tracker/CVE-2026-53613
- https://github.com/util-linux/util-linux/commit/0b010025a0e429bc80355c94db86a843395d49e2
- https://github.com/util-linux/util-linux/commit/0d3d55975aa3492c62fd345eac38f41cd166c0b0
- https://github.com/util-linux/util-linux/commit/2c773f336134acf016e639abb6f12ba7341fe4b8
- https://github.com/util-linux/util-linux/commit/39fef62bf3226abb6bb018fa8750afa0327e84b4
- https://github.com/util-linux/util-linux/commit/472cc3fb2d4d47cca7aab2e0b59eb3fb8a9359ec
- https://github.com/util-linux/util-linux/commit/646fb66603d10a7ac337e14f566f1af48e3107c9
- https://github.com/util-linux/util-linux/commit/708d1b3c51932dc5ba8082c7368187715e6a8d78
- https://github.com/util-linux/util-linux/commit/78a860982e036f38fe9c0b3344998df5ac2c2ff5
- https://github.com/util-linux/util-linux/commit/85d16b341f7232c9dbb4884b632e1e956584bee9
- https://github.com/util-linux/util-linux/commit/a9508d216eb8977979102782672e0470cc9bf2a2
- https://github.com/util-linux/util-linux/releases/tag/v2.41.5
- https://github.com/util-linux/util-linux/releases/tag/v2.42.2
- https://github.com/util-linux/util-linux/releases/tag/v2.42.4
- https://github.com/util-linux/util-linux/security/advisories/GHSA-8gj5-72r3-428g