A NULL pointer dereference flaw was found in the way mod_dav_svn handled REPORT requests. A remote, unauthenticated attacker could use a crafted REPORT request to crash mod_dav_svn. Versions 1.0.0 up to and including 1.7.18, and 1.8.0 up to and including 1.8.10, are affected. This issue will be fixed in versions 1.7.19 and 1.8.11. Acknowledgements: Red Hat would like to thank the Subversion project for reporting this issue. Upstream acknowledges Evgeny Kotkov of VisualSVN as the original reporter.
Created attachment 968769 [details] 1.7.18 patch from upstream
Created attachment 968770 [details] 1.8.10 patch from upstream
External References: http://subversion.apache.org/security/CVE-2014-3580-advisory.txt
Created subversion tracking bugs for this issue: Affects: fedora-all [bug 1174521]
subversion-1.8.11-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
subversion-1.8.11-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
Analysis ======== In the code of subversion there missing sanity check for repository path at various places, sending crafted report request causes crash because of NULL pointer dereference. In function dav_svn__get_deleted_rev_report(const dav_resource *resource, const apr_xml_doc *doc, ap_filter_t *output) reaching this line in the code of function dav_svn__get_deleted_rev_report() would cause a crash if repository path is not set or is NULL causing NULL pointer dereference abs_path = svn_path_join(resource->info->repos_path, rel_path, resource->pool); Similar problem exists in various other places of the subversion code.
This issue has been addressed in the following products: Red Hat Enterprise Linux 6 Via RHSA-2015:0165 https://rhn.redhat.com/errata/RHSA-2015-0165.html
This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Via RHSA-2015:0166 https://rhn.redhat.com/errata/RHSA-2015-0166.html
Statement: Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/.