CVE-2018-8861
Last modified
CVE-2018-8861 is a vulnerability of currently unknown severity. Vulnerabilities within the Philips Brilliance CT kiosk environment (Brilliance 64 version 2.6.2 and prior, Brilliance iCT versions 4.1.6 and prior, Brillance iCT SP versions 3.2.4 and prior, and Brilliance CT Big Bore 2.3.5 and prior) could enable a limited-access kiosk user or an unauthorized attacker to break-out from the containment of the kiosk environment, attain elevated privileges from the underlying Windows OS, and access unauthorized resources from the operating system.. EPSS estimates a 0.41% chance of exploitation in the next 30 days.
Description
Vulnerabilities within the Philips Brilliance CT kiosk environment (Brilliance 64 version 2.6.2 and prior, Brilliance iCT versions 4.1.6 and prior, Brillance iCT SP versions 3.2.4 and prior, and Brilliance CT Big Bore 2.3.5 and prior) could enable a limited-access kiosk user or an unauthorized attacker to break-out from the containment of the kiosk environment, attain elevated privileges from the underlying Windows OS, and access unauthorized resources from the operating system.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Philips | Brilliance Firmware 64 | <= 2.6.2 |
| Philips | Brilliance Ict Sp Firmware | <= 3.2.4 |
| Philips | Brilliance Ict Firmware | <= 4.1.6 |
| Philips | Brilliance Ct Big Bore Firmware | <= 2.3.5 |
References
- http://www.securityfocus.com/bid/104088Third Party Advisory, VDB Entry
- https://ics-cert.us-cert.gov/advisories/ICSMA-18-123-01Third Party Advisory, US Government Resource
- http://www.securityfocus.com/bid/104088Third Party Advisory, VDB Entry
- https://ics-cert.us-cert.gov/advisories/ICSMA-18-123-01Third Party Advisory, US Government Resource
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2018-8861?
How severe is CVE-2018-8861?
How do I fix CVE-2018-8861?
Are you affected by CVE-2018-8861?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
