Logo
componentlibdbi-perl
Name
libdbi-perl
Version
1.643
Type
library
Description
The Perl Database Interface
Licenses
Artistic-1.0 | GPL-1.0-or-later
PURL
-
CPE
cpe:2.3:*:*:libdbi-perl:1.643:*:*:*:*:*:*:*

Other Versions#


Project
Branch
Version
kirkstone
1.643
master
1.651

Patches#


#
Title
Author
Resolve
1
Fix possible stack overflow (old issue already noted by Tim)
"H.Merijn Brand - Tux" <linux@tux.freedom.nl>
CVE-2026-9698
2
Set a hard limit of 99999 on '?' placeholders
"H.Merijn Brand - Tux" <linux@tux.freedom.nl>
CVE-2026-14739
3
Improve CVE-2026-14380 tests for Profile
Robert Rothenberg <perl@rhizomnic.com>
CVE-2026-14380
4
Load profile packages using Module::Load [CVE-2026-14380]
Robert Rothenberg <perl@rhizomnic.com>
CVE-2026-14380
5
lib/DBD/File.pm: fix CVE-2014-10401
Jens Rehsack <sno@netbsd.org>
CVE-2014-10402
6
Replacing `?` with `:p#` in `preparse ()` with more than 9
"H.Merijn Brand - Tux" <linux@tux.freedom.nl>
CVE-2026-10879
7
t/40profile.t increase number of tests in the plan
Robert Rothenberg <perl@rhizomnic.com>
CVE-2026-14380
8
Fix out-of-bounds read in preparse when an initial comment is
Robert Rothenberg <perl@rhizomnic.com>
CVE-2026-14740
9
Add tests for CVE-2026-14380
Robert Rothenberg <perl@rhizomnic.com>
CVE-2026-14380

Vulnerabilities#


Name
Analysis
Description
Patched
DBI versions before 1.648 for Perl saved errors in a limited-sized buffer. Error messages that were returned when RaiseError, PrintError or HandleError were set were written to a 200-byte buffer without a length limit. Attackers that can influence the error text in an application can trigger a buffer overflow.
Patched
DBI versions before 1.650 for Perl read one byte out-of-bounds in preparse when deleting an initial SQL comment. The preparse method normalises SQL and removes comments. When the SQL starts with a comment line, the deletion of that line during normalisation led to an out-of-bounds read by one byte. The result is a fault on memory-hardened builds and nondeterministic newline retention on normal builds.
Patched
DBI versions before 1.650 for Perl have a heap overflow when preparsing SQL statements with an extreme number of placeholders. The fix for CVE-2026-10879 did not allocate enough memory to handle approximately 1.2-million placeholders. DBI version 1.650 sets a hard limit of 99,999 placeholders.
Patched
DBI versions before 1.650 for Perl are vulnerable to code injection via caller-influenced Profile. When a string is assigned to a DBI handle's Profile attribute, DBI splits it into path, package and arguments, and interpolates the package part in a string eval with no validation of the package name. Any caller-influenced value that reaches the Profile attribute is therefore arbitrary Perl code execution, including calls to run system commands. The Profile attribute can be set from three different sources that can carry untrusted data: the DBI_PROFILE environment variable, a direct attribute assignment, and a DSN driver-attribute clause dbi:Driver(Profile=>SPEC):db. An attacker controlling any of those inputs runs arbitrary Perl in the host process. The strongest remote position is a network-exposed DBI::Gofer / DBI::ProxyServer whose per-request DSN reaches the Profile attribute, letting a client execute code on the broker host.
Patched
DBI versions before 1.648 for Perl have a heap overflow when preparsing SQL statements with more than 9 binders. The preparse method expands SQL placeholder characters to numbered binders of the form :pN, but only allocates three characters per binder in the buffer. Placeholders 10-99 require four characters, 100-999 require five characters, et cetera.
Patched
An issue was discovered in the DBI module through 1.643 for Perl. DBD::File drivers can open files from folders other than those specifically passed via the f_dir attribute in the data source name (DSN). NOTE: this issue exists because of an incomplete fix for CVE-2014-10401.