dbcve.org
Jboss Bpm SuiteApplication · Redhat

CVE-2013-6468

MEDIUM · 6.5 CVSS v2.0 Published 2014-04-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
JBoss Drools, Red Hat JBoss BRMS before 6.0.1, and Red Hat JBoss BPM Suite before 6.0.1 allows remote authenticated users to execute arbitrary Java code via a (1) MVFLEX Expression Language (MVEL) or (2) Drools expression.

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

JBoss Drools, BRMS, and BPM Suite before version 6.0.1 contain a vulnerability allowing remote authenticated users to execute arbitrary Java code through MVFLEX Expression Language (MVEL) or Drools expression inputs. This is a critical code injection flaw in the business rules engine that permits full code execution by any user with authenticated access to the Drools interfaces.

MitigationUpgrade to JBoss BRMS/BPM Suite 6.0.1 or later which contains the patched version. If immediate patching is not feasible, restrict network access to Drools/BRMS/BPM Suite interfaces to only trusted administrative users.

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 Bpm SuiteApplication
Affected:= 6.0.0
Jboss DroolsApplication
Affected:all versions
Jboss Enterprise Brms PlatformApplication
Affected:= 6.0.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
Single
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:S/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 installed Drools/BRMS/BPM Suite version
    Check the JAR manifest files or the product version information in the JBoss installation directory. Look for version details in the drools-core, knowledge-api, or brms-platform JAR files, or check the application server's version reporting for JBoss BPM Suite or BRMS.
    Affected if The installed version is 6.0.0 for BPM Suite or BRMS, or any version of Drools prior to 6.0.1.
  2. Verify Drools Workbench or Decision Central is accessible
    Check if the Drools workbench (drools-wb) or BRMS/BPM Suite console interfaces are deployed and network-accessible. Look for endpoints such as /drools-wb, /business-central, or /kie-wb on the application server.
    Affected if The Drools/BRMS/BPM Suite web interfaces are exposed without proper access restrictions.
  3. Confirm MVEL or Drools expression evaluation is enabled
    Review the deployed knowledge bases and rule packages to determine if custom MVEL expressions or Drools expression language inputs are accepted as part of rule definitions, decision tables, or guided decision tables.
    Affected if Users with authenticated access can define or modify rules containing MVEL or Drools expressions that get evaluated by the engine.
  4. Check authentication configuration for Drools endpoints
    Examine the web.xml or jboss-web.xml deployment descriptors for the Drools/BRMS/BPM Suite applications to verify the authentication mechanism and role-based access controls protecting the rule authoring interfaces.
    Affected if The interfaces allow authenticated users to submit rule definitions without additional sandboxing or expression restriction.

You are affected if your JBoss Drools/BRMS/BPM Suite version is 6.0.0 or any version prior to 6.0.1, and the Drools workbench or expression evaluation features are accessible to authenticated users.

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 to JBoss BRMS/BPM Suite 6.0.1 or later which contains the patched version. If immediate patching is not feasible, restrict network access to Drools/BRMS/BPM Suite interfaces to only trusted administrative users.

Fix this in Jboss Bpm Suite Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-6468 — 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-2013-6468 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