CVE-2020-6789
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 · uneditedLoading a DLL through an Uncontrolled Search Path Element in the Bosch Monitor Wall installer up to and including version 10.00.0164 potentially allows an attacker to execute arbitrary code on a victim's system. A prerequisite is that the victim is tricked into placing a malicious DLL in the same directory where the installer is started from.
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 confidenceThe Bosch Monitor Wall installer up to v10.00.0164 suffers from an uncontrolled search path element vulnerability (CWE-427). When the installer runs, it loads DLLs from the current working directory without validating the path, allowing an attacker to place a malicious DLL with the same name as a required library in the same directory as the installer. If a victim is tricked into placing this DLL and running the installer, arbitrary code executes with the privileges of the user running 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<= 10.00.0164CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate Bosch Monitor Wall installationCheck common installation directories such as C:\Program Files\Bosch\Monitor Wall or C:\Program Files (x86)\Bosch\Monitor Wall. Also check Program Files for any folder starting with 'Bosch'.Affected if The software is found in any of these locations
-
Identify installed versionCheck the version of the installed Monitor Wall software. In the installation folder, look for version information in the file properties of the main executable, or check Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'Monitor Wall' or similar Bosch product.Affected if The installed version is 10.00.0164 or earlier
-
Locate the installer executableSearch for installer files named like 'MonitorWall*.exe', 'Setup*.exe', or 'Install*.exe' in user download folders, desktop, or installation media. Check the file properties to identify the version embedded in the installer.Affected if The installer version is 10.00.0164 or earlier
-
Verify DLL search path vulnerabilityThis vulnerability requires the installer to be run from a directory where a malicious DLL could be placed. The check is whether the installed version is within the affected range, as the installer loads DLLs from the current working directory without path validation.Affected if The installed version or installer version is 10.00.0164 or earlier and the software was potentially installed using an installer from an untrusted source
A user is affected if Bosch Monitor Wall version 10.00.0164 or earlier is installed, as the installer contains an uncontrolled search path element allowing DLL hijacking from the current working directory.
Generated from the published advisory. Verify against your own configuration.
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 dataVendors should implement secure DLL loading by using full absolute paths for all DLL dependencies, calling SetDllDirectory("") to disable the current directory DLL search, and/or using Safe DLL Search Mode. Users should ensure they download installers only from trusted sources and verify file integrity before execution.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6789 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-6789 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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