Vulnerabilities |
157 via 576 paths |
|---|---|
Dependencies |
251 |
Source |
Docker |
Target OS |
debian:13 |
high severity
- Vulnerable module: glib2.0/libglib2.0-0t64
- Introduced through: glib2.0/libglib2.0-0t64@2.84.4-3~deb13u1
- Fixed in: 2.84.4-3~deb13u2
Detailed paths
-
Introduced through: wordpress@latest › glib2.0/libglib2.0-0t64@2.84.4-3~deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A heap-based buffer overflow problem was found in glib through an incorrect calculation of buffer size in the g_escape_uri_string() function. If the string to escape contains a very large number of unacceptable characters (which would need escaping), the calculation of the length of the escaped string could overflow, leading to a potential write off the end of the newly allocated string.
Remediation
Upgrade Debian:13 glib2.0 to version 2.84.4-3~deb13u2 or higher.
References
high severity
new
- Vulnerable module: imagemagick/imagemagick-7-common
- Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u3, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3 and others
- Fixed in: 8:7.1.1.43+dfsg1-1+deb13u4
Detailed paths
-
Introduced through: wordpress@latest › imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u3
-
Introduced through: wordpress@latest › imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3
-
Introduced through: wordpress@latest › imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream imagemagick package and not the imagemagick package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
ImageMagick is free and open-source software used for editing and manipulating digital images. Prior to version 7.1.2-12, in the WriteSVGImage function, using an int variable to store number_attributes caused an integer overflow. This, in turn, triggered a buffer overflow and caused a DoS attack. Version 7.1.2-12 fixes the issue.
Remediation
Upgrade Debian:13 imagemagick to version 8:7.1.1.43+dfsg1-1+deb13u4 or higher.
References
high severity
new
- Vulnerable module: imagemagick/imagemagick-7-common
- Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u3, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3 and others
- Fixed in: 8:7.1.1.43+dfsg1-1+deb13u4
Detailed paths
-
Introduced through: wordpress@latest › imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u3
-
Introduced through: wordpress@latest › imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3
-
Introduced through: wordpress@latest › imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream imagemagick package and not the imagemagick package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
ImageMagick is free and open-source software used for editing and manipulating digital images. Prior to version 7.1.2-12, using Magick to read a malicious SVG file resulted in a DoS attack. Version 7.1.2-12 fixes the issue.
Remediation
Upgrade Debian:13 imagemagick to version 8:7.1.1.43+dfsg1-1+deb13u4 or higher.
References
medium severity
- Vulnerable module: glib2.0/libglib2.0-0t64
- Introduced through: glib2.0/libglib2.0-0t64@2.84.4-3~deb13u1
- Fixed in: 2.84.4-3~deb13u2
Detailed paths
-
Introduced through: wordpress@latest › glib2.0/libglib2.0-0t64@2.84.4-3~deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A flaw was found in glib. This vulnerability allows a heap buffer overflow and denial-of-service (DoS) via an integer overflow in GLib's GIO (GLib Input/Output) escape_byte_string() function when processing malicious file or remote filesystem attribute values.
Remediation
Upgrade Debian:13 glib2.0 to version 2.84.4-3~deb13u2 or higher.
References
medium severity
new
- Vulnerable module: imagemagick/imagemagick-7-common
- Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u3, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3 and others
- Fixed in: 8:7.1.1.43+dfsg1-1+deb13u4
Detailed paths
-
Introduced through: wordpress@latest › imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u3
-
Introduced through: wordpress@latest › imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3
-
Introduced through: wordpress@latest › imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream imagemagick package and not the imagemagick package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
ImageMagick is free and open-source software used for editing and manipulating digital images. Prior to version 7.1.2-12, Magick fails to check for circular references between two MVGs, leading to a stack overflow. This is a DoS vulnerability, and any situation that allows reading the mvg file will be affected. Version 7.1.2-12 fixes the issue.
Remediation
Upgrade Debian:13 imagemagick to version 8:7.1.1.43+dfsg1-1+deb13u4 or higher.
References
medium severity
- Vulnerable module: imagemagick/imagemagick-7-common
- Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u3, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3 and others
- Fixed in: 8:7.1.1.43+dfsg1-1+deb13u4
Detailed paths
-
Introduced through: wordpress@latest › imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u3
-
Introduced through: wordpress@latest › imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3
-
Introduced through: wordpress@latest › imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream imagemagick package and not the imagemagick package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
ImageMagick is free and open-source software used for editing and manipulating digital images. Prior to 7.1.2-9 and 6.9.13-34, there is a vulnerability in ImageMagick’s Magick++ layer that manifests when Options::fontFamily is invoked with an empty string. Clearing a font family calls RelinquishMagickMemory on _drawInfo->font, freeing the font string but leaving _drawInfo->font pointing to freed memory while _drawInfo->family is set to that (now-invalid) pointer. Any later cleanup or reuse of _drawInfo->font re-frees or dereferences dangling memory. DestroyDrawInfo and other setters (Options::font, Image::font) assume _drawInfo->font remains valid, so destruction or subsequent updates trigger crashes or heap corruption. This vulnerability is fixed in 7.1.2-9 and 6.9.13-34.
Remediation
Upgrade Debian:13 imagemagick to version 8:7.1.1.43+dfsg1-1+deb13u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-65955
- https://github.com/ImageMagick/ImageMagick/commit/6409f34d637a34a1c643632aa849371ec8b3b5a8
- https://github.com/ImageMagick/ImageMagick/commit/6f81eb15f822ad86e8255be75efad6f9762c32f8
- https://github.com/ImageMagick/ImageMagick/security/advisories/GHSA-q3hc-j9x5-mp9m
medium severity
- Vulnerable module: glib2.0/libglib2.0-0t64
- Introduced through: glib2.0/libglib2.0-0t64@2.84.4-3~deb13u1
- Fixed in: 2.84.4-3~deb13u2
Detailed paths
-
Introduced through: wordpress@latest › glib2.0/libglib2.0-0t64@2.84.4-3~deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A flaw was found in GLib (Gnome Lib). This vulnerability allows a remote attacker to cause heap corruption, leading to a denial of service or potential code execution via a buffer-underflow in the GVariant parser when processing maliciously crafted input strings.
Remediation
Upgrade Debian:13 glib2.0 to version 2.84.4-3~deb13u2 or higher.
References
medium severity
- Vulnerable module: imagemagick/imagemagick-7-common
- Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u3, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3 and others
- Fixed in: 8:7.1.1.43+dfsg1-1+deb13u4
Detailed paths
-
Introduced through: wordpress@latest › imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u3
-
Introduced through: wordpress@latest › imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3
-
Introduced through: wordpress@latest › imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream imagemagick package and not the imagemagick package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
ImageMagick is a software suite to create, edit, compose, or convert bitmap images. ImageMagick versions prior to 7.1.2-8 are vulnerable to denial-of-service due to unsigned integer underflow and division-by-zero in the CLAHEImage function. When tile width or height is zero, unsigned underflow occurs in pointer arithmetic, leading to out-of-bounds memory access, and division-by-zero causes immediate crashes. This issue has been patched in version 7.1.2-8.
Remediation
Upgrade Debian:13 imagemagick to version 8:7.1.1.43+dfsg1-1+deb13u4 or higher.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.41-12, glibc/libc-dev-bin@2.41-12 and others
Detailed paths
-
Introduced through: wordpress@latest › glibc/libc-bin@2.41-12
-
Introduced through: wordpress@latest › glibc/libc-dev-bin@2.41-12
-
Introduced through: wordpress@latest › glibc/libc6@2.41-12
-
Introduced through: wordpress@latest › glibc/libc6-dev@2.41-12
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:13 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:13 glibc.
References
low severity
- Vulnerable module: imagemagick/imagemagick-7-common
- Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u3, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3 and others
Detailed paths
-
Introduced through: wordpress@latest › imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u3
-
Introduced through: wordpress@latest › imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3
-
Introduced through: wordpress@latest › imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream imagemagick package and not the imagemagick package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A vulnerability was found in ImageMagick. This security flaw cause a remote code execution vulnerability in OpenBlob with --enable-pipes configured.
Remediation
There is no fixed version for Debian:13 imagemagick.
References
- https://security-tracker.debian.org/tracker/CVE-2023-34152
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/V2ZUHZXQ2C3JZYKPW4XHCMVVL467MA2V/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4UFQJCYJ23HWHNDOVKBHZQ7HCXXL6MM3/
- https://access.redhat.com/security/cve/CVE-2023-34152
- https://bugzilla.redhat.com/show_bug.cgi?id=2210659
- https://github.com/ImageMagick/ImageMagick/issues/6339
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4UFQJCYJ23HWHNDOVKBHZQ7HCXXL6MM3/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/V2ZUHZXQ2C3JZYKPW4XHCMVVL467MA2V/
low severity
- Vulnerable module: tar
- Introduced through: tar@1.35+dfsg-3.1
Detailed paths
-
Introduced through: wordpress@latest › tar@1.35+dfsg-3.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:13 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:13 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: cups/libcups2t64
- Introduced through: cups/libcups2t64@2.4.10-3+deb13u2
Detailed paths
-
Introduced through: wordpress@latest › cups/libcups2t64@2.4.10-3+deb13u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream cups package and not the cups package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
The browsing feature in the server in CUPS does not filter ANSI escape sequences from shared printer names, which might allow remote attackers to execute arbitrary code via a crafted printer name.
Remediation
There is no fixed version for Debian:13 cups.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.41-12, glibc/libc-dev-bin@2.41-12 and others
Detailed paths
-
Introduced through: wordpress@latest › glibc/libc-bin@2.41-12
-
Introduced through: wordpress@latest › glibc/libc-dev-bin@2.41-12
-
Introduced through: wordpress@latest › glibc/libc6@2.41-12
-
Introduced through: wordpress@latest › glibc/libc6-dev@2.41-12
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:13 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:13 glibc.
References
- https://security-tracker.debian.org/tracker/CVE-2019-1010023
- https://support.f5.com/csp/article/K11932200?utm_source=f5support&utm_medium=RSS
- https://sourceware.org/bugzilla/show_bug.cgi?id=22851
- http://www.securityfocus.com/bid/109167
- https://ubuntu.com/security/CVE-2019-1010023
- https://support.f5.com/csp/article/K11932200?utm_source=f5support&%3Butm_medium=RSS
low severity
- Vulnerable module: openjpeg2/libopenjp2-7
- Introduced through: openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u1
Detailed paths
-
Introduced through: wordpress@latest › openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openjpeg2 package and not the openjpeg2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
An integer overflow vulnerability was found in tiftoimage function in openjpeg 2.1.2, resulting in heap buffer overflow.
Remediation
There is no fixed version for Debian:13 openjpeg2.
References
- https://security-tracker.debian.org/tracker/CVE-2016-9580
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9580
- https://security.gentoo.org/glsa/201710-26
- https://github.com/szukw000/openjpeg/commit/cadff5fb6e73398de26a92e96d3d7cac893af255
- https://github.com/uclouvain/openjpeg/issues/871
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2016-9580
- http://www.securityfocus.com/bid/94822
low severity
- Vulnerable module: openjpeg2/libopenjp2-7
- Introduced through: openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u1
Detailed paths
-
Introduced through: wordpress@latest › openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openjpeg2 package and not the openjpeg2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
An infinite loop vulnerability in tiftoimage that results in heap buffer overflow in convert_32s_C1P1 was found in openjpeg 2.1.2.
Remediation
There is no fixed version for Debian:13 openjpeg2.
References
- https://security-tracker.debian.org/tracker/CVE-2016-9581
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9581
- https://security.gentoo.org/glsa/201710-26
- https://github.com/szukw000/openjpeg/commit/cadff5fb6e73398de26a92e96d3d7cac893af255
- https://github.com/uclouvain/openjpeg/issues/872
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2016-9581
- http://www.securityfocus.com/bid/94822
low severity
- Vulnerable module: openjpeg2/libopenjp2-7
- Introduced through: openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u1
Detailed paths
-
Introduced through: wordpress@latest › openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openjpeg2 package and not the openjpeg2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
An issue was discovered in OpenJPEG 2.3.0. A heap-based buffer overflow was discovered in the function t2_encode_packet in lib/openmj2/t2.c. The vulnerability causes an out-of-bounds write, which may lead to remote denial of service or possibly unspecified other impact.
Remediation
There is no fixed version for Debian:13 openjpeg2.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A vulnerability was found in GNU Binutils up to 2.44. It has been rated as critical. Affected by this issue is the function elf_gc_sweep of the file bfd/elflink.c of the component ld. The manipulation leads to memory corruption. An attack has to be approached locally. The exploit has been disclosed to the public and may be used. Upgrading to version 2.45 is able to address this issue. It is recommended to upgrade the affected component.
Remediation
There is no fixed version for Debian:13 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-5244
- https://sourceware.org/bugzilla/attachment.cgi?id=16010
- https://sourceware.org/bugzilla/show_bug.cgi?id=32858
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=d1458933830456e54223d9fc61f0d9b3a19256f5
- https://vuldb.com/?ctiid.310346
- https://vuldb.com/?id.310346
- https://vuldb.com/?submit.584634
- https://www.gnu.org/
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A vulnerability classified as critical has been found in GNU Binutils up to 2.44. This affects the function debug_type_samep of the file /binutils/debug.c of the component objdump. The manipulation leads to memory corruption. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue.
Remediation
There is no fixed version for Debian:13 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-5245
- https://sourceware.org/bugzilla/attachment.cgi?id=16004
- https://sourceware.org/bugzilla/show_bug.cgi?id=32829
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=6c3458a8b7ee7d39f070c7b2350851cb2110c65a
- https://vuldb.com/?ctiid.310347
- https://vuldb.com/?id.310347
- https://vuldb.com/?submit.584635
- https://www.gnu.org/
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A vulnerability, which was classified as problematic, has been found in GNU Binutils 2.45. Affected by this issue is the function bfd_elf_set_group_contents of the file bfd/elf.c. The manipulation leads to out-of-bounds write. It is possible to launch the attack on the local host. The exploit has been disclosed to the public and may be used. The name of the patch is 41461010eb7c79fee7a9d5f6209accdaac66cc6b. It is recommended to apply a patch to fix this issue.
Remediation
There is no fixed version for Debian:13 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-7546
- https://sourceware.org/bugzilla/attachment.cgi?id=16118
- https://sourceware.org/bugzilla/show_bug.cgi?id=33050#c2
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=41461010eb7c79fee7a9d5f6209accdaac66cc6b
- https://vuldb.com/?ctiid.316244
- https://vuldb.com/?id.316244
- https://vuldb.com/?submit.614375
- https://www.gnu.org/
- https://sourceware.org/bugzilla/show_bug.cgi?id=33050
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A vulnerability classified as problematic was found in GNU Binutils 2.45. Affected by this vulnerability is the function copy_section of the file binutils/objcopy.c. The manipulation leads to heap-based buffer overflow. Attacking locally is a requirement. The exploit has been disclosed to the public and may be used. The patch is named 08c3cbe5926e4d355b5cb70bbec2b1eeb40c2944. It is recommended to apply a patch to fix this issue.
Remediation
There is no fixed version for Debian:13 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-7545
- https://sourceware.org/bugzilla/attachment.cgi?id=16117
- https://sourceware.org/bugzilla/show_bug.cgi?id=33049
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=08c3cbe5926e4d355b5cb70bbec2b1eeb40c2944
- https://vuldb.com/?ctiid.316243
- https://vuldb.com/?id.316243
- https://vuldb.com/?submit.614355
- https://www.gnu.org/
- https://sourceware.org/bugzilla/show_bug.cgi?id=33049#c1
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A vulnerability has been found in GNU Binutils 2.45. The affected element is the function elf_swap_shdr in the library bfd/elfcode.h of the component Linker. The manipulation leads to heap-based buffer overflow. The attack must be carried out locally. The exploit has been disclosed to the public and may be used. The identifier of the patch is 9ca499644a21ceb3f946d1c179c38a83be084490. To fix this issue, it is recommended to deploy a patch. The code maintainer replied with "[f]ixed for 2.46".
Remediation
There is no fixed version for Debian:13 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-11083
- https://sourceware.org/bugzilla/attachment.cgi?id=16353
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=9ca499644a21ceb3f946d1c179c38a83be084490
- https://vuldb.com/?ctiid.326124
- https://vuldb.com/?id.326124
- https://vuldb.com/?submit.661277
- https://www.gnu.org/
- https://sourceware.org/bugzilla/show_bug.cgi?id=33457
- https://sourceware.org/bugzilla/show_bug.cgi?id=33457#c1
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A flaw has been found in GNU Binutils 2.45. Impacted is the function _bfd_elf_parse_eh_frame of the file bfd/elf-eh-frame.c of the component Linker. Executing manipulation can lead to heap-based buffer overflow. The attack is restricted to local execution. The exploit has been published and may be used. This patch is called ea1a0737c7692737a644af0486b71e4a392cbca8. A patch should be applied to remediate this issue. The code maintainer replied with "[f]ixed for 2.46".
Remediation
There is no fixed version for Debian:13 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-11082
- https://sourceware.org/bugzilla/attachment.cgi?id=16358
- https://sourceware.org/bugzilla/show_bug.cgi?id=33464
- https://sourceware.org/bugzilla/show_bug.cgi?id=33464#c2
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=ea1a0737c7692737a644af0486b71e4a392cbca8
- https://vuldb.com/?ctiid.326123
- https://vuldb.com/?id.326123
- https://vuldb.com/?submit.661276
- https://www.gnu.org/
low severity
- Vulnerable module: tiff/libtiff6
- Introduced through: tiff/libtiff6@4.7.0-3+deb13u1
Detailed paths
-
Introduced through: wordpress@latest › tiff/libtiff6@4.7.0-3+deb13u1
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:13 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:13 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/libtiff6
- Introduced through: tiff/libtiff6@4.7.0-3+deb13u1
Detailed paths
-
Introduced through: wordpress@latest › tiff/libtiff6@4.7.0-3+deb13u1
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:13 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:13 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: apache2
- Introduced through: apache2@2.4.65-2, apache2/apache2-bin@2.4.65-2 and others
Detailed paths
-
Introduced through: wordpress@latest › apache2@2.4.65-2
-
Introduced through: wordpress@latest › apache2/apache2-bin@2.4.65-2
-
Introduced through: wordpress@latest › apache2/apache2-data@2.4.65-2
-
Introduced through: wordpress@latest › apache2/apache2-utils@2.4.65-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream apache2 package and not the apache2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
The Apache HTTP Server, when accessed through a TCP connection with a large window size, allows remote attackers to cause a denial of service (network bandwidth consumption) via a Range header that specifies multiple copies of the same fragment. NOTE: the severity of this issue has been disputed by third parties, who state that the large window size required by the attack is not normally supported or configured by the server, or that a DDoS-style attack would accomplish the same goal
Remediation
There is no fixed version for Debian:13 apache2.
References
- https://security-tracker.debian.org/tracker/CVE-2007-0086
- http://www.securityfocus.com/archive/1/455833/100/0/threaded
- http://www.securityfocus.com/archive/1/455879/100/0/threaded
- http://www.securityfocus.com/archive/1/455882/100/0/threaded
- http://www.securityfocus.com/archive/1/455920/100/0/threaded
- http://osvdb.org/33456
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.41-12, glibc/libc-dev-bin@2.41-12 and others
Detailed paths
-
Introduced through: wordpress@latest › glibc/libc-bin@2.41-12
-
Introduced through: wordpress@latest › glibc/libc-dev-bin@2.41-12
-
Introduced through: wordpress@latest › glibc/libc6@2.41-12
-
Introduced through: wordpress@latest › glibc/libc6-dev@2.41-12
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:13 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:13 glibc.
References
- https://security-tracker.debian.org/tracker/CVE-2018-20796
- https://support.f5.com/csp/article/K26346590?utm_source=f5support&utm_medium=RSS
- https://debbugs.gnu.org/cgi/bugreport.cgi?bug=34141
- https://lists.gnu.org/archive/html/bug-gnulib/2019-01/msg00108.html
- https://security.netapp.com/advisory/ntap-20190315-0002/
- http://www.securityfocus.com/bid/107160
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2018-20796
- https://support.f5.com/csp/article/K26346590?utm_source=f5support&%3Butm_medium=RSS
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.41-12, glibc/libc-dev-bin@2.41-12 and others
Detailed paths
-
Introduced through: wordpress@latest › glibc/libc-bin@2.41-12
-
Introduced through: wordpress@latest › glibc/libc-dev-bin@2.41-12
-
Introduced through: wordpress@latest › glibc/libc6@2.41-12
-
Introduced through: wordpress@latest › glibc/libc6-dev@2.41-12
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:13 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:13 glibc.
References
- https://security-tracker.debian.org/tracker/CVE-2019-9192
- https://support.f5.com/csp/article/K26346590?utm_source=f5support&utm_medium=RSS
- https://sourceware.org/bugzilla/show_bug.cgi?id=24269
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2019-9192
- https://support.f5.com/csp/article/K26346590?utm_source=f5support&%3Butm_medium=RSS
low severity
- Vulnerable module: jansson/libjansson4
- Introduced through: jansson/libjansson4@2.14-2+b3
Detailed paths
-
Introduced through: wordpress@latest › jansson/libjansson4@2.14-2+b3
NVD Description
Note: Versions mentioned in the description apply only to the upstream jansson package and not the jansson package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
An issue was discovered in Jansson through 2.13.1. Due to a parsing error in json_loads, there's an out-of-bounds read-access bug. NOTE: the vendor reports that this only occurs when a programmer fails to follow the API specification
Remediation
There is no fixed version for Debian:13 jansson.
References
low severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.21.3-5, krb5/libk5crypto3@1.21.3-5 and others
Detailed paths
-
Introduced through: wordpress@latest › krb5/libgssapi-krb5-2@1.21.3-5
-
Introduced through: wordpress@latest › krb5/libk5crypto3@1.21.3-5
-
Introduced through: wordpress@latest › krb5/libkrb5-3@1.21.3-5
-
Introduced through: wordpress@latest › krb5/libkrb5support0@1.21.3-5
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:13 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:13 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: openjpeg2/libopenjp2-7
- Introduced through: openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u1
Detailed paths
-
Introduced through: wordpress@latest › openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openjpeg2 package and not the openjpeg2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
There is a NULL Pointer Access in function imagetopnm of convert.c:1943(jp2) of OpenJPEG 2.1.2. image->comps[compno].data is not assigned a value after initialization(NULL). Impact is Denial of Service.
Remediation
There is no fixed version for Debian:13 openjpeg2.
References
low severity
- Vulnerable module: openjpeg2/libopenjp2-7
- Introduced through: openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u1
Detailed paths
-
Introduced through: wordpress@latest › openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openjpeg2 package and not the openjpeg2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
There is a NULL pointer dereference in function imagetobmp of convertbmp.c:980 of OpenJPEG 2.1.2. image->comps[0].data is not assigned a value after initialization(NULL). Impact is Denial of Service.
Remediation
There is no fixed version for Debian:13 openjpeg2.
References
low severity
- Vulnerable module: openldap/libldap2
- Introduced through: openldap/libldap2@2.6.10+dfsg-1
Detailed paths
-
Introduced through: wordpress@latest › openldap/libldap2@2.6.10+dfsg-1
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:13 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:13 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/libldap2
- Introduced through: openldap/libldap2@2.6.10+dfsg-1
Detailed paths
-
Introduced through: wordpress@latest › openldap/libldap2@2.6.10+dfsg-1
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:13 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:13 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: patch
- Introduced through: patch@2.8-2
Detailed paths
-
Introduced through: wordpress@latest › patch@2.8-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream patch package and not the patch package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A double free exists in the another_hunk function in pch.c in GNU patch through 2.7.6.
Remediation
There is no fixed version for Debian:13 patch.
References
- https://security-tracker.debian.org/tracker/CVE-2018-6952
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6952
- https://security.gentoo.org/glsa/201904-17
- https://savannah.gnu.org/bugs/index.php?53133
- https://access.redhat.com/errata/RHSA-2019:2033
- http://www.securityfocus.com/bid/103047
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2018-6952
low severity
- Vulnerable module: patch
- Introduced through: patch@2.8-2
Detailed paths
-
Introduced through: wordpress@latest › patch@2.8-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream patch package and not the patch package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
An issue was discovered in GNU patch through 2.7.6. There is a segmentation fault, associated with a NULL pointer dereference, leading to a denial of service in the intuit_diff_type function in pch.c, aka a "mangled rename" issue.
Remediation
There is no fixed version for Debian:13 patch.
References
- https://security-tracker.debian.org/tracker/CVE-2018-6951
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6951
- https://security.gentoo.org/glsa/201904-17
- https://git.savannah.gnu.org/cgit/patch.git/commit/?id=f290f48a621867084884bfff87f8093c15195e6a
- https://savannah.gnu.org/bugs/index.php?53132
- http://www.securityfocus.com/bid/103044
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2018-6951
- https://usn.ubuntu.com/3624-1/
low severity
- Vulnerable module: tiff/libtiff6
- Introduced through: tiff/libtiff6@4.7.0-3+deb13u1
Detailed paths
-
Introduced through: wordpress@latest › tiff/libtiff6@4.7.0-3+deb13u1
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:13 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:13 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: m4
- Introduced through: m4@1.4.19-8
Detailed paths
-
Introduced through: wordpress@latest › m4@1.4.19-8
NVD Description
Note: Versions mentioned in the description apply only to the upstream m4 package and not the m4 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
The (1) maketemp and (2) mkstemp builtin functions in GNU m4 before 1.4.11 do not quote their output when a file is created, which might allow context-dependent attackers to trigger a macro expansion, leading to unspecified use of an incorrect filename.
Remediation
There is no fixed version for Debian:13 m4.
References
- https://security-tracker.debian.org/tracker/CVE-2008-1687
- http://slackware.com/security/viewer.php?l=slackware-security&y=2008&m=slackware-security.510612
- http://www.vupen.com/english/advisories/2008/1151/references
- http://xforce.iss.net/xforce/xfdb/41706
- http://www.openwall.com/lists/oss-security/2008/04/07/1
- http://www.openwall.com/lists/oss-security/2008/04/07/12
- http://www.openwall.com/lists/oss-security/2008/04/07/3
- http://www.openwall.com/lists/oss-security/2008/04/07/4
- http://secunia.com/advisories/29671
- http://secunia.com/advisories/29729
- http://www.securityfocus.com/bid/28688
- https://exchange.xforce.ibmcloud.com/vulnerabilities/41706
low severity
- Vulnerable module: m4
- Introduced through: m4@1.4.19-8
Detailed paths
-
Introduced through: wordpress@latest › m4@1.4.19-8
NVD Description
Note: Versions mentioned in the description apply only to the upstream m4 package and not the m4 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
Unspecified vulnerability in GNU m4 before 1.4.11 might allow context-dependent attackers to execute arbitrary code, related to improper handling of filenames specified with the -F option. NOTE: it is not clear when this issue crosses privilege boundaries.
Remediation
There is no fixed version for Debian:13 m4.
References
- https://security-tracker.debian.org/tracker/CVE-2008-1688
- http://osvdb.org/44272
- http://slackware.com/security/viewer.php?l=slackware-security&y=2008&m=slackware-security.510612
- http://www.vupen.com/english/advisories/2008/1151/references
- http://xforce.iss.net/xforce/xfdb/41704
- http://www.openwall.com/lists/oss-security/2008/04/07/1
- http://www.openwall.com/lists/oss-security/2008/04/07/3
- http://secunia.com/advisories/29671
- http://secunia.com/advisories/29729
- http://www.securityfocus.com/bid/28688
- https://exchange.xforce.ibmcloud.com/vulnerabilities/41704
low severity
- Vulnerable module: cups/libcups2t64
- Introduced through: cups/libcups2t64@2.4.10-3+deb13u2
Detailed paths
-
Introduced through: wordpress@latest › cups/libcups2t64@2.4.10-3+deb13u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream cups package and not the cups package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
OpenPrinting CUPS is an open source printing system for Linux and other Unix-like operating systems. Prior to version 2.4.15, a user in the lpadmin group can use the cups web ui to change the config and insert a malicious line. Then the cupsd process which runs as root will parse the new config and cause an out-of-bound write. This issue has been patched in version 2.4.15.
Remediation
There is no fixed version for Debian:13 cups.
References
- https://security-tracker.debian.org/tracker/CVE-2025-61915
- https://github.com/OpenPrinting/cups/commit/db8d560262c22a21ee1e55dfd62fa98d9359bcb0
- https://github.com/OpenPrinting/cups/releases/tag/v2.4.15
- http://www.openwall.com/lists/oss-security/2025/11/27/5
- https://github.com/OpenPrinting/cups/security/advisories/GHSA-hxm8-vfpq-jrfc
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A heap-based buffer over-read exists in the function d_expression_1 in cp-demangle.c in GNU libiberty, as distributed in GNU Binutils 2.31.1. A crafted input can cause segmentation faults, leading to denial-of-service, as demonstrated by c++filt.
Remediation
There is no fixed version for Debian:13 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2018-20712
- https://support.f5.com/csp/article/K38336243
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20712
- https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88629
- https://sourceware.org/bugzilla/show_bug.cgi?id=24043
- http://www.securityfocus.com/bid/106563
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2018-20712
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
An issue was discovered in GNU libiberty, as distributed in GNU Binutils 2.36. It is a stack-overflow issue in demangle_type in rust-demangle.c.
Remediation
There is no fixed version for Debian:13 binutils.
References
low severity
- Vulnerable module: imagemagick/imagemagick-7-common
- Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u3, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3 and others
Detailed paths
-
Introduced through: wordpress@latest › imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u3
-
Introduced through: wordpress@latest › imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3
-
Introduced through: wordpress@latest › imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream imagemagick package and not the imagemagick package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
The WritePICONImage function in coders/xpm.c in ImageMagick 7.0.6-4 allows remote attackers to cause a denial of service (memory leak) via a crafted file that is mishandled in an OpenPixelCache call.
Remediation
There is no fixed version for Debian:13 imagemagick.
References
low severity
- Vulnerable module: imagemagick/imagemagick-7-common
- Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u3, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3 and others
Detailed paths
-
Introduced through: wordpress@latest › imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u3
-
Introduced through: wordpress@latest › imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3
-
Introduced through: wordpress@latest › imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream imagemagick package and not the imagemagick package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
The WritePICONImage function in coders/xpm.c in ImageMagick 7.0.6-4 allows remote attackers to cause a denial of service (memory leak) via a crafted file that is mishandled in an AcquireSemaphoreInfo call.
Remediation
There is no fixed version for Debian:13 imagemagick.
References
low severity
- Vulnerable module: imagemagick/imagemagick-7-common
- Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u3, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3 and others
Detailed paths
-
Introduced through: wordpress@latest › imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u3
-
Introduced through: wordpress@latest › imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3
-
Introduced through: wordpress@latest › imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream imagemagick package and not the imagemagick package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
In ImageMagick 7.0.8-11 Q16, a tiny input file 0x50 0x36 0x36 0x36 0x36 0x4c 0x36 0x38 0x36 0x36 0x36 0x36 0x36 0x36 0x1f 0x35 0x50 0x00 can result in a hang of several minutes during which CPU and memory resources are consumed until ultimately an attempted large memory allocation fails. Remote attackers could leverage this vulnerability to cause a denial of service via a crafted file.
Remediation
There is no fixed version for Debian:13 imagemagick.
References
- https://security-tracker.debian.org/tracker/CVE-2018-15607
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-15607
- https://github.com/ImageMagick/ImageMagick/issues/1255
- http://www.securityfocus.com/bid/105137
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2018-15607
- https://usn.ubuntu.com/4034-1/
low severity
- Vulnerable module: jbig2dec/libjbig2dec0
- Introduced through: jbig2dec/libjbig2dec0@0.20-1+b3
Detailed paths
-
Introduced through: wordpress@latest › jbig2dec/libjbig2dec0@0.20-1+b3
NVD Description
Note: Versions mentioned in the description apply only to the upstream jbig2dec package and not the jbig2dec package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
Artifex Software jbig2dec v0.20 was discovered to contain a SEGV vulnerability via jbig2_error at /jbig2dec/jbig2.c.
Remediation
There is no fixed version for Debian:13 jbig2dec.
References
low severity
- Vulnerable module: jbigkit/libjbig0
- Introduced through: jbigkit/libjbig0@2.1-6.1+b2
Detailed paths
-
Introduced through: wordpress@latest › jbigkit/libjbig0@2.1-6.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:13 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:13 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: openjpeg2/libopenjp2-7
- Introduced through: openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u1
Detailed paths
-
Introduced through: wordpress@latest › openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openjpeg2 package and not the openjpeg2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
An issue was discovered in OpenJPEG 2.3.0. It allows remote attackers to cause a denial of service (attempted excessive memory allocation) in opj_calloc in openjp2/opj_malloc.c, when called from opj_tcd_init_tile in openjp2/tcd.c, as demonstrated by the 64-bit opj_decompress.
Remediation
There is no fixed version for Debian:13 openjpeg2.
References
low severity
- Vulnerable module: openjpeg2/libopenjp2-7
- Introduced through: openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u1
Detailed paths
-
Introduced through: wordpress@latest › openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openjpeg2 package and not the openjpeg2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
NULL pointer dereference vulnerabilities in the imagetopnm function in convert.c, sycc444_to_rgb function in color.c, color_esycc_to_rgb function in color.c, and sycc422_to_rgb function in color.c in OpenJPEG before 2.2.0 allow remote attackers to cause a denial of service (application crash) via crafted j2k files.
Remediation
There is no fixed version for Debian:13 openjpeg2.
References
low severity
- Vulnerable module: openjpeg2/libopenjp2-7
- Introduced through: openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u1
Detailed paths
-
Introduced through: wordpress@latest › openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openjpeg2 package and not the openjpeg2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
NULL Pointer Access in function imagetopnm of convert.c:2226(jp2) in OpenJPEG 2.1.2. Impact is Denial of Service. Someone must open a crafted j2k file.
Remediation
There is no fixed version for Debian:13 openjpeg2.
References
low severity
- Vulnerable module: openjpeg2/libopenjp2-7
- Introduced through: openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u1
Detailed paths
-
Introduced through: wordpress@latest › openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openjpeg2 package and not the openjpeg2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
NULL Pointer Access in function imagetopnm of convert.c(jp2):1289 in OpenJPEG 2.1.2. Impact is Denial of Service. Someone must open a crafted j2k file.
Remediation
There is no fixed version for Debian:13 openjpeg2.
References
low severity
- Vulnerable module: openjpeg2/libopenjp2-7
- Introduced through: openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u1
Detailed paths
-
Introduced through: wordpress@latest › openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openjpeg2 package and not the openjpeg2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
Heap Buffer Over-read in function imagetotga of convert.c(jp2):942 in OpenJPEG 2.1.2. Impact is Denial of Service. Someone must open a crafted j2k file.
Remediation
There is no fixed version for Debian:13 openjpeg2.
References
low severity
- Vulnerable module: tiff/libtiff6
- Introduced through: tiff/libtiff6@4.7.0-3+deb13u1
Detailed paths
-
Introduced through: wordpress@latest › tiff/libtiff6@4.7.0-3+deb13u1
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:13 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:13 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/libtiff6
- Introduced through: tiff/libtiff6@4.7.0-3+deb13u1
Detailed paths
-
Introduced through: wordpress@latest › tiff/libtiff6@4.7.0-3+deb13u1
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:13 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:13 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: apache2
- Introduced through: apache2@2.4.65-2, apache2/apache2-bin@2.4.65-2 and others
Detailed paths
-
Introduced through: wordpress@latest › apache2@2.4.65-2
-
Introduced through: wordpress@latest › apache2/apache2-bin@2.4.65-2
-
Introduced through: wordpress@latest › apache2/apache2-data@2.4.65-2
-
Introduced through: wordpress@latest › apache2/apache2-utils@2.4.65-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream apache2 package and not the apache2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
Apache httpd 2.0.59 and 2.2.4, with the Prefork MPM module, allows local users to cause a denial of service via certain code sequences executed in a worker process that (1) stop request processing by killing all worker processes and preventing creation of replacements or (2) hang the system by forcing the master process to fork an arbitrarily large number of worker processes. NOTE: This might be an inherent design limitation of Apache with respect to worker processes in hosted environments.
Remediation
There is no fixed version for Debian:13 apache2.
References
- https://security-tracker.debian.org/tracker/CVE-2007-3303
- http://www.securityfocus.com/archive/1/469899/100/0/threaded
- http://www.securityfocus.com/archive/1/471832/100/0/threaded
- http://security.psnc.pl/files/apache_report.pdf
- http://osvdb.org/37050
- http://www.securityfocus.com/bid/24215
- http://securityreason.com/securityalert/2814
low severity
- Vulnerable module: shadow/login.defs
- Introduced through: shadow/login.defs@1:4.17.4-2 and shadow/passwd@1:4.17.4-2
Detailed paths
-
Introduced through: wordpress@latest › shadow/login.defs@1:4.17.4-2
-
Introduced through: wordpress@latest › shadow/passwd@1:4.17.4-2
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:13 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:13 shadow.
References
- https://security-tracker.debian.org/tracker/CVE-2007-5686
- http://www.securityfocus.com/archive/1/482129/100/100/threaded
- http://www.securityfocus.com/archive/1/482857/100/0/threaded
- https://issues.rpath.com/browse/RPL-1825
- http://secunia.com/advisories/27215
- http://www.securityfocus.com/bid/26048
- http://www.vupen.com/english/advisories/2007/3474
low severity
- Vulnerable module: util-linux
- Introduced through: util-linux@2.41-5, util-linux/bsdutils@1:2.41-5 and others
Detailed paths
-
Introduced through: wordpress@latest › util-linux@2.41-5
-
Introduced through: wordpress@latest › util-linux/bsdutils@1:2.41-5
-
Introduced through: wordpress@latest › util-linux/libblkid1@2.41-5
-
Introduced through: wordpress@latest › util-linux/liblastlog2-2@2.41-5
-
Introduced through: wordpress@latest › util-linux/libmount1@2.41-5
-
Introduced through: wordpress@latest › util-linux/libsmartcols1@2.41-5
-
Introduced through: wordpress@latest › util-linux/libuuid1@2.41-5
-
Introduced through: wordpress@latest › util-linux/login@1:4.16.0-2+really2.41-5
-
Introduced through: wordpress@latest › util-linux/mount@2.41-5
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:13 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:13 util-linux.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A vulnerability classified as problematic was found in GNU Binutils 2.43/2.44. Affected by this vulnerability is the function bfd_set_format of the file format.c. The manipulation leads to memory corruption. The attack can be launched remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. Upgrading to version 2.45 is able to address this issue. The identifier of the patch is 8d97c1a53f3dc9fd8e1ccdb039b8a33d50133150. It is recommended to upgrade the affected component.
Remediation
There is no fixed version for Debian:13 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-1153
- https://sourceware.org/bugzilla/show_bug.cgi?id=32603
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=8d97c1a53f3dc9fd8e1ccdb039b8a33d50133150
- https://vuldb.com/?ctiid.295057
- https://vuldb.com/?id.295057
- https://vuldb.com/?submit.489991
- https://www.gnu.org/
- https://security.netapp.com/advisory/ntap-20250404-0005/
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A vulnerability was found in GNU Binutils 2.43. It has been declared as problematic. Affected by this vulnerability is the function bfd_putl64 of the file libbfd.c of the component ld. The manipulation leads to memory corruption. The attack can be launched remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The identifier of the patch is 75086e9de1707281172cc77f178e7949a4414ed0. It is recommended to apply a patch to fix this issue.
Remediation
There is no fixed version for Debian:13 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-1178
- https://sourceware.org/bugzilla/attachment.cgi?id=15914
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=75086e9de1707281172cc77f178e7949a4414ed0
- https://vuldb.com/?ctiid.295081
- https://vuldb.com/?id.295081
- https://vuldb.com/?submit.495369
- https://www.gnu.org/
- https://security.netapp.com/advisory/ntap-20250411-0008/
- https://sourceware.org/bugzilla/show_bug.cgi?id=32638
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
The C++ symbol demangler routine in cplus-dem.c in libiberty, as distributed in GNU Binutils 2.29, allows remote attackers to cause a denial of service (excessive memory allocation and application crash) via a crafted file, as demonstrated by a call from the Binary File Descriptor (BFD) library (aka libbfd).
Remediation
There is no fixed version for Debian:13 binutils.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A vulnerability has been found in GNU Binutils 2.43/2.44 and classified as problematic. Affected by this vulnerability is the function display_info of the file binutils/bucomm.c of the component objdump. The manipulation leads to memory leak. An attack has to be approached locally. The exploit has been disclosed to the public and may be used. The patch is named ba6ad3a18cb26b79e0e3b84c39f707535bbc344d. It is recommended to apply a patch to fix this issue.
Remediation
There is no fixed version for Debian:13 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-3198
- https://sourceware.org/bugzilla/show_bug.cgi?id=32716#c0
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=ba6ad3a18cb26b79e0e3b84c39f707535bbc344d
- https://vuldb.com/?ctiid.303151
- https://vuldb.com/?id.303151
- https://vuldb.com/?submit.545773
- https://www.gnu.org/
- https://sourceware.org/bugzilla/show_bug.cgi?id=32716
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A vulnerability was detected in GNU Binutils 2.45. This issue affects the function dump_dwarf_section of the file binutils/objdump.c. Performing manipulation results in out-of-bounds read. The attack is only possible with local access. The exploit is now public and may be used. The patch is named f87a66db645caf8cc0e6fc87b0c28c78a38af59b. It is suggested to install a patch to address this issue.
Remediation
There is no fixed version for Debian:13 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-11081
- https://github.com/user-attachments/files/20623354/hdf5_crash_3.txt
- https://sourceware.org/bugzilla/show_bug.cgi?id=33406
- https://sourceware.org/bugzilla/show_bug.cgi?id=33406#c2
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=f87a66db645caf8cc0e6fc87b0c28c78a38af59b
- https://vuldb.com/?ctiid.326122
- https://vuldb.com/?id.326122
- https://vuldb.com/?submit.661275
- https://www.gnu.org/
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A vulnerability was determined in GNU Binutils 2.45. The affected element is the function elf_x86_64_relocate_section of the file elf64-x86-64.c of the component Linker. This manipulation causes heap-based buffer overflow. The attack can only be executed locally. The exploit has been publicly disclosed and may be utilized. Patch name: 6b21c8b2ecfef5c95142cbc2c32f185cb1c26ab0. To fix this issue, it is recommended to deploy a patch.
Remediation
There is no fixed version for Debian:13 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-11495
- https://sourceware.org/bugzilla/attachment.cgi?id=16393
- https://sourceware.org/bugzilla/show_bug.cgi?id=33502
- https://sourceware.org/bugzilla/show_bug.cgi?id=33502#c3
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=6b21c8b2ecfef5c95142cbc2c32f185cb1c26ab0
- https://vuldb.com/?ctiid.327620
- https://vuldb.com/?id.327620
- https://vuldb.com/?submit.668290
- https://www.gnu.org/
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A vulnerability was found in GNU Binutils 2.45. Impacted is the function _bfd_x86_elf_late_size_sections of the file bfd/elfxx-x86.c of the component Linker. The manipulation results in out-of-bounds read. The attack needs to be approached locally. The exploit has been made public and could be used. The patch is identified as b6ac5a8a5b82f0ae6a4642c8d7149b325f4cc60a. A patch should be applied to remediate this issue.
Remediation
There is no fixed version for Debian:13 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-11494
- https://sourceware.org/bugzilla/attachment.cgi?id=16389
- https://sourceware.org/bugzilla/show_bug.cgi?id=33499
- https://sourceware.org/bugzilla/show_bug.cgi?id=33499#c2
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b6ac5a8a5b82f0ae6a4642c8d7149b325f4cc60a
- https://vuldb.com/?ctiid.327619
- https://vuldb.com/?id.327619
- https://vuldb.com/?submit.668281
- https://www.gnu.org/
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A weakness has been identified in GNU Binutils 2.45. The affected element is the function vfinfo of the file ldmisc.c. Executing manipulation can lead to out-of-bounds read. The attack can only be executed locally. The exploit has been made available to the public and could be exploited. This patch is called 16357. It is best practice to apply a patch to resolve this issue.
Remediation
There is no fixed version for Debian:13 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-11840
- https://sourceware.org/bugzilla/attachment.cgi?id=16351
- https://sourceware.org/bugzilla/attachment.cgi?id=16357
- https://sourceware.org/bugzilla/show_bug.cgi?id=33455
- https://vuldb.com/?ctiid.328775
- https://vuldb.com/?id.328775
- https://vuldb.com/?submit.661281
- https://www.gnu.org/
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A vulnerability was determined in GNU Binutils 2.45. Affected by this vulnerability is the function get_link_hash_entry of the file bfd/elflink.c of the component Linker. This manipulation causes out-of-bounds read. The attack can only be executed locally. The exploit has been publicly disclosed and may be utilized. Upgrading to version 2.46 addresses this issue. Patch name: aeaaa9af6359c8e394ce9cf24911fec4f4d23703. It is advisable to upgrade the affected component.
Remediation
There is no fixed version for Debian:13 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-11414
- https://sourceware.org/bugzilla/attachment.cgi?id=16361
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=aeaaa9af6359c8e394ce9cf24911fec4f4d23703
- https://vuldb.com/?ctiid.327350
- https://vuldb.com/?id.327350
- https://vuldb.com/?submit.665591
- https://www.gnu.org/
- https://sourceware.org/bugzilla/show_bug.cgi?id=33450
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A vulnerability was found in GNU Binutils 2.45. Affected is the function elf_link_add_object_symbols of the file bfd/elflink.c of the component Linker. The manipulation results in out-of-bounds read. The attack needs to be approached locally. The exploit has been made public and could be used. Upgrading to version 2.46 is able to address this issue. The patch is identified as 72efdf166aa0ed72ecc69fc2349af6591a7a19c0. Upgrading the affected component is advised.
Remediation
There is no fixed version for Debian:13 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-11413
- https://sourceware.org/bugzilla/attachment.cgi?id=16362
- https://sourceware.org/bugzilla/show_bug.cgi?id=33456#c10
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=72efdf166aa0ed72ecc69fc2349af6591a7a19c0
- https://vuldb.com/?ctiid.327349
- https://vuldb.com/?id.327349
- https://vuldb.com/?submit.665587
- https://www.gnu.org/
- https://sourceware.org/bugzilla/show_bug.cgi?id=33452
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A vulnerability has been found in GNU Binutils 2.45. This impacts the function bfd_elf_gc_record_vtentry of the file bfd/elflink.c of the component Linker. The manipulation leads to out-of-bounds read. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used. The identifier of the patch is 047435dd988a3975d40c6626a8f739a0b2e154bc. To fix this issue, it is recommended to deploy a patch.
Remediation
There is no fixed version for Debian:13 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-11412
- https://sourceware.org/bugzilla/attachment.cgi?id=16378
- https://sourceware.org/bugzilla/show_bug.cgi?id=33452#c8
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=047435dd988a3975d40c6626a8f739a0b2e154bc
- https://vuldb.com/?ctiid.327348
- https://vuldb.com/?id.327348
- https://www.gnu.org/
- https://sourceware.org/bugzilla/show_bug.cgi?id=33452
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
The demangle_template function in cplus-dem.c in GNU libiberty, as distributed in GNU Binutils 2.31.1, contains an integer overflow vulnerability (for "Create an array for saving the template argument values") that can trigger a heap-based buffer overflow, as demonstrated by nm.
Remediation
There is no fixed version for Debian:13 binutils.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A security flaw has been discovered in GNU Binutils 2.45. Impacted is the function tg_tag_type of the file prdbg.c. Performing manipulation results in unchecked return value. The attack needs to be approached locally. The exploit has been released to the public and may be exploited.
Remediation
There is no fixed version for Debian:13 binutils.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
An issue was discovered in cplus-dem.c in GNU libiberty, as distributed in GNU Binutils 2.30. Stack Exhaustion occurs in the C++ demangling functions provided by libiberty, and there are recursive stack frames: demangle_template_value_parm, demangle_integral_value, and demangle_expression.
Remediation
There is no fixed version for Debian:13 binutils.
References
low severity
- Vulnerable module: cups/libcups2t64
- Introduced through: cups/libcups2t64@2.4.10-3+deb13u2
Detailed paths
-
Introduced through: wordpress@latest › cups/libcups2t64@2.4.10-3+deb13u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream cups package and not the cups package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
OpenPrinting CUPS is an open source printing system for Linux and other Unix-like operating systems. Prior to version 2.4.15, a client that connects to cupsd but sends slow messages, e.g. only one byte per second, delays cupsd as a whole, such that it becomes unusable by other clients. This issue has been patched in version 2.4.15.
Remediation
There is no fixed version for Debian:13 cups.
References
- https://security-tracker.debian.org/tracker/CVE-2025-58436
- https://github.com/OpenPrinting/cups/commit/40008d76a001babbb9beb9d9d74b01a86fb6ddb4
- https://github.com/OpenPrinting/cups/releases/tag/v2.4.15
- http://www.openwall.com/lists/oss-security/2025/11/27/4
- https://github.com/OpenPrinting/cups/security/advisories/GHSA-8wpw-vfgm-qrrr
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.7.1-2
Detailed paths
-
Introduced through: wordpress@latest › expat/libexpat1@2.7.1-2
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:13 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:13 expat.
References
low severity
- Vulnerable module: ghostscript
- Introduced through: ghostscript@10.05.1~dfsg-1+deb13u1, ghostscript/libgs-common@10.05.1~dfsg-1+deb13u1 and others
Detailed paths
-
Introduced through: wordpress@latest › ghostscript@10.05.1~dfsg-1+deb13u1
-
Introduced through: wordpress@latest › ghostscript/libgs-common@10.05.1~dfsg-1+deb13u1
-
Introduced through: wordpress@latest › ghostscript/libgs10@10.05.1~dfsg-1+deb13u1
-
Introduced through: wordpress@latest › ghostscript/libgs10-common@10.05.1~dfsg-1+deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream ghostscript package and not the ghostscript package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
In Artifex Ghostscript through 10.05.1, ocr_begin_page in devices/gdevpdfocr.c has an integer overflow that leads to a heap-based buffer overflow in ocr_line8.
Remediation
There is no fixed version for Debian:13 ghostscript.
References
low severity
- Vulnerable module: imagemagick/imagemagick-7-common
- Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u3, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3 and others
Detailed paths
-
Introduced through: wordpress@latest › imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u3
-
Introduced through: wordpress@latest › imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3
-
Introduced through: wordpress@latest › imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream imagemagick package and not the imagemagick package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A design flaw in image processing software that modifies JPEG images might not modify the original EXIF thumbnail, which could lead to an information leak of potentially sensitive visual information that had been removed from the main JPEG image.
Remediation
There is no fixed version for Debian:13 imagemagick.
References
low severity
- Vulnerable module: imagemagick/imagemagick-7-common
- Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u3, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3 and others
Detailed paths
-
Introduced through: wordpress@latest › imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u3
-
Introduced through: wordpress@latest › imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3
-
Introduced through: wordpress@latest › imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream imagemagick package and not the imagemagick package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
The ReadPCXImage function in coders/pcx.c in ImageMagick 7.0.4.9 allows remote attackers to cause a denial of service (attempted large memory allocation and application crash) via a crafted file. NOTE: this vulnerability exists because of an incomplete fix for CVE-2016-8862 and CVE-2016-8866.
Remediation
There is no fixed version for Debian:13 imagemagick.
References
- https://security-tracker.debian.org/tracker/CVE-2017-7275
- https://github.com/ImageMagick/ImageMagick/issues/271
- https://blogs.gentoo.org/ago/2017/03/27/imagemagick-memory-allocation-failure-in-acquiremagickmemory-memory-c-incomplete-fix-for-cve-2016-8862-and-cve-2016-8866/
- http://www.securityfocus.com/bid/97166
low severity
- Vulnerable module: imagemagick/imagemagick-7-common
- Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u3, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3 and others
Detailed paths
-
Introduced through: wordpress@latest › imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u3
-
Introduced through: wordpress@latest › imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3
-
Introduced through: wordpress@latest › imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream imagemagick package and not the imagemagick package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
The IsPixelMonochrome function in MagickCore/pixel-accessor.h in ImageMagick 7.0.3.0 allows remote attackers to cause a denial of service (out-of-bounds read and crash) via a crafted file. NOTE: the vendor says "This is a Q64 issue and we do not support Q64."
Remediation
There is no fixed version for Debian:13 imagemagick.
References
- https://security-tracker.debian.org/tracker/CVE-2016-8678
- https://github.com/ImageMagick/ImageMagick/issues/272
- http://www.openwall.com/lists/oss-security/2016/10/16/2
- http://www.openwall.com/lists/oss-security/2016/12/08/18
- https://bugzilla.redhat.com/show_bug.cgi?id=1385694
- http://www.securityfocus.com/bid/93599
low severity
- Vulnerable module: libpng1.6/libpng16-16t64
- Introduced through: libpng1.6/libpng16-16t64@1.6.48-1+deb13u1
Detailed paths
-
Introduced through: wordpress@latest › libpng1.6/libpng16-16t64@1.6.48-1+deb13u1
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:13 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:13 libpng1.6.
References
low severity
- Vulnerable module: libraw/libraw23t64
- Introduced through: libraw/libraw23t64@0.21.4-2
Detailed paths
-
Introduced through: wordpress@latest › libraw/libraw23t64@0.21.4-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libraw package and not the libraw package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
libraw 20.0 has a null pointer dereference vulnerability in parse_tiff_ifd in src/metadata/tiff.cpp, which may result in context-dependent arbitrary code execution. Note: this vulnerability occurs only if you compile the software in a certain way
Remediation
There is no fixed version for Debian:13 libraw.
References
- https://security-tracker.debian.org/tracker/CVE-2020-24890
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/EWHUZCRMGOC3QS6C65KWBM6ZJM25V6HI/
- https://security.gentoo.org/glsa/202010-05
- https://github.com/LibRaw/LibRaw/issues/335
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/EWHUZCRMGOC3QS6C65KWBM6ZJM25V6HI/
low severity
- Vulnerable module: patch
- Introduced through: patch@2.8-2
Detailed paths
-
Introduced through: wordpress@latest › patch@2.8-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream patch package and not the patch package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
An Invalid Pointer vulnerability exists in GNU patch 2.7 via the another_hunk function, which causes a Denial of Service.
Remediation
There is no fixed version for Debian:13 patch.
References
low severity
- Vulnerable module: re2c
- Introduced through: re2c@4.1-1
Detailed paths
-
Introduced through: wordpress@latest › re2c@4.1-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream re2c package and not the re2c package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
re2c before 2.0 has uncontrolled recursion that causes stack consumption in find_fixed_tags.
Remediation
There is no fixed version for Debian:13 re2c.
References
low severity
- Vulnerable module: util-linux
- Introduced through: util-linux@2.41-5, util-linux/bsdutils@1:2.41-5 and others
Detailed paths
-
Introduced through: wordpress@latest › util-linux@2.41-5
-
Introduced through: wordpress@latest › util-linux/bsdutils@1:2.41-5
-
Introduced through: wordpress@latest › util-linux/libblkid1@2.41-5
-
Introduced through: wordpress@latest › util-linux/liblastlog2-2@2.41-5
-
Introduced through: wordpress@latest › util-linux/libmount1@2.41-5
-
Introduced through: wordpress@latest › util-linux/libsmartcols1@2.41-5
-
Introduced through: wordpress@latest › util-linux/libuuid1@2.41-5
-
Introduced through: wordpress@latest › util-linux/login@1:4.16.0-2+really2.41-5
-
Introduced through: wordpress@latest › util-linux/mount@2.41-5
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:13 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:13 util-linux.
References
- https://security-tracker.debian.org/tracker/CVE-2022-0563
- https://lore.kernel.org/util-linux/20220214110609.msiwlm457ngoic6w@ws.net.home/T/#u
- https://lore.kernel.org/util-linux/20220214110609.msiwlm457ngoic6w%40ws.net.home/T/#u
- https://security.gentoo.org/glsa/202401-08
- https://security.netapp.com/advisory/ntap-20220331-0002/
low severity
- Vulnerable module: patch
- Introduced through: patch@2.8-2
Detailed paths
-
Introduced through: wordpress@latest › patch@2.8-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream patch package and not the patch package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
Directory traversal vulnerability in util.c in GNU patch 2.6.1 and earlier allows user-assisted remote attackers to create or overwrite arbitrary files via a filename that is specified with a .. (dot dot) or full pathname, a related issue to CVE-2010-1679.
Remediation
There is no fixed version for Debian:13 patch.
References
- https://security-tracker.debian.org/tracker/CVE-2010-4651
- http://support.apple.com/kb/HT4723
- http://lists.apple.com/archives/security-announce/2011//Jun/msg00000.html
- http://lists.fedoraproject.org/pipermail/package-announce/2011-March/055241.html
- http://lists.fedoraproject.org/pipermail/package-announce/2011-March/055246.html
- http://git.savannah.gnu.org/cgit/patch.git/commit/?id=685a78b6052f4df6eac6d625a545cfb54a6ac0e1
- http://lists.gnu.org/archive/html/bug-patch/2010-12/msg00000.html
- http://www.vupen.com/english/advisories/2011/0600
- http://openwall.com/lists/oss-security/2011/01/05/10
- http://openwall.com/lists/oss-security/2011/01/06/19
- http://openwall.com/lists/oss-security/2011/01/06/20
- http://openwall.com/lists/oss-security/2011/01/06/21
- https://bugzilla.redhat.com/show_bug.cgi?id=667529
- http://secunia.com/advisories/43663
- http://secunia.com/advisories/43677
- http://www.securityfocus.com/bid/46768
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2010-4651
low severity
- Vulnerable module: apache2
- Introduced through: apache2@2.4.65-2, apache2/apache2-bin@2.4.65-2 and others
Detailed paths
-
Introduced through: wordpress@latest › apache2@2.4.65-2
-
Introduced through: wordpress@latest › apache2/apache2-bin@2.4.65-2
-
Introduced through: wordpress@latest › apache2/apache2-data@2.4.65-2
-
Introduced through: wordpress@latest › apache2/apache2-utils@2.4.65-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream apache2 package and not the apache2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
The mod_php module for the Apache HTTP Server allows local users with write access to PHP scripts to send signals to the server's process group and use the server's file descriptors, as demonstrated by sending a STOP signal, then intercepting incoming connections on the server's TCP port. NOTE: the PHP developer has disputed this vulnerability, saying "The opened file descriptors are opened by Apache. It is the job of Apache to protect them ... Not a bug in PHP.
Remediation
There is no fixed version for Debian:13 apache2.
References
- https://security-tracker.debian.org/tracker/CVE-2003-1307
- http://www.securityfocus.com/archive/1/348368
- http://www.securityfocus.com/archive/1/449234/100/0/threaded
- http://www.securityfocus.com/archive/1/449298/100/0/threaded
- http://bugs.php.net/38915
- http://hackerdom.ru/~dimmo/phpexpl.c
- http://www.securityfocus.com/bid/9302
low severity
- Vulnerable module: apache2
- Introduced through: apache2@2.4.65-2, apache2/apache2-bin@2.4.65-2 and others
Detailed paths
-
Introduced through: wordpress@latest › apache2@2.4.65-2
-
Introduced through: wordpress@latest › apache2/apache2-bin@2.4.65-2
-
Introduced through: wordpress@latest › apache2/apache2-data@2.4.65-2
-
Introduced through: wordpress@latest › apache2/apache2-utils@2.4.65-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream apache2 package and not the apache2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
suexec in Apache HTTP Server (httpd) 2.2.3 does not verify combinations of user and group IDs on the command line, which might allow local users to leverage other vulnerabilities to create arbitrary UID/GID owned files if /proc is mounted. NOTE: the researcher, who is reliable, claims that the vendor disputes the issue because "the attacks described rely on an insecure server configuration" in which the user "has write access to the document root." In addition, because this is dependent on other vulnerabilities, perhaps this is resultant and should not be included in CVE.
Remediation
There is no fixed version for Debian:13 apache2.
References
low severity
- Vulnerable module: avahi/libavahi-client3
- Introduced through: avahi/libavahi-client3@0.8-16, avahi/libavahi-common-data@0.8-16 and others
Detailed paths
-
Introduced through: wordpress@latest › avahi/libavahi-client3@0.8-16
-
Introduced through: wordpress@latest › avahi/libavahi-common-data@0.8-16
-
Introduced through: wordpress@latest › avahi/libavahi-common3@0.8-16
NVD Description
Note: Versions mentioned in the description apply only to the upstream avahi package and not the avahi package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A flaw was found in the Avahi-daemon, where it initializes DNS transaction IDs randomly only once at startup, incrementing them sequentially after that. This predictable behavior facilitates DNS spoofing attacks, allowing attackers to guess transaction IDs.
Remediation
There is no fixed version for Debian:13 avahi.
References
low severity
- Vulnerable module: avahi/libavahi-client3
- Introduced through: avahi/libavahi-client3@0.8-16, avahi/libavahi-common-data@0.8-16 and others
Detailed paths
-
Introduced through: wordpress@latest › avahi/libavahi-client3@0.8-16
-
Introduced through: wordpress@latest › avahi/libavahi-common-data@0.8-16
-
Introduced through: wordpress@latest › avahi/libavahi-common3@0.8-16
NVD Description
Note: Versions mentioned in the description apply only to the upstream avahi package and not the avahi package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A flaw was found in Avahi-daemon, which relies on fixed source ports for wide-area DNS queries. This issue simplifies attacks where malicious DNS responses are injected.
Remediation
There is no fixed version for Debian:13 avahi.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A vulnerability has been found in GNU Binutils 2.43 and classified as problematic. Affected by this vulnerability is the function __sanitizer::internal_strlen of the file binutils/nm.c of the component nm. The manipulation of the argument const leads to buffer overflow. The attack can be launched remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used.
Remediation
There is no fixed version for Debian:13 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-1147
- https://sourceware.org/bugzilla/attachment.cgi?id=15881
- https://sourceware.org/bugzilla/show_bug.cgi?id=32556
- https://vuldb.com/?ctiid.295051
- https://vuldb.com/?id.295051
- https://www.gnu.org/
- https://security.netapp.com/advisory/ntap-20250404-0003/
- https://vuldb.com/?submit.485254
low severity
- Vulnerable module: glib2.0/libglib2.0-0t64
- Introduced through: glib2.0/libglib2.0-0t64@2.84.4-3~deb13u1
Detailed paths
-
Introduced through: wordpress@latest › glib2.0/libglib2.0-0t64@2.84.4-3~deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
GLib 2.31.8 and earlier, when the g_str_hash function is used, computes hash values without restricting the ability to trigger hash collisions predictably, which allows context-dependent attackers to cause a denial of service (CPU consumption) via crafted input to an application that maintains a hash table. NOTE: this issue may be disputed by the vendor; the existence of the g_str_hash function is not a vulnerability in the library, because callers of g_hash_table_new and g_hash_table_new_full can specify an arbitrary hash function that is appropriate for the application.
Remediation
There is no fixed version for Debian:13 glib2.0.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.41-12, glibc/libc-dev-bin@2.41-12 and others
Detailed paths
-
Introduced through: wordpress@latest › glibc/libc-bin@2.41-12
-
Introduced through: wordpress@latest › glibc/libc-dev-bin@2.41-12
-
Introduced through: wordpress@latest › glibc/libc6@2.41-12
-
Introduced through: wordpress@latest › glibc/libc6-dev@2.41-12
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:13 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:13 glibc.
References
- https://security-tracker.debian.org/tracker/CVE-2019-1010024
- https://support.f5.com/csp/article/K06046097
- https://support.f5.com/csp/article/K06046097?utm_source=f5support&utm_medium=RSS
- https://sourceware.org/bugzilla/show_bug.cgi?id=22852
- http://www.securityfocus.com/bid/109162
- https://ubuntu.com/security/CVE-2019-1010024
- https://support.f5.com/csp/article/K06046097?utm_source=f5support&%3Butm_medium=RSS
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.41-12, glibc/libc-dev-bin@2.41-12 and others
Detailed paths
-
Introduced through: wordpress@latest › glibc/libc-bin@2.41-12
-
Introduced through: wordpress@latest › glibc/libc-dev-bin@2.41-12
-
Introduced through: wordpress@latest › glibc/libc6@2.41-12
-
Introduced through: wordpress@latest › glibc/libc6-dev@2.41-12
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:13 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:13 glibc.
References
- https://security-tracker.debian.org/tracker/CVE-2019-1010025
- https://support.f5.com/csp/article/K06046097
- https://support.f5.com/csp/article/K06046097?utm_source=f5support&utm_medium=RSS
- https://sourceware.org/bugzilla/show_bug.cgi?id=22853
- https://ubuntu.com/security/CVE-2019-1010025
- https://support.f5.com/csp/article/K06046097?utm_source=f5support&%3Butm_medium=RSS
low severity
- Vulnerable module: imagemagick/imagemagick-7-common
- Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u3, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3 and others
Detailed paths
-
Introduced through: wordpress@latest › imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u3
-
Introduced through: wordpress@latest › imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3
-
Introduced through: wordpress@latest › imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream imagemagick package and not the imagemagick package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
ImageMagick is free and open-source software used for editing and manipulating digital images. Prior to versions 6.9.13-27 and 7.1.2-1, there is undefined behavior (function-type-mismatch) in splay tree cloning callback. This results in a deterministic abort under UBSan (DoS in sanitizer builds), with no crash in a non-sanitized build. This issue has been patched in versions 6.9.13-27 and 7.1.2-1.
Remediation
There is no fixed version for Debian:13 imagemagick.
References
low severity
- Vulnerable module: imagemagick/imagemagick-7-common
- Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u3, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3 and others
Detailed paths
-
Introduced through: wordpress@latest › imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u3
-
Introduced through: wordpress@latest › imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3
-
Introduced through: wordpress@latest › imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream imagemagick package and not the imagemagick package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
Multiple unspecified vulnerabilities in GraphicsMagick before 1.2.4 allow remote attackers to cause a denial of service (crash, infinite loop, or memory consumption) via (a) unspecified vectors in the (1) AVI, (2) AVS, (3) DCM, (4) EPT, (5) FITS, (6) MTV, (7) PALM, (8) RLA, and (9) TGA decoder readers; and (b) the GetImageCharacteristics function in magick/image.c, as reachable from a crafted (10) PNG, (11) JPEG, (12) BMP, or (13) TIFF file.
Remediation
There is no fixed version for Debian:13 imagemagick.
References
- https://security-tracker.debian.org/tracker/CVE-2008-3134
- http://sourceforge.net/forum/forum.php?forum_id=841176
- http://sourceforge.net/project/shownotes.php?release_id=610253
- http://www.vupen.com/english/advisories/2008/1984/references
- http://xforce.iss.net/xforce/xfdb/43511
- http://xforce.iss.net/xforce/xfdb/43513
- http://lists.opensuse.org/opensuse-security-announce/2008-10/msg00004.html
- http://secunia.com/advisories/30879
- http://secunia.com/advisories/32151
- http://www.securityfocus.com/bid/30055
- http://www.securitytracker.com/id?1020413
- https://exchange.xforce.ibmcloud.com/vulnerabilities/43511
- https://exchange.xforce.ibmcloud.com/vulnerabilities/43513
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@257.9-1~deb13u1 and systemd/libudev1@257.9-1~deb13u1
Detailed paths
-
Introduced through: wordpress@latest › systemd/libsystemd0@257.9-1~deb13u1
-
Introduced through: wordpress@latest › systemd/libudev1@257.9-1~deb13u1
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:13 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:13 systemd.
References
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@257.9-1~deb13u1 and systemd/libudev1@257.9-1~deb13u1
Detailed paths
-
Introduced through: wordpress@latest › systemd/libsystemd0@257.9-1~deb13u1
-
Introduced through: wordpress@latest › systemd/libudev1@257.9-1~deb13u1
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:13 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:13 systemd.
References
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@257.9-1~deb13u1 and systemd/libudev1@257.9-1~deb13u1
Detailed paths
-
Introduced through: wordpress@latest › systemd/libsystemd0@257.9-1~deb13u1
-
Introduced through: wordpress@latest › systemd/libudev1@257.9-1~deb13u1
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:13 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:13 systemd.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A vulnerability was found in GNU Binutils 2.43 and classified as critical. This issue affects the function _bfd_elf_gc_mark_rsec of the file elflink.c of the component ld. The manipulation leads to heap-based buffer overflow. The attack may be initiated remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. The patch is named f9978defb6fab0bd8583942d97c112b0932ac814. It is recommended to apply a patch to fix this issue.
Remediation
There is no fixed version for Debian:13 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-1176
- https://sourceware.org/bugzilla/attachment.cgi?id=15913
- https://sourceware.org/bugzilla/show_bug.cgi?id=32636
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=f9978defb6fab0bd8583942d97c112b0932ac814
- https://vuldb.com/?ctiid.295079
- https://vuldb.com/?id.295079
- https://vuldb.com/?submit.495329
- https://www.gnu.org/
- https://security.netapp.com/advisory/ntap-20250411-0007/
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A vulnerability classified as critical was found in GNU Binutils 2.43. This vulnerability affects the function _bfd_elf_gc_mark_rsec of the file bfd/elflink.c of the component ld. The manipulation leads to memory corruption. The attack can be initiated remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The name of the patch is 931494c9a89558acb36a03a340c01726545eef24. It is recommended to apply a patch to fix this issue.
Remediation
There is no fixed version for Debian:13 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-1181
- https://sourceware.org/bugzilla/attachment.cgi?id=15918
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=931494c9a89558acb36a03a340c01726545eef24
- https://vuldb.com/?ctiid.295084
- https://vuldb.com/?id.295084
- https://www.gnu.org/
- https://security.netapp.com/advisory/ntap-20250425-0007/
- https://sourceware.org/bugzilla/show_bug.cgi?id=32643
- https://vuldb.com/?submit.495402
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A vulnerability, which was classified as critical, was found in GNU Binutils 2.43. Affected is the function bfd_elf_reloc_symbol_deleted_p of the file bfd/elflink.c of the component ld. The manipulation leads to memory corruption. It is possible to launch the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. The patch is identified as b425859021d17adf62f06fb904797cf8642986ad. It is recommended to apply a patch to fix this issue.
Remediation
There is no fixed version for Debian:13 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-1182
- https://sourceware.org/bugzilla/attachment.cgi?id=15919
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b425859021d17adf62f06fb904797cf8642986ad
- https://vuldb.com/?ctiid.295086
- https://vuldb.com/?id.295086
- https://www.gnu.org/
- https://sourceware.org/bugzilla/show_bug.cgi?id=32644
- https://vuldb.com/?submit.495407
low severity
- Vulnerable module: coreutils
- Introduced through: coreutils@9.7-3
Detailed paths
-
Introduced through: wordpress@latest › coreutils@9.7-3
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:13 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:13 coreutils.
References
low severity
- Vulnerable module: openldap/libldap2
- Introduced through: openldap/libldap2@2.6.10+dfsg-1
Detailed paths
-
Introduced through: wordpress@latest › openldap/libldap2@2.6.10+dfsg-1
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:13 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:13 openldap.
References
low severity
- Vulnerable module: coreutils
- Introduced through: coreutils@9.7-3
Detailed paths
-
Introduced through: wordpress@latest › coreutils@9.7-3
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:13 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:13 coreutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-5278
- https://access.redhat.com/security/cve/CVE-2025-5278
- https://bugzilla.redhat.com/show_bug.cgi?id=2368764
- http://www.openwall.com/lists/oss-security/2025/05/27/2
- http://www.openwall.com/lists/oss-security/2025/05/29/1
- https://cgit.git.savannah.gnu.org/cgit/coreutils.git/tree/NEWS?id=8c9602e3a145e9596dc1a63c6ed67865814b6633#n14
- http://www.openwall.com/lists/oss-security/2025/05/29/2
- https://cgit.git.savannah.gnu.org/cgit/coreutils.git/commit/?id=8c9602e3a145e9596dc1a63c6ed67865814b6633
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@257.9-1~deb13u1 and systemd/libudev1@257.9-1~deb13u1
Detailed paths
-
Introduced through: wordpress@latest › systemd/libsystemd0@257.9-1~deb13u1
-
Introduced through: wordpress@latest › systemd/libudev1@257.9-1~deb13u1
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:13 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:13 systemd.
References
low severity
- Vulnerable module: apache2
- Introduced through: apache2@2.4.65-2, apache2/apache2-bin@2.4.65-2 and others
Detailed paths
-
Introduced through: wordpress@latest › apache2@2.4.65-2
-
Introduced through: wordpress@latest › apache2/apache2-bin@2.4.65-2
-
Introduced through: wordpress@latest › apache2/apache2-data@2.4.65-2
-
Introduced through: wordpress@latest › apache2/apache2-utils@2.4.65-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream apache2 package and not the apache2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
The Apache HTTP Server 2.0.44, when DNS resolution is enabled for client IP addresses, uses a logging format that does not identify whether a dotted quad represents an unresolved IP address, which allows remote attackers to spoof IP addresses via crafted DNS responses containing numerical top-level domains, as demonstrated by a forged 123.123.123.123 domain name, related to an "Inverse Lookup Log Corruption (ILLC)" issue.
Remediation
There is no fixed version for Debian:13 apache2.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.41-12, glibc/libc-dev-bin@2.41-12 and others
Detailed paths
-
Introduced through: wordpress@latest › glibc/libc-bin@2.41-12
-
Introduced through: wordpress@latest › glibc/libc-dev-bin@2.41-12
-
Introduced through: wordpress@latest › glibc/libc6@2.41-12
-
Introduced through: wordpress@latest › glibc/libc6-dev@2.41-12
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:13 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:13 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/libgnutls30t64
- Introduced through: gnutls28/libgnutls30t64@3.8.9-3
Detailed paths
-
Introduced through: wordpress@latest › gnutls28/libgnutls30t64@3.8.9-3
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:13 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:13 gnutls28.
References
- https://security-tracker.debian.org/tracker/CVE-2011-3389
- http://lists.apple.com/archives/Security-announce/2011//Oct/msg00001.html
- http://lists.apple.com/archives/Security-announce/2011//Oct/msg00002.html
- http://support.apple.com/kb/HT4999
- http://support.apple.com/kb/HT5001
- http://support.apple.com/kb/HT5130
- http://support.apple.com/kb/HT5281
- http://support.apple.com/kb/HT5501
- http://support.apple.com/kb/HT6150
- http://lists.apple.com/archives/security-announce/2012/Feb/msg00000.html
- http://lists.apple.com/archives/security-announce/2012/Jul/msg00001.html
- http://lists.apple.com/archives/security-announce/2012/May/msg00001.html
- http://lists.apple.com/archives/security-announce/2012/Sep/msg00004.html
- http://lists.apple.com/archives/security-announce/2013/Oct/msg00004.html
- http://www.us-cert.gov/cas/techalerts/TA12-010A.html
- http://www.kb.cert.org/vuls/id/864643
- http://googlechromereleases.blogspot.com/2011/10/chrome-stable-release.html
- http://blog.mozilla.com/security/2011/09/27/attack-against-tls-protected-communications/
- http://blogs.technet.com/b/msrc/archive/2011/09/26/microsoft-releases-security-advisory-2588513.aspx
- http://blogs.technet.com/b/srd/archive/2011/09/26/is-ssl-broken-more-about-security-advisory-2588513.aspx
- http://curl.haxx.se/docs/adv_20120124B.html
- http://downloads.asterisk.org/pub/security/AST-2016-001.html
- http://my.opera.com/securitygroup/blog/2011/09/28/the-beast-ssl-tls-issue
- https://blogs.oracle.com/sunsecurity/entry/multiple_vulnerabilities_in_fetchmail
- https://bugzilla.novell.com/show_bug.cgi?id=719047
- https://cert-portal.siemens.com/productcert/pdf/ssa-556833.pdf
- http://technet.microsoft.com/security/advisory/2588513
- http://www.apcmedia.com/salestools/SJHN-7RKGNM/SJHN-7RKGNM_R4_EN.pdf
- http://www.ibm.com/developerworks/java/jdk/alerts/
- http://www.imperialviolet.org/2011/09/23/chromeandbeast.html
- http://www.opera.com/docs/changelogs/mac/1151/
- http://www.opera.com/docs/changelogs/mac/1160/
- http://www.opera.com/docs/changelogs/unix/1151/
- http://www.opera.com/docs/changelogs/unix/1160/
- http://www.opera.com/docs/changelogs/windows/1151/
- http://www.opera.com/docs/changelogs/windows/1160/
- http://www.opera.com/support/kb/view/1004/
- http://www.debian.org/security/2012/dsa-2398
- http://security.gentoo.org/glsa/glsa-201203-02.xml
- http://security.gentoo.org/glsa/glsa-201406-32.xml
- https://h20564.www2.hp.com/portal/site/hpsc/public/kb/docDisplay?docId=emr_na-c03839862
- http://marc.info/?l=bugtraq&m=132750579901589&w=2
- http://marc.info/?l=bugtraq&m=132872385320240&w=2
- http://marc.info/?l=bugtraq&m=133365109612558&w=2
- http://marc.info/?l=bugtraq&m=133728004526190&w=2
- http://marc.info/?l=bugtraq&m=134254866602253&w=2
- http://marc.info/?l=bugtraq&m=134254957702612&w=2
- http://ekoparty.org/2011/juliano-rizzo.php
- http://eprint.iacr.org/2004/111
- http://eprint.iacr.org/2006/136
- http://isc.sans.edu/diary/SSL+TLS+part+3+/11635
- https://ics-cert.us-cert.gov/advisories/ICSMA-18-058-02
- http://vnhacker.blogspot.com/2011/09/beast.html
- http://www.educatedguesswork.org/2011/09/security_impact_of_the_rizzodu.html
- http://www.insecure.cl/Beast-SSL.rar
- https://docs.microsoft.com/en-us/security-updates/securitybulletins/2012/ms12-006
- http://technet.microsoft.com/security/bulletin/MS12-006
- http://lists.opensuse.org/opensuse-security-announce/2012-01/msg00049.html
- http://lists.opensuse.org/opensuse-security-announce/2012-01/msg00051.html
- http://lists.opensuse.org/opensuse-security-announce/2012-05/msg00009.html
- http://www.oracle.com/technetwork/topics/security/cpujan2015-1972971.html
- http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html
- http://www.oracle.com/technetwork/topics/security/javacpuoct2011-443431.html
- http://osvdb.org/74829
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14752
- https://bugzilla.redhat.com/show_bug.cgi?id=737506
- http://rhn.redhat.com/errata/RHSA-2012-0508.html
- http://rhn.redhat.com/errata/RHSA-2013-1455.html
- http://secunia.com/advisories/45791
- http://secunia.com/advisories/47998
- http://secunia.com/advisories/48256
- http://secunia.com/advisories/48692
- http://secunia.com/advisories/48915
- http://secunia.com/advisories/48948
- http://secunia.com/advisories/49198
- http://secunia.com/advisories/55322
- http://secunia.com/advisories/55350
- http://secunia.com/advisories/55351
- http://www.securityfocus.com/bid/49388
- http://www.securityfocus.com/bid/49778
- http://www.securitytracker.com/id?1025997
- http://www.securitytracker.com/id?1026103
- http://www.securitytracker.com/id?1026704
- http://www.securitytracker.com/id/1029190
- http://lists.opensuse.org/opensuse-security-announce/2020-01/msg00040.html
- https://hermes.opensuse.org/messages/13154861
- https://hermes.opensuse.org/messages/13155432
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2011-3389
- http://www.ubuntu.com/usn/USN-1263-1
- http://www.mandriva.com/security/advisories?name=MDVSA-2012:058
- http://www.redhat.com/support/errata/RHSA-2011-1384.html
- http://www.redhat.com/support/errata/RHSA-2012-0006.html
- https://github.com/mpgn/BEAST-PoC
low severity
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.46.1-7
Detailed paths
-
Introduced through: wordpress@latest › sqlite3/libsqlite3-0@3.46.1-7
NVD Description
Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A Memory Leak vulnerability exists in SQLite Project SQLite3 3.35.1 and 3.37.0 via maliciously crafted SQL Queries (made via editing the Database File), it is possible to query a record, and leak subsequent bytes of memory that extend beyond the record, which could let a malicious user obtain sensitive information. NOTE: The developer disputes this as a vulnerability stating that If you give SQLite a corrupted database file and submit a query against the database, it might read parts of the database that you did not intend or expect.
Remediation
There is no fixed version for Debian:13 sqlite3.
References
- https://security-tracker.debian.org/tracker/CVE-2021-45346
- https://github.com/guyinatuxedo/sqlite3_record_leaking
- https://security.netapp.com/advisory/ntap-20220303-0001/
- https://sqlite.org/forum/forumpost/056d557c2f8c452ed5
- https://sqlite.org/forum/forumpost/53de8864ba114bf6
- https://www.sqlite.org/cves.html#status_of_recent_sqlite_cves
low severity
- Vulnerable module: openldap/libldap2
- Introduced through: openldap/libldap2@2.6.10+dfsg-1
Detailed paths
-
Introduced through: wordpress@latest › openldap/libldap2@2.6.10+dfsg-1
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:13 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:13 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: apache2
- Introduced through: apache2@2.4.65-2, apache2/apache2-bin@2.4.65-2 and others
Detailed paths
-
Introduced through: wordpress@latest › apache2@2.4.65-2
-
Introduced through: wordpress@latest › apache2/apache2-bin@2.4.65-2
-
Introduced through: wordpress@latest › apache2/apache2-data@2.4.65-2
-
Introduced through: wordpress@latest › apache2/apache2-utils@2.4.65-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream apache2 package and not the apache2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
mod_usertrack in Apache 1.3.11 through 1.3.20 generates session ID's using predictable information including host IP address, system time and server process ID, which allows local users to obtain session ID's and bypass authentication when these session ID's are used for authentication.
Remediation
There is no fixed version for Debian:13 apache2.
References
low severity
- Vulnerable module: apache2
- Introduced through: apache2@2.4.65-2, apache2/apache2-bin@2.4.65-2 and others
Detailed paths
-
Introduced through: wordpress@latest › apache2@2.4.65-2
-
Introduced through: wordpress@latest › apache2/apache2-bin@2.4.65-2
-
Introduced through: wordpress@latest › apache2/apache2-data@2.4.65-2
-
Introduced through: wordpress@latest › apache2/apache2-utils@2.4.65-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream apache2 package and not the apache2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
CRLF injection vulnerability in the mod_negotiation module in the Apache HTTP Server 2.2.6 and earlier in the 2.2.x series, 2.0.61 and earlier in the 2.0.x series, and 1.3.39 and earlier in the 1.3.x series allows remote authenticated users to inject arbitrary HTTP headers and conduct HTTP response splitting attacks by uploading a file with a multi-line name containing HTTP header sequences and a file extension, which leads to injection within a (1) "406 Not Acceptable" or (2) "300 Multiple Choices" HTTP response when the extension is omitted in a request for the file.
Remediation
There is no fixed version for Debian:13 apache2.
References
- https://security-tracker.debian.org/tracker/CVE-2008-0456
- https://lists.apache.org/thread.html/8d63cb8e9100f28a99429b4328e4e7cebce861d5772ac9863ba2ae6f@%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/f7f95ac1cd9895db2714fa3ebaa0b94d0c6df360f742a40951384a53@%3Ccvs.httpd.apache.org%3E
- http://support.apple.com/kb/HT3549
- http://lists.apple.com/archives/security-announce/2009/May/msg00002.html
- http://www.securityfocus.com/archive/1/486847/100/0/threaded
- http://www.us-cert.gov/cas/techalerts/TA09-133A.html
- http://security.gentoo.org/glsa/glsa-200803-19.xml
- http://www.mindedsecurity.com/MSA01150108.html
- https://lists.apache.org/thread.html/r57608dc51b79102f3952ae06f54d5277b649c86d6533dcd6a7d201f7@%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/r75cbe9ea3e2114e4271bbeca7aff96117b50c1b6eb7c4772b0337c1f@%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/r7dd6be4dc38148704f2edafb44a8712abaa3a2be120d6c3314d55919@%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/r84d043c2115176958562133d96d851495d712aa49da155d81f6733be@%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/r9ea3538f229874c80a10af473856a81fbf5f694cd7f471cc679ba70b@%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/r9f93cf6dde308d42a9c807784e8102600d0397f5f834890708bf6920@%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/rc4c53a0d57b2771ecd4b965010580db355e38137c8711311ee1073a8@%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/rdca61ae990660bacb682295f2a09d34612b7bb5f457577fe17f4d064@%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/rf6449464fd8b7437704c55f88361b66f12d5b5f90bcce66af4be4ba9@%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/rfbaf647d52c1cb843e726a0933f156366a806cead84fbd430951591b@%3Ccvs.httpd.apache.org%3E
- http://rhn.redhat.com/errata/RHSA-2013-0130.html
- http://securitytracker.com/id?1019256
- http://secunia.com/advisories/29348
- http://secunia.com/advisories/35074
- http://www.securityfocus.com/bid/27409
- http://securityreason.com/securityalert/3575
- http://www.vupen.com/english/advisories/2009/1297
- https://exchange.xforce.ibmcloud.com/vulnerabilities/39893
- https://lists.apache.org/thread.html/8d63cb8e9100f28a99429b4328e4e7cebce861d5772ac9863ba2ae6f%40%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/f7f95ac1cd9895db2714fa3ebaa0b94d0c6df360f742a40951384a53%40%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/r57608dc51b79102f3952ae06f54d5277b649c86d6533dcd6a7d201f7%40%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/r75cbe9ea3e2114e4271bbeca7aff96117b50c1b6eb7c4772b0337c1f%40%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/r7dd6be4dc38148704f2edafb44a8712abaa3a2be120d6c3314d55919%40%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/r84d043c2115176958562133d96d851495d712aa49da155d81f6733be%40%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/r9ea3538f229874c80a10af473856a81fbf5f694cd7f471cc679ba70b%40%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/r9f93cf6dde308d42a9c807784e8102600d0397f5f834890708bf6920%40%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/rc4c53a0d57b2771ecd4b965010580db355e38137c8711311ee1073a8%40%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/rdca61ae990660bacb682295f2a09d34612b7bb5f457577fe17f4d064%40%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/rf6449464fd8b7437704c55f88361b66f12d5b5f90bcce66af4be4ba9%40%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/rfbaf647d52c1cb843e726a0933f156366a806cead84fbd430951591b%40%3Ccvs.httpd.apache.org%3E
low severity
- Vulnerable module: apache2
- Introduced through: apache2@2.4.65-2, apache2/apache2-bin@2.4.65-2 and others
Detailed paths
-
Introduced through: wordpress@latest › apache2@2.4.65-2
-
Introduced through: wordpress@latest › apache2/apache2-bin@2.4.65-2
-
Introduced through: wordpress@latest › apache2/apache2-data@2.4.65-2
-
Introduced through: wordpress@latest › apache2/apache2-utils@2.4.65-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream apache2 package and not the apache2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
The Apache HTTP Server 2.0.44, when DNS resolution is enabled for client IP addresses, allows remote attackers to inject arbitrary text into log files via an HTTP request in conjunction with a crafted DNS response, as demonstrated by injecting XSS sequences, related to an "Inverse Lookup Log Corruption (ILLC)" issue.
Remediation
There is no fixed version for Debian:13 apache2.
References
low severity
- Vulnerable module: apt
- Introduced through: apt@3.0.3 and apt/libapt-pkg7.0@3.0.3
Detailed paths
-
Introduced through: wordpress@latest › apt@3.0.3
-
Introduced through: wordpress@latest › apt/libapt-pkg7.0@3.0.3
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:13 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:13 apt.
References
- https://security-tracker.debian.org/tracker/CVE-2011-3374
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642480
- https://people.canonical.com/~ubuntu-security/cve/2011/CVE-2011-3374.html
- https://seclists.org/fulldisclosure/2011/Sep/221
- https://snyk.io/vuln/SNYK-LINUX-APT-116518
- https://ubuntu.com/security/CVE-2011-3374
- https://access.redhat.com/security/cve/cve-2011-3374
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A vulnerability classified as problematic has been found in GNU Binutils 2.43. Affected is the function xstrdup of the file xstrdup.c of the component ld. The manipulation leads to memory leak. It is possible to launch the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue. The code maintainer explains: "I'm not going to commit some of the leak fixes I've been working on to the 2.44 branch due to concern that would destabilise ld. All of the reported leaks in this bugzilla have been fixed on binutils master."
Remediation
There is no fixed version for Debian:13 binutils.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A vulnerability was found in GNU Binutils 2.44 and classified as problematic. This issue affects the function process_debug_info of the file binutils/dwarf.c of the component DWARF Section Handler. The manipulation leads to memory leak. Attacking locally is a requirement. The identifier of the patch is e51fdff7d2e538c0e5accdd65649ac68e6e0ddd4. It is recommended to apply a patch to fix this issue.
Remediation
There is no fixed version for Debian:13 binutils.
References
low severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u2
Detailed paths
-
Introduced through: wordpress@latest › libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u2
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:13 relevant fixed versions and status.
A vulnerability was found in libxml2 up to 2.14.5. It has been declared as problematic. This vulnerability affects the function xmlParseSGMLCatalog of the component xmlcatalog. The manipulation leads to uncontrolled recursion. Attacking locally is a requirement. The exploit has been disclosed to the public and may be used. The real existence of this vulnerability is still doubted at the moment. The code maintainer explains, that "[t]he issue can only be triggered with untrusted SGML catalogs and it makes absolutely no sense to use untrusted catalogs. I also doubt that anyone is still using SGML catalogs at all."
Remediation
There is no fixed version for Debian:13 libxml2.
References
- https://security-tracker.debian.org/tracker/CVE-2025-8732
- https://drive.google.com/file/d/1woIeYVcSQB_NwfEhaVnX6MedpWJ_nqWl/view?usp=drive_link
- https://gitlab.gnome.org/GNOME/libxml2/-/issues/958
- https://gitlab.gnome.org/GNOME/libxml2/-/issues/958#note_2505853
- https://vuldb.com/?ctiid.319228
- https://vuldb.com/?id.319228
- https://vuldb.com/?submit.622285
low severity
- Vulnerable module: ncurses/libncursesw6
- Introduced through: ncurses/libncursesw6@6.5+20250216-2, ncurses/libtinfo6@6.5+20250216-2 and others
Detailed paths
-
Introduced through: wordpress@latest › ncurses/libncursesw6@6.5+20250216-2
-
Introduced through: wordpress@latest › ncurses/libtinfo6@6.5+20250216-2
-
Introduced through: wordpress@latest › ncurses/ncurses-base@6.5+20250216-2
-
Introduced through: wordpress@latest › ncurses/ncurses-bin@6.5+20250216-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:13 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:13 ncurses.
References
- https://security-tracker.debian.org/tracker/CVE-2025-6141
- https://invisible-island.net/ncurses/NEWS.html#index-t20250329
- https://lists.gnu.org/archive/html/bug-ncurses/2025-03/msg00107.html
- https://lists.gnu.org/archive/html/bug-ncurses/2025-03/msg00109.html
- https://lists.gnu.org/archive/html/bug-ncurses/2025-03/msg00114.html
- https://vuldb.com/?ctiid.312610
- https://vuldb.com/?id.312610
- https://vuldb.com/?submit.593000
- https://www.gnu.org/
low severity
- Vulnerable module: perl
- Introduced through: perl@5.40.1-6, perl/libperl5.40@5.40.1-6 and others
Detailed paths
-
Introduced through: wordpress@latest › perl@5.40.1-6
-
Introduced through: wordpress@latest › perl/libperl5.40@5.40.1-6
-
Introduced through: wordpress@latest › perl/perl-base@5.40.1-6
-
Introduced through: wordpress@latest › perl/perl-modules-5.40@5.40.1-6
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:13 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:13 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: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A vulnerability was found in GNU Binutils 2.43. It has been declared as problematic. This vulnerability affects the function bfd_malloc of the file libbfd.c of the component ld. The manipulation leads to memory leak. The attack can be initiated remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue. The code maintainer explains: "I'm not going to commit some of the leak fixes I've been working on to the 2.44 branch due to concern that would destabilise ld. All of the reported leaks in this bugzilla have been fixed on binutils master."
Remediation
There is no fixed version for Debian:13 binutils.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A vulnerability was found in GNU Binutils 2.43. It has been rated as problematic. This issue affects the function xmemdup of the file xmemdup.c of the component ld. The manipulation leads to memory leak. The attack may be initiated remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue. The code maintainer explains: "I'm not going to commit some of the leak fixes I've been working on to the 2.44 branch due to concern that would destabilise ld. All of the reported leaks in this bugzilla have been fixed on binutils master."
Remediation
There is no fixed version for Debian:13 binutils.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A vulnerability was found in GNU Binutils 2.43. It has been classified as problematic. This affects the function xstrdup of the file libiberty/xmalloc.c of the component ld. The manipulation leads to memory leak. It is possible to initiate the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue. The code maintainer explains: "I'm not going to commit some of the leak fixes I've been working on to the 2.44 branch due to concern that would destabilise ld. All of the reported leaks in this bugzilla have been fixed on binutils master."
Remediation
There is no fixed version for Debian:13 binutils.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A vulnerability was found in GNU Binutils 2.43 and classified as problematic. Affected by this issue is the function link_order_scan of the file ld/ldelfgen.c of the component ld. The manipulation leads to memory leak. The attack may be launched remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue. The code maintainer explains: "I'm not going to commit some of the leak fixes I've been working on to the 2.44 branch due to concern that would destabilise ld. All of the reported leaks in this bugzilla have been fixed on binutils master."
Remediation
There is no fixed version for Debian:13 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-1148
- https://sourceware.org/bugzilla/attachment.cgi?id=15887
- https://sourceware.org/bugzilla/show_bug.cgi?id=32576
- https://vuldb.com/?ctiid.295052
- https://vuldb.com/?id.295052
- https://vuldb.com/?submit.485747
- https://www.gnu.org/
- https://security.netapp.com/advisory/ntap-20250404-0004/
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A vulnerability classified as problematic has been found in GNU Binutils 2.43. This affects the function _bfd_elf_write_section_eh_frame of the file bfd/elf-eh-frame.c of the component ld. The manipulation leads to memory corruption. It is possible to initiate the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue.
Remediation
There is no fixed version for Debian:13 binutils.
References
low severity
- Vulnerable module: tiff/libtiff6
- Introduced through: tiff/libtiff6@4.7.0-3+deb13u1
Detailed paths
-
Introduced through: wordpress@latest › tiff/libtiff6@4.7.0-3+deb13u1
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:13 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:13 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: apache2
- Introduced through: apache2@2.4.65-2, apache2/apache2-bin@2.4.65-2 and others
- Fixed in: 2.4.66-1~deb13u1
Detailed paths
-
Introduced through: wordpress@latest › apache2@2.4.65-2
-
Introduced through: wordpress@latest › apache2/apache2-bin@2.4.65-2
-
Introduced through: wordpress@latest › apache2/apache2-data@2.4.65-2
-
Introduced through: wordpress@latest › apache2/apache2-utils@2.4.65-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream apache2 package and not the apache2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
mod_userdir+suexec bypass via AllowOverride FileInfo vulnerability in Apache HTTP Server. Users with access to use the RequestHeader directive in htaccess can cause some CGI scripts to run under an unexpected userid.
This issue affects Apache HTTP Server: from 2.4.7 through 2.4.65.
Users are recommended to upgrade to version 2.4.66, which fixes the issue.
Remediation
Upgrade Debian:13 apache2 to version 2.4.66-1~deb13u1 or higher.
References
low severity
- Vulnerable module: apache2
- Introduced through: apache2@2.4.65-2, apache2/apache2-bin@2.4.65-2 and others
- Fixed in: 2.4.66-1~deb13u1
Detailed paths
-
Introduced through: wordpress@latest › apache2@2.4.65-2
-
Introduced through: wordpress@latest › apache2/apache2-bin@2.4.65-2
-
Introduced through: wordpress@latest › apache2/apache2-data@2.4.65-2
-
Introduced through: wordpress@latest › apache2/apache2-utils@2.4.65-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream apache2 package and not the apache2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
Improper Neutralization of Escape, Meta, or Control Sequences vulnerability in Apache HTTP Server through environment variables set via the Apache configuration unexpectedly superseding variables calculated by the server for CGI programs.
This issue affects Apache HTTP Server from 2.4.0 through 2.4.65.
Users are recommended to upgrade to version 2.4.66 which fixes the issue.
Remediation
Upgrade Debian:13 apache2 to version 2.4.66-1~deb13u1 or higher.
References
low severity
- Vulnerable module: apache2
- Introduced through: apache2@2.4.65-2, apache2/apache2-bin@2.4.65-2 and others
- Fixed in: 2.4.66-1~deb13u1
Detailed paths
-
Introduced through: wordpress@latest › apache2@2.4.65-2
-
Introduced through: wordpress@latest › apache2/apache2-bin@2.4.65-2
-
Introduced through: wordpress@latest › apache2/apache2-data@2.4.65-2
-
Introduced through: wordpress@latest › apache2/apache2-utils@2.4.65-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream apache2 package and not the apache2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
Apache HTTP Server 2.4.65 and earlier with Server Side Includes (SSI) enabled and mod_cgid (but not mod_cgi) passes the shell-escaped query string to #exec cmd="..." directives.
This issue affects Apache HTTP Server before 2.4.66.
Users are recommended to upgrade to version 2.4.66, which fixes the issue.
Remediation
Upgrade Debian:13 apache2 to version 2.4.66-1~deb13u1 or higher.
References
low severity
- Vulnerable module: apache2
- Introduced through: apache2@2.4.65-2, apache2/apache2-bin@2.4.65-2 and others
- Fixed in: 2.4.66-1~deb13u1
Detailed paths
-
Introduced through: wordpress@latest › apache2@2.4.65-2
-
Introduced through: wordpress@latest › apache2/apache2-bin@2.4.65-2
-
Introduced through: wordpress@latest › apache2/apache2-data@2.4.65-2
-
Introduced through: wordpress@latest › apache2/apache2-utils@2.4.65-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream apache2 package and not the apache2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
An integer overflow in the case of failed ACME certificate renewal leads, after a number of failures (~30 days in default configurations), to the backoff timer becoming 0. Attempts to renew the certificate then are repeated without delays until it succeeds.
This issue affects Apache HTTP Server: from 2.4.30 before 2.4.66.
Users are recommended to upgrade to version 2.4.66, which fixes the issue.
Remediation
Upgrade Debian:13 apache2 to version 2.4.66-1~deb13u1 or higher.
References
low severity
new
- Vulnerable module: avahi/libavahi-client3
- Introduced through: avahi/libavahi-client3@0.8-16, avahi/libavahi-common-data@0.8-16 and others
Detailed paths
-
Introduced through: wordpress@latest › avahi/libavahi-client3@0.8-16
-
Introduced through: wordpress@latest › avahi/libavahi-common-data@0.8-16
-
Introduced through: wordpress@latest › avahi/libavahi-common3@0.8-16
NVD Description
Note: Versions mentioned in the description apply only to the upstream avahi package and not the avahi package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
Avahi is a system which facilitates service discovery on a local network via the mDNS/DNS-SD protocol suite. In versions up to and including 0.9-rc2, the simple protocol server ignores the documented client limit and accepts unlimited connections, allowing for easy local DoS. Although CLIENTS_MAX is defined, server_work() unconditionally accept()s and client_new() always appends the new client and increments n_clients. There is no check against the limit. When client cannot be accepted as a result of maximal socket number of avahi-daemon, it logs unconditionally error per each connection. Unprivileged local users can exhaust daemon memory and file descriptors, causing a denial of service system-wide for mDNS/DNS-SD. Exhausting local file descriptors causes increased system load caused by logging errors of each of request. Overloading prevents glibc calls using nss-mdns plugins to resolve *.local. names and link-local addresses. As of time of publication, no known patched versions are available, but a candidate fix is available in pull request 808, and some workarounds are available. Simple clients are offered for nss-mdns package functionality. It is not possible to disable the unix socket /run/avahi-daemon/socket, but resolution requests received via DBus are not affected directly. Tools avahi-resolve, avahi-resolve-address and avahi-resolve-host-name are not affected, they use DBus interface. It is possible to change permissions of unix socket after avahi-daemon is started. But avahi-daemon does not provide any configuration for it. Additional access restrictions like SELinux can also prevent unwanted tools to access the socket and keep resolution working for trusted users.
Remediation
There is no fixed version for Debian:13 avahi.
References
low severity
new
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
An issue was discovered in function d_unqualified_name in file cp-demangle.c in BinUtils 2.26 allowing attackers to cause a denial of service via crafted PE file.
Remediation
There is no fixed version for Debian:13 binutils.
References
low severity
new
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A buffer overflow vulnerability in function gnu_special in file cplus-dem.c in BinUtils 2.26 allows attackers to cause a denial of service via crafted PE file.
Remediation
There is no fixed version for Debian:13 binutils.
References
low severity
new
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
An issue was discovered in function d_discriminator in file cp-demangle.c in BinUtils 2.26 allows attackers to cause a denial of service via crafted PE file.
Remediation
There is no fixed version for Debian:13 binutils.
References
low severity
new
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
An issue was discovered in function d_print_comp_inner in file cp-demangle.c in BinUtils 2.26 allows attackers to cause a denial of service via crafted PE file.
Remediation
There is no fixed version for Debian:13 binutils.
References
low severity
new
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
An issue was discovered in function d_print_comp_inner in file cp-demangle.c in BinUtils 2.26 allows attackers to cause a denial of service via crafted PE file.
Remediation
There is no fixed version for Debian:13 binutils.
References
low severity
new
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: wordpress@latest › binutils@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-common@2.44-3
-
Introduced through: wordpress@latest › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: wordpress@latest › binutils/libbinutils@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf-nobfd0@2.44-3
-
Introduced through: wordpress@latest › binutils/libctf0@2.44-3
-
Introduced through: wordpress@latest › binutils/libgprofng0@2.44-3
-
Introduced through: wordpress@latest › binutils/libsframe1@2.44-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
An issue was discovered in function d_abi_tags in file cp-demangle.c in BinUtils 2.26 allows attackers to cause a denial of service via crafted PE file.
Remediation
There is no fixed version for Debian:13 binutils.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@8.14.1-2+deb13u2 and curl/libcurl4t64@8.14.1-2+deb13u2
Detailed paths
-
Introduced through: wordpress@latest › curl@8.14.1-2+deb13u2
-
Introduced through: wordpress@latest › curl/libcurl4t64@8.14.1-2+deb13u2
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:13 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:13 curl.
References
low severity
new
- Vulnerable module: curl
- Introduced through: curl@8.14.1-2+deb13u2 and curl/libcurl4t64@8.14.1-2+deb13u2
Detailed paths
-
Introduced through: wordpress@latest › curl@8.14.1-2+deb13u2
-
Introduced through: wordpress@latest › curl/libcurl4t64@8.14.1-2+deb13u2
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:13 relevant fixed versions and status.
When using CURLOPT_PINNEDPUBLICKEY option with libcurl or --pinnedpubkey
with the curl tool,curl should check the public key of the server certificate
to verify the peer.
This check was skipped in a certain condition that would then make curl allow the connection without performing the proper check, thus not noticing a possible impostor. To skip this check, the connection had to be done with QUIC with ngtcp2 built to use GnuTLS and the user had to explicitly disable the standard certificate verification.
Remediation
There is no fixed version for Debian:13 curl.
References
low severity
new
- Vulnerable module: curl
- Introduced through: curl@8.14.1-2+deb13u2 and curl/libcurl4t64@8.14.1-2+deb13u2
Detailed paths
-
Introduced through: wordpress@latest › curl@8.14.1-2+deb13u2
-
Introduced through: wordpress@latest › curl/libcurl4t64@8.14.1-2+deb13u2
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:13 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:13 curl.
References
low severity
new
- Vulnerable module: curl
- Introduced through: curl@8.14.1-2+deb13u2 and curl/libcurl4t64@8.14.1-2+deb13u2
Detailed paths
-
Introduced through: wordpress@latest › curl@8.14.1-2+deb13u2
-
Introduced through: wordpress@latest › curl/libcurl4t64@8.14.1-2+deb13u2
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:13 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:13 curl.
References
low severity
new
- Vulnerable module: curl
- Introduced through: curl@8.14.1-2+deb13u2 and curl/libcurl4t64@8.14.1-2+deb13u2
Detailed paths
-
Introduced through: wordpress@latest › curl@8.14.1-2+deb13u2
-
Introduced through: wordpress@latest › curl/libcurl4t64@8.14.1-2+deb13u2
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:13 relevant fixed versions and status.
When doing TLS related transfers with reused easy or multi handles and
altering the CURLSSLOPT_NO_PARTIALCHAIN option, libcurl could accidentally
reuse a CA store cached in memory for which the partial chain option was
reversed. Contrary to the user's wishes and expectations. This could make
libcurl find and accept a trust chain that it otherwise would not.
Remediation
There is no fixed version for Debian:13 curl.
References
low severity
new
- Vulnerable module: curl
- Introduced through: curl@8.14.1-2+deb13u2 and curl/libcurl4t64@8.14.1-2+deb13u2
Detailed paths
-
Introduced through: wordpress@latest › curl@8.14.1-2+deb13u2
-
Introduced through: wordpress@latest › curl/libcurl4t64@8.14.1-2+deb13u2
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:13 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:13 curl.
References
low severity
new
- Vulnerable module: curl
- Introduced through: curl@8.14.1-2+deb13u2 and curl/libcurl4t64@8.14.1-2+deb13u2
Detailed paths
-
Introduced through: wordpress@latest › curl@8.14.1-2+deb13u2
-
Introduced through: wordpress@latest › curl/libcurl4t64@8.14.1-2+deb13u2
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:13 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:13 curl.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.7.1-2
Detailed paths
-
Introduced through: wordpress@latest › expat/libexpat1@2.7.1-2
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:13 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:13 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
low severity
- Vulnerable module: ghostscript
- Introduced through: ghostscript@10.05.1~dfsg-1+deb13u1, ghostscript/libgs-common@10.05.1~dfsg-1+deb13u1 and others
Detailed paths
-
Introduced through: wordpress@latest › ghostscript@10.05.1~dfsg-1+deb13u1
-
Introduced through: wordpress@latest › ghostscript/libgs-common@10.05.1~dfsg-1+deb13u1
-
Introduced through: wordpress@latest › ghostscript/libgs10@10.05.1~dfsg-1+deb13u1
-
Introduced through: wordpress@latest › ghostscript/libgs10-common@10.05.1~dfsg-1+deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream ghostscript package and not the ghostscript package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
In Artifex GhostXPS before 10.06.0, there is a stack-based buffer overflow in xps_unpredict_tiff in xpstiff.c because the samplesperpixel value is not checked.
Remediation
There is no fixed version for Debian:13 ghostscript.
References
low severity
- Vulnerable module: gnutls28/libgnutls30t64
- Introduced through: gnutls28/libgnutls30t64@3.8.9-3
- Fixed in: 3.8.9-3+deb13u1
Detailed paths
-
Introduced through: wordpress@latest › gnutls28/libgnutls30t64@3.8.9-3
NVD Description
This vulnerability has not been analyzed by NVD yet.
Remediation
Upgrade Debian:13 gnutls28 to version 3.8.9-3+deb13u1 or higher.
References
low severity
- Vulnerable module: imagemagick/imagemagick-7-common
- Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u3, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3 and others
- Fixed in: 8:7.1.1.43+dfsg1-1+deb13u4
Detailed paths
-
Introduced through: wordpress@latest › imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u3
-
Introduced through: wordpress@latest › imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3
-
Introduced through: wordpress@latest › imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u3
NVD Description
Note: Versions mentioned in the description apply only to the upstream imagemagick package and not the imagemagick package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
ImageMagick is a software suite to create, edit, compose, or convert bitmap images. In versions 7.1.2-9 and prior, the TIM (PSX TIM) image parser contains a critical integer overflow vulnerability in its ReadTIMImage function (coders/tim.c). The code reads width and height (16-bit values) from the file header and calculates image_size = 2 * width * height without checking for overflow. On 32-bit systems (or where size_t is 32-bit), this calculation can overflow if width and height are large (e.g., 65535), wrapping around to a small value. This results in a small heap allocation via AcquireQuantumMemory and later operations relying on the dimensions can trigger an out of bounds read. This issue is fixed in version 7.1.2-10.
Remediation
Upgrade Debian:13 imagemagick to version 8:7.1.1.43+dfsg1-1+deb13u4 or higher.
References
low severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.21.3-5, krb5/libk5crypto3@1.21.3-5 and others
Detailed paths
-
Introduced through: wordpress@latest › krb5/libgssapi-krb5-2@1.21.3-5
-
Introduced through: wordpress@latest › krb5/libk5crypto3@1.21.3-5
-
Introduced through: wordpress@latest › krb5/libkrb5-3@1.21.3-5
-
Introduced through: wordpress@latest › krb5/libkrb5support0@1.21.3-5
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:13 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:13 krb5.
References
low severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.21.3-5, krb5/libk5crypto3@1.21.3-5 and others
Detailed paths
-
Introduced through: wordpress@latest › krb5/libgssapi-krb5-2@1.21.3-5
-
Introduced through: wordpress@latest › krb5/libk5crypto3@1.21.3-5
-
Introduced through: wordpress@latest › krb5/libkrb5-3@1.21.3-5
-
Introduced through: wordpress@latest › krb5/libkrb5support0@1.21.3-5
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:13 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:13 krb5.
References
low severity
- Vulnerable module: lcms2/liblcms2-2
- Introduced through: lcms2/liblcms2-2@2.16-2
Detailed paths
-
Introduced through: wordpress@latest › lcms2/liblcms2-2@2.16-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream lcms2 package and not the lcms2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A heap buffer overflow vulnerability has been identified in thesmooth2() in cmsgamma.c in lcms2-2.16 which allows a remote attacker to cause a denial of service. NOTE: the Supplier disputes this because "this is not exploitable as this function is never called on normal color management, is there only as a helper for low-level programming and investigation."
Remediation
There is no fixed version for Debian:13 lcms2.
References
low severity
- Vulnerable module: libde265/libde265-0
- Introduced through: libde265/libde265-0@1.0.15-1+b3
Detailed paths
-
Introduced through: wordpress@latest › libde265/libde265-0@1.0.15-1+b3
NVD Description
Note: Versions mentioned in the description apply only to the upstream libde265 package and not the libde265 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
Heap Buffer Overflow vulnerability in Libde265 v1.0.15 allows attackers to crash the application via crafted payload to display444as420 function at sdl.cc
Remediation
There is no fixed version for Debian:13 libde265.
References
low severity
- Vulnerable module: libde265/libde265-0
- Introduced through: libde265/libde265-0@1.0.15-1+b3
Detailed paths
-
Introduced through: wordpress@latest › libde265/libde265-0@1.0.15-1+b3
NVD Description
Note: Versions mentioned in the description apply only to the upstream libde265 package and not the libde265 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
Heap Buffer Overflow vulnerability in Libde265 v1.0.15 allows attackers to crash the application via crafted payload to __interceptor_memcpy function.
Remediation
There is no fixed version for Debian:13 libde265.
References
low severity
new
- Vulnerable module: libheif/libheif-plugin-dav1d
- Introduced through: libheif/libheif-plugin-dav1d@1.19.8-1, libheif/libheif-plugin-libde265@1.19.8-1 and others
Detailed paths
-
Introduced through: wordpress@latest › libheif/libheif-plugin-dav1d@1.19.8-1
-
Introduced through: wordpress@latest › libheif/libheif-plugin-libde265@1.19.8-1
-
Introduced through: wordpress@latest › libheif/libheif1@1.19.8-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libheif package and not the libheif package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
libheif is an HEIF and AVIF file format decoder and encoder. Prior to version 1.21.0, a crafted HEIF that exercises the overlay image item path triggers a heap buffer over-read in HeifPixelImage::overlay(). The function computes a negative row length (likely from an unclipped overlay rectangle or invalid offsets), which then underflows when converted to size_t and is passed to memcpy, causing a very large read past the end of the source plane and a crash. Version 1.21.0 contains a patch. As a workaround, avoid decoding images using iovl overlay boxes.
Remediation
There is no fixed version for Debian:13 libheif.
References
low severity
new
- Vulnerable module: libtasn1-6
- Introduced through: libtasn1-6@4.20.0-2
Detailed paths
-
Introduced through: wordpress@latest › libtasn1-6@4.20.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:13 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:13 libtasn1-6.
References
low severity
- Vulnerable module: openjpeg2/libopenjp2-7
- Introduced through: openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u1
Detailed paths
-
Introduced through: wordpress@latest › openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openjpeg2 package and not the openjpeg2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A vulnerability was found in OpenJPEG similar to CVE-2019-6988. This flaw allows an attacker to bypass existing protections and cause an application crash through a maliciously crafted file.
Remediation
There is no fixed version for Debian:13 openjpeg2.
References
low severity
- Vulnerable module: openjpeg2/libopenjp2-7
- Introduced through: openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u1
Detailed paths
-
Introduced through: wordpress@latest › openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openjpeg2 package and not the openjpeg2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A flaw was found in OpenJPEG. A resource exhaustion can occur in the opj_t1_decode_cblks function in tcd.c through a crafted image file, causing a denial of service.
Remediation
There is no fixed version for Debian:13 openjpeg2.
References
low severity
- Vulnerable module: openjpeg2/libopenjp2-7
- Introduced through: openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u1
Detailed paths
-
Introduced through: wordpress@latest › openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openjpeg2 package and not the openjpeg2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A flaw was found in OpenJPEG. Maliciously constructed pictures can cause the program to enter a large loop and continuously print warning messages on the terminal.
Remediation
There is no fixed version for Debian:13 openjpeg2.
References
low severity
new
- Vulnerable module: openldap/libldap2
- Introduced through: openldap/libldap2@2.6.10+dfsg-1
Detailed paths
-
Introduced through: wordpress@latest › openldap/libldap2@2.6.10+dfsg-1
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:13 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:13 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: shadow/login.defs
- Introduced through: shadow/login.defs@1:4.17.4-2 and shadow/passwd@1:4.17.4-2
Detailed paths
-
Introduced through: wordpress@latest › shadow/login.defs@1:4.17.4-2
-
Introduced through: wordpress@latest › shadow/passwd@1:4.17.4-2
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:13 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:13 shadow.
References
low severity
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.46.1-7
Detailed paths
-
Introduced through: wordpress@latest › sqlite3/libsqlite3-0@3.46.1-7
NVD Description
Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
An integer overflow exists in the FTS5 https://sqlite.org/fts5.html extension. It occurs when the size of an array of tombstone pointers is calculated and truncated into a 32-bit integer. A pointer to partially controlled data can then be written out of bounds.
Remediation
There is no fixed version for Debian:13 sqlite3.