Ringer Server Does Not Check Members When Loading Messages
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · Low · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-862.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Lif-Platforms | New-Ringer-Server | before 1.3.1 | 1.3.1 | Patch available | CNA |
- New-Ringer-Server VendorLif-Platforms Affected before 1.3.1 Fixed in 1.3.1 Patch available CNA
Remediation
- Fix · CNA New-Ringer-Server (Lif-Platforms) Fixed in 1.3.1
Timeline
- 2026-10-02 Threatist record created from CVE-2024-45050
References
More Lif-Platforms vulnerabilities
- TI-2023-27208 Lif Auth Server vulnerable to uncontrolled data in path expression CVSS 3.1HIGH 7.5
- TI-2024-32043 Lif Authentication Server Has No Auth Check When Updating Password In Account Recovery CVSS 4.0MEDIUM 6.9
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences