dbcve.org
Lp1501 FirmwareOperating system · Hidglobal

CVE-2022-31484

HIGH · 7.5 CVSS v3.1 Published 2022-06-06
Fix available
A fix is available. Upgrade to 1.29 or later.
See remediation →
84/100
Remediation priority · High
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
An unauthenticated attacker can send a specially crafted network packet to delete a user from the web interface. This vulnerability impacts products based on HID Mercury Intelligent Controllers LP1501, LP1502, LP2500, LP4502, and EP4502 which contain firmware versions prior to 1.29. The impact of this vulnerability is that an unauthenticated attacker could restrict access to the web interface to legitimate users and potentially requiring them to use the default user dip switch procedure to gain access back.

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

The vulnerability allows unauthenticated attackers to send specially crafted network packets to HID Mercury Intelligent Controllers (LP1501, LP1502, LP2500, LP4502, EP4502) that can delete users from the web interface. This is a pre-authentication flaw in firmware versions prior to 1.29.

MitigationUpgrade affected controllers to firmware version 1.29 or later to patch the vulnerability.

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
Lp1501 FirmwareOperating system
Affected:< 1.29
Lp1502 FirmwareOperating system
Affected:< 1.29
Lp2500 FirmwareOperating system
Affected:< 1.29
Lp4502 FirmwareOperating system
Affected:< 1.29
Ep4502 FirmwareOperating system
Affected:< 1.29
Lenels2 Lnl 4420 FirmwareOperating system
Affected:< 1.29
Lenels2 Lnl X2210 FirmwareOperating system
Affected:< 1.29
Lenels2 Lnl X2220 FirmwareOperating system
Affected:< 1.29

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 controller model
    Access the controller's web interface or administrative console and locate the device information or system status page to identify the exact model number (e.g., LP1501, LP2500, LNL 4420)
    Affected if The model is one of: LP1501, LP1502, LP2500, LP4502, EP4502, LNL 4420, LNL X2210, or LNL X2220
  2. Check the installed firmware version
    Within the controller's web interface or administrative console, navigate to the firmware version, system information, or about section to determine the currently installed firmware build
    Affected if The firmware version is below 1.29 (for example, 1.28.x or earlier)
  3. Verify network accessibility of the web interface
    Determine whether the controller's web management interface is accessible from untrusted network segments or the internet by reviewing network configuration, firewall rules, or by attempting to reach the web interface IP address
    Affected if The web interface is exposed to network segments accessible by unauthenticated attackers

The environment is affected if the controller model matches one of the vulnerable models (LP1501, LP1502, LP2500, LP4502, EP4502, LNL 4420, LNL X2210, LNL X2220) AND the installed firmware version is below 1.29, especially if the web interface is network-accessible to untrusted users.

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 1.29 or later
Fixed in 1.29
Interim mitigation

Upgrade affected controllers to firmware version 1.29 or later to patch the vulnerability.

Recommended fix High confidence

Firmware version 1.29

  1. Download the firmware version 1.29 or later from the vendor's official support portal at www.corporate.carrier.com
  2. Review the firmware upgrade documentation for your specific model (LP1501, LP1502, LP2500, LP4502, EP4502, Lnl 4420, Lnl X2210, or Lnl X2220)
  3. Ensure the controller is powered and connected to the network
  4. Access the controller's web interface or management console
  5. Upload the firmware file and initiate the upgrade process
  6. Verify the firmware version after upgrade confirms version 1.29 or later
  7. Test that the web interface is accessible and user management functions work correctly
Caveat Firmware upgrades may temporarily disrupt controller connectivity; ensure backup configuration and maintenance window are in place

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

Fix this in Lp1501 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-31484 — 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-31484 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