Service BridgeApplication · Lenovo

CVE-2019-6168

CRITICAL · 9.8 CVSS v3.1 Published 2019-06-26
Fix available
A fix is available. Upgrade to 4.1.0.1 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
A vulnerability reported in Lenovo Service Bridge before version 4.1.0.1 could allow remote code execution.

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

Lenovo Service Bridge versions prior to 4.1.0.1 contain a vulnerability that could allow remote code execution. The specific vulnerability type and attack vector are not detailed in the available description, but the critical CVSS score of 9.8 indicates the potential for complete system compromise without authentication.

MitigationUpgrade Lenovo Service Bridge to version 4.1.0.1 or later to remediate this vulnerability. Given the RCE capability at critical severity, also conduct forensic investigation to determine if any affected systems may have been compromised.

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
Service BridgeApplication
Affected:< 4.1.0.1

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. Check if Lenovo Service Bridge is installed
    Search for Lenovo Service Bridge in the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall, or check Add/Remove Programs
    Affected if Lenovo Service Bridge appears in the list of installed programs
  2. Find the installed version of Lenovo Service Bridge
    Examine the version field in the registry uninstall entry for Lenovo Service Bridge, or right-click the Service Bridge executable in its installation folder and select Properties to view the File Version
    Affected if Version information cannot be located or the software is found but version is not displayed
  3. Compare installed version against 4.1.0.1
    If a version number is found, compare it numerically to 4.1.0.1 - any version with a lower major, minor, or build number is below the fixed version
    Affected if Installed version is earlier than 4.1.0.1 (for example, 4.0.x, 3.x, or any version where the first three number groups are less than 4.1.0)
  4. Determine if the software is currently running
    Open Task Manager and look for Lenovo Service Bridge processes, or check running services with service name containing 'Lenovo' or 'Service Bridge'
    Affected if Lenovo Service Bridge process is actively running on the system

A system is affected if Lenovo Service Bridge is installed with any version prior to 4.1.0.1, as this creates the condition for the remote code execution vulnerability to be exploitable.

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 4.1.0.1 or later
Fixed in 4.1.0.1
Interim mitigation

Upgrade Lenovo Service Bridge to version 4.1.0.1 or later to remediate this vulnerability. Given the RCE capability at critical severity, also conduct forensic investigation to determine if any affected systems may have been compromised.

Recommended fix High confidence

Lenovo Service Bridge 4.1.0.1

  1. 1. Download Lenovo Service Bridge version 4.1.0.1 or later from the official Lenovo support website
  2. 2. Close any running instances of Lenovo Service Bridge
  3. 3. Uninstall the current version of Lenovo Service Bridge from the system
  4. 4. Install the downloaded version 4.1.0.1 or later
  5. 5. Verify the installed version matches 4.1.0.1 or higher

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

Fix this in Service Bridge Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,820
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,912.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-6168 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-6168 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