LiveActive security incident?Get immediate response
CVE Record

CVE-2021-38451: 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 offset and read out-of-bounds data.

MediumCVSS 4.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Versiondog’s proprietary CSC protocol can be asked to read data from unintended memory locations because an offset value is not properly checked. The main business concern is confidentiality: a low-privileged client may be able to read sensitive out-of-bounds data under specific conditions.

Executive priority

Treat this as a confidentiality risk for Versiondog environments, especially in OT settings. It is not KEV-listed and has medium CVSS severity, but affected scope is broad in the bundle, so asset owners should verify exposure and follow vendor guidance.

Technical view

CVE-2021-38451 is a CWE-125 out-of-bounds read in AUVESY Versiondog. CSC protocol function calls accept parameters, but the offset value is not sanitized, allowing arbitrary offsets and out-of-bounds reads. CVSS 3.1 is 4.8 with network attack vector, high complexity, low privileges, and user interaction required.

Likely exposure

Exposure is limited to environments running AUVESY Versiondog. The source bundle says all versions are affected, but it does not identify specific components, ports, deployment modes, or fixed releases.

Exploitation context

The CVSS vector indicates remote network reachability, high attack complexity, low required privileges, and required user interaction. CISA KEV status is false in the bundle, and no provided source states active exploitation.

Researcher notes

Evidence is narrow: the bundle provides the vulnerability class, CVSS vector, affected product, and CISA advisory link, but no exploit details, fixed version, or operational indicators. Avoid assuming affected ports, exploit maturity, or remediation specifics beyond vendor verification.

Mitigation direction

  • Check AUVESY and CISA guidance for fixed versions or vendor-approved mitigations.
  • Inventory Versiondog deployments and confirm whether CSC protocol access is required.
  • Restrict Versiondog access to authorized management users and trusted networks.
  • Prioritize remediation where Versiondog handles sensitive OT or automation data.

Validation and detection

  • Identify installed Versiondog versions and compare them with vendor guidance.
  • Review network paths that can reach Versiondog CSC services.
  • Confirm which users or clients have Versiondog protocol access.
  • Check logs for unexpected Versiondog protocol activity where available.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-125: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-38451 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.8CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:N1.23.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.8Medium
CVSS 3.1 vector shape for CVE-2021-38451Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AUVESYVersiondogAllListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-125 · source CWE mapping

Out-of-bounds Read

Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.