dbcve.org
Fl Mguard Centerport FirmwareOperating system · Phoenixcontact

CVE-2022-3480

HIGH · 7.5 CVSS v3.1 Published 2022-11-15
Fix available
A fix is available. Upgrade to 8.9.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
A remote, unauthenticated attacker could cause a denial-of-service of PHOENIX CONTACT FL MGUARD and TC MGUARD devices below version 8.9.0 by sending a larger number of unauthenticated HTTPS connections originating from different source IP’s. Configuring firewall limits for incoming connections cannot prevent the issue.

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 · high confidence

A remote, unauthenticated attacker can cause denial-of-service on vulnerable PHOENIX CONTACT FL MGUARD and TC MGUARD devices (versions below 8.9.0) by sending a large volume of HTTPS connections from multiple source IP addresses. This exhausts device resources, and notably, configuring firewall connection limits cannot prevent the attack due to the distributed nature of the connection sources.

MitigationUpgrade MGUARD firmware to version 8.9.0 or later. Until upgrade is possible, consider network segmentation to limit exposure and monitor for unusual HTTPS connection patterns.

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 data
Fl Mguard Centerport FirmwareOperating system
Affected:< 8.9.0
Fl Mguard Centerport Vpn 1000 FirmwareOperating system
Affected:< 8.9.0
Fl Mguard Core Tx FirmwareOperating system
Affected:< 8.9.0
Fl Mguard Core Tx Vpn FirmwareOperating system
Affected:< 8.9.0
Fl Mguard Delta Tx\/tx FirmwareOperating system
Affected:< 8.9.0
Fl Mguard Delta Tx\/tx Vpn FirmwareOperating system
Affected:< 8.9.0
Fl Mguard Gt\/gt FirmwareOperating system
Affected:< 8.9.0
Fl Mguard Gt\/gt Vpn FirmwareOperating system
Affected:< 8.9.0

CVSS 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify MGUARD devices in your network
    Locate Phoenix Contact FL MGUARD or TC MGUARD devices by reviewing network inventory, device labels, or scanning for 'MGUARD' or 'Phoenix Contact' in device hostnames/SNMP sysDescr
    Affected if Any FL MGUARD or TC MGUARD device is present in the environment
  2. Access device firmware version
    Log into the MGUARD web interface (HTTPS) or CLI and navigate to System > Firmware or use the 'show version' command in CLI to retrieve the installed firmware version
    Affected if Firmware version cannot be retrieved or is below 8.9.0
  3. Verify firmware version against affected range
    Compare the installed firmware version string (e.g., 8.8.x, 8.7.x, etc.) to the threshold 8.9.0 - note that any version less than 8.9.0 is affected
    Affected if Installed version is less than 8.9.0 (for example: 8.8.5, 8.7.0, 8.6.x, etc.)

Your environment is affected if any Phoenix Contact FL MGUARD or TC MGUARD device is running firmware version below 8.9.0.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 8.9.0 or later
Fixed in 8.9.0
Interim mitigation

Upgrade MGUARD firmware to version 8.9.0 or later. Until upgrade is possible, consider network segmentation to limit exposure and monitor for unusual HTTPS connection patterns.

Recommended fix High confidence

Firmware version 8.9.0 or later

  1. 1. Identify the exact FL MGUARD or TC MGUARD model device (e.g., Centerport, Core Tx, Delta Tx, GT) from the product label or web interface
  2. 2. Navigate to the official Phoenix Contact download portal or contact their support to obtain the firmware version 8.9.0 or later for your specific model
  3. 3. Backup the current device configuration through the web interface (System > Maintenance > Configuration)
  4. 4. Access the device web interface and navigate to System > Maintenance > Firmware Update
  5. 5. Upload the downloaded firmware file (8.9.0 or later) and initiate the update process
  6. 6. Wait for the firmware upload and installation to complete - do not power off the device during this process
  7. 7. After reboot, verify the firmware version has been updated to 8.9.0 or later in the web interface under System > Information
  8. 8. Restore the previously backed up configuration if needed
Caveat Review Phoenix Contact release notes for version 8.9.0 to check for any configuration or feature changes that may affect your deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fl Mguard Centerport Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-3480 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-3480 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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