dbcve.org
Jetwave 2212s FirmwareOperating system · Korenix

CVE-2021-39280

HIGH · 8.8 CVSS v3.1 Published 2022-02-06
Fix available
A fix is available. Upgrade to 1.5.1 / 1.8 or later.
See remediation →
94/100
Remediation priority · Urgent
Public exploit Remotely reachable Zero-click

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 · unedited
Certain Korenix JetWave devices allow authenticated users to execute arbitrary code as root via /syscmd.asp. This affects 2212X before 1.9.1, 2212S before 1.9.1, 2212G before 1.8, 3220 V3 before 1.5.1, 3420 V3 before 1.5.1, and 2311 through 2022-01-31.

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

A detailed technical summary for this CVE is being prepared.

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
Jetwave 2212s FirmwareOperating system
Affected:< 1.9.1
Jetwave 2212g FirmwareOperating system
Affected:< 1.8
Jetwave 2311 FirmwareOperating system
Affected:<= 1.2
Jetwave 3220 FirmwareOperating system
Affected:< 1.5.1
Jetwave 3420 FirmwareOperating system
Affected:< 1.5.1
Jetwave 2212x FirmwareOperating system
Affected:< 1.9.1

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
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

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 · scoped
Upgrade available Upgrade to 1.5.1 / 1.8 / 1.9.1 or later
Fixed in 1.5.11.81.9.1
Recommended fix High confidence

Upgrade to firmware 1.9.1 (2212X/S), 1.8 (2212G), 1.5.1 (3220/3420 V3), or latest available for 2311

  1. Identify the exact JetWave model number (2212X, 2212S, 2212G, 3220, 3420, or 2311)
  2. Check current firmware version through the device web interface or CLI
  3. Download the appropriate fixed firmware from the official Korenix website (www.korenix.com)
  4. Verify the firmware file integrity using checksums provided by the vendor
  5. Follow the vendor's official firmware upgrade procedure (typically via web-based firmware upload or TFTP)
  6. After upgrade, change the administrative password to a strong, unique credential
  7. Verify the vulnerability is remediated by confirming /syscmd.asp is either removed or properly sanitizes input
  8. Ensure the upgraded firmware version matches the fixed release (1.9.1 for 2212X/S, 1.8 for 2212G, 1.5.1 for 3220/3420)
Caveat Firmware upgrades may interrupt network connectivity; backup configuration before upgrading if possible

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-39280 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-39280 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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