Read the docs
TI-2016-04375 Aliases CVE-2016-5057GHSA-hgqq-6c8m-cfcc

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

Priority LOW 35CWE-254Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
None · High · None
Fix status
No fix listed

Attack profile from CVSS 3.0 · NVD. Fix status from CNA.

Summary

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

Why it matters now

EPSS 0.01211 68th percentileScored 2026-11-07
Public exploit Yes 1 exploit referenceTagged by NVD
Fix No fix listed No fixed version in the sources yet

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—OSRAM SYLVANIA Osram Lightify Pro through 2016-07-26OSRAM SYLVANIA Osram Lightify Pro through 2016-07-26—No fix listedCNA
  • OSRAM SYLVANIA Osram Lightify Pro through 2016-07-26 Vendor— Affected OSRAM SYLVANIA Osram Lightify Pro through 2016-07-26 Fixed in — No fix listed CNA

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:osram:lightify_pro:*:*:*:*:*:*:*:*up to -VulnerableOsram
  • cpe:2.3:a:osram:lightify_pro:*:*:*:*:*:*:*:* Versions up to - Vulnerable ·Osram

Remediation

No fixed version listed by the sources yet.

Timeline

  1. 2026-10-02 Threatist record created from CVE-2016-5057
  2. 2026-10-03 Alias added: GHSA-hgqq-6c8m-cfcc

References

Exploit 1

  • TI-2016-04376 OSRAM SYLVANIA Osram Lightify Pro through 2016-07-26 allows Zigbee replay. CVSS 3.0HIGH 7.5
  • TI-2016-04374 OSRAM SYLVANIA Osram Lightify Pro before 2016-07-26 uses only 8 hex digits for a PSK. CVSS 3.0HIGH 7.5
  • TI-2016-04377 Information disclosure in OSRAM SYLVANIA Osram Lightify Pro before 2016-07-26 CVSS 3.0MEDIUM 6.5
  • TI-2016-04373 Cross-site scripting in OSRAM SYLVANIA Osram Lightify Pro before 2016-07-26 CVSS 3.0MEDIUM 6.1

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences