# CVE-2022-32985: Hardcoded credentials in n/a

> A hardcoded backdoor account allows unauthorized SSH access to Nexans FTTO GigaSwitch devices, enabling full system compromise.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-5rg4-g8rc-v2hx

## What is CVE-2022-32985?

CVE-2022-32985 is a critical vulnerability in n/a, published on 17 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2022-32985?

It affects 13 products.


Products: Nexans Gigaswitch 641 Desk V5 Sfp-Vi Firmware, Nexans Gigaswitch 642 Desk V5 Sfp-2vi Firmware, Nexans Gigaswitch V5 2tp\(pd-F\+\) Sfp-Vi 54vdc Firmware, Nexans Gigaswitch V5 2tp\(pse\+\) Sfp-Vi 54vdc Firmware, Nexans Gigaswitch V5 2tp Sfp-Vi 54vdc Firmware, Nexans Gigaswitch V5 Sfp-2vi 230vac Firmware, Nexans Gigaswitch V5 Tp\(pse\+\) Sfp-2vi 54vdc Firmware, Nexans Gigaswitch V5 Tp\(pse\+\) Sfp-2vi 54vdc Ind Firmware, Nexans Gigaswitch V5 Tp\(pse\+\) Sfp-2vi 54vdc Med Firmware, Nexans Gigaswitch V5 Tp Sfp-2vi 54vdc Firmware, Nexans Gigaswitch V5 Tp Sfp-2vi 54vdc Ind Firmware, Nexans Gigaswitch V5 Tp Sfp-2vi 54vdc Med Firmware, Nexans Gigaswitch V5 Tp Sfp-Vi 230vac Firmware.

## How do I fix CVE-2022-32985?

No fix has been published for CVE-2022-32985 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-32985 being exploited?

There is no known exploitation of CVE-2022-32985 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-32985 and fix it if it is affected.

What it is: CVE-2022-32985 is a critical vulnerability in n/a, published on 17 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-32985 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-32985/ (Markdown: https://insights.sbomify.com/CVE-2022-32985/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-32985
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-32985
- OSV: https://osv.dev/vulnerability/CVE-2022-32985

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-32985/
Summaries are generated and may contain mistakes; the official description above is the record.