# CVE-2012-1430: Security feature bypass in n/a

> Remote attackers can bypass malware detection in various antivirus products by crafting specific ELF files, allowing malicious code to evade scanning.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Mar 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-j5wp-v3hh-9w4j

## What is CVE-2012-1430?

CVE-2012-1430 is a medium-severity vulnerability in n/a, published on 21 Mar 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-264

## Which versions are affected by CVE-2012-1430?

It affects 9 products.


Products: Aladdin Esafe, Bitdefender Bitdefender, Comodo Comodo Antivirus, F-Secure Anti-Virus, Mcafee Gateway, Mcafee Scan Engine, Nprotect Nprotect Antivirus, Rising-Global Rising Antivirus, Sophos Sophos Anti-Virus.

## How do I fix CVE-2012-1430?

No fix has been published for CVE-2012-1430 yet. Limit exposure of the affected software until one is available.

## Is CVE-2012-1430 being exploited?

There is no known exploitation of CVE-2012-1430 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2008-5528](https://insights.sbomify.com/CVE-2008-5528/): Security feature bypass in n/a (critical 9.3)
- [CVE-2012-1429](https://insights.sbomify.com/CVE-2012-1429/): Security feature bypass in n/a (medium 4.3)
- [CVE-2012-1431](https://insights.sbomify.com/CVE-2012-1431/): Security feature bypass in n/a (medium 4.3)
- [CVE-2012-1432](https://insights.sbomify.com/CVE-2012-1432/): Security feature bypass in n/a (medium 4.3)
- [CVE-2012-1439](https://insights.sbomify.com/CVE-2012-1439/): Security feature bypass in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-1430 and fix it if it is affected.

What it is: CVE-2012-1430 is a medium-severity vulnerability in n/a, published on 21 Mar 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-1430 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2012-1430/ (Markdown: https://insights.sbomify.com/CVE-2012-1430/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2012-1430
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-1430
- OSV: https://osv.dev/vulnerability/CVE-2012-1430

---
From sbomify Insights: https://insights.sbomify.com/CVE-2012-1430/
Summaries are generated and may contain mistakes; the official description above is the record.