The session id is generated from a SHA-1 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 Ado is no longer maintained, and has been removed from the CPAN index. It is still available on BackPAN.
Metrics
Affected Vendors & Products
No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Wed, 08 Apr 2026 19:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Berov
Berov ado::sessions |
|
| Vendors & Products |
Berov
Berov ado::sessions |
Wed, 08 Apr 2026 19:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Wed, 08 Apr 2026 16:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
Wed, 08 Apr 2026 06:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Ado::Sessions versions through 0.935 for Perl generates insecure session ids. The session id is generated from a SHA-1 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 Ado is no longer maintained, and has been removed from the CPAN index. It is still available on BackPAN. | |
| Title | Ado::Sessions versions through 0.935 for Perl generates insecure session ids | |
| Weaknesses | CWE-338 CWE-340 |
|
| References |
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: CPANSec
Published:
Updated: 2026-04-08T17:24:13.917Z
Reserved: 2026-03-28T19:14:30.969Z
Link: CVE-2026-5083
Updated: 2026-04-08T16:08:22.603Z
Status : Awaiting Analysis
Published: 2026-04-08T06:16:29.163
Modified: 2026-04-08T21:26:35.910
Link: CVE-2026-5083
No data.
OpenCVE Enrichment
Updated: 2026-04-08T19:43:50Z