Date Discovered February 12, 2007
Description Sun Solaris 10 is prone to a vulnerability that allows remote attackers to bypass authentication.
Successfully exploiting this issue allows remote attackers to gain remote access to vulnerable computers. If the targeted computer is configured to allow non-console logins for superusers, then remote superuser access is possible.
Update: By exploiting the same underlying flaw, attackers may pass other arguments to the 'login' program, potentially allowing them to bypass other security restrictions. Attackers may potentially bypass the console-only requirement for superuser logins.
- Avaya Interactive Response 2.0
- Nortel Networks Media Processing Svr 1000 Rel 3.0
- Nortel Networks Media Processing Svr 500 Rel 3.0
- Nortel Networks Self-Service - CCSS7
- Nortel Networks Self-Service - Peri Application Rel 3.0
- Sun Solaris 10.0
- Sun Solaris 10.0_x86
Block external access at the network boundary, unless external parties require service. If global access isn't required, filter access to the affected computer at the network boundary. Restricting access to only trusted computers and networks might greatly reduce the likelihood of remote exploits.
Sun has released an alert along with patches to address this issue. Please see the references for more information.
Credits kcope discovered this vulnerability.
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 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.