CVS Heap Overflow Vulnerability
- Concurrent Versions System (CVS) versions prior to 1.11.16
- CVS Features versions prior to 1.12.8
A heap overflow vulnerability in the Concurrent Versions System (CVS) could allow a remote attacker to execute arbitrary code on a vulnerable system.
CVS is a source code maintenance system that is widely used by open-source software development projects. There is a heap memory overflow vulnerability in the way CVS handles the insertion of modified and unchanged flags within entry lines. When processing an entry line, an additional byte of memory is allocated to flag the entry as modified or unchanged. There is a failure to check if a byte has been previously allocated for the flag, which creates an off-by-one buffer overflow. By calling a vulnerable function several times and inserting specific characters into the entry lines, a remote attacker could overwrite multiple blocks of memory. In some environments, the CVS server process is started by the Internet services daemon (inetd) and may run with root privileges.
An authenticated client could exploit this vulnerability to execute arbitrary code, execute commands, modify sensitive information, or cause a denial of service. Note that if a CVS server is configured to permit anonymous read-only access, then this provides sufficient access to exploit a vulnerable server, as anonymous users are authenticated through the cvspserver process.
An authenticated client could exploit this vulnerability to execute arbitrary code on the vulnerable system with the privileges of the CVS server process. It is possible for an anonymous user with read-only access to exploit a vulnerable server as they are authenticated through the cvspserver process.
In addition to compromising the system running CVS, there is a significant secondary impact in that source code maintained in CVS repositories could be modified to include Trojan horses, backdoors, or other malicious code.
SolutionApply Patch or Upgrade
Apply the appropriate patch or upgrade as specified by your vendor. For vendor specific responses, please see your vendor's website or Vulnerability Note VU#192038.
Disable CVS Server
Until a patch or upgrade can be applied, consider disabling the CVS server.Block or Restrict Access
Block or restrict access to the CVS server from untrusted hosts and networks. The CVS server typically listens on 2401/tcp, but may use another port or protocol.
Limit CVS Server Privileges
Note that some of these workarounds will only limit the scope and impact of possible attacks. Note also that anonymous (read-only) access is sufficent to exploit this vulnerability.
- Configure CVS server to run in a restricted (chroot) environment.
- Run CVS servers with the minimum set of privileges required on the host file system.
- Provide separate systems for development (write) and public/anonymous (read-only) CVS access.
- Host public/anonymous CVS servers on single-purpose, secured systems.
Appendix B. References
US-CERT thanks Stefan Esser of e-matters for reporting this problem and for information used to construct this advisory.
Feedback can be directed to the authors: Jason A. Rafail and Damon Morda
May 26, 2004: Initial release