dbcve.org
Brilliance Firmware 64Operating system · Philips

CVE-2018-8861

HIGH · 8.7 CVSS v3.0 Published 2018-05-04
Fix available
A fix is available. Upgrade to after 4.1.6 or later.
See remediation →
89/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The vulnerability allows a limited-access kiosk user or unauthorized attacker to escape the containment of the Philips Brilliance CT kiosk environment, elevate privileges on the underlying Windows OS, and access unauthorized system resources.

MitigationApply vendor-provided patches from Philips for the Brilliance CT kiosk software; if patches are unavailable, implement compensating controls such as network segmentation, enhanced monitoring, and physical access restrictions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Brilliance Firmware 64Operating system
Affected:<= 2.6.2
Brilliance Ict Sp FirmwareOperating system
Affected:<= 3.2.4
Brilliance Ict FirmwareOperating system
Affected:<= 4.1.6
Brilliance Ct Big Bore FirmwareOperating system
Affected:<= 2.3.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
Low

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Philips Brilliance CT system
    Access the system information or service menu on the CT scanner. This is typically found in the service mode accessible via specific key combinations or credentials provided to service personnel. Look for system identification screens that display the device model.
    Affected if The system is not a Philips Brilliance CT scanner (the vulnerability only affects specific Brilliance models)
  2. Check Brilliance Firmware 64 version
    In the service menu, navigate to System Information or Firmware Version. Record the installed firmware version number. Compare against the affected range: version 2.6.2 and earlier.
    Affected if Firmware version is 2.6.2 or lower on Brilliance Firmware 64 systems
  3. Check Brilliance ICT SP Firmware version
    In the service menu, navigate to System Information or Firmware Version. Record the installed firmware version number. Compare against the affected range: version 3.2.4 and earlier.
    Affected if Firmware version is 3.2.4 or lower on Brilliance ICT SP systems
  4. Check Brilliance ICT Firmware version
    In the service menu, navigate to System Information or Firmware Version. Record the installed firmware version number. Compare against the affected range: version 4.1.6 and earlier.
    Affected if Firmware version is 4.1.6 or lower on Brilliance ICT systems
  5. Check Brilliance CT Big Bore Firmware version
    In the service menu, navigate to System Information or Firmware Version. Record the installed firmware version number. Compare against the affected range: version 2.3.5 and earlier.
    Affected if Firmware version is 2.3.5 or lower on Brilliance CT Big Bore systems
  6. Verify kiosk containment configuration
    If you have access to the Windows subsystem underlying the kiosk, check if the restricted Brilliance kiosk environment is enabled. This is typically visible in the Windows Control Panel under System or in the Philips service software. The vulnerability specifically allows escape from this kiosk mode.
    Affected if The kiosk mode containment is active (the privilege escalation occurs when escaping this kiosk environment)

A user is affected if they have a Philips Brilliance CT system running any of the four firmware versions at or below the specified thresholds and the kiosk containment environment is enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 4.1.6
Interim mitigation

Apply vendor-provided patches from Philips for the Brilliance CT kiosk software; if patches are unavailable, implement compensating controls such as network segmentation, enhanced monitoring, and physical access restrictions.

Fix this in Brilliance Firmware 64 Scoped from the published advisory
  • Consultation12.0 h
  • Implementation8.0 h
  • Testing16.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,288.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-8861 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-8861 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data