# CVE-2005-3218: Security feature bypass in n/a

> Remote attackers can bypass virus detection in Dr.Web Antivirus by sending malicious executables in specially crafted RAR files.

- **Severity:** Medium 5.1 (`AV:N/AC:H/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Oct 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wgmq-2j65-4gv7

## What is CVE-2005-3218?

CVE-2005-3218 is a medium-severity vulnerability in n/a, published on 14 Oct 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Multiple interpretation error in unspecified versions of Dr.Web Antivirus allows remote attackers to bypass virus detection via a malicious executable in a specially crafted RAR file with malformed central and local headers, which can still be opened by products such as Winrar and PowerZip, even though they are rejected as corrupted by Winzip and BitZipper.

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

It affects 1 product.


Products: Dr.web Dr.web Antivirus.

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

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

## Is CVE-2005-3218 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-3373](https://insights.sbomify.com/CVE-2005-3373/): Security feature bypass in n/a (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-3218 is a medium-severity vulnerability in n/a, published on 14 Oct 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2005-3218 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-3218/ (Markdown: https://insights.sbomify.com/CVE-2005-3218/index.md)
```

## Sources

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

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