Iot Gateway SoftwareApplication · Bosch

CVE-2019-11601

HIGH · 7.5 CVSS v3.1 Published 2019-08-21
Fix available
A fix is available. Upgrade to 8.2.6 / 9.2.0 or later.
See remediation →
84/100
Remediation priority · High
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 directory traversal vulnerability in remote access to backup & restore in earlier versions than ProSyst mBS SDK 8.2.6 and Bosch IoT Gateway Software 9.2.0 allows remote attackers to write or delete files at any location.

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 directory traversal vulnerability exists in the remote backup and restore functionality of ProSyst mBS SDK and Bosch IoT Gateway Software. Attackers can use '..' sequences in backup/restore requests to escape the intended directory and write or delete files at arbitrary locations on the filesystem, leading to potential system compromise or denial of service.

MitigationUpgrade ProSyst mBS SDK to version 8.2.6 or later, and Bosch IoT Gateway Software to version 9.2.0 or later. Additionally, restrict network access to backup/restore interfaces and implement strict input validation on file paths.

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
Iot Gateway SoftwareApplication
Affected:< 9.2.0
Prosyst Mbs SdkApplication
Affected:< 8.2.6

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 IoT software
    Locate and identify any Bosch IoT Gateway Software or ProSyst mBS SDK installations on the system. Check for directories or services related to Bosch IoT Gateway or ProSyst mBS.
    Affected if Either product is installed on the system
  2. Determine installed software version
    Check the version of the installed Bosch IoT Gateway Software or ProSyst mBS SDK using vendor-provided tools, configuration files, or system inventory. Compare the version number against the affected ranges: < 9.2.0 for Bosch IoT Gateway Software and < 8.2.6 for ProSyst mBS SDK.
    Affected if The installed version is below 9.2.0 for Bosch IoT Gateway Software or below 8.2.6 for ProSyst mBS SDK
  3. Verify backup/restore functionality status
    Check whether the remote backup and restore functionality is enabled on the gateway. This may involve reviewing the gateway configuration, service settings, or administrative interfaces for backup/restore service status.
    Affected if The remote backup/restore feature is enabled and accessible
  4. Assess network exposure of backup/restore interface
    Review network configuration, firewall rules, or access control lists to determine if the backup/restore interface is exposed to network access. Check for open ports or services related to backup/restore functionality.
    Affected if The backup/restore interface is reachable from the network without proper access restrictions

A system is affected if it runs an installed version of Bosch IoT Gateway Software below 9.2.0 or ProSyst mBS SDK below 8.2.6, and the remote backup/restore functionality is enabled and network-accessible.

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 8.2.6 / 9.2.0 or later
Fixed in 8.2.69.2.0
Interim mitigation

Upgrade ProSyst mBS SDK to version 8.2.6 or later, and Bosch IoT Gateway Software to version 9.2.0 or later. Additionally, restrict network access to backup/restore interfaces and implement strict input validation on file paths.

Fix this in Iot Gateway Software Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-11601 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