Critical Filename Validation Vulnerability in Subversion Affects Multiple Debian Releases
Summary
DEBIAN-CVE-2024-46901: Insufficient validation of filenames against control characters in Apache Subversion repositories served via mod_dav_svn allows authenticated users with commit access to commit a corrupted revision, leading to disruption... Affects subversion versions < 1.14.1-3+deb11u2. Fixed in 1.14.1-3+deb11u2. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Subversion is a widely-used version control system that allows users to manage and track changes to files and directories over time. It is particularly popular in collaborative environments where multiple users need to work on the same project. The package is known for its robust features, including support for branching and merging, and it can serve repositories via various access methods, including mod_dav_svn. However, a recent vulnerability has been identified that affects its integrity when serving repositories through this method.
Vulnerability Detail
The vulnerability arises from insufficient validation of filenames against control characters in Apache Subversion repositories served via mod_dav_svn. This flaw allows authenticated users with commit access to submit a corrupted revision, potentially disrupting the functionality of the repository for all users. All versions of Subversion up to and including 1.14.4 are affected when using mod_dav_svn, making it critical for users to address this issue promptly to maintain repository integrity.
How To Fix
Minimum fixed version
1.14.1-3+deb11u2
This is the first release that contains the fix.
sudo apt-get install --only-upgrade subversionTip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
If immediate upgrading is not feasible, users can temporarily mitigate the risk by disabling mod_dav_svn for their repositories until the upgrade can be performed. This can be done by commenting out or removing the relevant configuration lines in the Apache configuration file.
Conclusion
The identified vulnerability in Subversion poses a significant risk to users who serve repositories via mod_dav_svn. It is crucial for users to upgrade to the patched versions to ensure the integrity and security of their repositories. Utilizing tools like Vulert can further enhance monitoring and protection against such vulnerabilities.
See every vulnerability recorded for subversion →
FAQ
All versions of Subversion up to and including 1.14.4 are affected when serving repositories via mod_dav_svn.
Authenticated users with commit access could submit corrupted revisions, leading to disruptions for all users of the repository.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Check your application against this vulnerability using the Vulert playground at Vulert Scanner without any signup.
Yes, you can disable mod_dav_svn in your Apache configuration to prevent the vulnerability from being exploited until you can upgrade.
Vulert is a tool that monitors open-source vulnerabilities in your software using just a manifest file like package-lock.json. It provides real-time alerts for vulnerabilities.
References
Related vulnerabilities
Recent vulnerabilities recorded for subversion.
