CVE-2022-31482
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 unauthenticated HTTP request 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.29. The overflowed data leads to segmentation fault and ultimately a denial-of-service condition, causing the device to reboot. The impact of this vulnerability is that an unauthenticated attacker could leverage this flaw to cause the target device to become unresponsive. An attacker could automate this attack to achieve persistent DoS, effectively rendering the target controller useless.
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 confidenceBuffer overflow vulnerability in HID Mercury Intelligent Controllers (LP1501, LP1502, LP2500, LP4502, EP4502) firmware versions prior to 1.29 allows unauthenticated attackers to send specially crafted HTTP requests that overflow a buffer, causing a segmentation fault and device reboot (DoS).
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.29< 1.29< 1.29< 1.29< 1.29< 1.29< 1.29< 1.29CVSS 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 the controller modelAccess the controller's web interface or check the device label to determine if the model is one of: LP1501, LP1502, LP2500, LP4502, EP4502, LNL-4420, LNL-X2210, or LNL-X2220.Affected if The model matches one of the listed affected products.
-
Check the installed firmware versionLog into the controller's web management interface and navigate to the System Info or Firmware version page. Alternatively, use the controller's CLI or management software to query the firmware version.Affected if The firmware version is lower than 1.29.
-
Verify HTTP service is enabledCheck the controller's network settings or service configuration to confirm the HTTP management interface is enabled.Affected if HTTP service is enabled on the device.
-
Assess network exposure of HTTP interfaceReview firewall rules, network segmentation, and access control lists to determine if the controller's HTTP port (typically port 80) is accessible from untrusted networks or the internet.Affected if The HTTP interface is exposed to untrusted or public networks without proper access controls.
You are affected if your controller model is one of the listed products and the firmware version is below 1.29, with the HTTP interface accessible to potential 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.29
Update affected controller firmware to version 1.29 or later to remediate this vulnerability.
Firmware version 1.29 (or any version >= 1.29)
- 1. Identify the specific model number (LP1501, LP1502, LP2500, LP4502, EP4502, LNL-4420, LNL-X2210, or LNL-X2220) of the affected HID Mercury Intelligent Controller.
- 2. Access the device management interface and verify the current firmware version is below 1.29.
- 3. Obtain the fixed firmware version 1.29 or later from LenelS2 or Carrier's official support portal (www.corporate.carrier.com).
- 4. Review the device's firmware upgrade documentation for prerequisites and procedures.
- 5. Back up the current device configuration if the upgrade process supports configuration preservation.
- 6. Upload and apply firmware version 1.29 or later following the vendor's documented upgrade procedure.
- 7. After upgrade, verify the device is operational and confirm the new firmware version is 1.29 or higher.
- 8. Test basic functionality to ensure the device is responsive and the HTTP service is functioning normally.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31482 — 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-31482 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