# CVE-2018-15885: Information disclosure in n/a

> Insufficient obfuscation in Ovation FindMe allows adversaries to detect covert operations and analyze software capabilities.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 26 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4pg5-xwrq-h998

## What is CVE-2018-15885?

CVE-2018-15885 is a high-severity vulnerability in n/a, published on 26 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Ovation FindMe 1.4-1083-1 is intended to support transmission of network traffic from covert video recorders but does not properly disrupt binary analysis for discovering the product's capabilities or purpose. This makes it easier for adversaries to detect the covert operation. Specifically, the product uses a compression technique to prevent the identification of certain libraries in the software by obfuscation. The software relies on a TLS callback and an additional executable file to enable these libraries and their access to certain websites. The unpacked software can be exploited by several different types of documented techniques.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2018-15885?

It affects 1 product.


Products: Ovation Findme.

## How do I fix CVE-2018-15885?

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

## Is CVE-2018-15885 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-15885 and fix it if it is affected.

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

## Sources

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

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