# CVE-2024-42027: Weak cryptography in Mobile

> Insufficient entropy in E2EE passwords allows attackers to crack them, compromising encrypted data in Rocket.Chat Mobile.

- **Severity:** Medium 6.7 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Oct 2024
- **Updated:** 7 Oct 2024
- **Also known as:** GHSA-f7vv-q49x-rvww

## What is CVE-2024-42027?

CVE-2024-42027 is a medium-severity vulnerability in Rocket.Chat Mobile, published on 7 Oct 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The E2EE password entropy generated by Rocket.Chat Mobile prior to version 4.5.1 is insufficient, allowing attackers to crack it if they have the appropriate time and resources.

Weakness: CWE-1391 (Use of Weak Credentials)

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


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

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

## Is CVE-2024-42027 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-42027 is a medium-severity vulnerability in Rocket.Chat Mobile, published on 7 Oct 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-42027 in the wild and no public exploit code.

Affected product: Rocket.Chat Mobile. 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-42027/ (Markdown: https://insights.sbomify.com/CVE-2024-42027/index.md)
```

## Sources

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

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