|
|
Message-Id: <A7758CF9-10E3-4268-8D53-3B68828B2146@stig.io>
Date: Mon, 11 May 2026 09:25:34 +0200
From: Stig Palmquist <stig@...g.io>
To: cve-announce@...urity.metacpan.org,
oss-security@...ts.openwall.com
Subject: CVE-2026-5084: WebDyne::Session versions through 2.075 for Perl
generates the session id insecurely
========================================================================
CVE-2026-5084 CPAN Security Group
========================================================================
CVE ID: CVE-2026-5084
Distribution: WebDyne
Versions: through 2.075
MetaCPAN: https://metacpan.org/dist/WebDyne
VCS Repo: https://github.com/aspeer/WebDyne
WebDyne::Session versions through 2.075 for Perl generates the session
id insecurely
Description
-----------
WebDyne::Session versions through 2.075 for Perl generates the session
id insecurely.
The session handler generates the session id from an MD5 hash seeded
with a call to the built-in rand() function. The rand function is
passed a maximum value based on the process id, the epoch time and the
reference address of the object, but this information will have no
effect on the overall quality of the seed of the message digest.
The rand function is seeded by 32-bits and is predictable. It is
considered unsuitable for cryptographic purposes.
Predictable session ids could allow an attacker to gain access to
systems.
Note that WebDyne::Session versions 1.042 and earlier appear to be in
separate distributions from WebDyne.
Problem types
-------------
- CWE-340 Generation of Predictable Numbers or Identifiers
- CWE-338 Use of Cryptographically Weak Pseudo-Random Number Generator
References
----------
https://metacpan.org/release/ASPEER/WebDyne-2.075/source/lib/WebDyne/Session.pm#L120
https://webdyne.org
https://security.metacpan.org/docs/guides/random-data-for-security.html
Powered by blists - more mailing lists
Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.