dbcve.org
Weblogic ServerApplication · Bea

CVE-2005-1744

CRITICAL · 9.8 CVSS v3.1 Published 2005-05-24
Fix available
A fix is available. Upgrade to after 7.0 or later.
See remediation →
100/100
Remediation priority · Urgent
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 WebLogic Express 7.0 through Service Pack 5 does not log out users when an application is redeployed, which allows those users to continue to access the application without having to log in again, which may be in violation of newly changed security constraints or role mappings.

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 · moderate confidence

BEA WebLogic Server and WebLogic Express versions 7.0 through Service Pack 5 fail to invalidate user sessions when an application is redeployed. This session persistence allows authenticated users to continue accessing the application without re-authentication, bypassing any updated security constraints or role mappings that may have changed in the new deployment.

MitigationUpgrade to WebLogic Server version 7.0 Service Pack 6 or later, which includes the session invalidation fix. If upgrade is not feasible, implement manual session invalidation scripts or processes before application redeployment.

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

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 directory for version information. Look for a file called 'version.txt' or check the registry/console for the exact version and Service Pack level. Common paths: BEA_HOME/weblogic700/ or check the startWebLogic.cmd/.sh script for version strings.
    Affected if The installed version is WebLogic Server or WebLogic Express 7.0 through Service Pack 5 (SP5)
  2. Verify session-based authentication is in use
    Inspect the application's web.xml deployment descriptor (or the equivalent WebLogic deployment plan) for <session-config> elements. Also check if applications use form-based or certificate authentication that creates user sessions.
    Affected if Applications are configured to use session-based authentication (HTTP sessions) for securing access
  3. Check for recent or planned application redeployment
    Review WebLogic console or admin logs for redeployment events (look for 'Redeploy' or 'Undeploy' commands, or the 'isRedeploying' method calls). Check deployment timestamps against security constraint updates.
    Affected if Applications have been or will be redeployed after security constraint or role mapping changes without manual session invalidation
  4. Inspect session persistence configuration
    Check the application's session descriptor in weblogic.xml or the WebLogic console for session persistence settings. Look for <session-descriptor> with persistent-store-type settings.
    Affected if Session persistence is enabled and the server was not restarted after redeployment

You are affected if running WebLogic Server/Express 7.0 through SP5 AND you use session-based authentication AND applications with updated security constraints have been redeployed without manual session invalidation.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 7.0
Interim mitigation

Upgrade to WebLogic Server version 7.0 Service Pack 6 or later, which includes the session invalidation fix. If upgrade is not feasible, implement manual session invalidation scripts or processes before application redeployment.

Recommended fix Moderate confidence

WebLogic Server 8.1 or later (e.g., 9.x, 10.x)

  1. Upgrade from WebLogic Server 7.0 to WebLogic Server 8.1 or later. Newer versions handle session invalidation properly during application redeployment.
  2. After upgrading, verify that user sessions are properly invalidated when applications are redeployed by testing the redeployment scenario with test user accounts.
  3. Ensure that any custom security configurations or role mappings are reviewed after the upgrade to confirm they are enforced correctly.
Caveat Upgrading from WebLogic 7.0 to 8.x may require application code changes due to API differences; conduct thorough compatibility testing before production deployment.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Weblogic Server Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2005-1744 — 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-2005-1744 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