sqlx
Activity
- Latest release
- 3mo ago
- Total releases
- 59
- Cadence
- ~36 days
- Last 12 months
- 2
Details
- License
- MIT OR Apache-2.0
- First release
- Jun 06, 2019
| Version | Released | |
|---|---|---|
0.9.0
unknown
|
0.9.0
unknown
Dependencies (22)
+ 14 more |
|
0.9.0-alpha.1
unknown
|
0.9.0-alpha.1
unknown
Dependencies (23)
+ 15 more |
|
0.8.6
unknown
|
0.8.6
unknown
Dependencies (23)
+ 15 more |
|
0.8.5
unknown
|
0.8.5
unknown
Dependencies (23)
+ 15 more |
|
0.8.4
unknown
yanked
|
0.8.4
unknown
yanked
Dependencies (23)
+ 15 more |
|
0.8.3
unknown
|
0.8.3
unknown
Dependencies (23)
+ 15 more |
|
0.8.2
unknown
|
0.8.2
unknown
Dependencies (23)
+ 15 more |
|
0.8.1
unknown
|
0.8.1
unknown
Dependencies (23)
+ 15 more |
|
0.8.0
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.8.0
unknown
Dependencies (23)
+ 15 more |
|
0.7.4
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.7.4
unknown
Dependencies (23)
+ 15 more |
|
0.7.3
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.7.3
unknown
Dependencies (23)
+ 15 more |
|
0.7.2
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.7.2
unknown
Dependencies (23)
+ 15 more |
|
0.7.1
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.7.1
unknown
Dependencies (23)
+ 15 more |
|
0.7.0
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.7.0
unknown
Dependencies (23)
+ 15 more |
|
0.7.0-alpha.3
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.7.0-alpha.3
unknown
Dependencies (23)
+ 15 more |
|
0.6.3
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.6.3
unknown
Dependencies (19)
+ 11 more |
|
0.7.0-alpha.2
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.7.0-alpha.2
unknown
Dependencies (22)
+ 14 more |
|
0.7.0-alpha.1
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.7.0-alpha.1
unknown
Dependencies (22)
+ 14 more |
|
0.6.2
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.6.2
unknown
Dependencies (19)
+ 11 more |
|
0.6.1
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.6.1
unknown
Dependencies (17)
+ 9 more |
|
0.6.0
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.6.0
unknown
Dependencies (17)
+ 9 more |
|
0.5.13
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.5.13
unknown
Dependencies (17)
+ 9 more |
|
0.5.12
unknown
yanked
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.5.12
unknown
yanked
Dependencies (17)
+ 9 more |
|
0.5.11
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.5.11
unknown
Dependencies (17)
+ 9 more |
|
0.5.10
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.5.10
unknown
Dependencies (17)
+ 9 more |
|
0.5.9
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.5.9
unknown
Dependencies (14)
+ 6 more |
|
0.5.8
unknown
yanked
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.5.8
unknown
yanked
Dependencies (14)
+ 6 more |
|
0.5.7
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.5.7
unknown
Dependencies (14)
+ 6 more |
|
0.5.6
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.5.6
unknown
Dependencies (14)
+ 6 more |
|
0.5.5
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.5.5
unknown
Dependencies (14)
+ 6 more |
|
0.5.4
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.5.4
unknown
Dependencies (14)
+ 6 more |
|
0.5.3
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.5.3
unknown
Dependencies (14)
+ 6 more |
|
0.5.2
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.5.2
unknown
Dependencies (14)
+ 6 more |
|
0.5.1
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.5.1
unknown
Dependencies (14)
+ 6 more |
|
0.5.0
unknown
yanked
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.5.0
unknown
yanked
Dependencies (14)
+ 6 more |
|
0.4.2
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.4.2
unknown
Dependencies (14)
+ 6 more |
|
0.4.1
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.4.1
unknown
Dependencies (14)
+ 6 more |
|
0.4.0
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.4.0
unknown
Dependencies (14)
+ 6 more |
|
0.4.0-beta.1
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.4.0-beta.1
unknown
Dependencies (14)
+ 6 more |
|
0.3.5
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.3.5
unknown
Dependencies (13)
+ 5 more |
|
0.3.4
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.3.4
unknown
Dependencies (13)
+ 5 more |
|
0.3.3
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.3.3
unknown
Dependencies (13)
+ 5 more |
|
0.3.2
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.3.2
unknown
Dependencies (13)
+ 5 more |
|
0.3.1
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.3.1
unknown
Dependencies (13)
+ 5 more |
|
0.3.0
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.3.0
unknown
Dependencies (13)
+ 5 more |
|
0.3.0-alpha.2
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.3.0-alpha.2
unknown
Dependencies (13)
+ 5 more |
|
0.3.0-alpha.1
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.3.0-alpha.1
unknown
Dependencies (10)
+ 2 more |
|
0.2.6
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.2.6
unknown
Dependencies (9)
+ 1 more |
|
0.2.5
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.2.5
unknown
Dependencies (9)
+ 1 more |
|
0.2.4
unknown
1 CVE
GHSA-xmrp-424f-vfpx
RUSTSEC-2024-0363
Aug 19, 2024
SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
Medium
The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:
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 MitigationAs 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.
For web application backends, consider adding some middleware that limits the size of request bodies by default. ResolutionWork has started on a branch to add and to manually audit the code that they flag. A fix is expected to be included in the Fixed in
0.8.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.2.4
unknown
Dependencies (8)
|