Secuno
ENNL
Book demo

CVE-2017-5159

Phoenix Contact Mguard Firmware vulnerability

9.8 CRITICALEPSS 2.43%
  1. Published13 Feb 2017

Description

An issue was discovered on Phoenix Contact mGuard devices that have been updated to Version 8.4.0. When updating an mGuard device to Version 8.4.0 via the update-upload facility, the update will succeed, but it will reset the password of the admin user to its default value.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Phoenix Contact Mguard Firmware8.4.0

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2025-434919.8
A vulnerability in the Poly Lens Desktop application running on the Windows platform…
CVE-2025-24109.1
Port manipulation vulnerabilities in ASPECT provide attackers with the ability to…
CVE-2025-07569.1
Overview   The product receives input from an upstream component, but it does…
CVE-2024-57068.8
The product receives input from an upstream component, but it does not restrict or…
CVE-2024-579719.1
DataSourceResource.java in the SpagoBI API support in Knowage Server in KNOWAGE before…

Frequently asked

Is CVE-2017-5159 being actively exploited?

CVE-2017-5159 is not in the CISA KEV catalog. Its EPSS exploit probability is 2.43%.

How severe is CVE-2017-5159?

CVE-2017-5159 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 2.43% probability of exploitation.

Which products are affected by CVE-2017-5159?

Affected products include Phoenix Contact Mguard Firmware.

How do I fix CVE-2017-5159?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2017-5159 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.