Subject: Security Advisory (BEA08-193.00)
From: BEA Systems Inc.
Minor Subject: Non-authorized user may be able to receive messages from a secured JMS Topic destination
Product(s) Affected: WebLogic Server
Threat level: Medium
Under certain circumstances, an attacker could bypass the security policies defined on a protected JMS Topic destination.
Severity: High
Secure JMS messages may be exposed to unauthorized applications.
A problem was identified that could potentially cause a security vulnerability in certain versions of WebLogic Server. Patches and upgrades are available to correct this problem (see Section II). BEA Systems treats potential security problems with a high degree of urgency and endeavors to take appropriate steps to help ensure the security of our customers’ systems. As a result, BEA Systems strongly suggests the following actions:
I. Read the following advisory.
II. Apply the suggested action.
III. If you know of any additional users interested in future security advisories, please forward them the registration instructions included in this advisory.
I. Advisory
WebLogic security policies can be configured to restrict the access to a JMS destination. If an application user does not have the “receive” permission to a JMS destination (queue/topic), an attempt of receiving messages from that destination by the application should fail with security errors. By exploiting this vulnerability an unauthorized user may be able to receive messages from a standalone (physical) JMS Topic destination or a member of a secured Distributed Topic member destination.
This advisory resolves this issue by checking permissions before allowing a subscriber to use a durable subscription.
Impact and CVSS Ratings:
CVSS Severity Score: 8.3 (High)
Attack Range (AV): Network
Attack Complexity (AC): Medium
Authentication Level (Au): None
Impact Type: Partial confidentiality and integrity and complete availability violation
Vulnerability Type: Information disclosure
CVSS Base Score Vector: (AV:N/AC:M/Au:N/C:P/I:P/A:C)
Complete CVSS Guide: http://www.first.org/cvss/cvss-guide.html
Online Calculator: http://nvd.nist.gov/cvss.cfm?calculator&version=2
The following versions of WebLogic Server are affected by this vulnerability
- WebLogic Server 10 with no maintenance packs, on all platforms
- WebLogic Server 9.2 released through Maintenance Pack 1, on all platforms
- WebLogic Server 9.1 on all platforms
- WebLogic Server 9.0 on all platforms
II. SUGGESTED ACTION
BEA Systems strongly recommends the following course of actions.
WebLogic Server 10.0
WebLogic Server 9.2
WebLogic Server 9.1
Use the Smart Update tool to install the 9.1 patch for CR321429.
WebLogic Server 9.0
Install the 9.0 GA Combo patch from support.bea.com by requesting Bug ID CR239280.
Install the patch from:
ftp://anonymous:dev2dev%40bea.com@ftpna.bea.com/pub/releases/security/CR321429_900.jarPlace the jar for the patch at the end of the PATCH_CLASSPATH.
BEA strongly suggests that customers apply the remedies recommended in all our security advisories. BEA also urges customers to apply every Service Pack as they are released. Service Packs include a roll-up of all bug fixes for each version of the product, as well as each of the prior Service Packs. Service Packs and information about them can be found at:
WebLogic Server: http://commerce.bea.com/showallversions.jsp?family=WLS WebLogic Platform: http://commerce.bea.com/showallversions.jsp?family=WLPNote: Information about securing WebLogic Server and WebLogic Express can be found at: http://edocs.bea.com/wls/docs100/security.html.. Specific lockdown information is provided at http://edocs.bea.com/wls/docs100/lockdown/index.html. We strongly encourage you to review this documentation to ensure your server deployment is securely configured.
III. FUTURE SECURITY COMMUNICATIONS
If there are security-related issues with BEA product, BEA Systems generally distributes an advisory and instructions with a recommended course of action. Because the security of your site, data, and code is a high priority, we are committed to generally communicating security-related issues to our customers and partners.
All previous advisories and notifications can be viewed at http://dev2dev.bea.com/advisories/
BEA Systems has established an opt-in emailing list specifically targeted for product security advisories and notifications. As a policy, if a user has opted-in to our emailing list and there is a relevant security issue with the BEA product(s) he/she is using, BEA generally distributes an advisory and instructions via email with a recommended course of action.
ADDITIONAL USERS WHO WISH TO REGISTER FOR ADVISORY DISTRIBUTION SHOULD FOLLOW THE REGISTRATION DIRECTIONS AT http://dev2dev.bea.com/advisories
IV. REPORTING SECURITY ISSUES
Security issues can be reported to BEA Systems by sending email to secalert@bea.com or by following the directions at http://dev2dev.bea.com/advisories. If BEA has validated a reported security issue, we will endeavor to assess the severity of the impact of the security issue and the likelihood of the exploitation of the vulnerability. Based on these assessments and other factors, BEA will endeavor to develop and appropriately prioritize a workaround or patch designed to reduce or eliminate the risk of the vulnerability.
If you have any questions or care to verify the authenticity of this advisory, please contact BEA Technical Support at support@bea.com
Thank you,
BEA Systems, Inc.
