From: BEA Systems Inc.
Minor Subject: Patches are available to protect Server version information
Product(s) Affected: WebLogic Server and WebLogic Express
Threat level: Low
No known exploit exists.
Severity: Low
No known exploit exists.
A problem was identified that could potentially cause a security vulnerability in certain versions of WebLogic Server and WebLogic Express. Patches are available to correct this problem (see Section II). BEA Systems treats potential security problems with the highest degree of urgency and does everything possible to ensure the security of all customer assets. As a result, BEA Systems strongly suggests the following actions:
I. Read the following advisory.This vulnerability occurs in both WebLogic Server and WebLogic Express. Throughout the rest of this advisory, references to WebLogic Server apply to both products.
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
This vulnerability can occur whenever an HTTP or HTTPS request is made of the server. By default, the server adds information about the version of WebLogic Server that is running.
Should an attacker discover a vulnerability that occurs in a specific version of WebLogic Server, they could use this header information to identify servers that are potentially vulnerable to this attack.
This advisory resolves this issue by changing the default setting for Web Servers from true to false.
The following versions of WebLogic Server and WebLogic Express are affected by this vulnerability:
- WebLogic Server 8.1, released through Service Pack 3, on all platforms
- WebLogic Server 7.0, released through Service Pack 5, on all platforms
- WebLogic Server 6.1, released through Service Pack 6, on all platforms
II. SUGGESTED ACTION
BEA Systems strongly recommends the following course of actions.
WebLogic Server and WebLogic Express
- For WebLogic Server 8.1 perform the following steps:
-
- Upgrade to WebLogic Server 8.1 Service Pack 3
- Apply the patch ftp://anonymous:dev2dev%40bea.com@ftpna.bea.com/pub/releases/security/CR103309_810sp3.jar
WebLogic Server 8.1 Service Pack 4 will include the functionality in this patch.
Change the Send Server Header setting in deployed Web Servers to false. For more information, see: http://e-docs.bea.com/wls/docs81/ConsoleHelp/domain_server_protocols_http.html
- For WebLogic Server 7.0 perform the following steps:
-
- Upgrade to WebLogic Server 7.0 Service Pack 5 and
- Apply the patch ftp://anonymous:dev2dev%40bea.com@ftpna.bea.com/pub/releases/security/CR103309_700sp5.jar
WebLogic Server 7.0 Service Pack 6 will include the functionality in this patch.
Change the Send Server Header setting in deployed Web Servers to false. For more information, see: http://e-docs.bea.com/wls/docs70/ConsoleHelp/domain_server_connections_http.html
- For WebLogic Server 6.1 perform the following steps:
-
- Upgrade to WebLogic Server 6.1 Service Pack 6
- Apply the patch ftp://anonymous:dev2dev%40bea.com@ftpna.bea.com/pub/releases/security/CR103309_610sp6.jar
WebLogic Server 6.1 Service Pack 7 will include the functionality in this patch.
Change the Send Server Header setting in deployed Web Servers to false. For more information, see: http://e-docs.bea.com/wls/docs61/security/lockdown.html
BEA Systems strongly suggests that customers apply the remedies recommended in all our security advisories. BEA Systems 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:
http://commerce.beasys.com/downloads/weblogic_server.jsp#wls
Note: Information about securing BEA WebLogic Server and WebLogic Express can be found in Securing a Production Environment at http://e-docs.bea.com/wls/docs81/lockdown/index.html.
BEA Systems strongly encourage you to review this documentation so that you can be assured that your server deployment is securely configured.
III. FUTURE SECURITY COMMUNICATIONS
As a corporate policy, if there are any security-related issues with any BEA product, BEA Systems will distribute an advisory and instructions with the appropriate course of action. Because the security of your site, data, and code is our highest priority, we are committed to communicating all security-related issues clearly and openly.
All previous advisories and notifications can be viewed at http://dev2dev.bea.com/advisoriesnotifications/.
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 are any security issues with the BEA product(s) he/she is using, BEA Systems will distribute an advisory and instructions via email with the appropriate course of action.
ADDITIONAL USERS WHO WISH TO REGISTER FOR ADVISORY DISTRIBUTION SHOULD FOLLOW THE REGISTRATION DIRECTIONS AT http://dev2dev.bea.com/advisoriesnotifications/.
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/advisoriesnotifications/. All reports of security issues will be promptly reviewed and all necessary actions taken to ensure the continued security of all customer assets.
If you have any questions or care to verify the authenticity of this advisory, please contact BEA Technical Support at support@bea.com.



