dbcve.org
Jboss Enterprise Application PlatformApplication · Redhat

CVE-2010-3708

HIGH · 7.5 CVSS v2.0 Published 2010-12-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
The serialization implementation in JBoss Drools in Red Hat JBoss Enterprise Application Platform (aka JBoss EAP or JBEAP) 4.3 before 4.3.0.CP09 and JBoss Enterprise SOA Platform 4.2 and 4.3 supports the embedding of class files, which allows remote attackers to execute arbitrary code via a crafted static initializer.

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 confidence

This is a Java deserialization vulnerability in JBoss Drools. The serialization implementation allows embedding of class files, enabling remote attackers to inject and execute arbitrary code via a crafted static initializer in serialized objects. This leads to complete remote code execution on the affected server.

MitigationUpgrade JBoss EAP to version 4.3.0.CP09 or later, or JBoss Enterprise SOA Platform to a patched version. If immediate patching is not possible, disable Drools serialization or restrict network access to the affected service.

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
Jboss Enterprise Application PlatformApplication
Affected:= 4.3.0
Jboss Enterprise Soa PlatformApplication
Affected:= 4.2.0= 4.3.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed JBoss product and version
    Check the version manifest or release files in the JBoss installation directory. For JBoss EAP, look in $JBOSS_HOME/etc/myproject.properties or release.properties. For JBoss SOA, check the version.info or similar release file.
    Affected if The installed version is exactly JBoss EAP 4.3.0 or JBoss Enterprise SOA Platform 4.2.0 or 4.3.0
  2. Confirm Drools component is deployed
    Inspect the deployments directory (typically $JBOSS_HOME/server/<profile>/deploy/) for drools-core.jar or drools-compiler.jar files. Also check the lib directory for drools-related JAR files.
    Affected if Drools libraries (drools-core, drools-compiler, or drools-jsr94) are present in the deployments or lib folder
  3. Verify Java serialization is enabled for Drools
    Look for serialization-related configuration in the JBoss configuration files or the drools-decisiontables configuration. Check if the Drools serialization API is being used by inspecting the application code or configuration for ObjectInputStream/ObjectOutputStream usage with Drools objects.
    Affected if Drools serialization is actively enabled and the application uses serialized Drools objects (such as KnowledgeAgent or RuleSet) over network or storage
  4. Check network exposure of Drools services
    Review JBoss remoting or JMX configuration files (jboss-services.xml, jboss-remoting-sar.xml) to determine if Drools-related MBeans or services are exposed on accessible network ports.
    Affected if Drools services or MBeans are accessible over the network without authentication or proper filtering

You are affected if you are running JBoss EAP 4.3.0 or JBoss Enterprise SOA Platform 4.2.0/4.3.0 with the Drools component deployed and its serialization feature enabled and accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade JBoss EAP to version 4.3.0.CP09 or later, or JBoss Enterprise SOA Platform to a patched version. If immediate patching is not possible, disable Drools serialization or restrict network access to the affected service.

Fix this in Jboss Enterprise Application Platform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-3708 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-3708 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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