# CVE-2005-0643: Memory corruption in n/a

> Remote attackers can execute arbitrary code via crafted LHA files due to a buffer overflow in the McAfee Scan Engine.

- **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:** 20 Mar 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-jxrm-52q6-p6p3

## What is CVE-2005-0643?

CVE-2005-0643 is a high-severity memory corruption vulnerability in n/a, published on 20 Mar 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in McAfee Scan Engine 4320 with DAT version before 4357 allows remote attackers to execute arbitrary code via crafted LHA files.

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

It affects 1 product.


Products: Mcafee Antivirus Engine.

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

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

## Is CVE-2005-0643 being exploited?

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

Public exploit code:

- LHA 1.x - Remote Buffer Overflow / Directory Traversal (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2005-0644](https://insights.sbomify.com/CVE-2005-0644/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-0643 is a high-severity memory corruption vulnerability in n/a, published on 20 Mar 2005. 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-2005-0643 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-2005-0643/ (Markdown: https://insights.sbomify.com/CVE-2005-0643/index.md)
```

## Sources

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

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