Vulnerabilities

285 via 1013 paths

Dependencies

255

Source

Group 6 Copy Created with Sketch. Docker

Target OS

debian:13
Test your Docker Hub image against our market leading vulnerability database Sign up for free
Severity
  • 5
  • 4
  • 6
  • 270
Status
  • 285
  • 0
  • 0

critical severity

Improper Validation of Array Index

  • Vulnerable module: libraw/libraw23t64
  • Introduced through: libraw/libraw23t64@0.21.4-2

Detailed paths

  • Introduced through: wordpress@apache 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.

A heap-based buffer overflow vulnerability exists in the lossless_jpeg_load_raw functionality of LibRaw Commit 0b56545 and Commit d20315b. A specially crafted malicious file can lead to a heap buffer overflow. An attacker can provide a malicious file to trigger this vulnerability.

Remediation

There is no fixed version for Debian:13 libraw.

References

critical severity

Integer Overflow or Wraparound

  • Vulnerable module: libraw/libraw23t64
  • Introduced through: libraw/libraw23t64@0.21.4-2

Detailed paths

  • Introduced through: wordpress@apache 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.

A heap-based buffer overflow vulnerability exists in the x3f_thumb_loader functionality of LibRaw Commit d20315b. A specially crafted malicious file can lead to a heap buffer overflow. An attacker can provide a malicious file to trigger this vulnerability.

Remediation

There is no fixed version for Debian:13 libraw.

References

critical severity

Integer Overflow or Wraparound

  • Vulnerable module: libraw/libraw23t64
  • Introduced through: libraw/libraw23t64@0.21.4-2

Detailed paths

  • Introduced through: wordpress@apache 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.

An integer overflow vulnerability exists in the uncompressed_fp_dng_load_raw functionality of LibRaw Commit 8dc68e2. A specially crafted malicious file can lead to a heap buffer overflow. An attacker can provide a malicious file to trigger this vulnerability.

Remediation

There is no fixed version for Debian:13 libraw.

References

critical severity

Integer Overflow or Wraparound

  • Vulnerable module: libraw/libraw23t64
  • Introduced through: libraw/libraw23t64@0.21.4-2

Detailed paths

  • Introduced through: wordpress@apache 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.

A heap-based buffer overflow vulnerability exists in the x3f_load_huffman functionality of LibRaw Commit d20315b. A specially crafted malicious file can lead to a heap buffer overflow. An attacker can provide a malicious file to trigger this vulnerability.

Remediation

There is no fixed version for Debian:13 libraw.

References

critical severity

Integer Overflow or Wraparound

  • Vulnerable module: libraw/libraw23t64
  • Introduced through: libraw/libraw23t64@0.21.4-2

Detailed paths

  • Introduced through: wordpress@apache 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.

An integer overflow vulnerability exists in the deflate_dng_load_raw functionality of LibRaw Commit 8dc68e2. A specially crafted malicious file can lead to a heap buffer overflow. An attacker can provide a malicious file to trigger this vulnerability.

Remediation

There is no fixed version for Debian:13 libraw.

References

high severity
new

Out-of-bounds Read

  • Vulnerable module: libheif/libheif-plugin-aomenc
  • Introduced through: libheif/libheif-plugin-aomenc@1.19.8-1, libheif/libheif-plugin-dav1d@1.19.8-1 and others

Detailed paths

  • Introduced through: wordpress@apache libheif/libheif-plugin-aomenc@1.19.8-1
  • Introduced through: wordpress@apache libheif/libheif-plugin-dav1d@1.19.8-1
  • Introduced through: wordpress@apache libheif/libheif-plugin-libde265@1.19.8-1
  • Introduced through: wordpress@apache libheif/libheif-plugin-x265@1.19.8-1
  • Introduced through: wordpress@apache 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 a HEIF and AVIF file format decoder and encoder. In versions 1.21.2 and prior, a crafted HEIF sequence file where the saiz box declares more samples than actually exist in the track's chunk table causes a heap-buffer-overflow (out-of-bounds read) in the SampleAuxInfoReader constructor. The SampleAuxInfoReader constructor iterates over saiz->get_num_samples() samples but doesn't validate that this count is consistent with the number of chunks in the chunks vector. When saiz declares more samples than the chunks cover, the loop increments current_chunk past chunks.size(), causing an out-of-bounds read on the chunks vector. The vulnerability is triggered during file parsing (heif_context_read_from_file) without any additional user interaction. Any application using libheif to open untrusted HEIF files is affected. This issue has been fixed in version 1.22.0.

Remediation

There is no fixed version for Debian:13 libheif.

References

high severity

Improper Input Validation

  • Vulnerable module: cups/libcups2t64
  • Introduced through: cups/libcups2t64@2.4.10-3+deb13u2

Detailed paths

  • Introduced through: wordpress@apache 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. In versions 2.4.16 and prior, in a network-exposed cupsd with a shared target queue, an unauthorized client can send a Print-Job to that shared PostScript queue without authentication. The server accepts a page-border value supplied as textWithoutLanguage, preserves an embedded newline through option escaping and reparse, and then reparses the resulting second-line PPD: text as a trusted scheduler control record. A follow-up raw print job can therefore make the server execute an attacker-chosen existing binary such as /usr/bin/vim as lp. At time of publication, there are no publicly available patches.

Remediation

There is no fixed version for Debian:13 cups.

References

high severity
new

Algorithmic Complexity

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.7.1-2

Detailed paths

  • Introduced through: wordpress@apache 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 before 2.8.1, the computational complexity of attribute name collision checks allows a denial of service via moderately sized crafted XML input.

Remediation

There is no fixed version for Debian:13 expat.

References

high severity

Heap-based Buffer Overflow

  • Vulnerable module: libde265/libde265-0
  • Introduced through: libde265/libde265-0@1.0.15-1+b3

Detailed paths

  • Introduced through: wordpress@apache 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.

libde265 is an open source implementation of the h.265 video codec. Prior to version 1.0.17, a malformed H.265 PPS NAL unit causes a segmentation fault in pic_parameter_set::set_derived_values(). This issue has been patched in version 1.0.17.

Remediation

There is no fixed version for Debian:13 libde265.

References

medium severity
new

Out-of-bounds Read

  • Vulnerable module: libheif/libheif-plugin-aomenc
  • Introduced through: libheif/libheif-plugin-aomenc@1.19.8-1, libheif/libheif-plugin-dav1d@1.19.8-1 and others

Detailed paths

  • Introduced through: wordpress@apache libheif/libheif-plugin-aomenc@1.19.8-1
  • Introduced through: wordpress@apache libheif/libheif-plugin-dav1d@1.19.8-1
  • Introduced through: wordpress@apache libheif/libheif-plugin-libde265@1.19.8-1
  • Introduced through: wordpress@apache libheif/libheif-plugin-x265@1.19.8-1
  • Introduced through: wordpress@apache 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 a HEIF and AVIF file format decoder and encoder. In versions 1.21.2 and below, a crafted 792-byte HEIF sequence file with samples_per_chunk=0 in the stsc box causes an unsigned integer underflow in the Chunk constructor (m_last_sample = 0 + 0 - 1 = UINT32_MAX), mapping all samples to an empty chunk and resulting in a denial of service. When any sample is accessed, the library reads from index 0 of an empty std::vector, causing a guaranteed SEGV (null-page read). The file parses successfully without producing an error; the crash occurs on the first frame access. This issue has been fixed in version 1.22.0.

Remediation

There is no fixed version for Debian:13 libheif.

References

medium severity

Integer Underflow

  • Vulnerable module: cups/libcups2t64
  • Introduced through: cups/libcups2t64@2.4.10-3+deb13u2

Detailed paths

  • Introduced through: wordpress@apache 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. In versions 2.4.16 and prior, an integer underflow vulnerability in _ppdCreateFromIPP() (cups/ppd-cache.c) allows any unprivileged local user to crash the cupsd root process by supplying a negative job-password-supported IPP attribute. The bounds check only caps the upper bound, so a negative value passes validation, is cast to size_t (wrapping to ~2^64), and is used as the length argument to memset() on a 33-byte stack buffer. This causes an immediate SIGSEGV in the cupsd root process. Combined with systemd's Restart=on-failure, an attacker can repeat the crash for sustained denial of service.

Remediation

There is no fixed version for Debian:13 cups.

References

medium severity

Use After Free

  • Vulnerable module: cups/libcups2t64
  • Introduced through: cups/libcups2t64@2.4.10-3+deb13u2

Detailed paths

  • Introduced through: wordpress@apache 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. In versions 2.4.16 and prior, a use-after-free vulnerability exists in the CUPS scheduler (cupsd) when temporary printers are automatically deleted. cupsdDeleteTemporaryPrinters() in scheduler/printers.c calls cupsdDeletePrinter() without first expiring subscriptions that reference the printer, leaving cupsd_subscription_t.dest as a dangling pointer to freed heap memory. The dangling pointer is subsequently dereferenced at multiple code sites, causing a crash (denial of service) of the cupsd daemon. With heap grooming, this can be leveraged for code execution.

Remediation

There is no fixed version for Debian:13 cups.

References

medium severity
new

Use After Free

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.7.1-2

Detailed paths

  • Introduced through: wordpress@apache 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 before 2.8.2 lacks handler call depth tracking for calls to XML_GetBuffer, XML_Parse, XML_ParseBuffer, XML_ParserFree, or XML_ParserReset from within handlers in cases of a policy violation. Thus, a use-after-free can occur,

Remediation

There is no fixed version for Debian:13 expat.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: cups/libcups2t64
  • Introduced through: cups/libcups2t64@2.4.10-3+deb13u2

Detailed paths

  • Introduced through: wordpress@apache 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 2.4.17, a network-adjacent attacker can send a crafted SNMP response to the CUPS SNMP backend that causes an out-of-bounds read of up to 176 bytes past a stack buffer. The leaked memory is converted from UTF-16 to UTF-8 and stored as printer supply description strings, which are subsequently visible to authenticated users via IPP Get-Printer-Attributes responses and the CUPS web interface. This vulnerability is fixed in 2.4.17.

Remediation

There is no fixed version for Debian:13 cups.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: libde265/libde265-0
  • Introduced through: libde265/libde265-0@1.0.15-1+b3

Detailed paths

  • Introduced through: wordpress@apache 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.

libde265 is an open source implementation of the h.265 video codec. Prior to version 1.0.17, a crafted HEVC bitstream causes an out-of-bounds heap write confirmed by AddressSanitizer. The trigger is a stale ctb_info.log2unitSize after an SPS change where PicWidthInCtbsY and PicHeightInCtbsY stay constant but Log2CtbSizeY changes, causing set_SliceHeaderIndex to index past the allocated image metadata array and write 2 bytes past the end of a heap allocation. This issue has been patched in version 1.0.17.

Remediation

There is no fixed version for Debian:13 libde265.

References

low severity

Out-of-Bounds

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u3, glibc/libc-dev-bin@2.41-12+deb13u3 and others

Detailed paths

  • Introduced through: wordpress@apache glibc/libc-bin@2.41-12+deb13u3
  • Introduced through: wordpress@apache glibc/libc-dev-bin@2.41-12+deb13u3
  • Introduced through: wordpress@apache glibc/libc6@2.41-12+deb13u3
  • Introduced through: wordpress@apache glibc/libc6-dev@2.41-12+deb13u3

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

OS Command Injection

  • Vulnerable module: imagemagick/imagemagick-7-common
  • Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8 and others

Detailed paths

  • Introduced through: wordpress@apache imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8

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

low severity
new

CVE-2026-8376

  • Vulnerable module: perl
  • Introduced through: perl@5.40.1-6, perl/libperl5.40@5.40.1-6 and others

Detailed paths

  • Introduced through: wordpress@apache perl@5.40.1-6
  • Introduced through: wordpress@apache perl/libperl5.40@5.40.1-6
  • Introduced through: wordpress@apache perl/perl-base@5.40.1-6
  • Introduced through: wordpress@apache 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.

Perl versions through 5.43.10 have a heap buffer overflow when compiling regular expressions with a repeated fixed string on 32-bit builds.

Perl_study_chunk in regcomp_study.c checked the size of the joined substring buffer in characters rather than bytes. For a quantified fixed substring with a large minimum count, the byte length mincount * l could overflow SSize_t, producing an undersized SvGROW allocation; the subsequent copy writes past the end of the buffer.

A caller that compiles an attacker-controlled regular expression on a 32-bit perl build triggers a heap buffer overflow at compile time.

Remediation

There is no fixed version for Debian:13 perl.

References

low severity

CVE-2005-2541

  • Vulnerable module: tar
  • Introduced through: tar@1.35+dfsg-3.1

Detailed paths

  • Introduced through: wordpress@apache 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

low severity
new

CVE-2026-42496

  • Vulnerable module: perl
  • Introduced through: perl@5.40.1-6, perl/libperl5.40@5.40.1-6 and others

Detailed paths

  • Introduced through: wordpress@apache perl@5.40.1-6
  • Introduced through: wordpress@apache perl/libperl5.40@5.40.1-6
  • Introduced through: wordpress@apache perl/perl-base@5.40.1-6
  • Introduced through: wordpress@apache 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.

Archive::Tar versions before 3.08 for Perl extract symlinks with attacker controlled targets outside the extraction directory.

_make_special_file() passes the tar header's linkname to symlink() without validating it against absolute paths or .. segments. The secure-extract mode check that guards regular file extraction does not cover the symlink target.

A subsequent open through the extracted name reads or writes the attacker chosen path.

Remediation

There is no fixed version for Debian:13 perl.

References

low severity

Improper Input Validation

  • Vulnerable module: cups/libcups2t64
  • Introduced through: cups/libcups2t64@2.4.10-3+deb13u2

Detailed paths

  • Introduced through: wordpress@apache 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

CVE-2019-1010023

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u3, glibc/libc-dev-bin@2.41-12+deb13u3 and others

Detailed paths

  • Introduced through: wordpress@apache glibc/libc-bin@2.41-12+deb13u3
  • Introduced through: wordpress@apache glibc/libc-dev-bin@2.41-12+deb13u3
  • Introduced through: wordpress@apache glibc/libc6@2.41-12+deb13u3
  • Introduced through: wordpress@apache glibc/libc6-dev@2.41-12+deb13u3

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

low severity

Integer Overflow or Wraparound

  • Vulnerable module: openjpeg2/libopenjp2-7
  • Introduced through: openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u2

Detailed paths

  • Introduced through: wordpress@apache openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u2

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

low severity

Out-of-Bounds

  • Vulnerable module: openjpeg2/libopenjp2-7
  • Introduced through: openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u2

Detailed paths

  • Introduced through: wordpress@apache openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u2

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

low severity

Out-of-bounds Write

  • Vulnerable module: openjpeg2/libopenjp2-7
  • Introduced through: openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u2

Detailed paths

  • Introduced through: wordpress@apache openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u2

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

Heap-based Buffer Overflow

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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 was found in binutils. A heap-buffer-overflow vulnerability exists when processing a specially crafted XCOFF (Extended Common Object File Format) object file during linking. A local attacker could trick a user into processing this malicious file, which could lead to arbitrary code execution, allowing the attacker to run unauthorized commands, or cause a denial of service, making the system unavailable.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

low severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

low severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

low severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

low severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

low severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

low severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.7.1-2

Detailed paths

  • Introduced through: wordpress@apache 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 before 2.7.4, the doContent function does not properly determine the buffer size bufSize because there is no integer overflow check for tag buffer reallocation.

Remediation

There is no fixed version for Debian:13 expat.

References

low severity

Stack-based Buffer Overflow

  • 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@apache ncurses/libncursesw6@6.5+20250216-2
  • Introduced through: wordpress@apache ncurses/libtinfo6@6.5+20250216-2
  • Introduced through: wordpress@apache ncurses/ncurses-base@6.5+20250216-2
  • Introduced through: wordpress@apache 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.

The infocmp command-line tool in ncurses before 6.5-20251213 has a stack-based buffer overflow in analyze_string in progs/infocmp.c.

Remediation

There is no fixed version for Debian:13 ncurses.

References

low severity

Out-of-Bounds

  • Vulnerable module: tiff/libtiff6
  • Introduced through: tiff/libtiff6@4.7.0-3+deb13u2

Detailed paths

  • Introduced through: wordpress@apache tiff/libtiff6@4.7.0-3+deb13u2

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

low severity

Out-of-Bounds

  • Vulnerable module: tiff/libtiff6
  • Introduced through: tiff/libtiff6@4.7.0-3+deb13u2

Detailed paths

  • Introduced through: wordpress@apache tiff/libtiff6@4.7.0-3+deb13u2

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

low severity

Resource Exhaustion

  • Vulnerable module: apache2
  • Introduced through: apache2@2.4.67-1~deb13u2, apache2/apache2-bin@2.4.67-1~deb13u2 and others

Detailed paths

  • Introduced through: wordpress@apache apache2@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-bin@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-data@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-utils@2.4.67-1~deb13u2

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

low severity

CVE-2025-66864

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

CVE-2025-66866

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

CVE-2025-69649

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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.

GNU Binutils thru 2.46 readelf contains a null pointer dereference vulnerability when processing a crafted ELF binary with malformed header fields. During relocation processing, an invalid or null section pointer may be passed into display_relocations(), resulting in a segmentation fault (SIGSEGV) and abrupt termination. No evidence of memory corruption beyond the null pointer dereference, nor any possibility of code execution, was observed.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Double Free

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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.

GNU Binutils thru 2.46 readelf contains a double free vulnerability when processing a crafted ELF binary with malformed relocation data. During GOT relocation handling, dump_relocations may return early without initializing the all_relocations array. As a result, process_got_section_contents() may pass an uninitialized r_symbol pointer to free(), leading to a double free and terminating the program with SIGABRT. No evidence of exploitable memory corruption or code execution was observed; the impact is limited to denial of service. NOTE: this is disputed by third parties because the observed behavior occurred only in pre-release code and did not affect any tagged version.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Cleartext Transmission of Sensitive Information

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u3 and curl/libcurl4t64@8.14.1-2+deb13u3

Detailed paths

  • Introduced through: wordpress@apache curl@8.14.1-2+deb13u3
  • Introduced through: wordpress@apache curl/libcurl4t64@8.14.1-2+deb13u3

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.

