LiveActive security incident?Get immediate response
CVE Record

CVE-2021-20409: IBM Security Verify Information Queue information disclosure

IBM Security Verify Information Queue 1.0.6 and 1.0.7 could allow a remote attacker to obtain sensitive information, caused by the failure to properly enable HTTP Strict Transport Security. An attacker could exploit this vulnerability to obtain sensitive information using man in the middle techniques. IBM X-Force ID: 196188.

MediumCVSS 5.9Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

IBM Security Verify Information Queue 1.0.6 and 1.0.7 did not properly enable HSTS. That weakens browser protections against connection downgrades or interception, so a remote attacker in a man-in-the-middle position could obtain sensitive information. CVSS 5.9 indicates moderate urgency, mainly for exposed or user-accessible deployments.

Executive priority

Treat this as a moderate confidentiality risk. It is not supported as actively exploited in the provided sources, but affected deployments handling sensitive data should be remediated through IBM guidance during the next security maintenance window.

Technical view

The issue is an information disclosure weakness caused by missing or improperly enabled HTTP Strict Transport Security. The CVSS vector is AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N, meaning remotely reachable, no privileges or user interaction, high attack complexity, and confidentiality-only impact.

Likely exposure

Exposure appears limited to IBM Security Verify Information Queue 1.0.6 and 1.0.7. The CVE record lists other versions as unaffected by default. Organizations without this IBM component, or not running those versions, are unlikely to be directly exposed.

Exploitation context

The provided sources do not show active exploitation, and the CVE is not listed as KEV. Successful abuse requires a man-in-the-middle position, which raises practical attack difficulty but can still matter on untrusted networks or where sensitive sessions traverse exposed paths.

Researcher notes

Evidence identifies an HSTS enablement failure, not a broader authentication or code execution flaw. The source bundle does not provide CWE mapping, patch versions, or detailed remediation text, so validation should stay focused on affected-version inventory and vendor-published guidance.

Mitigation direction

  • Identify IBM Security Verify Information Queue deployments and versions.
  • Prioritize upgrades or configuration changes according to IBM’s advisory.
  • Verify HTTPS responses use HSTS where IBM guidance requires it.
  • Reduce exposure from untrusted networks until vendor guidance is applied.

Validation and detection

  • Confirm whether versions 1.0.6 or 1.0.7 are present.
  • Review IBM advisory and X-Force entry for current remediation guidance.
  • Check external and internal service endpoints for expected HSTS behavior.
  • Document compensating controls if remediation cannot be applied immediately.
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-20409 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
Medium
CVSS
5.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

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
5.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N2.23.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.9Medium
CVSS 3.1 vector shape for CVE-2021-20409Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

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.7unaffected
Weakness

CWE details

No CWE listed

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