CVE-2019-8951
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 Open Redirect vulnerability located in the webserver affects several Bosch hardware and software products. The vulnerability potentially allows a remote attacker to redirect users to an arbitrary URL. Affected hardware products: Bosch DIVAR IP 2000 (vulnerable versions: 3.10; 3.20; 3.21; 3.50; 3.51; 3.55; 3.60; 3.61; 3.62; fixed versions: 3.62.0019 and newer), Bosch DIVAR IP 5000 (vulnerable versions: 3.10; 3.20; 3.21; 3.50; 3.51; 3.55; 3.60; 3.61; 3.62; fixed versions: 3.80.0033 and newer). Affected software products: Video Recording Manager (VRM) (vulnerable versions: 3.20; 3.21; 3.50; 3.51; 3.55; 3.60; 3.61; 3.62; fixed versions: 3.70.0056 and newer; 3.81.0032 and newer), Bosch Video Management System (BVMS) (vulnerable versions: 3.50.00XX; 3.55.00XX; 3.60.00XX; fixed versions: 7.5; 3.70.0056).
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 confidenceAn open redirect vulnerability exists in the webserver component of multiple Bosch video surveillance products (DIVAR IP 2000, DIVAR IP 5000, VRM, and BVMS). Attackers can craft malicious URLs that appear to originate from the legitimate Bosch webserver but redirect users to arbitrary external sites, enabling phishing and credential theft attacks.
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< 3.62.0019< 3.80.0033< 3.71.0056< 3.70.0056>= 3.81, < 3.81.0032CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Bosch product in your environmentAccess the system information page of your Bosch video surveillance system through the web interface or check system documentation to determine if you are running DIVAR IP 2000, DIVAR IP 5000, Video Management System (BVMS), or Video Recording Manager (VRM).Affected if The product is any of these four affected products and you cannot confirm the exact version.
-
Locate the firmware or software versionLog into the Bosch web interface and navigate to the System Information or About page. For DIVAR IP devices, check the firmware version displayed in the admin dashboard. For BVMS and VRM, check the software version in the application or installer information.Affected if You cannot determine the exact installed version number.
-
Compare your version against affected rangesFor DIVAR IP 2000: verify if version is below 3.62.0019. For DIVAR IP 5000: verify if version is below 3.80.0033. For BVMS: verify if version is below 3.71.0056. For VRM: verify if version is below 3.70.0056 OR between 3.81.0000 and 3.81.0031.Affected if Your installed version falls within any of these vulnerable ranges.
-
Test for open redirect behaviorIf you cannot confirm a safe version, send a crafted request to your webserver with a redirect parameter pointing to an external domain, such as `https://<your-bosch-server>/redirect?url=https://evil.com`. Observe if the response includes a Location header directing to the external domain.Affected if The server returns a 3xx redirect to an external domain not under your organizational control.
You are affected if your Bosch video surveillance product is one of the four affected types AND the installed firmware/software version falls below the fixed version thresholds, or you can demonstrate the open redirect behavior through testing.
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.
From vendor data3.62.00193.70.00563.71.0056
Update affected products to the vendor-specified fixed versions: DIVAR IP 2000 to 3.62.0019+, DIVAR IP 5000 to 3.80.0033+, VRM to 3.70.0056+ or 3.81.0032+, and BVMS to 7.5 or 3.70.0056+. If patching is not immediately feasible, implement URL validation at upstream proxies or network perimeter devices to detect and block suspicious redirect parameters.
- Consultation3.0 h
- Implementation4.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-8951 — 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-2019-8951 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