CVE-2022-45853
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 · uneditedThe privilege escalation vulnerability in the Zyxel GS1900-8 firmware version V2.70(AAHH.3) and the GS1900-8HP firmware version V2.70(AAHI.3) could allow an authenticated, local attacker with administrator privileges to execute some system commands as 'root' on a vulnerable device via SSH.
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 confidenceThis is a local privilege escalation vulnerability in Zyxel GS1900-8 and GS1900-8HP switches. An attacker with valid administrator credentials can execute arbitrary system commands as the root user via SSH, gaining full device control.
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.70\(aahh.3\)= 2.70\(aahi.3\)= 2.70\(aazi.3\)= 2.70\(aahj.3\)= 2.70\(aahl.3\)= 2.70\(aahk.3\)= 2.70\(abto.3\)= 2.70\(abtp.3\)CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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 device modelConnect to the device web interface or SSH and check the system information. The device should be one of: GS1900-8, GS1900-8HP, GS1900-10HP, GS1900-16, GS1900-24, GS1900-24E, GS1900-24EP, or GS1900-24HPV2.Affected if The device is not a Zyxel GS1900 series switch from the affected model list.
-
Check the firmware versionVia SSH or web interface, navigate to the firmware or system information section. The affected versions are: 2.70(aahh.3), 2.70(aahi.3), 2.70(aazi.3), 2.70(aahj.3), 2.70(aahl.3), 2.70(aahk.3), 2.70(abto.3), or 2.70(abtp.3).Affected if The installed firmware version exactly matches one of the affected versions listed.
-
Verify SSH access is enabledCheck the device configuration via web interface under System > SSH or similar, or attempt an SSH connection to the device on port 22.Affected if SSH service is enabled and reachable on the device.
-
Confirm administrator credentials existReview user accounts in the device web interface under Administration > User Account or similar, to confirm at least one administrator account is configured.Affected if Valid administrator credentials exist for the device.
A device is affected if it is a Zyxel GS1900 model (8, 8HP, 10HP, 16, 24, 24E, 24EP, or 24HPV2) running firmware version 2.70 with any of the affected suffixes, has SSH enabled, and has administrator accounts configured.
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 dataApply the vendor firmware update when available, or restrict SSH access to trusted administrator accounts only and monitor for unauthorized access.
- 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-45853 — 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-45853 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