Security Advisory

CVE-2020-12494: Beckhoff TwinCAT RT Driver EtherLeak

Last updated:
  • CVE-2020-12494

CVE-2020-12494 is an "EtherLeak" memory disclosure in Beckhoff's TwinCAT RT network driver for Intel 8254x and 8255x Ethernet controllers, the driver that provides TwinCAT's EtherCAT function: short Ethernet frames sent outside the real-time path are not zero-padded, so stale memory goes out in the padding bytes. NVD scores it CVSS v2 5.0 (Primary) and v3.1 5.3.

Vulnerability summary

CVSS base score

5

Medium severity

EPSS score (FIRST)

1.0%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

Vulnerability ID: CVE-2020-12494 · Source: NVD

Affected components

ComponentCPEVersion range
Beckhoff TwinCAT RT driver for Intel 8254x (TwinCAT 2.11 build 2350, 3.1 builds 4022 and 4024)cpe:2.3:a:beckhoff:twincat_driver:*:*:*:*:*:*:*:*TwinCAT 2.11 build 2350 driver <= 2.11.0.2120; TwinCAT 3.1 build 4022 driver <= 3.1.0.3512; TwinCAT 3.1 build 4024 driver <= 3.1.0.3603 (CERT@VDE VDE-2020-019 CSAF); patches on request from Beckhoff
Beckhoff TwinCAT RT driver for Intel 8255x (TwinCAT 2.11 build 2350, 3.1 builds 402x and 4024)cpe:2.3:a:beckhoff:twincat:*:*:*:*:*:*:*:*TwinCAT 2.11 build 2350 driver <= 2.11.0.2117; TwinCAT 3.1 build 402 driver <= 3.1.0.3600; TwinCAT 3.1 build 4024 driver <= 3.1.0.3500 (CERT@VDE VDE-2020-019 CSAF); patches on request from Beckhoff

What does this mean for affected devices?

NVD's description, taken from the CERT@VDE record, says that "except for Ethernet frames sent from real-time functionality, all other Ethernet frames sent through the driver are not padded if their payload is less than the minimum Ethernet frame size. Instead, arbitrary memory content is transmitted within in the padding bytes of the frame." The leaked bytes are most likely slices of earlier transmitted or received frames, and an attacker "can hardly control which memory content is affected". The record's own example trigger is a small ICMP echo request sent to the device.

NVD's only Primary metric is CVSS v2 5.0 (AV:N/AC:L/Au:N/C:P/I:N/A:N). NVD and CERT@VDE both give CVSS v3.1 5.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N), which NVD labels Secondary. NVD lists CWE-459 (Incomplete Cleanup); CERT@VDE's advisory uses CWE-200 (Exposure of Sensitive Information). The record was published on 2020-06-16 (NVD).

Which TwinCAT versions are affected?

CERT@VDE's VDE-2020-019, published 2020-06-16 and last revised on 2025-05-22, splits the driver into two products. The machine-readable version (CERT@VDE CSAF) lists:

Driver TwinCAT build Affected driver versions
Intel 8254x 2.11 build 2350 up to 2.11.0.2120
Intel 8254x 3.1 build 4022 up to 3.1.0.3512
Intel 8254x 3.1 build 4024 up to 3.1.0.3603
Intel 8255x 2.11 build 2350 up to 2.11.0.2117
Intel 8255x 3.1 build 402 up to 3.1.0.3600
Intel 8255x 3.1 build 4024 up to 3.1.0.3500

NVD's CPE configuration matches the same ranges and pairs them with the Intel 82540 to 82547 and 82557 to 82559 controllers. The flaw sits in the PC-side driver of a TwinCAT controller or industrial PC whose Intel port carries EtherCAT, not in EtherCAT field devices.

How do you fix or mitigate CVE-2020-12494?

CERT@VDE's remediation is that Beckhoff offers software patches for TwinCAT 3.1 and TwinCAT 2.11 on request, to be folded into the regular releases of those versions; the advisory names no public fixed build number. Its two mitigations: if a port needs no TwinCAT real-time communication, switch it to the Intel driver that ships with Beckhoff images, and block traffic from untrusted networks to the device at a perimeter firewall, "especially regarding ICMP and other small ethernet frames". Our EtherCAT protocol security guide lists this CVE next to the other EtherCAT-related records, including the Zeek parser flaws CVE-2023-7242, CVE-2023-7243 and CVE-2023-7244.

