LiveActive security incident?Get immediate response
CVE Record

CVE-2020-28615: 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_vertex() vh->shalfedges_last().

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 files. If an exposed application accepts attacker-supplied geometry input and parses it with this library, the flaw could crash the process or potentially allow code execution.

Executive priority

Treat as urgent where CGAL processes external files or customer uploads. Prioritize internet-facing or automated ingestion services first, then developer workstations and internal tooling that open untrusted geometry files.

Technical view

The CVE describes multiple vulnerabilities in CGAL 5.1.1 Nef polygon parsing, including an out-of-bounds read and type confusion in Nef_S2/SNC_io_parser.h read_vertex(), associated with CWE-129. The CVSS 3.0 score is 10.0.

Likely exposure

Exposure is most likely in applications or services that use libcgal 5.1.1 to parse untrusted Nef polygon or related geometry files. General hosts with CGAL installed but not processing attacker-controlled input have lower practical exposure.

Exploitation context

The sources state that malicious input can trigger the issue and could lead to code execution. The bundle does not show CISA KEV listing or other evidence of active exploitation.

Researcher notes

The source bundle identifies CGAL 5.1.1 and a specific Nef_S2 parser read path but does not provide full fixed-version detail. Avoid assuming exploit availability; focus validation on dependency inventory and untrusted parsing paths.

Mitigation direction

  • Inventory applications and packages using CGAL libcgal 5.1.1.
  • Apply relevant vendor security updates from Debian, Gentoo, or your software supplier.
  • Restrict or disable untrusted Nef polygon parsing until updated.
  • Check upstream and distribution guidance for exact fixed package versions.
  • Run affected parsers with least privilege and isolation where feasible.

Validation and detection

  • Confirm installed CGAL/libcgal versions on affected systems.
  • Map user-upload, network, or automated geometry parsing paths.
  • Verify vendor security updates are installed successfully.
  • Retest file-processing workflows after patching.
  • Review crash telemetry for malformed geometry parsing failures.
Prepared
Confidence
medium
Sources
4

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-28615 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-28615Attack 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.