# CVE-2025-24903: libsignal-service-rs Doesn't Check Origin of Sync Messages

> Attackers can forge sync messages to impersonate other devices, requiring library updates to enforce origin checks.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/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:** 13 Feb 2025
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-r58q-66g9-h6g8

## What is CVE-2025-24903?

CVE-2025-24903 is a high-severity missing authorization vulnerability in whisperfish libsignal-service-rs, published on 13 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

libsignal-service-rs is a Rust version of the libsignal-service-java library which implements the core functionality to communicate with Signal servers. Prior to commit 82d70f6720e762898f34ae76b0894b0297d9b2f8, any contact may forge a sync message, impersonating another device of the local user. The origin of sync messages is not checked. Patched libsignal-service can be found after commit 82d70f6720e762898f34ae76b0894b0297d9b2f8. The `Metadata` struct contains an additional `was_encrypted` field, which breaks the API, but should be easily resolvable. No known workarounds are available.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2025-24903?


## How do I fix CVE-2025-24903?

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

## Is CVE-2025-24903 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-24903 and fix it if it is affected.

What it is: CVE-2025-24903 is a high-severity missing authorization vulnerability in whisperfish libsignal-service-rs, published on 13 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-24903 in the wild and no public exploit code.

Affected product: whisperfish libsignal-service-rs. 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-2025-24903/ (Markdown: https://insights.sbomify.com/CVE-2025-24903/index.md)
```

## Sources

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

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