LiveActive security incident?Get immediate response
CVE Record

CVE-2021-32421: dpic 2021.01.01 has a Heap Use-After-Free in thedeletestringbox() function in dpic.y.

dpic 2021.01.01 has a Heap Use-After-Free in thedeletestringbox() function in dpic.y.

HighCVSS 7.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-32421 is a memory-safety flaw in dpic 2021.01.01. A specially handled input can trigger a heap use-after-free and crash the process. The public record rates this mainly as an availability risk, not a confirmed data theft or code execution issue.

Executive priority

Treat this as a high-priority availability issue if dpic is used in exposed or automated processing paths. For isolated desktop-only use, urgency is lower, but version confirmation and vendor-guidance review are still appropriate.

Technical view

The CVE describes CWE-416 heap use-after-free in thedeletestringbox() in dpic.y. The CVSS 3.1 score is 7.5 with network, low-complexity, no-privilege, no-user-interaction characteristics and availability-only impact. The bundle does not provide CPEs, a full affected-version range, or a named fixed release.

Likely exposure

Exposure is most plausible where dpic processes untrusted diagram or document input in automation, build systems, conversion services, or network-reachable workflows. The source data only names dpic 2021.01.01 and lists no CPEs, so asset validation is required.

Exploitation context

CISA KEV is false in the supplied bundle, and no cited source states active exploitation. Public evidence supports a denial-of-service style risk through process crash. The bundle does not substantiate exploit maturity or broader compromise capability.

Researcher notes

The record is sparse: it identifies function, weakness class, version, CVSS vector, issue, and commit reference, but not a fixed release or affected-version range. Validate against upstream repository history before asserting remediation status.

Mitigation direction

  • Inventory dpic usage and confirm whether version 2021.01.01 is present.
  • Review upstream issue and commit guidance before applying changes.
  • Avoid processing untrusted dpic input until remediated or isolated.
  • Run dpic conversion jobs with least privilege and resource limits.
  • Monitor vendor or maintainer channels for fixed release information.

Validation and detection

  • Check installed dpic version on hosts and build images.
  • Search CI, document conversion, and web processing workflows for dpic invocation.
  • Review package manifests and container images for bundled dpic copies.
  • Confirm whether upstream commit d317e406 is included in deployed builds.
  • Record compensating controls for any unpatched dpic processing path.
Prepared
Confidence
medium
Sources
4

Public sources used

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-416: 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-32421 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.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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
3Source 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.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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
n/an/an/aListed
Weakness

CWE details

CWE-416

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

CWE-416 · source CWE mapping

Use After Free

Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs