CVE-2026-85438
9.8MOOS-IvP · MOOS-IvP
MOOS-IvP contains a buffer overflow in StringToIvPFunction() due to unvalidated payload counts, allowing attackers to trigger memory corruption via crafted BHV_IPF payloads.
Executive summary
A buffer overflow vulnerability in the MOOS-IvP library allows unauthenticated remote attackers to achieve arbitrary code execution via crafted BHV_IPF payloads.
Vulnerability
The application fails to perform bounds checking on dimension, piece, and degree counts when processing encoded BHV_IPF payloads. This allows an unauthenticated attacker to supply malformed input that triggers an out of bounds write, leading to memory corruption and potential code execution.
Business impact
Successful exploitation of this vulnerability poses a critical risk to organizational infrastructure, as it allows for unauthorized remote code execution on systems running the affected software. This could result in a complete system compromise, unauthorized access to sensitive data, or severe operational disruption. Given the CVSS score of 9.8, the vulnerability is classified as critical, requiring immediate attention to prevent potential exploitation.
Remediation
Immediate Action: Update the MOOS-IvP installation to the latest version, which contains the necessary bounds checking logic to prevent the buffer overflow.
Proactive Monitoring: Monitor system logs for unusual process crashes or unexpected service restarts, which may indicate attempted exploitation of memory corruption vulnerabilities.
Compensating Controls: Deploy a Web Application Firewall or intrusion detection system to inspect incoming traffic for malformed BHV_IPF payloads that exhibit mismatched dimension or count values.
Exploitation status
Public Exploit Available: No (exploit_available unknown).
Analyst recommendation
Due to the critical severity and the potential for remote code execution, organizations must prioritize patching this vulnerability immediately. Ensure all instances of MOOS-IvP are updated to the latest available version to eliminate the underlying memory safety flaw. If an immediate update is not feasible, restrict network access to the affected service to trusted segments to reduce the attack surface.
More MOOS-IvP CVEs
Sources
Originally found and disclosed by Vlatko Kosturjak, per the CVE Program record.
- Pull Request #126 Issue tracker
- Proposed fix commit (pull request not merged) Patch commit
- github.com
- FunctionEncoder.cpp (verified sink) Technical analysis
- VulnCheck Advisory: MOOS-IvP through 24.8.1 Out-of-Bounds Write via Unvalidated IvP Payload Counts Third-party advisory