Security Resilience

CVE-2024-22319

Ibm Operational Decision Manager 8.10.3 … 8.12.0.1

High EPSS
Published
02 February 2024
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 8.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.76 99.5th percentile
Risk Priority 85 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-22319 is a high-severity Injection (CWE-74) vulnerability in Ibm Operational Decision Manager. Its CVSS base score is 8.1 (High).

Operationally, ranked in the top 0.5% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

IBM Operational Decision Manager versions 8.10.3, 8.10.4, 8.10.5.1, 8.11, 8.11.0.1, 8.11.1, and 8.12.0.1 contain a remote code execution flaw (CVE-2024-22319) that stems from JNDI injection. The issue occurs when an unchecked argument is supplied to a specific API, allowing an attacker to influence directory or naming lookups and ultimately execute arbitrary code. The vulnerability is tracked under CWE-74 and carries a CVSS 3.1 score of 8.1.

An unauthenticated remote attacker can trigger the flaw over the network by crafting a malicious request that passes a controlled value into the affected API. Successful exploitation yields full control over the confidentiality, integrity, and availability of the decision-manager instance, although the attack requires high complexity because of the need to reach and manipulate the vulnerable code path.

IBM has published remediation guidance on its support portal and X-Force exchange that addresses the affected releases and outlines available fixes or configuration changes. The current EPSS score of 0.87 with a recorded peak of 0.91 indicates sustained and elevated exploitation interest following disclosure.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

IBM Operational Decision Manager 8.10.3, 8.10.4, 8.10.5.1, 8.11, 8.11.0.1, 8.11.1 and 8.12.0.1 is susceptible to remote code execution attack via JNDI injection when passing an unchecked argument to a certain API. IBM X-Force ID: 279145.

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-7770Same vendor: Ibm
CVE-2024-31882Same vendor: Ibm
CVE-2023-35895Same vendor: Ibm
CVE-2020-17496Shared CWE-74
CVE-2025-20281Shared CWE-74
CVE-2023-43835Shared CWE-74
CVE-2025-25477Shared CWE-74
CVE-2024-6469Shared CWE-74
CVE-2023-49964Shared CWE-74
CVE-2023-44270Shared CWE-74

Affected Assets

ibm
operational decision manager
8.10.3, 8.10.4, 8.10.5.1, 8.11, 8.11.0.1

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SI-10 directly requires validation of information inputs to reject malformed or special-element content before it reaches downstream parsers.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.15 Logging partial match
finds

Logging supports detection of injection attempts but does not prevent the weakness.

finds

Monitoring activities can identify active injection attacks after they occur.

blocks

A.8.25 mandates a secure SDLC process that includes secure coding guidelines, security requirements, checkpoints, testing (scans/penetration), and developer training to reduce injection flaws, but does not itself enforce or guarantee neutralization of special elements at runtime.

blocks

Application security requirements explicitly call for controls against injection attacks in software design.

blocks

A.8.27 mandates security-by-design principles (including distrust external input, data validation/sanitization, secure architecture layers, and design reviews against attack patterns) that reach injection when applied to output construction; this stops exploitation for a minority slice (e.g. where principles drive sanitization) but leaves most code-level injection defects untouched without further implementation rigor.

prevents

Secure coding standards require proper neutralization of special elements, directly addressing CWE-74.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-74, a class-level weakness, and none of its children carries one either.

References