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 bdd Dev dependencies (1 total, all up-to-date)
Crate Required Latest Status cucumber ^0.220.22.1up to date
Crate iggy-mcp Dependencies (1 total, all up-to-date)
Crate Required Latest Status rmcp ^0.12.00.12.0up to date
Crate iggy-bench Dependencies (3 total, all up-to-date)
Crate Required Latest Status governor ^0.10.40.10.4up to date hostname ^0.4.20.4.2up to date rayon ^1.11.01.11.0up to date
Crate bench-dashboard-frontend Dependencies (7 total, all up-to-date)
Crate iggy-bench-dashboard-server Dependencies (7 total, all up-to-date)
Crate bench-dashboard-shared No external dependencies! 🙌
Crate bench-report No external dependencies! 🙌
Crate bench-runner Dependencies (2 total, all up-to-date)
Crate Required Latest Status dircpy ^0.3.190.3.19up to date git2 ^0.20.30.20.3up to date
Crate iggy_binary_protocol No external dependencies! 🙌
Crate iggy-cli Dependencies (1 total, all up-to-date)
Crate clock No external dependencies! 🙌
Crate iggy_common Dependencies (4 total, all up-to-date)
Crate Required Latest Status fast-async-mutex ^0.6.70.6.7up to date rcgen ^0.14.60.14.6up to date ring ^0.17.140.17.14up to date slab ^0.4.110.4.11up to date
Crate iggy-connectors No external dependencies! 🙌
Crate iggy_connector_sdk Dependencies (6 total, all up-to-date)
Crate iggy_connector_elasticsearch_sink Dependencies (1 total, all up-to-date)
Crate Required Latest Status elasticsearch ^9.1.0-alpha.1N/A up to date
Crate iggy_connector_iceberg_sink No external dependencies! 🙌
Crate iggy_connector_postgres_sink Dependencies (1 total, 1 possibly insecure)
Crate Required Latest Status sqlx ⚠️ ^0.80.8.6maybe insecure
Crate iggy_connector_quickwit_sink No external dependencies! 🙌
Crate iggy_connector_stdout_sink No external dependencies! 🙌
Crate iggy_connector_elasticsearch_source Dependencies (1 total, all up-to-date)
Crate Required Latest Status elasticsearch ^9.1.0-alpha.1N/A up to date
Crate iggy_connector_postgres_source Dependencies (1 total, all up-to-date)
Crate Required Latest Status sqlx ^0.8.60.8.6up to date
Crate iggy_connector_random_source No external dependencies! 🙌
Crate consensus No external dependencies! 🙌
Crate integration Dependencies (6 total, all up-to-date)
Crate journal No external dependencies! 🙌
Crate message_bus No external dependencies! 🙌
Crate metadata Dependencies (1 total, all up-to-date)
Crate Required Latest Status slab ^0.4.110.4.11up to date
Crate partitions No external dependencies! 🙌
Crate iggy Dependencies (1 total, all up-to-date)
Crate Required Latest Status num_cpus ^1.17.01.17.0up to date
Crate server Dependencies (23 total, all up-to-date)
Build dependencies (2 total, all up-to-date)
Crate Required Latest Status figment ^0.10.190.10.19up to date vergen-git2 ^1.0.71.0.7up to date
Crate tools No external dependencies! 🙌
Crate iggy_examples No external dependencies! 🙌
Security Vulnerabilities sqlx: Binary Protocol Misinterpretation caused by Truncating or Overflowing CastsRUSTSEC-2024-0363
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
SQL Injection isn't Dead: Smuggling Queries at the Protocol Levelhttp://web.archive.org/web/20240812130923/https://media.defcon.org/DEF%20CON%2032/DEF%20CON%2032%20presentations/DEF%20CON%2032%20-%20Paul%20Gerste%20-%20SQL%20Injection%20Isn't%20Dead%20Smuggling%20Queries%20at%20the%20Protocol%20Level.pdf
Essentially, encoding a value larger than 4GiB can cause the length prefix in the protocol to overflow,
causing the server to interpret the rest of the string as binary protocol commands or other data.
It appears SQLx does perform truncating casts in a way that could be problematic,
for example: https://github.com/launchbadge/sqlx/blob/6f2905695b9606b5f51b40ce10af63ac9e696bb8/sqlx-postgres/src/arguments.rs#L163
This code has existed essentially since the beginning,
so it is reasonable to assume that all published versions <= 0.8.0 are affected.
Mitigation
As always, you should make sure your application is validating untrustworthy user input.
Reject any input over 4 GiB, or any input that could encode to a string longer than 4 GiB.
Dynamically built queries are also potentially problematic if it pushes the message size over this 4 GiB bound.
Encode::size_hint()Json<T> and Text<T> adapters have no reasonable way to predict or estimate the final encoded size,
so they just return size_of::<T>() instead.
For web application backends, consider adding some middleware that limits the size of request bodies by default.
Resolution
sqlx 0.8.1 has been released with the fix: https://github.com/launchbadge/sqlx/blob/main/CHANGELOG.md#081---2024-08-23
Postgres users are advised to upgrade ASAP as a possible exploit has been demonstrated:
https://github.com/launchbadge/sqlx/issues/3440#issuecomment-2307956901
MySQL and SQLite do not appear to be exploitable, but upgrading is recommended nonetheless.
