# CVE-2004-0619: Integer overflow in n/a

> Local attackers can trigger an integer overflow in the Broadcom 5820 cryptonet driver to cause a system crash or execute arbitrary code.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 30 Jun 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-g9v2-9ccx-44qr

## What is CVE-2004-0619?

CVE-2004-0619 is a high-severity vulnerability in Redhat Fedora Core, published on 30 Jun 2004. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Integer overflow in the ubsec_keysetup function for Linux Broadcom 5820 cryptonet driver allows local users to cause a denial of service (crash) and possibly execute arbitrary code via a negative add_dsa_buf_bytes variable, which leads to a buffer overflow.

## Which versions are affected by CVE-2004-0619?

It affects 3 products.


Products: Redhat Fedora Core, Redhat Kernel, Redhat Linux.

## How do I fix CVE-2004-0619?

Apply the vendor's patch.

## Is CVE-2004-0619 being exploited?

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

## Other vulnerabilities in Redhat Fedora Core

- [CVE-2004-1154](https://insights.sbomify.com/CVE-2004-1154/): Integer overflow in n/a (critical 10.0)
- [CVE-2004-0989](https://insights.sbomify.com/CVE-2004-0989/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-0453](https://insights.sbomify.com/CVE-2006-0453/): Use after free in n/a (high 7.8)
- [CVE-2007-2874](https://insights.sbomify.com/CVE-2007-2874/): Memory corruption in n/a (medium 5.8)
- [CVE-2005-3630](https://insights.sbomify.com/CVE-2005-3630/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-0619 and fix it if it is affected.

What it is: CVE-2004-0619 is a high-severity vulnerability in Redhat Fedora Core, published on 30 Jun 2004. 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-2004-0619 in the wild and no public exploit code.

Affected product: Redhat Fedora Core. 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-2004-0619/ (Markdown: https://insights.sbomify.com/CVE-2004-0619/index.md)
```

## Sources

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

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