{"answers":{"affected":"3 open source packages ship an affected version, including scratchpad.","exploited":"There is no known exploitation of GHSA-77h3-w9rx-hj3q in the wild and no public exploit code.","fix":"No fix has been published for GHSA-77h3-w9rx-hj3q yet. Limit exposure of the affected software until one is available.","what":"GHSA-77h3-w9rx-hj3q is a memory corruption vulnerability in scratchpad, published on 14 Aug 2025."},"fix_prompt":"Check this codebase for GHSA-77h3-w9rx-hj3q and fix it if it is affected.\n\nWhat it is: GHSA-77h3-w9rx-hj3q is a memory corruption vulnerability in scratchpad, published on 14 Aug 2025. \nExploitation: There is no known exploitation of GHSA-77h3-w9rx-hj3q in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- scratchpad (crates.io): affected all versions up to 1.3.1; no fix listed\n- scratchpad (crates.io): affected all versions up to 1.3.1; no fix listed\n- scratchpad (crates.io): affected from 0.0.0-0; no fix listed\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-77h3-w9rx-hj3q/ (Markdown: https://insights.sbomify.com/GHSA-77h3-w9rx-hj3q/index.md)","id":"GHSA-77h3-w9rx-hj3q","markdown":"https://insights.sbomify.com/GHSA-77h3-w9rx-hj3q/index.md","name":"GHSA-77h3-w9rx-hj3q","record":{"aliases":["RUSTSEC-2025-0049"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["code_execution","denial_of_service"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust scratchpad library","requires_auth":"none","summary":"A Rust library allows heap buffer overflows via user-defined trait implementations, potentially enabling arbitrary code execution or crashes.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"The `get` and `set` methods of the public trait `scratchpad::Tracking` interact with unsafe code regions in the crate, and they influence the computation of addresses returned as raw pointers. However, the trait itself is not marked as unsafe, meaning users may provide custom implementations under the assumption that the crate upholds all safety guarantees.\n\nThis becomes problematic because even safe implementations of `get` and `set`-written without using any unsafe code-can still result in ill-formed raw pointers. These pointers may later be dereferenced within safe APIs of the crate (e.g., `marker::MarkerBack::allocate_slice_copy`), potentially leading to arbitrary memory access or heap buffer overflows.\n\nAccording to the [penultimate commit](https://github.com/okready/scratchpad/commit/957dee1a3902f48600b06910e8e0b1d5ee7dab83), the crate is in maintenance mode awaiting a cleanup that will reduce the area of unsafe code. Note that the last commits to the repository are from 4 years ago.","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":false,"headline":"User-defined implementations of the safe trait scratchpad::Tracking can cause heap buffer overflows","id":"GHSA-77h3-w9rx-hj3q","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":3,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["1.3.1"],"package":"scratchpad","purl":null,"source":"GHSA-77h3-w9rx-hj3q"},{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["1.3.1"],"package":"scratchpad","purl":"pkg:cargo/scratchpad","source":"GHSA-77h3-w9rx-hj3q"},{"ecosystem":"crates.io","fixed":[],"introduced":["0.0.0-0"],"last_affected":[],"package":"scratchpad","purl":"pkg:cargo/scratchpad","source":"RUSTSEC-2025-0049"}],"products":null,"published":"2025-08-14","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":"A Rust library allows heap buffer overflows via user-defined trait implementations, potentially enabling arbitrary code execution or crashes.","url":"https://insights.sbomify.com/GHSA-77h3-w9rx-hj3q/"}