Approved changes feed: RSS · Atom
cpe:2.3:a:chorny:apache::session::generate::moduniqueid:*:*:*:*:*:*:*:*
part: a version: * update: session
| Vendor | Chorny (4488ffc5-6f4d-552b-b0cd-c9be8b23af11) |
|---|---|
| Product | Apache (b013771b-0a95-563b-8981-6d84ef0c267e) |
| Edition | * |
| Language | generate |
| Software edition | * |
| Target software | moduniqueid |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-5081 |
vulnerable | 2026-06-08 08:07:02.971849 |
Apache::Session::Generate::ModUniqueId versions from 1.54 through 1.94 for Perl session ids are insecure
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.
Published: 2026-05-06T12:16:38.452Z
Updated: 2026-07-15T00:46:26.786Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.