Security readout for executives and security teams
Plain-English summary
IBM QRadar SIEM could expose authorized service tokens to other QRadar users in some scenarios. That matters because tokens may grant access to QRadar services or integrations. The public bundle rates this medium, with high confidentiality impact but high attack complexity and no stated integrity or availability impact.
Executive priority
Prioritize during normal vulnerability remediation, faster for QRadar systems with broad user access or sensitive integrations. The SIEM is security-critical infrastructure, so token exposure can undermine monitoring trust even without confirmed exploitation.
Technical view
CVE-2021-38919 affects IBM QRadar SIEM 7.3.3, 7.4.3, and 7.5.0. The issue is information disclosure of authorized service tokens. CVSS v3.0 is 5.9 with network attack vector, high complexity, no user interaction, and high confidentiality impact.
Likely exposure
Exposure is most likely in organizations running the listed QRadar SIEM versions, especially environments with multiple QRadar users and service tokens. The source bundle does not define the exact scenarios, token scope, or affected configurations.
Exploitation context
The bundle does not cite active exploitation, and KEV status is false. CVSS marks exploit maturity as unproven. Treat this as a credible confidentiality risk, not as confirmed in-the-wild exploitation.
Researcher notes
Public evidence identifies affected versions and impact but not the precise disclosure path. Do not assume exploitability beyond the published CVSS and IBM wording. Validate exposure against IBM guidance and local QRadar configuration.
Mitigation direction
- Review IBM advisory for version-specific remediation guidance.
- Inventory QRadar SIEM 7.3.3, 7.4.3, and 7.5.0 deployments.
- Apply only IBM-confirmed fixes, updates, or workarounds.
- Rotate service tokens if exposure is suspected.
- Limit QRadar user access to operationally necessary accounts.
Validation and detection
- Confirm QRadar SIEM version and build across all deployments.
- Identify whether authorized service tokens are configured or used.
- Review QRadar user roles and recent access to token-related views.
- Check IBM X-Force and support advisory for updated guidance.
- Look for unusual use of QRadar service tokens.
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-38919 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.9 (3.0)
- Known Exploited
- No
- Published
Vector: CVSS:3.0/I:N/PR:N/S:U/UI:N/A:N/C:H/AC:H/AV:N/E:U/RL:O/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/I:N/PR:N/S:U/UI:N/A:N/C:H/AC:H/AV:N/E:U/RL:O/RC:C2.23.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.0 score
5.9MediumVector: CVSS:3.0/I:N/PR:N/S:U/UI:N/A:N/C:H/AC:H/AV:N/E:U/RL:O/RC:C
Source materials
- CVE List V5 sourceCVE List V5
- https://www.ibm.com/support/pages/node/6574787CVE reference · x_refsource_CONFIRM
- ibm-qradar-cve202138919-info-disc (210021)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.
