dbcve.org
Weblogic ServerApplication · Bea

CVE-2005-1746

MEDIUM · 5.0 CVSS v2.0 Published 2005-05-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
The cluster cookie parsing code in BEA WebLogic Server 7.0 through Service Pack 5 attempts to contact any host or port specified in a cookie, even when it is not in the cluster, which allows remote attackers to cause a denial of service (cluster slowdown) via modified cookies.

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

The cluster cookie parsing code in BEA WebLogic Server 7.0 through Service Pack 5 does not validate that the host and port specified in a cluster cookie belong to legitimate cluster members before attempting to contact them. This allows remote attackers to send modified cookies containing arbitrary hosts/ports, causing the server to initiate connections to unintended targets and resulting in cluster slowdown or denial of service.

MitigationImplement validation logic to ensure the cookie-specified host and port correspond to a known cluster member before attempting connection; alternatively, upgrade to a patched WebLogic version. Network segmentation can provide additional defense-in-depth.

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:= 6.0= 6.1= 7.0= 7.0.0.1= 8.1
Weblogic PortalApplication
Affected:= 8.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
Authentication
None
Confidentiality
None
Integrity
None
Availability
Partial

AV:N/AC:L/Au:N/C:N/I:N/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 installed WebLogic version
    Check the WebLogic installation directory for version information. In the BEA_HOME or ORACLE_HOME, examine the registry.xml or product.ini file, or run the WebLogic version command (java -jar weblogic.jar) if available.
    Affected if The installed version is 6.0, 6.1, 7.0, 7.0.0.1, 8.1 (Server) or 8.0 (Portal), matching the affected ranges.
  2. Confirm clustering is enabled
    Locate the WebLogic configuration file (config.xml) for the domain and examine whether ClusterMBean or cluster-related configuration elements are defined. Check the WebLogic Administration Console for active cluster deployments.
    Affected if Clustering is enabled and the server is part of a WebLogic cluster configuration.
  3. Review cluster cookie configuration
    In the WebLogic Administration Console, navigate to the cluster configuration settings and inspect the cluster cookie parameters. Alternatively, examine the config.xml file for <cluster> elements and their cookie-related attributes.
    Affected if Cluster cookies are in use and no additional host/port validation is configured for incoming cluster cookie values.
  4. Check for custom cookie validation
    Search the WebLogic domain directory for custom security filters or validation logic that specifically validates cluster cookie host/port values against known cluster members. Look in the lib or applications directories.
    Affected if No custom validation logic exists to verify that cookie-specified hosts and ports correspond to legitimate cluster members.

A user is affected if running a vulnerable WebLogic version (6.0 through 8.1 for Server, 8.0 for Portal) with clustering enabled and without custom validation of cluster cookie host/port values.

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

Implement validation logic to ensure the cookie-specified host and port correspond to a known cluster member before attempting connection; alternatively, upgrade to a patched WebLogic version. Network segmentation can provide additional defense-in-depth.

Fix this in Weblogic Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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