BEA WebLogic Server and Express config.xml files stores usernames and passwords in plain text
| bea-configxml-plaintext-password (15860) |  Medium Risk |
Description:
BEA WebLogic Server and Express could allow a local attacker to obtain sensitive information. If a JDBC connection pool is not targeted to a server or a JDBC connection pool has been untargeted from all servers and then had the password changed, the username and password are stored in the config.xml file. A local attacker who has read access to the config.xml file can access the file to obtain the database username and password in plain text.
Consequences:
Obtain Information
Remedy:
For WebLogic Server and Express 8.1:
Upgrade to Service Pack 3, when it becomes available, or upgrade to Service Pack 2 and apply the patch for this vulnerability, as listed in BEA Systems Inc. SECURITY ADVISORY (BEA04-53.00). See References.
For WebLogic Server and Express 7.0:
Upgrade to Service Pack 5, as listed in BEA Systems Inc. SECURITY ADVISORY (BEA04-53.00). See References.
For WebLogic Server and Express 6.1:
Upgrade to Service Pack 7, when it becomes available, or upgrade to Service Pack 6 and apply the patch for this vulnerability, as listed in BEA Systems Inc. SECURITY ADVISORY (BEA04-53.00). See References.
References:
- BEA Systems, Inc. Security Advisory (BEA04-53.00): Patches are available to prevent password exposure. .
- BID-10131: BEA WebLogic Server/Express Potential Password Disclosure Weakness
- CVE-2004-1758: BEA WebLogic Server and WebLogic Express version 8.1 up to SP2, 7.0 up to SP4, and 6.1 up to SP6 may store the database username and password for an untargeted JDBC connection pool in plaintext in config.xml, which allows local users to gain privileges.
- OSVDB ID: 5297: BEA WebLogic config.xml Password Exposure
- SA11357: BEA WebLogic Database Password Stored in Plain Text Issue
- SECTRACK ID: 1009764: BEA WebLogic May Disclose Database Password Via `config.xml` For Untargeted JDBC Connection Pools
- US-CERT VU#920238: BEA WebLogic Server stores database password in clear text in config.xml
Platforms Affected:
- HP HP-UX 11.00
- HP HP-UX 11i
- IBM AIX 4.3.3
- Microsoft Windows 2000 Professional
- Oracle WebLogic Server 6.1 SP4 Express
- Oracle WebLogic Server 6.1 SP1 Express
- Oracle WebLogic Server 6.1 Express
- Oracle WebLogic Server 6.1 SP2
- Oracle WebLogic Server 6.1 Win32
- Oracle WebLogic Server 6.1 SP1
- Oracle WebLogic Server 6.1
- Oracle WebLogic Server 6.1 SP6
- Oracle WebLogic Server 6.1 SP5 Express
- Oracle WebLogic Server 6.1 SP5
- Oracle WebLogic Server 6.1 SP4
- Oracle WebLogic Server 6.1 SP3
- Oracle WebLogic Server 6.1 SP2 Win32
- Oracle WebLogic Server 6.1 SP3 Express
- Oracle WebLogic Server 6.1 SP2 Express
- Oracle WebLogic Server 6.1 SP1 Win32
- Oracle WebLogic Server 7.0
- Oracle WebLogic Server 7.0 Express
- Oracle WebLogic Server 7.0 SP4
- Oracle WebLogic Server 7.0 SP2 Express
- Oracle WebLogic Server 7.0 SP4 Express
- Oracle WebLogic Server 7.0 SP3 Express
- Oracle WebLogic Server 7.0 SP1 Express
- Oracle WebLogic Server 7.0 Win32
- Oracle WebLogic Server 7.0 SP4 Win32
- Oracle WebLogic Server 7.0 SP3
- Oracle WebLogic Server 7.0 SP2
- Oracle WebLogic Server 7.0 SP1
- Oracle WebLogic Server 8.1 SP1 Express
- Oracle WebLogic Server 8.1
- Oracle WebLogic Server 8.1 SP2 Win32
- Oracle WebLogic Server 8.1 Win32
- Oracle WebLogic Server 8.1 Express
- Oracle WebLogic Server 8.1 SP1
- Oracle WebLogic Server 8.1 SP1 Win32
- Oracle WebLogic Server 8.1 SP2
- Oracle WebLogic Server 8.1 SP2 Express
- RedHat Linux Intel Premium
- Sun Solaris 2.7
- Sun Solaris 8
Reported:
Apr 13, 2004
The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall the author/distributor (IBM Internet Security Systems X-Force) be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.
For corrections or additions please email xforce@iss.net