# CVE-2008-1197: Memory corruption in n/a

> Authenticated attackers can cause denial of service or execute arbitrary code on Netgear WN802T access points via malformed SSID requests.

- **Severity:** Medium 6.3 (`AV:N/AC:M/Au:S/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Sep 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8cg2-w5hc-m7gr

## What is CVE-2008-1197?

CVE-2008-1197 is a medium-severity memory corruption vulnerability in n/a, published on 5 Sep 2008. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Marvell driver for the Netgear WN802T Wi-Fi access point with firmware 1.3.16 on the Marvell 88W8361P-BEM1 chipset does not properly parse the SSID information element in an association request, which allows remote authenticated users to cause a denial of service (device reboot or hang) or possibly execute arbitrary code via a "Null SSID."

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2008-1197?

It affects 2 products.


Products: Marvell 88w8361w-Bem1, Netgear Wn802t.

## How do I fix CVE-2008-1197?

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

## Is CVE-2008-1197 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-1144](https://insights.sbomify.com/CVE-2008-1144/): Memory corruption in n/a (medium 6.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-1197 and fix it if it is affected.

What it is: CVE-2008-1197 is a medium-severity memory corruption vulnerability in n/a, published on 5 Sep 2008. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-1197 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-2008-1197/ (Markdown: https://insights.sbomify.com/CVE-2008-1197/index.md)
```

## Sources

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

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