GHSA-p2q9-36vw-c468 json
olm-sys: wrapped library unmaintained, potentially vulnerable
published 2y ago modified 9mo ago also RUSTSEC-2024-0368
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
After several cryptographic vulnerabilities in `libolm` were disclosed publicly, the Matrix Foundation has [officially deprecated the library](https://matrix.org/blog/2024/08/libolm-deprecation/). `olm-sys` is a thin wrapper around `libolm` and is now deprecated and potentially vulnerable in kind.
Users of `olm-sys` and its higher-level abstraction, `olm-rs`, are highly encouraged to switch to [`vodozemac`](https://crates.io/crates/vodozemac) as soon as possible. It is the successor effort to `libolm` and is written in Rust.
Is GHSA-p2q9-36vw-c468 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | olm-sys | <=1.3.2 >=0.0.0-0 |
no fix listed |
Classification
- Weakness
-
- CWE-1395 Dependency on Vulnerable Third-Party Component
References
-
gitlab.gnome.org
/BrainBlasted/olm-sys
package
-
gitlab.gnome.org
/BrainBlasted/olm-sys/-/issues/12
web, report
-
matrix.org
/blog/2024/08/libolm-deprecation
web
-
rustsec.org
/advisories/RUSTSEC-2024-0368.html
web, advisory
-
crates.io
/crates/olm-sys
package
-
matrix.org
/blog/2024/08/libolm-deprecation/
web
Sources
- GitHub Advisory GHSA-p2q9-36vw-c468
- OSV RUSTSEC-2024-0368
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.