Robocode vulnerable to Directory Traversal in recursivelyDelete Method

The impact of this vulnerability is significant. An attacker who successfully exploits CVE-2025-14306 can gain unauthorized access to delete files on the system where Robocode Core is running. This could lead to data loss, system instability, or even denial of service. The recursiveDelete method's failure to properly sanitize file paths is the root cause, enabling attackers to bypass intended security controls. The potential for widespread damage depends on the permissions granted to the Robocode process and the sensitivity of the files it has access to. While Robocode is primarily a programming education tool, its use in automated trading or other sensitive contexts could amplify the impact significantly.

Robocode users, particularly those utilizing older versions (≤1.9.5.5), are at risk. This includes educational institutions using Robocode for programming instruction, as well as individuals or organizations using Robocode for automated trading or other applications where file system access is required. Shared hosting environments where Robocode is installed could also be affected if the underlying system is vulnerable.

• java: Monitor Robocode process for unusual file deletion activity using system monitoring tools. • java: Examine Robocode logs for suspicious file path manipulation attempts. • generic web: If Robocode is exposed via a web interface, monitor access logs for requests containing unusual file path parameters. • generic web: Check for unexpected files appearing in the Robocode cache directory.

1. 2025-12-09Disclosure

   Public Disclosure

1. 予約済み2025-12-09
2. 公開日2025-12-09
3. EPSS 更新日2026-03-23

The primary mitigation for CVE-2025-14306 is to upgrade Robocode Core to version 1.9.5.6 or later. If upgrading is not immediately feasible, consider restricting the permissions of the Robocode process to minimize the potential damage from unauthorized file deletions. While a direct WAF rule is unlikely to be effective due to the nature of the vulnerability, monitoring file system activity for unexpected deletions originating from the Robocode process can provide an early warning. There are no specific Sigma or YARA rules readily available for this vulnerability, but monitoring for unusual file deletion patterns within the Robocode directory is recommended.