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

> Local users with plugin upload privileges can trigger buffer overflows in Nessus, potentially causing denial of service or arbitrary code execution.

- **Severity:** Medium 4.4 (`AV:L/AC:M/Au:N/C:P/I:P/A:P`)
- **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:** No
- **Published:** 6 Jun 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-p685-86cj-cwf4

## What is CVE-2003-0373?

CVE-2003-0373 is a medium-severity memory corruption vulnerability in n/a, published on 6 Jun 2003. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Multiple buffer overflows in libnasl in Nessus before 2.0.6 allow local users with plugin upload privileges to cause a denial of service (core dump) and possibly execute arbitrary code via (1) a long proto argument to the scanner_add_port function, (2) a long user argument to the ftp_log_in function, (3) a long pass argument to the ftp_log_in function.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Nessus Nessus.

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

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

## Is CVE-2003-0373 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-0374](https://insights.sbomify.com/CVE-2003-0374/): Multiple unknown vulnerabilities in Nessus before 2.0.6, in libnessus and possibly libnasl, a different set of vulnerabilities than those id (critical 10.0)
- [CVE-2003-0372](https://insights.sbomify.com/CVE-2003-0372/): Integer overflow in n/a (medium 4.6)
- [CVE-2007-3546](https://insights.sbomify.com/CVE-2007-3546/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2004-1445](https://insights.sbomify.com/CVE-2004-1445/): Race condition in n/a (low 3.7)
- [CVE-2006-2093](https://insights.sbomify.com/CVE-2006-2093/): Denial of service in n/a (low 2.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2003-0373 is a medium-severity memory corruption vulnerability in n/a, published on 6 Jun 2003. 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-2003-0373 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-0373/ (Markdown: https://insights.sbomify.com/CVE-2003-0373/index.md)
```

## Sources

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

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