Using libcurl, when a custom Host: header is first set for an HTTP request and a second request is subsequently done using the same easy handle but without the custom Host: header set, the second request would use stale information and pass on cookies meant for the first host in the second request. Leak them.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

Server-Side Request Forgery (SSRF)

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u3 and curl/libcurl4t64@8.14.1-2+deb13u3

Detailed paths

  • Introduced through: wordpress@apache curl@8.14.1-2+deb13u3
  • Introduced through: wordpress@apache curl/libcurl4t64@8.14.1-2+deb13u3

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.

libcurl might in some circumstances reuse the wrong connection for SMB(S) transfers.

libcurl features a pool of recent connections so that subsequent requests can reuse an existing connection to avoid overhead.

When reusing a connection a range of criteria must be met. Due to a logical error in the code, a network transfer operation that was requested by an application could wrongfully reuse an existing SMB connection to the same server that was using a different 'share' than the new subsequent transfer should.

This could in unlucky situations lead to the download of the wrong file or the upload of a file to the wrong place. When this happens, the same credentials are used and the server name is the same.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

Uncontrolled Recursion

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u3, glibc/libc-dev-bin@2.41-12+deb13u3 and others

Detailed paths

  • Introduced through: wordpress@apache glibc/libc-bin@2.41-12+deb13u3
  • Introduced through: wordpress@apache glibc/libc-dev-bin@2.41-12+deb13u3
  • Introduced through: wordpress@apache glibc/libc6@2.41-12+deb13u3
  • Introduced through: wordpress@apache glibc/libc6-dev@2.41-12+deb13u3

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

low severity

Uncontrolled Recursion

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u3, glibc/libc-dev-bin@2.41-12+deb13u3 and others

Detailed paths

  • Introduced through: wordpress@apache glibc/libc-bin@2.41-12+deb13u3
  • Introduced through: wordpress@apache glibc/libc-dev-bin@2.41-12+deb13u3
  • Introduced through: wordpress@apache glibc/libc6@2.41-12+deb13u3
  • Introduced through: wordpress@apache glibc/libc6-dev@2.41-12+deb13u3

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

low severity

Out-of-bounds Read

  • Vulnerable module: jansson/libjansson4
  • Introduced through: jansson/libjansson4@2.14-2+b3

Detailed paths

  • Introduced through: wordpress@apache 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

Integer Overflow or Wraparound

  • 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@apache krb5/libgssapi-krb5-2@1.21.3-5
  • Introduced through: wordpress@apache krb5/libk5crypto3@1.21.3-5
  • Introduced through: wordpress@apache krb5/libkrb5-3@1.21.3-5
  • Introduced through: wordpress@apache 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

low severity

NULL Pointer Dereference

  • Vulnerable module: openjpeg2/libopenjp2-7
  • Introduced through: openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u2

Detailed paths

  • Introduced through: wordpress@apache openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u2

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

NULL Pointer Dereference

  • Vulnerable module: openjpeg2/libopenjp2-7
  • Introduced through: openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u2

Detailed paths

  • Introduced through: wordpress@apache openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u2

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

Cryptographic Issues

  • Vulnerable module: openldap/libldap2
  • Introduced through: openldap/libldap2@2.6.10+dfsg-1

Detailed paths

  • Introduced through: wordpress@apache 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

low severity

Out-of-Bounds

  • Vulnerable module: openldap/libldap2
  • Introduced through: openldap/libldap2@2.6.10+dfsg-1

Detailed paths

  • Introduced through: wordpress@apache 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

low severity

Double Free

  • Vulnerable module: patch
  • Introduced through: patch@2.8-2

Detailed paths

  • Introduced through: wordpress@apache 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

low severity

NULL Pointer Dereference

  • Vulnerable module: patch
  • Introduced through: patch@2.8-2

Detailed paths

  • Introduced through: wordpress@apache 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

low severity
new

CVE-2026-42497

  • Vulnerable module: perl
  • Introduced through: perl@5.40.1-6, perl/libperl5.40@5.40.1-6 and others

Detailed paths

  • Introduced through: wordpress@apache perl@5.40.1-6
  • Introduced through: wordpress@apache perl/libperl5.40@5.40.1-6
  • Introduced through: wordpress@apache perl/perl-base@5.40.1-6
  • Introduced through: wordpress@apache 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.

Archive::Tar versions before 3.08 for Perl extract hardlinks to attacker controlled paths outside the extraction directory.

_make_special_file() passes the tar header's linkname to link() without validating it against absolute paths or .. segments, creating a hardlink that shares the victim file's inode.

A subsequent write through the extracted name modifies the victim file, and the post-extraction chmod, chown, and utime block in _extract_file() (guarded only against symlinks via -l) applies the tar header's mode, owner, and timestamps to the shared inode during extraction alone.

Remediation

There is no fixed version for Debian:13 perl.

References

low severity
new

CVE-2026-9538

  • Vulnerable module: perl
  • Introduced through: perl@5.40.1-6, perl/libperl5.40@5.40.1-6 and others

Detailed paths

  • Introduced through: wordpress@apache perl@5.40.1-6
  • Introduced through: wordpress@apache perl/libperl5.40@5.40.1-6
  • Introduced through: wordpress@apache perl/perl-base@5.40.1-6
  • Introduced through: wordpress@apache 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.

Archive::Tar versions before 3.10 for Perl allow memory exhaustion via attacker controlled entry size field in tar header.

_read_tar() reads each entry's payload with $handle->read($$data, $block), where $block is derived from the entry's 12-byte size field in the tar header with no upper bound on that value.

A crafted header declaring a multi-gigabyte size causes Perl to allocate a scalar of that size.

Remediation

There is no fixed version for Debian:13 perl.

References

low severity

Missing Release of Resource after Effective Lifetime

  • Vulnerable module: tiff/libtiff6
  • Introduced through: tiff/libtiff6@4.7.0-3+deb13u2

Detailed paths

  • Introduced through: wordpress@apache tiff/libtiff6@4.7.0-3+deb13u2

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

low severity

Numeric Errors

  • Vulnerable module: libssh2/libssh2-1t64
  • Introduced through: libssh2/libssh2-1t64@1.11.1-1

Detailed paths

  • Introduced through: wordpress@apache libssh2/libssh2-1t64@1.11.1-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libssh2 package and not the libssh2 package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

A security vulnerability has been detected in libssh2 up to 1.11.1. The impacted element is the function userauth_password of the file src/userauth.c. Such manipulation of the argument username_len/password_len leads to integer overflow. The attack may be launched remotely. The name of the patch is 256d04b60d80bf1190e96b0ad1e91b2174d744b1. A patch should be applied to remediate this issue.

Remediation

There is no fixed version for Debian:13 libssh2.

References

low severity

CVE-2008-1687

  • Vulnerable module: m4
  • Introduced through: m4@1.4.19-8

Detailed paths

  • Introduced through: wordpress@apache 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

low severity

CVE-2008-1688

  • Vulnerable module: m4
  • Introduced through: m4@1.4.19-8

Detailed paths

  • Introduced through: wordpress@apache 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

low severity

Out-of-Bounds

  • Vulnerable module: tiff/libtiff6
  • Introduced through: tiff/libtiff6@4.7.0-3+deb13u2

Detailed paths

  • Introduced through: wordpress@apache tiff/libtiff6@4.7.0-3+deb13u2

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 up to v4.7.1 was discovered to contain a stack overflow via the readSeparateStripsIntoBuffer function.

Remediation

There is no fixed version for Debian:13 tiff.

References

low severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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 was found in GNU Binutils. This vulnerability, a heap-based buffer overflow, specifically an out-of-bounds read, exists in the bfd linker component. An attacker could exploit this by convincing a user to process a specially crafted malicious XCOFF object file. Successful exploitation may lead to the disclosure of sensitive information or cause the application to crash, resulting in an application level denial of service.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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 was found in GNU Binutils. This heap-based buffer overflow vulnerability, specifically an out-of-bounds read in the bfd linker, allows an attacker to gain access to sensitive information. By convincing a user to process a specially crafted XCOFF object file, an attacker can trigger this flaw, potentially leading to information disclosure or an application level denial of service.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Out-of-bounds Read

  • Vulnerable module: libheif/libheif-plugin-aomenc
  • Introduced through: libheif/libheif-plugin-aomenc@1.19.8-1, libheif/libheif-plugin-dav1d@1.19.8-1 and others

Detailed paths

  • Introduced through: wordpress@apache libheif/libheif-plugin-aomenc@1.19.8-1
  • Introduced through: wordpress@apache libheif/libheif-plugin-dav1d@1.19.8-1
  • Introduced through: wordpress@apache libheif/libheif-plugin-libde265@1.19.8-1
  • Introduced through: wordpress@apache libheif/libheif-plugin-x265@1.19.8-1
  • Introduced through: wordpress@apache 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

Buffer Underflow

  • Vulnerable module: cups/libcups2t64
  • Introduced through: cups/libcups2t64@2.4.10-3+deb13u2

Detailed paths

  • Introduced through: wordpress@apache 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

low severity

Uncontrolled Recursion

  • 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@apache avahi/libavahi-client3@0.8-16
  • Introduced through: wordpress@apache avahi/libavahi-common-data@0.8-16
  • Introduced through: wordpress@apache 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 0.9rc2 and below, avahi-daemon can be crashed via a segmentation fault by sending an unsolicited mDNS response containing a recursive CNAME record, where the alias and canonical name point to the same domain (e.g., "h.local" as a CNAME for "h.local"). This causes unbounded recursion in the lookup_handle_cname function, leading to stack exhaustion. The vulnerability affects record browsers where AVAHI_LOOKUP_USE_MULTICAST is set explicitly, which includes record browsers created by resolvers used by nss-mdns. This issue is patched in commit 78eab31128479f06e30beb8c1cbf99dd921e2524.

Remediation

There is no fixed version for Debian:13 avahi.

References

low severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

low severity

Out-of-bounds Write

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

Insufficient Session Expiration

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u3 and curl/libcurl4t64@8.14.1-2+deb13u3

Detailed paths

  • Introduced through: wordpress@apache curl@8.14.1-2+deb13u3
  • Introduced through: wordpress@apache curl/libcurl4t64@8.14.1-2+deb13u3

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.

libcurl might in some circumstances reuse the wrong connection when asked to do an authenticated HTTP(S) request after a Negotiate-authenticated one, when both use the same host.

libcurl features a pool of recent connections so that subsequent requests can reuse an existing connection to avoid overhead.

When reusing a connection a range of criteria must be met. Due to a logical error in the code, a request that was issued by an application could wrongfully reuse an existing connection to the same server that was authenticated using different credentials.

An application that first uses Negotiate authentication to a server with user1:password1 and then does another operation to the same server asking for any authentication method but for user2:password2 (while the previous connection is still alive) - the second request gets confused and wrongly reuses the same connection and sends the new request over that connection thinking it uses a mix of user1's and user2's credentials when it is in fact still using the connection authenticated for user1...

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

Missing Release of Resource after Effective Lifetime

  • Vulnerable module: imagemagick/imagemagick-7-common
  • Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8 and others

Detailed paths

  • Introduced through: wordpress@apache imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8

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

Missing Release of Resource after Effective Lifetime

  • Vulnerable module: imagemagick/imagemagick-7-common
  • Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8 and others

Detailed paths

  • Introduced through: wordpress@apache imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8

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

Resource Exhaustion

  • Vulnerable module: imagemagick/imagemagick-7-common
  • Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8 and others

Detailed paths

  • Introduced through: wordpress@apache imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8

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

low severity

CVE-2023-46361

  • Vulnerable module: jbig2dec/libjbig2dec0
  • Introduced through: jbig2dec/libjbig2dec0@0.20-1+b3

Detailed paths

  • Introduced through: wordpress@apache 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

Out-of-Bounds

  • Vulnerable module: jbigkit/libjbig0
  • Introduced through: jbigkit/libjbig0@2.1-6.1+b2

Detailed paths

  • Introduced through: wordpress@apache 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

low severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: openjpeg2/libopenjp2-7
  • Introduced through: openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u2

Detailed paths

  • Introduced through: wordpress@apache openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u2

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

NULL Pointer Dereference

  • Vulnerable module: openjpeg2/libopenjp2-7
  • Introduced through: openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u2

Detailed paths

  • Introduced through: wordpress@apache openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u2

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

NULL Pointer Dereference

  • Vulnerable module: openjpeg2/libopenjp2-7
  • Introduced through: openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u2

Detailed paths

  • Introduced through: wordpress@apache openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u2

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

NULL Pointer Dereference

  • Vulnerable module: openjpeg2/libopenjp2-7
  • Introduced through: openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u2

Detailed paths

  • Introduced through: wordpress@apache openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u2

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

Out-of-Bounds

  • Vulnerable module: openjpeg2/libopenjp2-7
  • Introduced through: openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u2

Detailed paths

  • Introduced through: wordpress@apache openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u2

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

Improper Resource Shutdown or Release

  • Vulnerable module: tiff/libtiff6
  • Introduced through: tiff/libtiff6@4.7.0-3+deb13u2

Detailed paths

  • Introduced through: wordpress@apache tiff/libtiff6@4.7.0-3+deb13u2

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

low severity

NULL Pointer Dereference

  • Vulnerable module: tiff/libtiff6
  • Introduced through: tiff/libtiff6@4.7.0-3+deb13u2

Detailed paths

  • Introduced through: wordpress@apache tiff/libtiff6@4.7.0-3+deb13u2

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

low severity

Incorrect Authorization

  • Vulnerable module: cups/libcups2t64
  • Introduced through: cups/libcups2t64@2.4.10-3+deb13u2

Detailed paths

  • Introduced through: wordpress@apache 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. In versions 2.4.16 and prior, CUPS daemon (cupsd) contains an authorization bypass vulnerability due to case-insensitive username comparison during authorization checks. The vulnerability allows an unprivileged user to gain unauthorized access to restricted operations by using a user with a username that differs only in case from an authorized user. At time of publication, there are no publicly available patches.

Remediation

There is no fixed version for Debian:13 cups.

References

low severity

Arbitrary Code Injection

  • Vulnerable module: apache2
  • Introduced through: apache2@2.4.67-1~deb13u2, apache2/apache2-bin@2.4.67-1~deb13u2 and others

Detailed paths

  • Introduced through: wordpress@apache apache2@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-bin@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-data@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-utils@2.4.67-1~deb13u2

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

low severity

Memory Leak

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u2

Detailed paths

  • Introduced through: wordpress@apache 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 flaw was identified in the interactive shell of the xmllint utility, part of the libxml2 project, where memory allocated for user input is not properly released under certain conditions. When a user submits input consisting only of whitespace, the program skips command execution but fails to free the allocated buffer. Repeating this action causes memory to continuously accumulate. Over time, this can exhaust system memory and terminate the xmllint process, creating a denial-of-service condition on the local system.

Remediation

There is no fixed version for Debian:13 libxml2.

References

low severity

Access Restriction Bypass

  • 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@apache shadow/login.defs@1:4.17.4-2
  • Introduced through: wordpress@apache 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

low severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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 was found in the GNU Binutils BFD library, a widely used component for handling binary files such as object files and executables. The issue occurs when processing specially crafted XCOFF object files, where a relocation type value is not properly validated before being used. This can cause the program to read memory outside of intended bounds. As a result, affected tools may crash or expose unintended memory contents, leading to denial-of-service or limited information disclosure risks.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Out-of-bounds Read

  • 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@apache util-linux@2.41-5
  • Introduced through: wordpress@apache util-linux/bsdutils@1:2.41-5
  • Introduced through: wordpress@apache util-linux/libblkid1@2.41-5
  • Introduced through: wordpress@apache util-linux/liblastlog2-2@2.41-5
  • Introduced through: wordpress@apache util-linux/libmount1@2.41-5
  • Introduced through: wordpress@apache util-linux/libsmartcols1@2.41-5
  • Introduced through: wordpress@apache util-linux/libuuid1@2.41-5
  • Introduced through: wordpress@apache util-linux/login@1:4.16.0-2+really2.41-5
  • Introduced through: wordpress@apache 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

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

low severity

Uncontrolled Recursion

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u2

Detailed paths

  • Introduced through: wordpress@apache 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 flaw was found in libxml2, an XML parsing library. This uncontrolled recursion vulnerability occurs in the xmlCatalogXMLResolveURI function when an XML catalog contains a delegate URI entry that references itself. A remote attacker could exploit this configuration-dependent issue by providing a specially crafted XML catalog, leading to infinite recursion and call stack exhaustion. This ultimately results in a segmentation fault, causing a Denial of Service (DoS) by crashing affected applications.

Remediation

There is no fixed version for Debian:13 libxml2.

References

low severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

low severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

CVE-2025-69651

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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.

GNU Binutils thru 2.46 readelf contains a vulnerability that leads to an invalid pointer free when processing a crafted ELF binary with malformed relocation or symbol data. If dump_relocations returns early due to parsing errors, the internal all_relocations array may remain partially uninitialized. Later, process_got_section_contents() may attempt to free an invalid r_symbol pointer, triggering memory corruption checks in glibc and causing the program to terminate with SIGABRT. No evidence of further memory corruption or code execution was observed; the impact is limited to denial of service. NOTE: this is disputed by third parties because the observed behavior occurred only in pre-release code and did not affect any tagged version.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Memory Leak

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

low severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

low severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

low severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

low severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

low severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

low severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

low severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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 a manipulation can lead to out-of-bounds read. The attack can only be executed locally. The exploit has been made available to the public and could be used for attacks. This patch is called 16357. It is best practice to apply a patch to resolve this issue.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Out-of-bounds Write

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

Resource Exhaustion

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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 was found in the readelf utility of the binutils package. A local attacker could exploit two Denial of Service (DoS) vulnerabilities by providing a specially crafted Executable and Linkable Format (ELF) file. One vulnerability, a resource exhaustion (CWE-400), can lead to an out-of-memory condition. The other, a null pointer dereference (CWE-476), can cause a segmentation fault. Both issues can result in the readelf utility becoming unresponsive or crashing, leading to a denial of service.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Unchecked Return Value

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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 a manipulation results in unchecked return value. The attack needs to be approached locally. The exploit has been released to the public and may be used for attacks.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Uncontrolled Recursion

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

