Skip to content

Comments

chore(deps): Bump the cargo group across 1 directory with 6 updates#2

Open
dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot/cargo/cargo-b109f34fee
Open

chore(deps): Bump the cargo group across 1 directory with 6 updates#2
dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot/cargo/cargo-b109f34fee

Conversation

@dependabot
Copy link

@dependabot dependabot bot commented on behalf of github Dec 2, 2025

Bumps the cargo group with 6 updates in the / directory:

Package From To
tokio 1.43.0 1.43.1
tracing-subscriber 0.3.19 0.3.20
maxminddb 0.24.0 0.27.0
openssl 0.10.70 0.10.72
hickory-proto 0.24.2 0.24.3
ring 0.17.5 0.17.14

Updates tokio from 1.43.0 to 1.43.1

Commits
  • a7b658c chore: prepare Tokio v1.43.1 release
  • c1c8d10 Merge remote-tracking branch 'origin/tokio-1.38.x' into forward-port-1.38.x
  • aa303bc chore: prepare Tokio v1.38.2 release
  • 7b6ccb5 chore: backport CI fixes
  • 4b174ce sync: fix cloning value when receiving from broadcast channel
  • See full diff in compare view

Updates tracing-subscriber from 0.3.19 to 0.3.20

Release notes

Sourced from tracing-subscriber's releases.

tracing-subscriber 0.3.20

Security Fix: ANSI Escape Sequence Injection (CVE-TBD)

Impact

Previous versions of tracing-subscriber were vulnerable to ANSI escape sequence injection attacks. Untrusted user input containing ANSI escape sequences could be injected into terminal output when logged, potentially allowing attackers to:

  • Manipulate terminal title bars
  • Clear screens or modify terminal display
  • Potentially mislead users through terminal manipulation

In isolation, impact is minimal, however security issues have been found in terminal emulators that enabled an attacker to use ANSI escape sequences via logs to exploit vulnerabilities in the terminal emulator.

Solution

Version 0.3.20 fixes this vulnerability by escaping ANSI control characters in when writing events to destinations that may be printed to the terminal.

Affected Versions

All versions of tracing-subscriber prior to 0.3.20 are affected by this vulnerability.

Recommendations

Immediate Action Required: We recommend upgrading to tracing-subscriber 0.3.20 immediately, especially if your application:

  • Logs user-provided input (form data, HTTP headers, query parameters, etc.)
  • Runs in environments where terminal output is displayed to users

Migration

This is a patch release with no breaking API changes. Simply update your Cargo.toml:

[dependencies]
tracing-subscriber = "0.3.20"

Acknowledgments

We would like to thank zefr0x who responsibly reported the issue at security@tokio.rs.

If you believe you have found a security vulnerability in any tokio-rs project, please email us at security@tokio.rs.

Commits

Updates maxminddb from 0.24.0 to 0.27.0

Release notes

Sourced from maxminddb's releases.

0.27.0

This release includes significant API changes. See https://github.com/oschwald/maxminddb-rust/blob/HEAD/UPGRADING.md for migration guidance.

Breaking Changes

Lookup API

  • lookup() now returns LookupResult instead of Option<T>. The new API enables lazy decoding - data is only deserialized when explicitly requested.
  • lookup_prefix() has been removed. Use lookup(ip)?.network() instead.

Iteration API

  • within() now requires a second WithinOptions parameter. Use Default::default() for the previous behavior.
  • Within iterator now yields LookupResult instead of WithinItem<T>.

GeoIP2 Structs

  • The names fields now use a Names struct instead of BTreeMap<&str, &str>. Access names directly via language fields (e.g., names.english).
  • Nested struct fields (city, country, location, etc.) are now non-optional with Default, simplifying access patterns.
  • Removed is_anonymous_proxy and is_satellite_provider from Traits. These fields are no longer present in MaxMind databases.

Error Types

  • InvalidDatabase and Decoding variants now use structured fields instead of a single string. Pattern matching must be updated.
  • New InvalidInput variant for user input errors (e.g., IPv6 lookup in IPv4-only database).

Memory Mapping

  • Reader::open_mmap is now unsafe. The caller must ensure the database file is not modified or truncated while the Reader exists. This fixes a soundness issue. Reported by paolobarbolini. GitHub #86.

Added

  • LookupResult type with lazy decoding support:
    • has_data() - Check if data exists for this IP
    • network() - Get the network containing the IP
    • offset() - Get data offset for caching/deduplication
    • decode() - Deserialize full record
    • decode_path() - Selectively decode specific fields by path
  • PathElement enum and path! macro for navigating nested structures.

... (truncated)

Changelog

Sourced from maxminddb's changelog.

