# CVE-2024-45050: Ringer Server Does Not Check Members When Loading Messages

> An attacker can read private conversations between other users by bypassing membership checks in the Ringer messaging server.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Sep 2024
- **Updated:** 4 Sep 2024
- **Also known as:** GHSA-cpc7-79cg-qv65

## What is CVE-2024-45050?

CVE-2024-45050 is a high-severity missing authorization vulnerability in Lif-Platforms New-Ringer-Server, published on 4 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Ringer server is the server code for the Ringer messaging app. Prior to version 1.3.1, there is an issue with the messages loading route where Ringer Server does not check to ensure that the user loading the conversation is actually a member of that conversation. This allows any user with a Lif Account to load any conversation between two users without permission. This issue had been patched in version 1.3.1. There is no action required for users. Lif Platforms will update their servers with the patch.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2024-45050 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-45050 is a high-severity missing authorization vulnerability in Lif-Platforms New-Ringer-Server, published on 4 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-45050 in the wild and no public exploit code.

Affected product: Lif-Platforms New-Ringer-Server. 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-45050/ (Markdown: https://insights.sbomify.com/CVE-2024-45050/index.md)
```

## Sources

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

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