LiveActive security incident?Get immediate response
CVE Record

CVE-2021-20403: IBM Security Verify Information Queue 1.0.6 and 1.0.7 is vulnerable to cross-site request forgery which cou...

IBM Security Verify Information Queue 1.0.6 and 1.0.7 is vulnerable to cross-site request forgery which could allow an attacker to execute malicious and unauthorized actions transmitted from a user that the website trusts.

LowCVSS 3.1Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This is a low-severity cross-site request forgery issue in IBM Security Verify Information Queue 1.0.6 and 1.0.7. A successful attacker would need to trick a trusted user into causing an unauthorized action in the application. The supplied sources do not indicate data theft, service disruption, or confirmed exploitation.

Executive priority

Handle through routine vulnerability management unless the affected application controls sensitive business or identity workflows. The business risk is unauthorized action by a trusted user, but the available evidence supports low urgency and no known active exploitation.

Technical view

CVE-2021-20403 affects IBM Security Verify Information Queue versions 1.0.6 and 1.0.7. The CVSS 3.0 score is 3.1, with network access, no privileges required, high attack complexity, required user interaction, no confidentiality impact, low integrity impact, and no availability impact.

Likely exposure

Exposure is limited to environments running IBM Security Verify Information Queue 1.0.6 or 1.0.7. Practical risk depends on whether trusted users access the affected application and whether unauthorized state-changing actions are reachable through browser requests.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation. Exploitation requires user interaction and appears focused on unauthorized actions sent from a browser the website trusts, not direct unauthenticated compromise.

Researcher notes

The supplied data lacks CWE mapping, detailed endpoint scope, proof-of-concept detail, and named fixed version. Treat IBM’s advisory and X-Force entry as authoritative for remediation specifics and avoid assuming impact beyond low integrity modification.

Mitigation direction

  • Inventory IBM Security Verify Information Queue deployments and versions.
  • Prioritize remediation for versions 1.0.6 and 1.0.7.
  • Review IBM advisory 6414365 for the official fix or mitigation.
  • Apply vendor-provided remediation through normal change control.
  • Limit access to sensitive application functions until remediated.

Validation and detection

  • Confirm whether any deployment runs version 1.0.6 or 1.0.7.
  • Check IBM advisory details against installed build and maintenance level.
  • Verify remediation status in asset and change records.
  • Review application logs for unusual trusted-user state changes.
  • Confirm exposed workflows require appropriate anti-CSRF protections after remediation.
Prepared
Confidence
high
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-20403 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
Low
CVSS
3.1 (3.0)
Known Exploited
No
Published

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

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
3.1CVSS 3.0LowCVSS:3.0/AC:H/I:L/AV:N/A:N/UI:R/C:N/S:U/PR:N/RL:O/E:U/RC:C1.61.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

3.1Low
CVSS 3.0 vector shape for CVE-2021-20403Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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.