{"vuid":"VU#950070","idnumber":"950070","name":"BEA WebLogic Server contains vulnerability in handling of certain tags when editing \"weblogic.xml\"","keywords":["BEA Weblogic Server","WebLogic Builder","SecurityRoleAssignmentMBean.toXML()","weblogic.xml","default permissions","security-role-assignment","principal-name"],"overview":"BEA WebLogic Server contains a vulnerability in the way Weblogic Builder and the SecurityRoleAssignmentMBean.toXML method parse certain tags in the weblogic.xml file.","clean_desc":"BEA Systems describes WebLogic Server as \"an industrial-strength application infrastructure for developing, integrating, securing, and managing distributed Java applications.\" There is a vulnerability in the way Weblogic Builder and the SecurityRoleAssignmentMBean.toXML method handle missing tags in the weblogic.xml file. When this file contains the <security-role-assignment> tag, but does not contain a <principal-name> tag, the <security-role-assignment> tag is removed and default roles are assigned by the Servlet container. According to the BEA Security Advisory, the following versions of WebLogic Server and WebLogic Express are affected by this vulnerability. WebLogic Server and WebLogic Express version 8.1 through Service Pack 2, on all platforms. WebLogic Server and WebLogic Express version 7.0 through Service Pack 5, on all platforms.","impact":"A remote user may be able to gain unauthorized access to a web application.","resolution":"Apply a Patch\nBEA has issued an advisory to address this issue. According to the BEA Security Advisory, the following actions are recommended: WebLogic Server and WebLogic Express version 8.1 Any weblogic.xml file that has been edited by Weblogic Builder must be examined to ensure that all of the desired <security-role-assignment> tags are still in the file. To prevent this problem in the future: 1. Upgrade to WebLogic Server and WebLogic Express version 8.1 Service Pack 2. 2. Install the patch from: ftp://ftpna.beasys.com/pub/releases/security/CR171885_810sp2.jar WebLogic Server version 8.1 Service Pack 3 will include the functionality in this patch. You can also examine any weblogic.xml file that has been edited by WebLogic Builder and re-enter any <security-role-assignment> tags that have been deleted. WebLogic Server and WebLogic Express version 7.0 Any weblogic.xml file that has been edited by Weblogic Builder must be examined to ensure that all of the desired <security-role-assignment> tags are still in the file. To prevent this problem in the future: 1. Upgrade to WebLogic Server and WebLogic Express version 7.0 Service Pack 5. 2. Install the patch from: ftp://ftpna.beasys.com/pub/releases/security/CR171885_70sp5.jar WebLogic Server version 7.0 Service Pack 6 will include the functionality in this patch. You can also examine any weblogic.xml file that has been edited by WebLogic Builder and re-enter any <security-role-assignment> tags that have been deleted.","workarounds":"","sysaffected":"","thanks":"This vulnerability was reported by BEA Systems Inc.","author":"This document was written by Damon Morda.","public":["http://dev2dev.bea.com/resourcelibrary/advisoriesnotifications/BEA04_59.00.jsp","http://secunia.com/advisories/11593/","http://www.securitytracker.com/alerts/2004/May/1010128.html"],"cveids":[""],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2004-05-13T15:23:39Z","publicdate":"2004-05-12T00:00:00Z","datefirstpublished":"2004-06-11T16:17:16Z","dateupdated":"2004-06-11T16:22:29Z","revision":16,"vrda_d1_directreport":"","vrda_d1_population":"","vrda_d1_impact":"","cam_widelyknown":"15","cam_exploitation":"0","cam_internetinfrastructure":"7","cam_population":"9","cam_impact":"10","cam_easeofexploitation":"15","cam_attackeraccessrequired":"10","cam_scorecurrent":"5.56875","cam_scorecurrentwidelyknown":"6.834375","cam_scorecurrentwidelyknownexploited":"11.896875","ipprotocol":"","cvss_accessvector":"","cvss_accesscomplexity":"","cvss_authentication":null,"cvss_confidentialityimpact":"","cvss_integrityimpact":"","cvss_availabilityimpact":"","cvss_exploitablity":null,"cvss_remediationlevel":"","cvss_reportconfidence":"","cvss_collateraldamagepotential":"","cvss_targetdistribution":"","cvss_securityrequirementscr":"","cvss_securityrequirementsir":"","cvss_securityrequirementsar":"","cvss_basescore":"","cvss_basevector":"","cvss_temporalscore":"","cvss_environmentalscore":"","cvss_environmentalvector":"","metric":5.56875,"vulnote":null}