# CVE-2003-0270: Weak cryptography in n/a

> Remote attackers can sniff weakly encrypted credentials to gain administrative access to Apple AirPort wireless access points.

- **Severity:** High 7.6 (`AV:N/AC:H/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 May 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-252p-hhm3-3h4m

## What is CVE-2003-0270?

CVE-2003-0270 is a high-severity vulnerability in n/a, published on 14 May 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The administration capability for Apple AirPort 802.11 wireless access point devices uses weak encryption (XOR with a fixed key) for protecting authentication credentials, which could allow remote attackers to obtain administrative access via sniffing when the capability is available via Ethernet or non-WEP connections.

## Which versions are affected by CVE-2003-0270?

It affects 1 product.


Products: Apple 802.11n.

## How do I fix CVE-2003-0270?

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

## Is CVE-2003-0270 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-0270 exists.

Public exploit code:

- Apple Airport ACPP Authentication Scanner (metasploit)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-0270 and fix it if it is affected.

What it is: CVE-2003-0270 is a high-severity vulnerability in n/a, published on 14 May 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-0270 exists.

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-2003-0270/ (Markdown: https://insights.sbomify.com/CVE-2003-0270/index.md)
```

## Sources

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

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