[Security] Bump slice-deque from 0.1.13 to 0.1.16

[dependabot-preview[bot]]

Bumps slice-deque from 0.1.13 to 0.1.16. 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-2018-0008.toml).* > **Bug in SliceDeque::move_head_unchecked allows read of corrupted memory** > Affected versions of this crate did not properly update the > head and tail of the deque when inserting and removing elements from the front > if, before insertion or removal, the tail of the deque was in the mirrored > memory region, and if, after insertion or removal, the head of the deque is > exactly at the beginning of the mirrored memory region. > > An attacker that controls both element insertion and removal into the deque > could put it in a corrupted state. Once the deque enters such an state, its head > and tail are corrupted, but in bounds of the allocated memory. This can result > in partial reads and writes, reads of uninitialized memory, reads of memory > containing previously dropped objects, etc. An attacker could exploit this to > alter program execution. > > The flaw was corrected by properly updating the head and tail of the deque in > this case. > > Patched versions: >= 0.1.16 > 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.

---

Note: This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit.

You can always request more updates by clicking Bump now in your Dependabot dashboard.

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 cancel merge` will cancel a previously requested merge - `@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.

[K4ugummi]

Fixed with #51

[dependabot-preview[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.