LiveActive security incident?Get immediate response
CVE Record

CVE-2020-35629: 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_sloop() slh->facet().

CriticalCVSS 10Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CGAL libcgal 5.1.1 can mishandle malformed Nef polygon input. A malicious file or input stream may cause memory parsing errors that could lead to code execution. Business risk is highest where CGAL processes untrusted geometry files or user-supplied model data.

Executive priority

Treat as high-priority where CGAL handles external geometry data. The stated impact includes possible code execution and full confidentiality, integrity, and availability loss, but urgency depends on whether vulnerable parsing is reachable.

Technical view

CVE-2020-35629 is an out-of-bounds read/type confusion issue in Nef_S2/SNC_io_parser.h, specifically SNC_io_parser<EW>::read_sloop() via slh->facet(). Sources describe crafted malformed input as the trigger and potential code execution as the impact.

Likely exposure

Exposure is likely limited to applications, services, or workflows using CGAL libcgal 5.1.1 to parse Nef polygon data from untrusted or externally supplied files.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. Talos reports malicious input can trigger the flaw, but the provided evidence does not establish in-the-wild exploitation.

Researcher notes

Focus validation on reachability: whether Nef polygon parsing is exposed to attacker-controlled input. The bundle identifies the vulnerable function and affected version but does not provide patch-version detail or proof of exploitation.

Mitigation direction

  • Inventory applications and packages using CGAL libcgal 5.1.1.
  • Apply relevant vendor security updates from CGAL, Debian, Gentoo, or your distribution.
  • Restrict ingestion of untrusted Nef polygon files until patched.
  • Run parsing workloads with least privilege and isolation where feasible.
  • Check vendor advisories for fixed versions and backported patches.

Validation and detection

  • Confirm installed CGAL/libcgal package versions on affected systems.
  • Identify services or jobs that parse Nef polygon input.
  • Review dependency manifests and container images for CGAL 5.1.1.
  • Verify vendor security updates are installed successfully.
  • Test that untrusted geometry uploads are blocked or isolated.
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-35629 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-35629Attack 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.