First published: Tue Mar 18 2003(Updated: )
BEA WebLogic Server and Express 7.0 and 7.0.0.1, when using "memory" session persistence for web applications, does not clear authentication information when a web application is redeployed, which could allow users of that application to gain access without having to re-authenticate.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Oracle WebLogic Server | =7.0 | |
Oracle WebLogic Server | =7.0 | |
Oracle WebLogic Server | =7.0-sp1 | |
Oracle WebLogic Server | =7.0-sp1 | |
Oracle WebLogic Server | =7.0.0.1 | |
Oracle WebLogic Server | =7.0.0.1 | |
Oracle WebLogic Server | =7.0.0.1-sp1 | |
Oracle WebLogic Server | =7.0.0.1-sp1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2003-1095 is considered a high severity vulnerability due to the potential for unauthorized access.
To fix CVE-2003-1095, update to a version of BEA WebLogic Server that does not use memory session persistence for web applications.
Exploiting CVE-2003-1095 could allow users to access sensitive information without re-authenticating, compromising application security.
CVE-2003-1095 affects BEA WebLogic Server and Express versions 7.0 and 7.0.0.1, including their service packs.
A possible workaround for CVE-2003-1095 is to disable the use of memory session persistence in affected WebLogic configurations.