Subversion - Remote Assertion DoS and Spoofing Vulnerabilities

subversion Updated 02 Oct 2025

Summary

21/04/2015
N/A
Yes i
Unrated
Not published

DSA-3231-1: subversion - security update. Affects subversion versions < 1.6.17dfsg-4+deb7u9. Fixed in 1.6.17dfsg-4+deb7u9. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Subversion is a popular version control system used for managing and tracking changes to files and directories. It provides a centralized repository for storing and sharing code, allowing multiple users to collaborate on projects. Subversion supports various protocols, including HTTP, HTTPS, and SVN, making it versatile and widely adopted in software development workflows. However, certain versions of Subversion are susceptible to remote assertion denial-of-service (DoS) attacks and spoofing vulnerabilities.

Vulnerability Detail

The first vulnerability, identified as CVE-2015-0248, affects Subversion mod_dav_svn and svnserve. It allows remote attackers to trigger a DoS condition by sending specific requests with dynamically evaluated revision numbers. This vulnerability can lead to service disruption and potential crashes.

The second vulnerability, known as CVE-2015-0251, affects Subversion HTTP servers. It enables attackers to spoof svn:author property values for new revisions by exploiting specially crafted v1 HTTP protocol request sequences. This vulnerability can be leveraged to manipulate revision history and potentially deceive users about the origin of code changes.

How To Fix

Minimum fixed version

1.6.17dfsg-4+deb7u9

This is the first release that contains the fix.

sudo apt-get install --only-upgrade subversion

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Conclusion

Subversion versions prior to the fixed versions mentioned in this report are vulnerable to remote assertion DoS and spoofing attacks. It is highly recommended to upgrade to the latest patched versions to mitigate these vulnerabilities and ensure the security of your Subversion installation. For further assistance or support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for subversion →

Share this vulnerability

FAQ

Subversion is a version control system used for managing and tracking changes to files and directories in software development projects. It provides a centralized repository and supports various protocols for accessing and manipulating code.

A remote assertion DoS vulnerability refers to a security flaw that allows remote attackers to trigger assertion failures in software, leading to a denial-of-service condition. In the case of Subversion, certain requests with dynamically evaluated revision numbers can cause the server to crash or become unresponsive.

The spoofing vulnerability in Subversion HTTP servers enables attackers to manipulate svn:author property values for new revisions. This can be used to deceive users about the origin of code changes, potentially leading to trust issues and security concerns.

No, only specific versions of Subversion are affected. The fixed versions for the stable distribution (wheezy), upcoming stable distribution (jessie), and unstable distribution (sid) are mentioned in the 'how_to_fix' section.

To ensure the security of your Subversion installation, it is crucial to regularly update to the latest patched versions provided by the Subversion project. Additionally, following best practices for secure configuration and access control can further enhance the overall security posture.

Related vulnerabilities

Recent vulnerabilities recorded for subversion.

How To Fix

Minimum fixed version

1.6.17dfsg-4+deb7u9

This is the first release that contains the fix.

sudo apt-get install --only-upgrade subversion

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback