# CVE-2010-1425: Security feature bypass in n/a

> Remote attackers can bypass malware detection in F-Secure products by using crafted archive files, requiring user interaction to open the malicious file.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **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:** 15 Apr 2010
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-hc3f-7h3x-c3v8

## What is CVE-2010-1425?

CVE-2010-1425 is a medium-severity vulnerability in n/a, published on 15 Apr 2010. 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

F-Secure Internet Security 2010 and earlier; Anti-Virus for Microsoft Exchange 9 and earlier, and for MIMEsweeper 5.61 and earlier; Internet Gatekeeper for Windows 6.61 and earlier, and for Linux 4.02 and earlier; Anti-Virus 2010 and earlier; Home Server Security 2009; Protection Service for Consumers 9 and earlier, for Business - Workstation security 9 and earlier, for Business - Server Security 8 and earlier, and for E-mail and Server security 9 and earlier; Mac Protection build 8060 and earlier; Client Security 9 and earlier; and various Anti-Virus products for Windows, Linux, and Citrix; does not properly detect malware in crafted (1) 7Z, (2) GZIP, (3) CAB, or (4) RAR archives, which makes it easier for remote attackers to avoid detection.

## Which versions are affected by CVE-2010-1425?

It affects 14 products.


Products: F-Secure Anti-Virus, F-Secure F-Secure Anti-Virus, F-Secure F-Secure Anti-Virus Client Security, F-Secure F-Secure Anti-Virus for Citrix Servers, F-Secure F-Secure Anti-Virus for Linux, F-Secure F-Secure Anti-Virus for Microsoft Exchange, F-Secure F-Secure Anti-Virus for Mimesweeper, F-Secure F-Secure Anti-Virus for Windows Servers, F-Secure F-Secure Anti-Virus for Workstations, F-Secure F-Secure Anti-Virus Linux Client Security, F-Secure F-Secure Anti-Virus Linux Server Security, F-Secure F-Secure Internet Security, F-Secure Home Server Security, F-Secure Internet Gatekeeper.

## How do I fix CVE-2010-1425?

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

## Is CVE-2010-1425 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-7369](https://insights.sbomify.com/CVE-2013-7369/): SQL injection in n/a (high 7.5)
- [CVE-2009-1782](https://insights.sbomify.com/CVE-2009-1782/): Security feature bypass in n/a (medium 6.8)
- [CVE-2010-3499](https://insights.sbomify.com/CVE-2010-3499/): Security feature bypass in n/a (medium 6.4)
- [CVE-2012-6646](https://insights.sbomify.com/CVE-2012-6646/): Security feature bypass in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-1425 and fix it if it is affected.

What it is: CVE-2010-1425 is a medium-severity vulnerability in n/a, published on 15 Apr 2010. 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-2010-1425 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-2010-1425/ (Markdown: https://insights.sbomify.com/CVE-2010-1425/index.md)
```

## Sources

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

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