dbcve.org
BridgeApplication · Lg

CVE-2019-20781

HIGH · 7.8 CVSS v3.1 Published 2020-04-29
Fix available
A fix is available. Upgrade to 2019-04 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
An issue was discovered in LG Bridge before April 2019 on Windows. DLL Hijacking can occur.

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 · high confidence

LG Bridge software before April 2019 on Windows is vulnerable to DLL hijacking, where a local attacker can place a malicious DLL in a location from which the application loads a library, leading to arbitrary code execution with the privileges of the running user.

MitigationUpdate LG Bridge to the April 2019 release or later. Ensure the software is obtained from official LG sources and verify the digital signature of the installer.

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
BridgeApplication
Affected:< 2019-04

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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. Find LG Bridge installation directory
    Search for 'LG Bridge' in Program Files or Program Files (x86) folders, or use the Windows search feature to locate the lgbridge.exe executable
    Affected if LG Bridge is not installed on the system (not affected)
  2. Locate the LG Bridge executable version
    Right-click on lgbridge.exe, select Properties, and check the Details tab for the File Version or Product Version field
    Affected if The displayed version is earlier than the April 2019 release (e.g., any 2019-xx version prior to April, or any 2018-xx version)
  3. Check LG Bridge version via command line
    Open Command Prompt and run 'wmic product where "name like '%LG Bridge%'" get version,name' or navigate to the installation folder and run 'lgbridge.exe -version' if supported
    Affected if The returned version string indicates a build prior to the April 2019 release
  4. Verify installation date from Windows features
    Open Control Panel > Programs and Features, find LG Bridge in the list, and check the 'Installed On' date column
    Affected if The installation date is before April 2019, indicating an affected version is likely installed

If LG Bridge is installed and its version or installation date predates the April 2019 release, the system is vulnerable to this DLL hijacking flaw.

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
Upgrade available Upgrade to 2019-04 or later
Fixed in 2019-04
Interim mitigation

Update LG Bridge to the April 2019 release or later. Ensure the software is obtained from official LG sources and verify the digital signature of the installer.

Fix this in Bridge Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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