# CVE-2016-5052: Security feature bypass in OSRAM SYLVANIA Osram Lightify Home through 2016-07-26

> The Osram Lightify Home app lacks SSL pinning, allowing attackers to intercept and manipulate traffic via man-in-the-middle attacks.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 10 Apr 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vpvm-wrg6-pmr4

## What is CVE-2016-5052?

CVE-2016-5052 is a high-severity vulnerability in OSRAM SYLVANIA Osram Lightify Home through 2016-07-26, published on 10 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OSRAM SYLVANIA Osram Lightify Home through 2016-07-26 does not use SSL pinning.

Weakness: CWE-254

## Which versions are affected by CVE-2016-5052?

It affects 1 product.


Products: Osram Lightify Home.

## How do I fix CVE-2016-5052?

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

## Is CVE-2016-5052 being exploited?

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

## Other vulnerabilities in OSRAM SYLVANIA Osram Lightify Home through 2016-07-26

- [CVE-2016-5053](https://insights.sbomify.com/CVE-2016-5053/): Command injection in OSRAM SYLVANIA Osram Lightify Home before 2016-07-26 (critical 9.8)
- [CVE-2016-5051](https://insights.sbomify.com/CVE-2016-5051/): Information disclosure in OSRAM SYLVANIA Osram Lightify Home before 2016-07-26 (high 7.5)
- [CVE-2016-5054](https://insights.sbomify.com/CVE-2016-5054/): Other in OSRAM SYLVANIA Osram Lightify Home through 2016-07-26 (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-5052 and fix it if it is affected.

What it is: CVE-2016-5052 is a high-severity vulnerability in OSRAM SYLVANIA Osram Lightify Home through 2016-07-26, published on 10 Apr 2017. 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-2016-5052 in the wild and no public exploit code.

Affected product: OSRAM SYLVANIA Osram Lightify Home through 2016-07-26. 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-2016-5052/ (Markdown: https://insights.sbomify.com/CVE-2016-5052/index.md)
```

## Sources

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

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