0.27.0 - 2025-11-28

This release includes significant API changes. See https://github.com/oschwald/maxminddb-rust/blob/main/UPGRADING.md for migration guidance.

Breaking Changes

Lookup API

  • lookup() now returns LookupResult instead of Option<T>. The new API enables lazy decoding - data is only deserialized when explicitly requested.
  • lookup_prefix() has been removed. Use lookup(ip)?.network() instead.

Iteration API

  • within() now requires a second WithinOptions parameter. Use Default::default() for the previous behavior.
  • Within iterator now yields LookupResult instead of WithinItem<T>.

GeoIP2 Structs

  • The names fields now use a Names struct instead of BTreeMap<&str, &str>. Access names directly via language fields (e.g., names.english).
  • Nested struct fields (city, country, location, etc.) are now non-optional with Default, simplifying access patterns.
  • Removed is_anonymous_proxy and is_satellite_provider from Traits. These fields are no longer present in MaxMind databases.

Error Types

  • InvalidDatabase and Decoding variants now use structured fields instead of a single string. Pattern matching must be updated.
  • New InvalidInput variant for user input errors (e.g., IPv6 lookup in IPv4-only database).

Memory Mapping

  • Reader::open_mmap is now unsafe. The caller must ensure the database file is not modified or truncated while the Reader exists. This fixes a soundness issue. Reported by paolobarbolini. GitHub #86.

Added

  • LookupResult type with lazy decoding support:
    • has_data() - Check if data exists for this IP
    • network() - Get the network containing the IP
    • offset() - Get data offset for caching/deduplication
    • decode() - Deserialize full record
    • decode_path() - Selectively decode specific fields by path
  • PathElement enum and path! macro for navigating nested structures.

... (truncated)

Commits
  • 02d6fc7 Suppress dead_code warning in test struct
  • ff5cc41 Add .claude to .gitignore
  • df13038 Merge pull request #101 from oschwald/greg/gh-actions-updates
  • c7052ea Fix cargo audit workflow
  • 8e9cbae Add release script and trigger publish on GitHub releases
  • 5867bc7 Add Trusted Publishing workflow for crates.io
  • da0ecf6 Add security scanning and modernize GitHub Actions
  • bd45717 Merge pull request #100 from oschwald/greg/result
  • 98f0e4f Mark Reader::open_mmap as unsafe to fix soundness issue
  • 75dd92a Prepare 0.27.0 release
  • Additional commits viewable in compare view

Updates openssl from 0.10.70 to 0.10.72

Release notes

Sourced from openssl's releases.

openssl-v0.10.72

What's Changed

New Contributors

Full Changelog: rust-openssl/rust-openssl@openssl-v0.10.71...openssl-v0.10.72

openssl-v0.10.71

What's Changed

New Contributors

Full Changelog: rust-openssl/rust-openssl@openssl-v0.10.70...openssl-v0.10.71

Commits
  • 87085bd Merge pull request #2390 from alex/uaf-fix
  • d1a12e2 Fixed two UAFs and bumped versions for release
  • 7c7b2e6 Merge pull request #2389 from skmcgrail/aws-lc-follow-up
  • 34a477b Use --experimental with bindgen-cli with aws-lc build
  • d4bf071 Merge pull request #2386 from skmcgrail/aws-lc-follow-up
  • a86bf67 Remove comment
  • 705dbfb Fix test
  • e0df413 Skip final call for LibreSSL 4.1.0 for CCM mode
  • 2f1164b Enable additional capabilities for AWS-LC
  • dde9ffb Merge pull request #1805 from skmcgrail/aws-lc-support-final
  • Additional commits viewable in compare view

Updates hickory-proto from 0.24.2 to 0.24.3

Release notes

Sourced from hickory-proto's releases.

v0.24.3

What's Changed

Full Changelog: hickory-dns/hickory-dns@v0.24.2...v0.24.3

Changelog

Sourced from hickory-proto's changelog.

0.24.3

  • Fix DNSSEC verification of DNSKEY RRsets
Commits

Updates ring from 0.17.5 to 0.17.14

Changelog

Sourced from ring's changelog.

Version 0.17.14 (2025-03-11)

Fixed a performance bug in the AVX2-based AES-GCM implementation added in ring 0.17.13. This will be another notable performance improvement for most newish x86-64 systems. The performance issue impacted not just AES-GCM.

Compatibility with GNU binutils 2.29 (used on Amazon Linux 2), and probably even earlier versions, was restored. It is expected that ring 0.17.14 will build on all the systems that 0.17.12 would build on.

Version 0.17.13 (2025-03-06)

