CVE-2021-44494
📋 TL;DR
This vulnerability allows attackers to cause denial of service by crashing YottaDB or GT.M database systems through crafted input to ZRead commands. It affects all users running vulnerable versions of YottaDB (through r1.32) and FIS GT.M (through V7.0-000). The crash occurs due to a NULL pointer dereference when processing malicious input.
💻 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 until service restart.
Likely Case
Service crashes requiring manual intervention to restart database processes, causing temporary service disruption.
If Mitigated
Minimal impact if proper input validation and network segmentation are implemented.
🎯 Exploit Status
Exploitation requires ability to send crafted input to ZRead commands, typically requiring some level of access to the database interface.
🛠️ 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 latest version from official sources. 2. Backup current installation. 3. Install updated version following vendor documentation. 4. Restart all database processes.
🔧 Temporary Workarounds
Input Validation
allImplement strict input validation for all ZRead command inputs to reject malformed data.
# Application-level validation required - no system commands
Access Restriction
allRestrict access to ZRead functionality to trusted users and systems only.
# Configure application-level access controls
🧯 If You Can't Patch
- Implement network segmentation to isolate database systems from untrusted networks
- Deploy application-level input validation and sanitization for all ZRead inputs
🔍 How to Verify
Check if Vulnerable:
Check installed version against affected ranges: YottaDB <= r1.32 or GT.M <= V7.0-000
Check Version:
$ydb_dist/mumps -run %XCMD 'write $zversion' or $gtm_dist/mumps -run %XCMD 'write $zversion'
Verify Fix Applied:
Confirm version is YottaDB r1.34+ or GT.M V7.0-002+ and test ZRead functionality with normal operations
📡 Detection & Monitoring
Log Indicators:
- Database process crashes
- Core dumps in database logs
- ZRead command failures
Network Indicators:
- Unusual patterns of ZRead requests
- Multiple rapid connection attempts to database
SIEM Query:
source="database_logs" AND (event="crash" OR event="segfault") AND process="mumps"
🔗 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/