CVE intelligence and bounded remediation

CVE-2019-13943 — Siemens En100 Ethernet Module With Firmware Variant Dnp3 Tcp security vulnerability

Medium CVSS 6.1

A vulnerability has been identified in EN100 Ethernet module DNP3 variant (All versions), EN100 Ethernet module IEC 61850 variant (All versions < V4.37), EN100 Ethernet module IEC104 variant (All versions), EN100 Ethernet module Modbus TCP variant (All versions), EN100 Ethernet module PROFINET IO variant (All versions). The web interface could allow Cross-Site Scripting (XSS) attacks if an attacker is able to modify content of particular web pages, causing the application to behave in unexpected ways for legitimate users. Successful exploitation does not require for an attacker to be authenticated to the web interface. This could allow the attacker to read or modify contents of the web application. At the time of advisory publication no public exploitation of this security. vulnerability was known.

Severity
Medium
CVSS
6.1 (3.1)
Published
2019-12-12
CISA KEV
Not currently listed
Ecosystem
operating-system
Weaknesses
CWE-79

Affected products

  • siemens / en100_ethernet_module_with_firmware_variant_dnp3_tcp
  • siemens / en100_ethernet_module_with_firmware_variant_iec_61850
  • siemens / en100_ethernet_module_with_firmware_variant_iec104
  • siemens / en100_ethernet_module_with_firmware_variant_modbus_tcp
  • siemens / en100_ethernet_module_with_firmware_variant_profinet_io

Matched remediation archetype

Cross-site scripting and unsafe browser output

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Trace reflected, stored, and DOM-derived untrusted values into HTML, attributes, URLs, styles, scripts, and client-side template sinks.
  • Identify affected origins, authenticated user roles, sensitive browser capabilities, and where content is shared across tenants.
  • Review framework escaping, rich-text sanitization, legacy templates, and client-side rendering paths.

Remediate safely

  • Use context-aware framework output encoding and safe DOM APIs; keep untrusted data out of executable contexts.
  • Sanitize intentionally supported markup with a maintained allowlist policy and validate URLs and attributes separately.
  • Update affected rendering components and add tests for every output context using inert sentinel markup.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.