Skip to content
OpenAdvisories

Vendor

AUVESY

17 known vulnerabilities.

AUVESY at a glance

Last 12 months
0
Critical · all time
6
Exploited · all time
0
Public exploit · all time
0
New vulnerabilities per month · last 12 months
0 1 1 December 2025: 0 vulnerabilities Dec 2025 January 2026: 0 vulnerabilities February 2026: 0 vulnerabilities March 2026: 0 vulnerabilities Mar April 2026: 0 vulnerabilities May 2026: 0 vulnerabilities June 2026: 0 vulnerabilities Jun July 2026: 0 vulnerabilities August 2026: 0 vulnerabilities September 2026: 0 vulnerabilities Sep October 2026: 0 vulnerabilities November 2026: 0 vulnerabilities
Show as table
MonthVulnerabilitiesCritical
Nov 202600
Oct 202600
Sep 202600
Aug 202600
Jul 202600
Jun 202600
May 202600
Apr 202600
Mar 202600
Feb 202600
Jan 202600
Dec 202500
Nov 202500
Oct 202500
Sep 202500
Aug 202500
Jul 202500
Jun 202500
May 202500
Apr 202500
Mar 202500
Feb 202500
Jan 202500
Dec 202400

Products

Latest advisories

  • Critical max 9.8
    ICSA-21-292-01 17 CVEs

    AUVESY Versiondog

    Successful exploitation of these vulnerabilities could allow an attacker to achieve remote code execution, and acquire complete remote control over the machine.

17 results · Feed

  • Critical 9.8

    AUVESY Versiondog

    Some API functions permit by-design writing or copying data into a given buffer. Since the client controls these parameters, an attacker could rewrite the memory in any location of the affected product.

  • Critical 9.8

    AUVESY Versiondog

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

  • High 7.3

    AUVESY Versiondog

    The affected product’s OS Service does not verify any given parameter. A user can supply any type of parameter that will be passed to inner calls without checking the type of the parameter or the value.

  • Medium 4.8

    AUVESY Versiondog

    The affected product’s proprietary protocol CSC allows for calling numerous function codes. In order to call those function codes, the user must supply parameters. There is no sanitation on the value of the offset, which allows the client to specify any offse…

  • High 8.1

    AUVESY Versiondog

    The data of a network capture of the initial handshake phase can be used to authenticate at a SYSDBA level. If a specific .exe is not restarted often, it is possible to access the needed handshake packets between admin/client connections. Using the SYSDBA per…

  • Critical 9.1

    AUVESY Versiondog

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

  • High 8.2

    AUVESY Versiondog

    The affected product uses a hard-coded blowfish key for encryption/decryption processes. The key can be easily extracted from binaries.

  • High 8.0

    AUVESY Versiondog

    The webinstaller is a Golang web server executable that enables the generation of an Auvesy image agent. Resource consumption can be achieved by generating large amounts of installations, which are then saved without limitation in the temp folder of the webin…

  • High 7.3

    AUVESY Versiondog

    The affected product does not properly control the allocation of resources. A user may be able to allocate unlimited memory buffers using API functions.

  • High 7.3

    AUVESY Versiondog

    A specific function code receives a raw pointer supplied by the user and deallocates this pointer. The user can then control what memory regions will be freed and cause use-after-free condition.

  • Critical 9.1

    AUVESY Versiondog

    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.

  • Medium 6.5

    AUVESY Versiondog

    Many API function codes receive raw pointers remotely from the user and trust these pointers as valid in-bound memory regions. An attacker can manipulate API functions by writing arbitrary data into the resolved address of a raw pointer.

  • Critical 9.1

    AUVESY Versiondog

    Many of the services used by the affected product do not specify full paths for the DLLs they are loading. An attacker can exploit the uncontrolled search path by implanting their own DLL near the affected product’s binaries, thus hijacking the loaded DLL.

  • Critical 9.8

    AUVESY Versiondog

    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.

  • High 8.1

    AUVESY Versiondog

    The scheduler service running on a specific TCP port enables the user to start and stop jobs. There is no sanitation of the supplied JOB ID provided to the function. An attacker may send a malicious payload that can enable the user to execute another SQL expr…

  • High 8.0

    AUVESY Versiondog

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

  • High 7.3

    AUVESY Versiondog

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