dbcve.org
Unified Communication \& Collaboration ClientApplication · Starface

CVE-2020-10515

CRITICAL · 9.8 CVSS v3.1 Published 2020-04-02
Fix available
A fix is available. Upgrade to 6.7.1.204 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
STARFACE UCC Client before 6.7.1.204 on WIndows allows binary planting to execute code with System rights, aka usd-2020-0006.

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

The STARFACE UCC Client before version 6.7.1.204 on Windows contains a binary planting vulnerability that allows an attacker to place a malicious executable in a location where it will be loaded by the application, executing with System-level privileges. This gives the attacker full control over the affected system.

MitigationUpgrade STARFACE UCC Client to version 6.7.1.204 or later to remediate the binary planting vulnerability. Given the System-level execution privilege, also conduct forensic investigation to determine if exploitation occurred prior to patching.

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
Unified Communication \& Collaboration ClientApplication
Affected:< 6.7.1.204

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
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 checks

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

  1. Identify STARFACE UCC Client installation
    Check the Windows system for STARFACE UCC Client installation. Look in Add/Remove Programs (appwiz.cpl), or search for 'STARFACE' in Program Files directories, or check for STARFACE-related services running on the system.
    Affected if STARFACE UCC Client is found installed on the system
  2. Retrieve the installed version number
    Locate the STARFACE UCC Client executable (typically named like 'STARFACE.exe' or similar) and view its file properties (right-click > Properties > Details) to find the Product Version, or use command-line tools like 'wmic product where "name like '%STARFACE%'" get version' to query installed software.
    Affected if The version retrieved is below 6.7.1.204
  3. Confirm vulnerability applicability
    Verify that the installation is on Windows (the CVE specifically mentions Windows) and that it is a client/installation that loads executable components at runtime.
    Affected if The software is the STARFACE UCC Client for Windows and the version is below 6.7.1.204
  4. Check for unexpected executables
    As a secondary indicator, scan the STARFACE application directory and adjacent directories (especially writable locations) for unknown or suspicious .exe files that may have been placed as part of a binary planting attack.
    Affected if Unexpected or unknown executable files are found in STARFACE installation directories

The environment is affected if STARFACE UCC Client for Windows is installed with a version number lower than 6.7.1.204, as this is the specific version range in which the binary planting vulnerability exists.

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.

dbcve · scoped
Upgrade available Upgrade to 6.7.1.204 or later
Fixed in 6.7.1.204
Interim mitigation

Upgrade STARFACE UCC Client to version 6.7.1.204 or later to remediate the binary planting vulnerability. Given the System-level execution privilege, also conduct forensic investigation to determine if exploitation occurred prior to patching.

Recommended fix Moderate confidence

6.7.1.204 or later

  1. 1. Verify the current version of STARFACE UCC Client by opening the application and navigating to Help > About or checking the installed programs list
  2. 2. Download the latest STARFACE UCC Client version 6.7.1.204 or later from the official vendor website (support.starface.de or www.starface.com)
  3. 3. Close the STARFACE UCC Client completely before upgrading
  4. 4. Run the installer with administrator privileges
  5. 5. Follow the on-screen installation wizard prompts to complete the upgrade
  6. 6. Restart the system if prompted by the installer
  7. 7. Verify the new version is installed by checking Help > About in the application

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Unified Communication \& Collaboration Client Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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