dbcve.org
C520 FirmwareOperating system · Lenze

CVE-2022-2302

CRITICAL · 9.8 CVSS v3.1 Published 2022-07-11
Fix available
A fix is available. Upgrade to 01.08.01.3021 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Multiple Lenze products of the cabinet series skip the password verification upon second login. After a user has been logged on to the device once, a remote attacker can get full access without knowledge of the password.

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 · high confidence

Authentication bypass vulnerability in Lenze cabinet series devices where password verification is skipped after a user's first successful login. A remote attacker who can reach the device can gain full administrative access without knowing the password, exploiting the flawed session or re-authentication logic.

MitigationIsolate affected devices on restricted network segments; contact Lenze for firmware patches; implement network monitoring for unauthorized access attempts as compensating control until vendor fix is available.

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
C520 FirmwareOperating system
Affected:>= 1.07.00.2757, < 01.08.01.3021
C550 FirmwareOperating system
Affected:>= 1.07.00.2757, < 01.08.01.3021
C750 FirmwareOperating system
Affected:>= 1.07.00.2757, < 01.08.01.3021

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Lenze device model
    Locate the device labeling or access the device management interface to confirm the model number is C520, C550, or C750
    Affected if The device is a Lenze C520, C550, or C750 cabinet controller
  2. Determine the installed firmware version
    Access the device firmware or system information page (typically found in the web interface under System > Info or similar), or use the device's built-in diagnostic menu to retrieve the firmware version string
    Affected if The firmware version is >= 1.07.00.2757 AND < 01.08.01.3021
  3. Verify if web-based or remote management interface is enabled
    Check the device network configuration settings to confirm whether the HTTP/HTTPS web interface or any remote management protocol is accessible over the network
    Affected if Remote management or web interface is exposed on the network
  4. Review active administrative sessions
    In the device web interface, navigate to the session management or user status page to list currently logged-in administrative accounts
    Affected if Multiple admin sessions exist or unexpected admin accounts are active without proper re-authentication

You are affected if the device is a Lenze C520/C550/C750 with firmware between 1.07.00.2757 and 01.08.01.3021 and remote management is enabled, as the password verification bypass allows unauthenticated admin access after the first login.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 01.08.01.3021 or later
Fixed in 01.08.01.3021
Interim mitigation

Isolate affected devices on restricted network segments; contact Lenze for firmware patches; implement network monitoring for unauthorized access attempts as compensating control until vendor fix is available.

Recommended fix High confidence

Firmware version 01.08.01.3021 or later for C520, C550, and C750

  1. Identify the specific model (C520, C550, or C750) in use
  2. Access the device management interface or use Lenze's update tools to check the current firmware version
  3. Download the fixed firmware version 01.08.01.3021 or later from Lenze's official support website (cert.vde.com or lenze.com)
  4. Review Lenze's firmware upgrade documentation for your specific model
  5. Perform the firmware upgrade following Lenze's official procedures, ensuring stable power during the process
  6. After upgrade, verify the new firmware version is installed
  7. Test that the password authentication mechanism works correctly for all login attempts
  8. Ensure default credentials have been changed from factory defaults

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in C520 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-2302 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-2302 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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