# CVE-2001-1573: Memory corruption in n/a

> Remote attackers can execute arbitrary code via a buffer overflow in the smtpscan.dll component of Trend Micro InterScan VirusWall.

- **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:** No
- **Published:** 5 Aug 2005
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-2jgc-gr2q-548r

## What is CVE-2001-1573?

CVE-2001-1573 is a critical memory corruption vulnerability in n/a, published on 5 Aug 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in smtpscan.dll for Trend Micro InterScan VirusWall 3.51 for Windows NT has allows remote attackers to execute arbitrary code via a certain configuration parameter.

## Which versions are affected by CVE-2001-1573?

It affects 1 product.


Products: Trend Micro Interscan Viruswall.

## How do I fix CVE-2001-1573?

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

## Is CVE-2001-1573 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2001-1574](https://insights.sbomify.com/CVE-2001-1574/): Memory corruption in n/a (critical 10.0)
- [CVE-2001-0679](https://insights.sbomify.com/CVE-2001-0679/): Memory corruption in n/a (critical 10.0)
- [CVE-2001-0432](https://insights.sbomify.com/CVE-2001-0432/): Memory corruption in n/a (critical 10.0)
- [CVE-2001-0133](https://insights.sbomify.com/CVE-2001-0133/): Information disclosure in n/a (critical 10.0)
- [CVE-2000-0428](https://insights.sbomify.com/CVE-2000-0428/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-1573 and fix it if it is affected.

What it is: CVE-2001-1573 is a critical memory corruption vulnerability in n/a, published on 5 Aug 2005. 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-2001-1573 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-2001-1573/ (Markdown: https://insights.sbomify.com/CVE-2001-1573/index.md)
```

## Sources

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

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