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

CVE-2022-1667

HIGH · 7.5 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 →
84/100
Remediation priority · High
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
Client-side JavaScript controls may be bypassed by directly running a JS function to reboot the PLC (e.g., from the browser console) or by loading the corresponding, browser accessible PHP script

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 allows attackers to bypass client-side JavaScript controls in a PLC management interface and directly reboot the device by either executing JavaScript functions from the browser console or accessing an unprotected PHP script directly via URL. This indicates missing server-side authentication and authorization checks.

MitigationImplement proper server-side authentication and session validation for all sensitive operations including the reboot function. Remove or restrict access to the exposed PHP script and enforce role-based access controls.

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 firmware version
    Access the device web interface or use SNMP/CLI to retrieve the firmware version. Common paths: check 'About' or 'System Info' page in the web UI, or run 'show version' via CLI.
    Affected if The installed firmware version falls within these ranges: 1.23.0 to 1.23.20, 1.24.0 to 1.24.7, or 1.25.0 to 1.25.2.
  2. Verify web interface accessibility
    Confirm the Sepcos web management interface is reachable on the network. Check if HTTP/HTTPS ports are open on the device.
    Affected if The web interface is exposed on the network without network segmentation or access controls.
  3. Check for unauthenticated PHP script access
    Attempt to access the reboot functionality via direct URL request to the PHP script endpoint without authentication. Use a tool like curl: curl -k https://<device-ip>/<reboot-script-path>
    Affected if The device accepts and processes the request without requiring valid session authentication or authorization.
  4. Test client-side control bypass
    Open the web interface in a browser, open developer console, and attempt to call JavaScript reboot functions directly or modify disabled/hidden form elements to submit reboot requests.
    Affected if The device executes the reboot command when triggered through console execution or modified form submissions without server-side validation.

You are affected if the firmware version is in the affected ranges AND the web interface is accessible AND the device allows unauthenticated or client-side bypassed reboot requests.

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

Implement proper server-side authentication and session validation for all sensitive operations including the reboot function. Remove or restrict access to the exposed PHP script and enforce role-based access controls.

Recommended fix Moderate confidence

Upgrade to firmware 1.23.21 (if on 1.23.x), 1.24.8 (if on 1.24.x), or 1.25.3 (if on 1.25.x) - contact vendor for exact version for your model

  1. Contact Sepcos vendor directly to obtain the official firmware update and remediation guidance
  2. Request the specific firmware version appropriate for your current deployment (1.23.21, 1.24.8, or 1.25.3)
  3. Verify firmware compatibility with your specific Sepcos relay model before applying update
  4. Schedule maintenance window for firmware upgrade following vendor's documented procedures
  5. After upgrade, verify the PHP scripts are no longer directly accessible and JavaScript console commands do not trigger PLC reboot
Caveat Consult vendor release notes for any changes to relay configuration or operation that may affect your system

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
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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