# CVE-2014-100039: Denial of service in n/a

> Local attackers can crash Malwarebytes Anti-Exploit via a crafted IOCTL call, causing a denial of service.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jan 2015
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-8hxv-c53j-pffp

## What is CVE-2014-100039?

CVE-2014-100039 is a low-severity denial of service vulnerability in n/a, published on 13 Jan 2015. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

mbae.sys in Malwarebytes Anti-Exploit before 1.05.1.2014 allows local users to cause a denial of service (crash) via a crafted size in an unspecified IOCTL call, which triggers an out-of-bounds read.  NOTE: some of these details are obtained from third party information.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Malwarebytes Malwarebytes Anti-Exploit.

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

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

## Is CVE-2014-100039 being exploited?

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

Public exploit code:

- Malwarebytes Anti-Exploit 1.03.1.1220/1.04.1.1012 - Out-of-Bounds Read Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2014-4936](https://insights.sbomify.com/CVE-2014-4936/): Code injection in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-100039 is a low-severity denial of service vulnerability in n/a, published on 13 Jan 2015. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-100039 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-2014-100039/ (Markdown: https://insights.sbomify.com/CVE-2014-100039/index.md)
```

## Sources

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

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