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 repub

Dependencies

(12 total, 6 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 failure^0.10.1.8up to date
 comrak ⚠️^0.60.21.0out of date
 clap^24.5.4out of date
 rand^0.70.8.5out of date
 chrono ⚠️^0.40.4.37maybe insecure
 html5ever^0.240.27.0out of date
 zip^0.50.6.6out of date
 serde^1.01.0.197up to date
 serde_json^1.01.0.115up to date
 colored_truecolor^0.1.00.1.0up to date
 log^0.40.4.21up to date
 env_logger^0.60.11.3out of date

Security Vulnerabilities

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-2020-0159

Impact

Unix-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.

Workarounds

No workarounds are known.

References

comrak: XSS in `comrak`

RUSTSEC-2021-0026

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`

RUSTSEC-2021-0063

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. &#x64&#x61&#x74&#x61&#x3a. The intended behaviour, demonstrated upstream, is that these should be escaped and therefore harmless, but this behaviour was broken in comrak.