# CVE-2002-1312: Memory corruption in n/a

> Remote attackers can crash Linksys routers via a buffer overflow in the web management interface when remote management is enabled.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/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:** 14 Apr 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-pcmr-f7vq-p97c

## What is CVE-2002-1312?

CVE-2002-1312 is a medium-severity memory corruption vulnerability in n/a, published on 14 Apr 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in the Web management interface in Linksys BEFW11S4 wireless access point router 2 and BEFSR11, BEFSR41, and BEFSRU31 EtherFast Cable/DSL routers with firmware before 1.43.3 with remote management enabled allows remote attackers to cause a denial of service (router crash) via a long password.

## Which versions are affected by CVE-2002-1312?

It affects 9 products.


Products: Linksys Befn2ps4, Linksys Befsr11, Linksys Befsr41, Linksys Befsr81, Linksys Befsru31, Linksys Befsx41, Linksys Befvp41, Linksys Befw11s4, Linksys Hpro200.

## How do I fix CVE-2002-1312?

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

## Is CVE-2002-1312 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-0109](https://insights.sbomify.com/CVE-2002-0109/): Information disclosure in n/a (medium 6.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-1312 and fix it if it is affected.

What it is: CVE-2002-1312 is a medium-severity memory corruption vulnerability in n/a, published on 14 Apr 2005. 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-2002-1312 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-2002-1312/ (Markdown: https://insights.sbomify.com/CVE-2002-1312/index.md)
```

## Sources

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

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