summaryrefslogtreecommitdiff
path: root/metadata/glsa/glsa-200409-35.xml
diff options
context:
space:
mode:
authorV3n3RiX <venerix@redcorelinux.org>2017-10-09 18:53:29 +0100
committerV3n3RiX <venerix@redcorelinux.org>2017-10-09 18:53:29 +0100
commit4f2d7949f03e1c198bc888f2d05f421d35c57e21 (patch)
treeba5f07bf3f9d22d82e54a462313f5d244036c768 /metadata/glsa/glsa-200409-35.xml
reinit the tree, so we can have metadata
Diffstat (limited to 'metadata/glsa/glsa-200409-35.xml')
-rw-r--r--metadata/glsa/glsa-200409-35.xml70
1 files changed, 70 insertions, 0 deletions
diff --git a/metadata/glsa/glsa-200409-35.xml b/metadata/glsa/glsa-200409-35.xml
new file mode 100644
index 000000000000..90f8d1e36b57
--- /dev/null
+++ b/metadata/glsa/glsa-200409-35.xml
@@ -0,0 +1,70 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
+<glsa id="200409-35">
+ <title>Subversion: Metadata information leak</title>
+ <synopsis>
+ An information leak in mod_authz_svn could allow sensitive metadata of
+ protected areas to be leaked to unauthorized users.
+ </synopsis>
+ <product type="ebuild">Subversion</product>
+ <announced>2004-09-29</announced>
+ <revised>2004-09-29: 01</revised>
+ <bug>65085</bug>
+ <access>remote</access>
+ <affected>
+ <package name="dev-util/subversion" auto="yes" arch="*">
+ <unaffected range="ge">1.0.8</unaffected>
+ <vulnerable range="lt">1.0.8</vulnerable>
+ </package>
+ </affected>
+ <background>
+ <p>
+ Subversion is a versioning system designed to be a replacement for CVS.
+ mod_authz_svn is an Apache module to do path-based authentication for
+ Subversion repositories.
+ </p>
+ </background>
+ <description>
+ <p>
+ There is a bug in mod_authz_svn that causes it to reveal logged metadata
+ regarding commits to protected areas.
+ </p>
+ </description>
+ <impact type="low">
+ <p>
+ Protected files themselves will not be revealed, but an attacker could use
+ the metadata to reveal the existence of protected areas, such as paths,
+ file versions, and the commit logs from those areas.
+ </p>
+ </impact>
+ <workaround>
+ <p>
+ Rather than using mod_authz_svn, move protected areas into seperate
+ repositories and use native Apache authentication to make these
+ repositories unreadable.
+ </p>
+ </workaround>
+ <resolution>
+ <p>
+ All Subversion users should upgrade to the latest version:
+ </p>
+ <code>
+ # emerge sync
+
+ # emerge -pv "&gt;=dev-util/subversion-1.0.8"
+ # emerge "&gt;=dev-util/subversion-1.0.8"</code>
+ </resolution>
+ <references>
+ <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-0749">CAN-2004-0749</uri>
+ <uri link="http://subversion.tigris.org/security/CAN-2004-0749-advisory.txt">Subversion Advisory</uri>
+ </references>
+ <metadata tag="requester" timestamp="2004-09-27T08:34:50Z">
+ jaervosz
+ </metadata>
+ <metadata tag="submitter" timestamp="2004-09-27T23:33:38Z">
+ dmargoli
+ </metadata>
+ <metadata tag="bugReady" timestamp="2004-09-29T19:12:44Z">
+ koon
+ </metadata>
+</glsa>