dbcve.org
Video Streaming GatewayApplication · Bosch

CVE-2020-6769

CRITICAL · 9.1 CVSS v3.1 Published 2020-02-07
Fix available
A fix is available. Upgrade to after 6.45.08 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
Missing Authentication for Critical Function in the Bosch Video Streaming Gateway (VSG) allows an unauthenticated remote attacker to retrieve and set arbitrary configuration data of the Video Streaming Gateway. A successful attack can impact the confidentiality and availability of live and recorded video data of all cameras configured to be controlled by the VSG as well as the recording storage associated with the VSG. This affects Bosch Video Streaming Gateway versions 6.45 <= 6.45.08, 6.44 <= 6.44.022, 6.43 <= 6.43.0023 and 6.42.10 and older. This affects Bosch DIVAR IP 3000, DIVAR IP 7000 and DIVAR IP all-in-one 5000 if a vulnerable VSG version is installed with BVMS. This affects Bosch DIVAR IP 2000 <= 3.62.0019 and DIVAR IP 5000 <= 3.80.0039 if the corresponding port 8023 has been opened in the device's firewall.

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
How this class of weakness works · CWE-306

A sensitive function is reachable with no authentication at all, so anyone who finds the endpoint can use it. These are routinely discovered by automated scanning. The fix is to require and enforce authentication on every privileged path, with no exceptions left open.

General guidance for the missing authentication class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
Video Streaming GatewayApplication
Affected:<= 6.42.10>= 6.43, <= 6.43.0023>= 6.44, <= 6.44.022>= 6.45, <= 6.45.08
Divar Ip 2000 FirmwareOperating system
Affected:<= 3.62.0019
Divar Ip 5000 FirmwareOperating system
Affected:<= 3.80.0039

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

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

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 a release after 6.45.08
Vendor patch psirt.bosch.com →
Recommended fix Moderate confidence

Video Streaming Gateway: 6.45.09+ (or latest stable); DIVAR IP 2000: 3.62.0020+; DIVAR IP 5000: 3.80.0040+

  1. 1. Identify the current installed version of Bosch Video Streaming Gateway (VSG) or DIVAR IP firmware
  2. 2. For Video Streaming Gateway: Upgrade to version 6.45.09 or later (or the latest available stable version)
  3. 3. For DIVAR IP 2000: Upgrade to firmware version 3.62.0020 or later
  4. 4. For DIVAR IP 5000: Upgrade to firmware version 3.80.0040 or later
  5. 5. After upgrade, verify the vulnerability is remediated by confirming the authentication mechanism is enforced on the affected interfaces
  6. 6. If upgrading is not immediately possible, ensure firewall rules block unauthorized access to port 8023 on DIVAR IP devices

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

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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