CVE-2023-5217

Google Chromium libvpx Heap Buffer Overflow Vulnerability

Heap buffer overflow in vp8 encoding in libvpx in Google Chrome prior to 117.0.5938.132 and libvpx 1.13.1 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

CVSS 8.8 KEVPatch available

This record: live connection— last retrieved: 7 November 2026 at 02:35.

Vendor

Pilz

Products

PASvisu, PMI v8xx

up to version <1.14.1

Published

28 September 2023

Last modified

17 June 2026

Original source information

Taken directly from NVD, CISA or the vendor — sometimes in English, unchanged from the source.

Technical description

CVSS 3.1 — vector details

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack vector

NETWORK

Privileges required

NONE

User interaction

REQUIRED

Confidentiality

High

Integrity

High

Availability

High

EPSS — Exploit Prediction Scoring System

Probability of exploitation within 30 days

49.0%

Percentile

99e

Source: FIRST.org, updated on 6 November 2026.

Patch information

Install the fixed product version as soon as it is available. Please visit the Pilz eShop(https://www.pilz.com/en-INT/eshop) to check for the fixed version. Only use project files from trustworthy sources. Protect project files against modification by unauthorized users. Limit network access to legitimate connections by using a firewall or similar measures. Usepassword protection on the online project.

IACS Radar assessment

Our own interpretation and context for the source data above.

IACS Radar assessment

Our own interpretation and context for this vulnerability — not an official source.

IACS Radar priority score

88/ 100

Based on CVSS 8.8, EPSS 49.0%, industrial relevance 50/100; raised due to confirmed active exploitation (KEV).

Combines CVSS, EPSS, KEV status, industrial relevance and exposure relevance — a complement to, not a replacement for, the individual scores below and above.

Conditions for exploitation

•Network access to the affected device or segment is required.
•No valid credentials are needed.
•User interaction (for example opening a file) is required.

Operational impact & energy relevance

Possible loss of visibility of or control over the process upon successful exploitation.

No strong energy-sector-specific signals recognised; general OT/ICS relevance.

Additional mitigations

•Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Recommended defensive measures

•Apply the latest firmware or software update and validate its integrity.
•Restrict network access to the affected device to a dedicated OT management segment.
•Implement network segmentation in line with zones and conduits (IEC 62443-3-2).
•Monitor for abnormal protocol traffic using an OT-aware detection system.

Industrial relevance score

50/ 100

• Mentioned in an official CISA ICS advisory, which confirms direct relevance to industrial control systems.
• Included in the CISA KEV catalogue: confirmed evidence of actual exploitation.

Classification is provisional; manual verification by an OT security analyst is recommended.

Classified by IACS Radar-analysepijplijn (geautomatiseerd) on 7 November 2026.

IEC 62443 mapping

IEC 62443-4-1FR3 · Systeemintegriteit

Automatic IACS Radar assessment based on the reported CWE weakness classification; not an official certification statement.

Loading vulnerabilities…