CVE-2005-1742: Medium severity bea weblogic server vulnerability
Published May 24, 2005
·Updated
BEA WebLogic Server and WebLogic Express 8.1 SP2 and SP3 allows users with the Monitor security role to "shrink or reset JDBC connection pools."
Affected Software
76 affected components
Bea WebLogic Server=8.1
Bea WebLogic Server=8.1-sp4
Bea WebLogic Server=7.0-sp2
Bea WebLogic Server=7.0.0.1-sp4
Bea WebLogic Server=6.1-sp4
Bea WebLogic Server=6.1
Bea WebLogic Server=8.1
Bea WebLogic Server=6.1-sp5
Bea WebLogic Server=6.0-sp1
Bea WebLogic Server=6.1-sp6
Bea WebLogic Server=7.0-sp4
Bea WebLogic Server=6.1-sp1
Bea WebLogic Server=7.0
Bea WebLogic Server=6.0
Bea WebLogic Server=6.1-sp4
Bea WebLogic Server=6.1-sp4
Bea WebLogic Server=7.0.0.1-sp1
Bea WebLogic Server=6.1-sp6
Bea WebLogic Server=6.0-sp2
Bea WebLogic Server=6.0-sp2
Bea WebLogic Server=6.1-sp3
Bea WebLogic Server=6.0-sp2
Bea WebLogic Server=7.0-sp3
Bea WebLogic Server=7.0.0.1-sp4
Bea WebLogic Server=8.1-sp1
Bea WebLogic Server=6.0-sp1
Bea WebLogic Server=7.0.0.1-sp1
Bea WebLogic Server=6.1-sp2
Bea WebLogic Server=8.1-sp3
Bea WebLogic Server=7.0-sp2
Bea WebLogic Server=6.1-sp1
Bea WebLogic Server=8.1-sp3
Bea WebLogic Server=7.0.0.1
Bea WebLogic Server=6.0
Bea WebLogic Server=7.0-sp3
Bea WebLogic Server=7.0.0.1-sp1
Bea WebLogic Server=8.1
Bea WebLogic Server=8.1-sp4
Bea WebLogic Server=7.0-sp5
Bea WebLogic Server=7.0.0.1
Bea WebLogic Server=7.0-sp5
Bea WebLogic Server=7.0-sp5
Bea WebLogic Server=6.1-sp1
Bea WebLogic Server=6.1
Bea WebLogic Server=6.0
Bea WebLogic Server=8.1-sp1
Bea WebLogic Server=7.0-sp2
Bea WebLogic Server=8.1-sp3
Bea WebLogic Server=8.1-sp2
Bea WebLogic Server=6.1
Bea WebLogic Server=6.0-sp1
Bea WebLogic Server=7.0.0.1
Bea WebLogic Server=6.1-sp2
Bea WebLogic Server=7.0.0.1-sp3
Bea WebLogic Server=7.0-sp3
Bea WebLogic Server=7.0-sp1
Bea WebLogic Server=7.0.0.1-sp2
Bea WebLogic Server=6.1-sp5
Bea WebLogic Server=7.0-sp1
Bea WebLogic Server=7.0-sp4
Bea WebLogic Server=8.1-sp1
Bea WebLogic Server=6.1-sp3
Bea WebLogic Server=6.1-sp5
Bea WebLogic Server=7.0-sp1
Bea WebLogic Server=8.1-sp2
Bea WebLogic Server=8.1-sp4
Bea WebLogic Server=7.0.0.1-sp2
Bea WebLogic Server=6.1-sp2
Bea WebLogic Server=7.0
Bea WebLogic Server=8.1-sp2
Bea WebLogic Server=7.0
Bea WebLogic Server=6.1-sp3
Bea WebLogic Server=7.0.0.1-sp3
Bea WebLogic Server=7.0-sp4
Bea WebLogic Server=7.0.0.1-sp2
Oracle Weblogic Portal=8.0
Event History
May 24, 2005
CVE Published
04:00 AM
CVE Published
via MITRE·08:00 AM
Data Sourced
via MITRE·08:00 AM
Description
Frequently Asked Questions
1
What is the severity of CVE-2005-1742?
CVE-2005-1742 is classified as a moderate severity vulnerability.
2
How do I fix CVE-2005-1742?
To fix CVE-2005-1742, it is recommended to apply the latest patches or updates provided by Oracle for WebLogic Server.
3
What versions of WebLogic Server are affected by CVE-2005-1742?
CVE-2005-1742 affects BEA WebLogic Server versions 6.1, 7.0, and 8.1, specifically SP2 and SP3.
4
What risk does CVE-2005-1742 pose to my application?
CVE-2005-1742 allows users with the Monitor security role to manipulate JDBC connection pools, which could lead to unauthorized access or performance issues.
5
Is there a workaround for CVE-2005-1742 if I cannot apply the patch immediately?
A possible workaround for CVE-2005-1742 is to limit the users assigned to the Monitor security role in the WebLogic Server.