# CVE-2012-1453: Security feature bypass in n/a

> Remote attackers can bypass malware detection in multiple antivirus products by sending a specially crafted CAB file with a modified coffFiles field.

- **Severity:** Medium 4.3 (`AV:N/AC:M/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:** Not needed
- **Fix available:** No
- **Published:** 21 Mar 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-q3xc-hm3w-5mx3

## What is CVE-2012-1453?

CVE-2012-1453 is a medium-severity vulnerability in n/a, published on 21 Mar 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The CAB file parser in Dr.Web 5.0.2.03300, Trend Micro HouseCall 9.120.0.1004, Kaspersky Anti-Virus 7.0.0.125, Sophos Anti-Virus 4.61.0, Trend Micro AntiVirus 9.120.0.1004, McAfee Gateway (formerly Webwasher) 2010.1C, Emsisoft Anti-Malware 5.1.0.1, CA eTrust Vet Antivirus 36.1.8511, Antiy Labs AVL SDK 2.0.3.7, Antimalware Engine 1.1.6402.0 in Microsoft Security Essentials 2.0, Rising Antivirus 22.83.00.03, Ikarus Virus Utilities T3 Command Line Scanner 1.1.97.0, Fortinet Antivirus 4.2.254.0, and Panda Antivirus 10.0.2.7 allows remote attackers to bypass malware detection via a CAB file with a modified coffFiles field.  NOTE: this may later be SPLIT into multiple CVEs if additional information is published showing that the error occurred independently in different CAB parser implementations.

Weakness: CWE-264

## Which versions are affected by CVE-2012-1453?

It affects 14 products.


Products: Antiy Avl Sdk, Ca Etrust Vet Antivirus, Drweb Dr.web Antivirus, Emsisoft Anti-Malware, Fortinet Fortinet Antivirus, Ikarus Ikarus Virus Utilities T3 Command Line Scanner, Kaspersky Kaspersky Anti-Virus, Mcafee Gateway, Microsoft Security Essentials, Pandasecurity Panda Antivirus, Rising-Global Rising Antivirus, Sophos Sophos Anti-Virus, Trendmicro Housecall, Trendmicro Trend Micro Antivirus.

## How do I fix CVE-2012-1453?

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

## Is CVE-2012-1453 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-1424](https://insights.sbomify.com/CVE-2012-1424/): Security feature bypass in n/a (medium 4.3)
- [CVE-2012-1425](https://insights.sbomify.com/CVE-2012-1425/): Security feature bypass in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-1453 and fix it if it is affected.

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

## Sources

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

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