{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-67901 exists.","fix":"No fix has been published for CVE-2025-67901 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-67901 is a medium-severity vulnerability in kristapsdz openrsync, published on 14 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-67901 and fix it if it is affected.\n\nWhat it is: CVE-2025-67901 is a medium-severity vulnerability in kristapsdz openrsync, published on 14 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-67901 exists.\n\nAffected product: kristapsdz openrsync. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-67901/ (Markdown: https://insights.sbomify.com/CVE-2025-67901/index.md)","id":"CVE-2025-67901","markdown":"https://insights.sbomify.com/CVE-2025-67901/index.md","name":"CVE-2025-67901","record":{"aliases":["GHSA-cwrr-xmm2-f4jr"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"openrsync file sync","requires_auth":"low_privilege","summary":"A remote attacker can crash the openrsync server by sending a zero-length block data request, causing a segmentation fault.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-1284","name":"Improper Validation of Specified Quantity in Input"}],"description":"openrsync through 0.5.0, as used in OpenBSD through 7.8 and on other platforms, allows a client to cause a server SIGSEGV by specifying a length of zero for block data, because the relationship between p-\u003erem and p-\u003elen is not checked.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Null dereference in openrsync","id":"CVE-2025-67901","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2025-67903"},"packages":[],"prev":{"headline":"Code injection in NXLog Agent","id":"CVE-2025-67900"},"products":["openrsync"],"published":"2025-12-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-15","vendors":["kristapsdz"]},"summary":"A remote attacker can crash the openrsync server by sending a zero-length block data request, causing a segmentation fault.","url":"https://insights.sbomify.com/CVE-2025-67901/"}