dbcve.org
Lp1501 FirmwareOperating system · Hidglobal

CVE-2022-31485

MEDIUM · 5.3 CVSS v3.1 Published 2022-06-06
Fix available
A fix is available. Upgrade to 1.29 or later.
See remediation →
62/100
Remediation priority · Elevated
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 packets to update the “notes” section of the home page of 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.

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

An unauthenticated attacker can send specially crafted packets to update the notes section of the web interface on HID Mercury Intelligent Controllers (LP1501, LP1502, LP2500, LP4502, EP4502). This allows unauthorized modification of the home page content without authentication on devices running firmware versions prior to 1.29.

MitigationUpdate affected Mercury controller firmware to version 1.29 or later to remediate this 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
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

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 Mercury controller model
    Access the device web interface or check the physical device label. Look for model numbers: LP1501, LP1502, LP2500, LP4502, EP4502, LNL 4420, LNL X2210, or LNL X2220.
    Affected if The model is any of LP1501, LP1502, LP2500, LP4502, EP4502, LNL 4420, LNL X2210, or LNL X2220.
  2. Check the installed firmware version
    Log into the web interface and navigate to the About or System Information page. Alternatively, use the CLI via SSH/Telnet and run the 'show version' or 'firmware version' command.
    Affected if The firmware version displayed is less than 1.29.
  3. Confirm web interface is accessible
    Attempt to reach the device web interface over HTTP/HTTPS on the expected management IP address.
    Affected if The web interface is reachable on the network.
  4. Verify the notes/homepage feature exists
    Access the web interface and locate the notes or homepage content editing section. This is typically found in the system settings or dashboard area.
    Affected if The notes editing feature is present and accessible without authentication.

If the device model is one of the affected Mercury controllers (LP1501, LP1502, LP2500, LP4502, EP4502, LNL 4420, LNL X2210, LNL X2220) and the firmware version is below 1.29, the environment is vulnerable to unauthenticated modification of web interface notes.

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

Update affected Mercury controller firmware to version 1.29 or later to remediate this vulnerability.

Recommended fix High confidence

Firmware version 1.29 for LP1501, LP1502, LP2500, LP4502, EP4502, Lnl 4420, Lnl X2210, and Lnl X2220

  1. 1. Identify the specific model of the affected HID Mercury Intelligent Controller (LP1501, LP1502, LP2500, LP4502, EP4502, Lnl 4420, Lnl X2210, or Lnl X2220) in your environment
  2. 2. Download the firmware version 1.29 or later from the official Lenel/Carrier support portal at www.corporate.carrier.com
  3. 3. Review the firmware upgrade instructions provided by Lenel to ensure proper upgrade procedure
  4. 4. Schedule a maintenance window as firmware updates may require downtime
  5. 5. Backup current controller configuration before performing the upgrade
  6. 6. Apply firmware version 1.29 or later to the affected controller(s)
  7. 7. Verify the upgrade was successful by checking the firmware version in the web interface
  8. 8. Confirm the 'notes' section can no longer be modified without authentication
Caveat Firmware upgrades may temporarily disrupt access control operations; ensure proper change management procedures are followed

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
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
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,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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