dbcve.org
Access Professional EditionApplication · Bosch

CVE-2019-6958

CRITICAL · 9.1 CVSS v3.1 Published 2019-05-29
Fix available
A fix is available. Upgrade to 1.7.6.079 / 6.10 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
A recently discovered security vulnerability affects all Bosch Video Management System (BVMS) versions 9.0 and below, DIVAR IP 2000, 3000, 5000 and 7000, Configuration Manager, Building Integration System (BIS) with Video Engine, Access Professional Edition (APE), Access Easy Controller (AEC), Bosch Video Client (BVC) and Video SDK (VSDK). The RCP+ network port allows access without authentication. Adding authentication feature to the respective library fixes the issue. The issue is classified as "CWE-284: Improper Access Control." This vulnerability, for example, allows a potential attacker to delete video or read video data.

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

The RCP+ network protocol library used across multiple Bosch video management and physical security products (BVMS, DIVAR IP, BIS, VSDK, and others) lacks authentication controls, allowing unauthenticated remote attackers to connect to the RCP+ port and perform privileged operations including reading or deleting video data.

MitigationApply vendor patches to all affected products to add authentication to the RCP+ library, and restrict network access to RCP+ ports using firewalls or network segmentation to minimize exposure.

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
Access Professional EditionApplication
Affected:>= 3.0, <= 3.7
Bosch Video ClientApplication
Affected:< 1.7.6.079
Bosch Video Management SystemApplication
Affected:<= 9.0
Building Integration SystemApplication
Affected:>= 2.2, <= 4.4= 4.5= 4.6= 4.6.1
Configuration ManagerApplication
Affected:< 6.10
Video SdkApplication
Affected:< 6.32.0099
Dip 2000 FirmwareOperating system
Affected:< 0380.037
Dip 3000 FirmwareOperating system
Affected:all versions

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 Bosch video/security products
    Review installed software on the system for any of these products: Bosch Access Professional Edition, Bosch Video Client, Bosch Video Management System (BVMS), Building Integration System (BIS), Configuration Manager, Video SDK, DIP 2000, or DIP 3000 devices. Use 'Add/Remove Programs' on Windows or package managers on Linux to list installed software.
    Affected if Any of the listed Bosch products are installed and the version falls within the affected ranges: Access Professional Edition 3.0-3.7, Video Client < 1.7.6.079, BVMS <= 9.0, BIS 2.2-4.6.1, Configuration Manager < 6.10, Video SDK < 6.32.0099, DIP 2000 firmware < 0380.037, or DIP 3000 firmware (all ver
  2. Check product version numbers
    For each identified Bosch product, determine the exact version number. For BVMS, open the BVMS Configuration Client and go to 'About' or check the installer version. For BIS, open the BIS Configuration Manager and view the version info. For Access Professional Edition, check 'Help > About'. For Configuration Manager, check 'Help > About'. Compare against the affected version ranges provided in the CVE.
    Affected if The installed version matches one of the affected version ranges.
  3. Verify RCP+ protocol is enabled
    Access the configuration interface for the installed Bosch product. For BVMS, check 'Devices' > 'Hardware' > 'RCP+ Devices' to see if RCP+ connections are configured. For BIS, check the RCP+ service configuration. For Video SDK applications, check if the RCP+ client/server module is initialized. Look for any RCP+ port configuration in the product settings.
    Affected if RCP+ protocol is enabled and configured in the product, which is typically the default state for affected versions.
  4. Check RCP+ port accessibility
    Identify the RCP+ port (commonly port 5555 or as configured in the product). Run 'netstat -an | findstr 5555' or 'ss -tlnp | grep 5555' to check if the port is listening. Use a network scanner to verify if the port is accessible from untrusted networks. Check firewall rules with 'netsh advfirewall firewall show rule name=all' or iptables rules.
    Affected if The RCP+ port is listening and accessible from network segments that are not trusted or are exposed to untrusted networks.
  5. Review network exposure
    Review firewall rules, network segmentation, and ACLs to determine if the RCP+ port is protected from unauthenticated remote access. Check if the product is directly exposed to the internet or accessible from guest/untrusted network segments. Document all network paths that could reach the RCP+ service.
    Affected if There are no network access controls restricting RCP+ port access to authorized internal systems only.

The environment is affected if any Bosch product from the affected list is installed with a vulnerable version, RCP+ is enabled, and the RCP+ port is accessible without authentication from untrusted network locations.

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
Upgrade available Upgrade to 1.7.6.079 / 6.10 / 6.32.0099 or later
Fixed in 1.7.6.0796.106.32.0099
Interim mitigation

Apply vendor patches to all affected products to add authentication to the RCP+ library, and restrict network access to RCP+ ports using firewalls or network segmentation to minimize exposure.

Fix this in Access Professional Edition Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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