LiveActive security incident?Get immediate response
CVE Record

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

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2021-38449 is a critical memory-write flaw in AUVESY Versiondog. Public records say some API functions let a client choose buffer parameters, allowing memory to be rewritten in the affected product. Because the CVSS vector is network-based, unauthenticated, and no user interaction is required, exposed systems should be treated as high business risk.

Executive priority

Treat this as urgent if Versiondog is deployed, especially in industrial or operational environments. The issue has critical severity and needs no authentication per CVSS, but the provided sources do not confirm exploitation or a specific patch.

Technical view

The issue is classified as CWE-123, a write-what-where condition. The CVE description says client-controlled API parameters can write or copy data into a supplied buffer, potentially rewriting arbitrary memory in Versiondog. The published CVSS 3.1 score is 9.8 with high confidentiality, integrity, and availability impact.

Likely exposure

The source bundle lists AUVESY Versiondog, all versions, as affected. Highest concern is any Versiondog deployment whose API surface is reachable from untrusted networks. The bundle does not provide CPEs, deployment prerequisites, or a confirmed fixed version.

Exploitation context

The CVSS vector indicates network attackability, low complexity, no privileges, and no user interaction. CISA KEV status is false in the supplied data, so there is no provided evidence of known active exploitation. No public exploit details are included in the bundle.

Researcher notes

Analysis is limited to the supplied CVE and CISA reference metadata. The affected range is broad: all versions. Validate with the CISA ICS advisory and vendor materials before asserting exploitability details, fixes, or environment-specific impact.

Mitigation direction

  • Check the CISA ICS advisory and AUVESY guidance for current remediation details.
  • Inventory all Versiondog deployments and owners immediately.
  • Remove untrusted network reachability to Versiondog API surfaces where possible.
  • Apply vendor-provided updates or compensating controls when identified.
  • Document any exception where affected Versiondog remains reachable.

Validation and detection

  • Confirm whether AUVESY Versiondog is deployed in production or OT environments.
  • Identify network paths that can reach Versiondog API services.
  • Verify deployed versions against vendor and CISA guidance.
  • Check monitoring for unusual access to Versiondog services.
  • Record remediation status, residual exposure, and accountable owner.
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-123: 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-38449 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-38449Attack 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-123 · source CWE mapping

Write-what-where Condition

Write-what-where Condition represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.