{"vuid":"VU#574222","idnumber":"574222","name":"BEA WebLogic Server configuration wizard stores administrative credentials in clear text log files","keywords":["BEA Weblogic Server","username","password","information disclosure","configuration config.sh","config.cmd","BEA04_58.00"],"overview":"There is a vulnerability in BEA WebLogic Server in which a user with access to log files generated by the configuration wizard could obtain the administrative username and password.","clean_desc":"BEA Systems describes WebLogic Server as \"an industrial-strength application infrastructure for developing, integrating, securing, and managing distributed Java applications.\" WebLogic Server supplies a Configuration Wizard for UNIX and Windows systems that allows an administrator to use configuration templates to simplify the setup process. There is a vulnerability in the config.sh (UNIX) and config.cmd (Windows) configuration tools that could result in the administrative username and password being stored in the clear text log file produced by these tools. The BEA Security Advisory states that the following versions of WebLogic Server and Express are affected by this vulnerability: WebLogic Server and WebLogic Express 8.1 released through Service Pack 2, on all platforms","impact":"A user with privileges to access log files produced by the configuration tools could obtain the administrative username and password.","resolution":"Upgrade WebLogic Server and WebLogic Express version 8.1 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/CR135189_81sp2patch.jar WebLogic Server version 8.1 Service Pack 3 will include the functionality in this patch.","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_58.00.jsp","http://secunia.com/advisories/11437/","http://www.securitytracker.com/alerts/2004/Apr/1009898.html"],"cveids":[""],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2004-04-22T17:45:46Z","publicdate":"2004-04-21T00:00:00Z","datefirstpublished":"2004-04-23T20:18:23Z","dateupdated":"2004-04-23T20:20:32Z","revision":14,"vrda_d1_directreport":"","vrda_d1_population":"","vrda_d1_impact":"","cam_widelyknown":"15","cam_exploitation":"0","cam_internetinfrastructure":"9","cam_population":"7","cam_impact":"20","cam_easeofexploitation":"7","cam_attackeraccessrequired":"10","cam_scorecurrent":"4.41","cam_scorecurrentwidelyknown":"5.32875","cam_scorecurrentwidelyknownexploited":"9.00375","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":4.41,"vulnote":null}