CVE-2022-43393
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 improper check for unusual or exceptional conditions in the HTTP request processing function of Zyxel GS1920-24v2 firmware prior to V4.70(ABMH.8)C0, which could allow an unauthenticated attacker to corrupt the contents of the memory and result in a denial-of-service (DoS) condition on a vulnerable device.
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 GS1920-24v2 switch contains an improper check for unusual or exceptional conditions in its HTTP request processing function. An unauthenticated attacker sending specially crafted HTTP requests can corrupt memory contents, causing the device to crash and resulting in a denial-of-service condition.
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< 4.70\(abpi.5\)c0< 4.70\(abpj.5\)c0< 4.70\(abpk.5\)c0< 4.70\(abpl.5\)c0< 4.70\(acap.3\)c0< 4.70\(acaq.3\)c0< 4.70\(acdr.3\)c0< 4.70\(acds.3\)c0CVSS 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
- Low
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 switch modelCheck the device model label or web interface to confirm if it is one of: GS1350-6hp, GS1350-12hp, GS1350-18hp, GS1350-26hp, GS1915-8, GS1915-8ep, GS1915-24e, or GS1915-24epAffected if The model is one of the listed GS1350 or GS1915 variants
-
Check the firmware versionAccess the web management interface and navigate to Maintenance > Firmware or use the CLI command 'show version' to retrieve the current firmware version stringAffected if The firmware version is lower than 4.70(abpi.5)c0 for GS1350-6hp, 4.70(abpj.5)c0 for GS1350-12hp, 4.70(abpk.5)c0 for GS1350-18hp, 4.70(abpl.5)c0 for GS1350-26hp, 4.70(acap.3)c0 for GS1915-8, 4.70(acaq.3)c0 for GS1915-8ep, 4.70(acdr.3)c0 for GS1915-24e, or 4.70(acds.3)c0 for GS1915-24ep
-
Verify HTTP management is enabledIn the web interface, go to Management > HTTP/HTTPS or use CLI to check if HTTP service is active. The vulnerability exploits HTTP request processing, so HTTP must be enabled for the flaw to be exploitableAffected if HTTP management protocol is enabled on the device
-
Confirm device accessibility via HTTPAttempt to reach the device HTTP port (port 80) from the network. Check if the device responds to HTTP requests from untrusted sourcesAffected if The device HTTP interface is reachable from an untrusted network
You are affected if your device is a GS1350 or GS1915 model running firmware below the version thresholds listed and HTTP management is enabled and accessible.
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 · scoped4.70
Upgrade Zyxel GS1920-24v2 firmware to version V4.70(ABMH.8)C0 or later. If immediate patching is not feasible, restrict HTTP management access to trusted networks or disable HTTP management if only HTTPS is available.
Firmware version 4.70 or later from Zyxel support website (specific build codes: abpi.5c0, abpj.5c0, abpk.5c0, abpl.5c0 for GS1350 series; acap.3c0, acaq.3c0, acdr.3c0, acds.3c0 for GS1915 series)
- 1. Identify the exact model number of your Zyxel device from the affected list (Gs1350 6hp, Gs1350 12hp, Gs1350 18hp, Gs1350 26hp, Gs1915 8, Gs1915 8ep, Gs1915 24e, or Gs1915 24ep)
- 2. Visit the official Zyxel support portal at www.zyxel.com and navigate to the firmware download section for your specific model
- 3. Download the latest firmware version 4.70 or higher that corresponds to your model's build code (abpi.x, abpj.x, abpk.x, abpl.x, acap.x, acaq.x, acdr.x, or acds.x)
- 4. Access the device web management interface or CLI
- 5. Upload the firmware file and initiate the upgrade process
- 6. After upgrade completes, verify the firmware version in the device management interface
- 7. Reboot the device to ensure all components load with the updated firmware
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43393 — 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-43393 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