# CVE-2002-1912: Null dereference in n/a

> Remote attackers can cause a kernel panic and denial of service on SkyStream EMR5000 devices by sending excessive packets that trigger a null pointer exception.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jun 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-rrxf-p629-997j

## What is CVE-2002-1912?

CVE-2002-1912 is a high-severity vulnerability in n/a, published on 28 Jun 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SkyStream EMR5000 1.16 through 1.18 does not drop packets or disable the Ethernet interface when the buffers are full, which allows remote attackers to cause a denial of service (null pointer exception and kernel panic) via a large number of packets.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Skystream Emr5000.

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

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

## Is CVE-2002-1912 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2002-1912 is a high-severity vulnerability in n/a, published on 28 Jun 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-1912 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-1912/ (Markdown: https://insights.sbomify.com/CVE-2002-1912/index.md)
```

## Sources

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

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