An issue was discovered in FIS GT.M through V7.0-000 (related to the YottaDB code base). Using crafted input, can cause the bounds of a for loop to be miscalculated, which leads to a use after free condition a pointer is pushed into previously free memory by the loop.
Weakness
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory “belongs” to the code that operates on the new pointer.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Gt.m | Fisglobal | * | 7.0-000 (including) |
| Fis-gtm | Ubuntu | bionic | * |
| Fis-gtm | Ubuntu | esm-apps/bionic | * |
| Fis-gtm | Ubuntu | esm-apps/focal | * |
| Fis-gtm | Ubuntu | esm-apps/jammy | * |
| Fis-gtm | Ubuntu | esm-apps/xenial | * |
| Fis-gtm | Ubuntu | focal | * |
| Fis-gtm | Ubuntu | impish | * |
| Fis-gtm | Ubuntu | jammy | * |
| Fis-gtm | Ubuntu | kinetic | * |
| Fis-gtm | Ubuntu | lunar | * |
| Fis-gtm | Ubuntu | mantic | * |
| Fis-gtm | Ubuntu | upstream | * |
Potential Mitigations
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/