{"vuid":"VU#352110","idnumber":"352110","name":"BEA WebLogic Server internal methods may disclose sensitive information","keywords":["BEA","Weblogic Server","internal methods","information disclosure","administrative password","BEA04-55.00"],"overview":"There is a vulnerability in BEA WebLogic Server that could allow users to obtain the credentials of the user who booted the server.","clean_desc":"BEA Systems describes WebLogic Server as \"an industrial-strength application infrastructure for developing, integrating, securing, and managing distributed Java applications.\" WebLogic Server provides a number of internal methods to interface with the server. A local or remote user with privileges to install and execute code implementing these internal methods could obtain the username and password of the user who booted the system. The BEA Security Advisory states that the following versions of WebLogic Server and Express are affected by this vulnerability: WebLogic Server and WebLogic Express version 8.1 through Service Pack 2, on all platforms \nWebLogic Server and WebLogic Express version 7.0 through Service Pack 4, on all platforms","impact":"A local or remote user with privileges to install and execute code on the server could obtain the username and password of the user who booted the server.","resolution":"Upgrade\nBEA has released an advisory to address this issue. The BEA Security Advisory recommends that users take the following action: 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/CR132949_81sp2.jar. WebLogic Server version 8.1 Service Pack 3 will include the functionality in this patch. WebLogic Server and WebLogic Express version 7.0 1. Upgrade to WebLogic Server and WebLogic Express version 7.0 Service Pack 5.","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_55.00.jsp","http://secunia.com/advisories/11359/","http://securitytracker.com/alerts/2004/Apr/1009766.html"],"cveids":[""],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2004-04-16T14:49:13Z","publicdate":"2004-04-14T00:00:00Z","datefirstpublished":"2004-04-22T15:15:12Z","dateupdated":"2004-04-30T18:41:39Z","revision":10,"vrda_d1_directreport":"","vrda_d1_population":"","vrda_d1_impact":"","cam_widelyknown":"15","cam_exploitation":"0","cam_internetinfrastructure":"7","cam_population":"9","cam_impact":"15","cam_easeofexploitation":"7","cam_attackeraccessrequired":"8","cam_scorecurrent":"3.1185","cam_scorecurrentwidelyknown":"3.82725","cam_scorecurrentwidelyknownexploited":"6.66225","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":3.1185,"vulnote":null}