GHSA-fq33-vmhv-48xh json
ntru-rs has unsound FFI: Wrong API usage causes write past allocated area
published 3y ago modified 3y ago also RUSTSEC-2023-0032
- 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
The following usage causes undefined behavior. ```rust let kp: ntru::types::KeyPair = …; kp.get_public().export(Default::default()) ```
When compiled with debug assertions, the code above will trigger a `attempt to subtract with overflow` panic before UB occurs. Other mistakes (e.g. using `EncParams` from a different key) may always trigger UB.
Likely, older versions of this crate are also affected, but have not been tested.
Is GHSA-fq33-vmhv-48xh 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 | ntru | >=0.4.3, <=0.5.6 >=0.0.0-0 |
no fix listed |
References
-
github.com
/FrinkGlobal/ntru-rs/issues/8
web, report
-
github.com
/FrinkGlobal/ntru-rs
package
-
rustsec.org
/advisories/RUSTSEC-2023-0032.html
web, advisory
-
crates.io
/crates/ntru
package
Sources
- GitHub Advisory GHSA-fq33-vmhv-48xh
- OSV RUSTSEC-2023-0032
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.