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

> Buffer overflows in Gnocatan allow attackers to execute arbitrary code, requiring users to upgrade to a patched version.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 18 Jun 2003
- **Updated:** 17 Sep 2024
- **Also known as:** DSA-315, GHSA-jp7h-w5mf-w95f

## What is CVE-2003-0433?

CVE-2003-0433 is a high-severity memory corruption vulnerability in n/a, published on 18 Jun 2003. 

### Official description

Multiple buffer overflows in gnocatan 0.6.1 and earlier allow attackers to execute arbitrary code.

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

It affects 1 product.


Products: Gnocatan-Develop Gnocatan.

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

Upgrade to a fixed version.

## Is CVE-2003-0433 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2003-0433 is a high-severity memory corruption vulnerability in n/a, published on 18 Jun 2003. 
Exploitation: There is no known exploitation of CVE-2003-0433 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-0433/ (Markdown: https://insights.sbomify.com/CVE-2003-0433/index.md)
```

## Sources

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

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