CVE-2024-45193

Exp

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.

Published: 2024-08-22 Last update: 2025-06-17 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2024-45193 is rated Exploit Available (50/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.05%). Core evidence: 1 public exploit reference(s) are indexed (Exploit-DB). Mandatory action: Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2024-45193

EDB-ID Source Kind Published Link
nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2024-45193

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-03-19 0.04% 0.05% +0.01%
2 2024-08-23 0.04%

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-45193

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
2.8 1.4 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2024-45193

OS Trackers for CVE-2024-45193

vendor priority summary link
alpine CVE-2024-45193: 1 source package rows (olm); 5 state rows across 3 repos (3.22-community, 3.23-community, edge-community); fixed 0, open 5. https://security.alpinelinux.org/vuln/CVE-2024-45193
debian not yet assigned CVE-2024-45193 not yet assigned priority: Debian including 1 source packages (olm), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 5. https://security-tracker.debian.org/tracker/CVE-2024-45193
ubuntu medium CVE-2024-45193 medium priority: Ubuntu including 1 source packages (olm), 8 status rows across 8 suites (bionic, focal, jammy, noble, oracular, plucky, questing, upstream): needs-triage 6, ignored 2. https://ubuntu.com/security/CVE-2024-45193

Affected software / configurations for CVE-2024-45193

Vendor Product Version Raw CPE
matrix olm <= 3.2.16 cpe:2.3:a:matrix:olm:*:*:*:*:*:*:*:*

References for CVE-2024-45193

cvelogic Threat Intelligence