14:I[5228,["3385","static/chunks/3385-b76bb0d389ecb847.js","5753","static/chunks/5753-3df3dcd374d56bde.js","4462","static/chunks/4462-2f1547025558c923.js","1766","static/chunks/1766-e0a00c1dbb04d867.js","2122","static/chunks/2122-0aa89565809d0f14.js","8198","static/chunks/8198-02259efa89977c06.js","8058","static/chunks/8058-250b9e00e45a105b.js","2476","static/chunks/2476-39b31f73cd0731dd.js","4317","static/chunks/4317-05b07ec5dd2dfc17.js","8279","static/chunks/8279-51bfd849e487548c.js","9420","static/chunks/9420-af651d52266219df.js","1050","static/chunks/1050-c17118e9648df02f.js","9259","static/chunks/9259-b80e9833ae7b100c.js","7670","static/chunks/7670-77670847a8e0a1cb.js","1768","static/chunks/app/knowledgebases/%5BattackType%5D/%5Bid%5D/page-884b6d4b6fea536c.js"],"default"] 15:T489,The product attempts to return a memory resource to the system, but it calls a release function that is not compatible with the function that was originally used to allocate that resource. -------------

This weakness can be generally described as mismatching memory management routines, such as:

The memory was allocated on the stack (automatically), but it was deallocated using the memory management routine free() (CWE-590), which is intended for explicitly allocated heap memory.
The memory was allocated explicitly using one set of memory management functions, and deallocated using a different set. For example, memory might be allocated with malloc() in C++ instead of the new operator, and then deallocated with the delete operator.

When the memory management functions are mismatched, the consequences may be as severe as code execution, memory corruption, or program crash. Consequences and ease of exploit will vary depending on the implementation of the routines and the object being managed.

Mismatched Memory Management Routines