Philips IntelliSpace Portal 7.0.x/8.0.x SSL Certificate cryptographic issue
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.4 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Philips IntelliSpace Portal 7.0.x/8.0.x and classified as critical. This impacts an unknown function of the component SSL Certificate Handler. This manipulation causes cryptographic issue. The identification of this vulnerability is CVE-2018-5466. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability has been found in Philips IntelliSpace Portal 7.0.x/8.0.x (Medical Device Software) and classified as critical. Affected by this vulnerability is an unknown part of the component SSL Certificate Handler. The manipulation with an unknown input leads to a cryptographic issue vulnerability. The CWE definition for the vulnerability is CWE-310. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Philips IntelliSpace Portal all versions of 8.0.x, and 7.0.x have a self-signed SSL certificate vulnerability this could allow an attacker to gain unauthorized access to resources and information.
The bug was discovered 02/27/2018. The weakness was shared 03/26/2018 (Website). The advisory is shared at usa.philips.com. This vulnerability is known as CVE-2018-5466 since 01/12/2018. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1600 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 27 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 103182†). The entries VDB-109655, VDB-114821, VDB-115070 and VDB-115071 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.philips.ch/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.4VulDB Meta Temp Score: 7.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
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: Cryptographic issueCWE: CWE-310
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
01/12/2018 🔍02/27/2018 🔍
02/27/2018 🔍
03/26/2018 🔍
03/26/2018 🔍
03/27/2018 🔍
01/16/2020 🔍
Sources
Vendor: philips.chAdvisory: usa.philips.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2018-5466 (🔍)
GCVE (CVE): GCVE-0-2018-5466
GCVE (VulDB): GCVE-100-115069
SecurityFocus: 103182 - Philips Intellispace Portal Multiple Security Vulnerabilities
See also: 🔍
Entry
Created: 03/27/2018 11:09Updated: 01/16/2020 21:14
Changes: 03/27/2018 11:09 (60), 01/16/2020 21:14 (4)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.