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 mdbook

Dependencies

(26 total, 7 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 ammonia^3.3.04.0.0out of date
 anyhow^1.0.711.0.86up to date
 chrono^0.4.240.4.38up to date
 clap^4.3.124.5.9up to date
 clap_complete^4.3.24.5.8up to date
 elasticlunr-rs^3.0.23.0.2up to date
 env_logger^0.10.00.11.3out of date
 futures-util^0.3.280.3.30up to date
 handlebars^4.3.75.1.2out of date
 ignore^0.4.200.4.22up to date
 log^0.4.170.4.22up to date
 memchr^2.5.02.7.4up to date
 notify^6.0.16.1.1up to date
 notify-debouncer-mini^0.3.00.4.1out of date
 once_cell^1.17.11.19.0up to date
 opener^0.6.10.7.1out of date
 pulldown-cmark^0.9.30.11.0out of date
 regex^1.8.11.10.5up to date
 serde^1.0.1631.0.204up to date
 serde_json^1.0.961.0.120up to date
 shlex ⚠️^1.1.01.3.0maybe insecure
 tempfile^3.4.03.10.1up to date
 tokio^1.28.11.38.1up to date
 toml^0.5.110.8.15out of date
 topological-sort^0.2.20.2.2up to date
 warp^0.3.50.3.7up to date

Dev dependencies

(6 total, all up-to-date)

CrateRequiredLatestStatus
 assert_cmd^2.0.112.0.14up to date
 predicates^3.0.33.1.0up to date
 pretty_assertions^1.3.01.4.0up to date
 select^0.6.00.6.0up to date
 semver^1.0.171.0.23up to date
 walkdir^2.3.32.5.0up to date

Security Vulnerabilities

shlex: Multiple issues involving quote API

RUSTSEC-2024-0006

Issue 1: Failure to quote characters

Affected versions of this crate allowed the bytes { and \xa0 to appear unquoted and unescaped in command arguments.

If the output of quote or join is passed to a shell, then what should be a single command argument could be interpreted as multiple arguments.

This does not directly allow arbitrary command execution (you can't inject a command substitution or similar). But depending on the command you're running, being able to inject multiple arguments where only one is expected could lead to undesired consequences, potentially including arbitrary command execution.

The flaw was corrected in version 1.2.1 by escaping additional characters. Updating to 1.3.0 is recommended, but 1.2.1 offers a more minimal fix if desired.

Workaround: Check for the bytes { and \xa0 in quote/join input or output.

(Note: { is problematic because it is used for glob expansion. \xa0 is problematic because it's treated as a word separator in specific environments.)

Issue 2: Dangerous API w.r.t. nul bytes

Version 1.3.0 deprecates the quote and join APIs in favor of try_quote and try_join, which behave the same except that they have Result return type, returning Err if the input contains nul bytes.

Strings containing nul bytes generally cannot be used in Unix command arguments or environment variables, and most shells cannot handle nul bytes even internally. If you try to pass one anyway, then the results might be security-sensitive in uncommon scenarios. More details here.

Due to the low severity, the behavior of the original quote and join APIs has not changed; they continue to allow nuls.

Workaround: Manually check for nul bytes in quote/join input or output.

Issue 3: Lack of documentation for interactive shell risks

The quote family of functions does not and cannot escape control characters. With non-interactive shells this is perfectly safe, as control characters have no special effect. But if you writing directly to the standard input of an interactive shell (or through a pty), then control characters can cause misbehavior including arbitrary command injection.

This is essentially unfixable, and has not been patched. But as of version 1.3.0, documentation has been added.

Future versions of shlex may add API variants that avoid the issue at the cost of reduced portability.