Cyber Resilience

CVE-2023-38020

Ibm Soar Qradar Plugin App 1.0 – 5.0.3

Published
02 February 2024
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 4.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
EPSS Score 0.0038 31th percentile
Risk Priority 37 floored blend · peak EPSS

Summary

CVE-2023-38020 is a medium-severity Improper Output Neutralization for Logs (CWE-117) vulnerability in Ibm Soar Qradar Plugin App. Its CVSS base score is 4.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Indicator Removal (T1070); ranked at the 31th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

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

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

IBM SOAR QRadar Plugin App 1.0 through 5.0.3 could allow an authenticated user to manipulate output written to log files. IBM X-Force ID: 260576.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1070 Indicator Removal Stealth
Adversaries may selectively delete or modify artifacts generated to reduce indications of their presence and blend in with legitimate activity.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-35150Same vendor: Ibm
CVE-2023-38019Same product: Ibm Soar Qradar Plugin App
CVE-2025-14684Same vendor: Ibm
CVE-2023-38263Same product: Ibm Soar Qradar Plugin App
CVE-2025-36159Same vendor: Ibm
CVE-2025-36114Same product: Ibm Soar Qradar Plugin App
CVE-2025-36081Same vendor: Ibm
CVE-2024-25047Same vendor: Ibm
CVE-2024-56473Same vendor: Ibm
CVE-2024-22356Same vendor: Ibm

Affected Assets

ibm
soar qradar plugin app
1.0 — 5.0.3

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover missing or incorrect output neutralization when log messages are constructed from untrusted input.

Input validation reduces the chance that specially crafted data reaches log-message construction routines.

Mitigating Controls (NIST CSF 2.0) AI

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

PR.PS-06 mostly match
prevents

Secure SDLC practices and coding standards directly require output sanitization for logs.

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.

finds

Security testing can detect log injection flaws but does not prevent them at the source.

A.8.15 Logging partial match
degrades

Logging control directly requires proper log generation and handling, which mitigates improper output neutralization.

finds

Monitoring activities rely on trustworthy logs but do not ensure log message integrity.

prevents

Secure SDLC includes coding standards that reduce log-related weaknesses but does not specifically address logging.

prevents

Secure coding practices mandate input validation and output encoding, directly preventing log injection.

References