# CVE-2005-3253: Hardcoded credentials in n/a

> Remote attackers can bypass authentication on Avaya and Proxim wireless access points due to a static WEP key, requiring firmware upgrades.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Dec 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-72m9-jj7r-733c

## What is CVE-2005-3253?

CVE-2005-3253 is a high-severity vulnerability in n/a, published on 16 Dec 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2005-3253?

It affects 10 products.


Products: Avaya Wireless Ap-3, Avaya Wireless Ap-4, Avaya Wireless Ap-5, Avaya Wireless Ap-6, Avaya Wireless Ap-7, Avaya Wireless Ap-8, Proxim Ap-2000, Proxim Ap-4000, Proxim Ap-600, Proxim Ap-700.

## How do I fix CVE-2005-3253?

No fix has been published for CVE-2005-3253 yet. Limit exposure of the affected software until one is available.

## Is CVE-2005-3253 being exploited?

There is no known exploitation of CVE-2005-3253 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-3253 and fix it if it is affected.

What it is: CVE-2005-3253 is a high-severity vulnerability in n/a, published on 16 Dec 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-3253 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2005-3253/ (Markdown: https://insights.sbomify.com/CVE-2005-3253/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2005-3253
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2005-3253
- OSV: https://osv.dev/vulnerability/CVE-2005-3253

---
From sbomify Insights: https://insights.sbomify.com/CVE-2005-3253/
Summaries are generated and may contain mistakes; the official description above is the record.