A Security Vulnerability in Sun Java System Calendar Server May Allow Denial of Service (DoS) When Access Logging is Enabled |
|
| Category : | Security | | Release Phase : | Resolved | | Bug Id : | 6622866
| | Date of Resolved Release : | 13-Jun-2008
| | Product : | Sun ONE Calendar Server 6.0 Patch 1 Sun Java System Calendar Server 6 2004Q2 Sun Java System Calendar Server 6 2005Q1 Sun Java System Calendar Server 6 2005Q4
|
A Security Vulnerability in Sun Java System Calendar Server May Allow Denial of Service (DoS) When Access Logging is Enabled 1. Impact
A security vulnerability in Sun Java System Calendar Server may
allow a remote unprivileged user to crash the Calendar Server when
access logging is enabled. This is a type of Denial of Service (DoS).
2. Contributing Factors
SPARC Platform -
Sun ONE Calendar Server 6.0
-
Sun Java System Calendar Server 6 2004Q2
-
Sun Java System Calendar Server 6 2005Q1
-
Sun Java System Calendar Server 6 2005Q4
-
Sun Java System Calendar Server 6.3 without patch 121657-23
x86 Platform
- Sun ONE Calendar Server 6.0
-
Sun Java System Calendar Server 6 2004Q2
-
Sun Java System Calendar Server 6 2005Q1
-
Sun Java System Calendar Server 6 2005Q4
-
Sun Java System Calendar Server 6.3 without patch 121658-23
Linux
- Sun ONE Calendar Server 6.0
-
Sun Java System Calendar Server 6 2004Q2
-
Sun Java System Calendar Server 6 2005Q1
-
Sun Java System Calendar Server 6 2005Q4
-
Sun Java System Calendar Server 6.3 without patch 121659-23
Notes:
1. To determine the version of Sun Java System Calendar Server on a
system, the following command can be run:
$ csversion Sun Java(tm) System Calendar Server 6.3-7.01 (built Feb 20 2008) SunOS palamoor 5.10 Generic_118833-36 sun4u sparc SUNW,A70
2. This issue only affects the Calendar Server when access logging is
enabled. To determine if access logging is enabled, look for the config
"service.http.commandlog.all" in the configuration file (ics.conf).
$ grep service.http.commandlog.all
<install_path>/cal/config/ics.conf service.http.commandlog.all = "yes"
3. Symptoms
If this issue is exploited to cause a Denial of Service (DoS) the
Calendar Server will no longer be running on the system. This can be
determined using a command such as the following, which will produce no
output if the process has crashed:
$ pgrep cshttpd
Depending on the system configuration, the Calendar Server process may
leave a crash dump, which may have a stack trace similar to the
following if this issue has been exploited:
$ pstack core ... ... ----------------- lwp# 8 / thread# 8 -------------------- ff029a6c sock_readable (442f322e, 302e302e, 300a4143, 43455054,
3a205445, 58542f58) + 33c ...
...
4. Workaround
To workaround this issue, access logging can be disabled by editing the
"ics.conf" file, changing the value for "service.http.commandlog.all"
to "no", as follows:
$ grep service.http.commandlog.all
<install_path>/cal/config/ics.conf service.http.commandlog.all = "no"
5. Resolution
This issue is addressed in the following releases:
SPARC Platform
- Sun Java System Calendar Server 6.3 with patch
121657-23 or later
x86 Platform
- Sun Java System Calendar Server 6.3 with patch
121658-23 or later
Linux
- Sun Java System Calendar Server 6.3 with patch
121659-23 or later
To resolve this issue on versions prior to 6.3, an upgrade to the 6.3
release is required first, followed by the appropriate patch
application from above. The upgrade instructions can be found at:
http://docs.sun.com/source/819-7561/calendarSvr.html
For more information
on Security Sun Alerts, see Technical
Instruction
ID 213557.
This Sun Alert notification is being provided to you on
an "AS IS"
basis. This Sun Alert notification may contain information provided by
third parties. The issues described in this Sun Alert notification may
or may not impact your system(s). Sun makes no representations,
warranties, or guarantees as to the information contained herein. ANY
AND ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR
NON-INFRINGEMENT, ARE HEREBY DISCLAIMED. BY ACCESSING THIS DOCUMENT YOU
ACKNOWLEDGE THAT SUN SHALL IN NO EVENT BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES THAT ARISE OUT
OF YOUR USE OR FAILURE TO USE THE INFORMATION CONTAINED HEREIN. This
Sun Alert notification contains Sun proprietary and confidential
information. It is being provided to you pursuant to the provisions of
your agreement to purchase services from Sun, or, if you do not have
such an agreement, the Sun.com Terms of Use. This Sun Alert
notification may only be used for the purposes contemplated by these
agreements.
Copyright 2000-2008 Sun Microsystems, Inc., 4150 Network Circle, Santa
Clara, CA 95054 U.S.A. All rights reserved. AttachmentsThis solution has no attachment
|
|
Login Required
You must login and have a valid contract to access Sun's Premium content which includes:
- Sun Alerts
- Bugs
- Patches
- Solutions
- White Papers
- Documentation
- Support Knowledge
Login Required
You must login and have a valid contract to access Sun's contracted features
|
Access Legend:
Sun Contracted Content
Sun Contracted Feature
|
Please make use of SunSolve Feedback application by selecting the floating [+] to provide feedback about this specific document.
|