# CVE-2015-8252: Information disclosure in n/a

> Remote attackers can sniff cleartext serial numbers to derive hardcoded keys, compromising device security.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/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:** 27 Dec 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-f3pv-273r-pmfc

## What is CVE-2015-8252?

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

### Official description

The Frontel protocol before 3 on RSI Video Technologies Videofied devices sends a cleartext serial number, which allows remote attackers to determine a hardcoded key by sniffing the network and performing a "jumbled up" calculation with this number.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Rsi Video Technologies Frontel Protocol.

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

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

## Is CVE-2015-8252 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-8254](https://insights.sbomify.com/CVE-2015-8254/): Other in n/a (medium 5.9)
- [CVE-2015-8253](https://insights.sbomify.com/CVE-2015-8253/): Information disclosure in n/a (low 3.7)

## Fix prompt for AI coding agents

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

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

## Sources

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

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