Incorrect privilege assignment in the app permission update API of the Bosch Smart Home Controller (SHC)

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

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

A potential incorrect privilege assignment vulnerability exists in the app permission update API of the Bosch Smart Home Controller (SHC) before 9.8.905 that may result in a restricted app obtaining default app permissions. In order to exploit the vulnerability, the adversary needs to have successfully paired an app with restricted permissions, which required user interaction.

Patch / fix

fixed in 1

Bosch Smart Home Controller 9.8.905

Is CVE-2019-11893 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.45% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.0	5.5	CVSS:3.0/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
NVD	3.1	8.0	CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	4.9	AV:A/AC:M/Au:S/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-11893
NVD CVE-2019-11893

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.