/ 
Apache-Session-1.94
/ Apache::Session::Store::Informix
Security Advisories (3)
CVE-2013-10075 (2026-05-08)

Apache::Session versions through 1.94 for Perl re-creates deleted sessions. The session stores Apache::Session::Store::File and Apache::Session::Store::DB_File will create a session that does not exist. This can lead to sessions being revived, potentially with data that was to be deleted.

CVE-2025-40931 (2026-03-05)

Apache::Session::Generate::MD5 versions through 1.94 for Perl create insecure session id. Apache::Session::Generate::MD5 generates session ids insecurely. The default session id generator returns a MD5 hash seeded with the built-in rand() function, the epoch time, and the PID. The PID will come from a small set of numbers, and the epoch time may be guessed, if it is not leaked from the HTTP Date header. The built-in rand function is unsuitable for cryptographic usage. Predicable session ids could allow an attacker to gain access to systems. Note that the libapache-session-perl package in some Debian-based Linux distributions may be patched to use Crypt::URandom.

CVE-2026-5081 (2026-05-06)

Apache::Session::Generate::ModUniqueId versions from 1.54 through 1.94 for Perl session ids are insecure. Apache::Session::Generate::ModUniqueId (added in version 1.54) uses the value of the UNIQUE_ID environment variable for the session id. The UNIQUE_ID variable is set by the Apache mod_unique_id plugin, which generates unique ids for the request. The id is based on the IPv4 address, the process id, the epoch time, a 16-bit counter and a thread index, with no obfuscation. The server IP is often available to the public, and if not available, can be guessed from previous session ids being issued. The process ids may also be guessed from previous session ids. The timestamp is easily guessed (and leaked in the HTTP Date response header). The purpose of mod_unique_id is to assign a unique id to requests so that events can be correlated in different logs. The id is not designed, nor is it suitable for security purposes.

NAME

Apache::Session::Store::Informix - Store persistent data in a Informix database

SYNOPSIS

use Apache::Session::Store::Informix;

my $store = new Apache::Session::Store::Informix;

$store->insert($ref);
$store->update($ref);
$store->materialize($ref);
$store->remove($ref);

DESCRIPTION

Apache::Session::Store::Informix fulfills the storage interface of Apache::Session. Session data is stored in a Informix database.

SCHEMA

To use this module, you will need at least these columns in a table called 'sessions':

id char(32)     # or however long your session IDs are.
a_session lvarchar

To create this schema, you can execute this command using the sqlplus program:

CREATE TABLE sessions (
   id char(32) not null primary key,
   a_session lvarchar
);

If you use some other command, ensure that there is a unique index on the table's id column.

CONFIGURATION

The module must know what datasource, username, and password to use when connecting to the database. These values can be set using the options hash (see Apache::Session documentation). The options are DataSource, UserName, and Password.

Example:

tie %hash, 'Apache::Session::Informix', $id, {
    DataSource => 'dbi:Informix:database',
    UserName   => 'database_user',
    Password   => 'K00l'
};

Instead, you may pass in an already-opened DBI handle to your database.

tie %hash, 'Apache::Session::Informix', $id, {
    Handle => $dbh
};

The last option is LongReadLen, which specifies the maximum size of the session object. If not supplied, the default maximum size is 8 KB.

AUTHOR

This module was written by Mike Langen <mike.langen@tamedia.ch>, based on the original for Oracle.

SEE ALSO

Apache::Session, Apache::Session::Store::DBI