LiveActive security incident?Get immediate response
CVE Record

CVE-2020-28609: 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_face() store_iv().

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 specially crafted malformed Nef polygon files. If a business system processes untrusted geometry files with this library, the flaw could allow code execution in that processing context. Systems not using CGAL or not parsing attacker-supplied files are less likely exposed.

Executive priority

Treat this as high urgency where CGAL processes untrusted files, because successful exploitation could affect confidentiality, integrity, and availability of the processing system. Prioritize internet-facing or partner-facing file ingestion first.

Technical view

The issue is in CGAL Nef polygon parsing, specifically Nef_2/PM_io_parser.h PM_io_parser<PMDEC>::read_face() store_iv(). Sources describe an out-of-bounds read and type confusion triggered by malformed input, with potential code execution. The CVE maps to CWE-129 and has CVSS 3.0 score 10.0.

Likely exposure

Exposure is most likely in applications, services, or batch workflows using CGAL libcgal 5.1.1 to parse Nef polygon or related geometry files supplied by users, partners, or automated pipelines.

Exploitation context

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

Researcher notes

Evidence supports malformed-file-triggered memory safety issues in CGAL 5.1.1 Nef parsing. Public sources identify potential code execution, but the bundle does not provide exploit-in-the-wild evidence or a universal upstream fixed version.

Mitigation direction

  • Inventory applications and packages using CGAL libcgal 5.1.1.
  • Apply the relevant vendor or distribution CGAL security update where available.
  • For Debian LTS systems, review DLA 3226-1 for the cgal update path.
  • Avoid processing untrusted geometry files until remediation is confirmed.
  • Run exposed parsers with least privilege and isolation controls.

Validation and detection

  • Confirm whether deployed software links to or bundles CGAL libcgal 5.1.1.
  • Identify file upload, import, or batch jobs that parse Nef polygon data.
  • Check package versions against vendor or distribution security advisories.
  • Verify remediation in staging before re-enabling untrusted file processing.
  • Document any systems that cannot be patched and compensating controls used.
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-28609 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
3Source 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-28609Attack 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.