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

> Remote attackers can cause denial of service or execute arbitrary code via off-by-one errors in multiple protocol dissectors.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 May 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-mxvh-95qr-ww4v

## What is CVE-2003-0356?

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

### Official description

Multiple off-by-one vulnerabilities in Ethereal 0.9.11 and earlier allow remote attackers to cause a denial of service and possibly execute arbitrary code via the (1) AIM, (2) GIOP Gryphon, (3) OSPF, (4) PPTP, (5) Quake, (6) Quake2, (7) Quake3, (8) Rsync, (9) SMB, (10) SMPP, and (11) TSP dissectors, which do not properly use the tvb_get_nstringz and tvb_get_nstringz0 functions.

Weakness: CWE-193 (Off-by-one Error)

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

It affects 1 product.


Products: Ethereal Ethereal.

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

Upgrade to a fixed version.

## Is CVE-2003-0356 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-0365](https://insights.sbomify.com/CVE-2004-0365/): Null dereference in n/a (high 7.5)
- [CVE-2003-1013](https://insights.sbomify.com/CVE-2003-1013/): Null dereference in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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