CVE-2007-2696: Medium severity Bea WebLogic Server vulnerability

Published May 16, 2007
·
Updated

The JMS Server in BEA WebLogic Server 6.1 through SP7, 7.0 through SP6, and 8.1 through SP5 enforces security access policies on the front end, which allows remote attackers to access protected queues via direct requests to the JMS back-end server.

Affected Software

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

Remediation

Event History

May 16, 2007
CVE Published
via MITRE·01:00 AM
Data Sourced
via MITRE·01:00 AM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2007-2696?

The severity of CVE-2007-2696 is considered critical due to its potential for unauthorized access to protected JMS queues.

2

How do I fix CVE-2007-2696?

To fix CVE-2007-2696, update your BEA WebLogic Server to a version that is not vulnerable, specifically beyond SP7 for versions 6.1, beyond SP6 for version 7.0, and beyond SP5 for version 8.1.

3

What systems are affected by CVE-2007-2696?

CVE-2007-2696 affects BEA WebLogic Server versions 6.1 through SP7, 7.0 through SP6, and 8.1 through SP5.

4

What types of attacks are possible with CVE-2007-2696?

Attackers can exploit CVE-2007-2696 to remotely access and manage protected JMS queues by bypassing security policies.

5

Is there a workaround for CVE-2007-2696 while waiting for a patch?

While an official workaround is not specified, restricting access to the JMS server and implementing additional network security measures can help mitigate risks.

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