{"answers":{"affected":"3 open source packages ship an affected version, including diesel.","exploited":"There is no known exploitation of GHSA-wq9x-qwcq-mmgf in the wild and no public exploit code.","fix":"Upgrade diesel to 2.2.3 or later.","what":"GHSA-wq9x-qwcq-mmgf is a vulnerability in diesel, published on 23 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-wq9x-qwcq-mmgf and fix it if it is affected.\n\nWhat it is: GHSA-wq9x-qwcq-mmgf is a vulnerability in diesel, published on 23 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-wq9x-qwcq-mmgf in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- diesel (crates.io): affected all versions; fixed in 2.2.3\n- diesel (crates.io): affected all versions; fixed in 2.2.3\n- diesel (crates.io): affected from 0.0.0-0; fixed in 2.2.3\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-wq9x-qwcq-mmgf/ (Markdown: https://insights.sbomify.com/GHSA-wq9x-qwcq-mmgf/index.md)","id":"GHSA-wq9x-qwcq-mmgf","markdown":"https://insights.sbomify.com/GHSA-wq9x-qwcq-mmgf/index.md","name":"GHSA-wq9x-qwcq-mmgf","record":{"aliases":["RUSTSEC-2024-0365"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust ORM library","requires_auth":"none","summary":"An integer overflow in Diesel's binary protocol handling allows attackers to smuggle SQL queries, 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 Diesel Gitter Channel:\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.)\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 Diesel _does_ perform truncating casts in a way that could be problematic, \nfor example: \u003chttps://github.com/diesel-rs/diesel/blob/ae82c4a5a133db65612b7436356f549bfecda1c7/diesel/src/pg/connection/stmt/mod.rs#L36\u003e\n\nThis code has existed essentially since the beginning, \nso it is reasonable to assume that all published versions `\u003c= 2.2.2` are affected.\n\n## Mitigation\n\nThe prefered migration to the outlined problem is to update to a Diesel version newer than 2.2.2, which includes \nfixes for the problem. \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\nFor web application backends, consider adding some middleware that limits the size of request bodies by default.\n\n## Resolution\n\nDiesel now uses `#[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\nto prevent casts that will lead to precision loss or other trunctations. Additionally we performed an \naudit of the relevant code.\n\nA fix is included in the `2.2.3` release.","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":"Diesel vulnerable to Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts","id":"GHSA-wq9x-qwcq-mmgf","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":["2.2.3"],"introduced":["0"],"last_affected":[],"package":"diesel","purl":null,"source":"GHSA-wq9x-qwcq-mmgf"},{"ecosystem":"crates.io","fixed":["2.2.3"],"introduced":["0"],"last_affected":[],"package":"diesel","purl":"pkg:cargo/diesel","source":"GHSA-wq9x-qwcq-mmgf"},{"ecosystem":"crates.io","fixed":["2.2.3"],"introduced":["0.0.0-0"],"last_affected":[],"package":"diesel","purl":"pkg:cargo/diesel","source":"RUSTSEC-2024-0365"}],"products":null,"published":"2024-08-23","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 Diesel's binary protocol handling allows attackers to smuggle SQL queries, potentially leading to code execution or data modification.","url":"https://insights.sbomify.com/GHSA-wq9x-qwcq-mmgf/"}