Cyber Resilience

CVE-2025-41692

Crypto Weakness in Phoenixcontact Fl Switch 2708 Pn Firmware ≤ 3.50

Published
09 December 2025
Modified
19 December 2025
CVSS Score v3.1 6.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N
EPSS Score 0.0027 18th percentile
Risk Priority 36 floored blend · peak EPSS

Summary

CVE-2025-41692 is a medium-severity Use of Password Hash With Insufficient Computational Effort (CWE-916) vulnerability in Phoenixcontact Fl Switch 2303-8Sp1. Its CVSS base score is 6.8 (Medium).

Operationally, ranked at the 18th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-7 (Unsuccessful Logon Attempts) and IA-5 (Authenticator Management) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A high privileged remote attacker with admin privileges for the webUI can brute-force the "root" and "user" passwords of the underlying OS due to a weak password generation algorithm.

CWE(s)

Related Threats

CVEs Like This One

CVE-2025-41695Same product: Phoenixcontact Fl Nat 2008
CVE-2025-41749Same product: Phoenixcontact Fl Nat 2008
CVE-2025-41751Same product: Phoenixcontact Fl Nat 2008
CVE-2025-41747Same product: Phoenixcontact Fl Nat 2008
CVE-2025-41752Same product: Phoenixcontact Fl Nat 2008
CVE-2025-41693Same product: Phoenixcontact Fl Nat 2008
CVE-2025-41748Same product: Phoenixcontact Fl Nat 2008
CVE-2025-41745Same product: Phoenixcontact Fl Nat 2008
CVE-2025-41696Same product: Phoenixcontact Fl Nat 2008
CVE-2025-41746Same product: Phoenixcontact Fl Nat 2008

Affected Assets

phoenixcontact
fl switch 2708 pn firmware
≤ 3.50
phoenixcontact
fl switch 2708 firmware
≤ 3.50
phoenixcontact
fl switch 2608 pn firmware
≤ 3.50
phoenixcontact
fl switch 2608 firmware
≤ 3.50
phoenixcontact
fl switch 2516 pn firmware
≤ 3.50
phoenixcontact
fl switch 2208c firmware
≤ 3.50
phoenixcontact
fl switch 2208 pn firmware
≤ 3.50
phoenixcontact
fl switch 2208 firmware
≤ 3.50
phoenixcontact
fl switch 2207-fx sm firmware
≤ 3.50
phoenixcontact
fl switch 2207-fx firmware
≤ 3.50
+59 more product configuration(s) — see NVD for full list

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • IA-5 Authenticator Management
  • AC-7 Unsuccessful Logon Attempts
  • AC-3 Access Enforcement
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V11.4.2

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly requires organizations to manage authenticators (including passwords) using strong generation algorithms and secure distribution, eliminating the weak password generation flaw that enables the brute-force attack.

prevent

Enforces limits on consecutive invalid logon attempts against the root/user OS accounts, directly blocking the remote brute-force technique described in the CVE.

prevent

Enforces access decisions only after successful authentication, ensuring the weak OS passwords cannot be used to gain unauthorized system-level access even if guessed.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.DS-01 mostly match
prevents

Proper password hashing is a direct instance of using cryptographic hashes to protect data-at-rest.

PR.PS-06 mostly match
prevents

Secure development practices explicitly include selection and configuration of strong, computationally expensive password hashes.

PR.AA-03 partial match
prevents

Authentication policies may reference password handling but do not address storage or computational cost of hashes.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

degrades

Requires secure handling of authentication information, which includes choosing strong password hashing schemes.

prevents

Requires appropriate use of cryptography, which encompasses selecting strong hashing algorithms for passwords.

prevents

Secure coding practices include implementing password storage with adequate computational effort.

degrades

Mandates secure authentication mechanisms, directly addressing the need for computationally strong password hashes.

References