blob: 6ecbd1cb857bbf7d5487e62b9d6e97e9d8ff732c [file] [log] [blame]
<?xml version="1.0" encoding="utf-8"?>
<glsa id="200404-13">
<title>CVS Server and Client Vulnerabilities</title>
There are two vulnerabilities in CVS; one in the server and one in the
client. These vulnerabilities allow the reading and writing of arbitrary
files on both client and server.
<product type="ebuild">cvs</product>
<announced>April 14, 2004</announced>
<revised>May 22, 2006: 02</revised>
<package name="dev-util/cvs" auto="yes" arch="*">
<unaffected range="ge">1.11.15</unaffected>
<vulnerable range="le">1.11.14</vulnerable>
CVS, which stands for Concurrent Versions System, is a client/server
application which tracks changes to sets of files. It allows multiple
users to work concurrently on files, and then merge their changes back
into the main tree (which can be on a remote system). It also allows
branching, or maintaining separate versions for files.
There are two vulnerabilities in CVS; one in the server and one in the
client. The server vulnerability allows a malicious client to request
the contents of any RCS file to which the server has permission, even
those not located under $CVSROOT. The client vulnerability allows a
malicious server to overwrite files on the client machine anywhere the
client has permissions.
<impact type="normal">
Arbitrary files may be read or written on CVS clients and servers by
anybody with access to the CVS tree.
There is no known workaround at this time. All users are encouraged to
upgrade to the latest stable version of CVS.
All CVS users should upgrade to the latest stable version.
# emerge sync
# emerge -pv &quot;&gt;=dev-util/cvs-1.11.15&quot;
# emerge &quot;&gt;=dev-util/cvs-1.11.15&quot;</code>
<uri link=";content-type=text/x-cvsweb-markup">CVS commit log</uri>
<uri link="">CVE-2004-0180</uri>
<uri link="">CVE-2004-0405</uri>
<metadata tag="submitter">