# CVE-2008-4594: Other in n/a

> Unspecified vulnerability in Linksys WAP4400N firmware SNMPv3 component with unknown impact and attack vectors, likely remote.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 17 Oct 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-q393-8mr4-385r

## What is CVE-2008-4594?

CVE-2008-4594 is a critical vulnerability in n/a, published on 17 Oct 2008. It can be exploited over the network.

### Official description

Unspecified vulnerability in the SNMPv3 component in Linksys WAP4400N firmware 1.2.14 on the Marvell Semiconductor 88W8361P-BEM1 chipset has unknown impact and attack vectors, probably remote.

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

It affects 1 product.


Products: Linksys Wap400n.

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

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

## Is CVE-2008-4594 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-4441](https://insights.sbomify.com/CVE-2008-4441/): The Marvell driver for the Linksys WAP4400N Wi-Fi access point with firmware 1.2.14 on the Marvell 88W8361P-BEM1 chipset, when WEP mode is e (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-4594 is a critical vulnerability in n/a, published on 17 Oct 2008. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2008-4594 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-4594/ (Markdown: https://insights.sbomify.com/CVE-2008-4594/index.md)
```

## Sources

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

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