LiveActive security incident?Get immediate response
CVE Record

CVE-2020-21813: A heap based buffer overflow issue exists in GNU LibreDWG 0.10.2641 via output_TEXT ../../programs/dwg2SVG....

A heap based buffer overflow issue exists in GNU LibreDWG 0.10.2641 via output_TEXT ../../programs/dwg2SVG.c:114.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-21813 is a reported heap buffer overflow in GNU LibreDWG 0.10.2641, in the dwg2SVG text output path. The public record is sparse: no CVSS score, CWE, CPE, confirmed patch, or impact statement is provided. Treat risk as workload-dependent, especially where DWG files from outside parties are converted automatically.

Executive priority

Prioritize review if CAD conversion is internet-facing, automated, or handles customer-supplied DWG files. Otherwise, track as a targeted dependency risk pending clearer vendor remediation data.

Technical view

The CVE description identifies a heap-based buffer overflow in output_TEXT in programs/dwg2SVG.c around line 114 in GNU LibreDWG 0.10.2641. The sources do not document exploit primitives, affected CPEs, fixed versions, or confirmed security impact beyond memory corruption potential.

Likely exposure

Exposure is most likely where LibreDWG 0.10.2641 or dwg2SVG is installed and processes DWG files, especially untrusted CAD uploads, email attachments, vendor submissions, or automated conversion jobs.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. Public details are limited to the CVE record and a LibreDWG GitHub issue reference, so exploitation status and real-world weaponization remain unconfirmed.

Researcher notes

The CVE metadata is incomplete: severity, CVSS, CWE, CPE, affected product fields, exploit status, and fix version are not provided. Analysis should stay anchored to GNU LibreDWG 0.10.2641 and dwg2SVG only.

Mitigation direction

  • Inventory systems using GNU LibreDWG or dwg2SVG.
  • Check upstream LibreDWG guidance for fixed versions or recommended workarounds.
  • Avoid processing untrusted DWG files with affected LibreDWG builds.
  • Isolate CAD conversion jobs with least privilege and resource limits.
  • Monitor conversion services for crashes or memory-safety faults.

Validation and detection

  • Confirm whether LibreDWG 0.10.2641 is present in packages or containers.
  • Identify workflows that convert DWG files to SVG.
  • Review whether DWG inputs come from external or unauthenticated users.
  • Compare installed LibreDWG versions against upstream advisories.
  • Check logs for dwg2SVG crashes during DWG processing.
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.

cve · low confidence lookup

CVE-2020-21813 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
1ADP providers
2Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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