CVE-2021-23859
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 · uneditedAn unauthenticated attacker is able to send a special HTTP request, that causes a service to crash. In case of a standalone VRM or BVMS with VRM installation this crash also opens the possibility to send further unauthenticated commands to the service. On some products the interface is only local accessible lowering the CVSS base score. For a list of modified CVSS scores, please see the official Bosch Advisory Appendix chapter Modified CVSS Scores for CVE-2021-23859
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 confidenceAn unauthenticated attacker can send a specially crafted HTTP request to the VRM (Video Recording Manager) service that causes it to crash. In standalone VRM or BVMS with VRM installations, this crash leaves the service in a state that allows further unauthenticated commands to be sent, potentially enabling further exploitation.
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<= 9.0>= 10.0, < 10.0.2= 10.1= 11.0<= 3.81>= 3.82, <= 3.82.0057>= 3.83, <= 3.83.0021>= 4.0, <= 4.00.0070<= 2.9.1.0<= 3.8.0<= 4.9>= 2.1, <= 2.10.0008CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Identify VRM service presenceCheck if Video Recording Manager service is installed or running on the system. Look for VRM-related processes or services in the system service list, or check for VRM installation directories.Affected if VRM service is present and the version falls within the affected ranges: <= 3.81, 3.82 to 3.82.0057, 3.83 to 3.83.0021, or 4.0 to 4.00.0070
-
Check BVMS versionVerify the installed Bosch Video Management System version through the system administration interface, registry, or installed programs list.Affected if BVMS version is <= 9.0, >= 10.0 but < 10.0.2, exactly 10.1, or exactly 11.0
-
Check Access Easy Controller firmware versionAccess the controller web interface or use the management software to determine the firmware version.Affected if Firmware version is <= 2.9.1.0
-
Check Access Professional Edition versionVerify the installed version through the application or system information.Affected if Version is <= 3.8.0
-
Check Building Integration System versionDetermine the installed BIS version through the system administration panel or installed programs.Affected if Version is <= 4.9
-
Check VRM Exporter versionIdentify the Video Recording Manager Exporter version through the application or installation directory.Affected if Version is between 2.1 and 2.10.0008 inclusive
The environment is affected if any of the identified Bosch products have versions matching the affected ranges listed and the VRM HTTP service is network-accessible.
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.
dbcve · scoped10.0.2
Apply vendor patches from Bosch security advisories. Until patched, implement network segmentation or firewall rules to restrict HTTP access to the VRM service interface to trusted networks only.
Product-specific: VMS 10.0.2+/11.0.1+; VRM 3.82.0058+/3.83.0022+/4.00.0071+; Access Easy Controller 2.9.2.0+; Access Professional Edition 3.8.1+; Building Integration System 4.9.1+; VRM Exporter 2.10.0009+
- 1. Identify the exact product and version from the affected products list in your installation
- 2. For Bosch Video Management System (VMS): Upgrade to version 10.0.2 or later, or upgrade to version 11.0.1 or later
- 3. For Video Recording Manager (VRM): Upgrade to version 3.82.0058 or later, or version 3.83.0022 or later, or version 4.00.0071 or later
- 4. For Access Easy Controller Firmware: Upgrade to version 2.9.2.0 or later
- 5. For Access Professional Edition: Upgrade to version 3.8.1 or later
- 6. For Building Integration System: Upgrade to version 4.9.1 or later
- 7. For Video Recording Manager Exporter: Upgrade to version 2.10.0009 or later
- 8. After upgrading, verify the service remains running and accessible after processing HTTP requests
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-23859 — 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-2021-23859 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