Code execution via crafted-file memory corruption
Published May 14, 2020 · Updated Sep 17, 2024
Memory corruption in IBM i2 Analyst's Notebook 9.2.1 allows local users to execute arbitrary code by inducing a crafted file to be opened. IBM identifies .anb file loading as the affected operation but does not disclose the parser, memory operation, or precise corruption primitive. Exploitation requires a victim to open the file and executes code with the victim's privileges; related impact includes an application crash.
Summary
What happened
Memory corruption in IBM i2 Analyst's Notebook 9.2.1 allows local users to execute arbitrary code by inducing a crafted file to be opened. IBM identifies .anb file loading as the affected operation but does not disclose the parser, memory operation, or precise corruption primitive. Exploitation requires a victim to open the file and executes code with the victim's privileges; related impact includes an application crash.
The record
- CVE
- CVE-2020-4257
- Published
- May 14, 2020
- Updated
- Sep 17, 2024
- Vendor
- IBM
- Product
- i2 Analyst's Notebook
- Classifications
- CWE-787, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 14, 2020CVE publishedPublication date reported by the CVE source.
- Sep 17, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=9.2.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo