{"answers":{"affected":"3 open source packages ship an affected version, including sqlx.","exploited":"There is no known exploitation of GHSA-xmrp-424f-vfpx in the wild and no public exploit code.","fix":"Upgrade sqlx to 0.8.1 or later.","what":"GHSA-xmrp-424f-vfpx is a vulnerability in sqlx, published on 15 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-xmrp-424f-vfpx and fix it if it is affected.\n\nWhat it is: GHSA-xmrp-424f-vfpx is a vulnerability in sqlx, published on 15 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-xmrp-424f-vfpx in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- sqlx (crates.io): affected all versions; fixed in 0.8.1\n- sqlx (crates.io): affected all versions; fixed in 0.8.1\n- sqlx (crates.io): affected from 0.0.0-0; fixed in 0.8.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-xmrp-424f-vfpx/ (Markdown: https://insights.sbomify.com/GHSA-xmrp-424f-vfpx/index.md)","id":"GHSA-xmrp-424f-vfpx","markdown":"https://insights.sbomify.com/GHSA-xmrp-424f-vfpx/index.md","name":"GHSA-xmrp-424f-vfpx","record":{"aliases":["RUSTSEC-2024-0363"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust SQL library","requires_auth":"none","summary":"An integer overflow in SQLx allows attackers to smuggle queries via oversized inputs, potentially leading to code execution or data modification.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:\n\n\u003e SQL Injection isn't Dead: Smuggling Queries at the Protocol Level  \n\u003e \u003chttp://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\u003e  \n\u003e (Archive link for posterity.)\n\nEssentially, encoding a value larger than 4GiB can cause the length prefix in the protocol to overflow, \ncausing the server to interpret the rest of the string as binary protocol commands or other data.\n\nIt appears SQLx _does_ perform truncating casts in a way that could be problematic, \nfor example: \u003chttps://github.com/launchbadge/sqlx/blob/6f2905695b9606b5f51b40ce10af63ac9e696bb8/sqlx-postgres/src/arguments.rs#L163\u003e\n\nThis code has existed essentially since the beginning, \nso it is reasonable to assume that all published versions `\u003c= 0.8.0` are affected.\n\n## Mitigation\n\nAs always, you should make sure your application is validating untrustworthy user input. \nReject any input over 4 GiB, or any input that could _encode_ to a string longer than 4 GiB. \nDynamically built queries are also potentially problematic if it pushes the message size over this 4 GiB bound.\n\n[`Encode::size_hint()`](https://docs.rs/sqlx/latest/sqlx/trait.Encode.html#method.size_hint) \ncan be used for sanity checks, but do not assume that the size returned is accurate. \nFor example, the `Json\u003cT\u003e` and `Text\u003cT\u003e` adapters have no reasonable way to predict or estimate the final encoded size, \nso they just return `size_of::\u003cT\u003e()` instead.\n\nFor web application backends, consider adding some middleware that limits the size of request bodies by default.\n\n## Resolution\n\nWork has started on a branch to add `#[deny]` directives for the following Clippy lints:\n\n* [`cast_possible_truncation`](https://rust-lang.github.io/rust-clippy/master/#/cast_possible_truncation)\n* [`cast_possible_wrap`](https://rust-lang.github.io/rust-clippy/master/#/cast_possible_wrap)\n* [`cast_sign_loss`](https://rust-lang.github.io/rust-clippy/master/#/cast_sign_loss)\n\nand to manually audit the code that they flag.\n\nA fix is expected to be included in the `0.8.1` release (still WIP as of writing).","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"SQLx Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts","id":"GHSA-xmrp-424f-vfpx","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"integer_overflow","year":"2024"},"n_packages":3,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.8.1"],"introduced":["0"],"last_affected":[],"package":"sqlx","purl":null,"source":"GHSA-xmrp-424f-vfpx"},{"ecosystem":"crates.io","fixed":["0.8.1"],"introduced":["0"],"last_affected":[],"package":"sqlx","purl":"pkg:cargo/sqlx","source":"GHSA-xmrp-424f-vfpx"},{"ecosystem":"crates.io","fixed":["0.8.1"],"introduced":["0.0.0-0"],"last_affected":[],"package":"sqlx","purl":"pkg:cargo/sqlx","source":"RUSTSEC-2024-0363"}],"products":null,"published":"2024-08-15","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"An integer overflow in SQLx allows attackers to smuggle queries via oversized inputs, potentially leading to code execution or data modification.","url":"https://insights.sbomify.com/GHSA-xmrp-424f-vfpx/"}