# CVE-2003-1344: Information disclosure in n/a

> Remote attackers can obtain usernames and encrypted passwords by requesting specific log files from the Trend Micro Virus Control System Log Collector.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2007
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-j9jf-v6vm-xv8j

## What is CVE-2003-1344?

CVE-2003-1344 is a medium-severity vulnerability in n/a, published on 14 Oct 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Trend Micro Virus Control System (TVCS) Log Collector allows remote attackers to obtain usernames, encrypted passwords, and other sensitive information via a URL request for getservers.exe with the action parameter set to "selects1", which returns log files.

Weakness: CWE-310

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

It affects 1 product.


Products: Trend Micro Virus Control System.

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

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

## Is CVE-2003-1344 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-1344 exists.

Public exploit code:

- Trend Micro Virus Control System 1.8 - Information Disclosure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2001-0689](https://insights.sbomify.com/CVE-2001-0689/): Missing authorization in n/a (high 7.5)
- [CVE-2003-1342](https://insights.sbomify.com/CVE-2003-1342/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2003-1344 is a medium-severity vulnerability in n/a, published on 14 Oct 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-1344 exists.

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-1344/ (Markdown: https://insights.sbomify.com/CVE-2003-1344/index.md)
```

## Sources

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

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