The shlex crate before 1.2.1 for Rust allows unquoted and unescaped instances of the { and \xa0 characters, which may facilitate command injection.

Affected: crates.io: shlex

## 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][solved-xa0].)

## 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 resu…

framework-inputmodule-control-0.2.0-3.1 on GA media

Affected: crates.io: shlex

## 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][solved-xa0].)

## 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 resu…

Security update for rust-keylime

Affected: Ubuntu:20.04:LTS: rust-shlex, Ubuntu:22.04:LTS: rust-shlex, Ubuntu:24.04:LTS: rust-shlex, Ubuntu:25.10: rust-shlex, Ubuntu:26.04:LTS: rust-shlex

The shlex crate before 1.2.1 for Rust allows unquoted and unescaped instances of the { and \xa0 characters, which may facilitate command injection.