Sg200 50 FirmwareOperating system · Cisco
CVE-2019-1859
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 · uneditedA vulnerability in the Secure Shell (SSH) authentication process of Cisco Small Business Switches software could allow an attacker to bypass client-side certificate authentication and revert to password authentication. The vulnerability exists because OpenSSH mishandles the authentication process. An attacker could exploit this vulnerability by attempting to connect to the device via SSH. A successful exploit could allow the attacker to access the configuration as an administrative user if the default credentials are not changed. There are no workarounds available; however, if client-side certificate authentication is enabled, disable it and use strong password authentication. Client-side certificate authentication is disabled by default.
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 confidenceA vulnerability in the SSH authentication of Cisco Small Business Switches allows attackers to bypass client-side certificate authentication due to OpenSSH mishandling the authentication process. Successful exploitation grants administrative access if default credentials remain unchanged.
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
Sg200 50 FirmwareOperating system
< 1.4.10.6
Sg200 50p FirmwareOperating system
< 1.4.10.6
Sg200 50fp FirmwareOperating system
< 1.4.10.6
Sg200 26 FirmwareOperating system
< 1.4.10.6
Sg200 26p FirmwareOperating system
< 1.4.10.6
Sg200 26fp FirmwareOperating system
< 1.4.10.6
Sg200 18 FirmwareOperating system
< 1.4.10.6
Sg200 10fp FirmwareOperating system
< 1.4.10.6CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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.
-
Confirm device model is an affected Cisco SG200 switchAccess the switch web interface or CLI and identify the exact model number (e.g., SG200-50, SG200-26, SG200-18, SG200-10fp)Affected if The device is a Cisco SG200-50, SG200-50p, SG200-50fp, SG200-26, SG200-26p, SG200-26fp, SG200-18, or SG200-10fp
-
Check installed firmware versionIn the web interface, go to Administration > Firmware or use CLI command 'show version' to view the current firmware versionAffected if Firmware version is lower than 1.4.10.6
-
Verify SSH service is enabledIn the web interface, go to Security > SSH Settings or use CLI command 'show ip ssh' to confirm SSH is activeAffected if SSH is enabled on the device
-
Check if client-side certificate authentication is configuredIn the web interface, go to Security > SSH Authentication and look for certificate-based authentication settings; or use CLI to inspect SSH authentication methodsAffected if Client-side certificate authentication is enabled for SSH
-
Verify default administrative credentials are not in useIn the web interface, go to Administration > User Accounts to review configured admin accounts; check if the default 'admin' username retains its factory default passwordAffected if Default credentials (admin/admin or similar) are still active
The device is affected if it is a listed Cisco SG200 model running firmware below 1.4.10.6, has SSH enabled with client-side certificate authentication configured, and uses default administrative credentials.
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 data1.4.10.6
If client-side certificate authentication is enabled, disable it and configure strong password authentication. Ensure all default administrative credentials are changed before deploying the device.
Fix this in Sg200 50 Firmware
Scoped from the published advisory
- 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-2019-1859 — 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-2019-1859 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