CVE-2022-31483
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 upload a file with a filename including “..” and “/” to achieve the ability to upload the desired file anywhere on the filesystem. This vulnerability impacts products based on HID Mercury Intelligent Controllers LP1501, LP1502, LP2500, LP4502, and EP4502 which contain firmware versions prior to 1.271. This allows a malicious actor to overwrite sensitive system files and install a startup service to gain remote access to the underlaying Linux operating system with root privileges.
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 authenticated attacker can exploit a path traversal vulnerability in the file upload functionality of HID Mercury intelligent controllers by including '..' and '/' sequences in filenames. This allows uploading arbitrary files to any location on the filesystem, enabling overwriting of system files and installation of persistent startup services to gain root access to the underlying Linux OS.
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.271< 1.271< 1.271< 1.271< 1.271< 1.271< 1.271< 1.271CVSS 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 modelDetermine the exact model of the HID Mercury controller (LP1501, LP1502, LP2500, LP4502, EP4502, LNL-4420, LNL-X2210, or LNL-X2220) by checking the device label, management interface, or system documentationAffected if The model is one of: LP1501, LP1502, LP2500, LP4502, EP4502, LNL-4420, LNL-X2210, or LNL-X2220
-
Check firmware versionAccess the controller management interface or use the appropriate command (such as 'show version' or via the web UI) to retrieve the installed firmware versionAffected if The firmware version is less than 1.271 (for example, 1.260, 1.250, etc.)
-
Verify file upload feature accessCheck if the web-based management interface or API includes file upload or firmware update functionality that is accessible to authenticated usersAffected if File upload or firmware update functionality is available and accessible with authenticated credentials
You are affected if your controller model matches one of the eight listed models AND the installed firmware version is below 1.271, since the path traversal flaw exists in the file upload feature of those vulnerable versions.
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.271
Update firmware on affected LP1501, LP1502, LP2500, LP4502, and EP4502 controllers to version 1.271 or later to patch the path traversal vulnerability.
Firmware version 1.271
- 1. Identify the specific controller model (LP1501, LP1502, LP2500, LP4502, EP4502, Lenels2 Lnl 4420, Lenels2 Lnl X2210, or Lenels2 Lnl X2220) from the affected product line
- 2. Obtain the firmware version 1.271 or later from Carrier's official support website or through authorized channels
- 3. Review the firmware upgrade documentation provided by Carrier for the specific controller model
- 4. Ensure you have valid administrative credentials for the controller, as authentication is required
- 5. Perform the firmware upgrade following Carrier's documented procedures, typically via the controller's web interface or management software
- 6. After upgrade, verify the firmware version has been updated to 1.271 or later
- 7. Test that the path traversal vulnerability is no longer exploitable by attempting file upload with traversal characters (../ or similar)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31483 — 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-31483 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