CVE-2019-11603
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 HTTP Traversal Attack in earlier versions than ProSyst mBS SDK 8.2.6 and Bosch IoT Gateway Software 9.0.2 allows remote attackers to read files outside the http root.
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 ProSyst mBS SDK before 8.2.6 and Bosch IoT Gateway Software before 9.0.2 allows remote attackers to access files outside the HTTP document root by using '..' sequences in HTTP requests. The vulnerability is exploitable remotely over the network without authentication.
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.2< 8.2.6CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/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 if Bosch IoT Gateway Software is installedCheck for the presence of Bosch IoT Gateway Software installation directories or check installed packages/registry entries depending on the OS. Common paths may include /opt/bosch or program files directories.Affected if The software is installed and its version is below 9.0.2
-
Identify if ProSyst mBS SDK is installedCheck for the presence of ProSyst mBS SDK installation directories or check installed packages/registry entries. Look for 'Prosyst' or 'mBS' in installation paths.Affected if The SDK is installed and its version is below 8.2.6
-
Determine the installed version of Bosch IoT Gateway SoftwareLocate the version information file or use command-line tools such as 'gateway --version' or check version files in the installation directory.Affected if The version number returned is less than 9.0.2
-
Determine the installed version of ProSyst mBS SDKLocate version files in the SDK installation directory or check build/deployment descriptors that reference the SDK version.Affected if The version number returned is less than 8.2.6
-
Confirm the HTTP service is exposedVerify that the HTTP service component of the gateway or SDK is running and accessible over the network. Check service configuration files and listening ports.Affected if The HTTP service is running and accessible remotely, making the path traversal exploitable
You are affected if either Bosch IoT Gateway Software below 9.0.2 or ProSyst mBS SDK below 8.2.6 is installed with the HTTP service enabled and exposed.
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 data8.2.69.0.2
Upgrade to ProSyst mBS SDK 8.2.6 or later, or Bosch IoT Gateway Software 9.0.2 or later. If immediate patching is not possible, implement input validation to reject '..' sequences in HTTP requests and restrict the HTTP service to minimal filesystem permissions.
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11603 — 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-11603 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