Vulnerability record · CVE-2012-1441 · published 21 March 2012
CVE-2012-1441: eSafe and Prevx EXE parser malware detection bypass
Aladdin · Esafe
The Microsoft EXE file parser in eSafe 7.0.17.0 and Prevx 3.0 can be evaded by an EXE file that carries a modified value in any of several e_ fields. Because the parser misreads the file, the security product fails to flag malicious content, so its core detection function is defeated. The record notes this may later be split into separate CVEs if the error proves independent across parser implementations.
Description
The Microsoft EXE file parser in eSafe 7.0.17.0 and Prevx 3.0 allows remote attackers to bypass malware detection via an EXE file with a modified value in any of several e_ fields. 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.
AV:N/AC:M/Au:N/C:N/I:P/A:N
Automated analysis
medium priorityThe flaw defeats malware detection but has only partial integrity impact (CVSS 4.3) and no confirmed in-the-wild exploitation, despite a high EPSS score.
What it is
The Microsoft EXE file parser in eSafe 7.0.17.0 and Prevx 3.0 can be evaded by an EXE file that carries a modified value in any of several e_ fields. Because the parser misreads the file, the security product fails to flag malicious content, so its core detection function is defeated. The record notes this may later be split into separate CVEs if the error proves independent across parser implementations.
Impact
An attacker can deliver a malicious EXE that the affected scanner treats as benign, allowing malware to reach the endpoint without being detected. The flaw only affects detection integrity; the CVSS vector shows no confidentiality or availability impact.
Attack surface
Reached remotely over the network by supplying a crafted EXE file to the scanning product; no authentication is required, though the CVSS temporal-style vector notes medium access complexity. No user interaction beyond handling the file is implied by the description.
Exploitation
Not listed in CISA KEV and no reference carries an exploit tag, but EPSS is 0.70282 (99.35th percentile), indicating a high modeled likelihood of exploitation activity. No public exploit details are provided in the record.
What to do
- Apply vendor updates for eSafe and Prevx if any are available; the record does not list fixed versions, so confirm with the vendor.
- Do not rely on the affected EXE parser as a sole detection layer; add independent endpoint and network inspection.
- Block or quarantine EXE attachments and downloads at the gateway where operationally feasible.
- Monitor vendor advisories for the possible CVE split, which may change affected product scope.
Detection
- Hunt for EXE files with unusual or malformed e_ field values reaching the mail or web gateway.
- Correlate scanner verdicts with sandbox or second-opinion engine results to find files the affected parser passed.
- Alert on EXE files that pass the affected product but are flagged by other engines.
This assessment is produced automatically and is not human-reviewed. Verify against the vendor advisory before acting on it.
Affected products
2 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
Track CVE-2012-1441 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2012-1441), CISA KEV, FIRST EPSS (scores of 2026-09-27). This page is refreshed as NVD updates the record.