# CVE-2002-1426: Denial of service in n/a

> Remote attackers can crash HP ProCurve Switches by sending oversized SNMP write requests, causing a denial of service.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/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:** 18 Mar 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-p8h7-r4qf-mgv5

## What is CVE-2002-1426?

CVE-2002-1426 is a high-severity denial of service vulnerability in n/a, published on 18 Mar 2003. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

HP ProCurve Switch 4000M C.07.23 allows remote attackers to cause a denial of service (crash) via an SNMP write request containing 85 characters, possibly triggering a buffer overflow.

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

It affects 1 product.


Products: Hp Procurve Switch 4000m.

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

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

## Is CVE-2002-1426 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-1426 exists.

Public exploit code:

- HP ProCurve Switch 4000M - SNMP Write Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2002-0350](https://insights.sbomify.com/CVE-2002-0350/): Denial of service in n/a (high 7.8)
- [CVE-2002-1147](https://insights.sbomify.com/CVE-2002-1147/): Missing authorization in n/a (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-1426 is a high-severity denial of service vulnerability in n/a, published on 18 Mar 2003. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-1426 exists.

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-1426/ (Markdown: https://insights.sbomify.com/CVE-2002-1426/index.md)
```

## Sources

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

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