Database crash via incorrectly initialized f_incr type
Published Apr 15, 2022 · Updated Aug 4, 2024
NULL pointer dereference in YottaDB through r1.32 and FIS GT.M through V7.0-000 allows remote attackers to crash the database. The f_incr function in sr_port/f_incr.c incorrectly initializes a type while processing crafted input, leaving a NULL pointer that the process dereferences. No authentication or user interaction is required; exploitation terminates the affected database process without reported data disclosure or modification.
Summary
What happened
NULL pointer dereference in YottaDB through r1.32 and FIS GT.M through V7.0-000 allows remote attackers to crash the database. The f_incr function in sr_port/f_incr.c incorrectly initializes a type while processing crafted input, leaving a NULL pointer that the process dereferences. No authentication or user interaction is required; exploitation terminates the affected database process without reported data disclosure or modification.
The record
- CVE
- CVE-2021-44492
- 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