dbcve.org
Sepcos Control And Protection Relay FirmwareOperating system · Secheron

CVE-2022-1668

CRITICAL · 9.8 CVSS v3.1 Published 2022-06-24
Fix available
A fix is available. Upgrade to 1.23.21 / 1.24.8 or later.
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
Weak default root user credentials allow remote attackers to easily obtain OS superuser privileges over the open TCP port for SSH.

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

The vulnerability involves weak default root user credentials that can be exploited remotely via the SSH service (TCP port). Attackers with network access to the SSH port can authenticate using these default credentials and gain OS superuser (root) privileges on the affected system.

MitigationImmediately change default root passwords to strong unique credentials, disable direct root SSH login, enforce key-based authentication, implement fail2ban or account lockout policies, and restrict SSH access via firewall rules or network segmentation.

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
Sepcos Control And Protection Relay FirmwareOperating system
Affected:>= 1.23.0, < 1.23.21>= 1.24.0, < 1.24.8>= 1.25.0, < 1.25.3

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.1/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. Confirm the device is a Secheron Sepcos Control And Protection Relay
    Identify the device model through the device interface, management console, or network inventory. This vulnerability affects only this specific product line.
    Affected if The device is not a Secheron Sepcos Control And Protection Relay relay.
  2. Check the installed firmware version
    Access the device management interface or use the appropriate command to retrieve the firmware version. Compare the version against the affected ranges: 1.23.0 through 1.23.20, 1.24.0 through 1.24.7, and 1.25.0 through 1.25.2.
    Affected if The firmware version falls within any of the affected ranges (1.23.0 to 1.23.20, 1.24.0 to 1.24.7, or 1.25.0 to 1.25.2).
  3. Verify if SSH service is enabled and accessible
    Check if TCP port 22 (or the configured SSH port) is open and reachable on the device. Use a network scan or check device network configuration.
    Affected if SSH is enabled and accessible from a network where untrusted parties can reach the service.
  4. Confirm root SSH login is permitted
    Review the device SSH configuration to determine if direct root user login is allowed via SSH.
    Affected if Root login via SSH is permitted in the SSH service configuration.
  5. Verify the root password has been changed from default
    Attempt to authenticate via SSH using the factory default root credentials, or check if the root password has been changed from the manufacturer default.
    Affected if The root password remains at the factory default setting.

The environment is affected if the device runs a Secheron Sepcos firmware version within the affected ranges, SSH is accessible, root SSH login is permitted, and the root password has not been changed from the default credential.

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
Upgrade available Upgrade to 1.23.21 / 1.24.8 / 1.25.3 or later
Fixed in 1.23.211.24.81.25.3
Interim mitigation

Immediately change default root passwords to strong unique credentials, disable direct root SSH login, enforce key-based authentication, implement fail2ban or account lockout policies, and restrict SSH access via firewall rules or network segmentation.

Recommended fix High confidence

1.23.21 (or 1.24.8 or 1.25.3 depending on your current branch)

  1. 1. Identify the current firmware version running on the Sepcos Control And Protection Relay device
  2. 2. Determine which version branch is currently installed (1.23.x, 1.24.x, or 1.25.x)
  3. 3. Download the appropriate fixed firmware version from the vendor: upgrade to 1.23.21 or later for 1.23.x branch, 1.24.8 or later for 1.24.x branch, or 1.25.3 or later for 1.25.x branch
  4. 4. Review vendor firmware upgrade documentation and ensure proper backup procedures are in place
  5. 5. Upload and install the new firmware version following vendor-recommended procedures
  6. 6. After upgrade, verify that default root credentials have been changed from factory defaults
  7. 7. If SSH access is not required externally, configure network segmentation or firewall rules to restrict SSH access to trusted management networks only
  8. 8. Change the root password immediately after upgrade to a strong, unique password
Caveat Firmware upgrades on industrial control devices may require thorough testing in a non-production environment first; ensure compatibility with connected systems before deploying

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

Fix this in Sepcos Control And Protection Relay Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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