CVE-2005-0223
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 · uneditedThe Software Development Kit (SDK) and Run Time Environment (RTE) 1.4.1 and 1.4.2 for Tru64 UNIX allows remote attackers to cause a denial of service (Java Virtual Machine hang) via object deserialization.
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 confidenceThe vulnerability exists in the Java Virtual Machine components of Tru64 UNIX SDK and RTE versions 1.4.1 and 1.4.2. Remote attackers can trigger a denial of service by sending specially crafted serialized Java objects that cause the JVM to hang during deserialization.
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= 1.4.1= 1.4.2= 1.4.1= 1.4.2all versionsCVSS 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 the Java Runtime Environment versionRun 'java -version' or check the JRE package version on the system. On Tru64, you may also use 'swlist -v' to list installed software packages and look for SunJRE or SunSDK packages.Affected if The installed JRE or JDK version is exactly 1.4.1 or 1.4.2 (Sun Rte or Sun Sdk)
-
Confirm the operating system is Tru64 UNIXRun 'uname -a' or 'uname -srv' to identify the OS. Tru64 UNIX may also appear as Compaq Tru64 in system inventories.Affected if The system is running Compaq Tru64 or Tru64 UNIX with Java components installed
-
Identify Java processes accepting network connectionsUse 'netstat -an' or 'lsof -i' to list network listeners. Check for Java processes listening on TCP ports, particularly those that may handle serialized object streams (RMI, JMX, custom socket servers).Affected if Java applications are listening on network ports and could receive serialized object data from remote sources
-
Verify if deserialization is in useReview application configurations and code for use of ObjectInputStream, java.io.Serializable, RMI registries, or similar mechanisms that process serialized Java objects from untrusted sources.Affected if Applications use Java deserialization to process data from network sources without input validation
A user is affected if running Tru64 UNIX with Sun JRE/SDK versions 1.4.1 or 1.4.2, or any Java-enabled Tru64 system, with Java applications that accept serialized objects over the network.
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 to a patched version of Tru64 UNIX Java components, or if unsupported, disable Java deserialization in exposed applications and consider migrating to a supported platform.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2005-0223 — 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-0223 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