CVE-2013-0342: The CreateID function in packet.py in pyrad before 2.1 uses sequential packet IDs, which makes it easier fo...

Security readout for executives and security teams

pyrad before 2.1 generated RADIUS packet IDs sequentially. That predictability can make packet spoofing easier for a remote attacker, which matters most where pyrad supports authentication, authorization, or accounting flows. The source bundle does not provide CVSS scoring or active exploitation evidence. Exposure is limited to systems or applications using pyrad versions before 2.1. Risk is higher when pyrad participates in reachable RADIUS-related authentication or accounting traffic. The bundle does not identify downstream products, distributions, or specific deployment patterns. Treat this as targeted dependency cleanup, not an emergency by itself. Prioritize remediation where pyrad is tied to authentication infrastructure or reachable RADIUS workflows, because spoofing risk can affect trust decisions. Mitigation focus: Upgrade pyrad to version 2.1 or later.; Inventory applications and services that import or package pyrad.; Review vendor or distribution advisories for backported fixes..

Prepared

Jun 6, 2026, 03:53 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.