I2 Analysts NotebookApplication · Ibm

CVE-2020-4422

HIGH · 7.8 CVSS v3.1 Published 2020-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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 i2 Intelligent Analyis Platform 9.2.1 could allow a remote attacker to execute arbitrary code on the system, caused by a memory corruption. By persuading a victim to open a specially crafted file, a remote attacker could exploit this vulnerability to execute arbitrary code on the system or cause the application to crash. IBM X-Force ID: 180167.

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 · high confidence

IBM i2 Intelligent Analysis Platform 9.2.1 contains a memory corruption vulnerability that can be exploited by convincing a user to open a specially crafted malicious file, allowing a remote attacker to execute arbitrary code on the system or cause a denial of service condition.

MitigationApply the vendor-supplied patch or update to IBM i2 Intelligent Analysis Platform. Until patched, advise users to avoid opening files from untrusted sources.

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
I2 Analysts NotebookApplication
Affected:= 9.2.1

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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. Verify IBM i2 Analysts Notebook is installed
    Check the installed programs list in Windows Control Panel > Programs and Features, or use the command 'Get-WmiObject -Class Win32_Product | Select-Object Name, Version' in PowerShell to list installed software
    Affected if IBM i2 Analysts Notebook appears in the installed programs list
  2. Confirm the installed version is 9.2.1
    Locate the version number in the program's About or Help menu, or check the file version of the executable (typically in the installation directory such as C:\Program Files\IBM\i2\Analyst's Notebook or similar) by right-clicking the .exe file and selecting Properties > Details
    Affected if The version is listed as exactly 9.2.1
  3. Verify the application is configured to handle analysis files
    Check if the application file associations are registered (look for .anb or other i2 file extensions associated with the program) and confirm the application can open local files
    Affected if File associations for i2 analysis files exist and the application can open files from local storage
  4. Check for recent file opening activity
    Review Windows Event Logs under Security and Application logs for evidence of .anb or i2 analysis files being opened, or check recent documents in the application's File menu
    Affected if Users have opened analysis files with this application (the vulnerability is triggered only when a user opens a malicious file)

You are affected only if IBM i2 Analysts Notebook version 9.2.1 is installed AND users can open analysis files with it, since exploitation requires a user to open a specially crafted malicious file.

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 the vendor-supplied patch or update to IBM i2 Intelligent Analysis Platform. Until patched, advise users to avoid opening files from untrusted sources.

Fix this in I2 Analysts Notebook Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2020-4422 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