CVE-2005-4750
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 · uneditedBEA WebLogic Server and WebLogic Express 8.1 SP4 and earlier, 7.0 SP5 and earlier, and 6.1 SP7 and earlier allow remote attackers to cause a denial of service (server thread hang) via unknown attack vectors.
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 confidenceThis is a denial of service vulnerability in BEA WebLogic Server and WebLogic Express affecting versions 8.1 SP4 and earlier, 7.0 SP5 and earlier, and 6.1 SP7 and earlier. Remote attackers can cause server threads to hang, rendering the server unavailable. The specific attack vectors are not disclosed in the available description.
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= 6.1= 7.0= 8.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed WebLogic Server versionLocate the WebLogic installation directory and check the version file or startup logs. Common locations include the registry (Windows) or the BEA_HOME directory. Look for a version identifier in the format such as 6.1, 7.0, or 8.1.Affected if The installed version is 6.1, 7.0, or 8.1
-
Determine the installed service pack levelCheck the service pack version through the WebLogic console, startup logs, or the registry/manifest files in the BEA_HOME directory. The service pack is typically labeled as SP1, SP2, SP3, etc.Affected if The service pack is SP7 or lower for version 6.1, SP5 or lower for version 7.0, or SP4 or lower for version 8.1
-
Verify the exact version and SP combinationCompare your identified version and service pack against the affected ranges: 6.1 SP7 and earlier, 7.0 SP5 and earlier, or 8.1 SP4 and earlier.Affected if The version and service pack combination falls within any of the affected ranges listed
-
Confirm network exposure of the WebLogic administration or application portsReview your firewall rules and network configuration to determine if the WebLogic listen ports (typically 7001 for admin, or custom application ports) are accessible from untrusted networks.Affected if The WebLogic server ports are exposed to the internet or untrusted external networks, making it a reachable target for remote DoS attacks
You are affected if your WebLogic Server installation is version 6.1 with SP7 or earlier, version 7.0 with SP5 or earlier, or version 8.1 with SP4 or earlier, and the server is network-accessible to potential attackers.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade WebLogic Server to a version beyond the affected service packs (8.1 SP5+, 7.0 SP6+, 6.1 SP8+) or to a currently supported major version release.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-4750 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2005-4750 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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