CVE-2005-4766: Medium severity Bea WebLogic Server vulnerability

Published Dec 31, 2005
·
Updated

BEA WebLogic Server and WebLogic Express 8.1 SP4 and earlier, and 7.0 SP5 and earlier, do not encrypt multicast traffic, which might allow remote attackers to read sensitive cluster synchronization messages by sniffing the multicast traffic.

Affected Software

33 affected components
Bea WebLogic Server=7.0
Bea WebLogic Server=7.0
Bea WebLogic Server=7.0
Bea WebLogic Server=7.0-sp1
Bea WebLogic Server=7.0-sp1
Bea WebLogic Server=7.0-sp1
Bea WebLogic Server=7.0-sp2
Bea WebLogic Server=7.0-sp2
Bea WebLogic Server=7.0-sp2
Bea WebLogic Server=7.0-sp3
Bea WebLogic Server=7.0-sp3
Bea WebLogic Server=7.0-sp3
Bea WebLogic Server=7.0-sp4
Bea WebLogic Server=7.0-sp4
Bea WebLogic Server=7.0-sp4
Bea WebLogic Server=7.0-sp5
Bea WebLogic Server=7.0-sp5
Bea WebLogic Server=7.0-sp5
Bea WebLogic Server=8.1
Bea WebLogic Server=8.1
Bea WebLogic Server=8.1
Bea WebLogic Server=8.1-sp1
Bea WebLogic Server=8.1-sp1
Bea WebLogic Server=8.1-sp1
Bea WebLogic Server=8.1-sp2
Bea WebLogic Server=8.1-sp2
Bea WebLogic Server=8.1-sp2
Bea WebLogic Server=8.1-sp3
Bea WebLogic Server=8.1-sp3
Bea WebLogic Server=8.1-sp3
Bea WebLogic Server=8.1-sp4
Bea WebLogic Server=8.1-sp4
Bea WebLogic Server=8.1-sp4

Event History

Dec 31, 2005
CVE Published
05:00 AM
Apr 1, 2006
CVE Published
via MITRE·02:00 AM
Data Sourced
via MITRE·02:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2005-4766?

CVE-2005-4766 has been classified as a high severity vulnerability due to its potential to expose sensitive information.

2

How do I fix CVE-2005-4766?

To fix CVE-2005-4766, you should upgrade to a version of BEA WebLogic Server that encrypts multicast traffic.

3

What versions are affected by CVE-2005-4766?

CVE-2005-4766 affects BEA WebLogic Server versions 8.1 SP4 and earlier, and 7.0 SP5 and earlier.

4

What potential risks are associated with CVE-2005-4766?

The primary risk of CVE-2005-4766 is that remote attackers could intercept and read sensitive cluster synchronization messages.

5

Is there a workaround for CVE-2005-4766?

While the recommended solution is to upgrade, temporarily restricting multicast traffic may mitigate some risks associated with CVE-2005-4766.

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