# CVE-2022-22509: PHOENIX CONTACT: FL SWITCH 2xxx series incorrect privilege assignment

> A low-privileged user can escalate privileges to gain full access to the configuration of Phoenix Contact FL SWITCH 2xxx series devices.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Feb 2022
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-rh2h-p77p-xw9h

## What is CVE-2022-22509?

CVE-2022-22509 is a high-severity vulnerability in n/a, published on 2 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Phoenix Contact FL SWITCH Series 2xxx in version 3.00 an incorrect privilege assignment allows an low privileged user to enable full access to the device configuration.

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 65 products.


Products: Phoenixcontact Fl Switch 2005 Firmware, Phoenixcontact Fl Switch 2008 Firmware, Phoenixcontact Fl Switch 2008f Firmware, Phoenixcontact Fl Switch 2016 Firmware, Phoenixcontact Fl Switch 2105 Firmware, Phoenixcontact Fl Switch 2108 Firmware, Phoenixcontact Fl Switch 2116 Firmware, Phoenixcontact Fl Switch 2204-2tc-2sfx Firmware, Phoenixcontact Fl Switch 2205 Firmware, Phoenixcontact Fl Switch 2206-2fx Firmware, Phoenixcontact Fl Switch 2206-2fx Sm Firmware, Phoenixcontact Fl Switch 2206-2fx Sm St Firmware, Phoenixcontact Fl Switch 2206-2fx St Firmware, Phoenixcontact Fl Switch 2206-2sfx Firmware, Phoenixcontact Fl Switch 2206-2sfx Pn Firmware, Phoenixcontact Fl Switch 2206c-2fx Firmware, Phoenixcontact Fl Switch 2207-Fx Firmware, Phoenixcontact Fl Switch 2207-Fx Sm Firmware, Phoenixcontact Fl Switch 2208 Firmware, Phoenixcontact Fl Switch 2208 Pn Firmware and 45 more.

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

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

## Is CVE-2022-22509 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-22509 is a high-severity vulnerability in n/a, published on 2 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-22509 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-22509/ (Markdown: https://insights.sbomify.com/CVE-2022-22509/index.md)
```

## Sources

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

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