# CVE-2024-8270: macOS Rocket.Chat: TCC Policy Bypass via Dylib Injection Due to Missing Code Signing Flags and Dangerous Entitlements

> Attackers can bypass macOS TCC policies and sandbox restrictions via dylib injection due to missing code signing flags, gaining unauthorized access to sensitive permissions.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jun 2025
- **Updated:** 11 Jun 2025
- **Also known as:** GHSA-g594-fq98-w6pj

## What is CVE-2024-8270?

CVE-2024-8270 is a medium-severity vulnerability in Rocket.Chat Desktop, published on 10 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2024-8270?


## How do I fix CVE-2024-8270?

No fix has been published for CVE-2024-8270 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-8270 being exploited?

There is no known exploitation of CVE-2024-8270 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-8270 and fix it if it is affected.

What it is: CVE-2024-8270 is a medium-severity vulnerability in Rocket.Chat Desktop, published on 10 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-8270 in the wild and no public exploit code.

Affected product: Rocket.Chat Desktop. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-8270/ (Markdown: https://insights.sbomify.com/CVE-2024-8270/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-8270
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-8270
- OSV: https://osv.dev/vulnerability/CVE-2024-8270

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-8270/
Summaries are generated and may contain mistakes; the official description above is the record.