Deps.rs

glyph_brush 0.6.3

[![dependency status](https://deps.rs/crate/glyph_brush/0.6.3/status.svg)](https://deps.rs/crate/glyph_brush/0.6.3)

This project might be open to known security vulnerabilities, which can be prevented by tightening the version range of affected dependencies. Find detailed information at the bottom.

Crate glyph_brush

Dependencies

(6 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 rusttype^0.80.9.3out of date
 glyph_brush_layout^0.1.90.2.4out of date
 log^0.4.40.4.22up to date
 ordered-float ⚠️^14.5.0out of date
 rustc-hash^12.0.0out of date
 twox-hash^12.0.1out of date

Dev dependencies

(7 total, 4 outdated)

CrateRequiredLatestStatus
 approx^0.3.10.5.1out of date
 env_logger^0.70.11.5out of date
 gl^0.140.14.0up to date
 glutin^0.230.32.1out of date
 matches^0.10.1.10up to date
 once_cell^11.20.2up to date
 spin_sleep^0.31.2.1out of date

Security Vulnerabilities

ordered-float: ordered_float:NotNan may contain NaN after panic in assignment operators

RUSTSEC-2020-0082

After using an assignment operators such as NotNan::add_assign, NotNan::mul_assign, etc., it was possible for the resulting NotNan value to contain a NaN. This could cause undefined behavior in safe code, because the safe NotNan::cmp method contains internal unsafe code that assumes the value is never NaN. (It could also cause undefined behavior in third-party unsafe code that makes the same assumption, as well as logic errors in safe code.)

This was mitigated starting in version 0.4.0, by panicking if the assigned value is NaN. However, in affected versions from 0.4.0 onward, code that uses the NotNan value during unwinding, or that continues after catching the panic, could still observe the invalid value and trigger undefined behavior.

The flaw is fully corrected in versions 1.1.1 and 2.0.1, by ensuring that the assignment operators panic without modifying the operand, if the result would be NaN.