dbcve.org
Jetnet5018g FirmwareOperating system · Korenix

CVE-2017-14027

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 Credentials 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. The software uses undocumented hard-coded credentials that may allow an attacker to gain remote access.

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 · moderate confidence

Hard-coded, undocumented credentials embedded in Korenix JetNet industrial network device firmware (multiple models including JetNet5018G, JetNet5310G, JetNet5428G, JetNet5628G, JetNet5728G, JetNet5828G, JetNet6710G) allow remote attackers to gain unauthorized administrative access to the affected devices.

MitigationContact Korenix for firmware updates to remove hardcoded credentials; immediately change any default credentials, implement network segmentation to restrict access to affected devices, and apply compensating controls such as IP whitelisting and firewall rules.

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 the Korenix JetNet device model
    Access the device web interface, CLI, or check the device label to confirm the exact model number. Affected models include JetNet5018G, JetNet5310G, JetNet5428G, JetNet5628G, JetNet5628G-R, JetNet5728G, JetNet5828G, and JetNet6710G.
    Affected if The device is one of the listed Korenix JetNet models.
  2. Check the installed firmware version
    Log into the device web interface or CLI and navigate to the system information or firmware version page. The exact path varies by model but is typically found under 'System' > 'Information' or 'Status' > 'Device Info'.
    Affected if The firmware version matches exactly: 1.4, 1.4a, 1.1d, or 1.1 for the respective models listed.
  3. Verify the presence of undocumented user accounts
    Access the user management or account settings page in the device web interface (usually under 'System' > 'User' or 'Administration' > 'User Accounts'). Compare the list of accounts against those you personally configured.
    Affected if There are user accounts present that were not created by your administrative team, indicating hardcoded credentials may exist.
  4. Determine if remote management interfaces are exposed
    Check the device network configuration for enabled remote access services such as HTTP/HTTPS web management, SSH, or Telnet. Verify whether these interfaces are accessible from untrusted networks by reviewing firewall rules or attempting external connectivity tests.
    Affected if Remote web management, SSH, or Telnet is enabled and the device is accessible from networks outside your administrative control.

You are affected if you are running one of the listed Korenix JetNet models with firmware version 1.4, 1.4a, 1.1d, or 1.1, and the device has undocumented accounts or exposed remote management interfaces.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Contact Korenix for firmware updates to remove hardcoded credentials; immediately change any default credentials, implement network segmentation to restrict access to affected devices, and apply compensating controls such as IP whitelisting and firewall rules.

Fix this in Jetnet5018g Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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