Fix crate vulnerabilities

[rex4539]

https://rustsec.org/advisories/RUSTSEC-2024-0344
https://rustsec.org/advisories/RUSTSEC-2024-0332
https://rustsec.org/advisories/RUSTSEC-2024-0019
https://rustsec.org/advisories/RUSTSEC-2024-0019
https://rustsec.org/advisories/RUSTSEC-2023-0023
https://rustsec.org/advisories/RUSTSEC-2023-0063
https://rustsec.org/advisories/RUSTSEC-2024-0336
https://rustsec.org/advisories/RUSTSEC-2024-0006
https://rustsec.org/advisories/RUSTSEC-2024-0011
https://rustsec.org/advisories/RUSTSEC-2023-0052

Also updated yanked crates ahash, deunicode and futures-util.

Summary by CodeRabbit

• Chores
  • Updated an internal build dependency to enhance overall stability and reliability without affecting visible functionality.
  • Specified a particular version for a dependency to ensure consistent behavior across builds.

[coderabbitai]

"""

Walkthrough

This pull request updates the version of the cc dependency in the cryptonight-rs package's Cargo.toml file from 1.0 to 1.2.13. Additionally, it modifies the futures-util dependency in another Cargo.toml file, changing its version from ~0.3 to 0.3.31, which pins it to a specific version.

Changes

File Path	Change Summary
consensus/cryptonight-rs/Cargo.toml	Updated cc dependency version from 1.0 to 1.2.13
Cargo.toml	Updated futures-util dependency version from ~0.3 to 0.3.31

Sequence Diagram(s)

Poem

I'm a coding rabbit, hopping with delight,
A tiny version update makes my day so bright!
The cc crate grew from one to a higher mark,
In the code garden, I leave a joyful spark,
Nibble on carrots and code into the night!
"""

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ace07ac and ed8a361.

📒 Files selected for processing (1)

• Cargo.toml (1 hunks)

🔇 Additional comments (1)

Cargo.toml (1)

306-306: LGTM! Good practice to pin the futures-util version.

Pinning the futures-util version to "0.3.31" instead of using the flexible version "~0.3" is a good security practice as it prevents unexpected updates and ensures reproducible builds.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[nkysg]

@rex4539 hey, thanks for your contribution. I think some crates need to update cargo.toml just like cc, aes-gcm etc.

[rex4539]

Feel free to take over from here.

[nkysg]

the steps to create this

$ cargo audit
$ cargo update hashbrown