CVE-2013-0294: Medium severity pyrad vulnerability

Published Feb 15, 2013
·
Updated

Nathaniel McCallum reported that pyrad was using Python's random module in a number of places to generate pseudo-random data. In the case of the authenticator data, it was being used to secure a password sent over the wire. Because Python's random module is not really suited for this purpose (not random enough), it could lead to password hashing that may be predictable.

This has been corrected in upstream's forthcoming version 2.1 via:

https://github.com/wichert/pyrad/commit/38f74b36814ca5b1a27d9898141126af4953bee5

Other sources

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.

MITRE

Affected Software

6 affected componentsFixes available
redhat/python-pyrad<2.1
2.1
pip/pyrad<2.1
2.1
Pyrad Project Pyrad<2.1
Fedoraproject Fedora=18
Fedoraproject Fedora=19
Fedoraproject Fedora=20

Event History

Jan 28, 2020
CVE Published
via MITRE·03:53 PM
Data Sourced
via MITRE·03:53 PM
DescriptionWeakness
May 5, 2022
Advisory Published
via GitHub·12:29 AM

Frequently Asked Questions

1

What is the severity of CVE-2013-0294?

CVE-2013-0294 is classified as a moderate severity vulnerability affecting the pyrad package.

2

How do I fix CVE-2013-0294?

To fix CVE-2013-0294, upgrade pyrad to version 2.1 or later.

3

Which software versions are affected by CVE-2013-0294?

CVE-2013-0294 affects pyrad versions prior to 2.1.

4

What is the impact of CVE-2013-0294?

The impact of CVE-2013-0294 includes potential exposure of sensitive data due to inadequate random number generation.

5

Who reported CVE-2013-0294?

CVE-2013-0294 was reported by Nathaniel McCallum.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203