CVE-2010-0850
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 · uneditedUnspecified vulnerability in the Java 2D component in Oracle Java SE and Java for Business 1.3.1_27 allows remote attackers to affect confidentiality, integrity, and availability via unknown 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 an unspecified vulnerability in the Java 2D component affecting Java SE and Java for Business 1.3.1_27. The CVSS 7.5 score indicates high-severity impact allowing remote attackers to affect confidentiality, integrity, and availability via unknown vectors, likely enabling arbitrary code execution.
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.3.1_27= 1.3.0= 1.3.0_01= 1.3.0_02= 1.3.0_03= 1.3.0_04= 1.3.0_05= 1.3.1= 1.3.1_01= 1.3.1_01a= 1.3.1_02= 1.3.1_03<= 1.3.1_27= 1.3.0= 1.3.1= 1.3.1_2= 1.3.1_03= 1.3.1_04= 1.3.1_05= 1.3.1_06= 1.3.1_07= 1.3.1_08= 1.3.1_09= 1.3.1_10<= 1.3.1_27= 1.3.0= 1.3.0_01= 1.3.0_02= 1.3.0_03= 1.3.0_04= 1.3.0_05= 1.3.1= 1.3.1_01= 1.3.1_01a= 1.3.1_02= 1.3.1_03CVSS 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.
-
Detect Java installationRun 'java -version' from command line or check for java.exe in common paths like C:\Program Files\Java\ or /usr/lib/jvm/Affected if No Java installation found means not affected
-
Identify Java versionExecute 'java -version' and examine the output version string (e.g., 1.3.1_27)Affected if Version string starts with 1.3.x or shows 1.3.1_27 or earlier indicates affected version
-
Check for JRE specificallyLook for jre directory under Java installation paths and run 'jre\bin\java -version' if separate from JDKAffected if Standalone JRE at version 1.3.1_27 or earlier indicates affected installation
-
Enumerate all Java installationsSearch system for multiple java.exe instances: 'where java' on Windows or 'which -a java' on Unix-like systemsAffected if Any discovered installation matching 1.3.x versions indicates affected environment
Your environment is affected if any Java installation reports version 1.3.x up to and including 1.3.1_27.
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 Java to a patched version or migrate to a supported Java version, as Java 1.3.1 is end-of-life; locate and remediate all vulnerable Java installations in the environment.
- Consultation4.0 h
- Implementation2.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,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-0850 — 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-2010-0850 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