This project might be open to known security vulnerabilities, which can be prevented by tightening the version range of affected dependencies. Find detailed information at the bottom.

Crate bitcoin-blockparser

Dependencies

(10 total, 4 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.721.0.104up to date
 bitcoin^0.30.10.32.102out of date
 bitcoin-pool-identification^0.2.40.3.8out of date
 clap^4.3.214.6.5up to date
 diesel ⚠️^2.1.02.3.11maybe insecure
 diesel_migrations^2.1.02.3.2up to date
 dirs^5.0.16.0.0out of date
 rusty-leveldb^2.0.04.0.1out of date
 tracing^0.1.370.1.44up to date
 tracing-subscriber ⚠️^0.3.170.3.23maybe insecure

Dev dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 hex^0.4.30.4.3up to date
 tempfile^3.7.03.27.0up to date

Security Vulnerabilities

tracing-subscriber: Logging user input may result in poisoning logs with ANSI escape sequences

RUSTSEC-2025-0055

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.

This was patched in PR #3368 to escape ANSI control characters from user input.

diesel: Command injection in Diesel's implementation of `COPY FROM`/`COPY TO`

RUSTSEC-2026-0136

Diesel allows users to configure various options for PostgreSQL's COPY FROM and COPY TO statements. These configurations are partially provided as strings or characters.

Diesel did not check if any these user-provided options contain a quote character ', which can lead to the injection of additional options in the current COPY FROM/COPY TO statement.

This vulnerability affects any user of COPY FROM/COPY TO that passes user-provided input to any of the affected functions. It can result in modifications of options in the current statement, but it is not possible inject additional statements.

Mitigation

The preferred mitigation to the outlined problem is to update to Diesel version 2.3.8 or newer, which includes fixes for the problem.

Resolution

Diesel now correctly escapes any quotes contained in the provided arguments.

diesel: Possible unaligned data access for implementations of `SqliteAggregate`

RUSTSEC-2026-0137

Diesel allows to register custom aggregate SQL functions for SQLite via the SqliteAggregate interface.

To store an instance of the custom aggregate processor Diesel relied on the sqlite3_aggregate_context function provided by sqlite. This function doesn't provide any guarantees about alignment of the returned allocation, which in turn can lead to problems if the type implementing requires a special alignment, e.g. via a custom #[align(x)] attribute on the type implementing this trait. This affects any user of SqliteAggregate that registers the custom aggregate function with an SQLite connection, while using a non-standard alignment on the type implementing this trait.

Mitigation

The preferred mitigation to the outlined problem is to update to a Diesel version 2.3.8 or newer, which includes fixes for the problem.

Resolution

Diesel now allocates the corresponding memory on Rust side to get a correctly aligned allocation.