Arbitrary code execution via .anb memory corruption
Published May 14, 2020 · Updated Sep 17, 2024
Memory corruption in IBM i2 Analyst’s Notebook 9.2.1 allows remote attackers to execute arbitrary code via a specially crafted .anb file opened by a victim. The .anb loading component mishandles malformed file data, corrupting memory and enabling code execution or an application crash. Exploitation requires convincing a user to open the file, and code runs with that user’s privileges.
Summary
What happened
Memory corruption in IBM i2 Analyst’s Notebook 9.2.1 allows remote attackers to execute arbitrary code via a specially crafted .anb file opened by a victim. The .anb loading component mishandles malformed file data, corrupting memory and enabling code execution or an application crash. Exploitation requires convincing a user to open the file, and code runs with that user’s privileges.
The record
- CVE
- CVE-2020-4343
- Published
- May 14, 2020
- Updated
- Sep 17, 2024
- Vendor
- IBM
- Product
- i2 Analyst's Notebook
- Classifications
- 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?
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