Apache::Session::Generate::ModUniqueId versions from 1.54 through 1.94 for Perl session ids are insecure
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| CHORNY | Apache::Session::Generate::ModUniqueId | unaffected |
|
Configuration 1 [-]
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Chorny | Apache::session::generate::moduniqueid |
|
Vendor Solution
In cases where the session id is used for authentication or provides access to restricted data, consider alternate solutions like Apache::Session::Generate::Random.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.302% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Chorny apache\
|
|
| CPEs | cpe:2.3:a:chorny:apache\:\:session\:\:generate\:\:moduniqueid:*:*:*:*:*:perl:*:* | |
| Vendors & Products |
Chorny apache\
|
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-341 | |
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Chorny
Chorny apache::session::generate::moduniqueid |
|
| Vendors & Products |
Chorny
Chorny apache::session::generate::moduniqueid |
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Apache::Session::Generate::ModUniqueId versions from 1.54 through 1.94 for Perl session ids are insecure | |
| Weaknesses | CWE-340 | |
| References |
|