Vulnerability Note VU#584958

Macromedia JRun Server insecurely generates and handles JSESSIONIDs

Original Release date: 12 Oct 2004 | Last revised: 12 Oct 2004

Overview

A vulnerability exists in Macromedia JRun that may allow an attacker to gain access to an authenticated user's session.

Description

Macromedia JRun is an application server that works with most popular web servers such as Apache and IIS. Macromedia states that JRun is deployed at over 10,000 organizations worldwide. The JSESSIONID is a string that uniquely identifies a user's session. JSESSIONIDs are generated using a limited character set (0-9) , therefore reducing the search space required for a brute-force attack. According to reports, JRun Server also handles the JSESSIONIDs insecurely potentially allowing an attacker to gain access to an authorized user's session. The insecure handling may involve how JSESSIONIDs are stored in web browser cookies or URLs. However, the specific details are not available at this time.

Impact

Exploitation of this vulnerability may allow an attacker to hijack an authenticated user's session allowing the attacker to access sensitive information or execute commands on the server with the privileges of the compromised session.

Solution

Apply Patch

In the latest updater increases the security of the JSESSIONID by expanding the character set used for JESSIONIDs to include letters as well as numbers.

It is available for download at:

Systems Affected (Learn More)

VendorStatusDate NotifiedDate Updated
Macromedia Inc.Affected29 Sep 200411 Oct 2004
If you are a vendor and your product is affected, let us know.

CVSS Metrics (Learn More)

Group Score Vector
Base N/A N/A
Temporal N/A N/A
Environmental N/A N/A

References

Credit

This vulnerability was reported in Macromedia Security Bulletin MPSB04-08.

Macromedia credits @Stake for helping to discover and report this issue.

This document was written by Jeff Gennari.

Other Information

  • CVE IDs: Unknown
  • Date Public: 23 Sep 2004
  • Date First Published: 12 Oct 2004
  • Date Last Updated: 12 Oct 2004
  • Severity Metric: 5.32
  • Document Revision: 124

Feedback

If you have feedback, comments, or additional information about this vulnerability, please send us email.