# CVE-2015-0935: Deserialization in n/a

> Remote attackers can execute arbitrary PHP code in Bomgar Remote Support via crafted serialized data, requiring an upgrade to secure the system.

- **Severity:** High 7.5 (`AV:N/AC:L/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:** Not needed
- **Fix available:** No
- **Published:** 25 May 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-68pw-2wmh-cpr9

## What is CVE-2015-0935?

CVE-2015-0935 is a high-severity unsafe deserialization vulnerability in n/a, published on 25 May 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Bomgar Remote Support before 15.1.1 allows remote attackers to execute arbitrary PHP code via crafted serialized data to unspecified PHP scripts.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Bomgar Remote Support.

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

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

## Is CVE-2015-0935 being exploited?

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

Public exploit code:

- Bomgar Remote Support - Code Execution (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2017-12815](https://insights.sbomify.com/CVE-2017-12815/): Path traversal in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-0935 is a high-severity unsafe deserialization vulnerability in n/a, published on 25 May 2015. 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-2015-0935 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-0935/ (Markdown: https://insights.sbomify.com/CVE-2015-0935/index.md)
```

## Sources

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

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