CVE-2026-40504: Heap-based Buffer Overflow

Creolabs Gravity before 0.9.6 contains a heap buffer overflow vulnerability in the gravityvmexec function that allows attackers to write out-of-bounds memory by crafting scripts with many string literals at global scope. Attackers can exploit insufficient bounds checking in gravityfiberreassign t...

EUVD-2017-1454

Malware in sbrugna...

EUVD-2017-1392

Malware in sbrugna...

EUVD-2017-1389

Malware in sbrugna...

EUVD-2017-1390

Malware in sbrugna...

EUVD-2017-1568

Malware in sbrugna...

EUVD-2017-1391

Malware in sbrugna...

CVE-2017-1000172

Creolabs Gravity Version: 1.0 Use-After-Free Possible code execution. An example of a Heap-Use-After-Free after the 'sublexer' pointer has been freed. Line 542 of gravitylexer.c. 'lexer' is being used to access a variable but 'lexer' has already been freed, creating a Heap Use-After-Free conditio...

CVE-2017-1000173

Creolabs Gravity Version: 1.0 Heap Overflow Potential Code Execution. By creating a large loop whiling pushing data to a buffer, we can break out of the bounds checking of that buffer. When list.join is called on the data it will read past a buffer resulting in a Heap-Buffer-Overflow...

Creolabs Gravity 'operator_string_add' function stack buffer overflow vulnerability

Creolabs Gravity is an open source lightweight embedded programming language from Creolabs, Italy. The language supports procedural programming, object-oriented programming, functional programming and data-driven programming. A stack buffer overflow vulnerability exists in the 'operatorstringadd'...

CVE-2017-1000437

Creolabs Gravity 1.0 contains a stack based buffer overflow in the operatorstringadd function, resulting in remote code execution...

Stack overflow

Creolabs Gravity 1.0 contains a stack based buffer overflow in the operatorstringadd function, resulting in remote code execution...

CVE-2017-1000437

Creolabs Gravity 1.0 contains a stack based buffer overflow in the operatorstringadd function, resulting in remote code execution...

CVE-2017-1000437: Improper Restriction of Operations within the Bounds of a Memory Buffer

Creolabs Gravity 1.0 contains a stack based buffer overflow in the operatorstringadd function, resulting in remote code execution...

Creolabs Gravity Memory Misreference Vulnerability

Creolabs Gravity is an open source lightweight embedded programming language from Creolabs, Italy. The language supports procedural programming, object-oriented programming, functional programming and data-driven programming. A memory misreference vulnerability exists in Creolabs Gravity version...

Creolabs Gravity Heap Buffer Overflow Vulnerability

Creolabs Gravity is an open source lightweight embedded programming language from Creolabs, Italy. The language supports procedural programming, object-oriented programming, functional programming and data-driven programming. A heap buffer overflow vulnerability exists in Creolabs Gravity version...

Heap overflow

Creolabs Gravity Version: 1.0 Heap Overflow Potential Code Execution. By creating a large loop whiling pushing data to a buffer, we can break out of the bounds checking of that buffer. When list.join is called on the data it will read past a buffer resulting in a Heap-Buffer-Overflow...

CVE-2017-1000173

Creolabs Gravity Version: 1.0 Heap Overflow Potential Code Execution. By creating a large loop whiling pushing data to a buffer, we can break out of the bounds checking of that buffer. When list.join is called on the data it will read past a buffer resulting in a Heap-Buffer-Overflow...

CVE-2017-1000172

Creolabs Gravity Version: 1.0 Use-After-Free Possible code execution. An example of a Heap-Use-After-Free after the 'sublexer' pointer has been freed. Line 542 of gravitylexer.c. 'lexer' is being used to access a variable but 'lexer' has already been freed, creating a Heap Use-After-Free conditio...

Design/Logic Flaw

Creolabs Gravity Version: 1.0 Use-After-Free Possible code execution. An example of a Heap-Use-After-Free after the 'sublexer' pointer has been freed. Line 542 of gravitylexer.c. 'lexer' is being used to access a variable but 'lexer' has already been freed, creating a Heap Use-After-Free conditio...