# CVE-2007-1338: Security feature bypass in n/a

> Remote attackers can bypass IPv4 access restrictions on Apple AirPort Extreme routers by exploiting an unblocked IPv6 tunnel in the default configuration.

- **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:** 7 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-j777-7mfw-w8wv

## What is CVE-2007-1338?

CVE-2007-1338 is a high-severity vulnerability in n/a, published on 7 Mar 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The default configuration of the AirPort utility in Apple AirPort Extreme creates an IPv6 tunnel but does not enable the "Block incoming IPv6 connections" setting, which might allow remote attackers to bypass intended access restrictions by establishing IPv6 sessions that would have been rejected over IPv4.

## Which versions are affected by CVE-2007-1338?

It affects 1 product.


Products: Apple Airport Extreme.

## How do I fix CVE-2007-1338?

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

## Is CVE-2007-1338 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-1338 and fix it if it is affected.

What it is: CVE-2007-1338 is a high-severity vulnerability in n/a, published on 7 Mar 2007. 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-2007-1338 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-2007-1338/ (Markdown: https://insights.sbomify.com/CVE-2007-1338/index.md)
```

## Sources

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

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