Security readout for executives and security teams
Plain-English summary
IBM QRadar SIEM 7.2 and 7.3 can disclose sensitive information to unauthorized users. This is not described as system takeover, but exposed security data could help an attacker plan follow-on activity against the SIEM or monitored environment.
Executive priority
Treat as a moderate-priority remediation item. It affects a security monitoring platform, and leaked information may improve an attacker's ability to target the environment, even though no active exploitation is cited here.
Technical view
CVE-2018-2022 is an information disclosure issue in IBM QRadar SIEM 7.2 and 7.3. CVSS 3.0 score is 5.3: network-accessible, low complexity, no privileges, no user interaction, limited confidentiality impact, and no stated integrity or availability impact.
Likely exposure
Exposure is most relevant where IBM QRadar SIEM 7.2 or 7.3 remains deployed, especially if reachable by untrusted networks or broad internal user populations.
Exploitation context
The provided bundle does not show CISA KEV listing or active exploitation. The CVSS temporal vector marks exploit maturity as unproven, so exploitation should not be assumed from these sources alone.
Researcher notes
The source bundle does not provide affected endpoints, data classes, CWE, exploit details, or fixed build numbers. Keep validation focused on version exposure, vendor advisory status, and access-control review rather than speculative testing.
Mitigation direction
- Identify all IBM QRadar SIEM 7.2 and 7.3 deployments.
- Review IBM advisory ibm10888133 for official remediation details.
- Apply IBM-supported fixes or upgrades for affected QRadar versions.
- Restrict QRadar access to trusted administrative networks and users.
- Monitor vendor guidance for any updated fixed-version information.
Validation and detection
- Confirm deployed QRadar SIEM versions against the affected 7.2 and 7.3 range.
- Check patch or fix status against IBM advisory ibm10888133.
- Review access controls for unauthenticated or unauthorized QRadar exposure.
- Look for unexpected access to sensitive QRadar information in logs.
- Document compensating controls if immediate remediation is delayed.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2018-2022 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.0)
- Known Exploited
- No
- Published
Vector: CVSS:3.0/UI:N/AC:L/A:N/I:N/S:U/PR:N/AV:N/C:L/RL:O/E:U/RC:C
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.0/UI:N/AC:L/A:N/I:N/S:U/PR:N/AV:N/C:L/RL:O/E:U/RC:C3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.0 score
5.3MediumVector: CVSS:3.0/UI:N/AC:L/A:N/I:N/S:U/PR:N/AV:N/C:L/RL:O/E:U/RC:C
Source materials
- CVE List V5 sourceCVE List V5
- https://www.ibm.com/support/docview.wss?uid=ibm10888133CVE reference · x_refsource_CONFIRM
- ibm-qradar-cve20182022-info-disc (155346)CVE reference · vdb-entry, x_refsource_XF
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.