# CVE-2007-5474: Memory corruption in n/a

> Remote authenticated users can cause denial of service or execute arbitrary code on Linksys WRT350N access points via malformed Atheros information elements.

- **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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Sep 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-v648-rmcj-67cw

## What is CVE-2007-5474?

CVE-2007-5474 is a medium-severity memory corruption vulnerability in n/a, published on 5 Sep 2008. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The driver for the Linksys WRT350N Wi-Fi access point with firmware 2.00.17 on the Atheros AR5416-AC1E chipset does not properly parse the Atheros vendor-specific 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 an Atheros information element with an invalid length, as demonstrated by an element that is too long.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 2 products.


Products: Atheros Ar5416-Ac1e Chipset, Linksys Wrt350n.

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

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

## Is CVE-2007-5474 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2007-5474 is a medium-severity memory corruption vulnerability in n/a, published on 5 Sep 2008. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-5474 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-5474/ (Markdown: https://insights.sbomify.com/CVE-2007-5474/index.md)
```

## Sources

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

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