CVE-2018-5470
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 · uneditedPhilips IntelliSpace Portal all versions of 8.0.x, and 7.0.x have an unquoted search path or element vulnerability that has been identified, which may allow an authorized local user to execute arbitrary code and escalate their level of privileges.
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 · moderate confidencePhilips IntelliSpace Portal versions 7.0.x and 8.0.x contain an unquoted service path vulnerability. This occurs when Windows service or application paths containing spaces are not enclosed in quotes, allowing a local authenticated attacker to place a malicious executable earlier in the path hierarchy that gets executed in place of the intended binary, enabling privilege escalation.
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= 8.0= 9.0CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Check if Philips IntelliSpace Portal is installedLook for the application in Add/Remove Programs (appwiz.cpl) or check for the installation directory typically under C:\Program Files\Philips or C:\Program Files (x86)\PhilipsAffected if The application version is 7.0.x or 8.0.x (or 8.0, 9.0 per product list)
-
Identify Windows services associated with IntelliSpace PortalOpen Services (services.msc) and look for services with names containing 'Philips' or 'IntelliSpace Portal', or run 'sc queryex type= service state= all' and filter for Philips-related entriesAffected if Any Philips IntelliSpace Portal services exist on the system
-
Examine service binary paths for unquoted spacesFor each Philips service found, run 'sc qc <service_name>' to view the binary path, or use 'wmic service where "name like '%Philips%'" get name,pathname,startname' to list all paths. Check if the path contains spaces but is not enclosed in double quotesAffected if The service binary path contains one or more spaces and is NOT surrounded by quotes (e.g., C:\Program Files\Philips\app.exe is vulnerable; "C:\Program Files\Philips\app.exe" is not)
-
Verify write permissions on directories in the service pathFor each unquoted path identified, check write access to each directory in the path hierarchy using icacls (e.g., icacls "C:\Program Files\Philips"). Check if standard users or the attacker context has write permissions to parent directoriesAffected if Authenticated users have write access to any parent directory in the unquoted service path, allowing placement of a malicious executable
You are affected if Philips IntelliSpace Portal 7.0.x or 8.0.x is installed with Windows services that have unquoted binary paths containing spaces, and writable directories exist in that path hierarchy.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor-supplied security patches when available. In the interim, restrict write access to parent directories in the application path to prevent placement of malicious executables, and audit existing executables in those paths.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-5470 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-5470 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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