{"answers":{"affected":"2 open source packages ship an affected version, including net.sf.robocode:robocode.battle. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-14307 in the wild and no public exploit code.","fix":"Upgrade net.sf.robocode:robocode.battle to 1.9.5.6 or later.","what":"CVE-2025-14307 is a critical vulnerability in Robocode, published on 9 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-14307 and fix it if it is affected.\n\nWhat it is: CVE-2025-14307 is a critical vulnerability in Robocode, published on 9 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-14307 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- net.sf.robocode:robocode.battle (Maven): affected all versions; fixed in 1.9.5.6\n- net.sf.robocode:robocode.battle (Maven): affected all versions; fixed in 1.9.5.6\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-14307/ (Markdown: https://insights.sbomify.com/CVE-2025-14307/index.md)","id":"CVE-2025-14307","markdown":"https://insights.sbomify.com/CVE-2025-14307/index.md","name":"CVE-2025-14307","record":{"aliases":["DEBIAN-CVE-2025-14307","GHSA-2mxr-rc97-xrj2","UBUNTU-CVE-2025-14307"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Robocode game engine","requires_auth":"low_privilege","summary":"Attackers can exploit insecure temporary file creation in Robocode to execute arbitrary code or overwrite files via race conditions.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GovTech CSG","cpe":[{"product":"robocode","vendor":"robocode"}],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/AU:Y/R:U/V:D/RE:M/U:Red","version":"4.0"},"cwes":[{"id":"CWE-377","name":"DEPRECATED: Insecure Temporary File"}],"description":"An insecure temporary file creation vulnerability exists in the AutoExtract component of Robocode version 1.9.3.6. The createTempFile method fails to securely create temporary files, allowing attackers to exploit race conditions and potentially execute arbitrary code or overwrite critical files. This vulnerability can be exploited by manipulating the temporary file creation process, leading to potential unauthorized actions.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Insecure Temporary File Creation in Robocode's AutoExtract Component","id":"CVE-2025-14307","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"race_condition","year":"2025"},"n_packages":2,"n_references":1,"next":{"headline":"Integer Overflow in Robocode's Buffer Write Method","id":"CVE-2025-14308"},"packages":[{"ecosystem":"Maven","fixed":["1.9.5.6"],"introduced":["0"],"last_affected":[],"package":"net.sf.robocode:robocode.battle","purl":null,"source":"GHSA-2mxr-rc97-xrj2"},{"ecosystem":"Maven","fixed":["1.9.5.6"],"introduced":["0"],"last_affected":[],"package":"net.sf.robocode:robocode.battle","purl":"pkg:maven/net.sf.robocode/robocode.battle","source":"GHSA-2mxr-rc97-xrj2"}],"prev":{"headline":"Directory Traversal in Robocode's CacheCleaner Component","id":"CVE-2025-14306"},"products":["Robocode"],"published":"2025-12-09","related":[{"cvss_score":10,"headline":"Directory Traversal in Robocode's CacheCleaner Component","id":"CVE-2025-14306","kev_date_added":null,"published":"2025-12-09"},{"cvss_score":10,"headline":"Integer Overflow in Robocode's Buffer Write Method","id":"CVE-2025-14308","kev_date_added":null,"published":"2025-12-09"},{"cvss_score":9.8,"headline":"Improper Input Validation in net.sf.robocode:robocode.host allows for external service interaction","id":"CVE-2019-10648","kev_date_added":null,"published":"2019-03-30"},{"cvss_score":7.5,"headline":"Other in n/a","id":"CVE-2008-2078","kev_date_added":null,"published":"2008-05-05"},{"cvss_score":6.8,"headline":"Robocode Arbitrary Code Execution","id":"CVE-2007-6382","kev_date_added":null,"published":"2007-12-15"}],"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":"total"},"state":"PUBLISHED","updated":"2025-12-09","vendors":["Robocode Project"]},"summary":"Attackers can exploit insecure temporary file creation in Robocode to execute arbitrary code or overwrite files via race conditions.","url":"https://insights.sbomify.com/CVE-2025-14307/"}