CVE-2022-3086
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 · uneditedCradlepoint IBR600 NCOS versions 6.5.0.160bc2e and prior are vulnerable to shell escape, which enables local attackers with non-superuser credentials to gain full, unrestrictive shell access which may allow an attacker to execute arbitrary code.
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 · moderate confidenceCradlepoint IBR600 NCOS versions 6.5.0.160bc2e and prior contain a shell escape vulnerability that allows local attackers with non-superuser credentials to gain unrestricted shell access and execute arbitrary code on the affected router 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.1= 1.1= 1.1= 1.1= 1.1= 1.1>= 1.0, <= 1.2>= 1.0, <= 1.2CVSS 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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/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 the Moxa device modelAccess the device web interface or CLI and run 'show system info' or 'get system' to retrieve the hardware model number. Confirm it is one of: UC-8580, UC-8580-T, UC-8580-T-CT, UC-8580-T-Q, UC-8580-T-CT-Q, UC-8580-Q, UC-8540, or UC-8540-T-CT.Affected if The device model matches one of the listed Moxa UC-8580 or UC-8540 series variants.
-
Check the firmware versionIn the device CLI or web interface, run 'show version' or navigate to System Settings > Firmware Version to obtain the installed firmware version number.Affected if The firmware version is exactly 1.1 for UC-8580 series models, or between 1.0 and 1.2 inclusive for UC-8540 series models.
-
Verify local user account configurationCheck if local user accounts exist on the device by reviewing the user database via 'show users' or examining the device authentication settings in the web interface under User Management or Access Control.Affected if Local user accounts with shell or CLI access are configured on the device.
-
Confirm shell or CLI access method availabilityDetermine whether the device permits shell or CLI access for non-superuser accounts via serial console, SSH, or telnet by reviewing access methods in Security or Access settings.Affected if Non-superuser accounts can access the device shell or CLI through any enabled access method.
The device is affected if it is a Moxa UC-8580 or UC-8540 series model running firmware version 1.1 (UC-8580) or firmware version 1.0-1.2 (UC-8540) and local non-superuser accounts have shell or CLI access.
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.
From vendor dataUpgrade the Cradlepoint IBR600 firmware to a version beyond 6.5.0.160bc2; if immediate upgrade is not feasible, restrict physical and local network access to the device to limit attack surface.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3086 — 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-3086 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