dbcve.org
Coronary ToolsApplication · Philips

CVE-2020-27298

MEDIUM · 6.5 CVSS v3.1 Published 2021-01-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
No privileges 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
Philips Interventional Workspot (Release 1.3.2, 1.4.0, 1.4.1, 1.4.3, 1.4.5), Coronary Tools/Dynamic Coronary Roadmap/Stentboost Live (Release 1.0), ViewForum (Release 6.3V1L10). The software constructs all or part of an OS command using externally influenced input from an upstream component but does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when sent to a downstream component.

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 confidence

Philips Interventional Workspot, Coronary Tools/Dynamic Coronary Roadmap/Stentboost Live, and ViewForum contain an OS command injection vulnerability where the software constructs OS commands using externally influenced input from upstream components without properly neutralizing special elements that could modify the intended command.

MitigationApply available patches or updates provided by Philips for the affected software releases (Interventional Workspot 1.3.2, 1.4.0, 1.4.1, 1.4.3, 1.4.5; Coronary Tools/Dynamic Coronary Roadmap/Stentboost Live 1.0; ViewForum 6.3V1L10). If patches are unavailable, implement network segmentation and access controls to limit exposure to untrusted upstream components.

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
Coronary ToolsApplication
Affected:= 1.0
Dynamic Coronary RoadmapApplication
Affected:= 1.0
Interventional WorkspotApplication
Affected:= 1.3.2= 1.4.0= 1.4.1= 1.4.3= 1.4.5
Stentboost LiveApplication
Affected:= 1.0
ViewforumApplication
Affected:= 6.3v1l10

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checks

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

  1. Identify installed Philips interventional software
    Check the Windows registry or installed programs list for Philips Interventional Workspot, Philips Coronary Tools, Philips Dynamic Coronary Roadmap, Philips Stentboost Live, or Philips ViewForum
    Affected if Any of these Philips products are installed on the system
  2. Determine installed version
    Open the application or check the program's About/Version information within the Philips software, or check the Windows registry under the installed product's registry key for the version string
    Affected if The version matches exactly: Interventional Workspot 1.3.2, 1.4.0, 1.4.1, 1.4.3, or 1.4.5; Coronary Tools 1.0; Dynamic Coronary Roadmap 1.0; Stentboost Live 1.0; or ViewForum 6.3V1L10
  3. Verify upstream component connectivity
    Review network configuration and check if the system accepts input from external or untrusted upstream components that could feed data into the Philips applications
    Affected if The system accepts network input from upstream components without strict validation controls
  4. Check for suspicious process behavior
    Monitor running processes for unusual command execution or unexpected spawning of OS commands originating from the Philips application processes
    Affected if The Philips software is spawning shell commands with unexpected or user-controlled parameters

A user is affected if they have any of the specific Philips products installed with versions 1.0, 1.3.2, 1.4.0, 1.4.1, 1.4.3, 1.4.5, or 6.3V1L10 and the system processes input from upstream components.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply available patches or updates provided by Philips for the affected software releases (Interventional Workspot 1.3.2, 1.4.0, 1.4.1, 1.4.3, 1.4.5; Coronary Tools/Dynamic Coronary Roadmap/Stentboost Live 1.0; ViewForum 6.3V1L10). If patches are unavailable, implement network segmentation and access controls to limit exposure to untrusted upstream components.

Fix this in Coronary Tools Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-27298 — 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-2020-27298 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