Incorrect privilege assignment in the app pairing mechanism of the Bosch Smart Home Controller (SHC)

published 2019-05-29 7y ago modified 2026-06-17 4mo ago also EUVD-2019-3549

cvss: 8.0; version 3.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.5%; EPSS 0.5% chance of exploitation in 30 days, percentile 45%
public exploits: 0; none known

A 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.

Patch / fix

fixed in 1

Bosch Smart Home Controller 9.8.905

Is CVE-2019-11891 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.54% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.0	8.0	CVSS:3.0/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD	3.1	8.0	CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD	2.0	5.4	AV:A/AC:M/Au:N/C:P/I:P/A:P

Affected products

Bosch Smart Home Controller

Classification

Weakness

CWE-266 Incorrect Privilege Assignment
CWE-269 Improper Privilege Management

References

psirt.bosch.com /Advisory/BOSCH-SA-662084.html
vendor-advisory

Sources

CVE List CVE-2019-11891
NVD CVE-2019-11891

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.