LiveActive security incident?Get immediate response
CVE Record

CVE-2021-38477: 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.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2021-38477 is a critical Versiondog flaw where unauthenticated network access could allow file data to be read, written, manipulated, or deleted. For an operational technology environment, this can threaten confidentiality, integrity, and availability of engineering or automation-management data.

Executive priority

Treat this as urgent for any environment running Versiondog, especially OT or engineering networks. Prioritize exposure reduction first, then confirm vendor remediation guidance and backup integrity.

Technical view

The CVE describes multiple API function codes in AUVESY Versiondog that permit file and directory read/write operations. The assigned CVSS 3.1 score is 9.8 with network access, low complexity, no privileges, and no user interaction required. The listed weakness is CWE-73.

Likely exposure

The provided source bundle lists AUVESY Versiondog as affected across all versions, but does not provide deployment-specific exposure data. Risk is highest where Versiondog API services are reachable from untrusted networks.

Exploitation context

The bundle does not show CISA KEV listing or other cited evidence of active exploitation. The CVSS vector indicates the issue is remotely reachable and unauthenticated, but exploit activity should not be assumed from the provided evidence.

Researcher notes

Evidence is limited to the CVE record and CISA advisory reference in the bundle. Do not infer patch availability, exploit maturity, or product variants beyond AUVESY Versiondog as listed.

Mitigation direction

  • Check AUVESY and CISA guidance for supported fixes or compensating controls.
  • Restrict Versiondog API access to trusted management networks only.
  • Block direct internet exposure for Versiondog services.
  • Use network segmentation and VPN controls around OT management systems.
  • Maintain tested backups of Versiondog files and configuration data.

Validation and detection

  • Inventory all Versiondog deployments and confirm version ownership.
  • Identify whether Versiondog API services are reachable from untrusted networks.
  • Review CISA advisory and vendor guidance for affected scope.
  • Check logs and backups for unexpected file changes or deletions.
  • Confirm firewall rules restrict access to approved administrators.
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 · medium confidence lookup

CWE-73: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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-38477 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.8 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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-73 · source CWE mapping

External Control of File Name or Path

External Control of File Name or Path represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.