dbcve.org
ViosApplication · Ibm

CVE-2022-22350

MEDIUM · 5.5 CVSS v3.1 Published 2022-03-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
IBM AIX 7.1, 7.2, 7.3, and VIOS 3.1 could allow a non-privileged local user to exploit a vulnerability in CAA to cause a denial of service. IBM X-Force ID: 220394.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A local privilege vulnerability in IBM's Cluster Aware AIX (CAA) component allows a non-privileged local user to cause a denial of service on affected AIX 7.1, 7.2, 7.3 and VIOS 3.1 systems.

MitigationApply IBM's security patches for this vulnerability as referenced in the IBM security bulletin (X-Force ID 220394); restrict unauthorized local user access to systems running the CAA clustering component.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ViosApplication
Affected:= 3.1
AixOperating system
Affected:= 7.1= 7.2= 7.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check AIX or VIOS version
    Run 'oslevel -s' on the system to get the full version level (e.g., 7200-05-01-2231)
    Affected if The version starts with 7100, 7200, or 7300 (for AIX) or shows a VIOS version of 3.1.x
  2. Verify CAA filesets are installed
    Run 'lslpp -l cluster.aware.aix.rte' or 'lslpp -l | grep -i caa' to list installed Cluster Aware AIX filesets
    Affected if The cluster.aware.aix.rte or related CAA filesets are installed
  3. Check if CAA clustering is active
    Run 'lscluster -c' to display CAA cluster status, or use 'clstat -a' if cluster services are running
    Affected if CAA cluster is configured or active (the vulnerability can be exploited when CAA is running)
  4. Identify running CAA processes
    Run 'ps -ef | grep -i cl' or 'ps -ef | grep cluster' to look for cluster daemon processes such as 'clconfd' or 'clmuxd'
    Affected if CAA cluster daemon processes (clconfd, clmuxd, etc.) are running on the system

The system is affected if it runs AIX 7.1/7.2/7.3 or VIOS 3.1 AND has the Cluster Aware AIX component installed and active, allowing a local non-privileged user to trigger denial of service.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply IBM's security patches for this vulnerability as referenced in the IBM security bulletin (X-Force ID 220394); restrict unauthorized local user access to systems running the CAA clustering component.

Fix this in Vios Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22350 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-22350 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data