dbcve.org
Stbnic2212 FirmwareOperating system · Schneider Electric

CVE-2014-0754

HIGH · 10.0 CVSS v2.0 Published 2014-10-03
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
Directory traversal vulnerability in SchneiderWEB on Schneider Electric Modicon PLC Ethernet modules 140CPU65x Exec before 5.5, 140NOC78x Exec before 1.62, 140NOE77x Exec before 6.2, BMXNOC0401 before 2.05, BMXNOE0100 before 2.9, BMXNOE0110x Exec before 6.0, TSXETC101 Exec before 2.04, TSXETY4103x Exec before 5.7, TSXETY5103x Exec before 5.9, TSXP57x ETYPort Exec before 5.7, and TSXP57x Ethernet Copro Exec before 5.5 allows remote attackers to visit arbitrary resources via a crafted HTTP request.

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 · high confidence

Directory traversal vulnerability in SchneiderWEB web interface on Schneider Electric Modicon PLC Ethernet modules allows remote attackers to access arbitrary system files by using '..' path traversal sequences in crafted HTTP requests. With CVSS 10, this is a critical severity flaw enabling unauthenticated remote attackers to potentially read sensitive system files, configurations, or other resources outside the web root.

MitigationUpdate affected PLC Ethernet module firmware to the patched versions specified (140CPU65x Exec 5.5+, 140NOC78x 1.62+, 140NOE77x 6.2+, BMXNOC0401 2.05+, BMXNOE0100 2.9+, BMXNOE0110x 6.0+, TSXETC101 2.04+, TSXETY4103x 5.7+, TSXETY5103x 5.9+, TSXP57x ETYPort 5.7+, TSXP57x Ethernet Copro 5.5+). Implement network segmentation to restrict web interface access to trusted networks only.

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
Stbnic2212 FirmwareOperating system
Affected:all versions
Stbnip2212 FirmwareOperating system
Affected:all versions
Tsxetc0101 FirmwareOperating system
Affected:all versions
Tsxetc100 FirmwareOperating system
Affected:all versions
Tsxp573623mc FirmwareOperating system
Affected:all versions
Tsxety110ws FirmwareOperating system
Affected:all versions
Tsxp574634m FirmwareOperating system
Affected:all versions
Tsxety110wsc FirmwareOperating system
Affected:all versions

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 device model and firmware version
    Access the PLC web interface or use SNMP/management console to query the firmware version. Look for identifiers like Stbnic2212, Stbnip2212, Tsxetc0101, Tsxetc100, Tsxp573623mc, Tsxety110ws, Tsxp574634m, or Tsxety110wsc in the device information or web interface footer.
    Affected if The device model matches any of the listed affected products and the web interface is accessible.
  2. Confirm SchneiderWEB interface is enabled
    Attempt to access the default SchneiderWEB interface URL (typically http://<device_ip>/ or check for web server ports 80/443 open on the device). Use nmap or similar to scan for open HTTP/HTTPS ports on the PLC Ethernet module.
    Affected if The web interface responds and shows Schneider Electric PLC web content, indicating SchneiderWEB is enabled.
  3. Verify network exposure of the web interface
    Check if the PLC Ethernet module IP is accessible from untrusted networks. Review firewall rules, VLAN segmentation, and network ACLs to determine if the web interface port (80/443) is exposed to the internet or untrusted VLANs.
    Affected if The SchneiderWEB interface is reachable from networks outside the trusted control network.
  4. Test for path traversal vulnerability
    Send a crafted HTTP GET request with '../' sequences to the web interface, such as GET /..//..//..//etc/passwd or similar path traversal patterns. Compare the response to normal requests.
    Affected if The device returns file contents from outside the web root directory, confirming the directory traversal vulnerability is exploitable.

The environment is affected if a Schneider Electric Modicon PLC Ethernet module (Stbnic2212, Stbnip2212, Tsxetc0101, Tsxetc100, Tsxp573623mc, Tsxety110ws, Tsxp574634m, or Tsxety110wsc) has its SchneiderWEB interface exposed and accessible, as all firmware versions of these products contain the directory traversal flaw.

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
Patch available Apply the vendor patch
Vendor patch download.schneider-electric.com →
Interim mitigation

Update affected PLC Ethernet module firmware to the patched versions specified (140CPU65x Exec 5.5+, 140NOC78x 1.62+, 140NOE77x 6.2+, BMXNOC0401 2.05+, BMXNOE0100 2.9+, BMXNOE0110x 6.0+, TSXETC101 2.04+, TSXETY4103x 5.7+, TSXETY5103x 5.9+, TSXP57x ETYPort 5.7+, TSXP57x Ethernet Copro 5.5+). Implement network segmentation to restrict web interface access to trusted networks only.

Recommended fix Moderate confidence

Firmware version 5.5 (140CPU65x Exec), 1.62 (140NOC78x Exec), 6.2 (140NOE77x Exec), 2.05 (BMXNOC0401), 2.9 (BMXNOE0100), 6.0 (BMXNOE0110x Exec), 2.04 (TSXETC101), 5.7 (TSXETY4103x Exec), 5.9 (TSXETY5103x Exec), 5.7 (TSXP57x ETYPort Exec), or 5.5 (TSXP57x Ethernet Copro Exec) - depending on model

  1. 1. Identify the exact model number of the affected Schneider Electric Modicon PLC Ethernet module from the device hardware label or management interface
  2. 2. Access the Schneider Electric download portal at download.schneider-electric.com and locate the security advisory SEVD-2014-260-01
  3. 3. Download the firmware update corresponding to your specific model: 140CPU65x Exec to version 5.5 or later, 140NOC78x Exec to version 1.62 or later, 140NOE77x Exec to version 6.2 or later, BMXNOC0401 to version 2.05 or later, BMXNOE0100 to version 2.9 or later, BMXNOE0110x Exec to version 6.0 or later, TSXETC101 Exec to version 2.04 or later, TSXETY4103x Exec to version 5.7 or later, TSXETY5103x
  4. 4. Review the firmware upgrade procedure in the product manual to ensure proper backup of configuration and controlled shutdown of processes
  5. 5. Upload and apply the firmware update via the device's web interface or management software, following Schneider Electric's documented upgrade procedure
  6. 6. After upgrading, verify the firmware version has been successfully applied and test that the HTTP service functions normally
  7. 7. Implement network segmentation to limit HTTP access to the device to trusted networks only as an additional compensating control
Caveat Industrial control system firmware upgrades may require configuration backup and should be tested in a non-production environment first; some legacy features may be deprecated in newer firmware versions

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

Fix this in Stbnic2212 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-0754 — 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-2014-0754 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