October 25, 2003
A problem has been reported in MERCUR Mailserver when handling the POP3 AUTH command. This problem may make it possible for an attacker crash the service on a vulnerable system, or gain unauthorized access.
- Atrium Software MERCUR Mailserver 3.3.0
- Atrium Software MERCUR Mailserver 3.3.0 SP1
- Atrium Software MERCUR Mailserver 3.3.0 SP2
- Atrium Software MERCUR Mailserver 4.0.0 1
- Atrium Software MERCUR Mailserver 4.0.0 1 SP1
- Atrium Software MERCUR Mailserver 4.2.0
- Atrium Software MERCUR Mailserver 4.2.0 SP1
- Atrium Software MERCUR Mailserver 4.2.0 SP2
Block external access at the network boundary, unless external parties require service.
Filter network traffic of questionable integrity at network perimeters. Prohibit unauthorized traffic through ingress and egress filtering.
Run all software as a nonprivileged user with minimal access rights.
Execute all software with the minimal privileges required for functionality. Software that may be prone to attack from malicious users or content should be insulated with additional precautions such as restricted environments.
This vulnerability has been resolved in version 4.2 Service Pack 3a. See referenced vendor advisory for additional details.
Discovery credited to Kostya KORTCHINSKY.
© 1995- 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 firstname.lastname@example.org.
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 email@example.com 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.