i_triangle
Affected
- introduced
0.0.0-0, fixed0.29.0(semver)
Fixed versions
0.29.0
Fix
- Fixed version
0.29.0cargo update -p i_triangle --precise 0.29.0
Advisory
Also known as: None
DTriangle accessors may read out of bounds in affected versions
In affected versions, DTriangle::neighbor_by_order and DTriangle::vertex_by_order were public safe functions that accepted an
arbitrary order value. These functions used order to access fixed-size internal arrays with get_unchecked, without checking whether order was within bounds. Calling these methods with an out-of-bounds order could cause an out-of-bounds read from safe Rust code. This made the old APIs unsound, since safe callers could trigger undefined behavior without using unsafe.
The issue was fixed in version 0.29.0 as part of a broader rewrite that replaced the old triangle implementation with IntTriangle and removed the affected accessor methods.
Not rated by the source.
0.0.0-0, fixed 0.29.0 (semver)0.29.0
0.29.0cargo update -p i_triangle --precise 0.29.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: RustSec Advisory Database · CC0-1.0