CVE-2023-22618
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 · uneditedIf Security Hardening guide rules are not followed, then Nokia WaveLite products allow a local user to create new users with administrative privileges by manipulating a web request. This affects (for example) WaveLite Metro 200 and Fan, WaveLite Metro 200 OPS and Fans, WaveLite Metro 200 and F2B fans, WaveLite Metro 200 OPS and F2B fans, WaveLite Metro 200 NE and F2B fans, and WaveLite Metro 200 NE OPS and F2B fans.
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 confidenceLocal authenticated users can manipulate web requests on Nokia WaveLite Metro 200 devices to create new administrative users when security hardening guidelines are not followed, enabling privilege escalation from standard user to administrator.
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< r2.1.1< r2.1.1< r2.1.1< r2.1.1< r2.1.1< r2.1.1CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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.
-
Verify firmware versionAccess the device's web management interface or use SNMP to retrieve the firmware version. Look for a version string such as r2.1.0, r2.0.x, or earlier. Compare this version against the affected range.Affected if The firmware version is r2.1.0 or any version earlier than r2.1.1
-
Confirm web management interface is enabledAttempt to access the device's web interface on the standard HTTP/HTTPS ports (typically 80 or 443). Check the device configuration to see if the web-based management feature is turned on.Affected if The web management interface is accessible and enabled on the device
-
Identify user account privilegesLog into the web interface with a standard (non-administrator) user account. Navigate to the user management or administration section to see if standard users have the ability to add, modify, or delete user accounts.Affected if Standard (non-privileged) user accounts can access functions to create or modify user accounts, including administrative-level accounts
-
Check for security hardening configurationReview the device's security settings for authentication and authorization controls. Look for configuration options related to user role permissions, access control lists, or privilege escalation protections.Affected if Security hardening guidelines have not been applied, or authentication/authorization controls allow standard users to elevate privileges to administrator level
A user is affected if the device runs firmware version r2.1.0 or earlier, has the web management interface enabled, and allows standard users to create or modify administrative accounts without proper security hardening applied.
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.
dbcve · scopedApply Nokia's Security Hardening guide rules to properly configure authentication and authorization controls on affected WaveLite devices to prevent unauthorized privilege escalation.
r2.1.1
- Identify the specific WaveLite Metro 200 variant (Metro 200, Metro 200 OPS, Metro 200 NE, or Metro 200 NE OPS) and fan type (Fan, Fans, or F2B fans) currently deployed
- Access the device management interface through the web console
- Navigate to the firmware management or system settings section
- Download the firmware version r2.1.1 or later from the official Nokia support portal
- Upload and apply the r2.1.1 firmware to the device
- After firmware upgrade, verify the new firmware version is installed
- If the web request manipulation vulnerability persists, ensure security hardening guide rules are applied per Nokia documentation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation10.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,104.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22618 — 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-2023-22618 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