# CVE-2014-9642: Privilege escalation in n/a

> Local attackers can exploit a kernel driver flaw in BullGuard products to write to arbitrary memory and escalate privileges.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 6 Feb 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vwf9-jmrq-f5rf

## What is CVE-2014-9642?

CVE-2014-9642 is a high-severity vulnerability in n/a, published on 6 Feb 2015. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

bdagent.sys in BullGuard Antivirus, Internet Security, Premium Protection, and Online Backup before 15.0.288 allows local users to write data to arbitrary memory locations, and consequently gain privileges, via a crafted 0x0022405c IOCTL call.

Weakness: CWE-264

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

It affects 4 products.


Products: Bullguard Bdagent.sys, Bullguard Internet Security, Bullguard Online Backup, Bullguard Premium Protection.

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

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

## Is CVE-2014-9642 being exploited?

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

Public exploit code:

- BullGuard (Multiple Products) - Arbitrary Write Privilege Escalation (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-9642 is a high-severity vulnerability in n/a, published on 6 Feb 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-9642 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-9642/ (Markdown: https://insights.sbomify.com/CVE-2014-9642/index.md)
```

## Sources

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

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