CVE-2022-31486
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 authenticated attacker can send a specially crafted route to the “edit_route.cgi” binary and have it execute shell commands. This vulnerability impacts products based on HID Mercury Intelligent Controllers LP1501, LP1502, LP2500, LP4502, and EP4502 which contain firmware versions prior to 1.303 for the LP series and 1.297 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.
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 confidenceAuthenticated command injection vulnerability in the edit_route.cgi binary on HID Mercury Intelligent Controllers (LP1501, LP1502, LP2500, LP4502, EP4502). Attackers with valid credentials can send specially crafted route parameters that allow arbitrary shell command execution on 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.303< 1.303< 1.303< 1.303< 1.297< 1.297< 1.303< 1.303CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify controller modelAccess the device web interface or check system information page to identify the exact model (LP1501, LP1502, LP2500, LP4502, EP4502, LNL-4420, LNL-X2210, or LNL-X2220)Affected if Model matches any of the affected products listed in the CVE
-
Check firmware versionNavigate to the web interface System or About page to view the installed firmware version. Compare against affected versions: LP series and X2210/X2220 < 1.303, EP series and LNL-4420 < 1.297Affected if Installed firmware version is lower than the affected threshold for your specific model
-
Verify edit_route.cgi is accessibleAttempt to access the edit_route.cgi endpoint via HTTP/HTTPS on the device (e.g., https://<device-ip>/edit_route.cgi)Affected if The CGI script is accessible and responds to requests (indicates the management interface is enabled)
-
Confirm remote management exposureCheck network configuration to determine if the device management interface is exposed to untrusted networks (check firewall rules, NAT settings, or VLAN configuration)Affected if Port 80/443 or management interface is reachable from untrusted networks
You are affected if your controller model matches one of the vulnerable models AND your installed firmware version is below the threshold (LP/X series < 1.303, EP/LNL-4420 < 1.297) AND the management interface is network-accessible.
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.2971.303
Upgrade firmware to version 1.303 or later for LP series controllers and version 1.297 or later for EP series controllers. If immediate patching is not possible, restrict network access to the management interface and monitor for suspicious activity.
LP series to firmware >= 1.303; EP series and Lnl 4420 to firmware >= 1.297; Lnl X2210/X2220 to firmware >= 1.303
- 1. Identify the specific HID Mercury Intelligent Controller model (LP1501, LP1502, LP2500, LP4502, EP4502, Lnl 4420, Lnl X2210, or Lnl X2220) in your environment.
- 2. Access the device administrative interface or console.
- 3. Backup the current device configuration before performing any firmware update.
- 4. Download the firmware update from the official Carrier/Carrier Enterprise portal or LenelS2 support channels.
- 5. For LP series devices (LP1501, LP1502, LP2500, LP4502), upgrade to firmware version 1.303 or later.
- 6. For EP series devices (EP4502), upgrade to firmware version 1.297 or later.
- 7. For LenelS2 controllers (Lnl 4420, Lnl X2210, Lnl X2220), apply the corresponding fixed firmware versions (1.297 for Lnl 4420, 1.303 for X2210/X2220).
- 8. Verify the firmware upgrade was successful by checking the firmware version in the device interface.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2022-31486 — 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-31486 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