How severe is CVE-2012-1432?

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

Which packages are affected by CVE-2012-1432?

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

How do I fix CVE-2012-1432?

No fixed version has been published for CVE-2012-1432 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-1432 actively exploited in the wild?

No public exploit code has been indexed for CVE-2012-1432 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-1432?

CVE-2012-1432 has an EPSS (Exploit Prediction Scoring System) score of 93.5%, 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-1432?

CVE-2012-1432 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-1432?

CVE-2012-1432 affects aladdin esafe (1 version, e.g. 7.0.17.0); emsisoft anti-malware (1 version, e.g. 5.1.0.1); ikarus ikarus virus utilities t3 command line scanner (1 version, e.g. 1.1.97.0); pandasecurity panda antivirus (1 version, e.g. 10.0.2.7). Check the affected-products list on this page against your deployed version to confirm exposure.

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

CVE-2012-1432 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-1432: ESAFE CWE-264

EPSS Exploitation Probability

via FIRST.org ↗

93.5%probability of exploitation in next 30 days

Very High Risk100th percentile+87.91%

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 Microsoft EXE file parser in Emsisoft Anti-Malware 5.1.0.1, eSafe 7.0.17.0, Ikarus Virus Utilities T3 Command Line Scanner 1.1.97.0, and Panda Antivirus 10.0.2.7 allows remote attackers to bypass malware detection via an EXE file with a \57\69\6E\5A\69\70 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 EXE parser implementations.

Affected Products

4 products · 4 configurations

Application

esafealaddin

1 version

7.0.17.0

Application

anti-malwareemsisoft

1 version

5.1.0.1

Application

ikarus virus utilities t3 command line scannerikarus

1 version

1.1.97.0

Application

panda antiviruspandasecurity

1 version

10.0.2.7

Frequently Asked Questions

The Microsoft EXE file parser in Emsisoft Anti-Malware 5.1.0.1, eSafe 7.0.17.0, Ikarus Virus Utilities T3 Command Line Scanner 1.1.97.0, and Panda Antivirus 10.0.2.7 allows remote attackers to bypass malware detection via an EXE file with a \57\69\6E\5A\69\70 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 EXE parser implementations.

O3 Security · Impact-Aware SCA

Is CVE-2012-1432 in your stack?

O3 detects CVE-2012-1432 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