CVE Intelligence
Skip to main content
HIGH

CVE-2021-38459

CVE-2021-38459 — 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 permission, an attacker can change user passwords or delete the database.

Published Updated Sources: cvelistV5, icscert

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

1%

chance of exploitation in 30 days

Affects

auvesy

versiondog

CVSS base

8.1

HIGH

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

auvesy

Products (1)

versiondog

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
8.1CVSS 3.1HIGH——cvelistV5

Weakness & attack patterns

  • CWE-294

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1558.003Steal or Forge Kerberos Tickets: Kerberoasting
  • T1021Remote Services
  • T1114.002Email Collection: Remote Email Collection

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

  • Search application, proxy, and WAF logs for requests touching /client.

References

1 on the record

Elsewhere on this site

  • auvesyevery CVE for this vendor
  • CWE-294other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.