CVE-2020-12525
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 · uneditedM&M Software fdtCONTAINER Component in versions below 3.5.20304.x and between 3.6 and 3.6.20304.x is vulnerable to deserialization of untrusted data in its project storage.
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 confidenceM&M Software fdtCONTAINER component fails to properly validate deserialized data in its project storage functionality, allowing attackers to potentially execute arbitrary code or cause denial of service by supplying malicious serialized objects.
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 dataall versions>= 5.0, <= 5.0.5.31all versions< 4.5>= 4.5.0, <= 4.5.20304>= 4.6.0, <= 4.6.20304< 3.5>= 3.5.0, <= 3.5.20304>= 3.6.0, <= 3.6.20304<= 2.5.1<= 1.5.48CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 fdtCONTAINER or related product installationLocate the installed software: check program directories for fdtCONTAINER, Pactware (Pepperl Fuchs), Dtminspector (Wago), Wi Manager (Weidmueller), or Emerson Rosemount Transmitter Interface Software. Use system inventory tools or manually review installed programs.Affected if Any of these products are installed and the version falls within affected ranges
-
Determine installed versionAccess the software's About or Help menu, check the executable file properties (right-click > Properties > Details), or review installation logs and registry entries for version information.Affected if Version cannot be determined or is within affected ranges: Pactware 5.0-5.0.5.31; Wago Fdtcontainer Application <4.5, 4.5.0-4.5.20304, or 4.6.0-4.6.20304; Wago Fdtcontainer Component <3.5, 3.5.0-3.5.20304, or 3.6.0-3.6.20304; Wi Manager <=2.5.1; Emerson and Wago Dtminspector all versions; Io Link Ma
-
Locate project storage filesSearch for project files with extensions such as .fdt, .fdtp, .fdc, or vendor-specific project formats in user-accessible directories, typically under Documents or application data folders.Affected if Project storage files exist and are accessible to unauthorized users (lack of proper file permissions)
-
Verify deserialization feature exposureDetermine if the project storage functionality is enabled or accessible. Check if the software loads or imports project files, as the vulnerability occurs during deserialization of stored project data.Affected if Project storage feature is active and processes deserialized data from accessible project files
You are affected if the installed product is any version of Emerson Rosemount, Wago Dtminspector, Pepperl Fuchs Io Link Master <=1.5.48, Weidmueller Wi Manager <=2.5.1, Pepperl Fuchs Pactware 5.0-5.0.5.31, or Wago fdtCONTAINER (Application <4.5 or 4.5.x <=4.5.20304 or 4.6.x <=4.6.20304; Component <3.5 or 3.5.x <=3.5.20304 or 3.6.x <=3.6.20304), and project storage files are present and accessible.
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 data3.54.5
Upgrade fdtCONTAINER to version 3.5.20304.x or higher, or 3.6.20304.x or higher. Until patched, restrict unauthorized access to project storage files and implement network segmentation.
- Consultation6.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-12525 — 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-2020-12525 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