CVE-2012-1429
No exploitation reported yet. Patch in your normal cycle; we flag it the day exploitation starts.
What it is
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.
Live exploitation on the huntback network (30 days)
Detection
Evidence
No exploitation known. EPSS puts the chance of exploitation in the next 30 days at 92%.
Published
Observed: our own decoys saw it. Reported: CISA, the vendor or another named source says so. Weaponised: public exploit code or a scanner template exists. Methodology
Questions
Is CVE-2012-1429 being exploited in the wild?
Not on our sensors so far: the huntback decoy network has not captured an exploitation attempt, and it is not in the CISA KEV catalogue.
Can CVE-2012-1429 be detected on the network?
huntback has no wire signature for CVE-2012-1429 yet; it may need local or authenticated access to exploit.
How huntback helps
Deploy a decoy that emulates Anti-malware and you will see every attempt at this CVE the moment it lands, with the full payload, the attacker's infrastructure, and any stage-2 loader. Then huntback can scan the attacker back.
Related
NVD record → Browse all CVEs → Live malware and C2 finds → Novel-attack discovery → Deploy a decoy →API
This record, with its evidence timeline, as JSON:
curl -H "X-API-Key: $HUNTBACK_KEY" https://app.huntback.io/api/v1/evidence/CVE-2012-1429