This project contains known security vulnerabilities. Find detailed information at the bottom.

Crate torchbear

Dependencies

(44 total, 27 outdated, 2 insecure)

CrateRequiredLatestStatus
 actix^0.70.13.5out of date
 actix-lua^0.50.7.0out of date
 actix-web ⚠️^0.74.15.0insecure
 base64^0.100.23.1out of date
 blake2^0.80.11.0out of date
 checksumdir^0.3.00.3.0up to date
 chrono^0.40.4.45up to date
 clap^2.324.6.7out of date
 colored^1.63.1.1out of date
 comrak ⚠️^0.40.55.0insecure
 diff-rs^0.20.2.3up to date
 dirs^1.07.0.0out of date
 env_logger^0.60.11.11out of date
 failure^0.10.1.8up to date
 failure_derive^0.10.1.8up to date
 fern^0.50.7.1out of date
 futures^0.10.3.34out of date
 git2^0.80.21.0out of date
 heck^0.30.5.0out of date
 human-panic^1.02.0.8out of date
 libm^0.10.2.16out of date
 log^0.40.4.34up to date
 mime_guess^1.82.0.5out of date
 openssl^0.100.10.81up to date
 patch-rs^0.50.6.2out of date
 regex^1.11.13.1up to date
 rlua^0.150.20.1out of date
 rlua_serde^0.20.4.0out of date
 scl^0.00.0.1up to date
 select^0.40.6.1out of date
 serde^1.01.0.229up to date
 serde_derive^1.01.0.229up to date
 serde_json^1.01.0.151up to date
 serde_urlencoded^0.50.7.1out of date
 serde_yaml^0.80.9.34+deprecatedout of date
 sodiumoxide^0.20.2.7up to date
 splitdiff-rs^0.40.4.1up to date
 tantivy^0.80.26.2out of date
 tar^0.40.4.46up to date
 tera-v1^1.0.0-alpha.4N/Aup to date
 ulid^0.33.0.0out of date
 uuid^0.71.26.1out of date
 xz2^0.10.1.7up to date
 zip^0.58.6.0out of date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 tempfile^33.27.0up to date

Security Vulnerabilities

actix-web: Multiple memory safety issues

RUSTSEC-2018-0019

Affected versions contain multiple memory safety issues, such as:

  • Unsoundly coercing immutable references to mutable references
  • Unsoundly extending lifetimes of strings
  • Adding the Send marker trait to objects that cannot be safely sent between threads

This may result in a variety of memory corruption scenarios, most likely use-after-free.

A significant refactoring effort has been conducted to resolve these issues.

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.