First published: Fri Dec 16 2005(Updated: )
Wireless Access Points (AP) for (1) Avaya AP-3 through AP-6 2.5 to 2.5.4, and AP-7/AP-8 2.5 and other versions before 3.1, and (2) Proxim AP-600 and AP-2000 before 2.5.5, and Proxim AP-700 and AP-4000 after 2.4.11 and before 3.1, use a static WEP key of "12345", which allows remote attackers to bypass authentication.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Avaya Wireless AP-6 | =2.5 | |
Avaya Wireless AP-6 | =2.5.4 | |
Avaya Wireless AP-7 | =2.5 | |
Avaya Wireless AP-5 | =2.5.4 | |
Avaya Wireless AP-4 | =2.5.4 | |
Avaya Wireless AP-4 | =2.5 | |
Avaya Wireless AP-5 | =2.5 | |
Avaya Wireless AP-8 | =2.5 | |
Avaya Wireless AP-3 | =2.5 | |
Avaya Wireless AP-3 | =2.5.4 | |
Proxim Ap-4000 | =2.4.12 | |
Proxim AP-700 | =2.4.12 | |
Proxim AP-700 | =3.0 | |
Proxim Ap-2000 | =2.5.4 | |
Proxim Ap-4000 | =3.0 | |
Proxim AP-600 | =2.5.4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2005-3253 is considered to have a high severity due to the use of a static WEP key that can be easily exploited by attackers.
To fix CVE-2005-3253, update the firmware on the affected Avaya and Proxim wireless access points to versions that do not utilize static WEP keys.
CVE-2005-3253 affects Avaya AP-3 through AP-6 versions 2.5 to 2.5.4, AP-7/AP-8 versions before 3.1, and Proxim AP-600, AP-2000 versions before 2.5.5, and AP-700/AP-4000 versions before 3.1.
CVE-2005-3253 allows remote attackers to bypass wireless security by exploiting the static WEP key.
A workaround for CVE-2005-3253 is to disable WEP and use stronger encryption methods, such as WPA2, if possible.