What is the severity of CVE-2006-0421?

CVE-2006-0421 is considered a moderate vulnerability due to the potential for unauthorized privilege escalation between web application domains.

How do I fix CVE-2006-0421?

To mitigate CVE-2006-0421, it is recommended to restrict the ability to create and manage domains in BEA WebLogic Server to trusted administrators only.

Who is affected by CVE-2006-0421?

CVE-2006-0421 affects administrators using BEA WebLogic Server versions 6.1 and 7.0 when multiple domains are created on the same machine.

What are the potential risks associated with CVE-2006-0421?

The risks of CVE-2006-0421 include unauthorized access to sensitive data and escalation of privileges across different domains.

When was CVE-2006-0421 disclosed?

CVE-2006-0421 was disclosed in January 2006.

Vulnerability/
CVE-2006-0421

medium

4.6

CWE

NVD-CWE-Other

25/1/2006

7/8/2024

CVE-2006-0421

First published: Wed Jan 25 2006(Updated: )

By design, BEA WebLogic Server and WebLogic Express 7.0 and 6.1, when creating multiple domains from the same WebLogic instance on the same machine, allows administrators of any created domain to access other created domains, which could allow administrators to gain privileges that were not intended.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Oracle WebLogic Server	=6.1
Oracle WebLogic Server	=7.0
Oracle WebLogic Server	=6.1
Oracle WebLogic Server	=7.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2006-0421?
CVE-2006-0421 is considered a moderate vulnerability due to the potential for unauthorized privilege escalation between web application domains.
How do I fix CVE-2006-0421?
To mitigate CVE-2006-0421, it is recommended to restrict the ability to create and manage domains in BEA WebLogic Server to trusted administrators only.
Who is affected by CVE-2006-0421?
CVE-2006-0421 affects administrators using BEA WebLogic Server versions 6.1 and 7.0 when multiple domains are created on the same machine.
What are the potential risks associated with CVE-2006-0421?
The risks of CVE-2006-0421 include unauthorized access to sensitive data and escalation of privileges across different domains.
When was CVE-2006-0421 disclosed?
CVE-2006-0421 was disclosed in January 2006.

agent/references
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/remedy
agent/last-modified-date
agent/severity
agent/author
agent/description
agent/first-publish-date
agent/weakness
agent/event
agent/source
agent/tags
collector/nvd-historical
agent/software-canonical-lookup-request
collector/nvd-index
vendor/bea
canonical/oracle weblogic server
version/oracle weblogic server/6.1
version/oracle weblogic server/7.0

Company

Resources

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.

Frequently Asked Questions

What is the severity of CVE-2006-0421?
CVE-2006-0421 is considered a moderate vulnerability due to the potential for unauthorized privilege escalation between web application domains.
How do I fix CVE-2006-0421?
To mitigate CVE-2006-0421, it is recommended to restrict the ability to create and manage domains in BEA WebLogic Server to trusted administrators only.
Who is affected by CVE-2006-0421?
CVE-2006-0421 affects administrators using BEA WebLogic Server versions 6.1 and 7.0 when multiple domains are created on the same machine.
What are the potential risks associated with CVE-2006-0421?
The risks of CVE-2006-0421 include unauthorized access to sensitive data and escalation of privileges across different domains.
When was CVE-2006-0421 disclosed?
CVE-2006-0421 was disclosed in January 2006.

CVE-2006-0421

Remedy

Remedy

Remedy

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2006-0421?

How do I fix CVE-2006-0421?

Who is affected by CVE-2006-0421?

What are the potential risks associated with CVE-2006-0421?

When was CVE-2006-0421 disclosed?

Company

Resources

Contact

Frequently Asked Questions

What is the severity of CVE-2006-0421?

How do I fix CVE-2006-0421?

Who is affected by CVE-2006-0421?

What are the potential risks associated with CVE-2006-0421?

When was CVE-2006-0421 disclosed?