dbcve.org
Operational Decision ManagerApplication · Ibm

CVE-2014-6114

MEDIUM · 5.0 CVSS v2.0 Published 2014-12-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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 Hosted Transparent Decision Service in the Rule Execution Server in IBM WebSphere ILOG JRules 7.1 before MP1 FP5 IF43; WebSphere Operational Decision Management 7.5 before FP3 IF41; and Operational Decision Manager 8.0 before MP1 FP2 IF34, 8.5 before MP1 FP1 IF43, and 8.6 before IF8 allows remote attackers to read arbitrary files via an XML external entity declaration in conjunction with an entity reference, related to an XML External Entity (XXE) issue.

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 an XML External Entity (XXE) injection vulnerability in the Hosted Transparent Decision Service component of IBM WebSphere ILOG JRules and Operational Decision Manager. Attackers can exploit this by sending specially crafted XML requests containing external entity declarations to read arbitrary files from the server's filesystem.

MitigationApply the vendor-supplied interim fixes (IF) or maintenance packages (FP) as specified in the IBM security bulletin: MP1 FP5 IF43 for JRules 7.1, FP3 IF41 for ODM 7.5, and the appropriate IFs for versions 8.0-8.6. If patching is not immediately feasible, consider disabling the Hosted Transparent Decision Service or restricting XML input parsing.

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
Operational Decision ManagerApplication
Affected:= 8.0= 8.5= 8.6
Websphere Ilog JrulesApplication
Affected:= 7.1
Websphere Operational Decision ManagementApplication
Affected:= 7.5

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
None
Availability
None

AV:N/AC:L/Au:N/C:P/I:N/A:N

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 IBM product
    Check system for presence of IBM WebSphere ILOG JRules or IBM Operational Decision Manager by reviewing installed software packages, using system inventory tools, or locating typical installation directories for these products
    Affected if The product is IBM WebSphere ILOG JRules 7.1 or IBM Operational Decision Manager versions 7.5, 8.0, 8.5, or 8.6
  2. Verify product version
    Use vendor-provided commands or check version information files to determine the exact installed version of the IBM product identified in step 1
    Affected if Installed version matches exactly 7.1, 7.5, 8.0, 8.5, or 8.6 (or falls within these specific version numbers)
  3. Confirm Hosted Transparent Decision Service is enabled
    Review the product configuration or service settings to determine if the Hosted Transparent Decision Service component is active or exposed. Check service management consoles, configuration files, or running service status
    Affected if Hosted Transparent Decision Service is enabled and accessible to process incoming XML requests
  4. Check network exposure of XML endpoint
    Identify network listeners or endpoints that accept XML input for the decision service. Review web service configurations, application server bindings, or API exposure settings
    Affected if The service accepts XML requests from network sources, particularly untrusted inputs

You are affected if you have IBM WebSphere ILOG JRules 7.1, ODM 7.5, or ODM versions 8.0-8.6 installed AND the Hosted Transparent Decision Service is enabled and exposed to process XML requests.

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

Apply the vendor-supplied interim fixes (IF) or maintenance packages (FP) as specified in the IBM security bulletin: MP1 FP5 IF43 for JRules 7.1, FP3 IF41 for ODM 7.5, and the appropriate IFs for versions 8.0-8.6. If patching is not immediately feasible, consider disabling the Hosted Transparent Decision Service or restricting XML input parsing.

Fix this in Operational Decision Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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