[Security] Bump slice-deque from 0.1.16 to 0.2.0

[dependabot-preview[bot]]

Bumps slice-deque from 0.1.16 to 0.2.0. This update includes security fixes.

Vulnerabilities fixed

*Sourced from [The RustSec Advisory Database](https://github.com/RustSec/advisory-db/blob/master/crates/slice-deque/RUSTSEC-0000-0000.toml).* > **Bug in SliceDeque::move_head_unchecked corrupts its memory** > Affected versions of this crate entered a corrupted state if > `mem::size_of::() % allocation_granularity() != 0` and a specific allocation > pattern was used: sufficiently shifting the deque elements over the mirrored > page boundary. > > This allows an attacker that controls controls both element insertion and > removal to corrupt the deque, such that reading elements from it would read > bytes corresponding to other elements in the deque. (e.g. a read of T could read > some bytes from one value and some bytes from an adjacent one, resulting in a T > whose value representation is not meaningful). This is undefined behavior. > > The flaw was corrected by using a pair of pointers to track the head and tail of > the deque instead of a pair of indices. This pair of pointers are represented > using a Rust slice. > > Patched versions: >= 0.2.0 > Unaffected versions: none

Commits

- See full diff in [compare view](https://github.com/gnzlbg/slice_deque/commits)

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) Finally, you can contact us by mentioning @dependabot.

[azriel91]

Hiya! Please could this be merged and released? It's necessary for those with CI checks which don't let anything with security issues through 📛.

Thanks!

[germangb]

On it. I'm a bit behind