CVE-2022-22509
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is a privilege escalation vulnerability in Phoenix Contact FL SWITCH Series 2xxx devices version 3.00 where an incorrect privilege assignment mechanism allows a low-privileged user to elevate their own access rights and gain full administrative control over the device configuration.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 3.00= 3.00= 3.00= 3.00= 3.00= 3.00= 3.00= 3.00CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify device modelAccess the device web interface, CLI, or management console and retrieve the exact model name/number from the system information or device status pageAffected if The model matches any of these: FL SWITCH 2005, FL SWITCH 2008, FL SWITCH 2008f, FL SWITCH 2016, FL SWITCH 2105, FL SWITCH 2108, FL SWITCH 2116, or FL SWITCH 2204 2tc 2sfx
-
Check firmware versionIn the device management interface, navigate to System > Firmware, System > Information, or run the command that displays firmware version (commonly 'show firmware' or similar)Affected if The firmware version displayed is exactly 3.00
-
Verify user management configurationAccess the user management, access control, or accounts configuration section in the device web interface or CLI and list all configured users and their assigned privilege levelsAffected if Multiple user accounts exist with different privilege levels (such as user, operator, admin) and the system allows low-privilege users to modify their own access rights
-
Check for privilege assignment capabilityLog in with a low-privilege account (or create one if not present) and attempt to access or modify privilege-related settings, or examine the user role configuration files if accessible via CLIAffected if A low-privilege user can elevate their own account privileges or modify role assignments without proper administrative authentication
You are affected if your device is one of the FL SWITCH 2xxx models listed and is running firmware version 3.00, especially if multiple user accounts with different privilege levels are configured.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor-provided firmware patch when available; until then, restrict network access to the device management interfaces to trusted administrators only and monitor for unauthorized configuration changes.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22509 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-22509 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data