CVE-2013-0342: Input Validation
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:
https://github.com/wichert/pyrad/commit/38f74b36814ca5b1a27d9898141126af4953bee5
Other sources
The CreateID function in packet.py in pyrad before 2.1 uses sequential packet IDs, which makes it easier for remote attackers to spoof packets by predicting the next ID, a different vulnerability than CVE-2013-0294.
— MITRE
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2013-0342?
CVE-2013-0342 is considered a high severity vulnerability due to the potential for ID spoofing in RADIUS packets.
How do I fix CVE-2013-0342?
To fix CVE-2013-0342, upgrade pyrad to version 2.1 or later.
What type of vulnerability is CVE-2013-0342?
CVE-2013-0342 is a vulnerability related to unpredictable ID generation in RADIUS packet handling.
Who reported CVE-2013-0342?
CVE-2013-0342 was reported by Nathaniel McCallum.
In which function was the vulnerability identified for CVE-2013-0342?
The vulnerability in CVE-2013-0342 was identified in the CreateID() function within packet.py.