The vulnerability of the Linter Bastion database management system allows a malicious individual to execute arbitrary code with system privileges.

In the “sub41149F” authentication process at the address “0x0041150E”, there is no check for the correctness of input data. This may lead to buffer overflows in the stack during the processing of the RPC call numbered 0x13 “0x0040C95C”. This vulnerability allows a malicious attacker to execute...

The vulnerability of the Linter Bastion database management system allows a malicious individual to execute arbitrary code with system privileges.

In the procedure “sub40FBE6” at address “0x0040FC0A”, there is no check for the correctness of input data. This may lead to buffer overflows in the stack during the processing of the RPC call numbered 0x1A “0x0040DB0F”. This vulnerability allows a malicious attacker to execute arbitrary code with...

The vulnerability of the Linter Bastion database management system allows a malicious individual to control any service on a remote computer.

The RPC call with number 0x0A "0x0040AF25" allows a malicious individual to control any Windows service on a remote computer where linstmgr.exe is running, even though they have no authority to do so. This could enable the malicious individual to interfere with the normal operation of the service...

The vulnerability of the Linter Bastion database management system allows a malicious individual to execute arbitrary code.

The decompression algorithm in the zlib library version 1.1.3, which is part of the Linter Bastion database management system, allows for the use of the inflateEnd function to clean the memory more than once double-free. Exploiting this vulnerability enables attackers to execute arbitrary code by...

The vulnerability of the Linter Bastion database management system allows a malicious individual to trigger a service failure.

When processing an incorrect, improperly formed SQL query of the SELECT type low-level command SLCT, one of the streams of the Inter Bastion Database Management System enters an infinite loop, resulting in exhaustion of the entire stream stack. As a consequence, the Inter Bastion Database...

The vulnerability of the Linter Bastion database management system allows a malicious individual to cause errors in the program’s operation or execute arbitrary code.

The design of the RPC server linstmgr.exe is based on the assumption that client applications will always send valid data and behave as expected. Sending invalid data may cause errors in the program’s operation or may execute arbitrary code...

The vulnerability of the Linter Bastion database management system allows a malicious individual to replace and execute the executable file.

If the database management system Linter Bastion was installed without the “loltp.exe” module being installed, a malicious individual can place any executable file named “loltp.exe” in a directory that will be scanned by the executable file loader. Then, using RPC calls with numbers 0x1A...

The vulnerability of the Linter Bastion database management system allows a malicious individual to trigger a service failure.

In the “sub416B78” procedure, there is no check for the correctness of input data. This may lead to buffer overflows when processing the RPC call with the number 0x10 “0x0040C284”, resulting in corrupted data that is necessary for the proper functioning of the application. This vulnerability allo...

The vulnerability of the Linter Bastion database management system allows a malicious individual to execute arbitrary code with system privileges, as well as bypass the “closed environment” protection mechanism.

The dbcwnt.exe module contains a vulnerable function address 0x4017d4, which reads the value of the NETMBX environment variable into a buffer in the stack, without controlling the size of the copied data. This vulnerability allows a local attacker to execute arbitrary code. Additionally, this...

The vulnerability of the Linter Bastion database management system allows a malicious individual to halt any arbitrary service on a remote computer.

The RPC call with number 0x08 "0x0040AB4E" allows a malicious individual to terminate any service on a remote computer where the linstmgr.exe program is running, even though they have no authority to do so. For example, this could involve terminating the Linter Bastion database management system,...

The vulnerability of the Linter Bastion database management system allows a malicious individual to execute arbitrary services on a remote computer.

RPC call of number 0x08 "0x0040AB4E" allows a malicious individual to execute an arbitrary Windows service on a remote computer where linstmgr.exe is running, without having the necessary permissions. As a result, a service with vulnerabilities can be executed by the malicious individual, and tho...

The vulnerability of the Linter Bastion database management system allows a malicious individual to execute arbitrary code with system privileges.

In the procedure “sub40E0B6” at address “0x0040E10B”, there is no check for the correctness of input data. This may lead to buffer overflows in the stack during the processing of the RPC call numbered 0x16 “0x0040CF5C”. This vulnerability allows a malicious attacker to execute arbitrary code with...

The vulnerability of the Linter Bastion database management system allows a malicious individual to execute arbitrary code.

Exploiting vulnerabilities in the libpng library version 1.0.6 allows a malicious individual to execute arbitrary code using an improperly created PNG file...

The vulnerability of the Linter Bastion database management system allows a malicious individual to execute arbitrary code with system privileges.

This vulnerability allows both remote and local attackers to execute arbitrary code with system privileges, without the need for authentication. This is achieved by sending an incorrect OPEN command to the InterBase database...

The vulnerability of the Linter Bastion database management system allows a malicious individual to decode administrator login credentials.

By default, user passwords in the Linter Bastion Database Management System are encrypted using a less reliable encryption algorithm. The recovery of the password from the encrypted text takes less than a second. For example, in the “3.11” file, with an offset of 4203, the Linter Bastion Database...

The vulnerability of the Linter Bastion database management system allows a malicious individual to replace and execute the executable file.

In the database management system Linter Bastion, for encrypting BLOB data such as drawings, Word documents, PDF documents, etc., XOR encryption is used by default. As the gamma sequence the key for encryption is a static sequence of 255 bytes, this same gamma sequence is used for all databases. ...

The vulnerability of the Linter Bastion database management system allows a malicious individual to disrupt the normal operation of the database management system.

The RPC call with number 0x12 "0x0040C73C" allows a malicious individual to alter the configuration of the kernel startup file of the Linter Bastion database management system, thereby potentially disrupting the normal operation of the database management system...

The vulnerability of the Linter Bastion database management system allows a malicious individual to execute arbitrary code with system privileges or to disrupt the operation of the program.

In the procedure “sub4101B4”, there is no validation of the correctness of the input data at addresses “0x004104D1”, “0x004105AB”, and “0x004105EA”. This may lead to buffer overflows during the processing of RPC calls numbered 0x13 and 0x12 “0x0040C73C”. This vulnerability allows a malicious...

The vulnerability of the Linter Bastion database management system allows a malicious individual to disrupt the normal operation of the database management system.

The RPC call with number 0x19 "0x0040D8F0" allows a malicious individual to alter the configuration of the kernel startup file of the Linter Bastion database management system, thereby potentially disrupting the normal operation of the database management system...