First published: Fri 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: <a href="https://github.com/wichert/pyrad/commit/38f74b36814ca5b1a27d9898141126af4953bee5">https://github.com/wichert/pyrad/commit/38f74b36814ca5b1a27d9898141126af4953bee5</a>
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/python-pyrad | <2.1 | 2.1 |
pip/pyrad | <2.1 | 2.1 |
Pyrad | <2.1 | |
Fedora | =18 | |
Fedora | =19 | |
Fedora | =20 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2013-0294 is classified as a moderate severity vulnerability affecting the pyrad package.
To fix CVE-2013-0294, upgrade pyrad to version 2.1 or later.
CVE-2013-0294 affects pyrad versions prior to 2.1.
The impact of CVE-2013-0294 includes potential exposure of sensitive data due to inadequate random number generation.
CVE-2013-0294 was reported by Nathaniel McCallum.