CVE-2014-8125: Improper Input Validation in Drools and jBPM

CVE-2014-8125 · Severity: info · Published 2022-05-17

Improper Input Validation in Drools and jBPM

Technologies: org.drools:drools-core (Maven). Vendors: Maven.

Quick answers

Is CVE-2014-8125 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2014-8125 being exploited in the wild.
How severe is CVE-2014-8125?
Informational severity, published 17 May 2022.
Which products and versions are affected?
org.drools:drools-core (Maven) ECOSYSTEM:introduced=0,fixed=6.2.0.Final; org.jbpm:jbpm-bpmn2 (Maven) ECOSYSTEM:introduced=0,fixed=6.2.0.Final.
Is there a fix for CVE-2014-8125?
Yes. org.drools:drools-core (Maven): upgrade to 6.2.0.Final or later; org.jbpm:jbpm-bpmn2 (Maven): upgrade to 6.2.0.Final or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2014-8125?
Check whether you run org.drools:drools-core (Maven) or org.jbpm:jbpm-bpmn2 (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.drools:drools-core (Maven): upgrade to 6.2.0.Final or later
    # set org.drools:drools-core to 6.2.0.Final in your pom.xml or build.gradle
  • org.jbpm:jbpm-bpmn2 (Maven): upgrade to 6.2.0.Final or later
    # set org.jbpm:jbpm-bpmn2 to 6.2.0.Final in your pom.xml or build.gradle

Affected products

  • org.drools:drools-core (Maven) ECOSYSTEM:introduced=0,fixed=6.2.0.Final
  • org.jbpm:jbpm-bpmn2 (Maven) ECOSYSTEM:introduced=0,fixed=6.2.0.Final

Identifiers

  • CVE-2014-8125
  • GHSA-6qx9-rf9g-7jmr

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.