CVE-2019-8952
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 · uneditedA Path Traversal vulnerability located in the webserver affects several Bosch hardware and software products. The vulnerability potentially allows a remote authorized user to access arbitrary files on the system via the network interface. 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.10; 3.20; 3.21; 3.50; 3.51; 3.55; 3.60; 3.61; 3.62; 3.70; 3.71 before 3.71.0032 ; fixed versions: 3.71.0032; 3.81.0032 and newer), Bosch Video Management System (BVMS) (vulnerable versions: 3.50.00XX; 3.55.00XX; 3.60.00XX; 3.70.0056; fixed versions: 7.5; 3.71.0032).
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 confidenceA path traversal vulnerability in the webserver component of multiple Bosch video surveillance products allows a remote authenticated user to access arbitrary files on the system by manipulating file paths in HTTP requests. The vulnerability affects DIVAR IP 2000/5000 appliances and BVMS/VRM software through specific version ranges.
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.0032< 3.71.0032>= 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 useDetermine whether the system is running DIVAR IP 2000, DIVAR IP 5000, Bosch Video Management System (BVMS), or Video Recording Manager (VRM). Check the product model, installed software name, or system documentation.Affected if The product is one of: DIVAR IP 2000, DIVAR IP 5000, BVMS, or VRM.
-
Determine the installed firmware or software versionLocate the version information for the installed product. This is typically accessible through the product web interface, system settings, or command-line tools provided by Bosch. Record the exact version number (e.g., 3.60.0015).Affected if The exact version number cannot be determined or the product version is unknown.
-
Verify the webserver component is accessibleConfirm that the webserver component is enabled and reachable on the network. Attempt to access the web interface via HTTP/HTTPS on the default ports or the configured port for the device.Affected if The webserver is exposed and accessible to network users.
-
Compare version against affected rangesMatch the installed version to the affected ranges: DIVAR IP 2000 < 3.62.0019, DIVAR IP 5000 < 3.80.0033, BVMS < 3.71.0032, VRM < 3.71.0032 or >= 3.81 but < 3.81.0032.Affected if The installed version falls within any of these vulnerable ranges.
If the product is DIVAR IP 2000, DIVAR IP 5000, BVMS, or VRM and the installed version is below the safe thresholds (3.62.0019, 3.80.0033, 3.71.0032, or 3.81.0032 respectively), the system is vulnerable to the path traversal flaw.
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.71.00323.80.0033
Apply vendor-provided firmware/software updates: DIVAR IP 2000 to version 3.62.0019+, DIVAR IP 5000 to version 3.80.0033+, VRM to version 3.71.0032 or 3.81.0032+, and BVMS to version 7.5 or 3.71.0032.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-8952 — 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-8952 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