Resource Exhaustion

  • Vulnerable module: cups/libcups2t64
  • Introduced through: cups/libcups2t64@2.4.10-3+deb13u2

Detailed paths

  • Introduced through: wordpress@apache 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

low severity

Algorithmic Complexity

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.7.1-2

Detailed paths

  • Introduced through: wordpress@apache 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

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.7.1-2

Detailed paths

  • Introduced through: wordpress@apache 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 before 2.7.5 allows an infinite loop while parsing DTD content.

Remediation

There is no fixed version for Debian:13 expat.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.7.1-2

Detailed paths

  • Introduced through: wordpress@apache 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 before 2.7.5 allows a NULL pointer dereference with empty external parameter entity content.

Remediation

There is no fixed version for Debian:13 expat.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.7.1-2

Detailed paths

  • Introduced through: wordpress@apache 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 before 2.7.5 allows a NULL pointer dereference in the function setContext on retry after an earlier ouf-of-memory condition.

Remediation

There is no fixed version for Debian:13 expat.

References

low severity

Integer Overflow or Wraparound

  • 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@apache ghostscript@10.05.1~dfsg-1+deb13u1
  • Introduced through: wordpress@apache ghostscript/libgs-common@10.05.1~dfsg-1+deb13u1
  • Introduced through: wordpress@apache ghostscript/libgs10@10.05.1~dfsg-1+deb13u1
  • Introduced through: wordpress@apache 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

CVE-2005-0406

  • Vulnerable module: imagemagick/imagemagick-7-common
  • Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8 and others

Detailed paths

  • Introduced through: wordpress@apache imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8

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

Out-of-Bounds

  • Vulnerable module: imagemagick/imagemagick-7-common
  • Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8 and others

Detailed paths

  • Introduced through: wordpress@apache imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8

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

low severity

Out-of-bounds Read

  • Vulnerable module: imagemagick/imagemagick-7-common
  • Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8 and others

Detailed paths

  • Introduced through: wordpress@apache imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8

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

low severity

Buffer Overflow

  • Vulnerable module: libpng1.6/libpng16-16t64
  • Introduced through: libpng1.6/libpng16-16t64@1.6.48-1+deb13u5

Detailed paths

  • Introduced through: wordpress@apache libpng1.6/libpng16-16t64@1.6.48-1+deb13u5

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

NULL Pointer Dereference

  • Vulnerable module: libraw/libraw23t64
  • Introduced through: libraw/libraw23t64@0.21.4-2

Detailed paths

  • Introduced through: wordpress@apache 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

low severity

Release of Invalid Pointer or Reference

  • Vulnerable module: patch
  • Introduced through: patch@2.8-2

Detailed paths

  • Introduced through: wordpress@apache 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

Uncontrolled Recursion

  • Vulnerable module: re2c
  • Introduced through: re2c@4.1-1

Detailed paths

  • Introduced through: wordpress@apache 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

Unrestricted Upload of File with Dangerous Type

  • Vulnerable module: tar
  • Introduced through: tar@1.35+dfsg-3.1

Detailed paths

  • Introduced through: wordpress@apache 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.

A flaw was found in tar. A remote attacker could exploit this vulnerability by crafting a malicious archive, leading to hidden file injection with fully attacker-controlled content. This bypasses pre-extraction inspection mechanisms, potentially allowing an attacker to introduce malicious files onto a system without detection.

Remediation

There is no fixed version for Debian:13 tar.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: tiff/libtiff6
  • Introduced through: tiff/libtiff6@4.7.0-3+deb13u2

Detailed paths

  • Introduced through: wordpress@apache tiff/libtiff6@4.7.0-3+deb13u2

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 up to v4.7.1 was discovered to contain a NULL pointer dereference via the component libtiff/tif_open.c.

Remediation

There is no fixed version for Debian:13 tiff.

References

low severity

Information Exposure

  • 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@apache util-linux@2.41-5
  • Introduced through: wordpress@apache util-linux/bsdutils@1:2.41-5
  • Introduced through: wordpress@apache util-linux/libblkid1@2.41-5
  • Introduced through: wordpress@apache util-linux/liblastlog2-2@2.41-5
  • Introduced through: wordpress@apache util-linux/libmount1@2.41-5
  • Introduced through: wordpress@apache util-linux/libsmartcols1@2.41-5
  • Introduced through: wordpress@apache util-linux/libuuid1@2.41-5
  • Introduced through: wordpress@apache util-linux/login@1:4.16.0-2+really2.41-5
  • Introduced through: wordpress@apache 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

low severity

Improper Validation of Specified Quantity in Input

  • Vulnerable module: zlib/zlib1g
  • Introduced through: zlib/zlib1g@1:1.3.dfsg+really1.3.1-1+b1

Detailed paths

  • Introduced through: wordpress@apache zlib/zlib1g@1:1.3.dfsg+really1.3.1-1+b1

NVD Description

Note: Versions mentioned in the description apply only to the upstream zlib package and not the zlib package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

zlib before 1.3.2 allows CPU consumption via crc32_combine64 and crc32_combine_gen64 because x2nmodp can do right shifts within a loop that has no termination condition.

Remediation

There is no fixed version for Debian:13 zlib.

References

low severity

Directory Traversal

  • Vulnerable module: patch
  • Introduced through: patch@2.8-2

Detailed paths

  • Introduced through: wordpress@apache 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

low severity

CVE-2003-1307

  • Vulnerable module: apache2
  • Introduced through: apache2@2.4.67-1~deb13u2, apache2/apache2-bin@2.4.67-1~deb13u2 and others

Detailed paths

  • Introduced through: wordpress@apache apache2@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-bin@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-data@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-utils@2.4.67-1~deb13u2

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

low severity

CVE-2007-1743

  • Vulnerable module: apache2
  • Introduced through: apache2@2.4.67-1~deb13u2, apache2/apache2-bin@2.4.67-1~deb13u2 and others

Detailed paths

  • Introduced through: wordpress@apache apache2@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-bin@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-data@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-utils@2.4.67-1~deb13u2

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

Small Space of Random Values

  • 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@apache avahi/libavahi-client3@0.8-16
  • Introduced through: wordpress@apache avahi/libavahi-common-data@0.8-16
  • Introduced through: wordpress@apache 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

Use of Insufficiently Random Values

  • 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@apache avahi/libavahi-client3@0.8-16
  • Introduced through: wordpress@apache avahi/libavahi-common-data@0.8-16
  • Introduced through: wordpress@apache 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

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

low severity

Authentication Bypass

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u3 and curl/libcurl4t64@8.14.1-2+deb13u3

Detailed paths

  • Introduced through: wordpress@apache curl@8.14.1-2+deb13u3
  • Introduced through: wordpress@apache curl/libcurl4t64@8.14.1-2+deb13u3

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.

Successfully using libcurl to do a transfer over a specific HTTP proxy (proxyA) with Digest authentication and then changing the proxy host to a second one (proxyB) for a second transfer, reusing the same handle, makes libcurl wrongly pass on the Proxy-Authorization: header field meant for proxyA, to proxyB.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

Cryptographic Issues

  • Vulnerable module: glib2.0/libglib2.0-0t64
  • Introduced through: glib2.0/libglib2.0-0t64@2.84.4-3~deb13u3

Detailed paths

  • Introduced through: wordpress@apache glib2.0/libglib2.0-0t64@2.84.4-3~deb13u3

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

Information Exposure

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u3, glibc/libc-dev-bin@2.41-12+deb13u3 and others

Detailed paths

  • Introduced through: wordpress@apache glibc/libc-bin@2.41-12+deb13u3
  • Introduced through: wordpress@apache glibc/libc-dev-bin@2.41-12+deb13u3
  • Introduced through: wordpress@apache glibc/libc6@2.41-12+deb13u3
  • Introduced through: wordpress@apache glibc/libc6-dev@2.41-12+deb13u3

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

low severity

Use of Insufficiently Random Values

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u3, glibc/libc-dev-bin@2.41-12+deb13u3 and others

Detailed paths

  • Introduced through: wordpress@apache glibc/libc-bin@2.41-12+deb13u3
  • Introduced through: wordpress@apache glibc/libc-dev-bin@2.41-12+deb13u3
  • Introduced through: wordpress@apache glibc/libc6@2.41-12+deb13u3
  • Introduced through: wordpress@apache glibc/libc6-dev@2.41-12+deb13u3

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

low severity

Reliance on Undefined

  • Vulnerable module: imagemagick/imagemagick-7-common
  • Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8 and others

Detailed paths

  • Introduced through: wordpress@apache imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8

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

Resource Management Errors

  • Vulnerable module: imagemagick/imagemagick-7-common
  • Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8 and others

Detailed paths

  • Introduced through: wordpress@apache imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8

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

low severity

Out-of-Bounds

  • Vulnerable module: libpng1.6/libpng16-16t64
  • Introduced through: libpng1.6/libpng16-16t64@1.6.48-1+deb13u5

Detailed paths

  • Introduced through: wordpress@apache libpng1.6/libpng16-16t64@1.6.48-1+deb13u5

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 flaw has been found in pnggroup libpng up to 1.6.55. Affected by this vulnerability is the function do_pnm2png of the file contrib/pngminus/pnm2png.c of the component pnm2png. This manipulation of the argument width/height causes heap-based buffer overflow. The attack is restricted to local execution. The exploit has been published and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Remediation

There is no fixed version for Debian:13 libpng1.6.

References

low severity

Out-of-Bounds

  • Vulnerable module: libraw/libraw23t64
  • Introduced through: libraw/libraw23t64@0.21.4-2

Detailed paths

  • Introduced through: wordpress@apache 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.

A flaw has been found in LibRaw up to 0.22.0. This affects the function LibRaw::nikon_load_padded_packed_raw of the file src/decoders/decoders_libraw.cpp of the component TIFF/NEF. Executing a manipulation of the argument load_flags/raw_width can lead to out-of-bounds read. It is possible to launch the attack remotely. The exploit has been published and may be used. Upgrading to version 0.22.1 mitigates this issue. This patch is called b8397cd45657b84e88bd1202528d1764265f185c. It is advisable to upgrade the affected component.

Remediation

There is no fixed version for Debian:13 libraw.

References

low severity

Improper Validation of Integrity Check Value

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@257.13-1~deb13u1 and systemd/libudev1@257.13-1~deb13u1

Detailed paths

  • Introduced through: wordpress@apache systemd/libsystemd0@257.13-1~deb13u1
  • Introduced through: wordpress@apache systemd/libudev1@257.13-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

Improper Validation of Integrity Check Value

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@257.13-1~deb13u1 and systemd/libudev1@257.13-1~deb13u1

Detailed paths

  • Introduced through: wordpress@apache systemd/libsystemd0@257.13-1~deb13u1
  • Introduced through: wordpress@apache systemd/libudev1@257.13-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

Improper Validation of Integrity Check Value

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@257.13-1~deb13u1 and systemd/libudev1@257.13-1~deb13u1

Detailed paths

  • Introduced through: wordpress@apache systemd/libsystemd0@257.13-1~deb13u1
  • Introduced through: wordpress@apache systemd/libudev1@257.13-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

Authentication Bypass

  • 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@apache util-linux@2.41-5
  • Introduced through: wordpress@apache util-linux/bsdutils@1:2.41-5
  • Introduced through: wordpress@apache util-linux/libblkid1@2.41-5
  • Introduced through: wordpress@apache util-linux/liblastlog2-2@2.41-5
  • Introduced through: wordpress@apache util-linux/libmount1@2.41-5
  • Introduced through: wordpress@apache util-linux/libsmartcols1@2.41-5
  • Introduced through: wordpress@apache util-linux/libuuid1@2.41-5
  • Introduced through: wordpress@apache util-linux/login@1:4.16.0-2+really2.41-5
  • Introduced through: wordpress@apache 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. Improper hostname canonicalization in the login(1) utility, when invoked with the -h option, can modify the supplied remote hostname before setting PAM_RHOST. A remote attacker could exploit this by providing a specially crafted hostname, potentially bypassing host-based Pluggable Authentication Modules (PAM) access control rules that rely on fully qualified domain names. This could lead to unauthorized access.

Remediation

There is no fixed version for Debian:13 util-linux.

References

low severity

Heap-based Buffer Overflow

  • Vulnerable module: xz-utils
  • Introduced through: xz-utils@5.8.1-1 and xz-utils/liblzma5@5.8.1-1

Detailed paths

  • Introduced through: wordpress@apache xz-utils@5.8.1-1
  • Introduced through: wordpress@apache xz-utils/liblzma5@5.8.1-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream xz-utils package and not the xz-utils package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

XZ Utils provide a general-purpose data-compression library plus command-line tools. Prior to version 5.8.3, if lzma_index_decoder() was used to decode an Index that contained no Records, the resulting lzma_index was left in a state where where a subsequent lzma_index_append() would allocate too little memory, and a buffer overflow would occur. This issue has been patched in version 5.8.3.

Remediation

There is no fixed version for Debian:13 xz-utils.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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 was found in binutils, specifically within the readelf utility. This vulnerability allows a local attacker to cause a Denial of Service (DoS) by tricking a user into processing a specially crafted Executable and Linkable Format (ELF) file. The exploitation of this flaw can lead to the system becoming unresponsive due to excessive resource consumption or a program crash.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

low severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

low severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

low severity

Double Free

  • Vulnerable module: tiff/libtiff6
  • Introduced through: tiff/libtiff6@4.7.0-3+deb13u2

Detailed paths

  • Introduced through: wordpress@apache tiff/libtiff6@4.7.0-3+deb13u2

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 up to v4.7.1 was discovered to contain a double free via the component tools/tiffcrop.c.

Remediation

There is no fixed version for Debian:13 tiff.

References

low severity

Race Condition

  • Vulnerable module: coreutils
  • Introduced through: coreutils@9.7-3

Detailed paths

  • Introduced through: wordpress@apache 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

Improper Initialization

  • Vulnerable module: openldap/libldap2
  • Introduced through: openldap/libldap2@2.6.10+dfsg-1

Detailed paths

  • Introduced through: wordpress@apache 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

Stack-based Buffer Overflow

  • Vulnerable module: coreutils
  • Introduced through: coreutils@9.7-3

Detailed paths

  • Introduced through: wordpress@apache 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

low severity

Link Following

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@257.13-1~deb13u1 and systemd/libudev1@257.13-1~deb13u1

Detailed paths

  • Introduced through: wordpress@apache systemd/libsystemd0@257.13-1~deb13u1
  • Introduced through: wordpress@apache systemd/libudev1@257.13-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

Numeric Errors

  • Vulnerable module: apache2
  • Introduced through: apache2@2.4.67-1~deb13u2, apache2/apache2-bin@2.4.67-1~deb13u2 and others

Detailed paths

  • Introduced through: wordpress@apache apache2@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-bin@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-data@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-utils@2.4.67-1~deb13u2

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

Resource Management Errors

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u3, glibc/libc-dev-bin@2.41-12+deb13u3 and others

Detailed paths

  • Introduced through: wordpress@apache glibc/libc-bin@2.41-12+deb13u3
  • Introduced through: wordpress@apache glibc/libc-dev-bin@2.41-12+deb13u3
  • Introduced through: wordpress@apache glibc/libc6@2.41-12+deb13u3
  • Introduced through: wordpress@apache glibc/libc6-dev@2.41-12+deb13u3

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

low severity

Improper Input Validation

  • Vulnerable module: gnutls28/libgnutls30t64
  • Introduced through: gnutls28/libgnutls30t64@3.8.9-3+deb13u4

Detailed paths

  • Introduced through: wordpress@apache gnutls28/libgnutls30t64@3.8.9-3+deb13u4

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

low severity

Memory Leak

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.46.1-7+deb13u1

Detailed paths

  • Introduced through: wordpress@apache sqlite3/libsqlite3-0@3.46.1-7+deb13u1

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

low severity

Improper Certificate Validation

  • Vulnerable module: openldap/libldap2
  • Introduced through: openldap/libldap2@2.6.10+dfsg-1

Detailed paths

  • Introduced through: wordpress@apache 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

low severity

Session Fixation

  • Vulnerable module: apache2
  • Introduced through: apache2@2.4.67-1~deb13u2, apache2/apache2-bin@2.4.67-1~deb13u2 and others

Detailed paths

  • Introduced through: wordpress@apache apache2@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-bin@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-data@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-utils@2.4.67-1~deb13u2

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

Arbitrary Code Injection

  • Vulnerable module: apache2
  • Introduced through: apache2@2.4.67-1~deb13u2, apache2/apache2-bin@2.4.67-1~deb13u2 and others

Detailed paths

  • Introduced through: wordpress@apache apache2@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-bin@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-data@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-utils@2.4.67-1~deb13u2

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

low severity

Cross-site Scripting (XSS)

  • Vulnerable module: apache2
  • Introduced through: apache2@2.4.67-1~deb13u2, apache2/apache2-bin@2.4.67-1~deb13u2 and others

Detailed paths

  • Introduced through: wordpress@apache apache2@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-bin@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-data@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-utils@2.4.67-1~deb13u2

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

Improper Verification of Cryptographic Signature

  • Vulnerable module: apt
  • Introduced through: apt@3.0.3 and apt/libapt-pkg7.0@3.0.3

Detailed paths

  • Introduced through: wordpress@apache apt@3.0.3
  • Introduced through: wordpress@apache 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

low severity

Memory Leak

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

Uncontrolled Recursion

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u2

Detailed paths

  • Introduced through: wordpress@apache 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 flaw was identified in the RelaxNG parser of libxml2 related to how external schema inclusions are handled. The parser does not enforce a limit on inclusion depth when resolving nested <include> directives. Specially crafted or overly complex schemas can cause excessive recursion during parsing. This may lead to stack exhaustion and application crashes, creating a denial-of-service risk.

Remediation

There is no fixed version for Debian:13 libxml2.

References

low severity

Memory Leak

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

Out-of-Bounds

  • Vulnerable module: libheif/libheif-plugin-aomenc
  • Introduced through: libheif/libheif-plugin-aomenc@1.19.8-1, libheif/libheif-plugin-dav1d@1.19.8-1 and others

Detailed paths

  • Introduced through: wordpress@apache libheif/libheif-plugin-aomenc@1.19.8-1
  • Introduced through: wordpress@apache libheif/libheif-plugin-dav1d@1.19.8-1
  • Introduced through: wordpress@apache libheif/libheif-plugin-libde265@1.19.8-1
  • Introduced through: wordpress@apache libheif/libheif-plugin-x265@1.19.8-1
  • Introduced through: wordpress@apache 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.

