Vulnerabilities |
259 via 1064 paths |
|---|---|
Dependencies |
186 |
Source |
Docker |
Target OS |
debian:13 |
critical severity
- Vulnerable module: perl
- Introduced through: perl@5.40.1-6, perl/libperl5.40@5.40.1-6 and others
- Fixed in: 5.40.1-6+deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › perl@5.40.1-6
-
Introduced through: php@8.2-apache › perl/libperl5.40@5.40.1-6
-
Introduced through: php@8.2-apache › perl/perl-base@5.40.1-6
-
Introduced through: php@8.2-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 before 5.40.5-RC1, from 5.41.0 before 5.42.3-RC1, from 5.43.0 before 5.43.11 have a heap buffer overflow when compiling regular expressions with a repeated fixed string on 32-bit builds.
Perl_study_chunk in regcomp_study.c checked the size of the joined substring buffer in characters rather than bytes. For a quantified fixed substring with a large minimum count, the byte length mincount * l could overflow SSize_t, producing an undersized SvGROW allocation; the subsequent copy writes past the end of the buffer.
A caller that compiles an attacker-controlled regular expression on a 32-bit perl build triggers a heap buffer overflow at compile time.
Remediation
Upgrade Debian:13 perl to version 5.40.1-6+deb13u1 or higher.
References
critical severity
- Vulnerable module: perl
- Introduced through: perl@5.40.1-6, perl/libperl5.40@5.40.1-6 and others
- Fixed in: 5.40.1-6+deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › perl@5.40.1-6
-
Introduced through: php@8.2-apache › perl/libperl5.40@5.40.1-6
-
Introduced through: php@8.2-apache › perl/perl-base@5.40.1-6
-
Introduced through: php@8.2-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 before 5.40.5-RC1, from 5.41.0 before 5.42.3-RC1, from 5.43.0 before 5.43.10 produce silently incorrect regular expression matches when an alternation of more than 65535 fixed string branches is compiled into a trie in Perl_study_chunk.
When such branches are combined into a trie, the delta between the first branch and the shared tail is stored in a 16-bit field. A branch count above 65535 overflows the field, and the trie's match decision table is truncated with no warning or error.
A pattern of this shape produces false positive matches (matching strings it should not) and false negative matches (failing to match strings it should). When such a pattern gates an access or filtering decision, the result is wrong.
Remediation
Upgrade Debian:13 perl to version 5.40.1-6+deb13u1 or higher.
References
critical severity
- Vulnerable module: perl
- Introduced through: perl@5.40.1-6, perl/libperl5.40@5.40.1-6 and others
- Fixed in: 5.40.1-6+deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › perl@5.40.1-6
-
Introduced through: php@8.2-apache › perl/libperl5.40@5.40.1-6
-
Introduced through: php@8.2-apache › perl/perl-base@5.40.1-6
-
Introduced through: php@8.2-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
Upgrade Debian:13 perl to version 5.40.1-6+deb13u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-42496
- https://github.com/jib/archive-tar-new/commit/17c873492a05eddc0de18c1485e0b2cccd5a9158.patch
- https://metacpan.org/release/BINGOS/Archive-Tar-3.08/changes
- https://www.cve.org/CVERecord?id=CVE-2026-42497
- https://access.redhat.com/errata/RHSA-2026:30851
- https://access.redhat.com/errata/RHSA-2026:30852
- https://access.redhat.com/errata/RHSA-2026:30856
- https://access.redhat.com/errata/RHSA-2026:30857
- https://access.redhat.com/security/cve/CVE-2026-42496
- https://bugzilla.redhat.com/show_bug.cgi?id=2481314
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-42496.json
high severity
- Vulnerable module: libssh2/libssh2-1t64
- Introduced through: libssh2/libssh2-1t64@1.11.1-1+deb13u1
- Fixed in: 1.11.1-1+deb13u2
Detailed paths
-
Introduced through: php@8.2-apache › libssh2/libssh2-1t64@1.11.1-1+deb13u1
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.
libssh2 through 1.11.1, fixed in commit 5e47761, contains a double-free vulnerability in the sftp_open() function in src/sftp.c that allows a malicious SSH server to corrupt the heap of any authenticated client opening an SFTP session. When a server responds to SSH_FXP_OPEN with SSH_FXP_STATUS containing FX_OK, the response data buffer is freed, and if a subsequent sftp_packet_require() call returns a specific error such as LIBSSH2_ERROR_CHANNEL_PACKET_EXCEEDED, the same pointer is freed a second time, enabling tcache dup conditions on glibc systems that allow overlapping allocations and function pointer overwrites.
Remediation
Upgrade Debian:13 libssh2 to version 1.11.1-1+deb13u2 or higher.
References
high severity
new
- Vulnerable module: libxml2
- Introduced through: libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3
Detailed paths
-
Introduced through: php@8.2-apache › libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3
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 with Python bindings enabled. A remote attacker could exploit this vulnerability by providing a specially crafted XML document containing a Document Type Definition (DTD) with enumerated attribute values. This triggers a double-free error in the SAX attributeDecl callback handler, where a string is freed twice. This flaw can lead to a denial of service (DoS) due to a reproducible crash in Python applications using the libxml2 SAX bindings.
Remediation
There is no fixed version for Debian:13 libxml2.
References
high severity
- Vulnerable module: perl
- Introduced through: perl@5.40.1-6, perl/libperl5.40@5.40.1-6 and others
- Fixed in: 5.40.1-6+deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › perl@5.40.1-6
-
Introduced through: php@8.2-apache › perl/libperl5.40@5.40.1-6
-
Introduced through: php@8.2-apache › perl/perl-base@5.40.1-6
-
Introduced through: php@8.2-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 before 5.40.5-RC1, from 5.41.0 before 5.42.3-RC1, from 5.43.0 before 5.43.11 have an integer overflow in S_measure_struct leading to an out-of-bounds heap read in pack and unpack.
S_measure_struct adds each item's size times its repeat count to a running total with no overflow check, so a large repeat count in a pack or unpack template wraps the signed SSize_t total negative. The @, X, and x position codes then guard their moves with a signed length comparison that passes when the length is negative, advancing the buffer pointer out of bounds.
A template derived from untrusted input can read heap memory past the buffer and return it to the caller.
Remediation
Upgrade Debian:13 perl to version 5.40.1-6+deb13u1 or higher.
References
high severity
new
- Vulnerable module: libxml2
- Introduced through: libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3
Detailed paths
-
Introduced through: php@8.2-apache › libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3
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.
In libxml2 before 2.15.4, there is a heap-based buffer overflow in xmlXPtrEvalXPtrPart because of xmlXPtrEval xpointer length saturation.
Remediation
There is no fixed version for Debian:13 libxml2.
References
high severity
new
- Vulnerable module: libxml2
- Introduced through: libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3
Detailed paths
-
Introduced through: php@8.2-apache › libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3
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.
In xinclude in libxml2 before 2.15.4, xmlXIncludeProcess and xmlXIncludeProcessTree do not propagate parseFlags. This has security relevance for, for example, the XML_PARSE_NONET flag, if (without it) a custom resource loader accesses the internet and triggers XML external entity injection, SSRF, or a denial of service (e.g., for an attacker-controlled internet resource that is intentionally slow).
Remediation
There is no fixed version for Debian:13 libxml2.
References
high severity
new
- Vulnerable module: libxml2
- Introduced through: libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3
Detailed paths
-
Introduced through: php@8.2-apache › libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3
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.
In libxml2 before 2.15.4, xmlURIEscapeStr in uri.c has an integer overflow.
Remediation
There is no fixed version for Debian:13 libxml2.
References
high severity
new
- Vulnerable module: libxml2
- Introduced through: libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3
Detailed paths
-
Introduced through: php@8.2-apache › libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3
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.
In libxml2 before 2.15.4, xmlDictAddQString in dict.c has an integer overflow and resultant heap-based buffer overflow.
Remediation
There is no fixed version for Debian:13 libxml2.
References
high severity
new
- Vulnerable module: libxml2
- Introduced through: libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3
Detailed paths
-
Introduced through: php@8.2-apache › libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3
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.
In libxml2 before 2.15.4, xmlSnprintfElements in valid.c has a strcat stack-based buffer overflow.
Remediation
There is no fixed version for Debian:13 libxml2.
References
high severity
new
- Vulnerable module: pcre2/libpcre2-8-0
- Introduced through: pcre2/libpcre2-8-0@10.46-1~deb13u1
- Fixed in: 10.46-1~deb13u2
Detailed paths
-
Introduced through: php@8.2-apache › pcre2/libpcre2-8-0@10.46-1~deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream pcre2 package and not the pcre2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
In PCRE2 before 10.48, pcre2_jit_match mishandles a previously copied subject being passed in as a context. An incorrect free operation can occur.
Remediation
Upgrade Debian:13 pcre2 to version 10.46-1~deb13u2 or higher.
References
high severity
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.46.1-7+deb13u1
- Fixed in: 3.46.1-7+deb13u2
Detailed paths
-
Introduced through: php@8.2-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.
SQLite before 3.53.2 contains memory corruption vulnerabilities in the FTS5 full-text search extension that allow attackers to cause process crashes, memory exhaustion, or arbitrary code execution by supplying a crafted database with malformed FTS5 page data. Attackers can trigger an out-of-bounds read in fts5LeafSeek() via an attacker-controlled loop bound and a heap buffer overflow write in fts5ChunkIterate() through a crafted continuation page causing an integer underflow, exploitable when an FTS5 MATCH query is executed against the malicious database.
Remediation
Upgrade Debian:13 sqlite3 to version 3.46.1-7+deb13u2 or higher.
References
high severity
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.46.1-7+deb13u1
- Fixed in: 3.46.1-7+deb13u2
Detailed paths
-
Introduced through: php@8.2-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.
SQLite before 3.53.2 contains a heap-based buffer overflow vulnerability in the FTS5 full-text search extension that allows attackers to cause a crash or execute arbitrary code by supplying a crafted database with malicious continuation page metadata specifying a szLeaf value smaller than 4. Attackers can trigger an integer underflow in fts5ChunkIterate() causing an inflated remaining byte count during FTS5 MATCH query processing, leading to a heap buffer overflow of attacker-controlled data in applications compiled with SQLITE_ENABLE_FTS5.
Remediation
Upgrade Debian:13 sqlite3 to version 3.46.1-7+deb13u2 or higher.
References
high severity
new
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.8.2-1~deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › expat/libexpat1@2.8.2-1~deb13u1
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.
Expat through 2.8.4 fails to validate low surrogates following high surrogates in UTF-16 input, allowing malformed UTF-16 sequences to be accepted. Attackers can craft UTF-16 encoded XML with lone high surrogates that consume following code units, hiding markup characters from the parser and enabling XML injection attacks.
Remediation
There is no fixed version for Debian:13 expat.
References
- https://security-tracker.debian.org/tracker/CVE-2026-93990
- https://github.com/libexpat/libexpat
- https://github.com/libexpat/libexpat/commit/ff6e1d7e750bbe245178f51a47a965dc8342861a
- https://github.com/libexpat/libexpat/pull/1282
- https://www.vulncheck.com/advisories/expat-through-2.8.4-malformed-utf-16-acceptance-via-unchecked-surrogate
high severity
- Vulnerable module: gzip
- Introduced through: gzip@1.13-1
- Fixed in: 1.13-1+deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › gzip@1.13-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream gzip package and not the gzip package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
GNU gzip contains a global buffer overflow vulnerability in the LZH decompression logic caused by improper reuse of shared global state between different decompression formats within a single execution. GNU gzip maintains a global array that is shared across the LZ77, LZW, and LZH decompression routines and is not reinitialized between files processed in the same invocation. By decompressing a specially crafted LZW file followed by a specially crafted LZH file in a single gzip -d command, an attacker can poison the shared global state and subsequently trigger an out‑of‑bounds read in the LZH decoder. The LZH decompression logic follows stale values left in the shared array, causing reads past the end of the allocated global buffer.
This issue has been fixed in commits 63dbf6b3b9e6e781df1a6a64e609b10e23969681 and e7378c2d421be6a286922374425680bbe9ad8b7d.
Remediation
Upgrade Debian:13 gzip to version 1.13-1+deb13u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-41992
- https://cert.pl/en/posts/2026/04/CVE-2026-41991/
- https://cgit.git.savannah.gnu.org/cgit/gzip.git/commit/?id=63dbf6b3b9e6e781df1a6a64e609b10e23969681
- https://www.gnu.org/software/gzip/
- http://www.openwall.com/lists/oss-security/2026/08/23/1
- http://www.openwall.com/lists/oss-security/2026/08/25/1
- http://www.openwall.com/lists/oss-security/2026/08/27/2
- https://cgit.git.savannah.gnu.org/cgit/gzip.git/commit/?id=e7378c2d421be6a286922374425680bbe9ad8b7d
high severity
- Vulnerable module: libssh2/libssh2-1t64
- Introduced through: libssh2/libssh2-1t64@1.11.1-1+deb13u1
- Fixed in: 1.11.1-1+deb13u2
Detailed paths
-
Introduced through: php@8.2-apache › libssh2/libssh2-1t64@1.11.1-1+deb13u1
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.
libssh2 through 1.11.1, fixed in commit 42e33d8, contains a pre-authentication heap buffer overflow vulnerability that allows a malicious SSH server to corrupt heap metadata in any connecting client by sending a packet with a packet_length smaller than the cipher's block size during Encrypt-then-MAC cipher negotiation. In the fullpacket() function in src/transport.c, the ETM path allocates a buffer of packet_length bytes but copies blocksize minus one bytes via memcpy, causing an overflow that on 32-bit glibc writes attacker-controlled bytes into an adjacent chunk's SIZE field, enabling tcache bin confusion, overlapping live objects, and function pointer overwrite during the session handshake before authentication.
Remediation
Upgrade Debian:13 libssh2 to version 1.11.1-1+deb13u2 or higher.
References
high severity
- Vulnerable module: libssh2/libssh2-1t64
- Introduced through: libssh2/libssh2-1t64@1.11.1-1+deb13u1
- Fixed in: 1.11.1-1+deb13u2
Detailed paths
-
Introduced through: php@8.2-apache › libssh2/libssh2-1t64@1.11.1-1+deb13u1
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.
libssh2 through 1.11.1, fixed in commit a13bb6c, contains a missing bounds check vulnerability that allows a malicious SSH server to trigger an arbitrary-length heap out-of-bounds read and a free of an uninitialized pointer via the publickey subsystem. In libssh2_publickey_list_fetch(), the version 1 response parser reads a server-controlled comment_len value and advances the parse pointer without verifying sufficient bytes remain in the buffer, causing the out-of-bounds read to leak heap pointers from adjacent allocations defeating ASLR, followed by heap allocator state corruption when the error cleanup path frees an uninitialized pointer from a non-zeroed realloc() region.
Remediation
Upgrade Debian:13 libssh2 to version 1.11.1-1+deb13u2 or higher.
References
high severity
- Vulnerable module: libssh2/libssh2-1t64
- Introduced through: libssh2/libssh2-1t64@1.11.1-1+deb13u1
- Fixed in: 1.11.1-1+deb13u2
Detailed paths
-
Introduced through: php@8.2-apache › libssh2/libssh2-1t64@1.11.1-1+deb13u1
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.
libssh2 through 1.11.1, fixed in commit a2ed82d, contains a pre-authentication integer underflow vulnerability in the ssh2_cipher_crypt() function in src/openssl.c that allows a malicious SSH server to crash any connecting client by negotiating AES-GCM ciphers during handshake. Attackers can exploit the underflow in the expression computing blocksize minus aadlen minus authentication tag length to trigger an out-of-bounds read and a memcpy call with a near-SIZE_MAX length argument, causing immediate process crash before any authentication occurs.
Remediation
Upgrade Debian:13 libssh2 to version 1.11.1-1+deb13u2 or higher.
References
high severity
- Vulnerable module: perl
- Introduced through: perl@5.40.1-6, perl/libperl5.40@5.40.1-6 and others
- Fixed in: 5.40.1-6+deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › perl@5.40.1-6
-
Introduced through: php@8.2-apache › perl/libperl5.40@5.40.1-6
-
Introduced through: php@8.2-apache › perl/perl-base@5.40.1-6
-
Introduced through: php@8.2-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
Upgrade Debian:13 perl to version 5.40.1-6+deb13u1 or higher.
References
high severity
new
- Vulnerable module: pcre2/libpcre2-8-0
- Introduced through: pcre2/libpcre2-8-0@10.46-1~deb13u1
- Fixed in: 10.46-1~deb13u2
Detailed paths
-
Introduced through: php@8.2-apache › pcre2/libpcre2-8-0@10.46-1~deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream pcre2 package and not the pcre2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
PCRE2 before 10.48, on 32-bit platforms, has a pcre2_pattern_convert out-of-bounds write when an attacker can provide a large pattern.
Remediation
Upgrade Debian:13 pcre2 to version 10.46-1~deb13u2 or higher.
References
high severity
new
- Vulnerable module: zlib/zlib1g
- Introduced through: zlib/zlib1g@1:1.3.dfsg+really1.3.1-1+b1
Detailed paths
-
Introduced through: php@8.2-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 versions 1.3.1.2 through 1.3.2 contain a heap buffer overflow vulnerability in the gz_vacate() function when processing non-blocking gzwrite() operations with stale external buffer pointers. Attackers can trigger the overflow by calling gzprintf() or gzvprintf() after a write stall, causing an unchecked memmove() to write beyond the internal input buffer boundary.
Remediation
There is no fixed version for Debian:13 zlib.
References
- https://security-tracker.debian.org/tracker/CVE-2026-85091
- https://gist.github.com/thesmartshadow/e0b9481792afb7c31e86fee1ff084490
- https://github.com/madler/zlib
- https://github.com/madler/zlib/blob/v1.3.2/gzwrite.c#L393
- https://www.vulncheck.com/advisories/zlib-1.3.1.2-through-1.3.2-heap-buffer-overflow-via-gz-vacate
high severity
new
- Vulnerable module: libxml2
- Introduced through: libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3
Detailed paths
-
Introduced through: php@8.2-apache › libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3
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.
In xmlIO in libxml2 before 2.15.4, an inconsistency in xmlOutputWriteCallback and xmlBufUse causes negative lengths to reach write callbacks, aka a lack of a check for integer overflow before calling writecallback. This has security relevance for many types of uses of that length value within a callback.
Remediation
There is no fixed version for Debian:13 libxml2.
References
high severity
- Vulnerable module: acl/libacl1
- Introduced through: acl/libacl1@2.3.2-2+b1
Detailed paths
-
Introduced through: php@8.2-apache › acl/libacl1@2.3.2-2+b1
NVD Description
Note: Versions mentioned in the description apply only to the upstream acl package and not the acl package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
acl before version 2.4.0 contains a symlink traversal vulnerability in the libacl pathname-based functions acl_get_file(), acl_set_file(), acl_extended_file(), and acl_delete_def_file() that allows local attackers to escalate privileges by replacing any pathname component with a symbolic link. Attackers who control any component of a pathname processed by a privileged caller can redirect ACL read or write operations to arbitrary files or directories, enabling unauthorized manipulation of access control lists and local privilege escalation.
Remediation
There is no fixed version for Debian:13 acl.
References
- https://security-tracker.debian.org/tracker/CVE-2026-54369
- https://cgit.git.savannah.nongnu.org/cgit/acl.git/commit/?id=24a227d0ab8576612194f8a56c2314389adc74a5
- https://cgit.git.savannah.nongnu.org/cgit/acl.git/commit/?id=3589787cd589b34bdd9265936e17190b6d3f17d1
- https://www.vulncheck.com/advisories/acl-symlink-traversal-privilege-escalation-via-libacl-functions
- https://access.redhat.com/errata/RHSA-2026:34351
- https://access.redhat.com/errata/RHSA-2026:42736
- https://access.redhat.com/errata/RHSA-2026:42739
- https://access.redhat.com/errata/RHSA-2026:43420
- https://access.redhat.com/security/cve/CVE-2026-54369
- https://bugzilla.redhat.com/show_bug.cgi?id=2490277
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-54369.json
- https://access.redhat.com/errata/RHSA-2026:44481
- https://access.redhat.com/errata/RHSA-2026:46836
- https://access.redhat.com/errata/RHSA-2026:50205
- https://access.redhat.com/errata/RHSA-2026:53371
- https://access.redhat.com/errata/RHSA-2026:54769
- https://access.redhat.com/errata/RHSA-2026:58981
- https://access.redhat.com/errata/RHSA-2026:64805
- https://access.redhat.com/errata/RHSA-2026:67140
- https://access.redhat.com/errata/RHSA-2026:67142
- https://access.redhat.com/errata/RHSA-2026:67144
high severity
- Vulnerable module: attr/libattr1
- Introduced through: attr/libattr1@1:2.5.2-3
Detailed paths
-
Introduced through: php@8.2-apache › attr/libattr1@1:2.5.2-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream attr package and not the attr package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
attr before version 2.6.0 contains a symlink traversal vulnerability in the getfattr and setfattr utilities that allows local attackers to escalate privileges by replacing a pathname component with a symbolic link during directory hierarchy traversal. Attackers who control a pathname component can redirect getfattr and setfattr operations to arbitrary files by substituting a symlink, leading to local privilege escalation when getfattr or setfattr is invoked by a privileged process over an attacker-controlled path.
Remediation
There is no fixed version for Debian:13 attr.
References
- https://security-tracker.debian.org/tracker/CVE-2026-54371
- https://cgit.git.savannah.nongnu.org/cgit/attr.git/commit/?id=49f79e947270f06940b9100fa638f85dddc4aa7f
- https://cgit.git.savannah.nongnu.org/cgit/attr.git/commit/?id=c440855d6b33446edf4b5eb1a2d892281f15a99b
- https://www.vulncheck.com/advisories/attr-symlink-traversal-privilege-escalation-via-getfattr-setfattr
- https://access.redhat.com/security/cve/CVE-2026-54371
- https://bugzilla.redhat.com/show_bug.cgi?id=2490283
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-54371.json
- https://access.redhat.com/errata/RHSA-2026:34889
- https://access.redhat.com/errata/RHSA-2026:56133
- https://access.redhat.com/errata/RHSA-2026:59380
- https://access.redhat.com/errata/RHSA-2026:60226
- https://access.redhat.com/errata/RHSA-2026:61783
- https://access.redhat.com/errata/RHSA-2026:63135
- https://access.redhat.com/errata/RHSA-2026:63138
- https://access.redhat.com/errata/RHSA-2026:66018
high severity
- Vulnerable module: libssh2/libssh2-1t64
- Introduced through: libssh2/libssh2-1t64@1.11.1-1+deb13u1
- Fixed in: 1.11.1-1+deb13u2
Detailed paths
-
Introduced through: php@8.2-apache › libssh2/libssh2-1t64@1.11.1-1+deb13u1
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.
libssh2 through 1.11.1 reads an attacker-controlled 32-bit attribute count from a publickey-subsystem response and uses it in the allocation num_attrs * sizeof(libssh2_publickey_attribute) without bounds checking, so on 32-bit platforms the multiplication overflows to an undersized buffer. A malicious SSH server can then drive the attribute-parsing loop to write past the allocation, causing a heap buffer overflow in a connecting libssh2 client.
Remediation
Upgrade Debian:13 libssh2 to version 1.11.1-1+deb13u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-58050
- https://github.com/bikini/exploitarium/tree/main/libssh2-publickey-list-calc-poc
- https://github.com/libssh2/libssh2/blob/master/src/publickey.c
- https://www.vulncheck.com/advisories/libssh2-integer-overflow-in-publickey-subsystem-attribute-allocation
medium severity
- Vulnerable module: libssh2/libssh2-1t64
- Introduced through: libssh2/libssh2-1t64@1.11.1-1+deb13u1
- Fixed in: 1.11.1-1+deb13u2
Detailed paths
-
Introduced through: php@8.2-apache › libssh2/libssh2-1t64@1.11.1-1+deb13u1
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.
libssh2 through 1.11.1 grows its publickey list with SSH2_REALLOC but does not zero-initialize new entries before parsing populates them, so a parse failure reaching the cleanup path leaves libssh2_publickey_list_free operating on an uninitialized entry. A malicious SSH server offering the publickey subsystem can use a malformed response to make cleanup free an uninitialized, attacker-influenceable attrs pointer in a connecting libssh2 client.
Remediation
Upgrade Debian:13 libssh2 to version 1.11.1-1+deb13u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-58051
- https://github.com/bikini/exploitarium/tree/main/libssh2-publickey-list-calc-poc
- https://github.com/libssh2/libssh2/blob/master/src/publickey.c
- https://www.vulncheck.com/advisories/libssh2-free-of-uninitialized-pointer-in-publickey-list-cleanup
medium severity
new
- Vulnerable module: pcre2/libpcre2-8-0
- Introduced through: pcre2/libpcre2-8-0@10.46-1~deb13u1
- Fixed in: 10.46-1~deb13u2
Detailed paths
-
Introduced through: php@8.2-apache › pcre2/libpcre2-8-0@10.46-1~deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream pcre2 package and not the pcre2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
PCRE2 before 10.48, on 32-bit platforms, has a pcre2_compile_32 integer overflow and resultant out-of-bounds write.
Remediation
Upgrade Debian:13 pcre2 to version 10.46-1~deb13u2 or higher.
References
medium severity
new
- Vulnerable module: pcre2/libpcre2-8-0
- Introduced through: pcre2/libpcre2-8-0@10.46-1~deb13u1
- Fixed in: 10.46-1~deb13u2
Detailed paths
-
Introduced through: php@8.2-apache › pcre2/libpcre2-8-0@10.46-1~deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream pcre2 package and not the pcre2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
PCRE2 before 10.48 has a pcre2_match out-of-bounds read during the PCRE2_MATCH_INVALID_UTF matching of an invalid UTF subject.
Remediation
Upgrade Debian:13 pcre2 to version 10.46-1~deb13u2 or higher.
References
medium severity
- Vulnerable module: acl/libacl1
- Introduced through: acl/libacl1@2.3.2-2+b1
Detailed paths
-
Introduced through: php@8.2-apache › acl/libacl1@2.3.2-2+b1
NVD Description
Note: Versions mentioned in the description apply only to the upstream acl package and not the acl package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
acl before version 2.4.0 contains a time-of-check to time-of-use (TOCTOU) race condition vulnerability that allows local attackers to escalate privileges by replacing a pathname component with a symbolic link between an lstat() check and subsequent symlink-following operations such as stat(), chown(), chmod(), acl_get_file(), and acl_set_file(). Attackers who control a pathname component can redirect file access control list operations to arbitrary files when getfacl, setfacl, or chacl is invoked by a privileged process over an attacker-controlled path, resulting in local privilege escalation.
Remediation
There is no fixed version for Debian:13 acl.
References
- https://security-tracker.debian.org/tracker/CVE-2026-54370
- https://cgit.git.savannah.nongnu.org/cgit/acl.git/commit/?id=24a227d0ab8576612194f8a56c2314389adc74a5
- https://cgit.git.savannah.nongnu.org/cgit/acl.git/commit/?id=3589787cd589b34bdd9265936e17190b6d3f17d1
- https://www.vulncheck.com/advisories/acl-toctou-symlink-traversal-via-getfacl-setfacl-chacl
medium severity
new
- Vulnerable module: libxml2
- Introduced through: libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3
Detailed paths
-
Introduced through: php@8.2-apache › libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3
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.
In libxml2 before 2.15.4, xmlFAParsePosCharGroup has an out-of-bounds read, aka an out-of-bounds read in the NXT macro in xmlregexp.
Remediation
There is no fixed version for Debian:13 libxml2.
References
medium severity
new
- Vulnerable module: pcre2/libpcre2-8-0
- Introduced through: pcre2/libpcre2-8-0@10.46-1~deb13u1
- Fixed in: 10.46-1~deb13u2
Detailed paths
-
Introduced through: php@8.2-apache › pcre2/libpcre2-8-0@10.46-1~deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream pcre2 package and not the pcre2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
PCRE2 before 10.48 has a pcre2_match out-of-bounds read after a JIT fallback when an attacker can provide invalid UTF data.
Remediation
Upgrade Debian:13 pcre2 to version 10.46-1~deb13u2 or higher.
References
medium severity
new
- Vulnerable module: libxml2
- Introduced through: libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3
Detailed paths
-
Introduced through: php@8.2-apache › libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3
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. A local user or an attacker providing a specially crafted XML catalog can trigger a NULL pointer dereference during XML catalog parsing. This occurs when a nextCatalog element lacks its mandatory catalog attribute, leading to the application crashing and causing a Denial of Service (DoS).
Remediation
There is no fixed version for Debian:13 libxml2.
References
medium severity
- Vulnerable module: util-linux
- Introduced through: util-linux@2.41-5, util-linux/libblkid1@2.41-5 and others
- Fixed in: 2.41.5-0+deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › util-linux@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libblkid1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/liblastlog2-2@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libmount1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libsmartcols1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libuuid1@2.41-5
-
Introduced through: php@8.2-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 libblkid library of util-linux. During nested partition probing, the BSD, Minix, Solaris x86, and UnixWare partition probers cache a raw pointer to a parent partition entry in a dynamically allocated array. When subsequent partition additions cause the array to be reallocated, this pointer becomes stale, leading to a heap use-after-free read. An attacker who can present a crafted block device image (for example, via USB insertion or a loop-mounted disk image) can trigger this flaw without user interaction, as libblkid is invoked automatically by udev/udisks as root on block-device hot-plug events. This could lead to limited information disclosure or denial of service.
Remediation
Upgrade Debian:13 util-linux to version 2.41.5-0+deb13u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-13595
- https://access.redhat.com/errata/RHSA-2026:26573
- https://access.redhat.com/security/cve/CVE-2026-13595
- https://bugzilla.redhat.com/show_bug.cgi?id=2494101
- https://github.com/util-linux/util-linux/commit/c0186f14fbdb02f64c8e0ba701ce727ea764ff4c
low severity
- 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: php@8.2-apache › glibc/libc-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc-dev-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc6@2.41-12+deb13u3
-
Introduced through: php@8.2-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
- Vulnerable module: tar
- Introduced through: tar@1.35+dfsg-3.1
Detailed paths
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2005-2541
- http://marc.info/?l=bugtraq&m=112327628230258&w=2
- https://lists.apache.org/thread.html/rc713534b10f9daeee2e0990239fa407e2118e4aa9e88a7041177497c@%3Cissues.guacamole.apache.org%3E
- https://lists.apache.org/thread.html/rc713534b10f9daeee2e0990239fa407e2118e4aa9e88a7041177497c%40%3Cissues.guacamole.apache.org%3E
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.41-12+deb13u3, glibc/libc-dev-bin@2.41-12+deb13u3 and others
Detailed paths
-
Introduced through: php@8.2-apache › glibc/libc-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc-dev-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc6@2.41-12+deb13u3
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2019-1010023
- https://support.f5.com/csp/article/K11932200?utm_source=f5support&utm_medium=RSS
- https://sourceware.org/bugzilla/show_bug.cgi?id=22851
- http://www.securityfocus.com/bid/109167
- https://ubuntu.com/security/CVE-2019-1010023
- https://support.f5.com/csp/article/K11932200?utm_source=f5support&%3Butm_medium=RSS
low severity
new
- Vulnerable module: util-linux
- Introduced through: util-linux@2.41-5, util-linux/libblkid1@2.41-5 and others
Detailed paths
-
Introduced through: php@8.2-apache › util-linux@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libblkid1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/liblastlog2-2@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libmount1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libsmartcols1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libuuid1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/mount@2.41-5
-
Introduced through: php@8.2-apache › util-linux/bsdutils@1:2.41-5
-
Introduced through: php@8.2-apache › util-linux/login@1:4.16.0-2+really2.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.
The nsenter --join-cgroup option opens the target cgroup.procs file as root and leaves that file descriptor open across later namespace and credential changes and across execve(). Because the kernel checks later cgroup migrations using the credentials from the original open, a program run in an attacker-controlled target can inherit root's ability to move host processes between cgroups. After a privileged operator uses --join-cgroup against that target, an unprivileged user can migrate and terminate unrelated root processes.
Remediation
There is no fixed version for Debian:13 util-linux.
References
- https://security-tracker.debian.org/tracker/CVE-2026-78408
- https://access.redhat.com/security/cve/CVE-2026-78408
- https://bugzilla.redhat.com/show_bug.cgi?id=2522497
- https://access.redhat.com/errata/RHSA-2026:63162
- http://www.openwall.com/lists/oss-security/2026/09/05/2
- https://github.com/util-linux/util-linux/security/advisories/GHSA-55fx-f4gg-cfhj
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2026-6846
- https://access.redhat.com/errata/RHSA-2026:39022
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-6846.json
- https://access.redhat.com/errata/RHSA-2026:33527
- https://access.redhat.com/security/cve/CVE-2026-6846
- https://bugzilla.redhat.com/show_bug.cgi?id=2460006
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2025-5244
- https://sourceware.org/bugzilla/attachment.cgi?id=16010
- https://sourceware.org/bugzilla/show_bug.cgi?id=32858
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=d1458933830456e54223d9fc61f0d9b3a19256f5
- https://vuldb.com/?ctiid.310346
- https://vuldb.com/?id.310346
- https://vuldb.com/?submit.584634
- https://www.gnu.org/
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2025-5245
- https://sourceware.org/bugzilla/attachment.cgi?id=16004
- https://sourceware.org/bugzilla/show_bug.cgi?id=32829
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=6c3458a8b7ee7d39f070c7b2350851cb2110c65a
- https://vuldb.com/?ctiid.310347
- https://vuldb.com/?id.310347
- https://vuldb.com/?submit.584635
- https://www.gnu.org/
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2025-7546
- https://sourceware.org/bugzilla/attachment.cgi?id=16118
- https://sourceware.org/bugzilla/show_bug.cgi?id=33050#c2
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=41461010eb7c79fee7a9d5f6209accdaac66cc6b
- https://vuldb.com/?ctiid.316244
- https://vuldb.com/?id.316244
- https://vuldb.com/?submit.614375
- https://www.gnu.org/
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
- https://sourceware.org/bugzilla/show_bug.cgi?id=33050
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2025-7545
- https://sourceware.org/bugzilla/attachment.cgi?id=16117
- https://sourceware.org/bugzilla/show_bug.cgi?id=33049
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=08c3cbe5926e4d355b5cb70bbec2b1eeb40c2944
- https://vuldb.com/?ctiid.316243
- https://vuldb.com/?id.316243
- https://vuldb.com/?submit.614355
- https://www.gnu.org/
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
- https://sourceware.org/bugzilla/show_bug.cgi?id=33049#c1
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2025-11083
- https://sourceware.org/bugzilla/attachment.cgi?id=16353
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=9ca499644a21ceb3f946d1c179c38a83be084490
- https://vuldb.com/?ctiid.326124
- https://vuldb.com/?id.326124
- https://vuldb.com/?submit.661277
- https://www.gnu.org/
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://sourceware.org/bugzilla/show_bug.cgi?id=33457
- https://sourceware.org/bugzilla/show_bug.cgi?id=33457#c1
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2025-11082
- https://sourceware.org/bugzilla/attachment.cgi?id=16358
- https://sourceware.org/bugzilla/show_bug.cgi?id=33464
- https://sourceware.org/bugzilla/show_bug.cgi?id=33464#c2
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=ea1a0737c7692737a644af0486b71e4a392cbca8
- https://vuldb.com/?ctiid.326123
- https://vuldb.com/?id.326123
- https://vuldb.com/?submit.661276
- https://www.gnu.org/
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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 out-of-bounds write vulnerability was found in the BFD library's DLX ELF backend (bfd/elf32-dlx.c) in GNU binutils. The dlx_rtype_to_howto() function maps ELF relocation types to internal howto structures but fails to perform adequate bounds checking on attacker-controlled relocation type values (via ELF32_R_TYPE(r_info)) before indexing into the dlx_elf_howto_table[] array. The DLX relocation type number space is non-contiguous (basic types 0-6, extended types at 0x10000+), but the default case in the switch statement allows arbitrary index values to reach the array access.
A specially crafted ELF/DLX object file can trigger this out-of-bounds write when processed by any BFD-consuming tool (objdump, readelf, strip, ld, nm, objcopy). The vulnerability has been demonstrated to achieve arbitrary code execution via a File Stream Oriented Programming (FSOP) attack against glibc FILE structures (stderr), redirecting control flow to system().
Attack scenarios include CI/CD pipelines performing automated binary analysis, developer workstations running objdump/readelf on untrusted binaries, automated security scanning or malware analysis tools invoking binutils, and package build systems processing third-party code.
Note: This vulnerability is only exploitable when binutils is built with the DLX backend enabled (typically via --enable-targets=all).
Remediation
There is no fixed version for Debian:13 binutils.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.8.2-1~deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › expat/libexpat1@2.8.2-1~deb13u1
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.4 lacks handler call depth tracking with custom encoding callbacks. Thus, a use-after-free can occur. NOTE: this is similar to CVE-2026-50219, CVE-2026-56131 and CVE-2026-56412.
Remediation
There is no fixed version for Debian:13 expat.
References
low severity
- Vulnerable module: ncurses/libncursesw6
- Introduced through: ncurses/libncursesw6@6.5+20250216-2, ncurses/libtinfo6@6.5+20250216-2 and others
Detailed paths
-
Introduced through: php@8.2-apache › ncurses/libncursesw6@6.5+20250216-2
-
Introduced through: php@8.2-apache › ncurses/libtinfo6@6.5+20250216-2
-
Introduced through: php@8.2-apache › ncurses/ncurses-base@6.5+20250216-2
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2025-69720
- https://github.com/Cao-Wuhui/CVE-2025-69720
- https://invisible-island.net/archives/ncurses/6.5/
- https://invisible-island.net/ncurses/
- https://marc.info/?l=ncurses-bug&m=176539968328570&w=2
- https://marc.info/?l=ncurses-bug&m=176540731801330&w=2
- https://marc.info/?l=ncurses-bug&m=176545557728083&w=2
- https://cert-portal.siemens.com/productcert/html/ssa-253495.html
low severity
new
- Vulnerable module: util-linux
- Introduced through: util-linux@2.41-5, util-linux/libblkid1@2.41-5 and others
Detailed paths
-
Introduced through: php@8.2-apache › util-linux@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libblkid1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/liblastlog2-2@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libmount1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libsmartcols1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libuuid1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/mount@2.41-5
-
Introduced through: php@8.2-apache › util-linux/bsdutils@1:2.41-5
-
Introduced through: php@8.2-apache › util-linux/login@1:4.16.0-2+really2.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 versions through 2.41.5 and 2.42.2 fail to check mount helper exit status before running post-mount hooks, allowing unprivileged users to execute privileged operations on pre-existing filesystems. Attackers can exploit X-mount.idmap or X-mount.owner hooks to clone filesystems with inherited suid bits or modify target inode permissions after a helper fails, achieving privilege escalation.
Remediation
There is no fixed version for Debian:13 util-linux.
References
- https://security-tracker.debian.org/tracker/CVE-2026-76642
- https://github.com/util-linux/util-linux
- https://github.com/util-linux/util-linux/blob/v2.42.2/libmount/src/context_mount.c#L476
- https://github.com/util-linux/util-linux/blob/v2.42.2/libmount/src/context_mount.c#L892
- https://github.com/util-linux/util-linux/commit/1d14676ea70003e9f5b2a6a76af0cadb1190411a
- https://github.com/util-linux/util-linux/commit/a15c00a9e545aa8b9cf6ec0f888ff6c7b3eaeedc
- https://github.com/util-linux/util-linux/commit/f57cea130839c0af8dc0525274267ae4cfd66bbf
- https://www.vulncheck.com/advisories/util-linux-libmount-privilege-escalation-via-failed-mount-helper
- https://github.com/util-linux/util-linux/security/advisories/GHSA-m25x-3hj9-m26f
low severity
new
- Vulnerable module: util-linux
- Introduced through: util-linux@2.41-5, util-linux/libblkid1@2.41-5 and others
Detailed paths
-
Introduced through: php@8.2-apache › util-linux@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libblkid1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/liblastlog2-2@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libmount1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libsmartcols1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libuuid1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/mount@2.41-5
-
Introduced through: php@8.2-apache › util-linux/bsdutils@1:2.41-5
-
Introduced through: php@8.2-apache › util-linux/login@1:4.16.0-2+really2.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. Restricted bind mounts take the source path from fstab but do not pin that source before the privileged mount. A local unprivileged user who can replace the authorized source or a writable ancestor can redirect SUID mount(8) to bind another host directory. If the fstab entry also sets X-mount.owner, X-mount.group, or X-mount.mode, root then changes ownership or mode on that redirected inode.
Remediation
There is no fixed version for Debian:13 util-linux.
References
low severity
- Vulnerable module: apache2
- Introduced through: apache2@2.4.68-1~deb13u1, apache2/apache2-bin@2.4.68-1~deb13u1 and others
Detailed paths
-
Introduced through: php@8.2-apache › apache2@2.4.68-1~deb13u1
-
Introduced through: php@8.2-apache › apache2/apache2-bin@2.4.68-1~deb13u1
-
Introduced through: php@8.2-apache › apache2/apache2-data@2.4.68-1~deb13u1
-
Introduced through: php@8.2-apache › apache2/apache2-utils@2.4.68-1~deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream apache2 package and not the apache2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
The Apache HTTP Server, when accessed through a TCP connection with a large window size, allows remote attackers to cause a denial of service (network bandwidth consumption) via a Range header that specifies multiple copies of the same fragment. NOTE: the severity of this issue has been disputed by third parties, who state that the large window size required by the attack is not normally supported or configured by the server, or that a DDoS-style attack would accomplish the same goal
Remediation
There is no fixed version for Debian:13 apache2.
References
- https://security-tracker.debian.org/tracker/CVE-2007-0086
- http://www.securityfocus.com/archive/1/455833/100/0/threaded
- http://www.securityfocus.com/archive/1/455879/100/0/threaded
- http://www.securityfocus.com/archive/1/455882/100/0/threaded
- http://www.securityfocus.com/archive/1/455920/100/0/threaded
- http://osvdb.org/33456
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2025-69650
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=ea4bc025abdba85a90e26e13f551c16a44bfa921
- https://sourceware.org/bugzilla/show_bug.cgi?id=33700
- https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=81e90cf63a10ad11772c2437c8f2a88f1a00c739
- https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=ea4bc025abdba85a90e26e13f551c16a44bfa92
- https://sourceware.org/bugzilla/show_bug.cgi?id=33698
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.8.2-1~deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › expat/libexpat1@2.8.2-1~deb13u1
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.
Expat through 2.8.3 contains a denial of service vulnerability caused by quadratic algorithmic complexity in the storeAtts() function in xmlparse.c, where processing N specified attributes with non-normalized values triggers an O(N^2) linear scan of elementType->defaultAtts to determine CDATA status. A remote unauthenticated attacker can supply a single well-formed XML document of a few megabytes to an application parsing untrusted XML to cause excessive CPU consumption, resulting in denial of service without requiring authentication, external entity resolution, or non-default parser options.
Remediation
There is no fixed version for Debian:13 expat.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.8.2-1~deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › expat/libexpat1@2.8.2-1~deb13u1
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 2.8.2 and 2.8.3 before 2.8.4, misinterpretation of getentropy's return code leads to insufficient entropy, which results in being vulnerable to hash flooding attacks, causing a denial of service via crafted XML content.
Remediation
There is no fixed version for Debian:13 expat.
References
low severity
- 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: php@8.2-apache › glibc/libc-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc-dev-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc6@2.41-12+deb13u3
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2018-20796
- https://support.f5.com/csp/article/K26346590?utm_source=f5support&utm_medium=RSS
- https://debbugs.gnu.org/cgi/bugreport.cgi?bug=34141
- https://lists.gnu.org/archive/html/bug-gnulib/2019-01/msg00108.html
- https://security.netapp.com/advisory/ntap-20190315-0002/
- http://www.securityfocus.com/bid/107160
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2018-20796
- https://support.f5.com/csp/article/K26346590?utm_source=f5support&%3Butm_medium=RSS
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.41-12+deb13u3, glibc/libc-dev-bin@2.41-12+deb13u3 and others
Detailed paths
-
Introduced through: php@8.2-apache › glibc/libc-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc-dev-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc6@2.41-12+deb13u3
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2019-9192
- https://support.f5.com/csp/article/K26346590?utm_source=f5support&utm_medium=RSS
- https://sourceware.org/bugzilla/show_bug.cgi?id=24269
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2019-9192
- https://support.f5.com/csp/article/K26346590?utm_source=f5support&%3Butm_medium=RSS
low severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.21.3-5+deb13u1, krb5/libk5crypto3@1.21.3-5+deb13u1 and others
Detailed paths
-
Introduced through: php@8.2-apache › krb5/libgssapi-krb5-2@1.21.3-5+deb13u1
-
Introduced through: php@8.2-apache › krb5/libk5crypto3@1.21.3-5+deb13u1
-
Introduced through: php@8.2-apache › krb5/libkrb5-3@1.21.3-5+deb13u1
-
Introduced through: php@8.2-apache › krb5/libkrb5support0@1.21.3-5+deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
An issue was discovered in MIT Kerberos 5 (aka krb5) through 1.16. There is a variable "dbentry->n_key_data" in kadmin/dbutil/dump.c that can store 16-bit data but unknowingly the developer has assigned a "u4" variable to it, which is for 32-bit data. An attacker can use this vulnerability to affect other artifacts of the database as we know that a Kerberos database dump file contains trusted data.
Remediation
There is no fixed version for Debian:13 krb5.
References
- https://security-tracker.debian.org/tracker/CVE-2018-5709
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5709
- https://github.com/poojamnit/Kerberos-V5-1.16-Vulnerabilities/tree/master/Integer%20Overflow
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772@%3Cdev.mina.apache.org%3E
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2018-5709
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772%40%3Cdev.mina.apache.org%3E
low severity
- Vulnerable module: openldap/libldap2
- Introduced through: openldap/libldap2@2.6.10+dfsg-1
Detailed paths
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2015-3276
- http://www.oracle.com/technetwork/topics/security/linuxbulletinoct2015-2719645.html
- https://bugzilla.redhat.com/show_bug.cgi?id=1238322
- http://rhn.redhat.com/errata/RHSA-2015-2131.html
- http://www.securitytracker.com/id/1034221
- https://access.redhat.com/errata/RHSA-2015:2131
- https://access.redhat.com/security/cve/CVE-2015-3276
low severity
- Vulnerable module: openldap/libldap2
- Introduced through: openldap/libldap2@2.6.10+dfsg-1
Detailed paths
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2017-17740
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17740
- http://www.openldap.org/its/index.cgi/Incoming?id=8759
- http://lists.opensuse.org/opensuse-security-announce/2019-09/msg00053.html
- http://lists.opensuse.org/opensuse-security-announce/2019-09/msg00058.html
- https://kc.mcafee.com/corporate/index?page=content&id=SB10365
- https://www.oracle.com/security-alerts/cpuapr2022.html
low severity
- Vulnerable module: patch
- Introduced through: patch@2.8-2
Detailed paths
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2018-6952
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6952
- https://security.gentoo.org/glsa/201904-17
- https://savannah.gnu.org/bugs/index.php?53133
- https://access.redhat.com/errata/RHSA-2019:2033
- http://www.securityfocus.com/bid/103047
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2018-6952
low severity
- Vulnerable module: patch
- Introduced through: patch@2.8-2
Detailed paths
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2018-6951
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6951
- https://security.gentoo.org/glsa/201904-17
- https://git.savannah.gnu.org/cgit/patch.git/commit/?id=f290f48a621867084884bfff87f8093c15195e6a
- https://savannah.gnu.org/bugs/index.php?53132
- http://www.securityfocus.com/bid/103044
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2018-6951
- https://usn.ubuntu.com/3624-1/
low severity
- Vulnerable module: perl
- Introduced through: perl@5.40.1-6, perl/libperl5.40@5.40.1-6 and others
Detailed paths
-
Introduced through: php@8.2-apache › perl@5.40.1-6
-
Introduced through: php@8.2-apache › perl/libperl5.40@5.40.1-6
-
Introduced through: php@8.2-apache › perl/perl-base@5.40.1-6
-
Introduced through: php@8.2-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
- Vulnerable module: m4
- Introduced through: m4@1.4.19-8
Detailed paths
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2008-1687
- http://slackware.com/security/viewer.php?l=slackware-security&y=2008&m=slackware-security.510612
- http://www.vupen.com/english/advisories/2008/1151/references
- http://xforce.iss.net/xforce/xfdb/41706
- http://www.openwall.com/lists/oss-security/2008/04/07/1
- http://www.openwall.com/lists/oss-security/2008/04/07/12
- http://www.openwall.com/lists/oss-security/2008/04/07/3
- http://www.openwall.com/lists/oss-security/2008/04/07/4
- http://secunia.com/advisories/29671
- http://secunia.com/advisories/29729
- http://www.securityfocus.com/bid/28688
- https://exchange.xforce.ibmcloud.com/vulnerabilities/41706
low severity
- Vulnerable module: m4
- Introduced through: m4@1.4.19-8
Detailed paths
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2008-1688
- http://osvdb.org/44272
- http://slackware.com/security/viewer.php?l=slackware-security&y=2008&m=slackware-security.510612
- http://www.vupen.com/english/advisories/2008/1151/references
- http://xforce.iss.net/xforce/xfdb/41704
- http://www.openwall.com/lists/oss-security/2008/04/07/1
- http://www.openwall.com/lists/oss-security/2008/04/07/3
- http://secunia.com/advisories/29671
- http://secunia.com/advisories/29729
- http://www.securityfocus.com/bid/28688
- https://exchange.xforce.ibmcloud.com/vulnerabilities/41704
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
new
- Vulnerable module: util-linux
- Introduced through: util-linux@2.41-5, util-linux/libblkid1@2.41-5 and others
Detailed paths
-
Introduced through: php@8.2-apache › util-linux@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libblkid1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/liblastlog2-2@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libmount1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libsmartcols1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libuuid1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/mount@2.41-5
-
Introduced through: php@8.2-apache › util-linux/bsdutils@1:2.41-5
-
Introduced through: php@8.2-apache › util-linux/login@1:4.16.0-2+really2.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.
The X-mount.subdir option uses a detached-tree fast path on Linux 6.15 and later and passes the configured subdirectory to open_tree() with AT_SYMLINK_NOFOLLOW. That flag does not stop intermediate symlink traversal or keep resolution inside the newly mounted filesystem. A local unprivileged user with an fstab-authorized X-mount.subdir entry can attach a host path at the intended mountpoint.
Remediation
There is no fixed version for Debian:13 util-linux.
References
low severity
new
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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 vulnerability has been detected in GNU Binutils 2.47. Affected by this vulnerability is the function elf_x86_64_relocate_section of the file bfd/elf64-x86-64.c of the component ld. Such manipulation of the argument roff leads to buffer overflow. An attack has to be approached locally. The exploit has been disclosed publicly and may be used. Upgrading to version 2.48 addresses this issue. The name of the patch is 471130b39c03623ec6d78ece377ff4da3f6bfe7b. It is recommended to upgrade the affected component.
Remediation
There is no fixed version for Debian:13 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2026-90803
- https://github.com/r1ck9-2q/cve_summit/blob/main/Heap%20OOB%20readwrite%20and%20SEGV%20in%20%60elf_x86_64_relocate_section%60%20(bfdelf64-x86-64.c4530%20%204835)%20via%20malformed%20relocation.md
- https://sourceware.org/bugzilla/show_bug.cgi?id=34444
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=471130b39c03623ec6d78ece377ff4da3f6bfe7b
- https://vuldb.com/cve/CVE-2026-90803
- https://vuldb.com/submit/920280
- https://vuldb.com/vuln/403305
- https://vuldb.com/vuln/403305/cti
- https://www.gnu.org/
low severity
new
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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.47. This impacts the function cache_bwrite of the file bfd/cache.c of the component ld. The manipulation of the argument nbytes results in buffer overflow. The attack requires a local approach. The exploit has been released to the public and may be used for attacks. The project was informed of the problem early through a bug report but has not responded yet.
Remediation
There is no fixed version for Debian:13 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2026-90801
- https://github.com/r1ck9-2q/cve_summit/blob/main/Heap-buffer-overflow%20in%20%60cache_bwrite%60%20(bfdcache.c436)%20via%20malformed%20ELF%20with%20%60--gc-sections%20-w%60.md
- https://sourceware.org/bugzilla/show_bug.cgi?id=34442
- https://vuldb.com/cve/CVE-2026-90801
- https://vuldb.com/submit/920276
- https://vuldb.com/vuln/403303
- https://vuldb.com/vuln/403303/cti
- https://www.gnu.org/
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2018-20712
- https://support.f5.com/csp/article/K38336243
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20712
- https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88629
- https://sourceware.org/bugzilla/show_bug.cgi?id=24043
- http://www.securityfocus.com/bid/106563
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2018-20712
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- Vulnerable module: apache2
- Introduced through: apache2@2.4.68-1~deb13u1, apache2/apache2-bin@2.4.68-1~deb13u1 and others
Detailed paths
-
Introduced through: php@8.2-apache › apache2@2.4.68-1~deb13u1
-
Introduced through: php@8.2-apache › apache2/apache2-bin@2.4.68-1~deb13u1
-
Introduced through: php@8.2-apache › apache2/apache2-data@2.4.68-1~deb13u1
-
Introduced through: php@8.2-apache › apache2/apache2-utils@2.4.68-1~deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream apache2 package and not the apache2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
Apache httpd 2.0.59 and 2.2.4, with the Prefork MPM module, allows local users to cause a denial of service via certain code sequences executed in a worker process that (1) stop request processing by killing all worker processes and preventing creation of replacements or (2) hang the system by forcing the master process to fork an arbitrarily large number of worker processes. NOTE: This might be an inherent design limitation of Apache with respect to worker processes in hosted environments.
Remediation
There is no fixed version for Debian:13 apache2.
References
- https://security-tracker.debian.org/tracker/CVE-2007-3303
- http://www.securityfocus.com/archive/1/469899/100/0/threaded
- http://www.securityfocus.com/archive/1/471832/100/0/threaded
- http://security.psnc.pl/files/apache_report.pdf
- http://osvdb.org/37050
- http://www.securityfocus.com/bid/24215
- http://securityreason.com/securityalert/2814
low severity
- Vulnerable module: p11-kit/libp11-kit0
- Introduced through: p11-kit/libp11-kit0@0.25.5-3
Detailed paths
-
Introduced through: php@8.2-apache › p11-kit/libp11-kit0@0.25.5-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream p11-kit package and not the p11-kit package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A flaw was found in p11-kit. A local attacker, or one with equivalent access to a reachable RPC channel, could exploit an integer overflow vulnerability. By sending specially crafted messages, the attacker can cause the system to miscalculate memory allocation for nested attributes. This leads to a memory corruption issue, specifically a heap out-of-bounds write, which can crash the p11-kit RPC parsing process, resulting in a Denial of Service (DoS). This vulnerability is only exploitable on 32 bit systems.
Remediation
There is no fixed version for Debian:13 p11-kit.
References
low severity
- Vulnerable module: p11-kit/libp11-kit0
- Introduced through: p11-kit/libp11-kit0@0.25.5-3
Detailed paths
-
Introduced through: php@8.2-apache › p11-kit/libp11-kit0@0.25.5-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream p11-kit package and not the p11-kit package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A flaw was found in p11-kit. The RPC message attribute parsing functions p11_rpc_message_get_attribute() and p11_rpc_message_get_attribute_array_value() form a mutually-recursive call chain with no recursion depth limit when processing nested CKA_WRAP_TEMPLATE, CKA_UNWRAP_TEMPLATE, and CKA_DERIVE_TEMPLATE attributes. An unauthenticated attacker with local access to the p11-kit RPC Unix domain socket can send a specially crafted request with deeply nested template attributes, causing stack exhaustion and crashing the p11-kit server process and its dependent services.
Remediation
There is no fixed version for Debian:13 p11-kit.
References
- https://security-tracker.debian.org/tracker/CVE-2026-13757
- https://access.redhat.com/errata/RHSA-2026:37469
- https://access.redhat.com/errata/RHSA-2026:38342
- https://access.redhat.com/errata/RHSA-2026:49668
- https://access.redhat.com/security/cve/CVE-2026-13757
- https://bugzilla.redhat.com/show_bug.cgi?id=2494556
- https://github.com/advisories/GHSA-p2wm-69qx-x25w
- https://access.redhat.com/errata/RHSA-2026:49667
- https://access.redhat.com/errata/RHSA-2026:53371
- https://access.redhat.com/errata/RHSA-2026:54387
- https://access.redhat.com/errata/RHSA-2026:54760
- https://access.redhat.com/errata/RHSA-2026:58981
low severity
- Vulnerable module: shadow/login.defs
- Introduced through: shadow/login.defs@1:4.17.4-2 and shadow/passwd@1:4.17.4-2
Detailed paths
-
Introduced through: php@8.2-apache › shadow/login.defs@1:4.17.4-2
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2007-5686
- http://www.securityfocus.com/archive/1/482129/100/100/threaded
- http://www.securityfocus.com/archive/1/482857/100/0/threaded
- https://issues.rpath.com/browse/RPL-1825
- http://secunia.com/advisories/27215
- http://www.securityfocus.com/bid/26048
- http://www.vupen.com/english/advisories/2007/3474
low severity
new
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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.47. Affected by this issue is the function _bfd_elf_write_section_eh_frame of the file bfd/elf-eh-frame.c of the component Eh Frame Section Handler. Performing a manipulation of the argument cie_length/fde_length/augmentation_data_size/write_offset results in buffer overflow. Attacking locally is a requirement. The exploit is now public and may be used. The project was informed of the problem early through a bug report but has not responded yet.
Remediation
There is no fixed version for Debian:13 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2026-90804
- https://github.com/r1ck9-2q/cve_summit/blob/main/Heap%20OOB%20write%20%20negative-size%20%60memmove%60%20%20SEGV%20in%20%60_bfd_elf_write_section_eh_frame%60%20(bfdelf-eh-frame.c2064%20%202083%20%202193)%20via%20malformed%20%60.eh_frame%60.md
- https://sourceware.org/bugzilla/show_bug.cgi?id=34445
- https://vuldb.com/cve/CVE-2026-90804
- https://vuldb.com/submit/920281
- https://vuldb.com/vuln/403306
- https://vuldb.com/vuln/403306/cti
- https://www.gnu.org/
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2026-4647
- https://access.redhat.com/security/cve/CVE-2026-4647
- https://bugzilla.redhat.com/show_bug.cgi?id=2450302
- https://sourceware.org/bugzilla/show_bug.cgi?id=33919
- https://access.redhat.com/errata/RHSA-2026:33527
- https://access.redhat.com/errata/RHSA-2026:39022
low severity
- Vulnerable module: coreutils
- Introduced through: coreutils@9.7-3
Detailed paths
-
Introduced through: php@8.2-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.
GNU coreutils unexpand is vulnerable to a heap-based buffer overflow due to an integer overflow during buffer allocation when processing large tab stop (-t) values. The multiplication used to calculate the allocation size can wrap around, resulting in an undersized buffer. When processing crafted input, subsequent writes exceed the allocated memory, leading to an out‑of‑bounds heap write.
When running GNU coreutils unexpand with attacker-provided large tab stop (-t) arguments, this behavior leads to a crash and potentially achieve a heap write primitive depending on memory layout.
This issue has been fixed in the commit b60a159fdc5bfcf9988d3a4cb6f53abe8ad5d35d
Remediation
There is no fixed version for Debian:13 coreutils.
References
low severity
- Vulnerable module: coreutils
- Introduced through: coreutils@9.7-3
Detailed paths
-
Introduced through: php@8.2-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.
GNU coreutils uniq is vulnerable to an out‑of‑bounds read due to incorrect handling of multibyte input when the -w (--check-chars) option is used. The find_field() function miscalculates the byte length of characters by repeatedly processing a fixed pointer instead of advancing through the input, resulting in an inflated length value. This incorrect length is later used in a memcmp operation, causing reads beyond the allocated buffer when processing crafted multibyte input.
When running GNU coreutils uniq with attacker-provided arguments, this behavior leads to a crash and potential adjacent heap memory exposure.
This issue has been fixed in the commit d64e35a8a4c0e4608321433e0d84d917e4e36371.
Remediation
There is no fixed version for Debian:13 coreutils.
References
low severity
- Vulnerable module: util-linux
- Introduced through: util-linux@2.41-5, util-linux/libblkid1@2.41-5 and others
- Fixed in: 2.41.3-1
Detailed paths
-
Introduced through: php@8.2-apache › util-linux@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libblkid1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/liblastlog2-2@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libmount1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libsmartcols1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libuuid1@2.41-5
-
Introduced through: php@8.2-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
Upgrade Debian:13 util-linux to version 2.41.3-1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-14104
- https://access.redhat.com/security/cve/CVE-2025-14104
- https://bugzilla.redhat.com/show_bug.cgi?id=2419369
- https://access.redhat.com/errata/RHSA-2026:1696
- https://access.redhat.com/errata/RHSA-2026:1852
- https://access.redhat.com/errata/RHSA-2026:1913
- https://access.redhat.com/errata/RHSA-2026:2485
- https://access.redhat.com/errata/RHSA-2026:2563
- https://access.redhat.com/errata/RHSA-2026:2737
- https://access.redhat.com/errata/RHSA-2026:2800
- https://access.redhat.com/errata/RHSA-2026:3406
- https://access.redhat.com/errata/RHSA-2026:4943
- https://access.redhat.com/errata/RHSA-2026:7180
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2025-1153
- https://sourceware.org/bugzilla/show_bug.cgi?id=32603
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=8d97c1a53f3dc9fd8e1ccdb039b8a33d50133150
- https://vuldb.com/?ctiid.295057
- https://vuldb.com/?id.295057
- https://vuldb.com/?submit.489991
- https://www.gnu.org/
- https://security.netapp.com/advisory/ntap-20250404-0005/
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2025-1178
- https://sourceware.org/bugzilla/attachment.cgi?id=15914
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=75086e9de1707281172cc77f178e7949a4414ed0
- https://vuldb.com/?ctiid.295081
- https://vuldb.com/?id.295081
- https://vuldb.com/?submit.495369
- https://www.gnu.org/
- https://security.netapp.com/advisory/ntap-20250411-0008/
- https://sourceware.org/bugzilla/show_bug.cgi?id=32638
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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 (Binary Utilities) linker. This vulnerability, a heap-buffer-overflow read (CWE-125), occurs when the linker processes a specially crafted 32-bit XCOFF (Extended Common Object File Format) object file. An attacker could exploit this by providing a malicious file, leading to an out-of-bounds read of memory. This can result in information disclosure, potentially revealing sensitive heap data, and a Denial of Service (DoS) due to the linker crashing.
Remediation
There is no fixed version for Debian:13 binutils.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2025-69651
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=ea4bc025abdba85a90e26e13f551c16a44bfa921
- https://sourceware.org/bugzilla/show_bug.cgi?id=33698
- https://sourceware.org/bugzilla/show_bug.cgi?id=33700
- https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=81e90cf63a10ad11772c2437c8f2a88f1a00c739
- https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=ea4bc025abdba85a90e26e13f551c16a44bfa92
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2025-3198
- https://sourceware.org/bugzilla/show_bug.cgi?id=32716#c0
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=ba6ad3a18cb26b79e0e3b84c39f707535bbc344d
- https://vuldb.com/?ctiid.303151
- https://vuldb.com/?id.303151
- https://www.gnu.org/
- https://vuldb.com/?submit.545773
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
- https://sourceware.org/bugzilla/show_bug.cgi?id=32716
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2025-11081
- https://github.com/user-attachments/files/20623354/hdf5_crash_3.txt
- https://sourceware.org/bugzilla/show_bug.cgi?id=33406
- https://sourceware.org/bugzilla/show_bug.cgi?id=33406#c2
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=f87a66db645caf8cc0e6fc87b0c28c78a38af59b
- https://vuldb.com/?ctiid.326122
- https://vuldb.com/?id.326122
- https://vuldb.com/?submit.661275
- https://www.gnu.org/
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2025-11495
- https://sourceware.org/bugzilla/attachment.cgi?id=16393
- https://sourceware.org/bugzilla/show_bug.cgi?id=33502
- https://sourceware.org/bugzilla/show_bug.cgi?id=33502#c3
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=6b21c8b2ecfef5c95142cbc2c32f185cb1c26ab0
- https://vuldb.com/?ctiid.327620
- https://vuldb.com/?id.327620
- https://vuldb.com/?submit.668290
- https://www.gnu.org/
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2025-11414
- https://sourceware.org/bugzilla/attachment.cgi?id=16361
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=aeaaa9af6359c8e394ce9cf24911fec4f4d23703
- https://vuldb.com/?ctiid.327350
- https://vuldb.com/?id.327350
- https://vuldb.com/?submit.665591
- https://www.gnu.org/
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://sourceware.org/bugzilla/show_bug.cgi?id=33450
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2025-11413
- https://sourceware.org/bugzilla/attachment.cgi?id=16362
- https://sourceware.org/bugzilla/show_bug.cgi?id=33456#c10
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=72efdf166aa0ed72ecc69fc2349af6591a7a19c0
- https://vuldb.com/?ctiid.327349
- https://vuldb.com/?id.327349
- https://vuldb.com/?submit.665587
- https://www.gnu.org/
- https://vuldb.com/?submit.665590
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://sourceware.org/bugzilla/show_bug.cgi?id=33452
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2025-11412
- https://sourceware.org/bugzilla/attachment.cgi?id=16378
- https://sourceware.org/bugzilla/show_bug.cgi?id=33452#c8
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=047435dd988a3975d40c6626a8f739a0b2e154bc
- https://vuldb.com/?ctiid.327348
- https://vuldb.com/?id.327348
- https://www.gnu.org/
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://sourceware.org/bugzilla/show_bug.cgi?id=33452
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2025-11494
- https://sourceware.org/bugzilla/attachment.cgi?id=16389
- https://sourceware.org/bugzilla/show_bug.cgi?id=33499
- https://sourceware.org/bugzilla/show_bug.cgi?id=33499#c2
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b6ac5a8a5b82f0ae6a4642c8d7149b325f4cc60a
- https://vuldb.com/?ctiid.327619
- https://vuldb.com/?id.327619
- https://vuldb.com/?submit.668281
- https://www.gnu.org/
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2025-11840
- https://sourceware.org/bugzilla/attachment.cgi?id=16351
- https://sourceware.org/bugzilla/attachment.cgi?id=16357
- https://sourceware.org/bugzilla/show_bug.cgi?id=33455
- https://vuldb.com/?ctiid.328775
- https://vuldb.com/?id.328775
- https://vuldb.com/?submit.661281
- https://www.gnu.org/
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2025-11839
- https://sourceware.org/bugzilla/attachment.cgi?id=16344
- https://vuldb.com/?ctiid.328774
- https://vuldb.com/?id.328774
- https://vuldb.com/?submit.661279
- https://www.gnu.org/
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://sourceware.org/bugzilla/show_bug.cgi?id=33448
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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.
Multiple Use-After-Free vulnerabilities were found in the add_archive_element function in ld/ldmain.c of the GNU linker (ld), a component of binutils. The root cause is that plugin_maybe_claim() in ld/plugin.c frees the original BFD object via bfd_close/_bfd_delete_bfd when entry->the_bfd->my_archive == NULL, but the caller retains both the original abfd parameter and a shallow copy (orig_input.the_bfd) as dangling pointers. These dangling pointers are subsequently dereferenced at three distinct locations in add_archive_element:
- Line ~1442: accessing abfd->my_archive via bfd_usrdata(abfd->my_archive)
- Line ~1493: multiple accesses to abfd and abfd->my_archive in a conditional check and bfd_get_filename call
- Line ~1525: dereferencing the shallow copy orig_input.the_bfd->my_archive in trace/verbose logging
The vulnerability is triggered when LTO plugins are active (link_info.lto_plugin_active is true) and the input object has abfd->my_archive == NULL, which is a valid state for standalone object files. Red Hat builds binutils with --enable-plugins and --enable-lto, confirming the vulnerable code path is compiled in and reachable.
An attacker who can supply a crafted object or archive file to a build process using LTO-enabled linking could exploit this flaw to cause a denial of service (linker crash via segmentation fault). Arbitrary code execution is theoretically possible through heap manipulation but is substantially mitigated by hardening measures including stack protector, FORTIFY_SOURCE, ASLR, and PIE.
The attack surface is limited to build-time environments — the linker is a development tool not exposed in production runtime. The most realistic exploitation scenario is a supply chain attack introducing a crafted object file as a build dependency in CI/CD pipelines or development environments.
Remediation
There is no fixed version for Debian:13 binutils.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.8.2-1~deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › expat/libexpat1@2.8.2-1~deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
In libexpat through 2.7.3, a crafted file with an approximate size of 2 MiB can lead to dozens of seconds of processing time.
Remediation
There is no fixed version for Debian:13 expat.
References
low severity
- Vulnerable module: patch
- Introduced through: patch@2.8-2
Detailed paths
-
Introduced through: php@8.2-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
- Vulnerable module: re2c
- Introduced through: re2c@4.1-1
Detailed paths
-
Introduced through: php@8.2-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
- Vulnerable module: tar
- Introduced through: tar@1.35+dfsg-3.1
Detailed paths
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2026-5704
- https://access.redhat.com/security/cve/CVE-2026-5704
- https://bugzilla.redhat.com/show_bug.cgi?id=2455360
- http://www.openwall.com/lists/oss-security/2026/04/11/10
- http://www.openwall.com/lists/oss-security/2026/04/11/11
- http://www.openwall.com/lists/oss-security/2026/04/12/2
- https://access.redhat.com/errata/RHSA-2026:61581
- https://access.redhat.com/errata/RHSA-2026:61783
- https://access.redhat.com/errata/RHSA-2026:61586
- https://access.redhat.com/errata/RHSA-2026:66018
- https://access.redhat.com/errata/RHSA-2026:66514
low severity
- Vulnerable module: util-linux
- Introduced through: util-linux@2.41-5, util-linux/libblkid1@2.41-5 and others
Detailed paths
-
Introduced through: php@8.2-apache › util-linux@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libblkid1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/liblastlog2-2@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libmount1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libsmartcols1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libuuid1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/mount@2.41-5
-
Introduced through: php@8.2-apache › util-linux/bsdutils@1:2.41-5
-
Introduced through: php@8.2-apache › util-linux/login@1:4.16.0-2+really2.41-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream util-linux package and not the util-linux package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A flaw was found in the util-linux chfn and chsh utilities when compiled with Readline support. The Readline library uses an "INPUTRC" environment variable to get a path to the library config file. When the library cannot parse the specified file, it prints an error message containing data from the file. This flaw allows an unprivileged user to read root-owned files, potentially leading to privilege escalation. This flaw affects util-linux versions prior to 2.37.4.
Remediation
There is no fixed version for Debian:13 util-linux.
References
- https://security-tracker.debian.org/tracker/CVE-2022-0563
- https://lore.kernel.org/util-linux/20220214110609.msiwlm457ngoic6w@ws.net.home/T/#u
- https://lore.kernel.org/util-linux/20220214110609.msiwlm457ngoic6w%40ws.net.home/T/#u
- https://security.gentoo.org/glsa/202401-08
- https://security.netapp.com/advisory/ntap-20220331-0002/
low severity
- Vulnerable module: zlib/zlib1g
- Introduced through: zlib/zlib1g@1:1.3.dfsg+really1.3.1-1+b1
Detailed paths
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2026-27171
- https://7asecurity.com/blog/2026/02/zlib-7asecurity-audit/
- https://github.com/madler/zlib/releases/tag/v1.3.2
- https://ostif.org/zlib-audit-complete/
- https://github.com/madler/zlib/issues/904
- https://7asecurity.com/reports/pentest-report-zlib-RC1.1.pdf
low severity
- Vulnerable module: nghttp2/libnghttp2-14
- Introduced through: nghttp2/libnghttp2-14@1.64.0-1.1+deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › nghttp2/libnghttp2-14@1.64.0-1.1+deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream nghttp2 package and not the nghttp2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
nghttp2's nghttpx proxy through 1.69.0 forwards an HTTP/1.1 Upgrade request that also carries a Content-Length header and body onto reusable keep-alive backend connections, re-adding the Upgrade and Connection headers while passing Content-Length verbatim. A backend that resolves the resulting ambiguous message in the attacker's favor enables HTTP request/response smuggling and cross-client response-queue poisoning.
Remediation
There is no fixed version for Debian:13 nghttp2.
References
- https://security-tracker.debian.org/tracker/CVE-2026-58055
- https://github.com/bikini/exploitarium/tree/main/nghttp2-nghttpx-upgrade-queue-poison-poc
- https://github.com/nghttp2/nghttp2/commit/ab28105c4a0197da24f8bfc414bc116055249e1e
- https://www.vulncheck.com/advisories/nghttp2-nghttpx-http-request-response-smuggling-via-upgrade-request-with-content-length
low severity
- Vulnerable module: patch
- Introduced through: patch@2.8-2
Detailed paths
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2010-4651
- http://support.apple.com/kb/HT4723
- http://lists.apple.com/archives/security-announce/2011//Jun/msg00000.html
- http://lists.fedoraproject.org/pipermail/package-announce/2011-March/055241.html
- http://lists.fedoraproject.org/pipermail/package-announce/2011-March/055246.html
- http://git.savannah.gnu.org/cgit/patch.git/commit/?id=685a78b6052f4df6eac6d625a545cfb54a6ac0e1
- http://lists.gnu.org/archive/html/bug-patch/2010-12/msg00000.html
- http://www.vupen.com/english/advisories/2011/0600
- http://openwall.com/lists/oss-security/2011/01/05/10
- http://openwall.com/lists/oss-security/2011/01/06/19
- http://openwall.com/lists/oss-security/2011/01/06/20
- http://openwall.com/lists/oss-security/2011/01/06/21
- https://bugzilla.redhat.com/show_bug.cgi?id=667529
- http://secunia.com/advisories/43663
- http://secunia.com/advisories/43677
- http://www.securityfocus.com/bid/46768
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2010-4651
low severity
- Vulnerable module: apache2
- Introduced through: apache2@2.4.68-1~deb13u1, apache2/apache2-bin@2.4.68-1~deb13u1 and others
Detailed paths
-
Introduced through: php@8.2-apache › apache2@2.4.68-1~deb13u1
-
Introduced through: php@8.2-apache › apache2/apache2-bin@2.4.68-1~deb13u1
-
Introduced through: php@8.2-apache › apache2/apache2-data@2.4.68-1~deb13u1
-
Introduced through: php@8.2-apache › apache2/apache2-utils@2.4.68-1~deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream apache2 package and not the apache2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
The mod_php module for the Apache HTTP Server allows local users with write access to PHP scripts to send signals to the server's process group and use the server's file descriptors, as demonstrated by sending a STOP signal, then intercepting incoming connections on the server's TCP port. NOTE: the PHP developer has disputed this vulnerability, saying "The opened file descriptors are opened by Apache. It is the job of Apache to protect them ... Not a bug in PHP.
Remediation
There is no fixed version for Debian:13 apache2.
References
- https://security-tracker.debian.org/tracker/CVE-2003-1307
- http://www.securityfocus.com/archive/1/348368
- http://www.securityfocus.com/archive/1/449234/100/0/threaded
- http://www.securityfocus.com/archive/1/449298/100/0/threaded
- http://bugs.php.net/38915
- http://hackerdom.ru/~dimmo/phpexpl.c
- http://www.securityfocus.com/bid/9302
low severity
- Vulnerable module: apache2
- Introduced through: apache2@2.4.68-1~deb13u1, apache2/apache2-bin@2.4.68-1~deb13u1 and others
Detailed paths
-
Introduced through: php@8.2-apache › apache2@2.4.68-1~deb13u1
-
Introduced through: php@8.2-apache › apache2/apache2-bin@2.4.68-1~deb13u1
-
Introduced through: php@8.2-apache › apache2/apache2-data@2.4.68-1~deb13u1
-
Introduced through: php@8.2-apache › apache2/apache2-utils@2.4.68-1~deb13u1
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
new
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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.47. This issue affects the function bfd_elf_set_group_contents of the file bfd/elf.c of the component SHT_GROUP Section Handler. Executing a manipulation can lead to null pointer dereference. The attack needs to be launched locally. The exploit has been made available to the public and could be used for attacks. The project was informed of the problem early through a bug report but has not responded yet.
Remediation
There is no fixed version for Debian:13 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2026-90829
- https://sourceware.org/bugzilla/attachment.cgi?id=16883
- https://vuldb.com/cve/CVE-2026-90829
- https://vuldb.com/submit/925228
- https://vuldb.com/vuln/403331
- https://vuldb.com/vuln/403331/cti
- https://www.gnu.org/
- https://sourceware.org/bugzilla/show_bug.cgi?id=34451
low severity
new
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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 vulnerability has been detected in GNU Binutils 2.47. Impacted is the function _bfd_write_merged_section of the file bfd/merge.c of the component Section Merge. The manipulation leads to null pointer dereference. The attack needs to be performed locally. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through a bug report but has not responded yet.
Remediation
There is no fixed version for Debian:13 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2026-90830
- https://sourceware.org/bugzilla/attachment.cgi?id=16884
- https://sourceware.org/bugzilla/show_bug.cgi?id=34452
- https://vuldb.com/cve/CVE-2026-90830
- https://vuldb.com/submit/925229
- https://vuldb.com/vuln/403332
- https://vuldb.com/vuln/403332/cti
- https://www.gnu.org/
low severity
new
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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.47. This vulnerability affects the function elf_orphan_compatible of the file ld/ldelf.c of the component ELF Orphan Section Handler. Performing a manipulation results in null pointer dereference. The attack must be initiated from a local position. The exploit has been released to the public and may be used for attacks. The project was informed of the problem early through a bug report but has not responded yet.
Remediation
There is no fixed version for Debian:13 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2026-90828
- https://sourceware.org/bugzilla/attachment.cgi?id=16882
- https://sourceware.org/bugzilla/show_bug.cgi?id=34450
- https://vuldb.com/cve/CVE-2026-90828
- https://vuldb.com/submit/925227
- https://vuldb.com/vuln/403330
- https://vuldb.com/vuln/403330/cti
- https://www.gnu.org/
low severity
new
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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.47. The affected element is the function _bfd_elf_strtab_delref of the file bfd/elf-strtab.c of the component ELF String Table. The manipulation results in memory corruption. The attack requires a local approach. The exploit is now public and may be used. The project was informed of the problem early through a bug report but has not responded yet.
Remediation
There is no fixed version for Debian:13 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2026-90831
- https://sourceware.org/bugzilla/attachment.cgi?id=16886
- https://sourceware.org/bugzilla/show_bug.cgi?id=34454
- https://vuldb.com/cve/CVE-2026-90831
- https://vuldb.com/submit/925230
- https://vuldb.com/vuln/403333
- https://vuldb.com/vuln/403333/cti
- https://www.gnu.org/
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2025-1147
- https://sourceware.org/bugzilla/attachment.cgi?id=15881
- https://sourceware.org/bugzilla/show_bug.cgi?id=32556
- https://vuldb.com/?ctiid.295051
- https://vuldb.com/?id.295051
- https://www.gnu.org/
- https://security.netapp.com/advisory/ntap-20250404-0003/
- https://vuldb.com/?submit.485254
low severity
- Vulnerable module: 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: php@8.2-apache › glibc/libc-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc-dev-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc6@2.41-12+deb13u3
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2019-1010024
- https://support.f5.com/csp/article/K06046097
- https://support.f5.com/csp/article/K06046097?utm_source=f5support&utm_medium=RSS
- https://sourceware.org/bugzilla/show_bug.cgi?id=22852
- http://www.securityfocus.com/bid/109162
- https://ubuntu.com/security/CVE-2019-1010024
- https://support.f5.com/csp/article/K06046097?utm_source=f5support&%3Butm_medium=RSS
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.41-12+deb13u3, glibc/libc-dev-bin@2.41-12+deb13u3 and others
Detailed paths
-
Introduced through: php@8.2-apache › glibc/libc-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc-dev-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc6@2.41-12+deb13u3
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2019-1010025
- https://support.f5.com/csp/article/K06046097
- https://support.f5.com/csp/article/K06046097?utm_source=f5support&utm_medium=RSS
- https://sourceware.org/bugzilla/show_bug.cgi?id=22853
- https://ubuntu.com/security/CVE-2019-1010025
- https://support.f5.com/csp/article/K06046097?utm_source=f5support&%3Butm_medium=RSS
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@257.13-1~deb13u1 and systemd/libudev1@257.13-1~deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › systemd/libsystemd0@257.13-1~deb13u1
-
Introduced through: php@8.2-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
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@257.13-1~deb13u1 and systemd/libudev1@257.13-1~deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › systemd/libsystemd0@257.13-1~deb13u1
-
Introduced through: php@8.2-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
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@257.13-1~deb13u1 and systemd/libudev1@257.13-1~deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › systemd/libsystemd0@257.13-1~deb13u1
-
Introduced through: php@8.2-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
- Vulnerable module: util-linux
- Introduced through: util-linux@2.41-5, util-linux/libblkid1@2.41-5 and others
Detailed paths
-
Introduced through: php@8.2-apache › util-linux@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libblkid1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/liblastlog2-2@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libmount1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libsmartcols1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libuuid1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/mount@2.41-5
-
Introduced through: php@8.2-apache › util-linux/bsdutils@1:2.41-5
-
Introduced through: php@8.2-apache › util-linux/login@1:4.16.0-2+really2.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
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2025-1176
- https://sourceware.org/bugzilla/attachment.cgi?id=15913
- https://sourceware.org/bugzilla/show_bug.cgi?id=32636
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=f9978defb6fab0bd8583942d97c112b0932ac814
- https://vuldb.com/?ctiid.295079
- https://vuldb.com/?id.295079
- https://vuldb.com/?submit.495329
- https://www.gnu.org/
- https://security.netapp.com/advisory/ntap-20250411-0007/
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2025-1181
- https://sourceware.org/bugzilla/attachment.cgi?id=15918
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=931494c9a89558acb36a03a340c01726545eef24
- https://vuldb.com/?ctiid.295084
- https://vuldb.com/?id.295084
- https://www.gnu.org/
- https://security.netapp.com/advisory/ntap-20250425-0007/
- https://sourceware.org/bugzilla/show_bug.cgi?id=32643
- https://vuldb.com/?submit.495402
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2025-1182
- https://sourceware.org/bugzilla/attachment.cgi?id=15919
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b425859021d17adf62f06fb904797cf8642986ad
- https://vuldb.com/?ctiid.295086
- https://vuldb.com/?id.295086
- https://www.gnu.org/
- https://sourceware.org/bugzilla/show_bug.cgi?id=32644
- https://vuldb.com/?submit.495407
low severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.21.3-5+deb13u1, krb5/libk5crypto3@1.21.3-5+deb13u1 and others
Detailed paths
-
Introduced through: php@8.2-apache › krb5/libgssapi-krb5-2@1.21.3-5+deb13u1
-
Introduced through: php@8.2-apache › krb5/libk5crypto3@1.21.3-5+deb13u1
-
Introduced through: php@8.2-apache › krb5/libkrb5-3@1.21.3-5+deb13u1
-
Introduced through: php@8.2-apache › krb5/libkrb5support0@1.21.3-5+deb13u1
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 integer underflow vulnerability was found in MIT krb5 in the berval2tl_data() function in plugins/kdb/ldap/libkdb_ldap/ldap_principal2.c. The function performs an unsigned subtraction (bv_len - 2) without a prior bounds check. When bv_len is 0 or 1, the subtraction wraps to a large value which is then truncated to uint16_t, yielding 0xFFFE (65534) or 0xFFFF (65535). The subsequent malloc succeeds and memcpy reads up to 65534 bytes from a 0-1 byte buffer, resulting in a heap out-of-bounds read. The attack vector involves a malicious or compromised LDAP KDB backend returning a krbExtraData attribute with bv_len < 2, triggering the underflow when the KDC or kadmind reads principal data.
Remediation
There is no fixed version for Debian:13 krb5.
References
low severity
- Vulnerable module: coreutils
- Introduced through: coreutils@9.7-3
Detailed paths
-
Introduced through: php@8.2-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
- Vulnerable module: openldap/libldap2
- Introduced through: openldap/libldap2@2.6.10+dfsg-1
Detailed paths
-
Introduced through: php@8.2-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
new
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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.47. Affected is the function bfd_putl64 of the file bfd/libbfd.c of the component ld. This manipulation causes null pointer dereference. The attack requires local access. The exploit has been made available to the public and could be used for attacks. The project was informed of the problem early through a bug report but has not responded yet.
Remediation
There is no fixed version for Debian:13 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2026-90802
- https://github.com/r1ck9-2q/cve_summit/blob/main/SEGV%20in%20%60bfd_putl64%60%20(bfdlibbfd.c989)%20during%20relocation%20output%20via%20malformed%20ELF.md
- https://sourceware.org/bugzilla/show_bug.cgi?id=34443
- https://vuldb.com/cve/CVE-2026-90802
- https://vuldb.com/submit/920277
- https://vuldb.com/vuln/403304
- https://vuldb.com/vuln/403304/cti
- https://www.gnu.org/
low severity
- Vulnerable module: coreutils
- Introduced through: coreutils@9.7-3
Detailed paths
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2025-5278
- https://access.redhat.com/security/cve/CVE-2025-5278
- https://bugzilla.redhat.com/show_bug.cgi?id=2368764
- http://www.openwall.com/lists/oss-security/2025/05/27/2
- http://www.openwall.com/lists/oss-security/2025/05/29/1
- https://cgit.git.savannah.gnu.org/cgit/coreutils.git/tree/NEWS?id=8c9602e3a145e9596dc1a63c6ed67865814b6633#n14
- http://www.openwall.com/lists/oss-security/2025/05/29/2
- https://debbugs.gnu.org/cgi/bugreport.cgi?bug=78507
- https://access.redhat.com/errata/RHSA-2026:28911
- https://access.redhat.com/errata/RHSA-2026:33124
- https://access.redhat.com/errata/RHSA-2026:33313
- https://access.redhat.com/errata/RHSA-2026:33612
- https://access.redhat.com/errata/RHSA-2026:34102
- https://access.redhat.com/errata/RHSA-2026:39981
- https://access.redhat.com/errata/RHSA-2026:44481
- https://access.redhat.com/errata/RHSA-2026:46836
- https://access.redhat.com/errata/RHSA-2026:50205
- https://access.redhat.com/errata/RHSA-2026:58981
- https://cgit.git.savannah.gnu.org/cgit/coreutils.git/commit/?id=8c9602e3a145e9596dc1a63c6ed67865814b6633
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@257.13-1~deb13u1 and systemd/libudev1@257.13-1~deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › systemd/libsystemd0@257.13-1~deb13u1
-
Introduced through: php@8.2-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
- Vulnerable module: tar
- Introduced through: tar@1.35+dfsg-3.1
Detailed paths
-
Introduced through: php@8.2-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 GNU tar. When extracting an archive with the --one-top-level option, hardlink targets are not confined to the designated top-level directory and may resolve relative to the extraction working directory. A crafted archive can create hardlinks that escape the intended boundary and, when combined with a preexisting symbolic link under the working directory, may allow writing outside that boundary during a single extraction.
Remediation
There is no fixed version for Debian:13 tar.
References
- https://security-tracker.debian.org/tracker/CVE-2026-18508
- https://access.redhat.com/errata/RHSA-2026:50807
- https://access.redhat.com/security/cve/CVE-2026-18508
- https://bugzilla.redhat.com/show_bug.cgi?id=2509843
- https://access.redhat.com/errata/RHSA-2026:61581
- https://access.redhat.com/errata/RHSA-2026:61783
- https://access.redhat.com/errata/RHSA-2026:61586
- https://access.redhat.com/errata/RHSA-2026:66018
low severity
- Vulnerable module: tar
- Introduced through: tar@1.35+dfsg-3.1
Detailed paths
-
Introduced through: php@8.2-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 TOCTOU (Time-of-Check Time-of-Use) vulnerability in GNU tar's incremental dumpdir 'X' rename handling allows a local attacker with write access to a directory being backed up to influence the restore process if the attacker has access to the system where the restore is being performed. During restoration, files or directories may be created, renamed or overwritten outside the intended extraction directory. This could lead to unauthorized file modification or, in some cases, privilege escalation. Exploitation does not require the attacker to modify or craft the archive, and standard backup and restore workflows—including extracting into a newly created directory without using the -P option do not mitigate the issue.
Remediation
There is no fixed version for Debian:13 tar.
References
- https://security-tracker.debian.org/tracker/CVE-2026-18477
- https://access.redhat.com/errata/RHSA-2026:49361
- https://access.redhat.com/security/cve/CVE-2026-18477
- https://bugzilla.redhat.com/show_bug.cgi?id=2509735
- https://access.redhat.com/errata/RHSA-2026:61581
- https://access.redhat.com/errata/RHSA-2026:61783
- https://access.redhat.com/errata/RHSA-2026:61586
- https://access.redhat.com/errata/RHSA-2026:66018
low severity
- Vulnerable module: apache2
- Introduced through: apache2@2.4.68-1~deb13u1, apache2/apache2-bin@2.4.68-1~deb13u1 and others
Detailed paths
-
Introduced through: php@8.2-apache › apache2@2.4.68-1~deb13u1
-
Introduced through: php@8.2-apache › apache2/apache2-bin@2.4.68-1~deb13u1
-
Introduced through: php@8.2-apache › apache2/apache2-data@2.4.68-1~deb13u1
-
Introduced through: php@8.2-apache › apache2/apache2-utils@2.4.68-1~deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream apache2 package and not the apache2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
The Apache HTTP Server 2.0.44, when DNS resolution is enabled for client IP addresses, uses a logging format that does not identify whether a dotted quad represents an unresolved IP address, which allows remote attackers to spoof IP addresses via crafted DNS responses containing numerical top-level domains, as demonstrated by a forged 123.123.123.123 domain name, related to an "Inverse Lookup Log Corruption (ILLC)" issue.
Remediation
There is no fixed version for Debian:13 apache2.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.41-12+deb13u3, glibc/libc-dev-bin@2.41-12+deb13u3 and others
Detailed paths
-
Introduced through: php@8.2-apache › glibc/libc-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc-dev-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc6@2.41-12+deb13u3
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2010-4756
- http://cxib.net/stuff/glob-0day.c
- http://securityreason.com/achievement_securityalert/89
- http://securityreason.com/exploitalert/9223
- https://bugzilla.redhat.com/show_bug.cgi?id=681681
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2010-4756
- https://security.netapp.com/advisory/ntap-20241108-0002/
low severity
- Vulnerable module: gnutls28/libgnutls30t64
- Introduced through: gnutls28/libgnutls30t64@3.8.9-3+deb13u4
Detailed paths
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2011-3389
- http://lists.apple.com/archives/Security-announce/2011//Oct/msg00001.html
- http://lists.apple.com/archives/Security-announce/2011//Oct/msg00002.html
- http://support.apple.com/kb/HT4999
- http://support.apple.com/kb/HT5001
- http://support.apple.com/kb/HT5130
- http://support.apple.com/kb/HT5281
- http://support.apple.com/kb/HT5501
- http://support.apple.com/kb/HT6150
- http://lists.apple.com/archives/security-announce/2012/Feb/msg00000.html
- http://lists.apple.com/archives/security-announce/2012/Jul/msg00001.html
- http://lists.apple.com/archives/security-announce/2012/May/msg00001.html
- http://lists.apple.com/archives/security-announce/2012/Sep/msg00004.html
- http://lists.apple.com/archives/security-announce/2013/Oct/msg00004.html
- http://www.us-cert.gov/cas/techalerts/TA12-010A.html
- http://www.kb.cert.org/vuls/id/864643
- http://googlechromereleases.blogspot.com/2011/10/chrome-stable-release.html
- http://blog.mozilla.com/security/2011/09/27/attack-against-tls-protected-communications/
- http://blogs.technet.com/b/msrc/archive/2011/09/26/microsoft-releases-security-advisory-2588513.aspx
- http://blogs.technet.com/b/srd/archive/2011/09/26/is-ssl-broken-more-about-security-advisory-2588513.aspx
- http://curl.haxx.se/docs/adv_20120124B.html
- http://downloads.asterisk.org/pub/security/AST-2016-001.html
- http://my.opera.com/securitygroup/blog/2011/09/28/the-beast-ssl-tls-issue
- https://blogs.oracle.com/sunsecurity/entry/multiple_vulnerabilities_in_fetchmail
- https://bugzilla.novell.com/show_bug.cgi?id=719047
- https://cert-portal.siemens.com/productcert/pdf/ssa-556833.pdf
- http://technet.microsoft.com/security/advisory/2588513
- http://www.apcmedia.com/salestools/SJHN-7RKGNM/SJHN-7RKGNM_R4_EN.pdf
- http://www.ibm.com/developerworks/java/jdk/alerts/
- http://www.imperialviolet.org/2011/09/23/chromeandbeast.html
- http://www.opera.com/docs/changelogs/mac/1151/
- http://www.opera.com/docs/changelogs/mac/1160/
- http://www.opera.com/docs/changelogs/unix/1151/
- http://www.opera.com/docs/changelogs/unix/1160/
- http://www.opera.com/docs/changelogs/windows/1151/
- http://www.opera.com/docs/changelogs/windows/1160/
- http://www.opera.com/support/kb/view/1004/
- http://www.debian.org/security/2012/dsa-2398
- http://security.gentoo.org/glsa/glsa-201203-02.xml
- http://security.gentoo.org/glsa/glsa-201406-32.xml
- https://h20564.www2.hp.com/portal/site/hpsc/public/kb/docDisplay?docId=emr_na-c03839862
- http://marc.info/?l=bugtraq&m=132750579901589&w=2
- http://marc.info/?l=bugtraq&m=132872385320240&w=2
- http://marc.info/?l=bugtraq&m=133365109612558&w=2
- http://marc.info/?l=bugtraq&m=133728004526190&w=2
- http://marc.info/?l=bugtraq&m=134254866602253&w=2
- http://marc.info/?l=bugtraq&m=134254957702612&w=2
- http://ekoparty.org/2011/juliano-rizzo.php
- http://eprint.iacr.org/2004/111
- http://eprint.iacr.org/2006/136
- http://isc.sans.edu/diary/SSL+TLS+part+3+/11635
- https://ics-cert.us-cert.gov/advisories/ICSMA-18-058-02
- http://vnhacker.blogspot.com/2011/09/beast.html
- http://www.educatedguesswork.org/2011/09/security_impact_of_the_rizzodu.html
- http://www.insecure.cl/Beast-SSL.rar
- https://docs.microsoft.com/en-us/security-updates/securitybulletins/2012/ms12-006
- http://technet.microsoft.com/security/bulletin/MS12-006
- http://lists.opensuse.org/opensuse-security-announce/2012-01/msg00049.html
- http://lists.opensuse.org/opensuse-security-announce/2012-01/msg00051.html
- http://lists.opensuse.org/opensuse-security-announce/2012-05/msg00009.html
- http://www.oracle.com/technetwork/topics/security/cpujan2015-1972971.html
- http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html
- http://www.oracle.com/technetwork/topics/security/javacpuoct2011-443431.html
- http://osvdb.org/74829
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14752
- https://bugzilla.redhat.com/show_bug.cgi?id=737506
- http://rhn.redhat.com/errata/RHSA-2012-0508.html
- http://rhn.redhat.com/errata/RHSA-2013-1455.html
- http://secunia.com/advisories/45791
- http://secunia.com/advisories/47998
- http://secunia.com/advisories/48256
- http://secunia.com/advisories/48692
- http://secunia.com/advisories/48915
- http://secunia.com/advisories/48948
- http://secunia.com/advisories/49198
- http://secunia.com/advisories/55322
- http://secunia.com/advisories/55350
- http://secunia.com/advisories/55351
- http://www.securityfocus.com/bid/49388
- http://www.securityfocus.com/bid/49778
- http://www.securitytracker.com/id?1025997
- http://www.securitytracker.com/id?1026103
- http://www.securitytracker.com/id?1026704
- http://www.securitytracker.com/id/1029190
- http://lists.opensuse.org/opensuse-security-announce/2020-01/msg00040.html
- https://hermes.opensuse.org/messages/13154861
- https://hermes.opensuse.org/messages/13155432
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2011-3389
- http://www.ubuntu.com/usn/USN-1263-1
- http://www.mandriva.com/security/advisories?name=MDVSA-2012:058
- http://www.redhat.com/support/errata/RHSA-2011-1384.html
- http://www.redhat.com/support/errata/RHSA-2012-0006.html
- https://github.com/mpgn/BEAST-PoC
low severity
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.46.1-7+deb13u1
Detailed paths
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2021-45346
- https://github.com/guyinatuxedo/sqlite3_record_leaking
- https://security.netapp.com/advisory/ntap-20220303-0001/
- https://sqlite.org/forum/forumpost/056d557c2f8c452ed5
- https://sqlite.org/forum/forumpost/53de8864ba114bf6
- https://www.sqlite.org/cves.html#status_of_recent_sqlite_cves
low severity
- Vulnerable module: openldap/libldap2
- Introduced through: openldap/libldap2@2.6.10+dfsg-1
Detailed paths
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2020-15719
- https://access.redhat.com/errata/RHBA-2019:3674
- https://bugs.openldap.org/show_bug.cgi?id=9266
- https://bugzilla.redhat.com/show_bug.cgi?id=1740070
- http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00033.html
- http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00059.html
- https://kc.mcafee.com/corporate/index?page=content&id=SB10365
- https://www.oracle.com/security-alerts/cpuapr2022.html
low severity
- Vulnerable module: apache2
- Introduced through: apache2@2.4.68-1~deb13u1, apache2/apache2-bin@2.4.68-1~deb13u1 and others
Detailed paths
-
Introduced through: php@8.2-apache › apache2@2.4.68-1~deb13u1
-
Introduced through: php@8.2-apache › apache2/apache2-bin@2.4.68-1~deb13u1
-
Introduced through: php@8.2-apache › apache2/apache2-data@2.4.68-1~deb13u1
-
Introduced through: php@8.2-apache › apache2/apache2-utils@2.4.68-1~deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream apache2 package and not the apache2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
mod_usertrack in Apache 1.3.11 through 1.3.20 generates session ID's using predictable information including host IP address, system time and server process ID, which allows local users to obtain session ID's and bypass authentication when these session ID's are used for authentication.
Remediation
There is no fixed version for Debian:13 apache2.
References
low severity
- Vulnerable module: apache2
- Introduced through: apache2@2.4.68-1~deb13u1, apache2/apache2-bin@2.4.68-1~deb13u1 and others
Detailed paths
-
Introduced through: php@8.2-apache › apache2@2.4.68-1~deb13u1
-
Introduced through: php@8.2-apache › apache2/apache2-bin@2.4.68-1~deb13u1
-
Introduced through: php@8.2-apache › apache2/apache2-data@2.4.68-1~deb13u1
-
Introduced through: php@8.2-apache › apache2/apache2-utils@2.4.68-1~deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream apache2 package and not the apache2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
CRLF injection vulnerability in the mod_negotiation module in the Apache HTTP Server 2.2.6 and earlier in the 2.2.x series, 2.0.61 and earlier in the 2.0.x series, and 1.3.39 and earlier in the 1.3.x series allows remote authenticated users to inject arbitrary HTTP headers and conduct HTTP response splitting attacks by uploading a file with a multi-line name containing HTTP header sequences and a file extension, which leads to injection within a (1) "406 Not Acceptable" or (2) "300 Multiple Choices" HTTP response when the extension is omitted in a request for the file.
Remediation
There is no fixed version for Debian:13 apache2.
References
- https://security-tracker.debian.org/tracker/CVE-2008-0456
- https://lists.apache.org/thread.html/8d63cb8e9100f28a99429b4328e4e7cebce861d5772ac9863ba2ae6f@%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/f7f95ac1cd9895db2714fa3ebaa0b94d0c6df360f742a40951384a53@%3Ccvs.httpd.apache.org%3E
- http://support.apple.com/kb/HT3549
- http://lists.apple.com/archives/security-announce/2009/May/msg00002.html
- http://www.securityfocus.com/archive/1/486847/100/0/threaded
- http://www.us-cert.gov/cas/techalerts/TA09-133A.html
- http://security.gentoo.org/glsa/glsa-200803-19.xml
- http://www.mindedsecurity.com/MSA01150108.html
- https://lists.apache.org/thread.html/r57608dc51b79102f3952ae06f54d5277b649c86d6533dcd6a7d201f7@%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/r75cbe9ea3e2114e4271bbeca7aff96117b50c1b6eb7c4772b0337c1f@%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/r7dd6be4dc38148704f2edafb44a8712abaa3a2be120d6c3314d55919@%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/r84d043c2115176958562133d96d851495d712aa49da155d81f6733be@%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/r9ea3538f229874c80a10af473856a81fbf5f694cd7f471cc679ba70b@%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/r9f93cf6dde308d42a9c807784e8102600d0397f5f834890708bf6920@%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/rc4c53a0d57b2771ecd4b965010580db355e38137c8711311ee1073a8@%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/rdca61ae990660bacb682295f2a09d34612b7bb5f457577fe17f4d064@%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/rf6449464fd8b7437704c55f88361b66f12d5b5f90bcce66af4be4ba9@%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/rfbaf647d52c1cb843e726a0933f156366a806cead84fbd430951591b@%3Ccvs.httpd.apache.org%3E
- http://rhn.redhat.com/errata/RHSA-2013-0130.html
- http://securitytracker.com/id?1019256
- http://secunia.com/advisories/29348
- http://secunia.com/advisories/35074
- http://www.securityfocus.com/bid/27409
- http://securityreason.com/securityalert/3575
- http://www.vupen.com/english/advisories/2009/1297
- https://exchange.xforce.ibmcloud.com/vulnerabilities/39893
- https://lists.apache.org/thread.html/8d63cb8e9100f28a99429b4328e4e7cebce861d5772ac9863ba2ae6f%40%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/f7f95ac1cd9895db2714fa3ebaa0b94d0c6df360f742a40951384a53%40%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/r57608dc51b79102f3952ae06f54d5277b649c86d6533dcd6a7d201f7%40%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/r75cbe9ea3e2114e4271bbeca7aff96117b50c1b6eb7c4772b0337c1f%40%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/r7dd6be4dc38148704f2edafb44a8712abaa3a2be120d6c3314d55919%40%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/r84d043c2115176958562133d96d851495d712aa49da155d81f6733be%40%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/r9ea3538f229874c80a10af473856a81fbf5f694cd7f471cc679ba70b%40%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/r9f93cf6dde308d42a9c807784e8102600d0397f5f834890708bf6920%40%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/rc4c53a0d57b2771ecd4b965010580db355e38137c8711311ee1073a8%40%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/rdca61ae990660bacb682295f2a09d34612b7bb5f457577fe17f4d064%40%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/rf6449464fd8b7437704c55f88361b66f12d5b5f90bcce66af4be4ba9%40%3Ccvs.httpd.apache.org%3E
- https://lists.apache.org/thread.html/rfbaf647d52c1cb843e726a0933f156366a806cead84fbd430951591b%40%3Ccvs.httpd.apache.org%3E
low severity
- Vulnerable module: apache2
- Introduced through: apache2@2.4.68-1~deb13u1, apache2/apache2-bin@2.4.68-1~deb13u1 and others
Detailed paths
-
Introduced through: php@8.2-apache › apache2@2.4.68-1~deb13u1
-
Introduced through: php@8.2-apache › apache2/apache2-bin@2.4.68-1~deb13u1
-
Introduced through: php@8.2-apache › apache2/apache2-data@2.4.68-1~deb13u1
-
Introduced through: php@8.2-apache › apache2/apache2-utils@2.4.68-1~deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream apache2 package and not the apache2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
The Apache HTTP Server 2.0.44, when DNS resolution is enabled for client IP addresses, allows remote attackers to inject arbitrary text into log files via an HTTP request in conjunction with a crafted DNS response, as demonstrated by injecting XSS sequences, related to an "Inverse Lookup Log Corruption (ILLC)" issue.
Remediation
There is no fixed version for Debian:13 apache2.
References
low severity
- Vulnerable module: apt
- Introduced through: apt@3.0.3 and apt/libapt-pkg7.0@3.0.3
Detailed paths
-
Introduced through: php@8.2-apache › apt@3.0.3
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2011-3374
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642480
- https://people.canonical.com/~ubuntu-security/cve/2011/CVE-2011-3374.html
- https://seclists.org/fulldisclosure/2011/Sep/221
- https://snyk.io/vuln/SNYK-LINUX-APT-116518
- https://ubuntu.com/security/CVE-2011-3374
- https://access.redhat.com/security/cve/cve-2011-3374
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
new
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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.47. This affects the function _bfd_elf_eh_frame_section_offset of the file bfd/elf-eh-frame.c of the component Eh Frame Handler. Performing a manipulation results in null pointer dereference. The attack must be initiated from a local position. The exploit has been released to the public and may be used for attacks. The project was informed of the problem early through a bug report but has not responded yet.
Remediation
There is no fixed version for Debian:13 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2026-91779
- https://github.com/Ech06/CVE_submit/blob/main/bugzilla/issues/34446.md
- https://sourceware.org/bugzilla/show_bug.cgi?id=34446
- https://vuldb.com/cve/CVE-2026-91779
- https://vuldb.com/submit/933333
- https://vuldb.com/vuln/404050
- https://vuldb.com/vuln/404050/cti
- https://www.gnu.org/
low severity
new
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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.47. Affected by this vulnerability is the function elf_x86_allocate_dynrelocs of the file bfd/elfxx-x86.c of the component Dynamic Relocation Allocation. The manipulation results in null pointer dereference. The attack requires a local approach. The exploit is now public and may be used. Upgrading to version 2.48 addresses this issue. The patch is identified as d1268210b6f6/471130b39c0/283d3198bed/0a84e560216/a692a633d40. Upgrading the affected component is recommended.
Remediation
There is no fixed version for Debian:13 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2026-91782
- https://github.com/Ech06/CVE_submit/tree/main/bugzilla/pocs/34448
- https://sourceware.org/bugzilla/show_bug.cgi?id=34448
- https://vuldb.com/cve/CVE-2026-91782
- https://vuldb.com/submit/933335
- https://vuldb.com/vuln/404053
- https://vuldb.com/vuln/404053/cti
- https://www.gnu.org/
low severity
new
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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 vulnerability has been detected in GNU Binutils 2.47. Affected is the function elf_x86_64_common_section_index of the file bfd/elf64-x86-64.c of the component ELF Section Handler. The manipulation leads to null pointer dereference. The attack needs to be performed locally. The exploit has been disclosed publicly and may be used. Upgrading to version 2.48 is able to address this issue. The identifier of the patch is 7322e9bc30cb282575a701c307851fd3d66fee68. It is suggested to upgrade the affected component.
Remediation
There is no fixed version for Debian:13 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2026-91781
- https://github.com/Ech06/CVE_submit/tree/main/bugzilla/pocs/34449
- https://sourceware.org/bugzilla/show_bug.cgi?id=34449
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=7322e9bc30cb282575a701c307851fd3d66fee68
- https://vuldb.com/cve/CVE-2026-91781
- https://vuldb.com/submit/933336
- https://vuldb.com/vuln/404052
- https://vuldb.com/vuln/404052/cti
- https://www.gnu.org/
low severity
new
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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.47. This impacts the function elf_link_add_object_symbols of the file bfd/elflink.c. Executing a manipulation can lead to null pointer dereference. The attack needs to be launched locally. The exploit has been made available to the public and could be used for attacks. The project was informed of the problem early through a bug report but has not responded yet.
Remediation
There is no fixed version for Debian:13 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2026-91780
- https://github.com/Ech06/CVE_submit/tree/main/bugzilla/pocs/34447
- https://vuldb.com/cve/CVE-2026-91780
- https://vuldb.com/vuln/404051
- https://vuldb.com/vuln/404051/cti
- https://www.gnu.org/
- https://sourceware.org/bugzilla/show_bug.cgi?id=34447
- https://vuldb.com/submit/933334
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
new
- Vulnerable module: libxml2
- Introduced through: libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3
Detailed paths
-
Introduced through: php@8.2-apache › libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3
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.
xmlregexp in libxml2 before 2.15.4 has a NULL pointer dereference in xmlRegNewParserCtxt after a strdup failure, i.e., it does not calculate a string length after NULL checking.
Remediation
There is no fixed version for Debian:13 libxml2.
References
low severity
- Vulnerable module: ncurses/libncursesw6
- Introduced through: ncurses/libncursesw6@6.5+20250216-2, ncurses/libtinfo6@6.5+20250216-2 and others
Detailed paths
-
Introduced through: php@8.2-apache › ncurses/libncursesw6@6.5+20250216-2
-
Introduced through: php@8.2-apache › ncurses/libtinfo6@6.5+20250216-2
-
Introduced through: php@8.2-apache › ncurses/ncurses-base@6.5+20250216-2
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2025-6141
- https://invisible-island.net/ncurses/NEWS.html#index-t20250329
- https://lists.gnu.org/archive/html/bug-ncurses/2025-03/msg00107.html
- https://lists.gnu.org/archive/html/bug-ncurses/2025-03/msg00109.html
- https://lists.gnu.org/archive/html/bug-ncurses/2025-03/msg00114.html
- https://vuldb.com/?ctiid.312610
- https://vuldb.com/?id.312610
- https://vuldb.com/?submit.593000
- https://www.gnu.org/
- https://cert-portal.siemens.com/productcert/html/ssa-089022.html
- https://cert-portal.siemens.com/productcert/html/ssa-253495.html
low severity
new
- Vulnerable module: pcre2/libpcre2-8-0
- Introduced through: pcre2/libpcre2-8-0@10.46-1~deb13u1
- Fixed in: 10.46-1~deb13u2
Detailed paths
-
Introduced through: php@8.2-apache › pcre2/libpcre2-8-0@10.46-1~deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream pcre2 package and not the pcre2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
In PCRE2 before 10.48, pcre2_serialize_encode might disclose two bytes to an adversary, typically in a situation where the access available to the adversary is already unsafe.
Remediation
Upgrade Debian:13 pcre2 to version 10.46-1~deb13u2 or higher.
References
low severity
- Vulnerable module: perl
- Introduced through: perl@5.40.1-6, perl/libperl5.40@5.40.1-6 and others
Detailed paths
-
Introduced through: php@8.2-apache › perl@5.40.1-6
-
Introduced through: php@8.2-apache › perl/libperl5.40@5.40.1-6
-
Introduced through: php@8.2-apache › perl/perl-base@5.40.1-6
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2011-4116
- https://github.com/Perl-Toolchain-Gang/File-Temp/issues/14
- https://rt.cpan.org/Public/Bug/Display.html?id=69106
- https://seclists.org/oss-sec/2011/q4/238
- http://www.openwall.com/lists/oss-security/2011/11/04/2
- http://www.openwall.com/lists/oss-security/2011/11/04/4
low severity
- Vulnerable module: re2c
- Introduced through: re2c@4.1-1
Detailed paths
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2026-2903
- https://github.com/oneafter/0202/blob/main/re/repro
- https://github.com/skvadrik/re2c/
- https://github.com/skvadrik/re2c/commit/febeb977936f9519a25d9fbd10ff8256358cdb97
- https://github.com/skvadrik/re2c/issues/571
- https://github.com/skvadrik/re2c/issues/571#issuecomment-3837675101
- https://vuldb.com/?ctiid.347210
- https://vuldb.com/?id.347210
- https://vuldb.com/?submit.755030
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@257.13-1~deb13u1 and systemd/libudev1@257.13-1~deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › systemd/libsystemd0@257.13-1~deb13u1
-
Introduced through: php@8.2-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
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2025-1148
- https://sourceware.org/bugzilla/attachment.cgi?id=15887
- https://sourceware.org/bugzilla/show_bug.cgi?id=32576
- https://vuldb.com/?ctiid.295052
- https://vuldb.com/?id.295052
- https://vuldb.com/?submit.485747
- https://www.gnu.org/
- https://security.netapp.com/advisory/ntap-20250404-0004/
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- Vulnerable module: apr-util/libaprutil1-dbd-sqlite3
- Introduced through: apr-util/libaprutil1-dbd-sqlite3@1.6.3-3+b1, apr-util/libaprutil1-ldap@1.6.3-3+b1 and others
- Fixed in: 1.6.3-3+deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › apr-util/libaprutil1-dbd-sqlite3@1.6.3-3+b1
-
Introduced through: php@8.2-apache › apr-util/libaprutil1-ldap@1.6.3-3+b1
-
Introduced through: php@8.2-apache › apr-util/libaprutil1t64@1.6.3-3+b1
NVD Description
Note: Versions mentioned in the description apply only to the upstream apr-util package and not the apr-util package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
Heap-based Buffer Overflow vulnerability in Apache Portable Runtime Utility redis client.
This issue affects Apache Portable Runtime Utility: from 1.6.0 through 1.6.3.
Users are recommended to upgrade to version 1.6.4, which fixes the issue.
Remediation
Upgrade Debian:13 apr-util to version 1.6.3-3+deb13u1 or higher.
References
low severity
- Vulnerable module: apr-util/libaprutil1-dbd-sqlite3
- Introduced through: apr-util/libaprutil1-dbd-sqlite3@1.6.3-3+b1, apr-util/libaprutil1-ldap@1.6.3-3+b1 and others
- Fixed in: 1.6.3-3+deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › apr-util/libaprutil1-dbd-sqlite3@1.6.3-3+b1
-
Introduced through: php@8.2-apache › apr-util/libaprutil1-ldap@1.6.3-3+b1
-
Introduced through: php@8.2-apache › apr-util/libaprutil1t64@1.6.3-3+b1
NVD Description
Note: Versions mentioned in the description apply only to the upstream apr-util package and not the apr-util package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
Heap-based Buffer Overflow vulnerability in Apache Portable Runtime Utility memcached client
This issue affects Apache Portable Runtime Utility: from 1.3.0 through 1.6.3.
Remediation
Upgrade Debian:13 apr-util to version 1.6.3-3+deb13u1 or higher.
References
low severity
- Vulnerable module: apr-util/libaprutil1-dbd-sqlite3
- Introduced through: apr-util/libaprutil1-dbd-sqlite3@1.6.3-3+b1, apr-util/libaprutil1-ldap@1.6.3-3+b1 and others
- Fixed in: 1.6.3-3+deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › apr-util/libaprutil1-dbd-sqlite3@1.6.3-3+b1
-
Introduced through: php@8.2-apache › apr-util/libaprutil1-ldap@1.6.3-3+b1
-
Introduced through: php@8.2-apache › apr-util/libaprutil1t64@1.6.3-3+b1
NVD Description
Note: Versions mentioned in the description apply only to the upstream apr-util package and not the apr-util package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
APR-util versions 1.6.3 (and earlier) function apr_password_validate() was not constant-time with regards to hashes or passwords comparisons, potentially leaking their content via a side channel timing attack particularly on platforms without crypt() such as Windows, BeOS, NetWare, or Android.
Users are recommended to upgrade to version 1.6.4, which fixes this issue.
Remediation
Upgrade Debian:13 apr-util to version 1.6.3-3+deb13u1 or higher.
References
low severity
- Vulnerable module: apr-util/libaprutil1-dbd-sqlite3
- Introduced through: apr-util/libaprutil1-dbd-sqlite3@1.6.3-3+b1, apr-util/libaprutil1-ldap@1.6.3-3+b1 and others
- Fixed in: 1.6.3-3+deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › apr-util/libaprutil1-dbd-sqlite3@1.6.3-3+b1
-
Introduced through: php@8.2-apache › apr-util/libaprutil1-ldap@1.6.3-3+b1
-
Introduced through: php@8.2-apache › apr-util/libaprutil1t64@1.6.3-3+b1
NVD Description
Note: Versions mentioned in the description apply only to the upstream apr-util package and not the apr-util package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Apache Portable Runtime Utility via apr_dbd_oracle provider.
This issue affects Apache Portable Runtime Utility: from 1.6.0 through 1.6.3
Remediation
Upgrade Debian:13 apr-util to version 1.6.3-3+deb13u1 or higher.
References
low severity
- Vulnerable module: apr-util/libaprutil1-dbd-sqlite3
- Introduced through: apr-util/libaprutil1-dbd-sqlite3@1.6.3-3+b1, apr-util/libaprutil1-ldap@1.6.3-3+b1 and others
- Fixed in: 1.6.3-3+deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › apr-util/libaprutil1-dbd-sqlite3@1.6.3-3+b1
-
Introduced through: php@8.2-apache › apr-util/libaprutil1-ldap@1.6.3-3+b1
-
Introduced through: php@8.2-apache › apr-util/libaprutil1t64@1.6.3-3+b1
NVD Description
Note: Versions mentioned in the description apply only to the upstream apr-util package and not the apr-util package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
A bug in APR-util version 1.6.3 (and earlier) allows a stack recursion attack against any library consumer which parses XML from untrusted sources and uses the apr_xml_quote_elem() function.
Users are recommended to upgrade to version 1.6.4, which fixes this issue.
Remediation
Upgrade Debian:13 apr-util to version 1.6.3-3+deb13u1 or higher.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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
- Vulnerable module: binutils
- Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others
Detailed paths
-
Introduced through: php@8.2-apache › binutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-common@2.44-3
-
Introduced through: php@8.2-apache › binutils/binutils-x86-64-linux-gnu@2.44-3
-
Introduced through: php@8.2-apache › binutils/libbinutils@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf-nobfd0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libctf0@2.44-3
-
Introduced through: php@8.2-apache › binutils/libgprofng0@2.44-3
-
Introduced through: php@8.2-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.
Rejected reason: Red Hat Product Security has come to the conclusion that this CVE is false due to upstream security policy.
Remediation
There is no fixed version for Debian:13 binutils.
References
low severity
- Vulnerable module: bzip2
- Introduced through: bzip2@1.0.8-6 and bzip2/libbz2-1.0@1.0.8-6
Detailed paths
-
Introduced through: php@8.2-apache › bzip2@1.0.8-6
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2026-42250
- https://cert.pl/en/posts/2026/05/CVE-2026-42250/
- https://sourceware.org/bzip2/
- https://inbox.sourceware.org/bzip2-devel/20260528145407.293768-1-mark@klomp.org/
- https://sourceware.org/cgit/bzip2/commit/?id=35d122a3df8b0cc4082a4d89fdc6ee99f375fe67
low severity
- Vulnerable module: curl
- Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4
Detailed paths
-
Introduced through: php@8.2-apache › curl@8.14.1-2+deb13u4
-
Introduced through: php@8.2-apache › curl/libcurl4t64@8.14.1-2+deb13u4
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 to a specific HTTP origin
(hostA) with Digest authentication and then changing the origin to a
different one (hostB) for a second transfer, reusing the same handle, makes
libcurl wrongly pass on the Authorization: header field meant for hostA,
to hostB.
Remediation
There is no fixed version for Debian:13 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4
Detailed paths
-
Introduced through: php@8.2-apache › curl@8.14.1-2+deb13u4
-
Introduced through: php@8.2-apache › curl/libcurl4t64@8.14.1-2+deb13u4
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 reusing a libcurl handle for sequential transfers driven by
environment-variable proxy configuration, libcurl fails to clear the proxy
authentication state between requests. Specifically, if the initial transfer
authenticates against proxyA using Digest auth, a subsequent transfer routed
through proxyB erroneously leaks the Proxy-Authorization: header intended
solely for proxyA.
Remediation
There is no fixed version for Debian:13 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4
Detailed paths
-
Introduced through: php@8.2-apache › curl@8.14.1-2+deb13u4
-
Introduced through: php@8.2-apache › curl/libcurl4t64@8.14.1-2+deb13u4
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
- Vulnerable module: curl
- Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4
Detailed paths
-
Introduced through: php@8.2-apache › curl@8.14.1-2+deb13u4
-
Introduced through: php@8.2-apache › curl/libcurl4t64@8.14.1-2+deb13u4
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
- Vulnerable module: curl
- Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4
Detailed paths
-
Introduced through: php@8.2-apache › curl@8.14.1-2+deb13u4
-
Introduced through: php@8.2-apache › curl/libcurl4t64@8.14.1-2+deb13u4
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
- Vulnerable module: curl
- Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4
Detailed paths
-
Introduced through: php@8.2-apache › curl@8.14.1-2+deb13u4
-
Introduced through: php@8.2-apache › curl/libcurl4t64@8.14.1-2+deb13u4
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
new
- Vulnerable module: curl
- Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4
Detailed paths
-
Introduced through: php@8.2-apache › curl@8.14.1-2+deb13u4
-
Introduced through: php@8.2-apache › curl/libcurl4t64@8.14.1-2+deb13u4
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 flaw in the libcurl SASL negotiation for LDAP authentication allows an incomplete handshake sequence to be misinterpreted as a successful cryptographic verification. An attacker executing a Man-in-the-Middle (MITM) attack can inject a premature or shortcut response that bypasses complete peer validation.
Remediation
There is no fixed version for Debian:13 curl.
References
low severity
new
- Vulnerable module: curl
- Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4
Detailed paths
-
Introduced through: php@8.2-apache › curl@8.14.1-2+deb13u4
-
Introduced through: php@8.2-apache › curl/libcurl4t64@8.14.1-2+deb13u4
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 flaw in libcurl's handling of HTTP/2 Server Push streams, when the parent handle is set to share connections with other handles, can lead to use-after-free in the cleanup process.
Remediation
There is no fixed version for Debian:13 curl.
References
low severity
new
- Vulnerable module: curl
- Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4
Detailed paths
-
Introduced through: php@8.2-apache › curl@8.14.1-2+deb13u4
-
Introduced through: php@8.2-apache › curl/libcurl4t64@8.14.1-2+deb13u4
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 flaw in libcurl makes it wrongly reuse an HTTP connection setup for a given hostname using Negotiate authentication, when the initial request is done using empty credentials. This can make user B's request get sent over user A's previously authenticated connection.
Remediation
There is no fixed version for Debian:13 curl.
References
low severity
new
- Vulnerable module: curl
- Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4
Detailed paths
-
Introduced through: php@8.2-apache › curl@8.14.1-2+deb13u4
-
Introduced through: php@8.2-apache › curl/libcurl4t64@8.14.1-2+deb13u4
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 performing transfers via libcurl’s multi interface, pooled TLS connections can outlive their originating easy handles. In OpenSSL 3 provider configurations, libcurl attaches an allocated library context to the easy handle's state and passes it to OpenSSL without acquiring an ownership reference; destroying the easy handle prematurely frees this context while the active connection retains a dangling pointer, leading to a heap-use-after-free upon subsequent I/O or post-handshake operations.
Remediation
There is no fixed version for Debian:13 curl.
References
low severity
new
- Vulnerable module: curl
- Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4
Detailed paths
-
Introduced through: php@8.2-apache › curl@8.14.1-2+deb13u4
-
Introduced through: php@8.2-apache › curl/libcurl4t64@8.14.1-2+deb13u4
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 CURLOPT_PINNEDPUBLICKEY is configured alongside options that disable
standard peer verification (CURLOPT_SSL_VERIFYPEER = 0 and
CURLOPT_SSL_VERIFYHOST = 0), libcurl fails to enforce public key pinning on
connections established without a presented server certificate. Bypassing the
pinning check under these disabled-verification conditions allows
unauthenticated connections to succeed when they should be rejected.
Remediation
There is no fixed version for Debian:13 curl.
References
low severity
new
- Vulnerable module: curl
- Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4
Detailed paths
-
Introduced through: php@8.2-apache › curl@8.14.1-2+deb13u4
-
Introduced through: php@8.2-apache › curl/libcurl4t64@8.14.1-2+deb13u4
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 Set-Cookie: header using tab (horizontal tab, ASCII code 9) instead of
space (ascii code 32) immediately before the Secure attribute causes curl to
store the cookie without its Secure flag. The cookie might then wrongfully be
sent over plaintext HTTP on subsequent requests to the same host.
Remediation
There is no fixed version for Debian:13 curl.
References
low severity
new
- Vulnerable module: curl
- Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4
Detailed paths
-
Introduced through: php@8.2-apache › curl@8.14.1-2+deb13u4
-
Introduced through: php@8.2-apache › curl/libcurl4t64@8.14.1-2+deb13u4
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.
With the wolfSSL backend, when CA caching is enabled and an
CURLOPT_SSL_CTX_FUNCTION callback replaces the trust store, libcurl can
silently reinstall the cached store after the callback returns. A certificate
trusted by the cached store but rejected by the callback-selected store is
then incorrectly accepted.
Remediation
There is no fixed version for Debian:13 curl.
References
low severity
new
- Vulnerable module: curl
- Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4
Detailed paths
-
Introduced through: php@8.2-apache › curl@8.14.1-2+deb13u4
-
Introduced through: php@8.2-apache › curl/libcurl4t64@8.14.1-2+deb13u4
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 libpsl support is enabled, libcurl fails to enforce the Public Suffix
List boundary check when processing a Set-Cookie header where the Domain
attribute explicitly matches an origin host that is itself a public suffix
(e.g., Domain=co.uk set by co.uk).
Instead of coercing it into a strict host-only cookie, libcurl saves the
cookie with wildcard domain scope (.co.uk). Consequently, the cookie is
inappropriately included in subsequent outbound requests or HTTP redirects to
arbitrary sibling subdomains under the same public suffix (e.g.,
attacker.co.uk).
Remediation
There is no fixed version for Debian:13 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4
Detailed paths
-
Introduced through: php@8.2-apache › curl@8.14.1-2+deb13u4
-
Introduced through: php@8.2-apache › curl/libcurl4t64@8.14.1-2+deb13u4
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 Negotiate-authenticated ones, even when they are set to use different "services".
libcurl features a pool of recent connections so that subsequent requests can reuse an existing connection to avoid overhead.
When reusing a connection a range of criteria must be met. Due to a logical error in the code, a request that was issued by an application could wrongfully reuse an existing connection to the same server that was authenticated using different services.
Remediation
There is no fixed version for Debian:13 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4
Detailed paths
-
Introduced through: php@8.2-apache › curl@8.14.1-2+deb13u4
-
Introduced through: php@8.2-apache › curl/libcurl4t64@8.14.1-2+deb13u4
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 flaw in curl’s cookie parsing logic allows a malicious HTTP server to set "super cookies" that bypass the Public Suffix List check. This enables an attacker-controlled origin to inject cookies that curl subsequently scopes and transmits to unrelated third-party domains.
Remediation
There is no fixed version for Debian:13 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4
Detailed paths
-
Introduced through: php@8.2-apache › curl@8.14.1-2+deb13u4
-
Introduced through: php@8.2-apache › curl/libcurl4t64@8.14.1-2+deb13u4
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 would reuse a previously created connection even when some mTLS config related option had been changed that should have prohibited reuse.
libcurl keeps previously used connections in a connection pool for subsequent transfers to reuse if one of them matches the setup. However, some TLS settings related to client certificates were left out from the configuration match checks, making them match too easily. In particular options related to the private key.
Remediation
There is no fixed version for Debian:13 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4
Detailed paths
-
Introduced through: php@8.2-apache › curl@8.14.1-2+deb13u4
-
Introduced through: php@8.2-apache › curl/libcurl4t64@8.14.1-2+deb13u4
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.
In this scenario, libcurl first uses a proper HTTP/3 server for the initial transfers, and when it makes a second transfer to the same site it has been replaced by the attacker's impostor machine - without a valid certificate.
When libcurl returns to the hostname the second time with a cached SSL session
(CURLOPT_SSL_SESSIONID_CACHE is not disabled) and early data enabled (the
CURLSSLOPT_EARLYDATA bit is set in CURLOPT_SSL_OPTIONS), libcurl might
send off the second request's bytes on that new connection before enforcing
the certificate verification failure. Potentially leaking sensitive
information.
Remediation
There is no fixed version for Debian:13 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4
Detailed paths
-
Introduced through: php@8.2-apache › curl@8.14.1-2+deb13u4
-
Introduced through: php@8.2-apache › curl/libcurl4t64@8.14.1-2+deb13u4
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 a libcurl-based application performs transfers via SCP:// or SFTP://
and utilizes the CURLOPT_SSH_KEYFUNCTION callback, it may silently accept an
untrusted server. This vulnerability occurs when a server presents a host key
type that does not match the specific key type already recorded for that host
in the known_hosts file. Instead of rejecting the mismatch, the callback
mechanism fails to properly enforce the restriction, allowing the connection
to succeed without warning and risking a potential man-in-the-middle attack.
Remediation
There is no fixed version for Debian:13 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4
Detailed paths
-
Introduced through: php@8.2-apache › curl@8.14.1-2+deb13u4
-
Introduced through: php@8.2-apache › curl/libcurl4t64@8.14.1-2+deb13u4
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 a user invokes curl using a schemeless URL combined with
--proto-default sftp (or scp), a disconnect occurs between the tool layer
and libcurl. The tool layer incorrectly infers the URL scheme, which
erroneously bypasses the initialization of critical SSH security options like
CURLOPT_SSH_HOST_PUBLIC_KEY_SHA256 and CURLOPT_SSH_KNOWNHOSTS. Conversely, the
libcurl runtime successfully honors CURLOPT_DEFAULT_PROTOCOL and establishes
the connection via SFTP/SCP as specified. Because the tool layer skipped the
security configuration, these SSH host verification options are silently
omitted, causing curl to connect to an unverified SSH remote host without
throwing an error.
Remediation
There is no fixed version for Debian:13 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4
Detailed paths
-
Introduced through: php@8.2-apache › curl@8.14.1-2+deb13u4
-
Introduced through: php@8.2-apache › curl/libcurl4t64@8.14.1-2+deb13u4
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 new transfer that uses STARTTLS to upgrade the connection might reuse an existing live connection even though the TLS configuration mismatches so it should not.
Remediation
There is no fixed version for Debian:13 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4
Detailed paths
-
Introduced through: php@8.2-apache › curl@8.14.1-2+deb13u4
-
Introduced through: php@8.2-apache › curl/libcurl4t64@8.14.1-2+deb13u4
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 asking curl to use a .netrc file to find credentials and at the same
time specifying a URL with a username (without a password), like
https://user@example.com/, curl could wrongly get and use the password for
another user set in the .netrc file for that host if such a one exists and
there is no match for the specified user.
Remediation
There is no fixed version for Debian:13 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4
Detailed paths
-
Introduced through: php@8.2-apache › curl@8.14.1-2+deb13u4
-
Introduced through: php@8.2-apache › curl/libcurl4t64@8.14.1-2+deb13u4
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 had a flaw that when instructed to clear proxy authentication credentials which made it not do so, leaving the old credentials around to get used for subsequent transfers that should not know nor use them.
Remediation
There is no fixed version for Debian:13 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4
Detailed paths
-
Introduced through: php@8.2-apache › curl@8.14.1-2+deb13u4
-
Introduced through: php@8.2-apache › curl/libcurl4t64@8.14.1-2+deb13u4
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 use-after-free vulnerability exists in libcurl when an application
configures an HTTP/2 stream-dependency tree via CURLOPT_STREAM_DEPENDS or
CURLOPT_STREAM_DEPENDS_E, subsequently invokes curl_easy_reset(), and
finally terminates the handle with curl_easy_cleanup(). During this final
cleanup phase, libcurl attempts to access and modify an internal structure
that was already freed during the reset operation.
Remediation
There is no fixed version for Debian:13 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4
Detailed paths
-
Introduced through: php@8.2-apache › curl@8.14.1-2+deb13u4
-
Introduced through: php@8.2-apache › curl/libcurl4t64@8.14.1-2+deb13u4
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.
Calling curl_easy_pause() within the event-based CURLMOPT_SOCKETFUNCTION
callback triggers a use-after-free vulnerability, where libcurl attempts to
store a flag using a dangling struct pointer immediately after that pointer's
memory has been freed.
Remediation
There is no fixed version for Debian:13 curl.
References
low severity
- Vulnerable module: diffutils
- Introduced through: diffutils@1:3.10-4
Detailed paths
-
Introduced through: php@8.2-apache › diffutils@1:3.10-4
NVD Description
Note: Versions mentioned in the description apply only to the upstream diffutils package and not the diffutils package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
diff3 tool from GNU diffutils is vulnerable to a heap‑based buffer overflow due to multiple signed integer overflows in line‑mapping calculations. Incorrect arithmetic in mapping line ranges can result in corrupted values being used for memory allocation and loop bounds. When processing crafted diff output, these overflows may cause the application to allocate insufficient memory and subsequently perform out‑of‑bounds writes during internal processing. An attacker who can control the output of the diff program used by diff3 (e.g. via --diff-program pointing to a malicious script) can trigger out-of-bounds writes, resulting in a crash and potentially remote code execution depending on the environment.
This issue has been fixed in commit 9ff04d5b84743e331e80b589335a52c5480d1815
NOTE: The project maintainers claim that this is not a security issue. They state that the worst outcome this issue can cause is a crash of diff and that it cannot be used to escalate privileges.
Remediation
There is no fixed version for Debian:13 diffutils.
References
- https://security-tracker.debian.org/tracker/CVE-2026-53910
- https://cert.pl/en/posts/2026/07/CVE-2026-53910
- https://cgit.git.savannah.gnu.org/cgit/diffutils.git/commit/?id=73ed7ce85cc78effb94daf028c9af6b4e5252e50
- https://cgit.git.savannah.gnu.org/cgit/diffutils.git/commit/?id=9ff04d5b84743e331e80b589335a52c5480d1815
- https://git.savannah.gnu.org/cgit/diffutils.git/
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.8.2-1~deb13u1
- Fixed in: 2.8.3-1~deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › expat/libexpat1@2.8.2-1~deb13u1
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.3 has an out-of-bounds read and resultant infinite loop because low surrogates are treated the same as high surrogates during Unicode processing in the *_toUtf16 functions.
Remediation
Upgrade Debian:13 expat to version 2.8.3-1~deb13u1 or higher.
References
low severity
new
- 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: php@8.2-apache › glibc/libc-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc-dev-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc6@2.41-12+deb13u3
-
Introduced through: php@8.2-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.
Passing an effectively empty string to the ,ccs= syntax extension of the mode argument in the fopen function in the GNU C Library version 2.45 or earlier may result in a heap buffer overflow when the mode string input to the function is attacker controlled.
This usage pattern is not seen in applications in common GNU/Linux distributions and applications that process user-supplied values for ccs should not pass them through without validation.
Remediation
There is no fixed version for Debian:13 glibc.
References
low severity
new
- 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: php@8.2-apache › glibc/libc-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc-dev-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc6@2.41-12+deb13u3
-
Introduced through: php@8.2-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 strfmon and strfmon_l in the GNU C Library version 2.38 to 2.44 can write past the end of the caller-supplied output buffer when a conversion uses right-justified width padding.
Exploitation requires an application code path that calls strfmon or strfmon_l with right-justified width padding into a destination buffer that is large enough for the padding to succeed but too small for the internal memmove call. The field width or format may be attacker-influenced or a fixed susceptible pattern in the caller.
At the time of publication, no network-facing application impact is known.
Remediation
There is no fixed version for Debian:13 glibc.
References
low severity
new
- 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: php@8.2-apache › glibc/libc-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc-dev-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc6@2.41-12+deb13u3
-
Introduced through: php@8.2-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 tdelete on a sufficiently deep tree in the GNU C Library version 2.1 to 2.44 may write one pointer past the end of an alloca-allocated array on the stack, which may crash the application.
The tdelete implementation keeps an explicit stack of parent nodes for rebalancing, which is grown as needed while descending the tree. Two rebalancing branches push an additional entry without checking the capacity, and write past the array when the stack is exactly full. Triggering this requires a node at a depth of exactly 40 (or 40 plus a multiple of 20), which implies a tree with at least a million nodes, so an attacker must drive a large number of insertions and deletions through an application that uses tsearch and tdelete. The written value is a pointer into a tree node and is not directly attacker controlled. No affected application in common distributions has been identified.
Remediation
There is no fixed version for Debian:13 glibc.
References
low severity
- 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: php@8.2-apache › glibc/libc-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc-dev-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc6@2.41-12+deb13u3
-
Introduced through: php@8.2-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
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.41-12+deb13u3, glibc/libc-dev-bin@2.41-12+deb13u3 and others
- Fixed in: 2.41-12+deb13u4
Detailed paths
-
Introduced through: php@8.2-apache › glibc/libc-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc-dev-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc6@2.41-12+deb13u3
-
Introduced through: php@8.2-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
Upgrade Debian:13 glibc to version 2.41-12+deb13u4 or higher.
References
low severity
- 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: php@8.2-apache › glibc/libc-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc-dev-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc6@2.41-12+deb13u3
-
Introduced through: php@8.2-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
- 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: php@8.2-apache › glibc/libc-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc-dev-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc6@2.41-12+deb13u3
-
Introduced through: php@8.2-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 wordexp with WRDE_APPEND in the GNU C Library version 2.0 to version 2.43 can cause the interface to return invalid memory in the we_wordv member, which on subsequent calls to wordfree may abort the process.
Remediation
There is no fixed version for Debian:13 glibc.
References
low severity
- 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: php@8.2-apache › glibc/libc-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc-dev-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc6@2.41-12+deb13u3
-
Introduced through: php@8.2-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.
When expanding paths that begin with a tilde (~) followed by a username, the internal parse_tilde function extracts the username to determine the user's home directory. The implementation allocates memory for this username directly on the stack using the strndupa macro. Because the size of this allocation was determined by the length of the user-supplied input without any bounds checks, passing an excessively long username e.g. thousands of characters, forces the thread to exhaust its stack space. Thus if an application passes untrusted, attacker-controlled input to the wordexp function, an attacker can trigger a stack clash.
Remediation
There is no fixed version for Debian:13 glibc.
References
low severity
new
- 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: php@8.2-apache › glibc/libc-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc-dev-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc6@2.41-12+deb13u3
-
Introduced through: php@8.2-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.
Converting crafted SHIFT_JISX0213 input to UCS-4 or the internal wide character encoding, for example with iconv, in the GNU C Library version 2.3 to 2.44 may result in the converter making no progress, causing the calling application to hang.
Some SHIFT_JISX0213 sequences decode to two code points. If the output buffer has room for only the first one, the converter stores the second in the conversion state and returns E2BIG, but it never clears that pending character after emitting it on the next call. The converter then keeps emitting the pending character without consuming further input, so an application that retries the conversion loops forever. The input must be attacker controlled and the application must convert it with an output buffer small enough to split the two code points. Only the SHIFT_JISX0213 character set is affected, which is not commonly used. The related defect in the EUC_JISX0213 converter is tracked separately as CVE-2026-80489.
Remediation
There is no fixed version for Debian:13 glibc.
References
low severity
new
- 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: php@8.2-apache › glibc/libc-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc-dev-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc6@2.41-12+deb13u3
-
Introduced through: php@8.2-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.
Converting crafted EUC_JISX0213 input to UCS-4 or the internal wide character encoding, for example with iconv, in the GNU C Library version 2.3 to 2.44 may result in the converter making no progress, causing the calling application to hang.
Some EUC_JISX0213 sequences decode to two code points. If the output buffer has room for only the first one, the converter stores the second in the conversion state and returns E2BIG, but it never clears that pending character after emitting it on the next call. The converter then keeps emitting the pending character without consuming further input, so an application that retries the conversion loops forever. The input must be attacker controlled and the application must convert it with an output buffer small enough to split the two code points. Only the EUC_JISX0213 character set is affected, which is not commonly used. The related defect in SHIFT_JISX0213 converter is tracked separately as CVE-2026-77117.
Remediation
There is no fixed version for Debian:13 glibc.
References
low severity
new
- 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: php@8.2-apache › glibc/libc-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc-dev-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc6@2.41-12+deb13u3
-
Introduced through: php@8.2-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.
Initializing the DNS stub resolver from an /etc/resolv.conf file, or a LOCALDOMAIN environment variable, whose search list contains a domain of roughly 200 characters or more in the GNU C Library version 2.26 to 2.44 results in an assertion failure which aborts the process.
The resolver truncates the search list when copying it into the fixed-size _res.defdname buffer, then asserts that the copy is consistent with the full configuration. The consistency check compared against the wrong size and did not handle a first entry that does not fit, so a correctly truncated list failed the assertion. Any process that resolves names through the library is affected, including long-running processes that reload /etc/resolv.conf on the next query after it changes. Search domains are commonly written to /etc/resolv.conf from data received over DHCP or from a VPN server, so an attacker on the local network may be able to trigger this without privileges on the target system, subject to validation by the network configuration software.
Remediation
There is no fixed version for Debian:13 glibc.
References
- https://security-tracker.debian.org/tracker/CVE-2026-8674
- https://joshua.hu/fuzzing-glibc-libresolv
- https://sourceware.org/bugzilla/show_bug.cgi?id=31026
- https://sourceware.org/git/?p=glibc.git;a=blob_plain;f=advisories/GLIBC-SA-2026-0021
- https://sourceware.org/git/?p=glibc.git;a=commit;h=506ea57086bfb9ce3daff1c14246a1cb532aba0a
- http://www.openwall.com/lists/oss-security/2026/09/17/4
low severity
new
- 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: php@8.2-apache › glibc/libc-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc-dev-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc6@2.41-12+deb13u3
-
Introduced through: php@8.2-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 nscd service in the GNU C Library 2.3.4 onwards may crash due to a stack overflow when a malicious DNS server returns too large a response for a DNS query, resulting in degraded DNS resolution for the system.
Exploitation of this bug needs a system that has nscd enabled and using an untrusted DNS server for name resolution, with the compromised DNS server being capable of processing records large enough to result in a stack overflow in an nscd thread stack. During experimentation, bind 9 was unable to handle large records, but that could change in future or with a different name server. In typical installations, nscd is executed in an isolated context as its own user without a shell, due to which any compromise of that service is isolated.
There is a remote possibility of nscd cache corruption if an attacker manages to get the stack pointer into a desired point in the heap, potentially resulting in other caches in nscd being overwritten with corrupt data through the stack overflow, until the buggy code path eventually results in a crash.
Finally, a crash in nscd may result in performance degradation when resolving names, but it does not result in a denial of service.
Remediation
There is no fixed version for Debian:13 glibc.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.41-12+deb13u3, glibc/libc-dev-bin@2.41-12+deb13u3 and others
- Fixed in: 2.41-12+deb13u4
Detailed paths
-
Introduced through: php@8.2-apache › glibc/libc-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc-dev-bin@2.41-12+deb13u3
-
Introduced through: php@8.2-apache › glibc/libc6@2.41-12+deb13u3
-
Introduced through: php@8.2-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
Upgrade Debian:13 glibc to version 2.41-12+deb13u4 or higher.
References
low severity
- Vulnerable module: gzip
- Introduced through: gzip@1.13-1
- Fixed in: 1.13-1+deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › gzip@1.13-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream gzip package and not the gzip package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
GNU gzip contains a vulnerability in the gzexe utility related to insecure temporary file handling. When the mktemp utility is not available in the user’s PATH, gzexe falls back to constructing a temporary file path based solely on the process ID (PID). This predictable filename is created without exclusive access or existence checks. A local attacker can pre‑create the predicted temporary file path as a symbolic link pointing to an arbitrary file writable by the victim. When gzexe runs, it follows the symlink and overwrites the target file, resulting in a time‑of‑check to time‑of‑use (TOCTOU) condition that allows arbitrary file overwrite.
This issue has been fixed in the commit 4e6f8b24ab823146ab8776f0b7fe486ab34d4269
Remediation
Upgrade Debian:13 gzip to version 1.13-1+deb13u1 or higher.
References
low severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.21.3-5+deb13u1, krb5/libk5crypto3@1.21.3-5+deb13u1 and others
Detailed paths
-
Introduced through: php@8.2-apache › krb5/libgssapi-krb5-2@1.21.3-5+deb13u1
-
Introduced through: php@8.2-apache › krb5/libk5crypto3@1.21.3-5+deb13u1
-
Introduced through: php@8.2-apache › krb5/libkrb5-3@1.21.3-5+deb13u1
-
Introduced through: php@8.2-apache › krb5/libkrb5support0@1.21.3-5+deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
Kerberos 5 (aka krb5) 1.21.2 contains a memory leak vulnerability in /krb5/src/lib/gssapi/krb5/k5sealv3.c.
Remediation
There is no fixed version for Debian:13 krb5.
References
low severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.21.3-5+deb13u1, krb5/libk5crypto3@1.21.3-5+deb13u1 and others
Detailed paths
-
Introduced through: php@8.2-apache › krb5/libgssapi-krb5-2@1.21.3-5+deb13u1
-
Introduced through: php@8.2-apache › krb5/libk5crypto3@1.21.3-5+deb13u1
-
Introduced through: php@8.2-apache › krb5/libkrb5-3@1.21.3-5+deb13u1
-
Introduced through: php@8.2-apache › krb5/libkrb5support0@1.21.3-5+deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
Kerberos 5 (aka krb5) 1.21.2 contains a memory leak in /krb5/src/lib/rpc/pmap_rmt.c.
Remediation
There is no fixed version for Debian:13 krb5.
References
low severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3
Detailed paths
-
Introduced through: php@8.2-apache › libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3
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.
Use After Free in libxml2's xmlParseInternalSubset from GNOME libxml2 version 2.9.11 to 2.11.0 allows a remote attacker to cause a denial-of-service via maliciously crafted XML input with improper entity resolution handling.
Remediation
There is no fixed version for Debian:13 libxml2.
References
low severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3
Detailed paths
-
Introduced through: php@8.2-apache › libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3
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.
libxml2 is vulnerable to multiple stack-based buffer overflows in the xmlcatalog utility when running in --shell mode. The usershell() function processes user input using fixed-size stack buffers without proper bounds checking. By supplying an overly long input line, an attacker can overflow internal buffers (command, arg, and argv) during input parsing. This results in memory corruption within the stack frame. Successful exploitation may cause a crash or potentially allow arbitrary code execution in the context of the xmlcatalog process.
This issue has been fixed in the commit c2e233fc.
NOTE: The maintainers of this project did not agree that this issue is a vulnerability and considered it a bug.
Remediation
There is no fixed version for Debian:13 libxml2.
References
low severity
- Vulnerable module: openldap/libldap2
- Introduced through: openldap/libldap2@2.6.10+dfsg-1
Detailed paths
-
Introduced through: php@8.2-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
- https://security-tracker.debian.org/tracker/CVE-2026-22185
- https://seclists.org/fulldisclosure/2026/Jan/5
- https://seclists.org/fulldisclosure/2026/Jan/8
- https://www.openldap.org/
- https://www.vulncheck.com/advisories/openldap-lmdb-mdb-load-heap-buffer-underflow-in-readline
- https://bugs.openldap.org/show_bug.cgi?id=10421
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.5.6-1~deb13u2, openssl/libssl3t64@3.5.6-1~deb13u2 and others
- Fixed in: 3.5.7-1~deb13u2
Detailed paths
-
Introduced through: php@8.2-apache › openssl@3.5.6-1~deb13u2
-
Introduced through: php@8.2-apache › openssl/libssl3t64@3.5.6-1~deb13u2
-
Introduced through: php@8.2-apache › openssl/openssl-provider-legacy@3.5.6-1~deb13u2
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 OpenSSL QUIC server (Listener SSL object) processes valid QUIC Initial packets for unknown destination connection IDs, it can allocate and queue new incoming channels without enforcing any limit.
Impact summary: A remote peer that can make many Initial packets reach the server listener faster than the application accepts connections, can cause the memory allocated to store the per-channel state to grow without any limits, potentially making the QUIC listener unavailable and causing Denial of Service.
CWE: CWE-770: Allocation of Resources Without Limits or Throttling
Description: The function that handles inbound QUIC packets uses Connection-Id from the packet header to find an existing connection (QUIC channel). If no existing connection is found and the packet type is INITIAL, the function treats the packet as a new connection. It allocates a new channel object and inserts it into a queue where it waits to be accepted by the local application with SSL_accept(3ossl). The memory occupied by these initial channel objects may grow without bounds if the application is not able to call SSL_accept() frequently enough to serve these inbound connection requests.
The issue is present since OpenSSL 3.5 when the QUIC server implementation was added.
The fix introduces a limit for pending connections. The default limit is set to 256 pending connections (waiting to be accepted by the local application). Applications may change the default by calling SSL_set_value_uint(3ossl).
FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.
Remediation
Upgrade Debian:13 openssl to version 3.5.7-1~deb13u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-14456
- https://github.com/openssl/openssl/commit/08e7756c3900bcfd77a720e7b74e27d6e4ed01a9
- https://github.com/openssl/openssl/commit/4084152e040329ca0194c4c1750b9b46d00a5b6b
- https://github.com/openssl/openssl/commit/f2f1465f2d2e5c61dfeac4d20fd093797d821139
- https://openssl-library.org/news/secadv/20260813.txt
- http://www.openwall.com/lists/oss-security/2026/08/13/4
low severity
new
- Vulnerable module: openssl
- Introduced through: openssl@3.5.6-1~deb13u2, openssl/libssl3t64@3.5.6-1~deb13u2 and others
- Fixed in: 3.5.7-1~deb13u2
Detailed paths
-
Introduced through: php@8.2-apache › openssl@3.5.6-1~deb13u2
-
Introduced through: php@8.2-apache › openssl/libssl3t64@3.5.6-1~deb13u2
-
Introduced through: php@8.2-apache › openssl/openssl-provider-legacy@3.5.6-1~deb13u2
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: In a server or client configuration with RFC7250 Raw Public Keys (RPKs) enabled, and only the private key (with no associated certificate) configured locally, a NULL pointer dereference may occur when the remote peer solicits raw public keys and also sends the typically omitted "signature_algorithms_cert" TLS extension.
Impact summary: The impact is limited to a possible Denial of Service as a result of an application abort, no data disclosure or remote command execution are possible.
CWE: CWE-476: NULL Pointer Dereference
Description: While a passing comment in sample code in the documentation suggests that key-only RPK configurations are supported, the best-practice RPK configuration is to always configure a corresponding certificate (possibly self-signed or signed by any convenient CA).
When the private key is configured along with a matching certificate, the "signature_algorithms_cert" extension is handled reliably even without the fix, and peer clients or servers that don't support raw public keys may be able to complete a TLS connection by pinning or verifying the corresponding certificate or its public key.
Deployments that prefer to configure just a private key with no certificate need to upgrade to an updated release as noted below.
FIPS impact: no
No FIPS modules are affected by this issue, as the SSL protocol implementation is outside the OpenSSL FIPS module boundary.
Remediation
Upgrade Debian:13 openssl to version 3.5.7-1~deb13u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-14457
- https://github.com/openssl/openssl/commit/1e8c398db67404babd3e5af999bb6bd86f720c76
- https://github.com/openssl/openssl/commit/581aaa0f0a35d214740f0fe1f5283ec41f1212e1
- https://github.com/openssl/openssl/commit/d0af20478688a6aa2f59d61caa3f82136b181d7f
- https://github.com/openssl/openssl/commit/dad836b071da6579510c968615848ba03cac593b
- https://openssl-library.org/news/secadv/20260825.txt
low severity
new
- Vulnerable module: openssl
- Introduced through: openssl@3.5.6-1~deb13u2, openssl/libssl3t64@3.5.6-1~deb13u2 and others
- Fixed in: 3.5.7-1~deb13u2
Detailed paths
-
Introduced through: php@8.2-apache › openssl@3.5.6-1~deb13u2
-
Introduced through: php@8.2-apache › openssl/libssl3t64@3.5.6-1~deb13u2
-
Introduced through: php@8.2-apache › openssl/openssl-provider-legacy@3.5.6-1~deb13u2
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: QUIC server may double free QRX (QUIC record layer RX) object when channel creation fails for initial packet.
Impact summary: Double free leads to heap corruption, which typically results in termination of QUIC server process, leading to Denial of Service. There is so far no evidence that this double free is exploitable for remote code execution, thus it is considered highly improbable.
CWE: CWE-415: Double Free
Description: In order to validate initial packet, OpenSSL QUIC stack default packet handler (port_default_packet_handler()) creates a so-called QRX object. If the initial packet validates successfully with QRX object, the default packet handler proceeds to channel (connection object) creation. The QRX object used for packet validation is passed to port_bind_channel(), so it becomes part of the newly created connection. If port_bind_channel() fails, then it also frees the QRX object. Once port_bind_channel() returns, the port_default_packet_handler() detects the failure and proceeds to the error branch, where the same QRX object is freed for the second time.
The failure in port_bind_channel() function can be induced with a relatively low effort by a malformed (non RFC 9000 compliant) INITIAL packet. If the packet carries DCID (destination connection ID) which is shorter than 8 bytes, then port_bind_channel() jumps to the error path after ossl_quic_lcidm_enrol_odcid() detects that the DCID has invalid length.
FIPS impact: no The FIPS module is not affected, as the QUIC implementation is outside of the OpenSSL FIPS module boundary.
Remediation
Upgrade Debian:13 openssl to version 3.5.7-1~deb13u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-18798
- https://github.com/openssl/openssl/commit/70cebd74d3592f5272945501b58a60374c4e13af
- https://github.com/openssl/openssl/commit/967582d5037f01a26b6d19beae19af62a1b15c3c
- https://github.com/openssl/openssl/commit/a14a1deac403522fbeafabcb198503cf6caa7dc4
- https://openssl-library.org/news/secadv/20260825.txt
low severity
new
- Vulnerable module: openssl
- Introduced through: openssl@3.5.6-1~deb13u2, openssl/libssl3t64@3.5.6-1~deb13u2 and others
- Fixed in: 3.5.7-1~deb13u2
Detailed paths
-
Introduced through: php@8.2-apache › openssl@3.5.6-1~deb13u2
-
Introduced through: php@8.2-apache › openssl/libssl3t64@3.5.6-1~deb13u2
-
Introduced through: php@8.2-apache › openssl/openssl-provider-legacy@3.5.6-1~deb13u2
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 DTLS record for a future epoch while a handshake is in progress causes OpenSSL to buffer far more memory than the record itself requires.
Impact summary: A peer can use a small amount of network traffic to make an OpenSSL DTLS endpoint retain a disproportionately large amount of memory, which may lead to a Denial of Service.
CWE: CWE-405: Asymmetric Resource Consumption (Amplification)
Description: While a DTLS handshake is in progress, a peer may legitimately have already moved on to the next epoch (for example, having sent its ChangeCipherSpec and Finished messages) before the local endpoint has processed the same transition, typically because of reordering on the underlying UDP transport. OpenSSL buffers such early records so that they can be processed once the local endpoint catches up.
Buffering a record currently retains the entire read buffer it arrived in, which is sized to hold the largest possible DTLS record (around 16 kilobytes), rather than just the bytes that make up the record itself. Up to 100 such records may be buffered per connection. As a result, a peer that sends a stream of small forged records claiming to belong to the next epoch can cause an OpenSSL DTLS endpoint to retain around 1.7 megabytes of memory, despite sending only a small fraction of that amount of data over the network.
An attacker therefore gains a memory amplification factor of around 1200, and can multiply the effect across as many associations as it is able to open, making this a remote memory exhaustion Denial of Service risk for DTLS servers. Since the memory retained per connection remains bounded, and any limit an application already places on the number of concurrent associations also bounds the total exposure, this issue has been assessed as Low severity.
FIPS impact: no
No FIPS modules are affected by this issue as the affected code is outside the OpenSSL FIPS module boundary.
OpenSSL 4.0, 3.6, 3.5, 3.4, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.
OpenSSL 4.0 users should upgrade to OpenSSL 4.0.2. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.4. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.8. OpenSSL 3.4 users should upgrade to OpenSSL 3.4.7. OpenSSL 3.0 users should upgrade to OpenSSL 3.0.22.
Premium support customers only: OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1zi OpenSSL 1.0.2 users should upgrade to OpenSSL 1.0.2zr
This issue was reported on 18 May 2026 by Amazon Web Services. The fix has been developed by Matt Caswell.
-- cut (non-publishing metadata for internal use) -- Reported by: Amazon Web Services Fixed by: Matt Caswell
Remediation
Upgrade Debian:13 openssl to version 3.5.7-1~deb13u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-54874
- https://github.com/openssl/openssl/commit/4808b5d64176451f3d93d87d0ac9c81a9b13fb23
- https://github.com/openssl/openssl/commit/7110cb2f75806d0bf809eb2f90790d477900be40
- https://github.com/openssl/openssl/commit/a0c8ec557d9cac078f032d76cdf684fe743eb382
- https://github.com/openssl/openssl/commit/cc0c6710917cd5eec001b297355d2ba723505107
- https://github.com/openssl/openssl/commit/f52ffc11b90737ac89083909618dc2e1f42c561c
- https://openssl-library.org/news/secadv/20260825.txt
low severity
new
- Vulnerable module: openssl
- Introduced through: openssl@3.5.6-1~deb13u2, openssl/libssl3t64@3.5.6-1~deb13u2 and others
- Fixed in: 3.5.7-1~deb13u2
Detailed paths
-
Introduced through: php@8.2-apache › openssl@3.5.6-1~deb13u2
-
Introduced through: php@8.2-apache › openssl/libssl3t64@3.5.6-1~deb13u2
-
Introduced through: php@8.2-apache › openssl/openssl-provider-legacy@3.5.6-1~deb13u2
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: OpenSSL CMS decryption sizes the key-unwrap output buffer based on querying the unwrapped key size, but the AES-WRAP-PAD unwrap primitive can write and cleanse more bytes than that query reports, causing an 8-byte out-of-bounds heap write.
Impact summary: An attacker who supplies a crafted CMS message can trigger a deterministic 8-byte out-of-bounds heap write when the victim decrypts it with CMS_decrypt(), corrupting the heap and typically resulting in a Denial of Service.
CWE: CWE-787: Out-of-bounds Write
Description: The key-wrap OID is potentially attacker-controlled on the wire. CMS unwrapping allows both id-aesNNN-wrap-pad and id-aesNNN-wrap ciphers. An attacker can take a legitimate message and change a single OID byte to select the padded variant while leaving the message otherwise valid. Since the unwrap key is derived from the recipient's private operation (ECDH key agreement or ML-KEM decapsulation), the RFC 5649 integrity check cannot pass, and the decryption fails with integrity failure.
The write is a fixed-size (8-byte), fixed-value (zero) heap overflow immediately past the allocation, requires no special configuration, and is reachable from the public CMS_decrypt() function. The consequence is a heap corruption leading to a Denial of Service. The fix in the CMS code sizes the unwrap output buffer for the worst case so a failed unwrap cannot write past the allocation.
FIPS impact: no
As the CMS code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.
Remediation
Upgrade Debian:13 openssl to version 3.5.7-1~deb13u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-63072
- https://github.com/openssl/openssl/commit/2a3dac874c8057c1f0186849bf1ede1ae7b6b756
- https://github.com/openssl/openssl/commit/87784ad619af36b8807c2044b3940006fccc1e42
- https://github.com/openssl/openssl/commit/9530a5fd1aacaeccdced4478ea2340a480613335
- https://github.com/openssl/openssl/commit/9ec2f6d2ae2bcad907cf7ee38584855bafe4979a
- https://github.com/openssl/openssl/commit/a0c8ec557d9cac078f032d76cdf684fe743eb382
- https://openssl-library.org/news/secadv/20260825.txt
low severity
new
- Vulnerable module: openssl
- Introduced through: openssl@3.5.6-1~deb13u2, openssl/libssl3t64@3.5.6-1~deb13u2 and others
- Fixed in: 3.5.7-1~deb13u2
Detailed paths
-
Introduced through: php@8.2-apache › openssl@3.5.6-1~deb13u2
-
Introduced through: php@8.2-apache › openssl/libssl3t64@3.5.6-1~deb13u2
-
Introduced through: php@8.2-apache › openssl/openssl-provider-legacy@3.5.6-1~deb13u2
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: OpenSSL CMP response validation passed an unexpected response
sender distinguished name directly as the format string to ERR_raise_data().
Impact summary: A malicious or intercepted CMP endpoint can crash a CMP client that enforces an expected sender or uses a pinned server certificate whose subject becomes the default expected sender.
CWE: CWE-134 (Use of Externally-Controlled Format String)
Description: When validating a received CMP message, ossl_cmp_msg_check_update() converts the peer-supplied sender distinguished name with X509_NAME_oneline() and passes it directly as the format argument to ERR_raise_data(). Percent characters survive the conversion, so a sender DN such as "CN=%s%n" reaches BIO_vsnprintf() as an attacker-controlled format string with no matching variadic arguments. This path is only reached when the caller configures an expected sender or pins a server certificate, which is the normal configuration for a CMP client validating server responses.
Since the attacker controls the format string but none of the variadic arguments, such specifiers as %s and %n dereference or write through unrelated stack contents and crash the client. The reliable consequence is a denial of service, when the response comes from a malicious or intercepted CMP endpoint. There is no controlled memory write, arbitrary-address read, or reliable path to remote code execution.
FIPS impact: no
No FIPS modules are affected by this issue, as the CMP protocol implementation is outside the OpenSSL FIPS module boundary.
Remediation
Upgrade Debian:13 openssl to version 3.5.7-1~deb13u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-63073
- https://github.com/openssl/openssl/commit/0cc20b322639919aa423e90799d9a57c3b4b76ca
- https://github.com/openssl/openssl/commit/6a0acc072b4d37a7cac1252a29c1ce1f00c5ec29
- https://github.com/openssl/openssl/commit/7eb2e3ec9d1d4f35c8022fccd4b03398b3f33e21
- https://github.com/openssl/openssl/commit/a7e5a6eea8fd3ccca6b6fbba031a5fbf8a3d93b4
- https://openssl-library.org/news/secadv/20260825.txt
low severity
new
- Vulnerable module: openssl
- Introduced through: openssl@3.5.6-1~deb13u2, openssl/libssl3t64@3.5.6-1~deb13u2 and others
- Fixed in: 3.5.7-1~deb13u2
Detailed paths
-
Introduced through: php@8.2-apache › openssl@3.5.6-1~deb13u2
-
Introduced through: php@8.2-apache › openssl/libssl3t64@3.5.6-1~deb13u2
-
Introduced through: php@8.2-apache › openssl/openssl-provider-legacy@3.5.6-1~deb13u2
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 OpenSSL Certificate Management Protocol (CMP) caches additional certificates (extraCerts) sent in a CMP message, but never expunges them (for instance if they are invalid). If a server reuses an OSSL_CMP_CTX frequently, this cache of extraCerts may grow unboundedly, and a malicious client may flood a CMP server with requests driving this growth.
Impact summary: Users utilizing a CMP server that reuses a single OSSL_CMP_CTX for the lifetime of a server process may observe unbounded memory growth in the event a malicious client repeatedly sends requests containing unique extra certificates, which may lead to OOM conditions.
CWE: CWE-770: Allocation of Resources Without Limits or Throttling
Description: If a remote user sends CMP messages to a server with a list of extraCerts and the message is rejected, the extraCerts from the message remains in the server contexts untrusted certificate stack. This exposes servers with long lived ctx objects to Denial of Service attacks in which an attacker sends messages intending to be rejected with a large list of additional certificates repeatedly, forcing the server to store them indefinitely.
The issue was fixed by removing the added extra certs if the message is rejected, using the same method as when the context is configured to not do caching at all.
FIPS impact: no As the CMP code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.
Remediation
Upgrade Debian:13 openssl to version 3.5.7-1~deb13u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-63074
- https://github.com/openssl/openssl/commit/01e567978a55fba18142a230380c31296049fae7
- https://github.com/openssl/openssl/commit/21a5d9658b0c66daace60e10ea18ff32a448de9f
- https://github.com/openssl/openssl/commit/74ae7f6df47a5767c1010b88c47507dfc5b32c46
- https://github.com/openssl/openssl/commit/75360af9650d4e0c82ba0050c5c9912cd79e54af
- https://github.com/openssl/openssl/commit/f636f9ca0fa1bae5b42f9e787f025c96fb09c43a
- https://openssl-library.org/news/secadv/20260825.txt
low severity
new
- Vulnerable module: openssl
- Introduced through: openssl@3.5.6-1~deb13u2, openssl/libssl3t64@3.5.6-1~deb13u2 and others
- Fixed in: 3.5.7-1~deb13u2
Detailed paths
-
Introduced through: php@8.2-apache › openssl@3.5.6-1~deb13u2
-
Introduced through: php@8.2-apache › openssl/libssl3t64@3.5.6-1~deb13u2
-
Introduced through: php@8.2-apache › openssl/openssl-provider-legacy@3.5.6-1~deb13u2
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 OpenSSL processes QUIC traffic from a peer that repeatedly sends ack-eliciting packets while not acknowledging ACK-only responses, the QUIC stack can retain ACK-only packet metadata for the lifetime of the connection.
Impact summary: A remote peer that can complete a QUIC handshake can cause connection-scoped memory growth which may lead to Denial of Service through memory exhaustion, especially with sustained traffic or many concurrent QUIC connections.
CWE: CWE-770: Allocation of Resources Without Limits or Throttling
Description: When the OpenSSL QUIC stack sends an ACK-only packet, there is no requirement by the QUIC protocol that the peer will acknowledge that ACK-only packet (i.e. it is itself not ack-eliciting). However, the OpenSSL implementation stores the metadata about the ACK frames regardless. In and of itself that's ok, but if a malicious peer establishes a connection, and then drives the connection such that ACK-only packets are forced from the OpenSSL implementation peer (i.e., by sending numerous PING frames), and then withholding any subsequent acks for ack-eliciting data, like legitimate data, said malicious peer can force inappropriate memory growth on the OpenSSL peer, potentially leading to a Denial of Service.
The fix is to ensure that we account for the transmission of the ACK-only packet in the packet histories high and low watermark without actually storing the ACK-only packet metadata itself.
FIPS impact: no The OpenSSL FIPS module is not affected as the QUIC code is outside the FIPS module boundary.
Remediation
Upgrade Debian:13 openssl to version 3.5.7-1~deb13u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-63075
- https://github.com/openssl/openssl/commit/7308946576b12e64b8be53bcf0a120354b2b42bc
- https://github.com/openssl/openssl/commit/7c98d79738549df92868e7dd9be4bbf061eed709
- https://github.com/openssl/openssl/commit/bf84721c2548351176e367e6de505792f0118dc6
- https://github.com/openssl/openssl/commit/c902e5f16d6a9e130e96d3ca6d8f64d71652e393
- https://openssl-library.org/news/secadv/20260825.txt
low severity
new
- Vulnerable module: openssl
- Introduced through: openssl@3.5.6-1~deb13u2, openssl/libssl3t64@3.5.6-1~deb13u2 and others
- Fixed in: 3.5.7-1~deb13u2
Detailed paths
-
Introduced through: php@8.2-apache › openssl@3.5.6-1~deb13u2
-
Introduced through: php@8.2-apache › openssl/libssl3t64@3.5.6-1~deb13u2
-
Introduced through: php@8.2-apache › openssl/openssl-provider-legacy@3.5.6-1~deb13u2
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: OpenSSL CMP password based protection verification only checks whether the protectionAlg parameter was not NULL and not its ASN.1 type, before treating it as a PBMParameter. A crafted message can contain a parameter of a different type, which is then dereferenced as an invalid pointer.
Impact summary: A remote, unauthenticated attacker can crash an application acting as a CMP server that accepts PBM-protected messages, or a CMP client talking to a malicious or intercepted CMP server, resulting in a Denial of Service.
CWE: CWE-476: NULL Pointer Dereference
Description: When verifying the password-based MAC protection of a CMP message, OpenSSL library reads the protectionAlg algorithm parameter with X509_ALGOR_get0(), which returns both the parameter type and its value pointer. The value is then cast to an ASN1_STRING and treated as the expected PBMParameter after only checking that pointer is not NULL. The parameter type returned by X509_ALGOR_get0() was never consulted.
This happens during protection verification, before any MAC is computed, so no knowledge of the PBM shared secret is required; the only precondition is that PBM verification is reachable. On the server side this is reached from OSSL_CMP_SRV_process_request() for any application that stands up a CMP server accepting PBM-protected messages, and on the client side from CMP response validation against a malicious or on-path (MITM) server. The reliable consequence is a denial of service; there is no memory disclosure, no controlled memory write, and no path to code execution. CMP is a specialized feature that an application must explicitly enable.
FIPS impact: no As the CMP code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.
Remediation
Upgrade Debian:13 openssl to version 3.5.7-1~deb13u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-63076
- https://github.com/openssl/openssl/commit/37882aa2e0256e1072442a8f62f7db45b995c45b
- https://github.com/openssl/openssl/commit/a17cc8d612ecff6d94a9b7ca8b5283ddf5ff570e
- https://github.com/openssl/openssl/commit/a1f348ccb328c3afbd4ba6883f9b7c813c043259
- https://github.com/openssl/openssl/commit/a7af46a92d0ce19a90e669ef56d2576a07924226
- https://github.com/openssl/openssl/commit/cdacfff557389abfa9e4615abded2ec984517d6c
- https://openssl-library.org/news/secadv/20260825.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.5.6-1~deb13u2, openssl/libssl3t64@3.5.6-1~deb13u2 and others
- Fixed in: 3.5.7-1~deb13u2
Detailed paths
-
Introduced through: php@8.2-apache › openssl@3.5.6-1~deb13u2
-
Introduced through: php@8.2-apache › openssl/libssl3t64@3.5.6-1~deb13u2
-
Introduced through: php@8.2-apache › openssl/openssl-provider-legacy@3.5.6-1~deb13u2
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: ChaCha20-Poly1305 and AES-OCB decryption with an empty ciphertext can report success without verifying the supplied authentication tag when the operation is finalized by calling the EVP_Cipher() function.
Impact summary: Applications calling EVP_Cipher() on an empty ciphertext and expecting the call to check the AEAD tag may accept forged messages.
CWE: CWE-354 (Improper Validation of Integrity Check Value)
Description: The EVP_Cipher() API call for AEAD ciphers behaves like a one shot encryption and decryption call. It also verifies the AEAD tag after the decryption operation. However for AES-OCB and ChaCha20-Poly1305 ciphers it skipped the AEAD tag verification when an empty ciphertext was passed to the function. The callers of this function might believe that a successful return indicates a valid AEAD tag for these ciphers, even when that has not truly been validated in this case.
FIPS impact: no The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this CVE as the affected algorithms are not FIPS approved and thus not implemented in the FIPS module.
Remediation
Upgrade Debian:13 openssl to version 3.5.7-1~deb13u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-75803
- https://github.com/openssl/openssl/commit/119ab9555dc62275bbd71f6f49529b1a44feba42
- https://github.com/openssl/openssl/commit/3621257986e27e540bf96a11570929a6e5a9e05b
- https://github.com/openssl/openssl/commit/6c7aa6f8f6449b7fe0137ee8be65fcd239bd7d6a
- https://github.com/openssl/openssl/commit/bdeb0cd994d915342787f117ee75044f0dc36f34
- https://github.com/openssl/openssl/commit/bf95f5f772e9362f87b25cfa2f8cb15d984865b9
- https://openssl-library.org/news/secadv/20260825.txt
low severity
- Vulnerable module: pam/libpam-modules
- Introduced through: pam/libpam-modules@1.7.0-5, pam/libpam-modules-bin@1.7.0-5 and others
Detailed paths
-
Introduced through: php@8.2-apache › pam/libpam-modules@1.7.0-5
-
Introduced through: php@8.2-apache › pam/libpam-modules-bin@1.7.0-5
-
Introduced through: php@8.2-apache › pam/libpam-runtime@1.7.0-5
-
Introduced through: php@8.2-apache › pam/libpam0g@1.7.0-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream pam package and not the pam package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
Linux-PAM through 1.7.2 contains an observable timing discrepancy (CWE-208) in the pam_userdb module's plaintext-password comparison path in modules/pam_userdb/pam_userdb.c that allows a local or network-adjacent attacker able to repeatedly drive authentication through a calling service to recover the plaintext password of a target account by measuring response-timing differences.
Remediation
There is no fixed version for Debian:13 pam.
References
- https://security-tracker.debian.org/tracker/CVE-2026-54411
- https://cwe.mitre.org/data/definitions/208.html
- https://github.com/linux-pam/linux-pam
- https://github.com/linux-pam/linux-pam/blob/master/libpam/include/pam_inline.h
- https://github.com/linux-pam/linux-pam/blob/master/modules/pam_userdb/pam_userdb.c#L327
low severity
- Vulnerable module: patch
- Introduced through: patch@2.8-2
Detailed paths
-
Introduced through: php@8.2-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.
GNU patch is vulnerable to a denial of service (DoS) due to improper validation of hunk (single block of changes in diff) line offsets in unified-diff input. A specially crafted patch can specify an extremely large line number, causing the application to enter an effectively infinite processing loop while attempting to locate the requested position. This results in excessive CPU consumption and prevents the process from completing. An attacker can trigger this behavior by supplying a malicious patch file, causing the utility to become unresponsive and require manual termination.
This issue has been fixed in the commit faba04ef4f2b410257f76c1b9dc85e350929c4b9
Remediation
There is no fixed version for Debian:13 patch.
References
low severity
- Vulnerable module: patch
- Introduced through: patch@2.8-2
Detailed paths
-
Introduced through: php@8.2-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.
GNU patch is vulnerable to a NULL pointer dereference when processing a specially crafted unified-diff patch file. Improper handling of consecutive end-of-file newline markers can corrupt internal hunk (single block of changes in diff) data structures, causing the application to pass a NULL pointer to fwrite() during patch processing. An attacker can trigger this condition with a malicious patch file, causing the utility to crash and resulting in a denial of service.
This issue has been fixed in the commit e6d6a4e021660679d7fc9150f981d4920f722313
Remediation
There is no fixed version for Debian:13 patch.
References
low severity
new
- Vulnerable module: pcre2/libpcre2-8-0
- Introduced through: pcre2/libpcre2-8-0@10.46-1~deb13u1
- Fixed in: 10.46-1~deb13u2
Detailed paths
-
Introduced through: php@8.2-apache › pcre2/libpcre2-8-0@10.46-1~deb13u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream pcre2 package and not the pcre2 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
PCRE2 before 10.48 allows a pcre2_dfa_match out-of-bounds write because reuse of a cached workspace block, in a recursive DFA matching workspace, lacks a size check (even though a newly allocated block, for the same purpose, does have a size check). This outcome requires an attacker-controlled regular expression, or a recursive pattern in conjunction with a small heap limit (this can be set through the API).
Remediation
Upgrade Debian:13 pcre2 to version 10.46-1~deb13u2 or higher.
References
low severity
- Vulnerable module: perl
- Introduced through: perl@5.40.1-6, perl/libperl5.40@5.40.1-6 and others
- Fixed in: 5.40.1-6+deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › perl@5.40.1-6
-
Introduced through: php@8.2-apache › perl/libperl5.40@5.40.1-6
-
Introduced through: php@8.2-apache › perl/perl-base@5.40.1-6
-
Introduced through: php@8.2-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
Upgrade Debian:13 perl to version 5.40.1-6+deb13u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-15649
- https://github.com/pmqs/IO-Compress/commit/fd28c1d2374eee9811f6d0c5bddc0957abdf1da8.patch
- https://github.com/pmqs/IO-Compress/issues/65
- https://metacpan.org/release/PMQS/IO-Compress-2.215/changes
- http://www.openwall.com/lists/oss-security/2026/05/27/1
low severity
- Vulnerable module: perl
- Introduced through: perl@5.40.1-6, perl/libperl5.40@5.40.1-6 and others
- Fixed in: 5.40.1-6+deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › perl@5.40.1-6
-
Introduced through: php@8.2-apache › perl/libperl5.40@5.40.1-6
-
Introduced through: php@8.2-apache › perl/perl-base@5.40.1-6
-
Introduced through: php@8.2-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.
Socket versions before 2.041 for Perl have an out-of-bounds heap read.
In Socket.xs, pack_ip_mreq_source() checks the length of its source argument before the argument is read, so the check tests the byte length carried over from the preceding multiaddr argument instead. Both addresses occupy a 4-byte field, so a valid multiaddr lets a source of any length pass the check, and the source is then copied into the 4-byte imr_sourceaddr field with a fixed-size copy. A source shorter than 4 bytes is not rejected, and the copy reads up to 3 bytes past the end of its buffer.
Calling pack_ip_mreq_source() with a source value shorter than 4 bytes copies adjacent heap memory into the returned packed structure.
Remediation
Upgrade Debian:13 perl to version 5.40.1-6+deb13u1 or higher.
References
low severity
- Vulnerable module: perl
- Introduced through: perl@5.40.1-6, perl/libperl5.40@5.40.1-6 and others
Detailed paths
-
Introduced through: php@8.2-apache › perl@5.40.1-6
-
Introduced through: php@8.2-apache › perl/libperl5.40@5.40.1-6
-
Introduced through: php@8.2-apache › perl/perl-base@5.40.1-6
-
Introduced through: php@8.2-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.45.1 have out-of-bounds heap reads and writes during regular expression matching via an undersized superlinear cache in S_regmatch.
The regex engine's superlinear cache holds one bit per subject position for each participating WHILEM node, so the bit count is the subject length plus one times the number of nodes. Nothing checks that product for positive overflow of the signed 32-bit count: a 286331153 byte subject matched against a pattern with 15 participating nodes stores the count as 14, leaving a two byte cache. The cache is then indexed from the real match position and node number, so reads go past the end of the allocation, and on failure CACHEsayNO sets a bit past it.
A caller that matches an attacker controlled subject of this size against a pattern of this shape can crash the process or corrupt heap memory.
Remediation
There is no fixed version for Debian:13 perl.
References
- https://security-tracker.debian.org/tracker/CVE-2026-15534
- https://github.com/Perl/perl5/commit/54cf3d44cbbedd17d774e9a37921963e8fd5d0cb.patch
- https://github.com/Perl/perl5/commit/568e6fd238867bb9e99fa3f47cba3169009239e0.patch
- http://www.openwall.com/lists/oss-security/2026/08/09/12
- http://www.openwall.com/lists/oss-security/2026/08/09/13
low severity
- Vulnerable module: perl
- Introduced through: perl@5.40.1-6, perl/libperl5.40@5.40.1-6 and others
Detailed paths
-
Introduced through: php@8.2-apache › perl@5.40.1-6
-
Introduced through: php@8.2-apache › perl/libperl5.40@5.40.1-6
-
Introduced through: php@8.2-apache › perl/perl-base@5.40.1-6
-
Introduced through: php@8.2-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 from 5.9.4 before 5.41.9 produce incorrect regular expression match results when a stale failure flag ends the Aho-Corasick prescan early in S_find_byclass.
The prescan walks the subject for positions where the full pattern could match, and the engine tries it from the leftmost one recorded. A failing transition sets the failed flag, and a later successful transition does not clear it, so the prescan reads the stale flag as a failure and stops before it can record a candidate that starts earlier. It takes a subject where one candidate is recorded and a later character then forces a fallback through a fail link that succeeds.
Example:
"ABCDE" =~ m/ABCF|BCDE|C/; # matches C at offset 2, not BCDE "ABCDE" =~ m/ABCF|BCDE|C(G)/; # no match, BCDE missed
An alternation like this can miss input it should match, or match it on the wrong branch, so an access or filtering decision made from the result can be wrong.
Remediation
There is no fixed version for Debian:13 perl.
References
low severity
- Vulnerable module: perl
- Introduced through: perl@5.40.1-6, perl/libperl5.40@5.40.1-6 and others
- Fixed in: 5.40.1-6+deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › perl@5.40.1-6
-
Introduced through: php@8.2-apache › perl/libperl5.40@5.40.1-6
-
Introduced through: php@8.2-apache › perl/perl-base@5.40.1-6
-
Introduced through: php@8.2-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
Upgrade Debian:13 perl to version 5.40.1-6+deb13u1 or higher.
References
low severity
- Vulnerable module: perl
- Introduced through: perl@5.40.1-6, perl/libperl5.40@5.40.1-6 and others
- Fixed in: 5.40.1-6+deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › perl@5.40.1-6
-
Introduced through: php@8.2-apache › perl/libperl5.40@5.40.1-6
-
Introduced through: php@8.2-apache › perl/perl-base@5.40.1-6
-
Introduced through: php@8.2-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
Upgrade Debian:13 perl to version 5.40.1-6+deb13u1 or higher.
References
low severity
- Vulnerable module: perl
- Introduced through: perl@5.40.1-6, perl/libperl5.40@5.40.1-6 and others
- Fixed in: 5.40.1-6+deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › perl@5.40.1-6
-
Introduced through: php@8.2-apache › perl/libperl5.40@5.40.1-6
-
Introduced through: php@8.2-apache › perl/perl-base@5.40.1-6
-
Introduced through: php@8.2-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
Upgrade Debian:13 perl to version 5.40.1-6+deb13u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-48962
- https://github.com/pmqs/IO-Compress/commit/f2db247bf90d4cc7ee2710be384946081f3b4610.patch
- https://metacpan.org/release/PMQS/IO-Compress-2.220/changes
- http://www.openwall.com/lists/oss-security/2026/05/27/4
- https://access.redhat.com/errata/RHSA-2026:29182
- https://access.redhat.com/errata/RHSA-2026:29210
- https://access.redhat.com/errata/RHSA-2026:29867
- https://access.redhat.com/errata/RHSA-2026:29941
- https://access.redhat.com/errata/RHSA-2026:30085
- https://access.redhat.com/errata/RHSA-2026:30086
- https://access.redhat.com/errata/RHSA-2026:30115
- https://access.redhat.com/errata/RHSA-2026:30843
- https://access.redhat.com/errata/RHSA-2026:30851
- https://access.redhat.com/errata/RHSA-2026:30858
- https://access.redhat.com/errata/RHSA-2026:30859
- https://access.redhat.com/errata/RHSA-2026:30860
- https://access.redhat.com/security/cve/CVE-2026-48962
- https://bugzilla.redhat.com/show_bug.cgi?id=2481767
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-48962.json
- https://access.redhat.com/errata/RHSA-2026:50262
low severity
- Vulnerable module: perl
- Introduced through: perl@5.40.1-6, perl/libperl5.40@5.40.1-6 and others
- Fixed in: 5.40.1-6+deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › perl@5.40.1-6
-
Introduced through: php@8.2-apache › perl/libperl5.40@5.40.1-6
-
Introduced through: php@8.2-apache › perl/perl-base@5.40.1-6
-
Introduced through: php@8.2-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.
Storable versions before 3.41 for Perl have a signed integer overflow when deserializing a crafted SX_HOOK record.
retrieve_hook_common reads a signed 32-bit item count from an SX_HOOK record and calls av_extend with that count plus one. A count of I32_MAX wraps the addition to a negative value.
A crafted blob passed to thaw or retrieve triggers the overflow; av_extend receives the negative count and dies with a panic, terminating the deserialization.
Remediation
Upgrade Debian:13 perl to version 5.40.1-6+deb13u1 or higher.
References
low severity
- Vulnerable module: perl
- Introduced through: perl@5.40.1-6, perl/libperl5.40@5.40.1-6 and others
- Fixed in: 5.40.1-6+deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › perl@5.40.1-6
-
Introduced through: php@8.2-apache › perl/libperl5.40@5.40.1-6
-
Introduced through: php@8.2-apache › perl/perl-base@5.40.1-6
-
Introduced through: php@8.2-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
Upgrade Debian:13 perl to version 5.40.1-6+deb13u1 or higher.
References
low severity
- Vulnerable module: perl
- Introduced through: perl@5.40.1-6, perl/libperl5.40@5.40.1-6 and others
- Fixed in: 5.40.1-6+deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › perl@5.40.1-6
-
Introduced through: php@8.2-apache › perl/libperl5.40@5.40.1-6
-
Introduced through: php@8.2-apache › perl/perl-base@5.40.1-6
-
Introduced through: php@8.2-apache › perl/perl-modules-5.40@5.40.1-6
NVD Description
This vulnerability has not been analyzed by NVD yet.
Remediation
Upgrade Debian:13 perl to version 5.40.1-6+deb13u1 or higher.
References
low severity
new
- Vulnerable module: perl
- Introduced through: perl@5.40.1-6, perl/libperl5.40@5.40.1-6 and others
Detailed paths
-
Introduced through: php@8.2-apache › perl@5.40.1-6
-
Introduced through: php@8.2-apache › perl/libperl5.40@5.40.1-6
-
Introduced through: php@8.2-apache › perl/perl-base@5.40.1-6
-
Introduced through: php@8.2-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.
Pod::Text versions before 6.1.1 for Perl allow CPU and memory exhaustion formatting a POD document whose =over nesting drives the margin to the output width.
Each =over adds its indent to the margin, which wrap() subtracts from the output width to get the space available for text. When that space reaches zero, the line-splitting substitution matches the empty string, and the loop consumes no input while appending the margin padding on every pass.
Formatting an attacker-supplied POD document never returns, and the output grows until memory is exhausted.
Remediation
There is no fixed version for Debian:13 perl.
References
- https://security-tracker.debian.org/tracker/CVE-2026-82560
- https://github.com/rra/podlators/commit/70510174f69eb54aa6d617bde4e1402cd9b7c61f.patch
- https://metacpan.org/release/RRA/podlators-v6.1.0/source/lib/Pod/Text.pm#L245-261
- https://metacpan.org/release/RRA/podlators-v6.1.1/changes
- http://www.openwall.com/lists/oss-security/2026/09/19/6
low severity
- Vulnerable module: shadow/login.defs
- Introduced through: shadow/login.defs@1:4.17.4-2 and shadow/passwd@1:4.17.4-2
Detailed paths
-
Introduced through: php@8.2-apache › shadow/login.defs@1:4.17.4-2
-
Introduced through: php@8.2-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
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.46.1-7+deb13u1
Detailed paths
-
Introduced through: php@8.2-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
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.46.1-7+deb13u1
Detailed paths
-
Introduced through: php@8.2-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 NULL pointer dereference in the SQLite Session Extension in SQLite 3.53.1 and SQLite trunk builds before check-in e807d4e3798efd53 allows an attacker who can supply a malformed changeset blob to cause a denial of service. The issue occurs when sqlite3changeset_apply_v3() applies a corrupt changeset and reaches sqlite3_value_type() with a NULL sqlite3_value pointer.
Remediation
There is no fixed version for Debian:13 sqlite3.
References
low severity
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.46.1-7+deb13u1
Detailed paths
-
Introduced through: php@8.2-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 issue in SQLite before Fossil check-in 869a51ae84df allows a local attacker to obtain sensitive information via the Session Extension changeset concat/changegroup merge path
Remediation
There is no fixed version for Debian:13 sqlite3.
References
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@257.13-1~deb13u1 and systemd/libudev1@257.13-1~deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › systemd/libsystemd0@257.13-1~deb13u1
-
Introduced through: php@8.2-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.
Local unprivileged users can terminate arbitrary local processes via a systemd-oomd IPC API due to a missing path traversal validation.
Remediation
There is no fixed version for Debian:13 systemd.
References
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@257.13-1~deb13u1 and systemd/libudev1@257.13-1~deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › systemd/libsystemd0@257.13-1~deb13u1
-
Introduced through: php@8.2-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-homed contains a local privilege escalation bug via arbitrary system group addition to a local, logged in, homed-managed user
Remediation
There is no fixed version for Debian:13 systemd.
References
low severity
- Vulnerable module: util-linux
- Introduced through: util-linux@2.41-5, util-linux/libblkid1@2.41-5 and others
- Fixed in: 2.41.5-0+deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › util-linux@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libblkid1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/liblastlog2-2@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libmount1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libsmartcols1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libuuid1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/mount@2.41-5
NVD Description
This vulnerability has not been analyzed by NVD yet.
Remediation
Upgrade Debian:13 util-linux to version 2.41.5-0+deb13u1 or higher.
References
low severity
- Vulnerable module: util-linux
- Introduced through: util-linux@2.41-5, util-linux/libblkid1@2.41-5 and others
- Fixed in: 2.41.5-0+deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › util-linux@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libblkid1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/liblastlog2-2@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libmount1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libsmartcols1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libuuid1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/mount@2.41-5
NVD Description
This vulnerability has not been analyzed by NVD yet.
Remediation
Upgrade Debian:13 util-linux to version 2.41.5-0+deb13u1 or higher.
References
low severity
- Vulnerable module: util-linux
- Introduced through: util-linux@2.41-5, util-linux/libblkid1@2.41-5 and others
- Fixed in: 2.41.5-0+deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › util-linux@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libblkid1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/liblastlog2-2@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libmount1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libsmartcols1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libuuid1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/mount@2.41-5
NVD Description
This vulnerability has not been analyzed by NVD yet.
Remediation
Upgrade Debian:13 util-linux to version 2.41.5-0+deb13u1 or higher.
References
low severity
- Vulnerable module: util-linux
- Introduced through: util-linux@2.41-5, util-linux/libblkid1@2.41-5 and others
- Fixed in: 2.41.5-0+deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › util-linux@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libblkid1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/liblastlog2-2@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libmount1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libsmartcols1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libuuid1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/mount@2.41-5
NVD Description
This vulnerability has not been analyzed by NVD yet.
Remediation
Upgrade Debian:13 util-linux to version 2.41.5-0+deb13u1 or higher.
References
low severity
- Vulnerable module: util-linux
- Introduced through: util-linux@2.41-5, util-linux/libblkid1@2.41-5 and others
- Fixed in: 2.41.5-0+deb13u1
Detailed paths
-
Introduced through: php@8.2-apache › util-linux@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libblkid1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/liblastlog2-2@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libmount1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libsmartcols1@2.41-5
-
Introduced through: php@8.2-apache › util-linux/libuuid1@2.41-5
-
Introduced through: php@8.2-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
Upgrade Debian:13 util-linux to version 2.41.5-0+deb13u1 or higher.