CVE-2021-27497
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 Vue PACS versions 12.2.x.x and prior does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.
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 Vue PACS versions 12.2.x.x and prior contains a vulnerability where a protection mechanism is either not used or incorrectly implemented, leaving the system insufficiently defended against directed attacks. The CVSS 9.8 indicates this is a network-exploitable, easily exploitable flaw in a medical imaging system that handles sensitive patient data.
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< 12.2.1.5< 12.2.8.0< 12.2.1.5< 12.2.8.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify installed Philips productCheck the system for installed Philips imaging products: look for Philips Myvue, Philips Speech, Philips Vue Motion, or Philips Vue PACS in installed programs (Windows Add/Remove Programs), application directories, or running servicesAffected if Any of these four products are installed on the system
-
Determine installed product versionLocate the version information for the installed Philips product. Check the application's About/Info dialog, or look in the installation directory for version files, or query the Windows registry under HKLM\SOFTWARE\Philips for version keysAffected if The version cannot be determined or is lower than the affected ranges
-
Compare version against affected rangesCompare your installed version to the affected ranges: Myvue < 12.2.1.5, Speech < 12.2.8.0, Vue Motion < 12.2.1.5, Vue PACS < 12.2.8.0Affected if Installed version falls within any of these ranges: Myvue < 12.2.1.5, Speech < 12.2.8.0, Vue Motion < 12.2.1.5, Vue PACS < 12.2.8.0
-
Verify network accessibilityCheck if the Philips PACS service is exposed to the network by reviewing firewall rules, listening ports (typical PACS ports: 104, 11112, 5000-5999 range), and network configurationAffected if The affected product version is running and the service port is accessible from network segments outside the local medical device VLAN
You are affected if any Philips Myvue, Speech, Vue Motion, or Vue PACS version is installed that is below the thresholds (12.2.1.5 or 12.2.8.0 depending on product) AND the system is network-accessible.
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.
dbcve · scoped12.2.1.512.2.8.0
Apply the vendor patch or update Philips Vue PACS to a version beyond 12.2.x.x as specified in Philips security advisory. If patches are unavailable, implement compensating controls such as network segmentation, strict access controls, and monitoring.
Myvue: 12.2.1.5 | Speech: 12.2.8.0 | Vue Motion: 12.2.1.5 | Vue PACS: 12.2.8.0
- Identify which Philips Vue product(s) are in use (Myvue, Speech, Vue Motion, or Vue PACS)
- Check the current version of each affected product
- For Myvue: upgrade to version 12.2.1.5 or later
- For Speech: upgrade to version 12.2.8.0 or later
- For Vue Motion: upgrade to version 12.2.1.5 or later
- For Vue PACS: upgrade to version 12.2.8.0 or later
- After upgrade, verify the installed version matches the target fixed release
- Consult Philips official security advisory for any additional post-upgrade configuration requirements
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-27497 — 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-2021-27497 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