Skip to content
Fencer Vulns
critical 9.8

CVE-2022-32985 json

libnx_apl.so on Nexans FTTO GigaSwitch before 6.02N and 7.x before 7.02 implements a Backdoor Account for SSH logins on port 50200 or 50201.

published 2022-07-17 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-36051

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.3%
EPSS 1.3% chance of exploitation in 30 days, percentile 69%
public exploits
0
none known

Summary

libnx_apl.so on Nexans FTTO GigaSwitch before 6.02N and 7.x before 7.02 implements a Backdoor Account for SSH logins on port 50200 or 50201.

Patch / fix

  • nexans gigaswitch_641_desk_v5_sfp-vi_firmware 6.02n, 7.02
  • nexans gigaswitch_642_desk_v5_sfp-2vi_firmware 6.02n, 7.02
  • nexans gigaswitch_v5_2tp(pd-f+)_sfp-vi_54vdc_firmware 6.02n, 7.02
  • nexans gigaswitch_v5_2tp(pse+)_sfp-vi_54vdc_firmware 6.02n, 7.02
  • nexans gigaswitch_v5_2tp_sfp-vi_54vdc_firmware 6.02n, 7.02
  • nexans gigaswitch_v5_sfp-2vi_230vac_firmware 6.02n, 7.02
  • nexans gigaswitch_v5_tp(pse+)_sfp-2vi_54vdc_firmware 6.02n, 7.02
  • nexans gigaswitch_v5_tp(pse+)_sfp-2vi_54vdc_ind_firmware 6.02n, 7.02
  • nexans gigaswitch_v5_tp(pse+)_sfp-2vi_54vdc_med_firmware 6.02n, 7.02
  • nexans gigaswitch_v5_tp_sfp-2vi_54vdc_firmware 6.02n, 7.02
  • nexans gigaswitch_v5_tp_sfp-2vi_54vdc_ind_firmware 6.02n, 7.02
  • nexans gigaswitch_v5_tp_sfp-2vi_54vdc_med_firmware 6.02n, 7.02
  • nexans gigaswitch_v5_tp_sfp-vi_230vac_firmware 6.02n, 7.02

Exploit prediction

1.26% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • sec-consult.com https://sec-consult.com/vulnerability-lab/advisory/hardcoded-backdoor-user-outdated-software-components-nexans-ftto-gigaswitch/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Classification

Weakness
  • CWE-798 Use of Hard-coded Credentials

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.