The Schneider Electric M340 PLC modules allow remote attackers to cause a denial of service (resource consumption) via unspecified vectors.
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 2.1% (FIRST EPSS); higher than 81.8% of all records.
- No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The Schneider Electric M340 PLC modules allow remote attackers to cause a denial of service (resource consumption) via unspecified vectors. NOTE: the vendor reportedly disputes this issue because it "could not be duplicated" and "an attacker could not remotely exploit this observed behavior to deny PLC control functions.
- Published
- Apr 4, 2013
- Updated
- Jun 16, 2026
- EPSS
- 2.1% · 81th percentile
- CWE
- CWE-400
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 20 / 40 · 5.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| schneider-electric | modicon m340 bmx noc 0401 firmware | cpe:2.3:o:schneider-electric:modicon_m340_bmx_noc_0401_firmware |
| schneider-electric | modicon m340 bmx noc 0401 | cpe:2.3:h:schneider-electric:modicon_m340_bmx_noc_0401 |
| schneider-electric | modicon m340 bmx noe 0100 firmware | cpe:2.3:o:schneider-electric:modicon_m340_bmx_noe_0100_firmware |
| schneider-electric | modicon m340 bmx noe 0100 | cpe:2.3:h:schneider-electric:modicon_m340_bmx_noe_0100 |
| schneider-electric | modicon m340 bmx noe 0100h firmware | cpe:2.3:o:schneider-electric:modicon_m340_bmx_noe_0100h_firmware |
| schneider-electric | modicon m340 bmx noe 0100h | cpe:2.3:h:schneider-electric:modicon_m340_bmx_noe_0100h |
| schneider-electric | modicon m340 bmx noe 0110 firmware | cpe:2.3:o:schneider-electric:modicon_m340_bmx_noe_0110_firmware |
| schneider-electric | modicon m340 bmx noe 0110 | cpe:2.3:h:schneider-electric:modicon_m340_bmx_noe_0110 |
| schneider-electric | modicon m340 bmx noe 0110h firmware | cpe:2.3:o:schneider-electric:modicon_m340_bmx_noe_0110h_firmware |
| schneider-electric | modicon m340 bmx noe 0110h | cpe:2.3:h:schneider-electric:modicon_m340_bmx_noe_0110h |
| schneider-electric | modicon m340 bmx nor 0200h firmware | cpe:2.3:o:schneider-electric:modicon_m340_bmx_nor_0200h_firmware |
| schneider-electric | modicon m340 bmx nor 0200h | cpe:2.3:h:schneider-electric:modicon_m340_bmx_nor_0200h |
and 12 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- schneider-electric modicon m340 bmx noc 0401 firmwareall versions
- schneider-electric modicon m340 bmx noe 0100 firmwareall versions
- schneider-electric modicon m340 bmx noe 0100h firmwareall versions
- schneider-electric modicon m340 bmx noe 0110 firmwareall versions
- schneider-electric modicon m340 bmx noe 0110h firmwareall versions
- schneider-electric modicon m340 bmx nor 0200h firmwareall versions
- schneider-electric modicon m340 bmx p34-2010 firmwareall versions
- schneider-electric modicon m340 bmx p34-2030 firmwareall versions
- schneider-electric modicon m340 bmxp341000 firmwareall versions
- schneider-electric modicon m340 bmxp342010 firmwareall versions
- schneider-electric modicon m340 bmxp342020 firmwareall versions
- schneider-electric modicon m340 bmxp342030 firmwareall versions
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- P · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- P
Weakness class (CWE)
CWE-400 · Uncontrolled Resource ConsumptionCVSS vector
AV:N/AC:L/Au:N/C:N/I:N/A:P
nvd-primary
Root cause
Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.
The bug in code
The whole CWE-400 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
function expand(node) { return node.children.map(expand);}Fixed
const MAX_DEPTH = 32;function expand(node, depth = 0) { if (depth > MAX_DEPTH) throw new Error("too deep"); return node.children.map((c) => expand(c, depth + 1));}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.