Other device pages where a small leak gives away more than intended: CVE-2017-7923 in Hikvision cameras and CVE-2026-60007, a padding-oracle flaw in Eclipse Milo OPC UA.

CVE-2020-12494 is not in the CISA KEV catalog as of 2026-11-18 (catalog version 2026.11.13). FIRST EPSS gives it 0.01014, the 64th percentile, in the 2026-11-17 dataset (CISA KEV, FIRST EPSS).

How to fix this class of issueNo dedicated SoftWSP guide covers this weakness class; the fix is usually the vendor patch or firmware update referenced above. Our related guide explains how to plan and verify it: NIST SP 800-40 Rev. 4: enterprise patch management planning, explained.

Evidence

  • NVD: TwinCAT RT network driver for Intel 8254x and 8255x provides EtherCAT functionality; non-real-time frames below minimum size not padded, arbitrary memory in padding; example trigger small ICMP echo requests. Primary CVSS v2 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N; CVSS v3.1 5.3 from NVD and CERT@VDE (both Secondary); CWE-459; published 2020-06-16; CPE twincat_driver <= 3.1.0.3603 and twincat <= 3.1.0.3512, 3.1.0.3600, 3.1.0.3500, 2.11.0.2120, 2.11.0.2117 with Intel 8254x/8255x hardware. — NVD
  • VDE-2020-019 published 2020-06-16, last update 2025-05-22; CWE-200; remediation: Beckhoff offers software patches for TwinCAT 3.1 and TwinCAT 2.11 on request, included in the next regular releases; mitigation: use the Intel driver shipped with Beckhoff images if no real-time communication is needed, perimeter firewall blocking ICMP and other small frames. — CERT@VDE VDE-2020-019
  • CSAF VDE-2020-019 version 4 (2025-05-22): TwinCAT Driver for Intel 8254x: 2.11 2350 <=2.11.0.2120, 3.1 4022 <=3.1.0.3512, 3.1 4024 <=3.1.0.3603; Intel 8255x: 2.11 2350 <=2.11.0.2117, 3.1 402 <=3.1.0.3600, 3.1 4024 <=3.1.0.3500; all known_affected. — CERT@VDE CSAF VDE-2020-019
  • Not in the CISA KEV catalog, version 2026.11.13, checked 2026-11-18. — CISA KEV
  • EPSS 0.01014, percentile 0.63817, dataset 2026-11-17. — FIRST EPSS

Related advisories

Sources

  1. NVD
  2. CERT@VDE VDE-2020-019: Beckhoff EtherLeak in TwinCAT RT network driver
  3. CERT@VDE CSAF: VDE-2020-019 (machine-readable advisory)
  4. CISA KEV
  5. FIRST EPSS

Frequently asked questions

Which Beckhoff products are affected by CVE-2020-12494?

The TwinCAT RT network driver for Intel 8254x and 8255x Ethernet controllers in TwinCAT 2.11 build 2350 and TwinCAT 3.1 builds 402, 4022 and 4024, up to the driver versions CERT@VDE VDE-2020-019 lists, for example 3.1.0.3603 for the 8254x driver in build 4024.

Is there a fixed version of the TwinCAT driver for CVE-2020-12494?

CERT@VDE's advisory, last revised 2025-05-22, says Beckhoff offers software patches for TwinCAT 3.1 and 2.11 on request and names no public fixed build number, so ask Beckhoff support for the patch for your build (per CERT@VDE VDE-2020-019, checked 2026-11-18).

What data can CVE-2020-12494 leak?

Whatever memory ends up in the padding of short frames, most likely parts of earlier transmitted or received frames. The attacker cannot choose which memory leaks; a small ICMP echo request to the device is enough to provoke it (per NVD and CERT@VDE).

How do you mitigate CVE-2020-12494 without a patch?

Switch ports that need no TwinCAT real-time traffic to the Intel driver shipped with Beckhoff images, and block traffic from untrusted networks to the device at a perimeter firewall, especially ICMP and other small frames (per CERT@VDE VDE-2020-019).

Is CVE-2020-12494 in the CISA KEV catalog?

No, not as of 2026-11-18 (catalog version 2026.11.13). FIRST EPSS gives it 0.01014, the 64th percentile, in the 2026-11-17 dataset (per CISA KEV and FIRST EPSS).