Process crash via unchecked ious_open pointer
Published Apr 15, 2022 · Updated Aug 4, 2024
NULL pointer dereference in YottaDB 1.32 and earlier and GT.M 7.0-000 and earlier allows remote attackers to crash the process. Calls to ious_open in sr_unix/ious_open.c dereference a pointer without first checking whether it is NULL, terminating the process when crafted M code reaches the path. Exploitation requires M code to be executed; the demonstrated consequence is a process crash, with no reported data access or code execution.
Summary
What happened
NULL pointer dereference in YottaDB 1.32 and earlier and GT.M 7.0-000 and earlier allows remote attackers to crash the process. Calls to ious_open in sr_unix/ious_open.c dereference a pointer without first checking whether it is NULL, terminating the process when crafted M code reaches the path. Exploitation requires M code to be executed; the demonstrated consequence is a process crash, with no reported data access or code execution.
The record
- CVE
- CVE-2021-44487
- Published
- Apr 15, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 15, 2022CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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