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

> Remote attackers can bypass F-Prot Antivirus protection by sending ZIP files with specific version headers, preventing file analysis.

- **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:** 4 Nov 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-845f-qg27-4gv6

## What is CVE-2005-3499?

CVE-2005-3499 is a high-severity vulnerability in n/a, published on 4 Nov 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Frisk F-Prot Antivirus allows remote attackers to bypass protection via a ZIP file with a version header greater than 15, which prevents F-Prot from decompressing and analyzing the file.

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

It affects 1 product.


Products: Frisk Software F-Prot Antivirus.

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

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

## Is CVE-2005-3499 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-6294](https://insights.sbomify.com/CVE-2006-6294/): Multiple unspecified vulnerabilities in FRISK Software F-Prot Antivirus before 4.6.7 have unspecified impact and attack vectors. (high 7.5)
- [CVE-2005-3374](https://insights.sbomify.com/CVE-2005-3374/): Security feature bypass in n/a (medium 5.1)
- [CVE-2005-3213](https://insights.sbomify.com/CVE-2005-3213/): Security feature bypass in n/a (medium 5.1)
- [CVE-2006-6352](https://insights.sbomify.com/CVE-2006-6352/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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