LiveActive security incident?Get immediate response
CVE Record

CVE-2021-38453: AUVESY Versiondog

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

CriticalCVSS 9.1Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2021-38453 affects AUVESY Versiondog. Certain API functions can interact with the Windows registry, including modifying data. If the API is reachable by an attacker, the business risk is unauthorized configuration changes that could disrupt or alter systems managed by Versiondog.

Executive priority

Treat this as urgent for environments using Versiondog, especially OT or production operations. The available evidence supports critical severity, but not confirmed active exploitation. Prioritize exposure reduction and vendor-guided remediation over broad assumptions about fixes.

Technical view

The issue is classified as CWE-15 and scored CVSS 9.1. The vector indicates network access, low complexity, no privileges, and no user interaction, with high integrity and availability impact. The source bundle states all Versiondog versions are affected, but does not provide patch details.

Likely exposure

Exposure is most likely where AUVESY Versiondog is deployed and its API is reachable from untrusted or broadly accessible networks. The bundle lists affected versions as all, so teams should treat any Versiondog deployment as potentially in scope until vendor guidance confirms otherwise.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. Risk remains high because the CVSS vector indicates unauthenticated network access and potential registry data modification, which can affect system integrity and availability.

Researcher notes

The source bundle is narrow: it names registry read and modification through API functions, CWE-15, CVSS 9.1, and all versions affected. It does not include affected build boundaries, exploit status, or a specific patch level, so validation should center on deployment exposure and vendor advisory review.

Mitigation direction

  • Review the CISA ICS advisory and AUVESY guidance for official fixes.
  • Apply any vendor-provided updates or mitigations when confirmed applicable.
  • Restrict Versiondog API access to trusted administrative networks only.
  • Block external or unnecessary network paths to Versiondog services.
  • Monitor for unexpected registry-related API activity or configuration changes.

Validation and detection

  • Inventory all Versiondog deployments and confirm exposure paths.
  • Check whether any Versiondog API endpoints are reachable from untrusted networks.
  • Verify applied vendor updates or documented compensating controls.
  • Review logs for unexpected API use or registry modification indicators.
  • Document residual exposure where remediation guidance is not yet confirmed.
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-15: 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-38453 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
Critical
CVSS
9.1 (3.1)
Known Exploited
No
Published

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

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
9.1CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H3.95.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.1Critical
CVSS 3.1 vector shape for CVE-2021-38453Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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-15 · source CWE mapping

External Control of System or Configuration Setting

External Control of System or Configuration Setting represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.