Date Discovered July 11, 2003
Description It has been reported that there is a buffer overflow condition present in gopherd that may be exploited remotely to execute arbitrary code. The affected component is said to be used for determining view-types for gopher objects.
- University of Minnesota gopherd 2.0.3
- University of Minnesota gopherd 2.0.4
- University of Minnesota gopherd 2.3.0
- University of Minnesota gopherd 2.3.1
- University of Minnesota gopherd 3.0.0 .0
- University of Minnesota gopherd 3.0.1
- University of Minnesota gopherd 3.0.2
- University of Minnesota gopherd 3.0.3
- University of Minnesota gopherd 3.0.4
- University of Minnesota gopherd 3.0.5
Deploy network intrusion detection systems to monitor network traffic for malicious activity. Deploying intrusion detection systems may aid in detecting common types of attacks.
To limit the consequences of successful exploits, run the server in a closed or restricted environment. By default, gopherd will restrict the process to a chroot jail. Taking advantage of this may reduce the impact of successful exploitation.
Implement multiple redundant layers of security.
Kernel security enhancements such as stack protection and randomly mapped memory pages may limit exposure to stack-based overflow exploits.
The maintainer has responded to advise users to migrate to PyGopherd, as UMN gohperd has been removed from distribution and is no longer supported.
Debian has released an advisory (DSA-387-1) and fixes to address this issue.
Credits Reported by Vade 79 .
Copyright © Symantec Corporation.
Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from email@example.com
The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.
Symantec, Symantec products, Symantec Security Response, and firstname.lastname@example.org
are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.