LiveActive security incident?Get immediate response
CVE Record

CVE-2020-35632: 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_S2/SNC_io_parser.h SNC_io_parser<EW>::read_sface() sfh->boundary_entry_objects Edge_of.

CriticalCVSS 10Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Software using CGAL 5.1.1 to read certain polygon files can crash or potentially run attacker-controlled code when given a malformed file. Risk is highest where geometry files come from customers, partners, uploads, or automated imports. No source here shows active exploitation.

Executive priority

Prioritize remediation where CGAL processes outside-supplied files. The worst case is code execution in a file-processing workflow, but the provided evidence does not show active exploitation. Patch during the next urgent security maintenance window for exposed systems.

Technical view

CVE-2020-35632 affects CGAL libcgal 5.1.1 Nef polygon parsing. The cited issue is an out-of-bounds read in Nef_S2/SNC_io_parser.h read_sface(), with type confusion and possible code execution from crafted malformed input. It is tracked as CWE-129 and rated CVSS 10.0.

Likely exposure

Exposure is likely limited to systems, applications, or services that use libcgal CGAL-5.1.1 and parse untrusted Nef polygon or related geometry files. General servers without CGAL-based file parsing are unlikely to be exposed.

Exploitation context

The bundle says an attacker can provide malicious input to trigger the bug, but it does not cite public exploitation, weaponized tooling, or CISA KEV listing. Treat internet-facing or automated file-processing workflows as higher priority.

Researcher notes

Focus on dependency reachability, not only package presence. The vulnerable code path is Nef polygon parsing in CGAL 5.1.1, specifically cited around SNC_io_parser read_sface(). Evidence supports malformed-input triggered memory-safety impact; exact upstream fixed version is not provided in the bundle.

Mitigation direction

  • Identify applications and packages using CGAL libcgal 5.1.1.
  • Apply relevant vendor or distribution CGAL security updates.
  • Restrict or isolate untrusted geometry file parsing until patched.
  • Check current CGAL, Debian, or Gentoo guidance for fixed package versions.

Validation and detection

  • Inventory libcgal or CGAL versions on affected hosts and containers.
  • Review services for untrusted Nef polygon or geometry file ingestion.
  • Confirm Debian or Gentoo security updates are installed where applicable.
  • Test parsing workflows safely with benign validation files after updating.
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-35632 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-35632Attack 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.