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.
repub(12 total, 6 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| failure | ^0.1 | 0.1.8 | up to date |
| comrak ⚠️ | ^0.6 | 0.32.0 | out of date |
| clap | ^2 | 4.5.23 | out of date |
| rand | ^0.7 | 0.8.5 | out of date |
| chrono ⚠️ | ^0.4 | 0.4.39 | maybe insecure |
| html5ever | ^0.24 | 0.29.0 | out of date |
| zip | ^0.5 | 2.2.2 | out of date |
| serde | ^1.0 | 1.0.216 | up to date |
| serde_json | ^1.0 | 1.0.133 | up to date |
| colored_truecolor | ^0.1.0 | 0.1.0 | up to date |
| log | ^0.4 | 0.4.22 | up to date |
| env_logger | ^0.6 | 0.11.5 | out of 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.
comrak: XSS in `comrak`The comrak we were matching unsafe URL prefixes, such as data: or javascript: , in a case-sensitive manner. This meant prefixes like Data: were untouched.
comrak: XSS in `comrak`comrak operates by default in a "safe" mode of operation where unsafe content, such as arbitrary raw HTML or URLs with non-standard schemes, are not permitted in the output. This is per the reference GFM implementation, cmark-gfm.
Ampersands were not being correctly escaped in link targets, making it possible
to fashion unsafe URLs using schemes like data: or javascript: by entering
them as HTML entities, e.g. data:. The intended
behaviour, demonstrated upstream, is that these should be escaped and therefore
harmless, but this behaviour was broken in comrak.