dbcve.org
Icdm Rx\/tcp Socketserver FirmwareOperating system · Pepperl Fuchs

CVE-2024-38501

MEDIUM · 6.1 CVSS v3.1 Published 2024-08-13
Fix available
A fix is available. Upgrade to 1.0.7 / 1.08 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An unauthenticated remote attacker may use a HTML injection vulnerability with limited length to inject malicious HTML code and gain low-privileged access on the affected device.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

An unauthenticated remote attacker can exploit an HTML injection vulnerability with limited input length to inject malicious HTML code, potentially enabling low-privileged access to the affected device. The vulnerability appears to be a stored injection (given the length constraint), likely in a web interface of a network device or application.

MitigationImplement strict input validation and output encoding to neutralize HTML/JavaScript in user-supplied fields; apply Content Security Policy (CSP) headers as defense-in-depth.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Icdm Rx\/tcp Socketserver FirmwareOperating system
Affected:< 11.65
Profinet FirmwareOperating system
Affected:< 3.4.9
Profinet\/modbus FirmwareOperating system
Affected:< 1.0.7
Modbus Router FirmwareOperating system
Affected:< 7.09
Modbus Server FirmwareOperating system
Affected:< 7.11
Modbus Tcp FirmwareOperating system
Affected:< 7.11
Ethernet\/ip FirmwareOperating system
Affected:< 7.22
Eip\/modbus FirmwareOperating system
Affected:< 1.08

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Pepperl Fuchs device model
    Access the device web interface or check device documentation/labels to identify the specific model (e.g., ICDM Rx/tcp Socketserver, Profinet, Modbus Router, Modbus Server, Modbus TCP, Ethernet/ip, or EIP/Modbus)
    Affected if The device model matches any of the affected product lines: ICDM Rx/tcp Socketserver, Profinet, Profinet/Modbus, Modbus Router, Modbus Server, Modbus TCP, Ethernet/ip, or EIP/Modbus
  2. Check installed firmware version
    Log into the device web interface and navigate to System Information or Firmware/Software version page; alternatively, check via SNMP or device management console using 'show version' or equivalent command
    Affected if The firmware version is below the affected threshold for your specific device model (ICDMrx/tcp < 11.65, Profinet < 3.4.9, Profinet/Modbus < 1.0.7, Modbus Router < 7.09, Modbus Server < 7.11, Modbus TCP < 7.11, Ethernet/ip < 7.22, EIP/Modbus < 1.08)
  3. Verify web interface is enabled
    Check device configuration settings for web server/HTTP interface status; look for options like 'Enable Web Server', 'HTTP Management', or 'Web UI' in the device web-based management console
    Affected if The web interface is enabled and accessible on the device (required for the HTML injection to be exploitable)
  4. Confirm network accessibility of web interface
    Attempt to reach the device web interface via HTTP (typically ports 80/443) from a management workstation, or check firewall/network segmentation rules that may allow or block access
    Affected if The device web interface is reachable from network segments where untrusted users could send requests (even without authentication)

You are affected if you have a Pepperl Fuchs device from the affected product lines with a web-enabled firmware version below the specified thresholds, and the web interface is network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.0.7 / 1.08 / 3.4.9 or later
Fixed in 1.0.71.083.4.9
Interim mitigation

Implement strict input validation and output encoding to neutralize HTML/JavaScript in user-supplied fields; apply Content Security Policy (CSP) headers as defense-in-depth.

Recommended fix High confidence

Upgrade to Icdm Rx/tcp Socketserver firmware 11.65, Profinet 3.4.9, Profinet/modb Modbus 1.0.7, Modbus Router 7.09, Modbus Server 7.11, Modbus Tcp 7.11, Ethernet/ip 7.22, or Eip/modb Modbus 1.08 (as applicable to your device)

  1. Identify the specific firmware version currently running on the affected device(s) using the device's web interface or administrative console
  2. Navigate to the vendor's support or download page (cert.vde.com or official vendor site)
  3. Download the appropriate fixed firmware version for your device model: Icdm Rx/tcp Socketserver 11.65, Profinet 3.4.9, Profinet/modb Modbus 1.0.7, Modbus Router 7.09, Modbus Server 7.11, Modbus Tcp 7.11, Ethernet/ip 7.22, or Eip/modb Modbus 1.08
  4. Follow the vendor's standard firmware update procedure, typically via the device's web interface or a dedicated firmware upload utility
  5. After upgrading, verify the new firmware version is installed and confirm the vulnerability is remediated
  6. Consider implementing network segmentation and access controls to limit exposure until patches can be applied
Caveat Firmware updates on industrial devices may require recalibration or reconfiguration; always review vendor release notes before upgrading production systems

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Icdm Rx\/tcp Socketserver Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-38501 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-38501 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data