CVE-2006-0424: Medium severity Bea WebLogic Server vulnerability

Published Jan 25, 2006
·
Updated

BEA WebLogic Server and WebLogic Express 8.1 through SP4, 7.0 through SP6, and 6.1 through SP7 allows remote authenticated guest users to read the server log and obtain sensitive configuration information.

Affected Software

33 affected components
Bea WebLogic Server=7.0-sp2
Bea WebLogic Server=6.1-sp4
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=6.1-sp4
Bea WebLogic Server=6.1-sp7
Bea WebLogic Server=6.1-sp3
Bea WebLogic Server=7.0-sp6
Bea WebLogic Server=7.0-sp3
Bea WebLogic Server=8.1-sp3
Bea WebLogic Server=7.0-sp2
Bea WebLogic Server=7.0-sp3
Bea WebLogic Server=8.1-sp4
Bea WebLogic Server=7.0-sp5
Bea WebLogic Server=7.0-sp5
Bea WebLogic Server=6.1-sp1
Bea WebLogic Server=8.1-sp1
Bea WebLogic Server=8.1-sp3
Bea WebLogic Server=8.1-sp2
Bea WebLogic Server=6.1-sp2
Bea WebLogic Server=7.0-sp1
Bea WebLogic Server=6.1-sp5
Bea WebLogic Server=8.1-sp1
Bea WebLogic Server=6.1-sp3
Bea WebLogic Server=7.0-sp1
Bea WebLogic Server=8.1-sp4
Bea WebLogic Server=6.1-sp2
Bea WebLogic Server=8.1-sp2
Bea WebLogic Server=6.1-sp7
Bea WebLogic Server=7.0-sp6
Bea WebLogic Server=7.0-sp4

Event History

Jan 25, 2006
CVE Published
11:07 PM
Jan 26, 2006
CVE Published
via MITRE·04:00 AM
Data Sourced
via MITRE·04:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2006-0424?

CVE-2006-0424 is considered a critical vulnerability due to the potential exposure of sensitive configuration information.

2

How do I fix CVE-2006-0424?

To fix CVE-2006-0424, update your BEA WebLogic Server to a version that includes the security patches addressing this vulnerability.

3

Who is affected by CVE-2006-0424?

All remote authenticated guest users of BEA WebLogic Server versions 6.1 through 8.1, up to SP4, are affected by CVE-2006-0424.

4

What kind of information can be exploited through CVE-2006-0424?

CVE-2006-0424 allows remote authenticated users to access server logs which can contain sensitive configuration details.

5

Is there a workaround for CVE-2006-0424?

Temporary workarounds for CVE-2006-0424 include restricting access to server logs and adjusting user permissions until a patch can be applied.

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