# CVE-2005-0383: Auth bypass in n/a

> Remote attackers can gain privileges by replaying encrypted credentials in Trend Micro Control Manager.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Feb 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-2jvf-qvqx-mrwj

## What is CVE-2005-0383?

CVE-2005-0383 is a high-severity authentication bypass vulnerability in n/a, published on 13 Feb 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Trend Micro Control Manager 3.0 Enterprise Edition allows remote attackers to gain privileges via a replay attack of the encrypted username and password.

## Which versions are affected by CVE-2005-0383?

It affects 1 product.


Products: Trend Micro Control Manager.

## How do I fix CVE-2005-0383?

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

## Is CVE-2005-0383 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-5001](https://insights.sbomify.com/CVE-2011-5001/): Memory corruption in n/a (critical 10.0)
- [CVE-2012-2998](https://insights.sbomify.com/CVE-2012-2998/): SQL injection in n/a (high 7.5)
- [CVE-2006-3261](https://insights.sbomify.com/CVE-2006-3261/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-0383 and fix it if it is affected.

What it is: CVE-2005-0383 is a high-severity authentication bypass vulnerability in n/a, published on 13 Feb 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-2005-0383 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-2005-0383/ (Markdown: https://insights.sbomify.com/CVE-2005-0383/index.md)
```

## Sources

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

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