MPSB04-08 - Cumulative Security Patch available for JRun server
Originally posted: September 23, 2004
Summary
This is a cumulative patch for JRun server that includes all previously released patches for JRun 3.0, 3.1 and 4.0.
Solution
Macromedia has released a set of patches and updaters to address the problem.
Affected Software Versions
- JRun 4.0 (all editions)
- JRun 3.1 (all editions)
- JRun 3.0 (all editions)
Severity Rating
Macromedia categorizes this issue as a critical update and recommends users immediately patch their installations.
Details
This cumulative security rollup contains the following patches:
- JRun 4.0 implementation error in JRun's generation and handling of the JSESSIONID may enable session stealing or session fixation. Users will notice JSESSIONID generation no longer uses just numbers but is a combination of numbers and letters. (JRun 3.x not affected)
- JRun 4.0 cross-site scripting and session fixation issues in the JRun Management Console. (JRun 3.x not affected)
- JRun 4.0 server can be tricked into bypassing access restrictions and showing source for files that are not associated with Macromedia extensions (.php, .asp, .pl) by appending (for example ColdFusion)";.cfm" to the end of the URL. Only the Microsoft IIS connector is affected.(JRun 3.x not affected)
- All JRun versions buffer overflow has been discovered when JRun web server connectors are in "verbose" debug mode. (all connectors, platforms and versions)
NOTE: Running the connector in "verbose=true" mode is used to debug web server connector communication issues between the JRun connector module running inside the web server and the Macromedia JRun server. Verbose logging is disabled by default. Turning verbose on is not recommended on production systems but if left on, it is possible for an attacker to exploit a buffer overflow in the verbose logging module and crash the web server.
If verbose logging is disabled (default setting), the web server is NOT vulnerable.
| Web Server | Property file | Section/Location |
|---|---|---|
| Microsoft IIS (all versions) | jrun.ini | See below |
| Netscape, IPlanet, SunOne (all versions) | obj.conf | Init fn="jruninit" |
| Apache (all versions) | http.conf | "JRun Settings" section |
For installations with Microsoft IIS, thejrun.ini file could be in one of two places:
-
JRun and IIS on the same system
jrun.ini is located under the JRun server installation under a directory /wsconfig.
- JRun -- {jrun_root}/lib/wsconfig/[n]
-
JRun and IIS on separate systems
In a distributed configuration, the file is located where the web server configuration tool (wsconfig.jar) was run from.
Example: location of wsconfig.jar under c:\inetpub
c:\inetpub\wsconfig.jar -> jrun.ini is located in c:\inetpub\wsconfig\1\jrun.ini
Making the Changes
NOTE: Back up your existing files before making changes. As always, test the changes in a non-production environment before applying the changes to production servers.
| JRun 3.0 | English | French | Japanese |
|---|---|---|---|
| JRun 3.1 | English | French | Japanese |
| JRun 3.0 | English | French | Japanese |
|---|---|---|---|
| JRun 3.1 | English | French | Japanese |
JRun
- Stop JRun.
- Install JRun 3.0, 3.1 for the correct platform and language from the table above. For JRun 4.0, install the JRun 4.0 Updater 4 release.
- Start JRun
NOTE: Back up your existing files before making changes. As always, test the changes in a non-production environment before applying the changes to production servers.
Acknowledgements
Macromedia would like to thankthe following individuals and companies for working with to help protect our customers' security.
- iDefense for reporting the view source ";.cfm" and theconnector buffer overflow vulnerability
- @Stake for the weak JSESSIONID generation vulnerability
- Acros for reporting the "Unsanitized JRun Session ID Cookie Allows Modifying Server Response", a cross-site scripting issue and a session fixation issue in the JRun Management Console.
Revisions
September 23, 2004 - Bulletin first created.
Reporting Security Issues
Macromedia is committed to addressing security issues and providing customers with the information on how they can protect themselves. If you identify what you believe may be a security issue with a Macromedia product, please send an email to secure@macromedia.com. We will work to appropriately address and communicate the issue.
Receiving Security Bulletins
When Macromedia becomes aware of a security issue that we believe significantly affects our products or customers, we will notify customers when appropriate. Typically this notification will be in the form of a security bulletin explaining the issue and the response. Macromedia customers who would like to receive notification of new security bulletins when they are released can sign up for our security notification service.
For additional information on security issues at Macromedia, please visit: http://www.macromedia.com/security.
ANY INFORMATION, PATCHES, DOWNLOADS, WORKAROUNDS OR FIXES PROVIDED BY MACROMEDIA IN THIS BULLETIN ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MACROMEDIA AND ITS SUPPLIERS DISCLAIM ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED OR OTHERWISE, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. ALSO, THERE IS NO WARRANTY OF NON-INFRINGEMENT, TITLE OR QUIET ENJOYMENT. (USA ONLY) SOME STATES DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO THE ABOVE EXCLUSION MAY NOT APPLY TO YOU.
IN NO EVENT SHALL MACROMEDIA, INC. OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING, WITHOUT LIMITATION, DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, SPECIAL, PUNITIVE, COVER, LOSS OF PROFITS, BUSINESS INTERRUPTION OR THE LIKE, OR LOSS OF BUSINESS DAMAGES, BASED ON ANY THEORY OF LIABILITY INCLUDING BREACH OF CONTRACT, BREACH OF WARRANTY, TORT(INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF MACROMEDIA, INC. OR ITS SUPPLIERS OR THEIR REPRESENTATIVES HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. (USA ONLY) SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, SO THE ABOVE EXCLUSION OR LIMITATION MAY NOT APPLY TO YOU AND YOU MAY ALSO HAVE OTHER LEGAL RIGHTS THAT VARY FROM STATE TO STATE.
Macromedia reserves the right, from time to time, to update the information in this document with current information.
