An Improper Validation of Integrity Check Value issue was discovered in PHOENIX CONTACT mGuard firmware versions 7.2 to 8.6.0.
An Improper Validation of Integrity Check Value issue was discovered in PHOENIX CONTACT mGuard firmware versions 7.2 to 8.6.0. mGuard devices rely on internal checksums for verification of the internal integrity of the update packages. Verification may not always be performed correctly, allowing an attacker to modify firmware update packages.
- Published
- Jan 30, 2018
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 19th percentile
- CWE
- CWE-354
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| phoenixcontact | mguard centerport firmware | cpe:2.3:o:phoenixcontact:mguard_centerport_firmware |
| phoenixcontact | mguard centerport | cpe:2.3:h:phoenixcontact:mguard_centerport |
| phoenixcontact | mguard delta tx\/tx firmware | cpe:2.3:o:phoenixcontact:mguard_delta_tx\/tx_firmware |
| phoenixcontact | mguard delta tx\/tx | cpe:2.3:h:phoenixcontact:mguard_delta_tx\/tx |
| phoenixcontact | mguard delta tx\/tx vpn firmware | cpe:2.3:o:phoenixcontact:mguard_delta_tx\/tx_vpn_firmware |
| phoenixcontact | mguard delta tx\/tx vpn | cpe:2.3:h:phoenixcontact:mguard_delta_tx\/tx_vpn |
| phoenixcontact | mguard gt\/gt firmware | cpe:2.3:o:phoenixcontact:mguard_gt\/gt_firmware |
| phoenixcontact | mguard gt\/gt | cpe:2.3:h:phoenixcontact:mguard_gt\/gt |
| phoenixcontact | mguard gt\/gt vpn firmware | cpe:2.3:o:phoenixcontact:mguard_gt\/gt_vpn_firmware |
| phoenixcontact | mguard gt\/gt vpn | cpe:2.3:h:phoenixcontact:mguard_gt\/gt_vpn |
| phoenixcontact | mguard pci4000 vpn firmware | cpe:2.3:o:phoenixcontact:mguard_pci4000_vpn_firmware |
| phoenixcontact | mguard pci4000 vpn | cpe:2.3:h:phoenixcontact:mguard_pci4000_vpn |
and 34 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- phoenixcontact mguard centerport firmware7.2.0 and later · up to 8.6.0 inclusive
- phoenixcontact mguard core tx vpn firmware7.2.0 and later · up to 8.6.0 inclusive
- phoenixcontact mguard delta tx/tx firmware7.2.0 and later · up to 8.6.0 inclusive
- phoenixcontact mguard delta tx/tx vpn firmware7.2.0 and later · up to 8.6.0 inclusive
- phoenixcontact mguard gt/gt firmware7.2.0 and later · up to 8.6.0 inclusive
- phoenixcontact mguard gt/gt vpn firmware7.2.0 and later · up to 8.6.0 inclusive
- phoenixcontact mguard pci4000 vpn firmware7.2.0 and later · up to 8.6.0 inclusive
- phoenixcontact mguard pcie4000 vpn firmware7.2.0 and later · up to 8.6.0 inclusive
- phoenixcontact mguard rs2000 3g vpn firmware7.2.0 and later · up to 8.6.0 inclusive
- phoenixcontact mguard rs2000 4g vpn firmware7.2.0 and later · up to 8.6.0 inclusive
- phoenixcontact mguard rs2000 tx/tx vpn firmware7.2.0 and later · up to 8.6.0 inclusive
- phoenixcontact mguard rs2000 tx/tx-b firmware7.2.0 and later · up to 8.6.0 inclusive
- phoenixcontact mguard rs2005 tx vpn firmware7.2.0 and later · up to 8.6.0 inclusive
- phoenixcontact mguard rs4000 3g vpn firmware7.2.0 and later · up to 8.6.0 inclusive
- phoenixcontact mguard rs4000 4g vpn firmware7.2.0 and later · up to 8.6.0 inclusive
- phoenixcontact mguard rs4000 tx/tx firmware7.2.0 and later · up to 8.6.0 inclusive
- phoenixcontact mguard rs4000 tx/tx vpn firmware7.2.0 and later · up to 8.6.0 inclusive
- phoenixcontact mguard rs4000 tx/tx vpn-m firmware7.2.0 and later · up to 8.6.0 inclusive
- phoenixcontact mguard rs4000 tx/tx-p firmware7.2.0 and later · up to 8.6.0 inclusive
- phoenixcontact mguard rs4004 tx/dtx firmware7.2.0 and later · up to 8.6.0 inclusive
Versions reported by the vendor
Affected version ranges reported by the assigning authority (icscert). Independent of NVD's CPE analysis and usually ahead of it.
n/a PHOENIX CONTACT mGuard
- PHOENIX CONTACT mGuardaffected
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
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-354 · Improper Validation of Integrity Check ValueCVSS vector
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; 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 helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
- www.securityfocus.com/bid/102907
- cert.vde.com/en-us/advisories/vde-2018-001
- ics-cert.us-cert.gov/advisories/ICSA-18-030-01
Vendor advisories and official records. Exploit/PoC links are deliberately left out.