LiveActive security incident?Get immediate response
CVE Record

CVE-2021-43983: WECON LeviStudioU

WECON LeviStudioU Versions 2019-09-21 and prior are vulnerable to multiple stack-based buffer overflow instances while parsing project files, which may allow an attacker to execute arbitrary code.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-43983 affects WECON LeviStudioU when it opens project files. A malicious or malformed project file could crash the application or run code on the user's workstation. The main business risk is compromise of engineering systems through file handling, not remote internet scanning.

Executive priority

Treat this as a high-priority engineering workstation risk. It is not described as remotely exploitable without user action, but successful exploitation could give an attacker code execution where project files are handled.

Technical view

The CVE describes multiple stack-based buffer overflows in WECON LeviStudioU versions 2019-09-21 and prior while parsing project files. CVSS 3.1 is 7.8 with local attack vector, no privileges required, user interaction required, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely on workstations where WECON LeviStudioU is installed and users open project files, especially from email, partners, shared drives, or removable media. The source bundle has inconsistent affected-version wording, so confirm exact installed versions against vendor or CISA guidance.

Exploitation context

The source bundle does not report active exploitation, and the CVE is not listed as CISA KEV. Exploitation requires a user to open a crafted project file locally. That lowers wormable risk but keeps workstation compromise risk meaningful in operational environments.

Researcher notes

This is CWE-121 stack-based overflow behavior in project-file parsing. The CVSS vector confirms local delivery and required user interaction. ZDI references indicate multiple related advisories, but this bundle does not provide enough detail to distinguish each parsing path or confirm exploit availability.

Mitigation direction

  • Inventory systems running WECON LeviStudioU, especially version 2019-09-21 and prior.
  • Check WECON or CISA guidance for fixed versions or vendor-supported remediation.
  • Restrict opening LeviStudioU project files to trusted sources and approved transfer paths.
  • Isolate engineering workstations from general email, web browsing, and broad file shares.
  • Monitor for LeviStudioU crashes, unusual child processes, or unexpected file activity.

Validation and detection

  • Confirm installed LeviStudioU versions on engineering and maintenance workstations.
  • Map who receives, opens, or imports LeviStudioU project files.
  • Review whether project files arrive from external parties or removable media.
  • Check endpoint logs for repeated LeviStudioU faults or suspicious process behavior.
  • Verify any remediation against CISA and vendor advisory language.
Prepared
Confidence
high
Sources
12

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-121: 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
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-43983 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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
16Source 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
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2021-43983Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
WECONLeviStudioUAllListed
Weakness

CWE details

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

CWE-121 · source CWE mapping

Stack-based Buffer Overflow

Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.