# CVE-2003-0858: Denial of service in n/a

> Local attackers can cause a denial of service in Zebra and Quagga by sending spoofed messages to the kernel netlink interface.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Nov 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-44r4-q6xp-rh44, RHSA-2003:315

## What is CVE-2003-0858?

CVE-2003-0858 is a low-severity denial of service vulnerability in n/a, published on 18 Nov 2003. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Zebra 0.93b and earlier, and quagga before 0.95, allows local users to cause a denial of service by sending spoofed messages as other users to the kernel netlink interface.

Weakness: CWE-399

## Which versions are affected by CVE-2003-0858?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `quagga` | Red Hat:enterprise_linux:3::as | All versions | 0:0.96.2-8.3E |
| `quagga-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 0:0.96.2-8.3E |
| `quagga` | Red Hat:enterprise_linux:3::es | All versions | 0:0.96.2-8.3E |
| `quagga-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 0:0.96.2-8.3E |

Products: Gnu Zebra, Quagga Quagga Routing Software Suite.

## How do I fix CVE-2003-0858?

Upgrade to a fixed version.

## Is CVE-2003-0858 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-0795](https://insights.sbomify.com/CVE-2003-0795/): Null dereference in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-0858 and fix it if it is affected.

What it is: CVE-2003-0858 is a low-severity denial of service vulnerability in n/a, published on 18 Nov 2003. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2003-0858 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-2003-0858/ (Markdown: https://insights.sbomify.com/CVE-2003-0858/index.md)
```

## Sources

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

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