CVE-2012-1429: Medium severity aladdin esafe vulnerability

Published Mar 21, 2012
·
Updated

The ELF file parser in Bitdefender 7.2, Comodo Antivirus 7424, Emsisoft Anti-Malware 5.1.0.1, eSafe 7.0.17.0, F-Secure Anti-Virus 9.0.16160.0, Ikarus Virus Utilities T3 Command Line Scanner 1.1.97.0, McAfee Anti-Virus Scanning Engine 5.400.0.1158, McAfee Gateway (formerly Webwasher) 2010.1C, and nProtect Anti-Virus 2011-01-17.01 allows remote attackers to bypass malware detection via an ELF file with a ustar character sequence at a certain location. NOTE: this may later be SPLIT into multiple CVEs if additional information is published showing that the error occurred independently in different ELF parser implementations.

Affected Software

9 affected components
Aladdin eSafe=7.0.17.0
Comodo Comodo Antivirus=7424
Emsisoft Anti-Malware=5.1.0.1
F-Secure F-Secure anti-virus=9.0.16160.0
Ikarus Ikarus Virus Utilities T3 Command Line Scanner=1.1.97.0
McAfee Gateway=2010.1c
McAfee Scan Engine=5.400.0.1158
nProtect Nprotect Antivirus=2011-01-17.01
Softwin Bitdefender=7.2

Event History

Mar 21, 2012
CVE Published
via MITRE·10:00 AM
Data Sourced
via MITRE·10:00 AM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2012-1429?

CVE-2012-1429 has been classified as a moderate severity vulnerability affecting multiple antivirus software products.

2

How do I fix CVE-2012-1429?

To fix CVE-2012-1429, update your antivirus software to the latest version provided by the vendor.

3

Which antivirus products are affected by CVE-2012-1429?

CVE-2012-1429 affects several antivirus products including Bitdefender 7.2, Comodo Antivirus 7424, and McAfee Anti-Virus Scanning Engine 5.400.0.1158.

4

Is there a workaround for CVE-2012-1429?

While the primary solution is to update your antivirus, temporarily disabling the affected software can serve as a workaround until a fix is applied.

5

When was CVE-2012-1429 disclosed?

CVE-2012-1429 was disclosed in the year 2012, specifically during the IEEE Security and Privacy Conference.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203