It was found that when an SVN server (both svnserve and httpd with the mod_dav_svn module) searched the history of a file or a directory, it would disclose its location in the repository if that file or directory was not readable (for example, if it had been moved).
DescriptionVasyl Kaigorodov
2015-07-27 16:09:54 UTC
Upstream has reported the below security vulnerability in Subversion:
Summary
=======
Subversion servers, both httpd and svnserve, will reveal some paths
that should be hidden by path-based authz. When a node is copied
from an unreadable location to a readable location the unreadable
path may be revealed. This vulnerablity only reveals the path, it
does not reveal the contents of the path.
Known vulnerable
================
Subversion 1.8.0 to 1.8.13
Subversion 1.7.0 to 1.7.20
All older versions
Known fixed
===========
Subversion 1.8.14
Subversion 1.7.21
Details
=======
The function svn_repos_trace_node_locations() follows the history of
a node through earlier revisions and shows any copies. It should
stop following history when an unreadable path is encountered but an
implementation error causes the first unreadable path to be returned
in some circumstances. This only reveals the unreadable path, it
does not reveal the content of the file or directory at that path.
Any attempts to obtain the content will fail with an authorization
error.
Examples:
1. After copying "unreadable-path" to "readable-path" then following
the history of "readable-path" may reveal "unreadable-path".
2. After copying "unreadable/some-path" to "readable/other-path"
then following the history of "readable/other-path" may reveal
"unreadable/some-path".
Acknowledgements:
Red Hat would like to thank Apache Software Foundation for reporting this issue. Upstream acknowledges C. Michael Pilato, CollabNet, as the original reporter.
Comment 14Huzaifa S. Sidhpurwala
2015-09-15 06:01:27 UTC
Statement:
This issue affects the version of subversion as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low 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/.
Upstream has reported the below security vulnerability in Subversion: Summary ======= Subversion servers, both httpd and svnserve, will reveal some paths that should be hidden by path-based authz. When a node is copied from an unreadable location to a readable location the unreadable path may be revealed. This vulnerablity only reveals the path, it does not reveal the contents of the path. Known vulnerable ================ Subversion 1.8.0 to 1.8.13 Subversion 1.7.0 to 1.7.20 All older versions Known fixed =========== Subversion 1.8.14 Subversion 1.7.21 Details ======= The function svn_repos_trace_node_locations() follows the history of a node through earlier revisions and shows any copies. It should stop following history when an unreadable path is encountered but an implementation error causes the first unreadable path to be returned in some circumstances. This only reveals the unreadable path, it does not reveal the content of the file or directory at that path. Any attempts to obtain the content will fail with an authorization error. Examples: 1. After copying "unreadable-path" to "readable-path" then following the history of "readable-path" may reveal "unreadable-path". 2. After copying "unreadable/some-path" to "readable/other-path" then following the history of "readable/other-path" may reveal "unreadable/some-path". Acknowledgements: Red Hat would like to thank Apache Software Foundation for reporting this issue. Upstream acknowledges C. Michael Pilato, CollabNet, as the original reporter.