# CVE-2007-0488: Denial of service in n/a

> Remote attackers can crash Huawei Quidway R1600 routers by sending a long show arp command, causing denial of service.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **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:** 25 Jan 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7cmj-p544-vw4q

## What is CVE-2007-0488?

CVE-2007-0488 is a medium-severity denial of service vulnerability in n/a, published on 25 Jan 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Huawei Versatile Routing Platform 1.43 2500E-003 firmware on the Quidway R1600 Router, and possibly other models, allows remote attackers to cause a denial of service (device crash) via a long show arp command.

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

It affects 1 product.


Products: Huawei Versatile Routing Platform.

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

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

## Is CVE-2007-0488 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2007-0488 is a medium-severity denial of service vulnerability in n/a, published on 25 Jan 2007. 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-0488 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-0488/ (Markdown: https://insights.sbomify.com/CVE-2007-0488/index.md)
```

## Sources

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

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