CVE-2005-1749
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 · uneditedBuffer overflow in BEA WebLogic Server and WebLogic Express 6.1 Service Pack 4 allows remote attackers to cause a denial of service (CPU consumption from thread looping).
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 confidenceBuffer overflow vulnerability in BEA WebLogic Server and WebLogic Express 6.1 Service Pack 4 allows remote attackers to cause denial of service via CPU consumption from thread looping. The overflow triggers infinite looping in server threads, exhausting CPU resources.
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.0= 6.1= 7.0= 7.0.0.1= 8.1= 8.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify WebLogic Server versionCheck the installed WebLogic version by examining the registry (on Windows) or the installation directory for version files. Common locations: BEA_HOME/weblogic/version.txt or check the product version through the WebLogic administration console under 'Server' > 'General' tab.Affected if The installed version matches 6.0, 6.1, 7.0, 7.0.0.1, or 8.1 for WebLogic Server; or version 8.0 for Oracle Weblogic Portal.
-
Confirm WebLogic administration port exposureIdentify which ports the WebLogic administration service is listening on. Check configuration files (config.xml) in the domain directory, or run 'netstat -an' or 'ss -tlnp' to identify open ports associated with the WebLogic process.Affected if The administration port (typically 7001 for default installations) is accessible from untrusted networks.
-
Verify if HTTP cluster or servlet container is enabledExamine the config.xml file in the WebLogic domain directory for <Server> or <Application> elements that enable HTTP-related services. Check if the WebLogic servlet container is running.Affected if HTTP servlet container or cluster services are active and processing requests on the affected version.
-
Monitor for thread exhaustion symptomsUse operating system tools (top, htop, Windows Task Manager) to observe WebLogic process CPU usage. Use WebLogic administration console or JMX to check thread pool statistics - look for threads in 'STUCK' or infinite loop states.Affected if CPU consumption spikes to near-100% with thread count remaining high and no progress in request processing.
You are affected if running WebLogic Server 6.0, 6.1, 7.0, 7.0.0.1, or 8.1 (or Weblogic Portal 8.0) with the administration/HTTP interface exposed and experiencing unexplained thread exhaustion.
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 dataApply available patches for WebLogic 6.1 or migrate to a supported WebLogic version, as version 6.1 is end-of-life. Implement network-level filtering to restrict unauthorized access to the WebLogic administration ports.
- 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-1749 — 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-1749 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