dbcve.org
Video Recording ManagerApplication · Bosch

CVE-2019-11684

CRITICAL · 9.8 CVSS v3.1 Published 2021-02-26
Fix available
A fix is available. Upgrade to 3.71.0034 / 3.80.0039 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Improper Access Control in the RCP+ server of the Bosch Video Recording Manager (VRM) component allows arbitrary and unauthenticated access to a limited subset of certificates, stored in the underlying Microsoft Windows operating system. The fixed versions implement modified authentication checks. Prior releases of VRM software version 3.70 are considered unaffected. This vulnerability affects VRM v3.70.x, v3.71 < v3.71.0034 and v3.81 < 3.81.0050; DIVAR IP 5000 3.80 < 3.80.0039; BVMS all versions using VRM.

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

Improper Access Control in the RCP+ server of Bosch Video Recording Manager (VRM) allows unauthenticated attackers to access a limited subset of certificates stored in the Windows OS. This bypasses authentication checks, giving attackers access to sensitive cryptographic material.

MitigationUpdate VRM to v3.71.0034 or later, v3.81.0050 or later; DIVAR IP 5000 to 3.80.0039 or later. For BVMS environments, update the VRM component to a fixed version.

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
Video Recording ManagerApplication
Affected:>= 3.70, < 3.71.0034>= 3.81, < 3.81.0050
Divar Ip 5000 FirmwareOperating system
Affected:>= 3.80, < 3.80.0039
Video Management SystemApplication
Affected:= 3.70.0056= 3.70.0058= 3.70.0060= 3.70.0062= 3.71.0022= 3.71.0029= 3.71.0031= 3.71.0032= 3.81.0032= 3.81.0038= 3.81.0048

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Identify if Bosch VRM is installed
    Check the system for Bosch Video Recording Manager installation by looking for VRM-related services or the VRM installation directory, typically under Program Files/Bosch or the application data folder.
    Affected if VRM software is present on the system
  2. Determine the installed VRM version
    Locate the VRM version information through the VRM administration interface, Windows Programs and Features, or check the VRM service properties. Compare this version number against the affected ranges: 3.70 to 3.71.0033, 3.81 to 3.81.0049, or specific BVMS versions (3.70.0056, 3.70.0058, 3.70.0060, 3.70.0062, 3.71.0022, 3.71.0029, 3.71.0031, 3.71.0032, 3.81.0032, 3.81.0038, 3.81.0048).
    Affected if The installed VRM version falls within any of the vulnerable version ranges
  3. Confirm the RCP+ server is accessible
    Verify that the RCP+ server component is running and network-accessible, as this is the vulnerable component. Check VRM service status and any firewall rules allowing RCP+ server communication (typically port 5550 or similar).
    Affected if The RCP+ server is running and exposed on the network without additional authentication layers

A system is affected if Bosch VRM is installed with a version matching the vulnerable ranges AND the RCP+ server component is active and accessible.

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.

dbcve · scoped
Upgrade available Upgrade to 3.71.0034 / 3.80.0039 / 3.81.0050 or later
Fixed in 3.71.00343.80.00393.81.0050
Interim mitigation

Update VRM to v3.71.0034 or later, v3.81.0050 or later; DIVAR IP 5000 to 3.80.0039 or later. For BVMS environments, update the VRM component to a fixed version.

Recommended fix High confidence

VRM: 3.71.0034 or 3.81.0050; DIVAR IP 5000: 3.80.0039; VMS: contact Bosch for patched version

  1. 1. Identify the currently installed Bosch Video Recording Manager (VRM), DIVAR IP 5000, or Video Management System (VMS) version
  2. 2. For VRM versions 3.70.x through 3.71.x: upgrade to VRM version 3.71.0034 or later
  3. 3. For VRM version 3.81.x: upgrade to VRM version 3.81.0050 or later
  4. 4. For DIVAR IP 5000: upgrade firmware to version 3.80.0039 or later
  5. 5. For VMS: contact Bosch support for the patched version corresponding to your 3.70.0056/0058/0060/0062 release
  6. 6. Obtain the upgrade from the official Bosch PSIRT source at psirt.bosch.com
  7. 7. Test the upgrade in a non-production environment before deploying to production
  8. 8. Apply the upgrade to production systems following standard change management procedures
Caveat Upgrade should be backward compatible but test in staging first; ensure proper backup before upgrading

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

Fix this in Video Recording Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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