Loading vulnerabilities…
Loading vulnerabilities…
CVE-2024-24782
An unauthenticated attacker can send a ping request from one network to another through an error in the origin verification even though the ports are separated by VLAN.
This record: live connection— last retrieved: 7 November 2026 at 14:22.
Vendor
Products
F30 03X YY (COM) all variants, F30 03X YY (CPU) all variants, F35 03X YY (COM) all variants, F35 03X YY (CPU) all variants, F60 CPU 03X YY (COM) all variants, F60 CPU 03X YY (CPU) all variants and 6 more
up to version <=24.14
Published
13 February 2024
Last modified
17 June 2026
Taken directly from NVD, CISA or the vendor — sometimes in English, unchanged from the source.
An unauthenticated attacker can send a ping request from one network to another through an error in the origin verification even though the ports are separated by VLAN.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Attack vector
NETWORK
Privileges required
NONE
User interaction
NONE
Confidentiality
Limited
Integrity
None
Availability
None
Probability of exploitation within 30 days
0.2%
Percentile
5e
Source: FIRST.org, updated on 6 November 2026.
CVE-2024-24781: All load limiting measures are helpful (e.g. in external devices or also in the switch of the above mentioned products). Please check whether the reduced speed is still sufficient for the desired application. Protect the network with segregation measures and restrict the access of unauthorized network participants (e.g. close unused ports) CVE-2024-24782: Switching the MAC-learning from 'conservative' to 'tolerant' mitigates the above described vulnerability but leads to potential IP-Spoofing and ARP-Poisoning and should therefore be avoided. HIMax and HIQuad X systems can be setup in the way that real physical segregation (between different modules) is used. E.g. it is impossible to ping from one X-COM to another X-COM in the same Rack. HIMatrix should be used in that way that CPU and COM are NOT connected via VLAN e.g. CPU connected to Port 1 and 2, COM Connected to Port 3 and 4.
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
Based on CVSS 4.3, EPSS 0.2%, industrial relevance 40/100.
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
Operational impact & energy relevance
Limited impact on availability; the risk lies mainly with confidentiality or integrity of process data.
No strong energy-sector-specific signals recognised; general OT/ICS relevance.
Recommended defensive measures
Industrial relevance score
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
Automatic IACS Radar assessment based on the reported CWE weakness classification; not an official certification statement.