This project contains known security vulnerabilities. Find detailed information at the bottom.
cursive(24 total, 15 outdated, 3 insecure, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| bear-lib-terminal | ^2.0.0 | 2.0.0 | up to date |
| cfg-if | ^0.1.7 | 1.0.4 | out of date |
| chrono ⚠️ | ^0.4.6 | 0.4.42 | maybe insecure |
| crossbeam-channel | ^0.3.8 | 0.5.15 | out of date |
| crossterm | ^0.9.2 | 0.29.0 | out of date |
| enum-map | ^0.5.0 | 2.7.3 | out of date |
| enumset | ^0.3.17 | 1.1.10 | out of date |
| hashbrown | ^0.2.1 | 0.16.1 | out of date |
| lazy_static | ^1.3.0 | 1.5.0 | up to date |
| libc | ^0.2.51 | 0.2.178 | up to date |
| log | ^0.4.6 | 0.4.29 | up to date |
| maplit | ^1.0.1 | 1.0.2 | up to date |
| ncurses ⚠️ | ^5.99.0 | 6.0.1 | insecure |
| num | ^0.2.0 | 0.4.3 | out of date |
| owning_ref ⚠️ | ^0.4.0 | 0.4.1 | insecure |
| pancurses ⚠️ | ^0.16.1 | 0.17.0 | insecure |
| pulldown-cmark | ^0.4.1 | 0.13.0 | out of date |
| signal-hook | ^0.1.8 | 0.3.18 | out of date |
| term_size | ^0.3.1 | 0.3.2 | up to date |
| termion | ^1.5.1 | 4.0.6 | out of date |
| toml | ^0.5.0 | 0.9.10+spec-1.1.0 | out of date |
| unicode-segmentation | ^1.2.1 | 1.12.0 | up to date |
| unicode-width | ^0.1.5 | 0.2.2 | out of date |
| xi-unicode | ^0.1.0 | 0.3.0 | out of date |
(2 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| pretty-bytes | ^0.2.2 | 0.2.2 | up to date |
| rand | ^0.6.5 | 0.9.2 | out of date |
pancurses: Format string vulnerabilities in `pancurses`pancurses::mvprintw and pancurses::printw passes a pointer from a rust &str to C,
allowing hostile input to execute a format string attack, which trivially allows writing
arbitrary data to stack memory.
ncurses: Buffer overflow and format vulnerabilities in functions exposed without unsafencurses exposes functions from the ncurses library which:
instr, mvwinstr, etc)printw family).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.
owning_ref: Multiple soundness issues in `owning_ref`OwningRef::map_with_owner is unsound and may result in a use-after-free.OwningRef::map is unsound and may result in a use-after-free.OwningRefMut::as_owner and OwningRefMut::as_owner_mut are unsound and may result in a use-after-free.noalias attribute.safer_owning_ref is a replacement crate which fixes these issues.
No patched versions of the original crate are available, and the maintainer is unresponsive.