# CVE-2015-2096: Use after free in n/a

> Remote attackers can execute arbitrary code via a use-after-free vulnerability in the WebGate eDVR Manager ActiveX control requiring user interaction.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Mar 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-wf56-xf2j-qq37

## What is CVE-2015-2096?

CVE-2015-2096 is a medium-severity use after free vulnerability in n/a, published on 9 Mar 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Use-after-free vulnerability in the Connect function in the WESPMonitor.WESPMonitorCtrl.1 ActiveX control in WebGate eDVR Manager allows remote attackers to execute arbitrary code via an invalid IP address and a page reload.

## Which versions are affected by CVE-2015-2096?

It affects 1 product.


Products: Webgateinc Edvr Manager.

## How do I fix CVE-2015-2096?

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

## Is CVE-2015-2096 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-2098](https://insights.sbomify.com/CVE-2015-2098/): Memory corruption in n/a (high 8.8)
- [CVE-2015-2095](https://insights.sbomify.com/CVE-2015-2095/): Memory corruption in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-2096 and fix it if it is affected.

What it is: CVE-2015-2096 is a medium-severity use after free vulnerability in n/a, published on 9 Mar 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2015-2096 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-2015-2096/ (Markdown: https://insights.sbomify.com/CVE-2015-2096/index.md)
```

## Sources

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

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