# CVE-2024-45193: Weak cryptography in n/a

> Attackers can exploit Ed25519 signature malleability in the libolm library due to missing validation, potentially bypassing security checks.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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:** 22 Aug 2024
- **Updated:** 10 Sep 2024
- **Also known as:** DEBIAN-CVE-2024-45193, ECHO-aabb-f88e-39bf, GHSA-w58g-789j-fj58, UBUNTU-CVE-2024-45193

## What is CVE-2024-45193?

CVE-2024-45193 is a medium-severity vulnerability in n/a, published on 22 Aug 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in Matrix libolm through 3.2.16. There is Ed25519 signature malleability due to lack of validation criteria (does not ensure that S < n). This refers to the libolm implementation of Olm. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

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

It affects 1 product.


Products: Matrix Olm.

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

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

## Is CVE-2024-45193 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-34813](https://insights.sbomify.com/CVE-2021-34813/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-45191](https://insights.sbomify.com/CVE-2024-45191/): Information disclosure in n/a (medium 5.3)
- [CVE-2024-45192](https://insights.sbomify.com/CVE-2024-45192/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-45193 is a medium-severity vulnerability in n/a, published on 22 Aug 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-45193 in the wild and no public exploit code.

Affected product: n/a. 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-45193/ (Markdown: https://insights.sbomify.com/CVE-2024-45193/index.md)
```

## Sources

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

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