CVE-2019-11891
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 potential incorrect privilege assignment vulnerability exists in the app pairing mechanism of the Bosch Smart Home Controller (SHC) before 9.8.905 that may result in elevated privileges of the adversary's choosing. In order to exploit the vulnerability, the adversary needs physical access to the SHC during the attack.
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 confidenceThe Bosch Smart Home Controller before version 9.8.905 contains an incorrect privilege assignment vulnerability in its app pairing mechanism. An attacker with physical access to the device during the pairing process can obtain elevated privileges beyond what should be granted through the legitimate pairing workflow.
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.8.905CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 device modelAccess the Bosch Smart Home Controller web interface or mobile app and confirm the device is a Bosch Smart Home Controller. Look for the device name or model information in the system settings or device information section.Affected if The device is not a Bosch Smart Home Controller, this CVE does not apply.
-
Locate the firmware version informationIn the Bosch Smart Home app, navigate to Settings > System > About or Settings > Devices > Smart Home Controller. Alternatively, access the controller's web interface and look under System Information or Device Details. The firmware version is typically displayed as a numeric build number.Affected if Unable to locate firmware version information means the check cannot be completed.
-
Compare installed version against vulnerable rangeCompare the firmware version shown to the affected range: any version before 9.8.905 (e.g., 9.8.900, 9.7.x, etc.) is vulnerable. Note that version 9.8.905 and later are patched.Affected if The installed firmware version is less than 9.8.905 (for example, 9.8.900, 9.8.0, or any earlier version).
-
Verify pairing mechanism exposureSince this vulnerability requires physical access during the pairing process, determine if the device has been recently paired or if pairing is currently enabled. Check the controller's pairing status through the app or web interface - look for any active pairing sessions or recently added devices.Affected if The device is affected if it is running vulnerable firmware AND has undergone or may undergo the app pairing process while potentially exposed to unauthorized physical access.
You are affected if your Bosch Smart Home Controller is running firmware version 9.8.905 or any later version; only versions below 9.8.905 are vulnerable to this privilege escalation during pairing.
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 data9.8.905
Upgrade the Bosch Smart Home Controller to firmware version 9.8.905 or later to obtain the patched pairing mechanism. Additionally, ensure physical security of the device to limit exposure to local attackers.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11891 — 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-11891 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