Http::Session2
Approved changes feed: RSS · Atom
cpe:2.3:a:tokuhirom:http\:\:session2:*:*:*:*:*:perl:*:*
part: a version: * update: *
| Vendor | Tokuhirom (e7be1a59-2cec-585e-9645-9dba2f687da1) |
|---|---|
| Product | Http::Session2 (223b5ad4-59a1-5d26-baff-bcac65e82b40) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | perl |
| 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-3255 |
vulnerable | 2026-06-08 08:01:18.268234 |
HTTP::Session2 versions before 1.12 for Perl may generate weak session ids using the rand() function
HTTP::Session2 versions before 1.12 for Perl for Perl may generate weak session ids using the rand() function.
The HTTP::Session2 session id generator returns 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.
HTTP::Session2 after version 1.02 will attempt to use the /dev/urandom device to generate a session id, but if the device is unavailable (for example, under Windows), then it will revert to the insecure method described above.
Published: 2026-02-27T20:12:35.414Z
Updated: 2026-03-03T20:23:53.160Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2018-25160 |
vulnerable | 2026-06-08 05:11:29.515228 |
HTTP::Session2 versions through 1.09 for Perl does not validate the format of user provided session ids, enabling code injection or other impact depending on session backend
HTTP::Session2 versions through 1.09 for Perl does not validate the format of user provided session ids, enabling code injection or other impact depending on session backend.
For example, if an application uses memcached for session storage, then it may be possible for a remote attacker to inject memcached commands in the session id value.
Published: 2026-02-27T20:15:31.418Z
Updated: 2026-03-03T20:22:20.829Z |
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.