CVE-2024-22320
Published: 02 February 2024
Summary
CVE-2024-22320 is a critical-severity Deserialization of Untrusted Data (CWE-502) vulnerability in Ibm Operational Decision Manager. Its CVSS base score is 9.8 (Critical).
Operationally, ranked in the top 0.4% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
IBM Operational Decision Manager 8.10.3 contains an unsafe deserialization flaw tracked as CVE-2024-22320 and CWE-502. The vulnerability resides in the handling of serialized objects and enables remote code execution when untrusted input is processed.
A remote authenticated attacker can exploit the issue by submitting a specially crafted request, resulting in arbitrary code execution under the SYSTEM context. The flaw is rated 9.8 on CVSS 3.1 with an attack vector of network, no required privileges or user interaction, and full impact on confidentiality, integrity, and availability.
IBM has published remediation guidance at its support pages referenced under X-Force ID 279146. The associated EPSS score currently stands at 0.9084 with a recorded peak of 0.9233, and public technical write-ups detail the Java deserialization path used to reach code execution.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-19881
Vulnerability details
IBM Operational Decision Manager 8.10.3 could allow a remote authenticated attacker to execute arbitrary code on the system, caused by an unsafe deserialization. By sending specially crafted request, an attacker could exploit this vulnerability to execute arbitrary code in the…
more
context of SYSTEM. IBM X-Force ID: 279146.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Penetration testing supplies malicious serialized objects, detecting unsafe deserialization and supporting corrective actions.
Evaluation of untrusted data handling (deserialization testing) reveals unsafe processing, which the required remediation process addresses.
Untrusted serialized data can be deserialized and observed inside the chamber, blocking gadget-chain exploitation outside the sandbox.
Validates or rejects untrusted serialized data before deserialization occurs.
Identifies and blocks malicious code introduced through deserialization of untrusted data at system boundaries.
Integrity verification of serialized information can detect tampering before deserialization occurs.
Provenance of associated data allows detection of untrusted sources before deserialization or processing occurs.