CVE-2004-1758: Medium severity Bea WebLogic Server vulnerability

Published Apr 13, 2004
·
Updated

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.

Affected Software

37 affected components
Bea WebLogic Server=8.1
Bea WebLogic Server=7.0-sp2
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.1-sp6
Bea WebLogic Server=7.0-sp4
Bea WebLogic Server=6.1-sp1
Bea WebLogic Server=7.0
Bea WebLogic Server=6.1-sp4
Bea WebLogic Server=6.1-sp3
Bea WebLogic Server=7.0-sp3
Bea WebLogic Server=8.1-sp1
Bea WebLogic Server=6.1-sp2
Bea WebLogic Server=7.0-sp2
Bea WebLogic Server=6.1-sp1
Bea WebLogic Server=7.0-sp3
Bea WebLogic Server=8.1
Bea WebLogic Server=6.1-sp1
Bea WebLogic Server=6.1
Bea WebLogic Server=8.1-sp1
Bea WebLogic Server=8.1-sp2
Bea WebLogic Server=6.1
Bea WebLogic Server=6.1-sp2
Bea WebLogic Server=7.0-sp1
Bea WebLogic Server=6.1-sp5
Bea WebLogic Server=7.0-sp4
Bea WebLogic Server=8.1-sp1
Bea WebLogic Server=6.1-sp3
Bea WebLogic Server=7.0-sp1
Bea WebLogic Server=8.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=7.0-sp4

Event History

Apr 13, 2004
CVE Published
04:00 AM
Mar 10, 2005
CVE Published
via MITRE·10:00 AM
Data Sourced
via MITRE·10:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2004-1758?

CVE-2004-1758 is considered a high severity vulnerability due to the exposure of database credentials in plaintext.

2

How do I fix CVE-2004-1758?

To fix CVE-2004-1758, you should upgrade to a fixed version of BEA WebLogic Server that addresses the plaintext storage issue of JDBC connection pool credentials.

3

What versions of WebLogic Server are affected by CVE-2004-1758?

CVE-2004-1758 affects BEA WebLogic Server versions 6.1 up to SP6, 7.0 up to SP4, and 8.1 up to SP2.

4

What are the risks of not addressing CVE-2004-1758?

If CVE-2004-1758 is not addressed, local users may gain unauthorized access to sensitive database information, leading to potential privilege escalation.

5

Can I mitigate CVE-2004-1758 without upgrading?

Mitigating CVE-2004-1758 without upgrading is challenging, but you can limit local user access to the configuration files where credentials are stored.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203