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.
embassy-stm32(33 total, 11 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| bit_field | ^0.10.2 | 0.10.2 | up to date |
| bxcan | ^0.7.0 | 0.8.0 | out of date |
| cfg-if | ^1.0.0 | 1.0.0 | up to date |
| chrono ⚠️ | ^0.4 | 0.4.39 | maybe insecure |
| cortex-m | ^0.7.6 | 0.7.7 | up to date |
| cortex-m-rt | >=0.6.15, <0.8 | 0.7.5 | up to date |
| critical-section | ^1.1 | 1.2.0 | up to date |
| defmt | ^0.3 | 0.3.10 | up to date |
| document-features | ^0.2.7 | 0.2.10 | up to date |
| embassy-embedded-hal | ^0.1.0 | 0.3.0 | out of date |
| embassy-executor | ^0.5.0 | 0.7.0 | out of date |
| embassy-futures | ^0.1.0 | 0.1.1 | up to date |
| embassy-hal-internal | ^0.1.0 | 0.2.0 | out of date |
| embassy-net-driver | ^0.2.0 | 0.2.0 | up to date |
| embassy-sync | ^0.5.0 | 0.6.2 | out of date |
| embassy-time | ^0.3.0 | 0.4.0 | out of date |
| embassy-time-driver | ^0.1 | 0.2.0 | out of date |
| embassy-usb-driver | ^0.1.0 | 0.1.0 | up to date |
| embedded-hal | ^1.0 | 1.0.0 | up to date |
| embedded-hal-async | ^1.0 | 1.0.0 | up to date |
| embedded-hal-nb | ^1.0 | 1.0.0 | up to date |
| embedded-io | ^0.6.0 | 0.6.1 | up to date |
| embedded-io-async | ^0.6.1 | 0.6.1 | up to date |
| embedded-storage | ^0.3.1 | 0.3.1 | up to date |
| embedded-storage-async | ^0.4.1 | 0.4.1 | up to date |
| futures | ^0.3.17 | 0.3.31 | up to date |
| log | ^0.4.14 | 0.4.25 | up to date |
| nb | ^1.0.0 | 1.1.0 | up to date |
| rand_core | ^0.6.3 | 0.9.0 | out of date |
| sdio-host | ^0.5.0 | 0.9.0 | out of date |
| stm32-fmc | ^0.3.0 | 0.4.0 | out of date |
| stm32-metapac | ^15 | 16.0.0 | out of date |
| vcell | ^0.1.3 | 0.1.3 | up to date |
(1 total, all up-to-date)
| Crate | Required | Latest | Status |
|---|---|---|---|
| critical-section | ^1.1 | 1.2.0 | up to date |
chrono: Potential segfault in `localtime_r` invocationsUnix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.
No workarounds are known.