CVE-2022-31808
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 · uneditedA vulnerability has been identified in SiPass integrated AC5102 (ACC-G2) (All versions < V2.85.44), SiPass integrated ACC-AP (All versions < V2.85.43). Affected devices improperly sanitize user input on the telnet command line interface. This could allow an authenticated user to escalate privileges by injecting arbitrary commands that are executed 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 confidenceThe vulnerability is a command injection issue in the telnet CLI of SiPass integrated access control devices (AC5102 and ACC-AP). An authenticated attacker can inject arbitrary OS commands through unsanitized user input, which are then executed with root privileges, enabling full system compromise.
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< 2.85.43< 2.85.44CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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 the SiPass device modelCheck the device label, web interface, or system information to confirm whether the unit is an AC5102 (ACC G2) or ACC-AP model.Affected if The device is a SiPass integrated AC5102 or ACC-AP access control unit.
-
Check the installed firmware versionAccess the device web interface or use the CLI to retrieve the firmware version. For web interface, look under System > About or similar. Compare the version number against 2.85.44 for AC5102 or 2.85.43 for ACC-AP.Affected if AC5102 firmware is below V2.85.44 or ACC-AP firmware is below V2.85.43.
-
Verify telnet service statusCheck if port 23 is open and listening on the device. Use a network scanner or run 'telnet <device_ip>' from a local system to confirm the telnet CLI is accessible.Affected if Telnet service is enabled and the CLI port is reachable from the network.
-
Confirm network exposure of telnetReview firewall rules and network segmentation to determine whether the telnet port is exposed to untrusted networks or the internet. Check if the device is on an isolated or DMZ network segment.Affected if Telnet is accessible from untrusted network segments or directly from the internet.
The user is affected if they have a SiPass AC5102 or ACC-AP device with firmware below the patched versions AND telnet is accessible from their network.
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 data2.85.432.85.44
Upgrade SiPass integrated AC5102 firmware to version V2.85.44 or later, and ACC-AP firmware to V2.85.43 or later. If immediate patching is not possible, disable telnet access and restrict network access to these devices.
- Consultation6.0 h
- Implementation4.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,368.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31808 — 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-31808 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