CVE-2022-31480
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 could arbitrarily upload firmware files to the target device, ultimately causing a Denial-of-Service (DoS). 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 attacker needs to have a properly signed and encrypted binary, loading the firmware to the device ultimately triggers a reboot.
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 confidenceUnauthenticated arbitrary firmware upload vulnerability in HID Mercury Intelligent Controllers allows attackers to upload specially crafted signed/encrypted firmware images without authentication. Loading the malicious firmware triggers a device reboot, causing Denial-of-Service. Affected devices include LP1501, LP1502, LP2500, LP4502 (firmware <1.302) and EP4502 (firmware <1.296).
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify HID Mercury or Carrier Lenels2 controllers in your environmentReview network documentation, asset inventory, or physically inspect controllers to determine if LP1501, LP1502, LP2500, LP4502, EP4502, Lnl 4420, Lnl X2210, or Lnl X2220 models are presentAffected if Any of these model numbers are found in your environment
-
Locate the firmware version for each identified controllerAccess the controller admin interface or use the vendor management software to view the installed firmware version; consult controller documentation for the specific command or menu pathAffected if Unable to determine firmware version for any controller in scope
-
Compare installed firmware version against affected rangesFor LP series (LP1501, LP1502, LP2500, LP4502) and Lnl X2210/X2220, check if version is below 1.302; for EP4502 and Lnl 4420, check if version is below 1.296Affected if The installed firmware version falls below the specified thresholds for your model
-
Verify firmware upload interface accessibilityConfirm that the controller firmware upload/update feature is exposed on the network or accessible without requiring authentication, as the vulnerability allows unauthenticated uploadsAffected if The firmware upload interface is network-accessible without authentication
If you have any LP1501, LP1502, LP2500, LP4502, EP4502, Lnl 4420, Lnl X2210, or Lnl X2220 controllers running firmware below 1.302 (LP series, X2210, X2220) or below 1.296 (EP4502, Lnl 4420), your environment is affected by this unauthenticated firmware upload vulnerability.
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
Upgrade firmware to version 1.302 or later for LP series and 1.296 or later for EP series. Identify all affected controllers in the environment and schedule controlled firmware updates following vendor procedures.
LP series (LP1501, LP1502, LP2500, LP4502, X2210, X2220): Firmware >= 1.302 | EP series (EP4502, Lnl 4420): Firmware >= 1.296
- 1. Identify the specific model number (LP1501, LP1502, LP2500, LP4502, EP4502, Lnl 4420, Lnl X2210, or Lnl X2220) of the affected HID Mercury controller
- 2. For LP series controllers (LP1501, LP1502, LP2500, LP4502) and X2210/X2220: upgrade firmware to version 1.302 or later
- 3. For EP series controllers (EP4502) and Lnl 4420: upgrade firmware to version 1.296 or later
- 4. Obtain the firmware from the official Lenel/S2 or Carrier support portal at corporate.carrier.com
- 5. Follow the vendor's documented firmware upgrade procedure, ensuring proper handling of the signed and encrypted binary
- 6. After upgrade, verify the firmware version matches the target fixed release
- 7. Confirm the device returns to normal operation after the firmware update process completes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31480 — 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-31480 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