dbcve.org
Jetnet5018g FirmwareOperating system · Korenix

CVE-2017-14021

CRITICAL · 9.8 CVSS v3.0 Published 2017-11-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
A Use of Hard-coded Cryptographic Key issue was discovered in Korenix JetNet JetNet5018G version 1.4, JetNet5310G version 1.4a, JetNet5428G-2G-2FX version 1.4, JetNet5628G-R version 1.4, JetNet5628G version 1.4, JetNet5728G-24P version 1.4, JetNet5828G version 1.1d, JetNet6710G-HVDC version 1.1e, and JetNet6710G version 1.1. An attacker may gain access to hard-coded certificates and private keys allowing the attacker to perform man-in-the-middle attacks.

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 confidence

Hard-coded cryptographic certificates and private keys are embedded in the firmware of multiple Korenix JetNet industrial network switch models. An attacker with access to these keys can impersonate the device or intercept traffic, enabling man-in-the-middle attacks.

MitigationReplace hardcoded certificates with unique, dynamically generated certificates; if vendor firmware update unavailable, isolate affected devices behind network segmentation and implement VPN tunnels to limit exposure.

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
Jetnet5018g FirmwareOperating system
Affected:= 1.4
Jetnet5310g FirmwareOperating system
Affected:= 1.4a
Jetnet5428g 2g 2fx FirmwareOperating system
Affected:= 1.4
Jetnet5628g FirmwareOperating system
Affected:= 1.4
Jetnet5628g R FirmwareHardware / appliance
Affected:= 1.4
Jetnet5728g 24p FirmwareHardware / appliance
Affected:= 1.4
Jetnet5828g FirmwareHardware / appliance
Affected:= 1.1d
Jetnet6710g FirmwareOperating system
Affected:= 1.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Korenix JetNet model
    Inspect the physical device label or access the device management interface (web UI or CLI) to determine the exact model number (e.g., JetNet5018g, JetNet5310g, JetNet5428g, JetNet5628g, JetNet5628g R, JetNet5728g 24p, JetNet5828g, or JetNet6710g)
    Affected if Model is any of the eight affected JetNet models listed in the CVE
  2. Check installed firmware version
    Access the device CLI (via console/SSH) and run 'show version' or access the web management interface System > Firmware/Upgrade page to retrieve the current firmware version string
    Affected if Firmware version matches: 1.4 (JetNet5018g, JetNet5428g, JetNet5628g, JetNet5628g R, JetNet5728g 24p), 1.4a (JetNet5310g), 1.1d (JetNet5828g), or 1.1 (JetNet6710g)
  3. Compare against affected version list
    Cross-reference your identified model and firmware version with the CVE-affected product/version matrix provided in the advisory
    Affected if Your exact model and firmware version combination matches one of the eight affected combinations listed in the CVE

If your Korenix JetNet device model and firmware version match any of the eight affected combinations (1.4, 1.4a, 1.1d, or 1.1 depending on model), the device contains the hardcoded certificates and is vulnerable to impersonation and MITM attacks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace hardcoded certificates with unique, dynamically generated certificates; if vendor firmware update unavailable, isolate affected devices behind network segmentation and implement VPN tunnels to limit exposure.

Recommended fix Moderate confidence

Latest firmware version available from Korenix for your specific JetNet model (contact vendor for version numbers - the description notes JetNet6710G-HVDC version 1.1e was also affected, suggesting incremental fixes)

  1. Check Korenix (Korenix Technology) official website for the latest firmware versions for your specific JetNet model.
  2. Locate and download the most recent firmware release for your affected device model.
  3. Review the firmware release notes to confirm the version addresses CVE-2017-14021 (hard-coded cryptographic key removal).
  4. Follow the vendor's standard firmware upgrade procedure for your JetNet device, typically via web interface or TFTP.
  5. After upgrade, verify that the hard-coded certificates/keys have been replaced with unique, device-specific cryptographic material.
  6. Ensure HTTPS/tls configurations are regenerated post-upgrade.
Caveat Review vendor release notes for any configuration or feature changes between versions; firmware upgrades on industrial devices may require downtime and configuration backup

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

Fix this in Jetnet5018g Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-14021 — 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-2017-14021 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