{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-62000 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-62000 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-62000 is a medium-severity vulnerability in BullWall Ransomware Containment, published on 18 Dec 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-62000 and fix it if it is affected.\n\nWhat it is: CVE-2025-62000 is a medium-severity vulnerability in BullWall Ransomware Containment, published on 18 Dec 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-62000 in the wild and no public exploit code.\n\nAffected product: BullWall Ransomware Containment. 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-62000/ (Markdown: https://insights.sbomify.com/CVE-2025-62000/index.md)","id":"CVE-2025-62000","markdown":"https://insights.sbomify.com/CVE-2025-62000/index.md","name":"CVE-2025-62000","record":{"aliases":["GHSA-cv2v-p23m-2q4h"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Ransomware containment software","requires_auth":"low_privilege","summary":"An authenticated attacker can bypass a specific ransomware detection method by preserving file headers, though other integrity checks may still detect the encryption.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"cisa-cg","cpe":[{"product":"ransomware_containment","vendor":"bullwall"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-1023","name":"Incomplete Comparison with Missing Factors"}],"description":"BullWall Ransomware Containment may not always detect an encrypted file. This issue affects a specific file inspection method that evaluates file content based on header bytes. An authenticated attacker could encrypt files, preserving the first four bytes and preventing this particular method from triggering. The affected product implements additional integrity-based detection mechanisms capable of identifying file corruption or encryption for some common file extensions independent of header bytes. As a result, this vulnerability does not represent a complete bypass of ransomware detection, but a limitation of one detection method when evaluated independently. Versions 4.6.0.0, 4.6.0.6, 4.6.0.7, and 4.6.1.4 are affected. Other versions may also be affected. BullWall plans to improve detection method documentation.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"BullWall Ransomware Containment incomplete file inspection","id":"CVE-2025-62000","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"BullWall Ransomware Containment hard-coded folder exclusions","id":"CVE-2025-62001"},"packages":[],"prev":{"headline":"OPEXUS FOIAXpress stored XSS via logo image","id":"CVE-2025-61999"},"products":["Ransomware Containment"],"published":"2025-12-18","related":[{"cvss_score":8.7,"headline":"BullWall Ransomware Containment hard-coded folder exclusions","id":"CVE-2025-62001","kev_date_added":null,"published":"2025-12-18"},{"cvss_score":5.3,"headline":"BullWall Ransomware Containment file count detection bypass","id":"CVE-2025-62002","kev_date_added":null,"published":"2025-12-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"2026-01-15","vendors":["BullWall"]},"summary":"An authenticated attacker can bypass a specific ransomware detection method by preserving file headers, though other integrity checks may still detect the encryption.","url":"https://insights.sbomify.com/CVE-2025-62000/"}