Increased MSRV to 1.66.0 to avoid bugs in earlier versions so that we can safely use core::arch::x86_64::__cpuid and core::arch::x86::__cpuid from Rust in future releases.

AVX2-based VAES-CLMUL implementation. This will be a notable performance improvement for most newish x86-64 systems. This will likely raise the minimum binutils version supported for very old Linux distros.

Version 0.17.12 (2025-03-05)

Bug fix: briansmith/ring#2447 for denial of service (DoS).

  • Fixes a panic in ring::aead::quic::HeaderProtectionKey::new_mask() when integer overflow checking is enabled. In the QUIC protocol, an attacker can induce this panic by sending a specially-crafted packet. Even unintentionally it is likely to occur in 1 out of every 2**32 packets sent and/or received.

  • Fixes a panic on 64-bit targets in ring::aead::{AES_128_GCM, AES_256_GCM} when overflow checking is enabled, when encrypting/decrypting approximately 68,719,476,700 bytes (about 64 gigabytes) of data in a single chunk. Protocols like TLS and SSH are not affected by this because those protocols break large amounts of data into small chunks. Similarly, most applications will not attempt to encrypt/decrypt 64GB of data in one chunk.

Overflow checking is not enabled in release mode by default, but RUSTFLAGS="-C overflow-checks" or overflow-checks = true in the Cargo.toml profile can override this. Overflow checking is usually enabled by default in debug mode.

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 close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
    You can disable automated security fix PRs for this repo from the Security Alerts page.

@dependabot
chore(deps): Bump the cargo group across 1 directory with 6 updates
b5d0f92 
Bumps the cargo group with 6 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [tokio](https://github.com/tokio-rs/tokio) | `1.43.0` | `1.43.1` |
| [tracing-subscriber](https://github.com/tokio-rs/tracing) | `0.3.19` | `0.3.20` |
| [maxminddb](https://github.com/oschwald/maxminddb-rust) | `0.24.0` | `0.27.0` |
| [openssl](https://github.com/rust-openssl/rust-openssl) | `0.10.70` | `0.10.72` |
| [hickory-proto](https://github.com/hickory-dns/hickory-dns) | `0.24.2` | `0.24.3` |
| [ring](https://github.com/briansmith/ring) | `0.17.5` | `0.17.14` |



Updates `tokio` from 1.43.0 to 1.43.1
- [Release notes](https://github.com/tokio-rs/tokio/releases)
- [Commits](tokio-rs/tokio@tokio-1.43.0...tokio-1.43.1)

Updates `tracing-subscriber` from 0.3.19 to 0.3.20
- [Release notes](https://github.com/tokio-rs/tracing/releases)
- [Commits](tokio-rs/tracing@tracing-subscriber-0.3.19...tracing-subscriber-0.3.20)

Updates `maxminddb` from 0.24.0 to 0.27.0
- [Release notes](https://github.com/oschwald/maxminddb-rust/releases)
- [Changelog](https://github.com/oschwald/maxminddb-rust/blob/main/CHANGELOG.md)
- [Commits](oschwald/maxminddb-rust@0.24.0...v0.27.0)

Updates `openssl` from 0.10.70 to 0.10.72
- [Release notes](https://github.com/rust-openssl/rust-openssl/releases)
- [Commits](rust-openssl/rust-openssl@openssl-v0.10.70...openssl-v0.10.72)

Updates `hickory-proto` from 0.24.2 to 0.24.3
- [Release notes](https://github.com/hickory-dns/hickory-dns/releases)
- [Changelog](https://github.com/hickory-dns/hickory-dns/blob/v0.24.3/CHANGELOG.md)
- [Commits](hickory-dns/hickory-dns@v0.24.2...v0.24.3)

Updates `ring` from 0.17.5 to 0.17.14
- [Changelog](https://github.com/briansmith/ring/blob/main/RELEASES.md)
- [Commits](https://github.com/briansmith/ring/commits)

---
updated-dependencies:
- dependency-name: tokio
  dependency-version: 1.43.1
  dependency-type: direct:production
  dependency-group: cargo
- dependency-name: tracing-subscriber
  dependency-version: 0.3.20
  dependency-type: direct:production
  dependency-group: cargo
- dependency-name: maxminddb
  dependency-version: 0.27.0
  dependency-type: direct:production
  dependency-group: cargo
- dependency-name: openssl
  dependency-version: 0.10.72
  dependency-type: direct:production
  dependency-group: cargo
- dependency-name: hickory-proto
  dependency-version: 0.24.3
  dependency-type: direct:production
  dependency-group: cargo
- dependency-name: ring
  dependency-version: 0.17.14
  dependency-type: indirect
  dependency-group: cargo
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels Dec 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file rust Pull requests that update rust code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants