Osram Lightify Home prior 2016-07-26 Port 4000 Service Command missing authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.2 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Osram Lightify Home. Affected by this issue is some unknown functionality of the component Port 4000 Service. Performing a manipulation as part of Command results in missing authentication. This vulnerability is reported as CVE-2016-5053. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.
Details
A vulnerability, which was classified as critical, was found in Osram Lightify Home. This affects some unknown functionality of the component Port 4000 Service. The manipulation as part of a Command leads to a missing authentication vulnerability. CWE is classifying the issue as CWE-306. The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
OSRAM SYLVANIA Osram Lightify Home before 2016-07-26 allows remote attackers to execute arbitrary commands via TCP port 4000.
The bug was discovered 07/26/2016. The weakness was disclosed 04/10/2017 (Website). It is possible to read the advisory at community.rapid7.com. This vulnerability is uniquely identified as CVE-2016-5053 since 05/26/2016. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 257 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 2016-07-26 eliminates this vulnerability.It is possible to mitigate the weakness by firewalling tcp/4000. The best possible mitigation is suggested to be upgrading to the latest version.
The entries VDB-99505, VDB-99506, VDB-99508 and VDB-99509 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Missing authenticationCWE: CWE-306 / CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Lightify Home 2016-07-26
Firewalling: 🔍
Timeline
05/26/2016 🔍07/26/2016 🔍
04/09/2017 🔍
04/10/2017 🔍
04/10/2017 🔍
08/28/2020 🔍
Sources
Advisory: community.rapid7.comStatus: Not defined
CVE: CVE-2016-5053 (🔍)
GCVE (CVE): GCVE-0-2016-5053
GCVE (VulDB): GCVE-100-99507
OSVDB: - CVE-2016-5053 - OSRAM SYLVANIA - Lightify Home - Command Execution Issue
See also: 🔍
Entry
Created: 04/10/2017 09:53Updated: 08/28/2020 08:09
Changes: 04/10/2017 09:53 (60), 08/28/2020 08:09 (2)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.