Tuleap fehlender CSRF-Schutz bei der Verwaltung von SVN-Commit-Regeln und unveränderlichen Tags

An attacker can exploit this CSRF vulnerability to gain unauthorized control over SVN repositories managed by Tuleap. By crafting malicious requests and tricking authenticated users into executing them, an attacker could modify commit rules, potentially allowing unauthorized code changes or bypassing security controls. They could also alter immutable tags, disrupting version control and potentially leading to data corruption or loss. The impact is particularly severe in environments where SVN is used for critical software development or deployment pipelines, as a successful attack could compromise the integrity of the entire codebase.

Organizations heavily reliant on Tuleap for software development and version control, particularly those using SVN for critical projects, are at risk. Environments with shared Tuleap instances or those lacking robust user awareness training are also more vulnerable to CSRF attacks.

• php: Examine Tuleap application logs for unusual requests related to SVN commit rule or immutable tag modifications. Look for requests originating from unexpected sources or with suspicious parameters.

grep -i 'svn commit rule|immutable tag' /var/log/tuleap/application.log

• generic web: Monitor access logs for requests to SVN management endpoints with unusual HTTP referer headers. This can indicate a potential CSRF attempt.

curl -I <tuleap_url>/svn/management/endpoint | grep Referer

1. 2025-11-12Disclosure

   disclosure

1. Reserviert2025-10-27
2. Veröffentlicht2025-11-12
3. EPSS aktualisiert2026-03-23

The primary mitigation for CVE-2025-64117 is to upgrade Tuleap to a patched version: 16.13.99.1761813675, 16.13-5, or 16.12-8. If an immediate upgrade is not feasible, consider implementing stricter access controls and input validation on SVN commit rule and immutable tag management interfaces. Implementing a Content Security Policy (CSP) with strict origin restrictions can also help mitigate CSRF attacks. Regularly review SVN commit logs for any suspicious activity. After upgrading, confirm the fix by attempting to trigger a CSRF request and verifying that it is blocked.