CVE-2020-6786
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 Video Recording Manager installer up to and including version 3.82.0055 for 3.82, up to and including version 3.81.0064 for 3.81 and 3.71 and older 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 Video Recording Manager installer is vulnerable to DLL hijacking (uncontrolled search path element). An attacker can place a malicious DLL in the same directory as the installer, and the installer will load and execute it with elevated privileges when the victim runs the installer. This affects versions up to 3.82.0055 (3.82 branch), 3.81.0064 (3.81 and 3.71 branches), and older versions.
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<= 3.71>= 3.81, <= 3.81.0064>= 3.82, <= 3.82.0055CVSS 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 the Bosch Video Recording Manager installerSearch the system for installer files named 'Video_Recording_Manager' or similar, or check download folders and installation media where the installer may be stored. Common locations include user download folders, shared network drives, or installation media.Affected if The installer file exists on the system in any location.
-
Identify the installer versionRight-click the installer executable, select Properties, and look at the Version tab or Details section to find the product version number. Alternatively, run the installer with /? or check any accompanying version info files.Affected if The version displayed is within the affected ranges: <= 3.71, 3.81.0000 through 3.81.0064, or 3.82.0000 through 3.82.0055.
-
Determine the installer locationCheck the full path of the installer file by viewing its properties or using the file explorer address bar. Note whether the installer resides in a shared/network folder, USB drive, or other location accessible to untrusted parties.Affected if The installer is located in a directory that could be writeable by untrusted users, such as shared folders, download directories, or removable media.
-
Check for recently created DLLs in the installer directoryOpen the folder containing the installer and sort files by creation date. Look for any DLL files created around the same time as or after the installer that were not part of the original installation package.Affected if Unexpected DLL files exist in the same directory as the installer, especially if their timestamps suggest they were placed there recently.
A user is affected if they have a Bosch Video Recording Manager installer with a version within 3.71 and below, 3.81.0000-3.81.0064, or 3.82.0000-3.82.0055, particularly if the installer is stored in an accessible or shared location.
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 dataUpdate the Bosch Video Recording Manager installer to the latest patched version which implements secure DLL loading or uses safe DLL search mode to prevent loading from the current directory. Users should never run installers from untrusted or shared locations.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6786 — 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-6786 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