CVE-2013-0664
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 · uneditedThe FactoryCast service on the Schneider Electric Quantum 140NOE77111 and 140NWM10000, M340 BMXNOE0110x, and Premium TSXETY5103 PLC modules allows remote authenticated users to send Modbus messages, and consequently execute arbitrary code, by embedding these messages in SOAP HTTP POST requests.
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 confidenceThe FactoryCast web service on Schneider Electric PLC network modules (Quantum 140NOE77111, 140NWM10000, M340 BMXNOE0110x, Premium TSXETY5103) accepts SOAP HTTP POST requests containing embedded Modbus messages. Remote attackers with valid authentication can exploit this to send arbitrary Modbus commands and achieve remote code execution on the PLC modules.
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= 140noe77111= 140nwm10000= bmxnoe0110x= tsxety5103CVSS 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
- M
- Authentication
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:S/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed PLC hardware modelsLocate the physical PLC modules or check inventory/asset management systems for Schneider Electric Modicon Quantum (140NOE77111, 140NWM10000), M340 (BMXNOE0110x), or Premium (TSXETY5103) network modulesAffected if Any of these specific model numbers are present in the environment
-
Check FactoryCast web service statusAccess the PLC web interface or check running services on the network module for the FactoryCast web serviceAffected if FactoryCast web service is enabled and running on the PLC network module
-
Verify network accessibility of FactoryCast serviceAttempt to reach the web interface on the PLC network module from various network segments, or review firewall rules and network segmentation configurationsAffected if FactoryCast service is exposed beyond the intended local management network
-
Confirm authentication configurationReview user accounts and authentication settings for the FactoryCast web interface to determine if default or weak credentials may be in useAffected if Authentication is enabled but uses default credentials or is accessible to unauthorized users
-
Review firmware versionCheck the installed firmware version on the affected PLC network modules against the known affected versionsAffected if The firmware version matches 140NOE77111, 140NWM10000, BMXNOE0110x, or TSXETY5103
A user is affected if they have any of the specified PLC network module models with FactoryCast web service enabled and accessible on their network.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply Schneider Electric firmware updates for affected modules and restrict FactoryCast service access to authorized personnel via network segmentation or disabling the service if unused.
- Consultation12.0 h
- Implementation20.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,208.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0664 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-0664 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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