First published: Fri Feb 15 2013(Updated: )
Nathaniel McCallum reported that pyrad was creating serialized RADIUS packet IDs in the CreateID() function in packet.py. This is not suitable for RADIUS as the RFC specifies that the ID must not be predictable. As a result, the ID of the next packet sent can be spoofed. 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 |
---|---|---|
pip/pyrad | <2.1 | 2.1 |
Pyrad | <2.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2013-0342 is considered a high severity vulnerability due to the potential for ID spoofing in RADIUS packets.
To fix CVE-2013-0342, upgrade pyrad to version 2.1 or later.
CVE-2013-0342 is a vulnerability related to unpredictable ID generation in RADIUS packet handling.
CVE-2013-0342 was reported by Nathaniel McCallum.
The vulnerability in CVE-2013-0342 was identified in the CreateID() function within packet.py.