LiveActive security incident?Get immediate response
CVE Record

CVE-2021-33983: Buffer Overflow vulnerability in Dvidelabs flatcc v.0.6.0 allows local attacker to execute arbitrary code v...

Buffer Overflow vulnerability in Dvidelabs flatcc v.0.6.0 allows local attacker to execute arbitrary code via the fltacc execution of the error_ref_sym function.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-33983 is a local buffer overflow reported in Dvidelabs flatcc v0.6.0. A user with local access could potentially make the affected execution path run arbitrary code, with high confidentiality, integrity, and availability impact. The provided sources do not identify active exploitation or a confirmed fixed version.

Executive priority

Treat as a high-priority local exposure issue for developer and build environments, not as confirmed internet-facing exploitation. Prioritize inventory and vendor-status confirmation before broad emergency response.

Technical view

The CVE describes CWE-120 in flatcc v0.6.0 involving the error_ref_sym function during tool execution. CVSS 3.1 is 7.8: local attack vector, low complexity, low privileges required, no user interaction, unchanged scope, and high CIA impact. Product metadata is incomplete in the CVE bundle.

Likely exposure

Exposure is most likely where flatcc v0.6.0 is installed or invoked locally, especially developer workstations, build hosts, CI runners, or packaging environments. The CVE bundle provides no CPEs or broader affected product list.

Exploitation context

The source bundle does not show CISA KEV listing or other evidence of active exploitation. The scored scenario requires local access and low privileges; remote unauthenticated exploitation is not supported by the provided evidence.

Researcher notes

Evidence is limited: affected vendor/product fields are n/a, no CPEs are supplied, and only one GitHub issue is referenced. Avoid assuming affected forks, fixed releases, exploit maturity, or remote reachability without additional vendor evidence.

Mitigation direction

  • Inventory systems and pipelines for flatcc v0.6.0 usage.
  • Check the upstream flatcc issue and CVE record for maintainer remediation guidance.
  • Restrict local access to build hosts running affected flatcc tooling.
  • Run build and parsing tools with least privilege and isolated workspaces.
  • Replace or update flatcc only after confirming a fixed upstream version.

Validation and detection

  • Review dependency manifests, toolchains, containers, and CI images for flatcc v0.6.0.
  • Confirm whether flatcc is executable by untrusted local users.
  • Map systems where flatcc processes untrusted or externally supplied inputs.
  • Check vendor and GitHub issue status for fix or workaround updates.
  • Document compensating controls where no vendor fix is 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-120: 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-33983 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:L/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
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/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-33983Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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

CWE-120 · source CWE mapping

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.