# CVE-2012-1457: Security feature bypass in n/a > Remote attackers can bypass malware detection in multiple antivirus engines by crafting a TAR archive with an invalid length 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:** Yes - **Published:** 21 Mar 2012 - **Updated:** 6 Aug 2024 - **Also known as:** DEBIAN-CVE-2012-1457, GHSA-j7hj-5xvp-7w4p ## What is CVE-2012-1457? CVE-2012-1457 is a medium-severity vulnerability in Clamav Clamav, 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 TAR file parser in Avira AntiVir 7.11.1.163, Antiy Labs AVL SDK 2.0.3.7, avast! Antivirus 4.8.1351.0 and 5.0.677.0, AVG Anti-Virus 10.0.0.1190, Bitdefender 7.2, Quick Heal (aka Cat QuickHeal) 11.00, ClamAV 0.96.4, Command Antivirus 5.2.11.5, Emsisoft Anti-Malware 5.1.0.1, eSafe 7.0.17.0, F-Prot Antivirus 4.6.2.117, G Data AntiVirus 21, Ikarus Virus Utilities T3 Command Line Scanner 1.1.97.0, Jiangmin Antivirus 13.0.900, K7 AntiVirus 9.77.3565, Kaspersky Anti-Virus 7.0.0.125, McAfee Anti-Virus Scanning Engine 5.400.0.1158, McAfee Gateway (formerly Webwasher) 2010.1C, Antimalware Engine 1.1.6402.0 in Microsoft Security Essentials 2.0, NOD32 Antivirus 5795, Norman Antivirus 6.06.12, PC Tools AntiVirus 7.0.3.5, Rising Antivirus 22.83.00.03, AVEngine 20101.3.0.103 in Symantec Endpoint Protection 11, Trend Micro AntiVirus 9.120.0.1004, Trend Micro HouseCall 9.120.0.1004, VBA32 3.12.14.2, and VirusBuster 13.6.151.0 allows remote attackers to bypass malware detection via a TAR archive entry with a length field that exceeds the total TAR file size. NOTE: this may later be SPLIT into multiple CVEs if additional information is published showing that the error occurred independently in different TAR parser implementations. Weakness: CWE-264 ## Which versions are affected by CVE-2012-1457? It affects 28 products. Products: Aladdin Esafe, Alwil Avast Antivirus, Anti-Virus Vba32, Antiy Avl Sdk, Authentium Command Antivirus, Avg Avg Anti-Virus, Avira Antivir, Bitdefender Bitdefender, Cat Quick Heal, Clamav Clamav, Emsisoft Anti-Malware, Eset Nod32 Antivirus, F-Prot F-Prot Antivirus, Gdata-Software G Data Antivirus, Ikarus Ikarus Virus Utilities T3 Command Line Scanner, Jiangmin Jiangmin Antivirus, K7computing Antivirus, Kaspersky Kaspersky Anti-Virus, Mcafee Gateway, Mcafee Scan Engine and 8 more. ## How do I fix CVE-2012-1457? Apply the vendor's patch. ## Is CVE-2012-1457 being exploited? There is no known exploitation of CVE-2012-1457 in the wild and no public exploit code. ## Other vulnerabilities in Clamav Clamav - [CVE-2008-5528](https://insights.sbomify.com/CVE-2008-5528/): Security feature bypass in n/a (critical 9.3) - [CVE-2012-1429](https://insights.sbomify.com/CVE-2012-1429/): Security feature bypass in n/a (medium 4.3) - [CVE-2012-1430](https://insights.sbomify.com/CVE-2012-1430/): Security feature bypass in n/a (medium 4.3) - [CVE-2012-1431](https://insights.sbomify.com/CVE-2012-1431/): Security feature bypass in n/a (medium 4.3) - [CVE-2012-1432](https://insights.sbomify.com/CVE-2012-1432/): Security feature bypass in n/a (medium 4.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2012-1457 and fix it if it is affected. What it is: CVE-2012-1457 is a medium-severity vulnerability in Clamav Clamav, 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-1457 in the wild and no public exploit code. Affected product: Clamav Clamav. 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-1457/ (Markdown: https://insights.sbomify.com/CVE-2012-1457/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2012-1457 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-1457 - OSV: https://osv.dev/vulnerability/CVE-2012-1457 --- From sbomify Insights: https://insights.sbomify.com/CVE-2012-1457/ Summaries are generated and may contain mistakes; the official description above is the record.