Skip to content
Fencer Intel
medium 5.9

CVE-2013-0294 json

pyrad is vulnerable to the use of Insufficiently Random Values

published 6y ago modified 4mo ago also GHSA-q4v3-wmm6-hcrx , PYSEC-2020-211 , EUVD-2020-0156

cvss
5.9
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.8%
EPSS 2.8% chance of exploitation in 30 days, percentile 86%
public exploits
0
none known

Summary

packet.py in pyrad before 2.1 uses weak random numbers to generate RADIUS authenticators and hash passwords, which makes it easier for remote attackers to obtain sensitive information via a brute force attack.

Patch / fix

  • pypi pyrad 2.1
  • pyrad_project pyrad 2.1
  • pyrad Debian 14, Debian 13, Debian 12 2.0-2

debian advisories DEBIAN-CVE-2013-0294

Is CVE-2013-0294 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2013-0294 updated cvss 5.8

python-pyrad: poor randomness leads to predictable password hashing and RADIUS IDs

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.85% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N
GitHub 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
pypi pyrad
<2.1
2.1

Affected products

  • pyrad pyrad

Classification

Weakness
  • CWE-330 Use of Insufficiently Random Values

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.