/ 
CGI-Session-4.10
/ CGI::Session::Driver::sqlite
Security Advisories (2)
CPANSA-CGI-Session-2006-01 (2006-04-06)

possible SQL injection attack

CVE-2026-56016 (2026-07-01)

CGI::Session::ID::md5 versions before 4.49 for Perl generate predictable session ids from low-entropy sources. The generate_id method builds the session id from a MD5 digest of the process id, the epoch time, and the built-in rand() function. All three are predictable, low-entropy sources: the PID is drawn from a small range, the epoch time can be guessed or read from the HTTP Date header, and Perl's rand() is unsuitable for security purposes because it is predictable and reversible. An attacker who predicts a session id can impersonate the corresponding session and bypass authentication.

NAME

CGI::Session::Driver::sqlite - CGI::Session driver for SQLite

SYNOPSIS

$s = new CGI::Session("driver:sqlite", $sid, {DataSource=>'/my/folder/sessions.sqlt'});
$s = new CGI::Session("driver:sqlite", $sid, {Handle=>$dbh});

DESCRIPTION

sqlite driver stores session data in SQLite files using DBD::SQLite DBI driver. More details see CGI::Session::Driver::DBI, its parent class.

DRIVER ARGUMENTS

Supported driver arguments are DataSource and Handle. At most only one of these arguments can be set while creating session object.

DataSource should be in the form of dbi:SQLite:dbname=/path/to/db.sqlt. If dbi:SQLite: is missing it will be prepended for you. If Handle is present it should be database handle ($dbh) returned by DBI::connect().

As of version 1.7 of this driver, the third argument is NOT optional. Using a default database in the temporary directory is a security risk since anyone on the machine can create and/or read your session data. If you understand these risks and still want the old behavior, you can set the DataSource option to '/tmp/sessions.sqlt'.

BUGS AND LIMITATIONS

None known.

LICENSING

For support and licensing see CGI::Session