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

> Remote attackers can trigger a buffer overflow in l2tpd by sending a long attribute value, potentially leading to code execution or service disruption.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Apr 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-6hfv-gvx3-3h9v

## What is CVE-2002-0873?

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

### Official description

Vulnerability in l2tpd 0.67 allows remote attackers to overwrite the vendor field via a long value in an attribute/value pair, possibly via a buffer overflow.

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

It affects 1 product.


Products: L2tpd L2tpd.

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

Upgrade to a fixed version.

## Is CVE-2002-0873 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-0872](https://insights.sbomify.com/CVE-2002-0872/): Weak cryptography in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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