# CVE-2015-2078: Security feature bypass in n/a

> Man-in-the-middle attackers can spoof SSL servers due to improper X.509 certificate verification in the Komodia Redirector SDK.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Feb 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-q8jw-gpmq-9hhm

## What is CVE-2015-2078?

CVE-2015-2078 is a medium-severity vulnerability in n/a, published on 24 Feb 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The SDK for Komodia Redirector with SSL Digestor, as used in Lavasoft Ad-Aware Web Companion 1.1.885.1766 and Ad-Aware AdBlocker (alpha) 1.3.69.1, Qustodio for Windows, Atom Security, Inc. StaffCop 5.8, and other products, does not properly verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers, a different vulnerability than CVE-2015-2077.

Weakness: CWE-310

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

It affects 1 product.


Products: Komodia Redirector Sdk.

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

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

## Is CVE-2015-2078 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-2077](https://insights.sbomify.com/CVE-2015-2077/): Hardcoded credentials in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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