CVE-2022-31481
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 · uneditedAn unauthenticated attacker can send a specially crafted update file to the device that can overflow a buffer. 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. The overflowed data can allow the attacker to manipulate the “normal” code execution to that of their choosing. 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.
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 confidenceAn unauthenticated attacker can send a specially crafted firmware update file to HID Mercury Intelligent Controllers (LP1501, LP1502, LP2500, LP4502, EP4502) that triggers a buffer overflow. This allows arbitrary code execution, enabling the attacker to monitor communications, manipulate relays, modify configurations, or destabilize the device.
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< 1.302< 1.302< 1.302< 1.302< 1.296< 1.296< 1.302< 1.302CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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.
-
Identify controller modelAccess the controller's web interface, administrative console, or use SNMP/network discovery to determine the exact model (LP1501, LP1502, LP2500, LP4502, EP4502, LNL-4420, LNL-X2210, or LNL-X2220)Affected if Model matches one of the affected products listed in the CVE
-
Determine installed firmware versionCheck the firmware version displayed in the controller's web interface under System Information, Device Status, or similar. Alternatively, check via administrative software or SNMP if availableAffected if Firmware version is lower than 1.302 for LP series/LNL-X2210/LNL-X2220, or lower than 1.296 for EP4502/LNL-4420
-
Verify network exposure of firmware update interfaceCheck network configuration to determine if the controller's management interface or firmware update port (typically HTTP/HTTPS admin ports) is accessible from untrusted networks or the internetAffected if The firmware update interface is exposed to untrusted networks (unauthenticated attackers require network access to send malicious firmware)
A user is affected if their controller model matches one of the listed products AND the installed firmware version is below the specified threshold for that model, AND the device is network-accessible to unauthenticated attackers.
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 · scoped1.2961.302
Update firmware to version 1.302 for LP series or 1.296 for EP series. Verify the update in a staging environment before production deployment, as these controllers manage physical security functions.
LP series to firmware >= 1.302; EP series to firmware >= 1.296
- Identify the specific model (LP1501, LP1502, LP2500, LP4502, EP4502, Lnl 4420, Lnl X2210, or Lnl X2220) from the device label or management interface
- Locate the current firmware version in the device administration interface or system documentation
- Download the firmware update from the official Carrier/Corporate.carrier.com support portal or LenelS2 authorized distribution channel
- For LP series controllers (LP1501, LP1502, LP2500, LP4502): upgrade to firmware version 1.302 or later
- For EP series controllers (EP4502, Lenels2 Lnl 4420): upgrade to firmware version 1.296 or later
- For Lenels2 Lnl X2210 and X2220: upgrade to firmware version 1.302 or later
- Apply the firmware update via the device's firmware upload/update feature, following the vendor's documented upgrade procedure
- Verify the firmware version has been successfully updated after the process completes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing16.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,576.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31481 — 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-2022-31481 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