LiveActive security incident?Get immediate response
CVE Record

CVE-2020-28625: 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_facet() fh->boundary_entry_objects SLoop_of.

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, causing memory errors that may allow code execution. Business risk is highest where CGAL processes untrusted geometry files or data from customers, uploads, integrations, or automated pipelines.

Executive priority

Treat as high-priority where CGAL parses external geometry data, because the stated impact includes code execution and full confidentiality, integrity, and availability compromise. Prioritize internet-facing or customer-input workflows first.

Technical view

The issue is in CGAL Nef polygon parsing, specifically SNC_io_parser read_facet boundary handling. Sources describe out-of-bounds read and type confusion conditions from malformed input, with potential code execution. The CVE lists CWE-129 and CVSS 10.0.

Likely exposure

Exposure is likely in applications or services using libcgal CGAL-5.1.1 to parse Nef polygon data from untrusted or semi-trusted sources. Internal-only batch tools are lower exposure unless inputs originate externally.

Exploitation context

The source bundle says an attacker can provide malicious input to trigger the vulnerability. CISA KEV status is false, and the provided sources do not state active exploitation in the wild.

Researcher notes

Do not assume every CGAL user is vulnerable; validate reachable Nef polygon parsing and the deployed version. The bundle identifies CGAL-5.1.1 and distro advisories, but does not provide exploit prevalence or a universal upstream fixed version.

Mitigation direction

  • Identify CGAL/libcgal deployments and confirm whether version 5.1.1 is present.
  • Apply relevant CGAL, Debian, Gentoo, or platform security updates where available.
  • Restrict untrusted geometry parsing until patched or isolated.
  • Run parsing workloads with least privilege and process isolation.
  • Check vendor guidance for exact fixed versions and backported package names.

Validation and detection

  • Inventory binaries, packages, containers, and build manifests for CGAL/libcgal usage.
  • Confirm whether Nef polygon parsing is reachable from uploads, APIs, or automated imports.
  • Review package manager advisory status for Debian or Gentoo managed systems.
  • Check application logs for crashes during malformed geometry parsing.
  • Document compensating controls if patching is delayed.
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-28625 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-28625Attack 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.