dbcve.org
IpsfullhdApplication · Lg

CVE-2020-7807

MEDIUM · 5.5 CVSS v3.1 Published 2020-09-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
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
A vulnerability that can hijack a DLL file that is loaded during products(LGPCSuite_Setup, IPSFULLHD, LG_ULTRAWIDE, ULTRA_HD_Driver Setup) installation into a DLL file that the hacker wants. Missing Support for Integrity Check vulnerability in ____COMPONENT____ of LG Electronics (LGPCSuite_Setup), (IPSFULLHD, LG_ULTRAWIDE, ULTRA_HD_Driver Setup) allows ____ATTACKER/ATTACK____ to cause ____IMPACT____. This issue affects: LG Electronics; LGPCSuite_Setup : 1.0.0.3 on Windows(x86, x64); IPSFULLHD, LG_ULTRAWIDE, ULTRA_HD_Driver Setup : 1.0.0.9 on Windows(x86, x64).

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

This is a DLL hijacking vulnerability in LG Electronics installer software (LGPCSuite_Setup, IPSFULLHD, LG_ULTRAWIDE, ULTRA_HD_Driver Setup). During installation, the software loads DLL files without proper integrity verification or secure path validation, allowing attackers to place a malicious DLL in a location where the installer will load it instead of the legitimate DLL.

MitigationOrganizations should obtain these LG installers only from verified, official sources. The vendor should implement secure DLL loading mechanisms including explicit DLL path specification, digital signature verification, and removal of vulnerable DLL search paths.

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
IpsfullhdApplication
Affected:= 1.0.0.3
Lg UltrawideApplication
Affected:= 1.0.0.3
Lgpcsuite SetupApplication
Affected:= 1.0.0.9
Ultra Hd Driver SetupApplication
Affected:= 1.0.0.3

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
None
Integrity
High
Availability
None

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

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 installed LG installer software
    Search the system for the following LG installer programs: LGPCSuite_Setup, IPSFULLHD, LG_ULTRAWIDE, or ULTRA_HD_Driver Setup. Check Program Files directories, LG software folders, or use system search tools to locate these executables.
    Affected if Any of these LG installer executables exist on the system with the vulnerable versions listed below
  2. Check LG Ipsfullhd version
    Right-click on the IPSFULLHD installer executable, select Properties, and examine the File Version field under the Details tab.
    Affected if The file version equals exactly 1.0.0.3
  3. Check LG Ultrawide version
    Right-click on the LG_ULTRAWIDE installer executable, select Properties, and examine the File Version field under the Details tab.
    Affected if The file version equals exactly 1.0.0.3
  4. Check LGPCSuite Setup version
    Right-click on the LGPCSuite_Setup installer executable, select Properties, and examine the File Version field under the Details tab.
    Affected if The file version equals exactly 1.0.0.9
  5. Check Ultra HD Driver Setup version
    Right-click on the ULTRA_HD_Driver Setup installer executable, select Properties, and examine the File Version field under the Details tab.
    Affected if The file version equals exactly 1.0.0.3

The environment is affected if any of the four LG installer programs (IPSFULLHD, LG_ULTRAWIDE, LGPCSuite_Setup, or ULTRA_HD_Driver Setup) are present with the exact version numbers 1.0.0.3 or 1.0.0.9.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Organizations should obtain these LG installers only from verified, official sources. The vendor should implement secure DLL loading mechanisms including explicit DLL path specification, digital signature verification, and removal of vulnerable DLL search paths.

Fix this in Ipsfullhd Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA8.0 h
52.0 hours of engineering $9,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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