dbcve.org
Iot Gateway SoftwareApplication · Bosch

CVE-2019-11897

HIGH · 8.6 CVSS v3.0 Published 2019-08-21
Fix available
A fix is available. Upgrade to 8.2.6 / 9.3.0 or later.
See remediation →
95/100
Remediation priority · Urgent
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 Server-Side Request Forgery (SSRF) vulnerability in the backup & restore functionality in earlier versions than ProSyst mBS SDK 8.2.6 and Bosch IoT Gateway Software 9.3.0 allows a remote attacker to forge GET requests to arbitrary URLs. In addition, this could potentially allow an attacker to read sensitive zip files from the local server.

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 confidence

This is a Server-Side Request Forgery (SSRF) vulnerability in the backup and restore functionality of ProSyst mBS SDK and Bosch IoT Gateway Software. The vulnerability allows remote attackers to force the server to make GET requests to arbitrary URLs, potentially reaching internal systems. Additionally, the flaw permits reading sensitive zip files from the local server file system.

MitigationUpgrade to ProSyst mBS SDK 8.2.6 or later, or Bosch IoT Gateway Software 9.3.0 or later. If immediate patching is not possible, restrict network access to the backup/restore interfaces and monitor for suspicious outbound requests.

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.3.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
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Bosch IoT Gateway Software version
    Locate the installation directory and check the version file or banner. Common locations include /opt/bosch/iot-gateway or the installation root. Look for a version.info, VERSION, or similar file, or run: java -jar gateway.jar --version
    Affected if The installed version is below 9.3.0
  2. Identify installed ProSyst mBS SDK version
    Check the SDK installation directory for version information. Look in the SDK root folder for a version manifest or about file. The version is typically stored in a manifest.mf or version.properties file within the SDK libraries
    Affected if The installed version is below 8.2.6
  3. Verify if backup/restore functionality is exposed
    Examine the web service configuration or API endpoints. Check configuration files (typically in a config/ or conf/ directory) for backup/restore service definitions. Look for endpoints related to backup, restore, or archive operations that may be accessible over HTTP/HTTPS
    Affected if The backup/restore interface is externally accessible without authentication or proper network restrictions
  4. Inspect network logs for suspicious outbound requests
    Review gateway or firewall logs for outgoing HTTP/HTTPS connections from the gateway server to unusual internal or external IP addresses. Focus on GET requests originating from the gateway software process, especially to internal IP ranges (127.0.0.0/8, 10.0.0.0/8, 192.168.0.0/16)
    Affected if Outbound GET requests are observed from the gateway to arbitrary URLs that were not initiated by legitimate backup operations
  5. Check file system for unauthorized zip file access
    Audit server logs and access records for backup/restore operations accessing zip files outside the expected backup directory. Review application logs for file read operations on sensitive system directories
    Affected if Evidence exists of zip file reads from locations outside designated backup directories, particularly system or configuration directories

You are affected if either Bosch IoT Gateway Software below 9.3.0 or ProSyst mBS SDK below 8.2.6 is installed AND the backup/restore interface is accessible, as the SSRF flaw allows arbitrary URL requests and local file access.

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.3.0 or later
Fixed in 8.2.69.3.0
Interim mitigation

Upgrade to ProSyst mBS SDK 8.2.6 or later, or Bosch IoT Gateway Software 9.3.0 or later. If immediate patching is not possible, restrict network access to the backup/restore interfaces and monitor for suspicious outbound requests.

Fix this in Iot Gateway Software Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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