Subversion 1.0.6 is ready. Grab it from: http://subversion.tigris.org/tarballs/subversion-1.0.6.tar.gz http://subversion.tigris.org/tarballs/subversion-1.0.6.tar.bz2 The MD5 checksums are: 160c655194dff55f9fdd856110801d01 subversion-1.0.6.tar.gz bb05fe041fef7491b3555904d97f5e1c subversion-1.0.6.tar.bz2 PGP Signatures are available at: http://subversion.tigris.org/tarballs/subversion-1.0.6.tar.gz.asc http://subversion.tigris.org/tarballs/subversion-1.0.6.tar.bz2.asc PGP Signatures will be made by the following person(s) for this release: Ben Reser [1024D/641E358B] with fingerprint: 42F5 91FD E577 F545 FB40 8F6B 7241 856B 641E 358B This is likely the last bugfix release in the 1.0.x line. Subversion versions up to and including 1.0.5 have a bug in mod_authz_svn that allows users with write access to read portions of the repository that they do not have read access to. Subversion 1.0.6 and newer (including 1.1.0-rc1) are not vulnerable to this issue. Details: ======== mod_authz_svn would allow a user to copy portions of a repo to which they did not have read permissions to portions that they did have read permissions on, thereby evading the read restrictions. Severity: ========= This is a low risk issue. Only sites running mod_authz_svn (an Apache module) that are trying to restrict some of their users with write access to a repo from reading part of that repo are vulnerable. Most installations will not fall into this category. Additionally, any attempt to use such a vulnerability will be apparent as the copy will be versioned. Plus, it's doubtful any site would permit public write access to its repository so this issue should not be accessible by unauthenticated users. This vulnerability does not affect users running svnserve. Workarounds: ============ * Disable DAV and use svnserve. * Separate content into different repos. * Disable the COPY method via Apache configuration. Note this will disallow all copies. Recommendations: ================ We recommend all users upgrade to 1.0.6 or 1.1.0-rc1. Questions, comments, and bug reports to users_at_subversion.tigris.org. Thanks, -The Subversion Team --------------------8-<-------cut-here---------8-<----------------------- User-visible-changes: * fixed: crash in status command, caused by race (r10144) * fixed: crashes when deleting a revision-prop (r10148, r10185, r10192) * fixed: mod_authz_svn allows COPY method on repos with space in name (#1837) * fixed: mod_authz_svn COPY security hole: authorize whole tree (issue #1949) Developer-visible changes: * neon 0.24.7 now required (fixes wire compression bugs) (r10159, 10176) --------------------------------------------------------------------- To unsubscribe, e-mail: announce-unsubscribe@subversion.tigris.org For additional commands, e-mail: announce-help@subversion.tigris.org Reproducible: Always Steps to Reproduce:
Paul will look into this and provide an ebuild? Please also remove old vulnerable and uneeded versions.
Stuart -- mind tending to this while Paul is enjoying his vacation?
Okay, I'm looking at it now.
Right, dev-util/subversion-1.0.6 and net-misc/neon-0.24.7 are now in the tree, and marked as ~arch. I'll get started on testing on x86. If you can start getting the other arches testing and marking stable, that'll be great. Best regards, Stu
Arch maintainers please test subversion-1.0.6 and mark stable.
Target keywords: alpha amd64 hppa ~ppc sparc x86
Also remember to mark net-misc/neon-0.24.7 stable as subversion depends on it.
Stable on x86.
subversion 1.0.6, now with sparc goodness. coming soon to an rsync mirror near you! Warning: may eat excessive amounts of disk space and RAM. Your data is at risk if you do not keep up repayments on the bribe money required for the db not to corrupt itself. XML has been known to cause cancer in lab rats.
Stable on alpha.
ppc,amd64,hppa: please mark neon-0.24.7 stable amd64,hppa: please mark subversion-1.0.6 stable
I can draft this, hopefully sometime this weekend.
stable on amd64
Stable on hppa.
Since subversion is ~ on the PPC platform, I think it's not necessary to wait for ppc to mark neon-0.24.7 stable to release the GLSA. People running suversion as ~ on ppc will probably know they need to have neon ~ too to resolve the dependency. ppc : feel free to mark neon-0.24.7 stable if you disagree.
GLSA 200407-20.
