LiveActive security incident?Get immediate response
CVE Record

CVE-2021-20408: IBM Security Verify Information Queue 1.0.6 and 1.0.7 could disclose highly sensitive information to a loca...

IBM Security Verify Information Queue 1.0.6 and 1.0.7 could disclose highly sensitive information to a local user due to inproper storage of a plaintext cryptographic key. IBM X-Force ID: 198187.

HighCVSS 7.1Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

IBM Security Verify Information Queue 1.0.6 and 1.0.7 may store a cryptographic key in plaintext. A local user could access sensitive information if they already have low-privileged access to the system. This is serious for environments where the product protects identity or security workflow data.

Executive priority

Prioritize this where the product is deployed on shared systems or handles sensitive security data. The local-access requirement limits broad exposure, but plaintext key storage can undermine confidentiality and integrity once an attacker has a foothold.

Technical view

The CVE describes improper storage of a plaintext cryptographic key, enabling local, low-privileged access to highly sensitive information. CVSS 3.0 score is 7.1, with local attack vector, low complexity, no user interaction, high confidentiality and integrity impact, and no availability impact.

Likely exposure

Exposure is limited to IBM Security Verify Information Queue versions 1.0.6 and 1.0.7. The attacker must be a local user with privileges, so externally exposed internet services are not the main risk signal from the provided evidence.

Exploitation context

The provided bundle does not show active exploitation. CISA KEV is false, and the CVSS temporal exploit-code maturity is listed as unproven. Treat this as a local post-access risk rather than a confirmed exploited vulnerability.

Researcher notes

The source bundle contains an X-Force ID inconsistency: the description states 198187, while the referenced X-Force URL and name use 196187. No CWE, patch version, or detailed remediation text is included in the provided bundle.

Mitigation direction

  • Inventory IBM Security Verify Information Queue deployments and identify versions 1.0.6 or 1.0.7.
  • Review IBM’s advisory for the official remediation or upgrade path.
  • Restrict unnecessary local user access on affected hosts.
  • Rotate exposed cryptographic material if IBM guidance indicates key compromise risk.
  • Prioritize remediation on systems processing sensitive identity or security data.

Validation and detection

  • Confirm installed product versions against the affected 1.0.6 and 1.0.7 range.
  • Review host access controls for unnecessary local users or service accounts.
  • Check whether remediation from IBM’s advisory has been applied.
  • Verify cryptographic keys are no longer stored in plaintext after remediation.
  • Track the issue using CVE-2021-20408 and the IBM X-Force reference.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CVE-2021-20408 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.1 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/S:U/AV:L/UI:N/I:H/C:H/PR:L/A:N/AC:L/RC:C/E:U/RL:O

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
7.1CVSS 3.0HighCVSS:3.0/S:U/AV:L/UI:N/I:H/C:H/PR:L/A:N/AC:L/RC:C/E:U/RL:O1.85.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

7.1High
CVSS 3.0 vector shape for CVE-2021-20408Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/S:U/AV:L/UI:N/I:H/C:H/PR:L/A:N/AC:L/RC:C/E:U/RL:O

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
IBMSecurity Verify Information Queue1.0.6, 1.0.7Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.