Local crash via underflowed memset size
Published Apr 15, 2022 · Updated Aug 4, 2024
Integer underflow in op_fnj3 in FIS GT.M 7.0-000 and earlier allows local users to crash the application with crafted M code. The function derives a byte count from attacker-controlled input and passes the underflowed size to memset, causing a segmentation fault. Reachability requires login access and the ability to modify executed M code; the documented consequence is a process crash, not data access or modification.
Summary
What happened
Integer underflow in op_fnj3 in FIS GT.M 7.0-000 and earlier allows local users to crash the application with crafted M code. The function derives a byte count from attacker-controlled input and passes the underflowed size to memset, causing a segmentation fault. Reachability requires login access and the ability to modify executed M code; the documented consequence is a process crash, not data access or modification.
The record
- CVE
- CVE-2021-44509
- Published
- Apr 15, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-191, T1499.004
- Attack vector
- local
- Privileges
- authenticated
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