Code execution via op_write function-pointer corruption
Published Apr 15, 2022 · Updated Aug 4, 2024
Function-pointer corruption in YottaDB r1.32 and earlier and FIS GT.M V7.0-000 and earlier allows remote attackers to execute code. The op_write implementation in sr_port/op_write.c permits crafted input to alter a function pointer that determines the next execution target. Network-reachable, unauthenticated access is sufficient, and successful exploitation redirects control flow with the affected process's privileges.
Summary
What happened
Function-pointer corruption in YottaDB r1.32 and earlier and FIS GT.M V7.0-000 and earlier allows remote attackers to execute code. The op_write implementation in sr_port/op_write.c permits crafted input to alter a function pointer that determines the next execution target. Network-reachable, unauthenticated access is sufficient, and successful exploitation redirects control flow with the affected process's privileges.
The record
- CVE
- CVE-2021-44486
- Published
- Apr 15, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1190
- 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