CVE-2020-12523: Phoenix Contact mGuard Devices versions before 8.8.3: LAN ports get functional after reboot even if they are disabled in the device configuration
Noroxi assessment
Priority: Monitor (action score 36/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: 0.89% (FIRST EPSS); higher than 60.1% of all records.
- 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.
- According to the record, no fixed version is available yet.
- Severity is disputed: the assigning authority (CNA) scores it 5.4, NVD 9.1.
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
On Phoenix Contact mGuard Devices versions before 8.8.3 LAN ports get functional after reboot even if they are disabled in the device configuration. For mGuard devices with integrated switch on the LAN side, single switch ports can be disabled by device configuration. After a reboot these ports get functional independent from their configuration setting: Missing Initialization of Resource
- Published
- Dec 17, 2020
- Updated
- Jun 16, 2026
- EPSS
- 0.8% · 60th percentile
- CWE
- CWE-909
Report tools
Action score
36
Low priority for now.
- CVSS
- 36 / 40 · 9.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.8%
CNA vs NVD score
- NVD
- 9.1
- CNA · CERTVDE
- 5.4
- 3.7 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
Is your version affected? Check itNoroxi 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 |
|---|---|---|
| phoenixcontact | tc mguard rs4000 4g vzw vpn firmware | cpe:2.3:o:phoenixcontact:tc_mguard_rs4000_4g_vzw_vpn_firmware |
| phoenixcontact | tc mguard rs4000 4g vzw vpn | cpe:2.3:h:phoenixcontact:tc_mguard_rs4000_4g_vzw_vpn |
| phoenixcontact | tc mguard rs4000 4g att vpn firmware | cpe:2.3:o:phoenixcontact:tc_mguard_rs4000_4g_att_vpn_firmware |
| phoenixcontact | tc mguard rs4000 4g att vpn | cpe:2.3:h:phoenixcontact:tc_mguard_rs4000_4g_att_vpn |
| phoenixcontact | fl mguard rs4004 tx\/dtx firmware | cpe:2.3:o:phoenixcontact:fl_mguard_rs4004_tx\/dtx_firmware |
| phoenixcontact | fl mguard rs4004 tx\/dtx | cpe:2.3:h:phoenixcontact:fl_mguard_rs4004_tx\/dtx |
| phoenixcontact | fl mguard rs4004 tx\/dtx vpn firmware | cpe:2.3:o:phoenixcontact:fl_mguard_rs4004_tx\/dtx_vpn_firmware |
| phoenixcontact | fl mguard rs4004 tx\/dtx vpn | cpe:2.3:h:phoenixcontact:fl_mguard_rs4004_tx\/dtx_vpn |
| phoenixcontact | tc mguard rs4000 3g vpn firmware | cpe:2.3:o:phoenixcontact:tc_mguard_rs4000_3g_vpn_firmware |
| phoenixcontact | tc mguard rs4000 3g vpn | cpe:2.3:h:phoenixcontact:tc_mguard_rs4000_3g_vpn |
| phoenixcontact | tc mguard rs4000 4g vpn firmware | cpe:2.3:o:phoenixcontact:tc_mguard_rs4000_4g_vpn_firmware |
| phoenixcontact | tc mguard rs4000 4g vpn | cpe:2.3:h:phoenixcontact:tc_mguard_rs4000_4g_vpn |
and 6 more
Versions reported by the vendor
Affected version ranges reported by the assigning authority (CERTVDE). Independent of NVD's CPE analysis and usually ahead of it.
Innominate Innominate mGuard rs4000 4TX/3G/TX VPN
- unspecified and later · before 8.8.3affected
Innominate Innominate mGuard rs4000 4TX/TX
- unspecified and later · before 8.8.3affected
Innominate Innominate mGuard rs4000 4TX/TX VPN
- unspecified and later · before 8.8.3affected
Phoenix Contact FL MGUARD RS4004 TX/DTX (2701876)
- unspecified and later · before 8.8.3affected
Phoenix Contact FL MGUARD RS4004 TX/DTX VPN (2701877)
- unspecified and later · before 8.8.3affected
Phoenix Contact TC MGUARD RS4000 3G VPN (2903440)
- unspecified and later · before 8.8.3affected
Phoenix Contact TC MGUARD RS4000 4G ATT VPN (1010463)
- unspecified and later · before 8.8.3affected
Phoenix Contact TC MGUARD RS4000 4G VPN (2903586)
- unspecified and later · before 8.8.3affected
Phoenix Contact TC MGUARD RS4000 4G VZW VPN (1010461)
- unspecified and later · before 8.8.3affected
Affected versions · NVD (9)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- phoenixcontact fl mguard rs4004 tx/dtx firmwarebefore 8.8.3
- phoenixcontact fl mguard rs4004 tx/dtx vpn firmwarebefore 8.8.3
- phoenixcontact innominate mguard rs4000 4tx/3g/tx vpn firmwarebefore 8.8.3
- phoenixcontact innominate mguard rs4000 4tx/tx firmwarebefore 8.8.3
- phoenixcontact innominate mguard rs4000 4tx/tx vpn firmwarebefore 8.8.3
- phoenixcontact tc mguard rs4000 3g vpn firmwareall versions
- phoenixcontact tc mguard rs4000 4g att vpn firmwarebefore 8.8.3
- phoenixcontact tc mguard rs4000 4g vpn firmwarebefore 8.8.3
- phoenixcontact tc mguard rs4000 4g vzw vpn firmwarebefore 8.8.3
Same product
phoenixcontact: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-7699Phoenix Contact: OS command execution in MGUARD products35Monitor
- CVE-2024-43388Phoenix Contact: SNMP reconfiguration due to improper input validation in MGUARD devices35Monitor
- CVE-2024-43387Phoenix Contact: Access files due to improper neutralization of special elements in MGUARD devices35Monitor
Published before and after this one in the same product
- Later →CVE-2024-7734Sep 10, 2024 · Phoenix Contact: Multiple mGuard devices are vulnerable to a drain of open file descriptors.21Monitor
- Later →CVE-2024-43385Sep 10, 2024 · Phoenix Contact: OS command execution through PROXY_HTTP_PORT in mGuard devices35Monitor
- Later →CVE-2024-43386Sep 10, 2024 · Phoenix Contact: OS command execution through EMAIL_NOTIFICATION.TO in mGuard devices.35Monitor
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.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.
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
- high · data can be read
- 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
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-909 · Missing Initialization of ResourceCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (0)
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.