CVE-2005-3583
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(1) Java Runtime Environment (JRE) and (2) Software Development Kit (SDK) 1.4.2_08, 1.4.2_09, and 1.5.0_05 and possibly other versions allow remote attackers to cause a denial of service (JVM unresponsive) via a crafted serialized object, such as a font object as demonstrated on JBoss.
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 · high confidenceThis is a denial of service vulnerability in JRE/SDK versions 1.4.2_08, 1.4.2_09, 1.5.0_05 and possibly other versions where a remote attacker can cause JVM unresponsiveness by sending a crafted serialized object (such as a font object) to an application that deserializes untrusted input, as demonstrated on JBoss.
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.2= 1.4.2_08= 1.4.2_09= 1.5.0_05CVSS 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
- Complete
AV:N/AC:L/Au:N/C:N/I:N/A:C
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 installed Java versionRun 'java -version' or 'java -fullversion' from command line to obtain the exact JRE/JDK version numberAffected if The version shown is 1.4.2_08, 1.4.2_09, 1.5.0_05, or falls within the 1.4.2 or 1.5.0 release families (prior to patches)
-
Check for Java deserialization usageSearch application source code and configuration for use of ObjectInputStream, java.io.Deserialize, or similar deserialization methods, or examine network traffic for serialized Java objectsAffected if The application deserializes objects from untrusted sources without validation
-
Identify exposed deserialization endpointsReview application server configuration and deployed web services for endpoints that accept serialized objects (common paths include /invoker/JMXInvoker, /invoker/RMIInvoker, or custom SOAP/REST services using Java serialization)Affected if The application exposes network endpoints that accept and deserialize untrusted serialized data
-
Check for known vulnerable frameworksExamine deployed applications for known vulnerable components such as older JBoss versions, WebLogic, or other Java EE application servers that handle serialized objectsAffected if Running legacy JBoss or similar application servers that deserialize untrusted input on exposed network interfaces
You are affected if your environment runs a vulnerable Sun JRE/SDK version (1.4.2_08, 1.4.2_09, 1.5.0_05, or unpatched 1.4.2/1.5.0) AND your application exposes deserialization of untrusted 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 Java version and avoid deserializing untrusted serialized objects, or implement deserialization allowlists/whitelisting to block malicious objects.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-3583 — 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-3583 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