# CVE-2003-0033: Memory corruption in n/a

> Remote attackers can execute arbitrary code on Snort systems by sending fragmented RPC packets due to a buffer overflow in the RPC preprocessor.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Sep 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-2wc7-p52f-xgxm

## What is CVE-2003-0033?

CVE-2003-0033 is a critical memory corruption vulnerability in n/a, published on 1 Sep 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in the RPC preprocessor for Snort 1.8 and 1.9.x before 1.9.1 allows remote attackers to execute arbitrary code via fragmented RPC packets.

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

It affects 1 product.


Products: Snort Snort.

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

Upgrade to a fixed version.

## Is CVE-2003-0033 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-5276](https://insights.sbomify.com/CVE-2006-5276/): Memory corruption in n/a (critical 10.0)
- [CVE-2016-1417](https://insights.sbomify.com/CVE-2016-1417/): Path traversal in n/a (high 8.8)
- [CVE-2007-0251](https://insights.sbomify.com/CVE-2007-0251/): Integer overflow in n/a (high 7.8)
- [CVE-2007-1398](https://insights.sbomify.com/CVE-2007-1398/): Denial of service in n/a (high 7.1)
- [CVE-2008-1804](https://insights.sbomify.com/CVE-2008-1804/): Security feature bypass in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2003-0033 is a critical memory corruption vulnerability in n/a, published on 1 Sep 2004. 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-2003-0033 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-0033/ (Markdown: https://insights.sbomify.com/CVE-2003-0033/index.md)
```

## Sources

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

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