CVE-2020-14477 Vulnerability Analysis & Exploit Details

CVE-2020-14477
Vulnerability Scoring

4.4
/10
Medium Risk

The vulnerability CVE-2020-14477 could compromise system integrity but typically requires user interaction to be exploited.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Local
    Vulnerability requires local system access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2020-14477 Details

Status: Analyzed

Last updated: 🕓 15 Jul 2020, 16:15 UTC
Originally published on: 🕔 26 Jun 2020, 17:15 UTC

Time between publication and last update: 18 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

CVE-2020-14477 Vulnerability Summary

CVE-2020-14477: In Philips Ultrasound ClearVue Versions 3.2 and prior, Ultrasound CX Versions 5.0.2 and prior, Ultrasound EPIQ/Affiniti Versions VM5.0 and prior, Ultrasound Sparq Version 3.0.2 and prior and Ultrasound Xperius all versions, an attacker may use an alternate path or channel that does not require authentication of the alternate service login to view or modify information.

Assessing the Risk of CVE-2020-14477

Access Complexity Graph

The exploitability of CVE-2020-14477 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2020-14477

CVE-2020-14477 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2020-14477, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2020-14477, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: Low
    CVE-2020-14477 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: Low
    Exploiting CVE-2020-14477 may cause minor changes to data without severely impacting its accuracy.
  • Availability: None
    CVE-2020-14477 does not impact system availability.

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.044% (probability of exploit)

EPSS Percentile: 13.01% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 86.99% of others.

CVE-2020-14477 References

External References

CWE Common Weakness Enumeration

CWE-288

CAPEC Common Attack Pattern Enumeration and Classification

  • Directory Indexing CAPEC-127 An adversary crafts a request to a target that results in the target listing/indexing the content of a directory as output. One common method of triggering directory contents as output is to construct a request containing a path that terminates in a directory name rather than a file name since many applications are configured to provide a list of the directory's contents when such a request is received. An adversary can use this to explore the directory tree on a target as well as learn the names of files. This can often end up revealing test files, backup files, temporary files, hidden files, configuration files, user accounts, script contents, as well as naming conventions, all of which can be used by an attacker to mount additional attacks.
  • Exploitation of Thunderbolt Protection Flaws CAPEC-665 An adversary leverages a firmware weakness within the Thunderbolt protocol, on a computing device to manipulate Thunderbolt controller firmware in order to exploit vulnerabilities in the implementation of authorization and verification schemes within Thunderbolt protection mechanisms. Upon gaining physical access to a target device, the adversary conducts high-level firmware manipulation of the victim Thunderbolt controller SPI (Serial Peripheral Interface) flash, through the use of a SPI Programing device and an external Thunderbolt device, typically as the target device is booting up. If successful, this allows the adversary to modify memory, subvert authentication mechanisms, spoof identities and content, and extract data and memory from the target device. Currently 7 major vulnerabilities exist within Thunderbolt protocol with 9 attack vectors as noted in the Execution Flow.

Vulnerable Configurations

  • cpe:2.3:h:philips:clearvue_850:-:*:*:*:*:*:*:*
    cpe:2.3:h:philips:clearvue_850:-:*:*:*:*:*:*:*
  • cpe:2.3:o:philips:clearvue_850_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:philips:clearvue_850_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:philips:clearvue_850_firmware:3.2:*:*:*:*:*:*:*
    cpe:2.3:o:philips:clearvue_850_firmware:3.2:*:*:*:*:*:*:*
  • cpe:2.3:h:philips:clearvue_350:-:*:*:*:*:*:*:*
    cpe:2.3:h:philips:clearvue_350:-:*:*:*:*:*:*:*
  • cpe:2.3:o:philips:clearvue_350_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:philips:clearvue_350_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:philips:clearvue_350_firmware:3.2:*:*:*:*:*:*:*
    cpe:2.3:o:philips:clearvue_350_firmware:3.2:*:*:*:*:*:*:*
  • cpe:2.3:h:philips:cx50:-:*:*:*:*:*:*:*
    cpe:2.3:h:philips:cx50:-:*:*:*:*:*:*:*
  • cpe:2.3:o:philips:cx50_firmware:5.0.2:*:*:*:*:*:*:*
    cpe:2.3:o:philips:cx50_firmware:5.0.2:*:*:*:*:*:*:*
  • cpe:2.3:h:philips:affiniti_70:-:*:*:*:*:*:*:*
    cpe:2.3:h:philips:affiniti_70:-:*:*:*:*:*:*:*
  • cpe:2.3:o:philips:affiniti_70_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:philips:affiniti_70_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:philips:affiniti_70_firmware:5.0:*:*:*:*:*:*:*
    cpe:2.3:o:philips:affiniti_70_firmware:5.0:*:*:*:*:*:*:*
  • cpe:2.3:h:philips:affiniti_50:-:*:*:*:*:*:*:*
    cpe:2.3:h:philips:affiniti_50:-:*:*:*:*:*:*:*
  • cpe:2.3:o:philips:affiniti_50_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:philips:affiniti_50_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:philips:affiniti_50_firmware:5.0:*:*:*:*:*:*:*
    cpe:2.3:o:philips:affiniti_50_firmware:5.0:*:*:*:*:*:*:*
  • cpe:2.3:h:philips:epiq_7:-:*:*:*:*:*:*:*
    cpe:2.3:h:philips:epiq_7:-:*:*:*:*:*:*:*
  • cpe:2.3:o:philips:epiq_7_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:philips:epiq_7_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:philips:epiq_7_firmware:5.0:*:*:*:*:*:*:*
    cpe:2.3:o:philips:epiq_7_firmware:5.0:*:*:*:*:*:*:*
  • cpe:2.3:h:philips:sparq:-:*:*:*:*:*:*:*
    cpe:2.3:h:philips:sparq:-:*:*:*:*:*:*:*
  • cpe:2.3:o:philips:sparq_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:philips:sparq_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:philips:sparq_firmware:3.0.2:*:*:*:*:*:*:*
    cpe:2.3:o:philips:sparq_firmware:3.0.2:*:*:*:*:*:*:*
  • cpe:2.3:h:philips:xperius:-:*:*:*:*:*:*:*
    cpe:2.3:h:philips:xperius:-:*:*:*:*:*:*:*
  • cpe:2.3:o:philips:xperius_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:philips:xperius_firmware:*:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2020-14477: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-3275 – The Themesflat Addons For Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the TF E Slider widget in all versions up...
  • CVE-2025-1457 – The Element Pack Addons for Elementor – Free Templates and Widgets for Your WordPress Websites plugin for WordPress is vulnerable to Stored Cross-S...
  • CVE-2025-1093 – The AIHub theme for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the generate_image function in all ver...
  • CVE-2025-3284 – The User Registration & Membership – Custom Registration Form, Login Form, and User Profile plugin for WordPress is vulnerable to Cross-Site Reques...
  • CVE-2025-3278 – The UrbanGo Membership plugin for WordPress is vulnerable to privilege escalation in versions up to, and including, 1.0.4. This is due to the plugi...