A vulnerability was determined in strukturag libheif up to 1.21.2. This affects the function vvdec_push_data2 of the file libheif/plugins/decoder_vvdec.cc of the component HEIF File Parser. Executing a manipulation of the argument size can lead to out-of-bounds read. The attack needs to be launched locally. The exploit has been publicly disclosed and may be utilized. This patch is called b97c8b5f198b27f375127cd597a35f2113544d03. It is advisable to implement a patch to correct this issue.

Remediation

There is no fixed version for Debian:13 libheif.

References

low severity

Improper Resource Shutdown or Release

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u2

Detailed paths

  • Introduced through: wordpress@apache 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

low severity

Out-of-Bounds

  • 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@apache ncurses/libncursesw6@6.5+20250216-2
  • Introduced through: wordpress@apache ncurses/libtinfo6@6.5+20250216-2
  • Introduced through: wordpress@apache ncurses/ncurses-base@6.5+20250216-2
  • Introduced through: wordpress@apache 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

low severity

Link Following

  • Vulnerable module: perl
  • Introduced through: perl@5.40.1-6, perl/libperl5.40@5.40.1-6 and others

Detailed paths

  • Introduced through: wordpress@apache perl@5.40.1-6
  • Introduced through: wordpress@apache perl/libperl5.40@5.40.1-6
  • Introduced through: wordpress@apache perl/perl-base@5.40.1-6
  • Introduced through: wordpress@apache 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

low severity

Improper Resource Shutdown or Release

  • Vulnerable module: re2c
  • Introduced through: re2c@4.1-1

Detailed paths

  • Introduced through: wordpress@apache 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.

A flaw has been found in skvadrik re2c up to 4.4. Impacted is the function check_and_merge_special_rules of the file src/parse/ast.cc. This manipulation causes null pointer dereference. The attack can only be executed locally. The exploit has been published and may be used. Patch name: febeb977936f9519a25d9fbd10ff8256358cdb97. It is suggested to install a patch to address this issue.

Remediation

There is no fixed version for Debian:13 re2c.

References

low severity

Incorrect Resource Transfer Between Spheres

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@257.13-1~deb13u1 and systemd/libudev1@257.13-1~deb13u1

Detailed paths

  • Introduced through: wordpress@apache systemd/libsystemd0@257.13-1~deb13u1
  • Introduced through: wordpress@apache systemd/libudev1@257.13-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.

In systemd 259, systemd-journald can send ANSI escape sequences to the terminals of arbitrary users when a "logger -p emerg" command is executed, if ForwardToWall=yes is set.

Remediation

There is no fixed version for Debian:13 systemd.

References

low severity

Memory Leak

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

Memory Leak

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

Memory Leak

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

Memory Leak

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

low severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

Resource Exhaustion

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u2

Detailed paths

  • Introduced through: wordpress@apache 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 flaw was found in the libxml2 library. This uncontrolled resource consumption vulnerability occurs when processing XML catalogs that contain repeated <nextCatalog> elements pointing to the same downstream catalog. A remote attacker can exploit this by supplying crafted catalogs, causing the parser to redundantly traverse catalog chains. This leads to excessive CPU consumption and degrades application availability, resulting in a denial-of-service condition.

Remediation

There is no fixed version for Debian:13 libxml2.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.7.1-2

Detailed paths

  • Introduced through: wordpress@apache 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 before 2.7.4, XML_ExternalEntityParserCreate does not copy unknown encoding handler user data.

Remediation

There is no fixed version for Debian:13 expat.

References

low severity

Improper Resource Shutdown or Release

  • Vulnerable module: tiff/libtiff6
  • Introduced through: tiff/libtiff6@4.7.0-3+deb13u2

Detailed paths

  • Introduced through: wordpress@apache tiff/libtiff6@4.7.0-3+deb13u2

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

low severity
new

Buffer Over-read

  • Vulnerable module: apache2
  • Introduced through: apache2@2.4.67-1~deb13u2, apache2/apache2-bin@2.4.67-1~deb13u2 and others

Detailed paths

  • Introduced through: wordpress@apache apache2@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-bin@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-data@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-utils@2.4.67-1~deb13u2

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.

Buffer Over-read vulnerability in Apache HTTP Server via outbound OCSP requests to an attacker controlled OCSP server

This issue affects Apache HTTP Server: from 2.4.0 through 2.4.67.

Users are recommended to upgrade to version 2.4.68, which fixes the issue.

Remediation

There is no fixed version for Debian:13 apache2.

References

low severity
new

Buffer Underflow

  • Vulnerable module: apache2
  • Introduced through: apache2@2.4.67-1~deb13u2, apache2/apache2-bin@2.4.67-1~deb13u2 and others

Detailed paths

  • Introduced through: wordpress@apache apache2@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-bin@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-data@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-utils@2.4.67-1~deb13u2

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.

Buffer Underwrite vulnerability in Apache HTTP Server on crafted regular expressions in the configuration.

This issue affects Apache HTTP Server: from 2.4.0 through 2.4.67.

Users are recommended to upgrade to version 2.4.68, which fixes the issue.

Remediation

There is no fixed version for Debian:13 apache2.

References

low severity
new

Cross-site Scripting (XSS)

  • Vulnerable module: apache2
  • Introduced through: apache2@2.4.67-1~deb13u2, apache2/apache2-bin@2.4.67-1~deb13u2 and others

Detailed paths

  • Introduced through: wordpress@apache apache2@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-bin@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-data@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-utils@2.4.67-1~deb13u2

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.

A cross-site scripting vulnerability exists in mod_proxy_ftp's HTML directory list generation in Apache HTTP Server 2.4.67 and earlier when listing FTP directory contents either via forward or reverse proxy configuration.

Users are recommended to upgrade to version 2.4.68, which fixes this issue.

Remediation

There is no fixed version for Debian:13 apache2.

References

low severity
new

Exposure of Resource to Wrong Sphere

  • Vulnerable module: apache2
  • Introduced through: apache2@2.4.67-1~deb13u2, apache2/apache2-bin@2.4.67-1~deb13u2 and others

Detailed paths

  • Introduced through: wordpress@apache apache2@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-bin@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-data@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-utils@2.4.67-1~deb13u2

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.

A path handling issue in mod_dav_fs in Apache 2.4.67 and earlier allows a WebDAV content author to directly manipulate trusted DAV property databases, potentially causing child process crashes.

Users are recommended to upgrade to version 2.4.68, which fixes this issue.

Remediation

There is no fixed version for Debian:13 apache2.

References

low severity
new

Heap-based Buffer Overflow

  • Vulnerable module: apache2
  • Introduced through: apache2@2.4.67-1~deb13u2, apache2/apache2-bin@2.4.67-1~deb13u2 and others

Detailed paths

  • Introduced through: wordpress@apache apache2@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-bin@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-data@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-utils@2.4.67-1~deb13u2

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.

Heap-based Buffer Overflow vulnerability in Apache HTTP Server with mod_xml2enc, xml2StartParse, and untrusted content

This issue affects Apache HTTP Server: from 2.4.0 through 2.4.67.

Users are recommended to upgrade to version 2.4.68, which fixes the issue.

Remediation

There is no fixed version for Debian:13 apache2.

References

low severity
new

Heap-based Buffer Overflow

  • Vulnerable module: apache2
  • Introduced through: apache2@2.4.67-1~deb13u2, apache2/apache2-bin@2.4.67-1~deb13u2 and others

Detailed paths

  • Introduced through: wordpress@apache apache2@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-bin@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-data@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-utils@2.4.67-1~deb13u2

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.

A buffer overflow in mod_proxy_html in Apache HTTP Server 2.4.67 and earlier allows an attack by an untrusted backend. Users are recommended to upgrade to version 2.4.68, which fixes this issue.

Remediation

There is no fixed version for Debian:13 apache2.

References

low severity
new

Heap-based Buffer Overflow

  • Vulnerable module: apache2
  • Introduced through: apache2@2.4.67-1~deb13u2, apache2/apache2-bin@2.4.67-1~deb13u2 and others

Detailed paths

  • Introduced through: wordpress@apache apache2@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-bin@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-data@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-utils@2.4.67-1~deb13u2

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.

Heap-based Buffer Overflow vulnerability in Apache HTTP Server with malicious backend servers and ProxyPassReverseCookie*

This issue affects Apache HTTP Server: from 2.4.0 through 2.4.67.

Users are recommended to upgrade to version 2.4.68, which fixes the issue.

Remediation

There is no fixed version for Debian:13 apache2.

References

low severity
new

Improper Privilege Management

  • Vulnerable module: apache2
  • Introduced through: apache2@2.4.67-1~deb13u2, apache2/apache2-bin@2.4.67-1~deb13u2 and others

Detailed paths

  • Introduced through: wordpress@apache apache2@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-bin@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-data@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-utils@2.4.67-1~deb13u2

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 Privilege Management vulnerability in Apache HTTP Server 2.4.67 and earlier allows local .htaccess authors to read files with the privileges of the httpd user.

This issue affects Apache HTTP Server: from through 2.4.67.

Users are recommended to upgrade to version 2.4.68, which fixes the issue.

Remediation

There is no fixed version for Debian:13 apache2.

References

low severity
new

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: apache2
  • Introduced through: apache2@2.4.67-1~deb13u2, apache2/apache2-bin@2.4.67-1~deb13u2 and others

Detailed paths

  • Introduced through: wordpress@apache apache2@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-bin@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-data@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-utils@2.4.67-1~deb13u2

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.

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability in the mod_proxy_ftp module in Apache HTTP Server with an attacker controlled backend FTP server.

This issue affects undefined: from 2.4.0 through 2.4.67.

Users are recommended to upgrade to version 2.4.68, which fixes the issue.

Remediation

There is no fixed version for Debian:13 apache2.

References

low severity
new

Out-of-bounds Read

  • Vulnerable module: apache2
  • Introduced through: apache2@2.4.67-1~deb13u2, apache2/apache2-bin@2.4.67-1~deb13u2 and others

Detailed paths

  • Introduced through: wordpress@apache apache2@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-bin@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-data@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-utils@2.4.67-1~deb13u2

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.

Out-of-bounds Read vulnerability in Apache HTTP Server with mod_headers and mod_mime and multiple response languages.

This issue affects Apache HTTP Server: from 2.4.0 through 2.4.67.

Remediation

There is no fixed version for Debian:13 apache2.

References

low severity
new

Uncontrolled Memory Allocation

  • Vulnerable module: apache2
  • Introduced through: apache2@2.4.67-1~deb13u2, apache2/apache2-bin@2.4.67-1~deb13u2 and others
  • Fixed in: 2.4.67-1~deb13u3

Detailed paths

  • Introduced through: wordpress@apache apache2@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-bin@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-data@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-utils@2.4.67-1~deb13u2

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.

Memory Allocation with Excessive Size Value vulnerability in Apache HTTP Server's mod_http leads to denial of service via malicious HTTP requests.

This issue affects Apache HTTP Server: from 2.4.17 through 2.4.67.

Remediation

Upgrade Debian:13 apache2 to version 2.4.67-1~deb13u3 or higher.

References

low severity
new

Use After Free

  • Vulnerable module: apache2
  • Introduced through: apache2@2.4.67-1~deb13u2, apache2/apache2-bin@2.4.67-1~deb13u2 and others

Detailed paths

  • Introduced through: wordpress@apache apache2@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-bin@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-data@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-utils@2.4.67-1~deb13u2

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.

Use After Free vulnerability in Apache HTTP Server with mod_ldap in per-directory configuration

This issue affects Apache HTTP Server: from 2.4.0 through 2.4.67.

Users are recommended to upgrade to version 2.4.68, which fixes the issue.

Remediation

There is no fixed version for Debian:13 apache2.

References

low severity
new

Use After Free

  • Vulnerable module: apache2
  • Introduced through: apache2@2.4.67-1~deb13u2, apache2/apache2-bin@2.4.67-1~deb13u2 and others

Detailed paths

  • Introduced through: wordpress@apache apache2@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-bin@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-data@2.4.67-1~deb13u2
  • Introduced through: wordpress@apache apache2/apache2-utils@2.4.67-1~deb13u2

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.

Use After Free vulnerability in Apache HTTP Server module mod_http2 when file handles are already exhausted.

This issue affects Apache HTTP Server: from 2.4.55 through 2.4.67.

Remediation

There is no fixed version for Debian:13 apache2.

References

low severity

Reachable Assertion

  • 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@apache avahi/libavahi-client3@0.8-16
  • Introduced through: wordpress@apache avahi/libavahi-common-data@0.8-16
  • Introduced through: wordpress@apache 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 0.9-rc2 and earlier, avahi-daemon can be crashed by sending unsolicited announcements containing CNAME resource records pointing it to resource records with short TTLs. As soon as they expire avahi-daemon crashes.

Remediation

There is no fixed version for Debian:13 avahi.

References

low severity

Reachable Assertion

  • 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@apache avahi/libavahi-client3@0.8-16
  • Introduced through: wordpress@apache avahi/libavahi-common-data@0.8-16
  • Introduced through: wordpress@apache 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 0.9-rc2 and earlier, avahi-daemon can be crashed by sending 2 unsolicited announcements with CNAME resource records 2 seconds apart.

Remediation

There is no fixed version for Debian:13 avahi.

References

low severity

Reachable Assertion

  • 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@apache avahi/libavahi-client3@0.8-16
  • Introduced through: wordpress@apache avahi/libavahi-common-data@0.8-16
  • Introduced through: wordpress@apache 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 0.9-rc2 and earlier, an unprivileged local users can crash avahi-daemon (with wide-area disabled) by creating record browsers with the AVAHI_LOOKUP_USE_WIDE_AREA flag set via D-Bus. This can be done by either calling the RecordBrowserNew method directly or creating hostname/address/service resolvers/browsers that create those browsers internally themselves.

Remediation

There is no fixed version for Debian:13 avahi.

References

low severity

Reachable Assertion

  • 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@apache avahi/libavahi-client3@0.8-16
  • Introduced through: wordpress@apache avahi/libavahi-common-data@0.8-16
  • Introduced through: wordpress@apache 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. Prior to version 0.9-rc4, any unprivileged local user can crash avahi-daemon by sending a single D-Bus method call with conflicting publish flags. This issue has been patched in version 0.9-rc4.

Remediation

There is no fixed version for Debian:13 avahi.

References

low severity

Resource Exhaustion

  • 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@apache avahi/libavahi-client3@0.8-16
  • Introduced through: wordpress@apache avahi/libavahi-common-data@0.8-16
  • Introduced through: wordpress@apache 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

CVE-2025-66861

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

CVE-2025-66862

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

CVE-2025-66863

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

CVE-2025-66865

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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

CVE-2025-69644

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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 Binutils before 2.46. The objdump contains a denial-of-service vulnerability when processing a crafted binary with malformed debug information. A logic flaw in the handling of DWARF location list headers can cause objdump to enter an unbounded loop and produce endless output until manually interrupted. This issue affects versions prior to the upstream fix and allows a local attacker to cause excessive resource consumption by supplying a malicious input file.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

CVE-2025-69645

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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.

Binutils objdump contains a denial-of-service vulnerability when processing a crafted binary with malformed DWARF debug information. A logic error in the handling of DWARF compilation units can result in an invalid offset_size value being used inside byte_get_little_endian, leading to an abort (SIGABRT). The issue was observed in binutils 2.44. A local attacker can trigger the crash by supplying a malicious input file.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

CVE-2025-69646

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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.

Binutils objdump contains a denial-of-service vulnerability when processing a crafted binary with malformed DWARF debug_rnglists data. A logic error in the handling of the debug_rnglists header can cause objdump to repeatedly print the same warning message and fail to terminate, resulting in an unbounded logging loop until the process is interrupted. The issue was observed in binutils 2.44. A local attacker can exploit this vulnerability by supplying a malicious input file, leading to excessive CPU and I/O usage and preventing completion of the objdump analysis.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

CVE-2025-69647

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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.

GNU Binutils thru 2.45.1 readelf contains a denial-of-service vulnerability when processing a crafted binary with malformed DWARF loclists data. A logic flaw in the DWARF parsing code can cause readelf to repeatedly print the same table output without making forward progress, resulting in an unbounded output loop that never terminates unless externally interrupted. A local attacker can trigger this behavior by supplying a malicious input file, causing excessive CPU and I/O usage and preventing readelf from completing its analysis.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

CVE-2025-69648

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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.

GNU Binutils thru 2.45.1 readelf contains a denial-of-service vulnerability when processing a crafted binary with malformed DWARF .debug_rnglists data. A logic flaw in the DWARF parsing path causes readelf to repeatedly print the same warning message without making forward progress, resulting in a non-terminating output loop that requires manual interruption. No evidence of memory corruption or code execution was observed.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

CVE-2025-69652

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: wordpress@apache binutils@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-common@2.44-3
  • Introduced through: wordpress@apache binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: wordpress@apache binutils/libbinutils@2.44-3
  • Introduced through: wordpress@apache binutils/libctf-nobfd0@2.44-3
  • Introduced through: wordpress@apache binutils/libctf0@2.44-3
  • Introduced through: wordpress@apache binutils/libgprofng0@2.44-3
  • Introduced through: wordpress@apache 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.

GNU Binutils thru 2.46 readelf contains a vulnerability that leads to an abort (SIGABRT) when processing a crafted ELF binary with malformed DWARF abbrev or debug information. Due to incomplete state cleanup in process_debug_info(), an invalid debug_info_p state may propagate into DWARF attribute parsing routines. When certain malformed attributes result in an unexpected data length of zero, byte_get_little_endian() triggers a fatal abort. No evidence of memory corruption or code execution was observed; the impact is limited to denial of service.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity
new

Out-of-bounds Write

  • Vulnerable module: bzip2
  • Introduced through: bzip2@1.0.8-6 and bzip2/libbz2-1.0@1.0.8-6

Detailed paths

  • Introduced through: wordpress@apache bzip2@1.0.8-6
  • Introduced through: wordpress@apache bzip2/libbz2-1.0@1.0.8-6

NVD Description

Note: Versions mentioned in the description apply only to the upstream bzip2 package and not the bzip2 package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

