How severe is CVE-2012-1430?

No CVSS score has been assigned to CVE-2012-1430 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2012-1430?

Affected package information for CVE-2012-1430 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2012-1430?

No fixed version has been published for CVE-2012-1430 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2012-1430 actively exploited in the wild?

No public exploit code has been indexed for CVE-2012-1430 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2012-1430?

CVE-2012-1430 has an EPSS (Exploit Prediction Scoring System) score of 96.1%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2012-1430?

CVE-2012-1430 is classified as CWE-264 (CWE-264). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2012-1430?

CVE-2012-1430 affects aladdin esafe (1 version, e.g. 7.0.17.0); bitdefender bitdefender (1 version, e.g. 7.2); comodo comodo antivirus (1 version, e.g. 7424); f-secure anti-virus (1 version, e.g. 9.0.16160.0), and 5 more product(s). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2012-1430 published, and has it been updated?

CVE-2012-1430 was published on March 21, 2012 and was last updated on April 29, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2012-1430: ESAFE CWE-264

EPSS Exploitation Probability

via FIRST.org ↗

96.1%probability of exploitation in next 30 days

Very High Risk100th percentile+95.57%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

The ELF file parser in Bitdefender 7.2, Comodo Antivirus 7424, eSafe 7.0.17.0, F-Secure Anti-Virus 9.0.16160.0, McAfee Anti-Virus Scanning Engine 5.400.0.1158, McAfee Gateway (formerly Webwasher) 2010.1C, nProtect Anti-Virus 2011-01-17.01, Sophos Anti-Virus 4.61.0, and Rising Antivirus 22.83.00.03 allows remote attackers to bypass malware detection via an ELF file with a \19\04\00\10 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 Products

9 products · 9 configurations

Application

esafealaddin

1 version

7.0.17.0

Application

bitdefenderbitdefender

1 version

7.2

Application

comodo antiviruscomodo

1 version

7424

Application

anti-virusf-secure

1 version

9.0.16160.0

Application

gatewaymcafee

1 version

2010.1c

Application

scan enginemcafee

1 version

5.400.0.1158

Frequently Asked Questions

The ELF file parser in Bitdefender 7.2, Comodo Antivirus 7424, eSafe 7.0.17.0, F-Secure Anti-Virus 9.0.16160.0, McAfee Anti-Virus Scanning Engine 5.400.0.1158, McAfee Gateway (formerly Webwasher) 2010.1C, nProtect Anti-Virus 2011-01-17.01, Sophos Anti-Virus 4.61.0, and Rising Antivirus 22.83.00.03 allows remote attackers to bypass malware detection via an ELF file with a \19\04\00\10 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 implementati

O3 Security · Impact-Aware SCA

Is CVE-2012-1430 in your stack?

O3 detects CVE-2012-1430 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works