{"answers":{"affected":"2 open source packages ship an affected version, including process-sync. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-48752 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-48752 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-48752 is a low-severity use after free vulnerability in Forestryks process-sync-rs, published on 24 May 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-48752 and fix it if it is affected.\n\nWhat it is: CVE-2025-48752 is a low-severity use after free vulnerability in Forestryks process-sync-rs, published on 24 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-48752 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- process-sync (crates.io): affected all versions up to 0.2.2; no fix listed\n- process-sync (crates.io): affected all versions up to 0.2.2; 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/CVE-2025-48752/ (Markdown: https://insights.sbomify.com/CVE-2025-48752/index.md)","id":"CVE-2025-48752","markdown":"https://insights.sbomify.com/CVE-2025-48752/index.md","name":"CVE-2025-48752","record":{"aliases":["GHSA-mqwx-r894-9hfp"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Rust process-sync crate","requires_auth":"none","summary":"A missing mutex unlock check in the process-sync crate allows use-after-free, potentially leading to code execution or crashes.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"process-sync","vendor":"forestryks"}],"cvss":{"score":2.9,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-416","name":"Use After Free"}],"description":"In the process-sync crate 0.2.2 for Rust, the drop function lacks a check for whether the pthread_mutex is unlocked.","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Process Sync has a Potential Unsound Issue in SharedMutex","id":"CVE-2025-48752","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"use_after_free","year":"2025"},"n_packages":2,"n_references":2,"next":{"headline":"Race condition in anode","id":"CVE-2025-48753"},"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.2.2"],"package":"process-sync","purl":null,"source":"GHSA-mqwx-r894-9hfp"},{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.2.2"],"package":"process-sync","purl":"pkg:cargo/process-sync","source":"GHSA-mqwx-r894-9hfp"}],"prev":{"headline":"process_lock has a Potential Unsound issue in unlock","id":"CVE-2025-48751"},"products":["process-sync-rs"],"published":"2025-05-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-05-24","vendors":["Forestryks"]},"summary":"A missing mutex unlock check in the process-sync crate allows use-after-free, potentially leading to code execution or crashes.","url":"https://insights.sbomify.com/CVE-2025-48752/"}