dbcve.org
ViosApplication · Ibm

CVE-2022-22351

HIGH · 8.6 CVSS v3.1 Published 2022-03-07
Fix available
A fix is available. Upgrade to 3.1.1.60 / 3.1.2.40 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 trusted host user to exploit a vulnerability in the nimsh daemon to cause a denial of service in the nimsh daemon on another trusted host. IBM X-Force ID: 220396

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

A detailed technical summary for this CVE is being prepared.

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.1, < 3.1.1.60>= 3.1.2, < 3.1.2.40>= 3.1.3, < 3.1.3.20
AixOperating system
Affected:>= 7.1.5.0, <= 7.1.5.37>= 7.2.4.0, <= 7.2.4.4= 7.2.5.0= 7.2.5.1= 7.2.5.100= 7.3.0= 7.3.0.0

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
None
Availability
High

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

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.

dbcve · scoped
Upgrade available Upgrade to 3.1.1.60 / 3.1.2.40 / 3.1.3.20 or later
Fixed in 3.1.1.603.1.2.403.1.3.20
Vendor patch www.ibm.com →
Recommended fix Moderate confidence

VIOS: 3.1.1.60, 3.1.2.40, or 3.1.3.20; AIX: 7.1.5.38+, 7.2.4.5+, or 7.2.5.2+ (verify exact versions from IBM support page)

  1. 1. Identify the current AIX or VIOS version using 'oslevel -s' (AIX) or 'ioslevel' (VIOS).
  2. 2. Review the IBM support page at https://www.ibm.com/support/pages/node/6561275 to obtain the appropriate interim fix (fix bundle) for your specific AIX or VIOS version.
  3. 3. For AIX: Download and install the APAR (Authorized Program Analysis Report) patch using 'smitty update' or 'emgr -e <fix>.epkg' after downloading from IBM Fix Central.
  4. 4. For VIOS: Download the VIOS update from IBM Fix Central and apply it using 'updateios -install -accept' after backing up current state.
  5. 5. After applying the patch, reboot the system or restart the nimsh daemon using 'stopsrc -s nimsh' and 'startsrc -s nimsh' to ensure the fix takes effect.
  6. 6. Verify the fix is applied by checking the nimsh version or running 'emgr -l' (AIX) to list installed fixes.
Caveat Test the patch in a non-production environment first; some interim fixes may require system reboot and could have dependencies.

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22351 — 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-22351 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