{"answers":{"affected":"2 open source packages ship an affected version, including process_lock. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-48751 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-48751 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-48751 is a low-severity vulnerability in tickbh ProcessLock, 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-48751 and fix it if it is affected.\n\nWhat it is: CVE-2025-48751 is a low-severity vulnerability in tickbh ProcessLock, 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-48751 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- process_lock (crates.io): affected all versions up to 0.1.0; no fix listed\n- process_lock (crates.io): affected all versions up to 0.1.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/CVE-2025-48751/ (Markdown: https://insights.sbomify.com/CVE-2025-48751/index.md)","id":"CVE-2025-48751","markdown":"https://insights.sbomify.com/CVE-2025-48751/index.md","name":"CVE-2025-48751","record":{"aliases":["GHSA-6v24-6wgf-8vj6"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Rust process lock library","requires_auth":"none","summary":"A data race in the unlock function of the process_lock crate allows attackers to cause data corruption or crashes.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"process_lock","vendor":"tickbh"}],"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-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"The process_lock crate 0.1.0 for Rust allows data races in unlock.","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_lock has a Potential Unsound issue in unlock","id":"CVE-2025-48751","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"race_condition","year":"2025"},"n_packages":2,"n_references":2,"next":{"headline":"Process Sync has a Potential Unsound Issue in SharedMutex","id":"CVE-2025-48752"},"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.1.0"],"package":"process_lock","purl":null,"source":"GHSA-6v24-6wgf-8vj6"},{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.1.0"],"package":"process_lock","purl":"pkg:cargo/process_lock","source":"GHSA-6v24-6wgf-8vj6"}],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2025-48749"},"products":["ProcessLock"],"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":["tickbh"]},"summary":"A data race in the unlock function of the process_lock crate allows attackers to cause data corruption or crashes.","url":"https://insights.sbomify.com/CVE-2025-48751/"}