bzip2 contains an off‑by‑one error in the bzip2recover utility. When processing a specially crafted file, the application performs an out‑of‑bounds write to a global buffer, resulting in memory corruption and a crash (denial of service).

This issue was fixed in bzip2 patch 35d122a3df8b0cc4082a4d89fdc6ee99f375fe67

Remediation

There is no fixed version for Debian:13 bzip2.

References

low severity

Directory Traversal

  • Vulnerable module: cups/libcups2t64
  • Introduced through: cups/libcups2t64@2.4.10-3+deb13u2

Detailed paths

  • Introduced through: wordpress@apache 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. In versions 2.4.16 and prior, the RSS notifier allows .. path traversal in notify-recipient-uri (e.g., rss:///../job.cache), letting a remote IPP client write RSS XML bytes outside CacheDir/rss (anywhere that is lp-writable). In particular, because CacheDir is group-writable by default (typically root:lp and mode 0770), the notifier (running as lp) can replace root-managed state files via temp-file + rename(). This PoC clobbers CacheDir/job.cache with RSS XML, and after restarting cupsd the scheduler fails to parse the job cache and previously queued jobs disappear. At time of publication, there are no publicly available patches.

Remediation

There is no fixed version for Debian:13 cups.

References

low severity

Heap-based Buffer Overflow

  • Vulnerable module: cups/libcups2t64
  • Introduced through: cups/libcups2t64@2.4.10-3+deb13u2

Detailed paths

  • Introduced through: wordpress@apache 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. In versions 2.4.16 and prior, there is a heap-based buffer overflow in the CUPS scheduler when building filter option strings from job attribute. At time of publication, there are no publicly available patches.

Remediation

There is no fixed version for Debian:13 cups.

References

low severity

Improper Authentication

  • Vulnerable module: cups/libcups2t64
  • Introduced through: cups/libcups2t64@2.4.10-3+deb13u2

Detailed paths

  • Introduced through: wordpress@apache 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. In versions 2.4.16 and prior, a local unprivileged user can coerce cupsd into authenticating to an attacker-controlled localhost IPP service with a reusable Authorization: Local ... token. That token is enough to drive /admin/ requests on localhost, and the attacker can combine CUPS-Create-Local-Printer with printer-is-shared=true to persist a file:///... queue even though the normal FileDevice policy rejects such URIs. Printing to that queue gives an arbitrary root file overwrite; the PoC below uses that primitive to drop a sudoers fragment and demonstrate root command execution. At time of publication, there are no publicly available patches.

Remediation

There is no fixed version for Debian:13 cups.

References

low severity

CVE-2025-10966

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u3 and curl/libcurl4t64@8.14.1-2+deb13u3

Detailed paths

  • Introduced through: wordpress@apache curl@8.14.1-2+deb13u3
  • Introduced through: wordpress@apache curl/libcurl4t64@8.14.1-2+deb13u3

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

CVE-2025-14017

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u3 and curl/libcurl4t64@8.14.1-2+deb13u3

Detailed paths

  • Introduced through: wordpress@apache curl@8.14.1-2+deb13u3
  • Introduced through: wordpress@apache curl/libcurl4t64@8.14.1-2+deb13u3

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

CVE-2025-14819

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u3 and curl/libcurl4t64@8.14.1-2+deb13u3

Detailed paths

  • Introduced through: wordpress@apache curl@8.14.1-2+deb13u3
  • Introduced through: wordpress@apache curl/libcurl4t64@8.14.1-2+deb13u3

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

CVE-2025-15079

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u3 and curl/libcurl4t64@8.14.1-2+deb13u3

Detailed paths

  • Introduced through: wordpress@apache curl@8.14.1-2+deb13u3
  • Introduced through: wordpress@apache curl/libcurl4t64@8.14.1-2+deb13u3

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

CVE-2025-15224

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u3 and curl/libcurl4t64@8.14.1-2+deb13u3

Detailed paths

  • Introduced through: wordpress@apache curl@8.14.1-2+deb13u3
  • Introduced through: wordpress@apache curl/libcurl4t64@8.14.1-2+deb13u3

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

CVE-2026-1965

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u3 and curl/libcurl4t64@8.14.1-2+deb13u3

Detailed paths

  • Introduced through: wordpress@apache curl@8.14.1-2+deb13u3
  • Introduced through: wordpress@apache curl/libcurl4t64@8.14.1-2+deb13u3

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.

libcurl can in some circumstances reuse the wrong connection when asked to do an Negotiate-authenticated HTTP or HTTPS request.

libcurl features a pool of recent connections so that subsequent requests can reuse an existing connection to avoid overhead.

When reusing a connection a range of criterion must first be met. Due to a logical error in the code, a request that was issued by an application could wrongfully reuse an existing connection to the same server that was authenticated using different credentials. One underlying reason being that Negotiate sometimes authenticates connections and not requests, contrary to how HTTP is designed to work.

An application that allows Negotiate authentication to a server (that responds wanting Negotiate) with user1:password1 and then does another operation to the same server also using Negotiate but with user2:password2 (while the previous connection is still alive) - the second request wrongly reused the same connection and since it then sees that the Negotiate negotiation is already made, it just sends the request over that connection thinking it uses the user2 credentials when it is in fact still using the connection authenticated for user1...

The set of authentication methods to use is set with CURLOPT_HTTPAUTH.

Applications can disable libcurl's reuse of connections and thus mitigate this problem, by using one of the following libcurl options to alter how connections are or are not reused: CURLOPT_FRESH_CONNECT, CURLOPT_MAXCONNECTS and CURLMOPT_MAX_HOST_CONNECTIONS (if using the curl_multi API).

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

CVE-2026-3783

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u3 and curl/libcurl4t64@8.14.1-2+deb13u3

Detailed paths

  • Introduced through: wordpress@apache curl@8.14.1-2+deb13u3
  • Introduced through: wordpress@apache curl/libcurl4t64@8.14.1-2+deb13u3

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 redirect to a second URL, curl could leak that token to the second hostname under some circumstances.

If the hostname that the first request is redirected to has information in the used .netrc file, with either of the machine or default keywords, curl would pass on the bearer token set for the first host also to the second one.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

CVE-2026-3784

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u3 and curl/libcurl4t64@8.14.1-2+deb13u3

Detailed paths

  • Introduced through: wordpress@apache curl@8.14.1-2+deb13u3
  • Introduced through: wordpress@apache curl/libcurl4t64@8.14.1-2+deb13u3

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 would wrongly reuse an existing HTTP proxy connection doing CONNECT to a server, even if the new request uses different credentials for the HTTP proxy. The proper behavior is to create or use a separate connection.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

CVE-2026-3805

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u3 and curl/libcurl4t64@8.14.1-2+deb13u3

Detailed paths

  • Introduced through: wordpress@apache curl@8.14.1-2+deb13u3
  • Introduced through: wordpress@apache curl/libcurl4t64@8.14.1-2+deb13u3

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 a second SMB request to the same host again, curl would wrongly use a data pointer pointing into already freed memory.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

CVE-2026-6429

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u3 and curl/libcurl4t64@8.14.1-2+deb13u3

Detailed paths

  • Introduced through: wordpress@apache curl@8.14.1-2+deb13u3
  • Introduced through: wordpress@apache curl/libcurl4t64@8.14.1-2+deb13u3

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 asked to both use a .netrc file for credentials and to follow HTTP redirects, libcurl could leak the password used for the first host to the followed-to host under certain circumstances.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

Improper Certificate Validation

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u3 and curl/libcurl4t64@8.14.1-2+deb13u3

Detailed paths

  • Introduced through: wordpress@apache curl@8.14.1-2+deb13u3
  • Introduced through: wordpress@apache curl/libcurl4t64@8.14.1-2+deb13u3

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.

A vulnerability exists where a connection requiring TLS incorrectly reuses an existing unencrypted connection from the same connection pool. If an initial transfer is made in clear-text (via IMAP, SMTP, or POP3), a subsequent request to that same host bypasses the TLS requirement and instead transmit data unencrypted.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

Insufficiently Protected Credentials

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u3 and curl/libcurl4t64@8.14.1-2+deb13u3

Detailed paths

  • Introduced through: wordpress@apache curl@8.14.1-2+deb13u3
  • Introduced through: wordpress@apache curl/libcurl4t64@8.14.1-2+deb13u3

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 might erroneously pass on credentials for a first proxy to a second proxy.

This can happen when the following conditions are true:

  1. curl is setup to use specific different proxies for different URL schemes
  2. the first proxy needs credentials
  3. the second proxy uses no credentials
  4. while using the first proxy (using say http://), curl is asked to follow a redirect to a URL using another scheme (say https://), accessed using a second, different, proxy

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

Open Redirect

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u3 and curl/libcurl4t64@8.14.1-2+deb13u3

Detailed paths

  • Introduced through: wordpress@apache curl@8.14.1-2+deb13u3
  • Introduced through: wordpress@apache curl/libcurl4t64@8.14.1-2+deb13u3

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

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.7.1-2

Detailed paths

  • Introduced through: wordpress@apache 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

low severity

Insufficient Entropy

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.7.1-2

Detailed paths

  • Introduced through: wordpress@apache 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 before 2.8.0 uses insufficient entropy, and thus hash flooding can occur via a crafted XML document.

Remediation

There is no fixed version for Debian:13 expat.

References

low severity

Stack-based Buffer Overflow

  • 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@apache ghostscript@10.05.1~dfsg-1+deb13u1
  • Introduced through: wordpress@apache ghostscript/libgs-common@10.05.1~dfsg-1+deb13u1
  • Introduced through: wordpress@apache ghostscript/libgs10@10.05.1~dfsg-1+deb13u1
  • Introduced through: wordpress@apache 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

CVE-2026-5435

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u3, glibc/libc-dev-bin@2.41-12+deb13u3 and others

Detailed paths

  • Introduced through: wordpress@apache glibc/libc-bin@2.41-12+deb13u3
  • Introduced through: wordpress@apache glibc/libc-dev-bin@2.41-12+deb13u3
  • Introduced through: wordpress@apache glibc/libc6@2.41-12+deb13u3
  • Introduced through: wordpress@apache glibc/libc6-dev@2.41-12+deb13u3

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 deprecated functions ns_printrrf, ns_printrr and fp_nquery in the GNU C Library version 2.2 and newer fail to enforce the caller-supplied buffer length, and can result in an out-of-bounds write when printing TSIG records.

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

CVE-2026-5928

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u3, glibc/libc-dev-bin@2.41-12+deb13u3 and others

Detailed paths

  • Introduced through: wordpress@apache glibc/libc-bin@2.41-12+deb13u3
  • Introduced through: wordpress@apache glibc/libc-dev-bin@2.41-12+deb13u3
  • Introduced through: wordpress@apache glibc/libc6@2.41-12+deb13u3
  • Introduced through: wordpress@apache glibc/libc6-dev@2.41-12+deb13u3

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.

Calling the ungetwc function on a FILE stream with wide characters encoded in a character set that has overlaps between its single byte and multi-byte character encodings, in the GNU C Library version 2.43 or earlier, may result in an attempt to read bytes before an allocated buffer, potentially resulting in unintentional disclosure of neighboring data in the heap, or a program crash.

A bug in the wide character pushback implementation (_IO_wdefault_pbackfail in libio/wgenops.c) causes ungetwc() to operate on the regular character buffer (fp->_IO_read_ptr) instead of the actual wide-stream read pointer (fp->_wide_data->_IO_read_ptr). The program crash may happen in cases where fp->_IO_read_ptr is not initialized and hence points to NULL. The buffer under-read requires a special situation where the input character encoding is such that there are overlaps between single byte representations and multibyte representations in that encoding, resulting in spurious matches. The spurious match case is not possible in the standard Unicode character sets.

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

CVE-2026-6238

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u3, glibc/libc-dev-bin@2.41-12+deb13u3 and others

Detailed paths

  • Introduced through: wordpress@apache glibc/libc-bin@2.41-12+deb13u3
  • Introduced through: wordpress@apache glibc/libc-dev-bin@2.41-12+deb13u3
  • Introduced through: wordpress@apache glibc/libc6@2.41-12+deb13u3
  • Introduced through: wordpress@apache glibc/libc6-dev@2.41-12+deb13u3

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 deprecated functions ns_printrrf, ns_printrr and fp_nquery in the GNU C Library version 2.2 and newer fail to validate the RDATA content against the RDATA length in a DNS response when processing LOC, CERT, TKEY or TSIG records, which may allow an attacker to craft a DNS response, causing a target application to crash or read uninitialized memory.

These functions are for application debugging only and hence not in the path of code executed by the DNS resolver. Further, they have been deprecated since version 2.34 and should not be used by any new applications. Applications should consider porting away from these interfaces since they may be removed in future versions.

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

Out-of-bounds Write

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u3, glibc/libc-dev-bin@2.41-12+deb13u3 and others

Detailed paths

  • Introduced through: wordpress@apache glibc/libc-bin@2.41-12+deb13u3
  • Introduced through: wordpress@apache glibc/libc-dev-bin@2.41-12+deb13u3
  • Introduced through: wordpress@apache glibc/libc6@2.41-12+deb13u3
  • Introduced through: wordpress@apache glibc/libc6-dev@2.41-12+deb13u3

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.

Calling the scanf family of functions with a %mc (malloc'd character match) in the GNU C Library version 2.7 to version 2.43 with a format width specifier with an explicit width greater than 1024 could result in a one byte heap buffer overflow.

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity
new

Heap-based Buffer Overflow

  • Vulnerable module: imagemagick/imagemagick-7-common
  • Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8 and others
  • Fixed in: 8:7.1.1.43+dfsg1-1+deb13u9

Detailed paths

  • Introduced through: wordpress@apache imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8

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-48 and 7.1.2-23, when reading multiple images with different dimensions an out of bounds heap write can occur. This issue has been patched in versions 6.9.13-48 and 7.1.2-23.

Remediation

Upgrade Debian:13 imagemagick to version 8:7.1.1.43+dfsg1-1+deb13u9 or higher.

References

low severity
new

Heap-based Buffer Overflow

  • Vulnerable module: imagemagick/imagemagick-7-common
  • Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8 and others
  • Fixed in: 8:7.1.1.43+dfsg1-1+deb13u9

Detailed paths

  • Introduced through: wordpress@apache imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8

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-48 and 7.1.2-23, an attacker who can connect to a magick -distribute-cache service can cause a heap buffer over-write in the server process. This issue has been patched in versions 6.9.13-48 and 7.1.2-23.

Remediation

Upgrade Debian:13 imagemagick to version 8:7.1.1.43+dfsg1-1+deb13u9 or higher.

References

low severity
new

Incorrect Calculation of Buffer Size

  • Vulnerable module: imagemagick/imagemagick-7-common
  • Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8 and others
  • Fixed in: 8:7.1.1.43+dfsg1-1+deb13u9

Detailed paths

  • Introduced through: wordpress@apache imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8

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-48 and 7.1.2-23, when using LZMA compression in the MIFF encoder an out of bounds write can occur due to a missing check. This issue has been patched in versions 6.9.13-48 and 7.1.2-23.

Remediation

Upgrade Debian:13 imagemagick to version 8:7.1.1.43+dfsg1-1+deb13u9 or higher.

References

low severity
new

Information Exposure

  • Vulnerable module: imagemagick/imagemagick-7-common
  • Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8 and others
  • Fixed in: 8:7.1.1.43+dfsg1-1+deb13u9

Detailed paths

  • Introduced through: wordpress@apache imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8

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-48 and 7.1.2-23, the distributed pixel cache was originally designed to operate without a challenge–response authentication model. This has been changed in versions 6.9.13-48 and 7.1.2-23.

Remediation

Upgrade Debian:13 imagemagick to version 8:7.1.1.43+dfsg1-1+deb13u9 or higher.

References

low severity
new

Off-by-one Error

  • Vulnerable module: imagemagick/imagemagick-7-common
  • Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8 and others
  • Fixed in: 8:7.1.1.43+dfsg1-1+deb13u9

Detailed paths

  • Introduced through: wordpress@apache imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8

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-48 and 7.1.2-23, an incorrect check in the JP2 will result in an heap buffer over-write of a single byte when specifying certain options. This issue has been patched in versions 6.9.13-48 and 7.1.2-23.

Remediation

Upgrade Debian:13 imagemagick to version 8:7.1.1.43+dfsg1-1+deb13u9 or higher.

References

low severity
new

Out-of-bounds Read

  • Vulnerable module: imagemagick/imagemagick-7-common
  • Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8 and others
  • Fixed in: 8:7.1.1.43+dfsg1-1+deb13u9

Detailed paths

  • Introduced through: wordpress@apache imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8

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-48 and 7.1.2-22, an invalid connected-components:keep-top value could result in a heap buffer over-read when performing the connected components operation. This issue has been patched in versions 6.9.13-48 and 7.1.2-22.

Remediation

Upgrade Debian:13 imagemagick to version 8:7.1.1.43+dfsg1-1+deb13u9 or higher.

References

low severity
new

Out-of-bounds Read

  • Vulnerable module: imagemagick/imagemagick-7-common
  • Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8 and others
  • Fixed in: 8:7.1.1.43+dfsg1-1+deb13u9

Detailed paths

  • Introduced through: wordpress@apache imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8

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-47 and 7.1.2-22, an off by one in the meta encoder could result in an out of bounds read of a single byte in the meta encoder. This issue has been patched in versions 6.9.13-47 and 7.1.2-22.

Remediation

Upgrade Debian:13 imagemagick to version 8:7.1.1.43+dfsg1-1+deb13u9 or higher.

References

low severity
new

Out-of-bounds Read

  • Vulnerable module: imagemagick/imagemagick-7-common
  • Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8 and others
  • Fixed in: 8:7.1.1.43+dfsg1-1+deb13u9

Detailed paths

  • Introduced through: wordpress@apache imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8

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-47 and 7.1.2-22, when performing a polynomial distortion an out of bounds over-read of 24 bytes can occur when specifying specific arguments. This issue has been patched in versions 6.9.13-47 and 7.1.2-22.

Remediation

Upgrade Debian:13 imagemagick to version 8:7.1.1.43+dfsg1-1+deb13u9 or higher.

References

low severity
new

Out-of-bounds Read

  • Vulnerable module: imagemagick/imagemagick-7-common
  • Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8 and others
  • Fixed in: 8:7.1.1.43+dfsg1-1+deb13u9

Detailed paths

  • Introduced through: wordpress@apache imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8

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-48 and 7.1.2-23, an attacker who can connect to a magick -distribute-cache service can cause a heap buffer over-read in the server process. This issue has been patched in versions 6.9.13-48 and 7.1.2-23.

Remediation

Upgrade Debian:13 imagemagick to version 8:7.1.1.43+dfsg1-1+deb13u9 or higher.

References

low severity
new

Out-of-bounds Read

  • Vulnerable module: imagemagick/imagemagick-7-common
  • Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8 and others
  • Fixed in: 8:7.1.1.43+dfsg1-1+deb13u9

Detailed paths

  • Introduced through: wordpress@apache imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8

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-47 and 7.1.2-22, when writing an IPTC output file a malicious input file could cause an out of bounds read of a single byte. This issue has been patched in versions 6.9.13-47 and 7.1.2-22.

Remediation

Upgrade Debian:13 imagemagick to version 8:7.1.1.43+dfsg1-1+deb13u9 or higher.

References

low severity
new

Race Condition

  • Vulnerable module: imagemagick/imagemagick-7-common
  • Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8 and others
  • Fixed in: 8:7.1.1.43+dfsg1-1+deb13u9

Detailed paths

  • Introduced through: wordpress@apache imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8

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-48 and 7.1.2-23, an attacker who can connect to a magick -distribute-cache service can hijack a file descriptor in the server process when a race condition is met. This issue has been patched in versions 6.9.13-48 and 7.1.2-23.

Remediation

Upgrade Debian:13 imagemagick to version 8:7.1.1.43+dfsg1-1+deb13u9 or higher.

References

low severity
new

Resource Exhaustion

  • Vulnerable module: imagemagick/imagemagick-7-common
  • Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8 and others
  • Fixed in: 8:7.1.1.43+dfsg1-1+deb13u9

Detailed paths

  • Introduced through: wordpress@apache imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8

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 7.1.2.23 and 6.9.13-48, due to a missing check in the MIFF decoder, a crafted file could cause an infinite loop resulting in CPU exhaustion. Versions 7.1.2.23 and 6.9.13-48 fix the issue.

Remediation

Upgrade Debian:13 imagemagick to version 8:7.1.1.43+dfsg1-1+deb13u9 or higher.

References

low severity
new

Resource Exhaustion

  • Vulnerable module: imagemagick/imagemagick-7-common
  • Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8 and others
  • Fixed in: 8:7.1.1.43+dfsg1-1+deb13u9

Detailed paths

  • Introduced through: wordpress@apache imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8

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-47 and 7.1.2-22, due to a missing check in the PSD decoder it would be possible to bypass the list-length resource policy when decoding a PSD image. Other security limits would still apply. This issue has been patched in versions 6.9.13-47 and 7.1.2-22.

Remediation

Upgrade Debian:13 imagemagick to version 8:7.1.1.43+dfsg1-1+deb13u9 or higher.

References

low severity
new

Resource Exhaustion

  • Vulnerable module: imagemagick/imagemagick-7-common
  • Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8 and others
  • Fixed in: 8:7.1.1.43+dfsg1-1+deb13u9

Detailed paths

  • Introduced through: wordpress@apache imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8

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-47 and 7.1.2-22, because of a missing check in the MNG coder it would be possible to read more images than the list limit policy would allow resulting in excessive resource use. This issue has been patched in versions 6.9.13-47 and 7.1.2-22.

Remediation

Upgrade Debian:13 imagemagick to version 8:7.1.1.43+dfsg1-1+deb13u9 or higher.

References

low severity

Stack-based Buffer Overflow

  • Vulnerable module: imagemagick/imagemagick-7-common
  • Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8 and others
  • Fixed in: 8:7.1.1.43+dfsg1-1+deb13u9

Detailed paths

  • Introduced through: wordpress@apache imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8

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-21 and 6.9.13-46, a malicious MIFF file could trigger an overflow when a user opens it in the display tool and right-clicks a tile to invoke the Load / Update menu item. This vulnerability is fixed in 7.1.2-21 and 6.9.13-46.

Remediation

Upgrade Debian:13 imagemagick to version 8:7.1.1.43+dfsg1-1+deb13u9 or higher.

References

low severity
new

Uncontrolled Recursion

  • Vulnerable module: imagemagick/imagemagick-7-common
  • Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8 and others
  • Fixed in: 8:7.1.1.43+dfsg1-1+deb13u9

Detailed paths

  • Introduced through: wordpress@apache imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8

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-23, due to a missing depth check a stack overflow can occur in the fx operation by passing a crafted argument. This issue has been patched in version 7.1.2-23.

Remediation

Upgrade Debian:13 imagemagick to version 8:7.1.1.43+dfsg1-1+deb13u9 or higher.

References

low severity
new

Use After Free

  • Vulnerable module: imagemagick/imagemagick-7-common
  • Introduced through: imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8, imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8 and others
  • Fixed in: 8:7.1.1.43+dfsg1-1+deb13u9

Detailed paths

  • Introduced through: wordpress@apache imagemagick/imagemagick-7-common@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickcore-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8
  • Introduced through: wordpress@apache imagemagick/libmagickwand-7.q16-10@8:7.1.1.43+dfsg1-1+deb13u8

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 7.1.2.23 and 6.9.13-48, a crafted MSL image can trigger a heap-use-after-free. Versions 7.1.2.23 and 6.9.13-48 fix the issue.

Remediation

Upgrade Debian:13 imagemagick to version 8:7.1.1.43+dfsg1-1+deb13u9 or higher.

References

low severity

CVE-2024-26461

  • 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@apache krb5/libgssapi-krb5-2@1.21.3-5
  • Introduced through: wordpress@apache krb5/libk5crypto3@1.21.3-5
  • Introduced through: wordpress@apache krb5/libkrb5-3@1.21.3-5
  • Introduced through: wordpress@apache 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

Integer Underflow

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.21.3-5, krb5/libk5crypto3@1.21.3-5 and others
  • Fixed in: 1.21.3-5+deb13u1

Detailed paths

  • Introduced through: wordpress@apache krb5/libgssapi-krb5-2@1.21.3-5
  • Introduced through: wordpress@apache krb5/libk5crypto3@1.21.3-5
  • Introduced through: wordpress@apache krb5/libkrb5-3@1.21.3-5
  • Introduced through: wordpress@apache 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.

In MIT Kerberos 5 (aka krb5) before 1.22.3, there is an integer underflow and resultant out-of-bounds read if an application calls gss_accept_sec_context() on a system with a NegoEx mechanism registered in /etc/gss/mech. An unauthenticated remote attacker can trigger this, possibly causing the process to terminate in parse_message.

Remediation

Upgrade Debian:13 krb5 to version 1.21.3-5+deb13u1 or higher.

References

low severity

Memory Leak

  • 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@apache krb5/libgssapi-krb5-2@1.21.3-5
  • Introduced through: wordpress@apache krb5/libk5crypto3@1.21.3-5
  • Introduced through: wordpress@apache krb5/libkrb5-3@1.21.3-5
  • Introduced through: wordpress@apache 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

NULL Pointer Dereference

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.21.3-5, krb5/libk5crypto3@1.21.3-5 and others
  • Fixed in: 1.21.3-5+deb13u1

Detailed paths

  • Introduced through: wordpress@apache krb5/libgssapi-krb5-2@1.21.3-5
  • Introduced through: wordpress@apache krb5/libk5crypto3@1.21.3-5
  • Introduced through: wordpress@apache krb5/libkrb5-3@1.21.3-5
  • Introduced through: wordpress@apache 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.

In MIT Kerberos 5 (aka krb5) before 1.22.3, there is a NULL pointer dereference if an application calls gss_accept_sec_context() on a system with a NegoEx mechanism registered in /etc/gss/mech. An unauthenticated remote attacker can trigger this, causing the process to terminate in parse_nego_message.

Remediation

Upgrade Debian:13 krb5 to version 1.21.3-5+deb13u1 or higher.

References

low severity

CVE-2025-29070

  • Vulnerable module: lcms2/liblcms2-2
  • Introduced through: lcms2/liblcms2-2@2.16-2+deb13u2

Detailed paths

  • Introduced through: wordpress@apache lcms2/liblcms2-2@2.16-2+deb13u2

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

CVE-2024-38949

  • Vulnerable module: libde265/libde265-0
  • Introduced through: libde265/libde265-0@1.0.15-1+b3

Detailed paths

  • Introduced through: wordpress@apache 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

CVE-2024-38950

  • Vulnerable module: libde265/libde265-0
  • Introduced through: libde265/libde265-0@1.0.15-1+b3

Detailed paths

  • Introduced through: wordpress@apache 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

CVE-2025-61147

  • Vulnerable module: libde265/libde265-0
  • Introduced through: libde265/libde265-0@1.0.15-1+b3

Detailed paths

  • Introduced through: wordpress@apache 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.

strukturag libde265 commit d9fea9d wa discovered to contain a segmentation fault via the component decoder_context::compute_framedrop_table().

Remediation

There is no fixed version for Debian:13 libde265.

References

low severity
new

CVE-2026-41069

  • Vulnerable module: libheif/libheif-plugin-aomenc
  • Introduced through: libheif/libheif-plugin-aomenc@1.19.8-1, libheif/libheif-plugin-dav1d@1.19.8-1 and others

Detailed paths

  • Introduced through: wordpress@apache libheif/libheif-plugin-aomenc@1.19.8-1
  • Introduced through: wordpress@apache libheif/libheif-plugin-dav1d@1.19.8-1
  • Introduced through: wordpress@apache libheif/libheif-plugin-libde265@1.19.8-1
  • Introduced through: wordpress@apache libheif/libheif-plugin-x265@1.19.8-1
  • Introduced through: wordpress@apache 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 a HEIF and AVIF file format decoder and encoder. In versions 1.21.2 and prior, a malformed HEIF sequence file can trigger an out-of-bounds read in core sequence parsing logic, causing DoS. A malformed file can have stco.entry_count == 0 (creating no chunks) while still passing validation because saio.entry_count == 0 matches, but with saiz.sample_count > 0 the SampleAuxInfoReader constructor still enters its loop. This leads to an out-of-bounds dereference on the empty chunks[0] in chunked mode.

Remediation

There is no fixed version for Debian:13 libheif.

References

low severity
new

Heap-based Buffer Overflow

  • Vulnerable module: libheif/libheif-plugin-aomenc
  • Introduced through: libheif/libheif-plugin-aomenc@1.19.8-1, libheif/libheif-plugin-dav1d@1.19.8-1 and others

Detailed paths

  • Introduced through: wordpress@apache libheif/libheif-plugin-aomenc@1.19.8-1
  • Introduced through: wordpress@apache libheif/libheif-plugin-dav1d@1.19.8-1
  • Introduced through: wordpress@apache libheif/libheif-plugin-libde265@1.19.8-1
  • Introduced through: wordpress@apache libheif/libheif-plugin-x265@1.19.8-1
  • Introduced through: wordpress@apache 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 a HEIF and AVIF file format decoder and encoder. Versions 1.21.2 and below contain a heap buffer overflow in MaskImageCodec::decode_mask_image(). When decoding a HEIF file containing a mask image (mski), the function copies the full iloc extent data into a pixel buffer using memcpy(dst, data.data(), data.size()). The copy length data.size() is determined by the iloc extent in the file (attacker-controlled), while the destination buffer is sized based on the declared image dimensions. Because no upper-bound check exists on the data length, a crafted file whose iloc extent exceeds the pixel buffer allocation overflows the heap. The vulnerable single-memcpy branch is reached when the mskC property specifies bits_per_pixel = 8 and the ispe property declares an even width ≥ 64 (so that stride == width), with no changes to default security limits or external codec plugins required. This issue has been fixed in version 1.22.0.

Remediation

There is no fixed version for Debian:13 libheif.

References

low severity
new

Information Exposure

  • Vulnerable module: libheif/libheif-plugin-aomenc
  • Introduced through: libheif/libheif-plugin-aomenc@1.19.8-1, libheif/libheif-plugin-dav1d@1.19.8-1 and others

Detailed paths

  • Introduced through: wordpress@apache libheif/libheif-plugin-aomenc@1.19.8-1
  • Introduced through: wordpress@apache libheif/libheif-plugin-dav1d@1.19.8-1
  • Introduced through: wordpress@apache libheif/libheif-plugin-libde265@1.19.8-1
  • Introduced through: wordpress@apache libheif/libheif-plugin-x265@1.19.8-1
  • Introduced through: wordpress@apache 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 a HEIF and AVIF file format decoder and encoder. In versions 1.21.2 and prior, when decoding a HEIF grid image with strict_decoding=false (the default), a corrupted tile silently fails to decode and the library returns heif_error_Ok with no indication of failure, leading to an uninitialized heap memory information leak. The canvas is allocated via create_clone_image_at_new_size() → plane.alloc() → new (std::nothrow) uint8_t[allocation_size] which does not zero the memory; only the alpha plane is explicitly initialized via fill_plane(), so the Y, Cb, and Cr planes contain whatever was previously at that heap address. The failed tile's region of the canvas is never written. It retains uninitialized heap data that is delivered to the caller as decoded pixel values (4,096 bytes per Y/Cb/Cr plane = 12,288+ bytes total). Any application using libheif to decode grid-based HEIF/AVIF files with default settings is vulnerable: a crafted .heic or .avif file causes 4,096+ bytes of heap memory to appear as pixel values in the decoded image, and the calling application receives heif_error_Ok, so it has no indication the output contains heap garbage. In server-side image processing, an uploaded crafted HEIF decoded and re-encoded (e.g., as PNG/JPEG for thumbnails, CDN, social media) can leak cross-user data such as auth tokens, database results, and other users' image data. This issue has been fixed in version 1.22.0.

Remediation

There is no fixed version for Debian:13 libheif.

References

low severity
new

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: libheif/libheif-plugin-aomenc
  • Introduced through: libheif/libheif-plugin-aomenc@1.19.8-1, libheif/libheif-plugin-dav1d@1.19.8-1 and others

Detailed paths

  • Introduced through: wordpress@apache libheif/libheif-plugin-aomenc@1.19.8-1
  • Introduced through: wordpress@apache libheif/libheif-plugin-dav1d@1.19.8-1
  • Introduced through: wordpress@apache libheif/libheif-plugin-libde265@1.19.8-1
  • Introduced through: wordpress@apache libheif/libheif-plugin-x265@1.19.8-1
  • Introduced through: wordpress@apache 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 a HEIF and AVIF file format decoder and encoder. In versions 1.21.2 and below, a crafted 800-byte HEIF sequence file causes an infinite loop in Box_stts::get_sample_duration(), consuming 100% CPU indefinitely with zero progress, leading to DoS. The loop has no iteration limit or timeout and is triggered during file open (parsing) - before any user interaction or image decoding. The process stays alive (no crash, no error logged), making it invisible to crash-based monitoring. This issue has been fixed in version 1.22.0.

Remediation

There is no fixed version for Debian:13 libheif.

References

low severity
new

Out-of-bounds Read

  • Vulnerable module: libheif/libheif-plugin-aomenc
  • Introduced through: libheif/libheif-plugin-aomenc@1.19.8-1, libheif/libheif-plugin-dav1d@1.19.8-1 and others

Detailed paths

  • Introduced through: wordpress@apache libheif/libheif-plugin-aomenc@1.19.8-1
  • Introduced through: wordpress@apache libheif/libheif-plugin-dav1d@1.19.8-1
  • Introduced through: wordpress@apache libheif/libheif-plugin-libde265@1.19.8-1
  • Introduced through: wordpress@apache libheif/libheif-plugin-x265@1.19.8-1
  • Introduced through: wordpress@apache 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 a HEIF and AVIF file format decoder and encoder. Versions 1.21.2 and prior contain a heap buffer over-read in HeifPixelImage::overlay() in libheif/pixelimage.cc. When compositing an overlay image (iovl) whose child image has a different bit depth for the alpha channel than for the color channels, the function indexes into the alpha plane using the color channel stride (in_stride) instead of the previously retrieved alpha_stride, causing reads past the end of the alpha buffer (up to 3,123 bytes for a 100×50 image with 10-bit color and 8-bit alpha). A crafted HEIF file can exploit this to cause a denial of service (crash) or potentially disclose adjacent heap memory through leaked bytes embedded in the decoded output pixels. This issue has been fixed in versionThis issue has been fixed in version 1.22.0.

Remediation

There is no fixed version for Debian:13 libheif.

References

low severity
new

Out-of-bounds Write

  • Vulnerable module: libheif/libheif-plugin-aomenc
  • Introduced through: libheif/libheif-plugin-aomenc@1.19.8-1, libheif/libheif-plugin-dav1d@1.19.8-1 and others

Detailed paths

  • Introduced through: wordpress@apache libheif/libheif-plugin-aomenc@1.19.8-1
  • Introduced through: wordpress@apache libheif/libheif-plugin-dav1d@1.19.8-1
  • Introduced through: wordpress@apache libheif/libheif-plugin-libde265@1.19.8-1
  • Introduced through: wordpress@apache libheif/libheif-plugin-x265@1.19.8-1
  • Introduced through: wordpress@apache 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 a HEIF and AVIF file format decoder and encoder. Versions 1.21.2 and prior contain a heap-buffer-overflow (write) vulnerability in the grid tile compositing, allowing an attacker to write 64 bytes of fully attacker-controlled data past the end of a chroma plane heap allocation by crafting a HEIF/AVIF file with a 1×4 grid of odd-height tiles. The overflow is triggered during normal image decoding with default build configuration. The written bytes are chroma (Cb/Cr) pixel values from the attacking tile, giving the attacker full control over the overflow content. This issue has been fixed in version 1.22.0.

Remediation

There is no fixed version for Debian:13 libheif.

References

low severity

Out-of-bounds Write

  • Vulnerable module: libtasn1-6
  • Introduced through: libtasn1-6@4.20.0-2

Detailed paths

  • Introduced through: wordpress@apache 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

Resource Exhaustion

  • Vulnerable module: openjpeg2/libopenjp2-7
  • Introduced through: openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u2

Detailed paths

  • Introduced through: wordpress@apache openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u2

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

Resource Exhaustion

  • Vulnerable module: openjpeg2/libopenjp2-7
  • Introduced through: openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u2

Detailed paths

  • Introduced through: wordpress@apache openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u2

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

Resource Exhaustion

  • Vulnerable module: openjpeg2/libopenjp2-7
  • Introduced through: openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u2

Detailed paths

  • Introduced through: wordpress@apache openjpeg2/libopenjp2-7@2.5.3-2.1~deb13u2

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

Out-of-bounds Read

  • Vulnerable module: openldap/libldap2
  • Introduced through: openldap/libldap2@2.6.10+dfsg-1

Detailed paths

  • Introduced through: wordpress@apache 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

low severity
new

CVE-2026-34180

  • Vulnerable module: openssl
  • Introduced through: openssl@3.5.6-1~deb13u1, openssl/libssl3t64@3.5.6-1~deb13u1 and others
  • Fixed in: 3.5.6-1~deb13u2

Detailed paths

  • Introduced through: wordpress@apache openssl@3.5.6-1~deb13u1
  • Introduced through: wordpress@apache openssl/libssl3t64@3.5.6-1~deb13u1
  • Introduced through: wordpress@apache openssl/openssl-provider-legacy@3.5.6-1~deb13u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Issue summary: Parsing a crafted DER-encoded ASN.1 structure with a primitive element whose content exceeds 2 gigabytes in length may cause a heap buffer over-read on 64-bit Unix and Unix-like platforms.

Impact summary: The heap buffer over-read may crash the application (Denial of Service) or to load into the decoded ASN.1 object contents of memory beyond the end of the input buffer. More typically such ASN.1 elements would instead be truncated.

An integer truncation in OpenSSL's ASN.1 decoder causes the content length of an ASN.1 primitive element to be mishandled when it exceeds 2 gigabytes. In the worst case the truncated length is treated as a request to scan the binary content for a terminating zero byte, possibly causing OpenSSL to read either less than or beyond the end of the allocated buffer.

Applications that pass attacker-supplied data to d2i_X509(), d2i_PKCS7(), or any other d2i_* decoding function are affected. OpenSSL's own command-line tools are not vulnerable, as data read through the BIO layer is checked before it reaches the affected code. The issue only affects 64-bit Unix and Unix-like platforms; 32-bit platforms and 64-bit Windows are not affected.

The FIPS modules in 4.0, 3.6, 3.5, 3.4 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.

Remediation

Upgrade Debian:13 openssl to version 3.5.6-1~deb13u2 or higher.

References

low severity
new

CVE-2026-34181

  • Vulnerable module: openssl
  • Introduced through: openssl@3.5.6-1~deb13u1, openssl/libssl3t64@3.5.6-1~deb13u1 and others
  • Fixed in: 3.5.6-1~deb13u2

Detailed paths

  • Introduced through: wordpress@apache openssl@3.5.6-1~deb13u1
  • Introduced through: wordpress@apache openssl/libssl3t64@3.5.6-1~deb13u1
  • Introduced through: wordpress@apache openssl/openssl-provider-legacy@3.5.6-1~deb13u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Issue Summary: The PKCS#12 file processing fails to perform sufficient input validation for files that use Password-Based Message Authentication Code 1 (PBMAC1) integrity mechanism allowing a certificate and private key forgery.

Impact Summary: An attacker impersonating a user can cause a service reading PKCS#12 files to accept forged certificates and private keys with a 1 in 256 probability.

If a service accepting PKCS#12 files is using passwords for authenticating the received files, the attacker can create unencrypted PKCS#12 files that use PBMAC1 authentication that specifies an HMAC key of only one byte, allowing them to craft a file that will be accepted with a 1 in 256 probability. That would then cause the service to accept a certificate and private key controlled by the attacker.

The FIPS modules are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.

Remediation

Upgrade Debian:13 openssl to version 3.5.6-1~deb13u2 or higher.

References

low severity
new

CVE-2026-34182

  • Vulnerable module: openssl
  • Introduced through: openssl@3.5.6-1~deb13u1, openssl/libssl3t64@3.5.6-1~deb13u1 and others
  • Fixed in: 3.5.6-1~deb13u2

Detailed paths

  • Introduced through: wordpress@apache openssl@3.5.6-1~deb13u1
  • Introduced through: wordpress@apache openssl/libssl3t64@3.5.6-1~deb13u1
  • Introduced through: wordpress@apache openssl/openssl-provider-legacy@3.5.6-1~deb13u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Issue Summary: Cryptographic Message Services (CMS) processing fails to perform sufficient input validation on the cipher and tag length fields of AuthEnvelopedData containers, leading to various potential compromises.

Impact Summary: Attackers making use of these vulnerabilities may achieve key-equivalent functionality for a given CMS recipient and/or bypass integrity validation for a given message.

In one use case, an attacker may send a CMS message containing AuthEnvelopedData with the cipher specified as a non-AEAD cipher. OpenSSL erroneously allows this selection, and attempts to decrypt and validate the message.

An on-path attacker who captures one legitimate AES-GCM AuthEnvelopedData addressed to the victim can re-emit it with the recipientInfos set left byte-for-byte intact, so the victim's private key still unwraps the genuine CEK (the content-encryption key), but with the inner OID rewritten to AES-256-OFB (Output Feedback Mode, an unauthenticated keystream mode) and with an attacker-chosen IV and ciphertext. The victim initializes AES-256-OFB under the real CEK, never consults the MAC field, and CMS_decrypt() returns success.

If the application under attack responds to the attacker with any indicator showing success or failure of the decryption effort, it is possible for the attacker to use this as an oracle to obtain key equivalent functionality for the CEK used for the chosen recipient of the message.

In another use case, an attacker can reduce the tag length of the chosen AEAD cipher for a given AuthEnvelopedData container to be a single byte long, allowing an attacker to brute force CMS decryption, producing an integrity bypass for applications that trust CMS_decrypt() to reject modified content.

The FIPS modules are not affected by this issue.

Remediation

Upgrade Debian:13 openssl to version 3.5.6-1~deb13u2 or higher.

References

low severity
new

CVE-2026-34183

  • Vulnerable module: openssl
  • Introduced through: openssl@3.5.6-1~deb13u1, openssl/libssl3t64@3.5.6-1~deb13u1 and others
  • Fixed in: 3.5.6-1~deb13u2

Detailed paths

  • Introduced through: wordpress@apache openssl@3.5.6-1~deb13u1
  • Introduced through: wordpress@apache openssl/libssl3t64@3.5.6-1~deb13u1
  • Introduced through: wordpress@apache openssl/openssl-provider-legacy@3.5.6-1~deb13u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Issue summary: Remote peer may exhaust heap memory of the QUIC server or client by flooding it with packets containing PATH_CHALLENGE frames.

Impact summary: A malicious remote peer can cause an unbounded memory allocation which can lead to an abnormal termination of the application acting as a QUIC client or server and a Denial of Service.

A remote peer may exhaust heap memory by flooding the local QUIC stack with PATH_CHALLENGE frames. The local QUIC stack allocates a PATH_RESPONSE frame for every PATH_CHALLENGE it receives. The allocated PATH_RESPONSE frame gets freed only when the remote peer acknowledges reception of the PATH_RESPONSE frame which will not be done by a malicious peer.

The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue. The QUIC stack is outside of OpenSSL FIPS module boundary.

Remediation

Upgrade Debian:13 openssl to version 3.5.6-1~deb13u2 or higher.

References

low severity
new

CVE-2026-42764

  • Vulnerable module: openssl
  • Introduced through: openssl@3.5.6-1~deb13u1, openssl/libssl3t64@3.5.6-1~deb13u1 and others
  • Fixed in: 3.5.6-1~deb13u2

Detailed paths

  • Introduced through: wordpress@apache openssl@3.5.6-1~deb13u1
  • Introduced through: wordpress@apache openssl/libssl3t64@3.5.6-1~deb13u1
  • Introduced through: wordpress@apache openssl/openssl-provider-legacy@3.5.6-1~deb13u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Issue summary: Receiving a QUIC initial packet with an invalid token may trigger a NULL pointer dereference in the OpenSSL QUIC server with address validation disabled.

Impact summary: NULL pointer dereference typically causes abnormal termination of the affected QUIC server process and a Denial of Service.

If the address validation is disabled in the OpenSSL QUIC server implementation, an attacker can crash the server by sending an initial packet with an invalid or expired token.

By default, the client address validation is enabled in the OpenSSL QUIC server implementation, which makes the default configuration not vulnerable to this issue. However if the SSL_LISTENER_FLAG_NO_VALIDATE is used with the SSL_new_listener() call, the address validation is disabled making the vulnerable code reachable.

The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.

Remediation

Upgrade Debian:13 openssl to version 3.5.6-1~deb13u2 or higher.

References

low severity
new

CVE-2026-42766

  • Vulnerable module: openssl
  • Introduced through: openssl@3.5.6-1~deb13u1, openssl/libssl3t64@3.5.6-1~deb13u1 and others
  • Fixed in: 3.5.6-1~deb13u2

Detailed paths

  • Introduced through: wordpress@apache openssl@3.5.6-1~deb13u1
  • Introduced through: wordpress@apache openssl/libssl3t64@3.5.6-1~deb13u1
  • Introduced through: wordpress@apache openssl/openssl-provider-legacy@3.5.6-1~deb13u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Issue summary: A specially crafted password-encrypted CMS message can trigger a NULL pointer dereference during CMS decryption.

Impact summary: This NULL pointer dereference leads to an application crash and a Denial of Service.

The CMS PasswordRecipientInfo.keyDerivationAlgorithm field is defined as OPTIONAL in the ASN.1 specification and may therefore be absent in specially crafted inputs. During the password-based CMS decryption the OpenSSL CMS implementation dereferences this field without first checking whether it was present.

An attacker who supplies such a CMS message to an application performing password-based CMS decryption can trigger an application crash, leading to a Denial of Service.

Applications that process password-encrypted CMS messages may be affected.

The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.

Remediation

Upgrade Debian:13 openssl to version 3.5.6-1~deb13u2 or higher.

References

low severity
new

CVE-2026-42767

  • Vulnerable module: openssl
  • Introduced through: openssl@3.5.6-1~deb13u1, openssl/libssl3t64@3.5.6-1~deb13u1 and others
  • Fixed in: 3.5.6-1~deb13u2

Detailed paths

  • Introduced through: wordpress@apache openssl@3.5.6-1~deb13u1
  • Introduced through: wordpress@apache openssl/libssl3t64@3.5.6-1~deb13u1
  • Introduced through: wordpress@apache openssl/openssl-provider-legacy@3.5.6-1~deb13u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Issue summary: An attacker-controlled CMP (Certificate Management Protocol) server could trigger a NULL pointer dereference in a CMP client application.

Impact summary: A NULL pointer dereference causes a crash of the application and a Denial of Service.

An attacker controlling a CMP server (or acting as a man-in-the-middle) could craft a CMP response containing a CRMF (Certificate Request Message Format) CertRepMessage with an EncryptedValue structure where the symmAlg field has an algorithm OID but no parameters field. When the OpenSSL CMP client processes this response, the NULL dereference occurs, causing a crash of the CMP client.

Applications that process untrusted CMP/CRMF messages may be affected.

The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.

Remediation

Upgrade Debian:13 openssl to version 3.5.6-1~deb13u2 or higher.

References

low severity
new

CVE-2026-42768

  • Vulnerable module: openssl
  • Introduced through: openssl@3.5.6-1~deb13u1, openssl/libssl3t64@3.5.6-1~deb13u1 and others
  • Fixed in: 3.5.6-1~deb13u2

Detailed paths

  • Introduced through: wordpress@apache openssl@3.5.6-1~deb13u1
  • Introduced through: wordpress@apache openssl/libssl3t64@3.5.6-1~deb13u1
  • Introduced through: wordpress@apache openssl/openssl-provider-legacy@3.5.6-1~deb13u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Issue summary: The CMS_decrypt and PKCS7_decrypt functions are vulnerable to Bleichenbacher-style attack when an attacker is able to provide the CMS or S/MIME messages and observe the error code and/or decryption output.

Impact summary: The Bleichenbacher-style attack allows an attacker to use the victim's vulnerable application as a way to decrypt or sign messages with the victim's private RSA key.

The attack is possible in 2 variants.

  1. The decryption API (CMS_decrypt(), PKCS7_decrypt()) is used without providing the recipient certificate. In this case OpenSSL iterates over every KeyTransRecipientInfo (KTRI) without stopping at the first success.

An attacker who authors a message with two KTRI entries — the first one wrapping a real CEK under the victim's public key, the second with an arbitrary probe ciphertext — obtains opportunity to iterate the 2nd KTRI to get a valid PKCS#1 v1.5 padding if the error code of the application is available.

That is a Bleichenbacher oracle (Bleichenbacher, CRYPTO '98): an adaptive-chosen-ciphertext side channel from which the attacker decrypts any RSA ciphertext to the victim's key or forges any PKCS#1 v1.5 signature under it.

  1. When the decryption API (CMS_decrypt(), PKCS7_decrypt()) is provided with the recipient certificate, and the recipient is not found, a random key is substituted.

An attacker who authors a message and is able to compare both error code and the result of the decryption, can mount a Bleichenbacher oracle.

We are not aware of any applications that provide a remote attacker an opportunity to mount an attack described in these scenarios. We consider the existence of such application very unlikely, and for this reason this CVE has been evaluated as Low severity.

To avoid these attacks, when RSA PKCS#1 v1.5 Key Transport is in use, the invoked EVP_PKEY_decrypt() will use the implicit rejection mechanism described in draft-irtf-cfrg-rsa-guidance. In previous OpenSSL releases the implicit rejection was explicitly disabled.

The implicit rejection mechanism always returns a plaintext value, the symmetric key. This result is deterministic for the ciphertext and the private key. The length of the decryption result can happen to match the length of the key of the symmetric cipher that was used for the content encryption. When a certificate is not provided, the last RecipientInfo producing a key that looks valid will be used. It may cause getting garbage content on decryption. As a proper way to deal with this a recipient certificate has to be provided to identify the particular RecipientInfo for decryption.

The FIPS modules in 4.0, 3.6, 3.5, and 3.4 are not affected by this issue, as CMS and S/MIME processing happens outside the OpenSSL FIPS module boundary.

Remediation

Upgrade Debian:13 openssl to version 3.5.6-1~deb13u2 or higher.

References

low severity
new

CVE-2026-42769

  • Vulnerable module: openssl
  • Introduced through: openssl@3.5.6-1~deb13u1, openssl/libssl3t64@3.5.6-1~deb13u1 and others
  • Fixed in: 3.5.6-1~deb13u2

Detailed paths

  • Introduced through: wordpress@apache openssl@3.5.6-1~deb13u1
  • Introduced through: wordpress@apache openssl/libssl3t64@3.5.6-1~deb13u1
  • Introduced through: wordpress@apache openssl/openssl-provider-legacy@3.5.6-1~deb13u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Issue Summary: An error in the callback used to verify the certificate provided in a Root CA key update Certificate Management Protocol (CMP) message response rendered the certificate validation ineffectual, which could lead to escalation of credentials from the Registration Authority (RA) level to the root Certification Authority (root CA) level.

Impact Summary: The Registration Autority could replace the root CA certificate for the CMP clients with an arbitrary root CA certificate.

One of the parts of the Certificate Management Protocol (CMP), specified in RFC 9810, is Root Certification Authority (root CA) key Rollover, which is sent by the server in a message with type 'id-it-rootCaKeyUpdate'. As part of these messages, 'newWithOld' certificate, the new root CA certificate signed with the old root CA key, is provided, and verifying its signature is crucial for transferring the trust from the old CA key to the new one.

The 'id-it-rootCaKeyUpdate' messages are expected to be processed with OSSL_CMP_get1_rootCaKeyUpdate(), that is expected to verify the 'newWithOld' certificate. A typo in the certificate chain building code led to adding an incorrect certificate ('newWithOld' instead of 'oldRoot') to the certificate chain, rendering the certificate verification process ineffectual (only the issuer name and the algorithm OIDs were verified by other parts of the verification code).

An attacker who already has credentials that satisfy the CMP message protection checks can generate a new key pair and use a crafted self-signed certificate in its 'id-it-rootCaKeyUpdate' CMP messages which affected CMP clients would accept as a new trust anchor.

Significant preconditions for the attack (having valid RA-level credentials) are the reason the issue was assigned Low severity.

The FIPS modules are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.

Remediation

Upgrade Debian:13 openssl to version 3.5.6-1~deb13u2 or higher.

References

low severity
new

CVE-2026-42770

  • Vulnerable module: openssl
  • Introduced through: openssl@3.5.6-1~deb13u1, openssl/libssl3t64@3.5.6-1~deb13u1 and others
  • Fixed in: 3.5.6-1~deb13u2

Detailed paths

  • Introduced through: wordpress@apache openssl@3.5.6-1~deb13u1
  • Introduced through: wordpress@apache openssl/libssl3t64@3.5.6-1~deb13u1
  • Introduced through: wordpress@apache openssl/openssl-provider-legacy@3.5.6-1~deb13u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Issue summary: When EVP_PKEY_derive_set_peer() is called with a DHX (X9.42) peer key, the peer key is not properly checked for the subgroup membership.

Impact summary: A malicious peer which presents an X9.42 key carrying the victim's p and g parameters, a forged q = r (a small prime factor of the cofactor (p−1)/q_local), and a public value Y of order r can recover the victim's private key after a small number of key exchange attempts.

When EVP_PKEY_derive_set_peer() is called with a DHX (X9.42) peer key, the subgroup membership check Y^q ≡ 1 (mod p) is performed using the peer's own q parameter, not the local key's q. The peer's domain parameters are then matched against the domain parameters of the private key, but the value of q is not compared.

A malicious peer who presents an X9.42 key carrying the victim's p, g, a forged q = r (a small prime factor of the cofactor), and a public value Y of order r passes all checks. The shared secret then takes only r distinct values, leaking priv mod r. Repeating for each small-prime factor of the cofactor and combining via CRT recovers the full private key (Lim–Lee / small-subgroup-confinement attack).

The realistic attack surface is narrow: principally CMP deployments with long-lived RA/CA DHX keys and bespoke enterprise or government applications using X9.42 DHX static keys with interactive protocols and therefore this issue was assigned Low severity.

The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are affected by this issue.

Remediation

Upgrade Debian:13 openssl to version 3.5.6-1~deb13u2 or higher.

References

low severity
new

CVE-2026-45445

  • Vulnerable module: openssl
  • Introduced through: openssl@3.5.6-1~deb13u1, openssl/libssl3t64@3.5.6-1~deb13u1 and others
  • Fixed in: 3.5.6-1~deb13u2

Detailed paths

  • Introduced through: wordpress@apache openssl@3.5.6-1~deb13u1
  • Introduced through: wordpress@apache openssl/libssl3t64@3.5.6-1~deb13u1
  • Introduced through: wordpress@apache openssl/openssl-provider-legacy@3.5.6-1~deb13u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Issue summary: When an application drives an AES-OCB context through the public EVP_Cipher() one-shot interface, the application-supplied initialisation vector (IV) is silently discarded.

Impact summary: Every message encrypted under the same key uses the same effective nonce regardless of the IV supplied by the caller, resulting in (key, nonce) reuse and loss of confidentiality. If the same code path is used to compute the authentication tag, the tag depends only on the (key, IV) pair and not on the plaintext or ciphertext, allowing universal forgery of arbitrary ciphertext from a single captured message.

OpenSSL provides two ways to drive a cipher: the documented streaming interface (EVP_CipherUpdate / EVP_CipherFinal_ex) and a lower-level one-shot, EVP_Cipher(), whose documentation explicitly recommends against use by applications in favour of EVP_CipherUpdate() and EVP_CipherFinal_ex(). The OCB provider's streaming handler flushes the application-supplied IV into the OCB context before processing data; the one-shot handler did not. Every call to EVP_Cipher() on an AES-OCB context therefore ran with the all-zero key-derived offset state left by cipher initialisation, regardless of the caller's IV.

If EVP_EncryptFinal_ex() is subsequently used to obtain the authentication tag, the deferred IV setup runs at that point and clears the running checksum that should have been accumulated over the plaintext. The resulting tag is a function of (key, IV) only and verifies against any ciphertext produced under the same (key, IV) pair.

The OpenSSL SSL/TLS implementation is not affected: AES-OCB is not a TLS cipher suite, and libssl does not call EVP_Cipher() in any case. Applications that drive AES-OCB through the documented streaming AEAD API (EVP_CipherUpdate / EVP_CipherFinal_ex) are not affected. Only applications that combine the AES-OCB cipher with the EVP_Cipher() one-shot API are vulnerable.

The FIPS modules in 4.0, 3.6, 3.5, 3.4 and 3.0 are not affected by this issue, as AES-OCB is outside the OpenSSL FIPS module boundary.

Remediation

Upgrade Debian:13 openssl to version 3.5.6-1~deb13u2 or higher.

References

low severity
new

CVE-2026-45446

  • Vulnerable module: openssl
  • Introduced through: openssl@3.5.6-1~deb13u1, openssl/libssl3t64@3.5.6-1~deb13u1 and others
  • Fixed in: 3.5.6-1~deb13u2

Detailed paths

  • Introduced through: wordpress@apache openssl@3.5.6-1~deb13u1
  • Introduced through: wordpress@apache openssl/libssl3t64@3.5.6-1~deb13u1
  • Introduced through: wordpress@apache openssl/openssl-provider-legacy@3.5.6-1~deb13u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Issue summary: The implementations of AES-SIV (RFC 5297) and AES-GCM-SIV (RFC 8452) mishandle the authentication of AAD (Additional Authenticated Data) with an empty ciphertext allowing a forgery of such messages.

Impact summary: An attacker can forge empty messages with arbitrary AAD to the victim's application using these ciphers.

AES-SIV (RFC 5297) and AES-GCM-SIV (RFC 8452) are nonce-misuse-resistant AEAD modes: they accept a key, nonce, optional AAD (bytes that are authenticated but not encrypted), and plaintext, and produces ciphertext plus a 16-byte tag. On decrypt, EVP_DecryptFinal_ex() is documented to return success only if the tag is verified succesfully.

In OpenSSL's provider implementation of these ciphers, the expected tag is computed only when decryption function is invoked with non-empty data. If the caller supplies AAD and then calls EVP_DecryptFinal_ex() without invocation of the ciphertext update, which can happen when the received ciphertext length is zero, the tag is never recalculated and still holds its all-zeros value.

When AES-GCM-SIV is used, an attacker who sends arbitrary AAD, empty ciphertext, and all-zeros tag passes authentication under any key they do not know, single-shot. When AES-SIV is used, for mounting the attack it's necessary for the application to reuse the decryption context without resetting the key.

AES-SIV is implemented since OpenSSL 3.0. AES-GCM-SIV is implemented since OpenSSL 3.2.

No protocols implemented in OpenSSL itself (TLS/CMS/PKCS7/HPKE/QUIC) support either AES-GCM-SIV or AES-SIV. To mount an attack, the applications must implement their own protocol and use the EVP interface. Also they must skip the ciphertext update when a message with an empty ciphertext arrives.

The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as these algorithms are not FIPS approved and the affected code is outside the OpenSSL FIPS module boundary.

Remediation

Upgrade Debian:13 openssl to version 3.5.6-1~deb13u2 or higher.

References

low severity
new

CVE-2026-45447

  • Vulnerable module: openssl
  • Introduced through: openssl@3.5.6-1~deb13u1, openssl/libssl3t64@3.5.6-1~deb13u1 and others
  • Fixed in: 3.5.6-1~deb13u2

Detailed paths

  • Introduced through: wordpress@apache openssl@3.5.6-1~deb13u1
  • Introduced through: wordpress@apache openssl/libssl3t64@3.5.6-1~deb13u1
  • Introduced through: wordpress@apache openssl/openssl-provider-legacy@3.5.6-1~deb13u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Issue summary: A specially crafted PKCS#7 or S/MIME signed message could trigger a use-after-free during PKCS#7 signature verification.

Impact summary: A use-after-free may result in process crashes, heap corruption, or potentially remote code execution.

When processing a PKCS#7 or S/MIME signed message, if the SignedData digestAlgorithms field is present as an empty ASN.1 SET, OpenSSL may incorrectly free a caller-owned BIO during PKCS7_verify(). A subsequent use of the BIO by the calling application results in a use-after-free condition.

In the common case this occurs when the application later calls BIO_free() on the BIO originally passed to PKCS7_verify(). Depending on allocator behavior and application-specific BIO usage patterns, this may result in a crash or other memory corruption. In some application contexts this may potentially be exploitable for remote code execution.

Applications that process PKCS#7 or S/MIME signed messages using OpenSSL PKCS#7 APIs may be affected. Applications using the CMS APIs for this processing are not affected.

The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.

Remediation

Upgrade Debian:13 openssl to version 3.5.6-1~deb13u2 or higher.

References

low severity
new

CVE-2026-7383

  • Vulnerable module: openssl
  • Introduced through: openssl@3.5.6-1~deb13u1, openssl/libssl3t64@3.5.6-1~deb13u1 and others
  • Fixed in: 3.5.6-1~deb13u2

Detailed paths

  • Introduced through: wordpress@apache openssl@3.5.6-1~deb13u1
  • Introduced through: wordpress@apache openssl/libssl3t64@3.5.6-1~deb13u1
  • Introduced through: wordpress@apache openssl/openssl-provider-legacy@3.5.6-1~deb13u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Issue summary: A signed integer overflow when sizing the destination buffer for Unicode output in ASN1_mbstring_ncopy() can lead to a heap buffer overflow.

Impact summary: A heap buffer overflow may lead to a crash or possibly attacker controlled code execution or other undefined behaviour.

In ASN1_mbstring_copy() and ASN1_mbstring_ncopy() the destination size for Unicode output is computed in a signed int: by left shift of the input character count for BMPSTRING (UTF-16) and UNIVERSALSTRING (UTF-32), and by summing per-character byte counts for UTF8STRING. The calculation overflows when the input reaches around 2^30 characters. In the worst case (UNIVERSALSTRING at 2^30 characters) the size wraps to zero, OPENSSL_malloc(1) is called, and the subsequent character copy writes several gigabytes past the one-byte allocation.

X.509 certificate processing routes through ASN1_STRING_set_by_NID(), whose DIRSTRING_TYPE mask excludes UNIVERSALSTRING and whose per-NID size limits cap the input length; no network protocol or certificate-handling path in OpenSSL exercises the overflow. Triggering the bug requires an application that calls ASN1_mbstring_copy() or ASN1_mbstring_ncopy() directly, or registers a custom string type via ASN1_STRING_TABLE_add(), with attacker-controlled input on the order of half a gigabyte or more. For these reasons this issue was assigned Low severity.

The FIPS modules in 4.0, 3.6, 3.5, 3.4 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.

Remediation

Upgrade Debian:13 openssl to version 3.5.6-1~deb13u2 or higher.

References

low severity
new

CVE-2026-9076

  • Vulnerable module: openssl
  • Introduced through: openssl@3.5.6-1~deb13u1, openssl/libssl3t64@3.5.6-1~deb13u1 and others
  • Fixed in: 3.5.6-1~deb13u2

Detailed paths

  • Introduced through: wordpress@apache openssl@3.5.6-1~deb13u1
  • Introduced through: wordpress@apache openssl/libssl3t64@3.5.6-1~deb13u1
  • Introduced through: wordpress@apache openssl/openssl-provider-legacy@3.5.6-1~deb13u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Issue summary: When CMS password-based decryption (RFC 3211 / PWRI key unwrap) processes attacker-supplied CMS data, an attacker-chosen stream-mode KEK cipher can trigger a heap out-of-bounds read in kek_unwrap_key().

Impact summary: A heap buffer over-read may trigger a crash which leads to Denial of Service for an application if the input buffer ends at a memory page boundary and the following page is unmapped. There is no information disclosure as the over-read bytes are not revealed to the attacker.

The key unwrapping function performs a check-byte test as specified in the RFC that reads 7 bytes from a heap allocation that is based on the wrapped key length from the message. There is a minimum length check based on the block length of the wrapping cipher. However the cipher is selected from an OID carried in the attacker's PWRI keyEncryptionAlgorithm with no requirement that the cipher be a block cipher. When an attacker selects a stream-mode cipher the guard will be ineffective and the allocated buffer containing the unwrapped key can be too small to fit the check-bytes specified in the RFC and a buffer over-read can happen.

Applications calling CMS_decrypt() or CMS_decrypt_set1_password() (equivalently openssl cms -decrypt -pwri_password ...) on untrusted CMS data are vulnerable to this issue. No password knowledge is required: the over-read happens during the unwrap attempt before any authentication succeeds.

The over-read is limited to a few bytes and is not written to output, so there is no information disclosure. Triggering a crash requires the allocation to border unmapped memory, which is unlikely with the normal allocator.

The FIPS modules are not affected by this issue.

Remediation

Upgrade Debian:13 openssl to version 3.5.6-1~deb13u2 or higher.

References

low severity
new

CVE-2025-15649

  • Vulnerable module: perl
  • Introduced through: perl@5.40.1-6, perl/libperl5.40@5.40.1-6 and others

Detailed paths

  • Introduced through: wordpress@apache perl@5.40.1-6
  • Introduced through: wordpress@apache perl/libperl5.40@5.40.1-6
  • Introduced through: wordpress@apache perl/perl-base@5.40.1-6
  • Introduced through: wordpress@apache 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.

IO::Uncompress::Unzip versions before 2.215 for Perl propagate uncaught exception when parsing zip header with malformed DOS date.

_dosToUnixTime() decodes the local-file-header last-modification date field and calls Time::Local::timelocal() without an eval guard. A header whose date field decodes to an out-of-range month, day, or hour causes timelocal() to die.

The exception propagates out of IO::Uncompress::Unzip->new($file) where callers expect undef plus $UnzipError.

Remediation

There is no fixed version for Debian:13 perl.

References

low severity
new

CVE-2026-48959

  • Vulnerable module: perl
  • Introduced through: perl@5.40.1-6, perl/libperl5.40@5.40.1-6 and others

Detailed paths

  • Introduced through: wordpress@apache perl@5.40.1-6
  • Introduced through: wordpress@apache perl/libperl5.40@5.40.1-6
  • Introduced through: wordpress@apache perl/perl-base@5.40.1-6
  • Introduced through: wordpress@apache 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.

IO::Uncompress::Unzip versions before 2.220 for Perl allow CPU exhaustion via per-byte read loop in fastForward.

fastForward() compares length $offset (the digit count of the offset, 1 to 19) against the chunk size $c instead of $offset itself, so $c shrinks from 16 KiB to 1-19 bytes per iteration.

Extracting a named entry from an attacker supplied zip via IO::Uncompress::Unzip->new($zip, Name => $target) drives a per-byte read loop scaling with the entry's compressed size, up to the non-Zip64 4 GiB cap.

Remediation

There is no fixed version for Debian:13 perl.

References

low severity
new

CVE-2026-48961

  • Vulnerable module: perl
  • Introduced through: perl@5.40.1-6, perl/libperl5.40@5.40.1-6 and others

Detailed paths

  • Introduced through: wordpress@apache perl@5.40.1-6
  • Introduced through: wordpress@apache perl/libperl5.40@5.40.1-6
  • Introduced through: wordpress@apache perl/perl-base@5.40.1-6
  • Introduced through: wordpress@apache 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.

IO::Compress versions from 2.207 before 2.220 for Perl ship a zipdetails CLI tool that crashes with undefined subroutine on Info-ZIP Unix Extra Field with 8-byte UID or GID.

When decode_ux() in bin/zipdetails handles an Info-ZIP Unix Extra Field (tag 0x7875) with UID Size or GID Size set to 8, causing zipdetails to decode an 8-byte UID or GID value, it dispatches through decodeLitteEndian(), which calls a misnamed helper unpackValueQ. The actual function defined in the same file is unpackValue_Q (with underscore); the call raises 'Undefined subroutine &main::unpackValueQ' and the script exits with status 255.

Library callers of IO::Compress and IO::Uncompress are not affected; the defect is in the bundled CLI tool.

Remediation

There is no fixed version for Debian:13 perl.

References

low severity
new

CVE-2026-48962

  • Vulnerable module: perl
  • Introduced through: perl@5.40.1-6, perl/libperl5.40@5.40.1-6 and others

Detailed paths

  • Introduced through: wordpress@apache perl@5.40.1-6
  • Introduced through: wordpress@apache perl/libperl5.40@5.40.1-6
  • Introduced through: wordpress@apache perl/perl-base@5.40.1-6
  • Introduced through: wordpress@apache 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.

IO::Compress versions before 2.220 for Perl can execute arbitrary code in File::GlobMapper via an attacker-controlled output glob.

_parseOutputGlob() wraps the caller-supplied output glob string in double quotes and stores it in the parser state; _getFiles() then runs the stored expression through eval STRING. A literal double quote in the output glob closes the dquote wrapper, and the characters that follow are evaluated as Perl.

Arbitrary Perl in the output glob executes at the calling process's privilege.

Remediation

There is no fixed version for Debian:13 perl.

References

low severity
new

CVE-2026-7010

  • Vulnerable module: perl
  • Introduced through: perl@5.40.1-6, perl/libperl5.40@5.40.1-6 and others

Detailed paths

  • Introduced through: wordpress@apache perl@5.40.1-6
  • Introduced through: wordpress@apache perl/libperl5.40@5.40.1-6
  • Introduced through: wordpress@apache perl/perl-base@5.40.1-6
  • Introduced through: wordpress@apache 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.

HTTP::Tiny versions before 0.093 for Perl do not validate CRLF in HTTP request lines or control field header values.

The unvalidated inputs are the method and URI in the request line, the URL host that becomes the Host: header, and HTTP/1.1 control data field values.

An attacker who controls one of these inputs, for example a user supplied URL passed to a webhook or URL fetch endpoint, can inject additional headers and smuggle requests to the upstream server.

Remediation

There is no fixed version for Debian:13 perl.

References

low severity

CVE-2024-56433

  • 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@apache shadow/login.defs@1:4.17.4-2
  • Introduced through: wordpress@apache 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

CVE-2025-70873

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.46.1-7+deb13u1

Detailed paths

  • Introduced through: wordpress@apache sqlite3/libsqlite3-0@3.46.1-7+deb13u1

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 information disclosure issue in the zipfileInflate function in the zipfile extension in SQLite v3.51.1 and earlier allows attackers to obtain heap memory via supplying a crafted ZIP file.

Remediation

There is no fixed version for Debian:13 sqlite3.

References

low severity

Time-of-check Time-of-use (TOCTOU)

  • 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@apache util-linux@2.41-5
  • Introduced through: wordpress@apache util-linux/bsdutils@1:2.41-5
  • Introduced through: wordpress@apache util-linux/libblkid1@2.41-5
  • Introduced through: wordpress@apache util-linux/liblastlog2-2@2.41-5
  • Introduced through: wordpress@apache util-linux/libmount1@2.41-5
  • Introduced through: wordpress@apache util-linux/libsmartcols1@2.41-5
  • Introduced through: wordpress@apache util-linux/libuuid1@2.41-5
  • Introduced through: wordpress@apache util-linux/login@1:4.16.0-2+really2.41-5
  • Introduced through: wordpress@apache 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.

util-linux is a random collection of Linux utilities. Prior to version 2.41.4, a TOCTOU (Time-of-Check-Time-of-Use) vulnerability has been identified in the SUID binary /usr/bin/mount from util-linux. The mount binary, when setting up loop devices, validates the source file path with user privileges via fork() + setuid() + realpath(), but subsequently re-canonicalizes and opens it with root privileges (euid=0) without verifying that the path has not been replaced between both operations. Neither O_NOFOLLOW, nor inode comparison, nor post-open fstat() are employed. This allows a local unprivileged user to replace the source file with a symlink pointing to any root-owned file or device during the race window, causing the SUID binary to open and mount it as root. Exploitation requires an /etc/fstab entry with user,loop options whose path points to a directory where the attacker has write permission, and that /usr/bin/mount has the SUID bit set (the default configuration on virtually all Linux distributions). The impact is unauthorized read access to root-protected files and block devices, including backup images, disk volumes, and any file containing a valid filesystem. This issue has been patched in version 2.41.4.

Remediation

There is no fixed version for Debian:13 util-linux.

References