dbcve.org
Weblogic ServerApplication · Bea

CVE-2002-2141

HIGH · 7.5 CVSS v2.0 Published 2002-12-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
BEA WebLogic Server and Express 7.0 and 7.0.0.1, when running Servlets and Enterprise JavaBeans (EJB) on more than one server, will remove the security constraints and roles on all servers for any Servlets or EJB that are used by an application that is undeployed on one server, which could allow remote attackers to conduct unauthorized activities in violation of the intended restrictions.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

BEA WebLogic Server and Express 7.0 and 7.0.0.1 contains a flaw where security constraints and role mappings for Servlets and Enterprise JavaBeans are incorrectly removed cluster-wide when an application is undeployed on only one server in a multi-server cluster. This leaves those components unprotected on all other servers in the cluster.

MitigationUpgrade from the vulnerable WebLogic 7.0/7.0.0.1 versions to a patched version. Review and re-apply security constraints for all Servlets and EJBs after any undeployment operations in clustered environments.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Weblogic ServerApplication
Affected:= 7.0= 7.0.0.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify WebLogic Server version
    Check the WebLogic installation version using the command 'java -cp weblogic.jar utils.Version' or inspect the BEA_HOME directory for version files. Alternatively, access the WebLogic Administration Console and view the Server > Configuration > General tab.
    Affected if The installed version is exactly 7.0 or 7.0.0.1.
  2. Confirm clustered environment
    Access the WebLogic Administration Console and navigate to the cluster configuration page, or check the domain configuration file (config.xml) for multiple <Server> entries under a <Cluster> element.
    Affected if The environment contains multiple managed servers configured in a cluster.
  3. Review application deployment history
    Examine the WebLogic server logs and deployment records for any undeployment operations. Check the Administration Console under Deployments > Applications for any applications that were undeployed on a single server.
    Affected if Any Servlet or EJB application was undeployed on only one server in the cluster.
  4. Inspect Servlet security constraints
    Review the web.xml deployment descriptor for each Servlet application in the cluster. Compare the <security-constraint> definitions across all cluster members using the Administration Console or by inspecting the deployed application files.
    Affected if Security constraints defined in web.xml are missing or removed for any Servlet that was part of an application undeployed in the cluster.
  5. Inspect EJB role mappings
    Review the ejb-jar.xml and WebLogic-specific deployment descriptors (weblogic-ejb-jar.xml) for each EJB. Check the <security-role-assignment> and <method-permission> elements. Verify role mappings exist on all cluster servers.
    Affected if Role mappings for EJBs are missing or incorrect compared to the original configuration after an undeployment operation.

A user is affected if WebLogic Server version 7.0 or 7.0.0.1 is running in a clustered environment and any Servlet or EJB application has been undeployed on only one server in the cluster, resulting in missing security constraints or role mappings.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade from the vulnerable WebLogic 7.0/7.0.0.1 versions to a patched version. Review and re-apply security constraints for all Servlets and EJBs after any undeployment operations in clustered environments.

Fix this in Weblogic Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2002-2141 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2002-2141 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data