macOS Rocket.Chat: TCC Policy Bypass via Dylib Injection Due to Missing Code Signing Flags and Dangerous Entitlements
The macOS Rocket.Chat application is affected by a vulnerability that allows bypassing Transparency, Consent, and Control (TCC) policies, enabling the exploitation or abuse of permissions specified in its entitlements (e.g., microphone, camera, automation, network client). Since Rocket.Chat was not signed with the Hardened Runtime nor set to enforce Library Validation, it is vulnerable to DYLIB injection attacks, which can lead to unauthorized actions or escalation of permissions. Consequently, an attacker gains capabilities that are not permitted by default under the Sandbox and its application profile.
Problem Types
| Type | CWE ID | Description |
|---|
| CWE | CWE-863 | CWE-863 Incorrect Authorization |
Type: CWE
Description: CWE-863 Incorrect Authorization
Metrics
| Version | Base score | Base severity | Vector |
|---|
| 3.1 | 5.5 | MEDIUM | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Version: 3.1
Base score: 5.5
Base severity: MEDIUM
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Impacts
| CAPEC ID | Description |
|---|
| CAPEC-122 | CAPEC-122 Privilege Abuse |
Description: CAPEC-122 Privilege Abuse