Security readout for executives and security teams
Plain-English summary
CVE-2021-38874 is an IBM QRadar SIEM information exposure issue. In some situations, authenticated users could access information across tenant and domain boundaries. The business concern is confidentiality: separated customers, teams, or business units may not be isolated as expected.
Executive priority
Treat this as a confidentiality governance issue, not an emergency remote takeover. Prioritize remediation if QRadar supports multiple tenants, customers, regulated environments, or segregated business units.
Technical view
IBM reports QRadar SIEM 7.3.3, 7.4.3, and 7.5.0 are affected. The CVSS 3.0 score is 4.3, with network access, low privileges, low complexity, no user interaction, and low confidentiality impact. Integrity and availability are not listed as impacted.
Likely exposure
Exposure is most relevant where QRadar SIEM uses tenant or domain separation. Systems running IBM QRadar SIEM 7.3.3, 7.4.3, or 7.5.0 should be reviewed against IBM guidance.
Exploitation context
The provided sources do not show CISA KEV listing or confirmed active exploitation. The CVSS exploit maturity is marked unproven. Exploitation would require a valid low-privileged QRadar user with network access.
Researcher notes
The source bundle does not provide detailed root cause, affected components, or precise exploitation conditions. Analysis should stay scoped to IBM's description: information access across tenant and domain boundaries in some situations.
Mitigation direction
- Review IBM advisory 6574787 for affected and fixed QRadar levels.
- Apply IBM-provided updates or workarounds where available.
- Prioritize multi-tenant or domain-separated QRadar deployments.
- Limit QRadar accounts to required roles and domains.
- Monitor for unexpected cross-domain or cross-tenant data access.
Validation and detection
- Inventory QRadar SIEM versions and compare against 7.3.3, 7.4.3, and 7.5.0.
- Identify deployments using QRadar tenant or domain boundaries.
- Confirm remediation status against the IBM advisory.
- Review user roles and domain assignments for least privilege.
- Check logs for anomalous access across tenant or domain boundaries.
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-2021-38874 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
- 4.3 (3.0)
- Known Exploited
- No
- Published
Vector: CVSS:3.0/I:N/S:U/PR:L/A:N/UI:N/AC:L/AV:N/C:L/RC:C/RL:O/E:U
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/I:N/S:U/PR:L/A:N/UI:N/AC:L/AV:N/C:L/RC:C/RL:O/E:U2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.0 score
4.3MediumVector: CVSS:3.0/I:N/S:U/PR:L/A:N/UI:N/AC:L/AV:N/C:L/RC:C/RL:O/E:U
Source materials
- CVE List V5 sourceCVE List V5
- https://www.ibm.com/support/pages/node/6574787CVE reference · x_refsource_CONFIRM
- ibm-qradar-cve202138874-info-disc (208397)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.