LiveActive security incident?Get immediate response
CVE Record

CVE-2022-22370: IBM Security Verify Access 10.0.0.0, 10.0.1.0, 10.0.2.0, and 10.0.3.0 is vulnerable to cross-site scripting.

IBM Security Verify Access 10.0.0.0, 10.0.1.0, 10.0.2.0, and 10.0.3.0 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 221194.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-22370 is a medium-severity cross-site scripting issue in IBM Security Verify Access. An authenticated user could place JavaScript into the Web UI, potentially changing trusted-session behavior and exposing credentials.

Executive priority

Treat this as a moderate-priority identity-platform issue. It is not described as actively exploited, but credential disclosure inside a trusted security product session warrants timely remediation and access tightening.

Technical view

IBM Security Verify Access 10.0.0.0 through 10.0.3.0 are affected. The CVSS 3.0 score is 5.4 with network access, low privileges, low complexity, required user interaction, changed scope, and limited confidentiality and integrity impact.

Likely exposure

Exposure is likely limited to organizations running the named IBM Security Verify Access versions, especially where the administrative or Web UI is reachable by authenticated users beyond tightly controlled administrators.

Exploitation context

The bundle does not identify CISA KEV listing or active exploitation. The CVSS vector marks exploit maturity high, but exploitation still requires low privileges and user interaction within the Web UI context.

Researcher notes

No CWE is provided in the bundle. The key constraints are authenticated access and user interaction. Patch details are not included in the supplied data, so remediation should track IBM's advisory rather than inferred fixed versions.

Mitigation direction

  • Check IBM advisory 6601725 for the vendor-approved fix or workaround.
  • Prioritize upgrades or remediation for affected versions 10.0.0.0 through 10.0.3.0.
  • Restrict Web UI access to trusted administrative networks and users.
  • Review IBM X-Force entry 221194 for updated vendor risk details.
  • Monitor trusted-session credential exposure indicators until remediation is complete.

Validation and detection

  • Inventory IBM Security Verify Access versions across production and non-production environments.
  • Confirm whether any instance runs 10.0.0.0, 10.0.1.0, 10.0.2.0, or 10.0.3.0.
  • Verify current fix level against IBM advisory 6601725.
  • Review Web UI access paths and authenticated user populations.
  • Use authorized, non-destructive XSS validation to confirm unsafe script content is neutralized.
Prepared
Confidence
medium
Sources
4

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-2022-22370 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.4 (3.0)
Known Exploited
No
Published

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

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.4CVSS 3.0MediumCVSS:3.0/A:N/PR:L/AC:L/C:L/S:C/UI:R/I:L/AV:N/RL:O/RC:C/E:H2.32.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

5.4Medium
CVSS 3.0 vector shape for CVE-2022-22370Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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 Access10.0.2.0, 10.0.0.0, 10.0.1.0, 10.0.3.0Listed
Weakness

CWE details

No CWE listed

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