dbcve.org
Bosch Video Management SystemApplication · Bosch

CVE-2021-23860

MEDIUM · 6.1 CVSS v3.1 Published 2021-12-08
Fix available
A fix is available. Upgrade to 10.0.2 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
An error in a page handler of the VRM may lead to a reflected cross site scripting (XSS) in the web-based interface. To exploit this vulnerability an attack must be able to modify the HTTP header that is sent. This issue also affects installations of the DIVAR IP and BVMS with VRM installed.

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 · moderate confidence

A reflected cross-site scripting (XSS) vulnerability exists in the VRM (Video Recording Manager) web interface. The vulnerability stems from improper handling of HTTP headers in a page handler, allowing an attacker to inject malicious scripts that are reflected back to the user's browser. The attack requires the ability to modify HTTP headers sent to the server.

MitigationImplement proper input validation and output encoding for all HTTP header values in the VRM page handler to prevent XSS injection. Alternatively, deploy a web application firewall (WAF) rule to filter malicious header content until a code-level fix is available.

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
Bosch Video Management SystemApplication
Affected:<= 9.0>= 10.0, < 10.0.2= 10.1= 11.0
Video Recording ManagerApplication
Affected:<= 3.81>= 3.82, <= 3.82.0057>= 3.83, <= 3.83.0021>= 4.0, <= 4.00.0070

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Confirm VRM web interface is accessible
    Access the VRM web interface URL (typically port 808 or 8443 for VRM) in a browser or via curl. Check if the login page or VRM dashboard loads.
    Affected if The VRM web interface is reachable and responding to HTTP requests.
  2. Identify installed product type
    Determine whether Bosch Video Management System (BVMS) or standalone Video Recording Manager (VRM) is deployed. Check installed programs, services, or documentation.
    Affected if Either BVMS or standalone VRM software is installed.
  3. Check BVMS version
    If using Bosch Video Management System, open the BVMS Configuration Client or check the About section in the administration page. Alternatively, check the installed software version in Windows Programs and Features.
    Affected if The installed BVMS version is <= 9.0, >= 10.0 but < 10.0.2, exactly 10.1, or exactly 11.0.
  4. Check VRM version
    If using standalone Video Recording Manager, open the VRM web interface admin page or check the installed software version in Windows Programs and Features.
    Affected if The installed VRM version is <= 3.81, >= 3.82 but <= 3.82.0057, >= 3.83 but <= 3.83.0021, or >= 4.0 but <= 4.00.0070.
  5. Verify VRM page handler accepts custom headers
    Send an HTTP request to the VRM web interface with a custom X-Test header containing a test value (for example, curl -H 'X-Test: <script>alert(1)</script>' http://<vrm-host>:<port>/). Observe whether the value is reflected in the response without encoding.
    Affected if The VRM web interface reflects custom HTTP header values back in the response without sanitization or encoding.

The environment is affected if VRM web interface is running and the installed version falls within any of the affected BVMS or VRM version ranges listed, AND the VRM page handler reflects custom HTTP headers without proper encoding.

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 10.0.2 or later
Fixed in 10.0.2
Interim mitigation

Implement proper input validation and output encoding for all HTTP header values in the VRM page handler to prevent XSS injection. Alternatively, deploy a web application firewall (WAF) rule to filter malicious header content until a code-level fix is available.

Recommended fix High confidence

BVMS: 10.0.2 or later for 10.x line, or latest 10.x/11.x release; VRM: 3.82.0058+, 3.83.0022+, or 4.00.0071+ depending on branch

  1. 1. Identify the exact version of Bosch Video Management System (BVMS) or Video Recording Manager (VRM) currently installed
  2. 2. For BVMS 10.0.x installations: upgrade to BVMS 10.0.2 or later
  3. 3. For BVMS 10.1.x installations: upgrade to a version newer than 10.1 (e.g., 10.0.2 or later if applicable, or next major release)
  4. 4. For BVMS 11.0.x installations: upgrade to a version newer than 11.0
  5. 5. For BVMS 9.0 and below: upgrade to a supported newer version (e.g., 10.0.2 or later)
  6. 6. For VRM 3.82.x: upgrade to VRM version 3.82.0058 or later
  7. 7. For VRM 3.83.x: upgrade to VRM version 3.83.0022 or later
  8. 8. For VRM 4.0.x: upgrade to VRM version 4.00.0071 or later
Caveat Upgrading major versions (e.g., 9.0 to 10.x) may require migration planning and compatibility checks with connected devices and integrations

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

Fix this in Bosch Video Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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