# CVE-2014-4936: Code injection in n/a

> Man-in-the-middle attackers can execute arbitrary code by spoofing the update server in Malwarebytes Anti-Malware and Anti-Exploit.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Dec 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-82fc-m9m7-w2mg

## What is CVE-2014-4936?

CVE-2014-4936 is a critical code injection vulnerability in n/a, published on 16 Dec 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The upgrade functionality in Malwarebytes Anti-Malware (MBAM) consumer before 2.0.3 and Malwarebytes Anti-Exploit (MBAE) consumer 1.04.1.1012 and earlier allow man-in-the-middle attackers to execute arbitrary code by spoofing the update server and uploading an executable.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2014-4936?

It affects 2 products.


Products: Malwarebytes Malwarebytes Anti-Exploit, Malwarebytes Malwarebytes Anti-Malware.

## How do I fix CVE-2014-4936?

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

## Is CVE-2014-4936 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2014-4936 exists.

Public exploit code:

- Repository for CVE-2014-4936 POC code. (github_poc): https://github.com/0x3a/CVE-2014-4936
- Malwarebytes Anti-Malware < 2.0.3 / Anti-Exploit < 1.03.1.1220 - Update Code Execution (Metasploit) (exploitdb)
- Malwarebytes Anti-Malware and Anti-Exploit Update Remote Code Execution (metasploit)

## Other vulnerabilities in n/a

- [CVE-2014-100039](https://insights.sbomify.com/CVE-2014-100039/): Denial of service in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-4936 and fix it if it is affected.

What it is: CVE-2014-4936 is a critical code injection vulnerability in n/a, published on 16 Dec 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2014-4936 exists.

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-2014-4936/ (Markdown: https://insights.sbomify.com/CVE-2014-4936/index.md)
```

## Sources

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

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