CVE-2021-44492
📋 TL;DR
This vulnerability in YottaDB and FIS GT.M database systems allows attackers to cause a crash via a NULL pointer dereference by sending crafted input to the f_incr function. It affects all systems running vulnerable versions of these database platforms. The impact is denial of service, potentially disrupting database operations.
💻 Affected Systems
- YottaDB
- FIS GT.M
📦 What is this software?
Gt.m by Fisglobal
Yottadb by Yottadb
⚠️ Risk & Real-World Impact
Worst Case
Complete database service disruption leading to application downtime and data unavailability
Likely Case
Database process crash requiring restart, causing temporary service interruption
If Mitigated
Minimal impact with proper network segmentation and input validation
🎯 Exploit Status
Exploitation requires sending crafted input to the vulnerable f_incr function, which may be accessible through various interfaces
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: YottaDB r1.34+, FIS GT.M V7.0-002+
Vendor Advisory: http://tinco.pair.com/bhaskar/gtm/doc/articles/GTM_V7.0-002_Release_Notes.html
Restart Required: Yes
Instructions:
1. Download patched version from official sources. 2. Backup databases. 3. Install updated version. 4. Restart database processes.
🔧 Temporary Workarounds
Input validation wrapper
allImplement input validation for f_incr function calls to filter malicious input
# Custom M code wrapper for f_incr calls
# Validate input parameters before calling f_incr
Network access restrictions
linuxRestrict network access to database ports from untrusted sources
iptables -A INPUT -p tcp --dport <db_port> -s trusted_network -j ACCEPT
iptables -A INPUT -p tcp --dport <db_port> -j DROP
🧯 If You Can't Patch
- Implement strict network segmentation to isolate database servers from untrusted networks
- Monitor for abnormal database crashes and implement automated restart procedures
🔍 How to Verify
Check if Vulnerable:
Check version with: yottadb -version or mumps -version
Check Version:
yottadb -version | grep Version || mumps -version | head -1
Verify Fix Applied:
Confirm version is YottaDB r1.34+ or GT.M V7.0-002+
📡 Detection & Monitoring
Log Indicators:
- Database process crashes
- NULL pointer dereference errors in database logs
- Abnormal termination of database processes
Network Indicators:
- Unusual patterns of requests to database functions
- Multiple connection attempts followed by service disruption
SIEM Query:
source="database.log" AND ("segmentation fault" OR "NULL pointer" OR "f_incr" OR "abnormal termination")
🔗 References
- http://tinco.pair.com/bhaskar/gtm/doc/articles/GTM_V7.0-002_Release_Notes.html
- https://gitlab.com/YottaDB/DB/YDB/-/issues/828
- https://sourceforge.net/projects/fis-gtm/files/
- http://tinco.pair.com/bhaskar/gtm/doc/articles/GTM_V7.0-002_Release_Notes.html
- https://gitlab.com/YottaDB/DB/YDB/-/issues/828
- https://sourceforge.net/projects/fis-gtm/files/