Skip to content
Noroxi
CVE-2020-7486· NVD / CVE Program· CNA schneider

**VERSION NOT SUPPORTED WHEN ASSIGNED** A vulnerability could cause TCM modules to reset when under high network load in TCM v10.4.x and in

**VERSION NOT SUPPORTED WHEN ASSIGNED** A vulnerability could cause TCM modules to reset when under high network load in TCM v10.4.x and in system v10.3.x. This vulnerability was discovered and remediated in version v10.5.x on August 13, 2009. TCMs from v10.5.x and on will no longer exhibit this behavior.

HighCVSS 7.5 · v3.1—No exploit No fix recorded
Published
Apr 16, 2020
Updated
Jun 16, 2026
EPSS
1.6% · 76th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.6%

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

VendorProduct
schneider-electrictricon tcm 4351 firmware
schneider-electrictricon tcm 4351
schneider-electrictricon tcm 4352 firmware
schneider-electrictricon tcm 4352
schneider-electrictricon tcm 4351a firmware
schneider-electrictricon tcm 4351a
schneider-electrictricon tcm 4351b firmware
schneider-electrictricon tcm 4351b
schneider-electrictricon tcm 4352a firmware
schneider-electrictricon tcm 4352a
schneider-electrictricon tcm 4352b firmware
schneider-electrictricon tcm 4352b

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • schneider-electric tricon tcm 4351 firmware10.3.x
  • schneider-electric tricon tcm 4351 firmware10.4.x
  • schneider-electric tricon tcm 4351a firmware10.3.x
  • schneider-electric tricon tcm 4351a firmware10.4.x
  • schneider-electric tricon tcm 4351b firmware10.3.x
  • schneider-electric tricon tcm 4351b firmware10.4.x
  • schneider-electric tricon tcm 4352 firmware10.3.x
  • schneider-electric tricon tcm 4352 firmware10.4.x
  • schneider-electric tricon tcm 4352a firmware10.3.x
  • schneider-electric tricon tcm 4352a firmware10.4.x
  • schneider-electric tricon tcm 4352b firmware10.3.x
  • schneider-electric tricon tcm 4352b firmware10.4.x

Versions reported by the vendor

Affected version ranges reported by the assigning authority (schneider). Independent of NVD's CPE analysis and usually ahead of it.

  • n/a Tricon TCM Model 4351, 4352, 4351A/B, 4352A/B (v10.3.x, v10.4.x)

    • Tricon TCM Model 4351, 4352, 4351A/B, 4352A/B (v10.3.x, v10.4.x)affected

Same product

schneider-electric: all records

Other highest-scoring records for the same primary product.

  • CVE-2020-7491**VERSION NOT SUPPORTED WHEN ASSIGNED** A legacy debug port account in TCMs installed in Tricon system versions 10.2.0 through 10.5.3 is vis
    30Monitor

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.

EPSS, last 120 days

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 researchers

Finders, 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).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-400 · Uncontrolled Resource Consumption

CVSS vector

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

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 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
function expand(node) {  return node.children.map(expand);}

Fixed

ts
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.

All records