AUVESY

The server permits communication without any authentication procedure, allowing the attacker to initiate a session with the server without providing any form of authentication.

Some API functions permit by-design writing or copying data into a given buffer.

The scheduler service running on a specific TCP port enables the user to start and stop jobs.

There are multiple API function codes that permit reading and writing data to or from files and directories, which could lead to the manipulation and/or the deletion of files.

The data of a network capture of the initial handshake phase can be used to authenticate at a SYSDBA level.

There are multiple API function codes that permit data writing to any file, which may allow an attacker to modify existing files or create new files.

Some API functions allow interaction with the registry, which includes reading values as well as data modification.

The database connection to the server is performed by calling a specific API, which could allow an unprivileged user to gain SYSDBA permissions.

The affected product’s code base doesn’t properly control arguments for specific functions, which could lead to a stack overflow.

Many of the services used by the affected product do not specify full paths for the DLLs they are loading.

A specific function code receives a raw pointer supplied by the user and deallocates this pointer.

The affected product does not properly control the allocation of resources.

The webinstaller is a Golang web server executable that enables the generation of an Auvesy image agent.

The affected product uses a hard-coded blowfish key for encryption/decryption processes.

Many API function codes receive raw pointers remotely from the user and trust these pointers as valid in-bound memory regions.

The affected product’s OS Service does not verify any given parameter.

The affected product’s proprietary protocol CSC allows for calling numerous function codes.