LiveActive security incident?Get immediate response
CVE Record

CVE-2020-28602: Multiple code execution vulnerabilities exists in the Nef polygon-parsing functionality of CGAL libcgal CGA...

Multiple code execution vulnerabilities exists in the Nef polygon-parsing functionality of CGAL libcgal CGAL-5.1.1. A specially crafted malformed file can lead to an out-of-bounds read and type confusion, which could lead to code execution. An attacker can provide malicious input to trigger any of these vulnerabilities. An oob read vulnerability exists in Nef_2/PM_io_parser.h PM_io_parser<PMDEC>::read_vertex() Halfedge_of[].

CriticalCVSS 10Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CGAL/libcgal 5.1.1 has memory-safety flaws in Nef polygon file parsing. A malicious malformed geometry file could crash or potentially execute code in software that processes it. Business risk is highest where external users, partners, or automated feeds can submit geometry files.

Executive priority

Prioritize remediation for internet-facing or partner-facing file processing systems. The severity is critical, but urgency depends on actual CGAL 5.1.1 use and untrusted geometry input exposure.

Technical view

The CVE describes multiple code execution vulnerabilities in CGAL 5.1.1 Nef polygon parsing. One cited issue is an out-of-bounds read in Nef_2/PM_io_parser.h, PM_io_parser<PMDEC>::read_vertex(), involving Halfedge_of[]. The CVE maps to CWE-129 and has CVSS 3.0 score 10.0.

Likely exposure

Exposure is likely in applications or services using CGAL/libcgal 5.1.1 to parse Nef polygon or related malformed geometry input. Risk depends on whether untrusted files or data can reach the parser.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation. The stated attack path is malicious input supplied to affected parsing functionality, with possible code execution from out-of-bounds read and type confusion.

Researcher notes

Evidence is strongest for affected version, vulnerable parser area, weakness class, and impact. The bundle does not provide exploit-in-the-wild evidence or universal fixed-version details, so validation should focus on dependency provenance and parser reachability.

Mitigation direction

  • Inventory CGAL/libcgal usage, including bundled copies inside applications.
  • Apply relevant CGAL, Debian, Gentoo, or vendor security updates.
  • For source builds, check upstream CGAL guidance before selecting a fixed version.
  • Restrict or disable untrusted geometry file processing until patched.
  • Run parsing workloads with least privilege and process isolation.

Validation and detection

  • Confirm whether libcgal 5.1.1 is installed or bundled.
  • Map all services that parse Nef polygon or geometry files.
  • Check whether external users can submit files reaching CGAL parsing.
  • Verify Debian or Gentoo advisory updates are applied where applicable.
  • Retest file ingestion workflows after updating dependencies.
Prepared
Confidence
medium
Sources
5

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-129: 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-2020-28602 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
10 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/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
4Source 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
10CVSS 3.0CriticalCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H3.96Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

10Critical
CVSS 3.0 vector shape for CVE-2020-28602Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/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
CGAL ProjectlibcgalCGAL-5.1.1Listed
Weakness

CWE details

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

CWE-129 · source CWE mapping

Improper Validation of Array Index

Improper Validation of Array Index represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.