dbcve.org
Lp1501 FirmwareOperating system · Hidglobal

CVE-2022-31479

CRITICAL · 9.8 CVSS v3.1 Published 2022-06-06
Fix available
A fix is available. Upgrade to 1.296 / 1.302 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
An unauthenticated attacker can update the hostname with a specially crafted name that will allow for shell commands to be executed during the core collection process. This vulnerability impacts products based on HID Mercury Intelligent Controllers LP1501, LP1502, LP2500, LP4502, and EP4502 which contain firmware versions prior to 1.302 for the LP series and 1.296 for the EP series. An attacker with this level of access on the device can monitor all communications sent to and from this device, modify onboard relays, change configuration files, or cause the device to become unstable. The injected commands only get executed during start up or when unsafe calls regarding the hostname are used. This allows the attacker to gain remote access to the device and can make their persistence permanent by modifying the filesystem.

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

This is a command injection vulnerability in HID Mercury intelligent controllers where an unauthenticated attacker can inject shell commands through a specially crafted hostname value. The injected commands execute during the core collection process at device startup or when unsafe calls regarding the hostname are used, allowing remote code execution with elevated privileges.

MitigationUpgrade firmware to version 1.302 or later for LP series devices and 1.296 or later for EP series devices. Until patching is feasible, implement network segmentation and restrict access to the device management interface to minimize exposure.

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.302
Lp1502 FirmwareOperating system
Affected:< 1.302
Lp2500 FirmwareOperating system
Affected:< 1.302
Lp4502 FirmwareOperating system
Affected:< 1.302
Ep4502 FirmwareOperating system
Affected:< 1.296
Lenels2 Lnl 4420 FirmwareOperating system
Affected:< 1.296
Lenels2 Lnl X2210 FirmwareOperating system
Affected:< 1.302
Lenels2 Lnl X2220 FirmwareOperating system
Affected:< 1.302

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 device model
    Locate the physical HID Mercury controller or check network inventory for Mercury intelligent controllers (LP1501, LP1502, LP2500, LP4502, EP4502) or Carrier Lenels2 models (LNL 4420, LNL X2210, LNL X2220). Inspect the device label or query SNMP/network scan results for the model identifier.
    Affected if The device is one of the listed models: Hidglobal Lp1501, Lp1502, Lp2500, Lp4502, Ep4502 or Carrier Lenels2 Lnl 4420, Lnl X2210, Lnl X2220.
  2. Check the installed firmware version
    Access the device management interface (web UI or CLI) and navigate to the system information or firmware version page. Alternatively, use SNMP or the controller's API to query the firmware version. Compare the version number against the affected ranges.
    Affected if Firmware version is below 1.302 for LP series (Lp1501, Lp1502, Lp2500, Lp4502) or below 1.296 for EP series (Ep4502) and Lenels2 models (Lnl 4420 requires <1.296; Lnl X2210 and Lnl X2220 require <1.302).
  3. Verify if hostname configuration is accessible
    Check whether the device management interface exposes hostname configuration options. This typically appears in network settings, system configuration, or device identification settings. Determine if this interface is reachable over the network.
    Affected if The hostname configuration interface is exposed and accessible, as the command injection occurs through specially crafted hostname values.
  4. Assess network exposure
    Review firewall rules, access control lists, and network segmentation to determine if the device management interface is reachable from untrusted networks or the internet. Check for direct exposure of ports used by the controller (typically HTTP/HTTPS for web interface).
    Affected if The device management interface is accessible from untrusted networks without proper network segmentation or access restrictions.

The environment is affected if an HID Mercury or Carrier Lenels2 controller is running firmware versions below the specified thresholds (1.302 for LP series/X2210/X2220, 1.296 for EP series/LNL 4420) and the hostname configuration interface is network-accessible.

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.296 / 1.302 or later
Fixed in 1.2961.302
Interim mitigation

Upgrade firmware to version 1.302 or later for LP series devices and 1.296 or later for EP series devices. Until patching is feasible, implement network segmentation and restrict access to the device management interface to minimize exposure.

Recommended fix High confidence

Firmware 1.302 for LP series (LP1501, LP1502, LP2500, LP4502, X2210, X2220); Firmware 1.296 for EP series (EP4502) and Lnl 4420

  1. Identify the specific model of the HID Mercury Intelligent Controller (LP1501, LP1502, LP2500, LP4502, EP4502, Lenels2 Lnl 4420, Lenels2 Lnl X2210, or Lenels2 Lnl X2220)
  2. Obtain the firmware update from the official Carrier/Lenel support portal at www.corporate.carrier.com
  3. For LP series controllers (LP1501, LP1502, LP2500, LP4502): Upgrade firmware to version 1.302 or later
  4. For EP series controllers (EP4502): Upgrade firmware to version 1.296 or later
  5. For Lenels2 Lnl 4420: Upgrade firmware to version 1.296 or later
  6. For Lenels2 Lnl X2210 and X2220: Upgrade firmware to version 1.302 or later
  7. Verify the firmware upgrade was successful and the hostname configuration is no longer vulnerable to command injection
Caveat Physical access to controller may be required for firmware update; ensure backup of configuration before upgrading; controller may restart during update

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

Fix this in Lp1501 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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 locally
dbcve dependency scanner

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