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

CVE-2022-2105

CRITICAL · 9.1 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
Client-side JavaScript controls may be bypassed to change user credentials and permissions without authentication, including a “root” user level meant only for the vendor. Web server root level access allows for changing of safety critical parameters.

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

Client-side JavaScript validation can be bypassed to modify user credentials and permissions without authentication. This allows an unauthenticated attacker to create or modify accounts, including escalating to a hidden vendor 'root' account level, which provides access to modify safety-critical system parameters.

MitigationImplement server-side authentication and authorization for all credential and permission changes; remove or disable the vendor root account; enforce server-side validation for all sensitive operations.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 firmware version
    Access the device web interface or system information page, typically found in Settings > About or System > Information. Look for the firmware version number displayed.
    Affected if The installed firmware version falls within any of these ranges: >= 1.23.0 and < 1.23.21, OR >= 1.24.0 and < 1.24.8, OR >= 1.25.0 and < 1.25.3
  2. Confirm web interface accessibility
    Attempt to access the Secheron Sepcos web interface via HTTP/HTTPS on the device IP address. Note whether the login page loads and whether authentication is enforced.
    Affected if The web interface is accessible without requiring authentication, or authentication can be bypassed through direct API calls
  3. Check for vendor root account
    Navigate to the user management or accounts section within the web interface. Look for an account with elevated privileges or a vendor-specific account name. Enumerate all existing user accounts.
    Affected if A hidden vendor root account exists with elevated permissions that can modify safety-critical system parameters
  4. Verify server-side validation is enforced
    Attempt to intercept and modify credential or permission change requests using a web proxy. Send modified requests directly to the server endpoint bypassing client-side JavaScript checks.
    Affected if Credential or permission changes succeed when client-side validation is bypassed, indicating missing server-side authorization checks

You are affected if your Sepcos firmware version is 1.23.0 through 1.23.20, 1.24.0 through 1.24.7, or 1.25.0 through 1.25.2, and the web interface is accessible with exploitable client-side validation.

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 server-side authentication and authorization for all credential and permission changes; remove or disable the vendor root account; enforce server-side validation for all sensitive operations.

Recommended fix High confidence

Upgrade to firmware version 1.23.21, 1.24.8, 1.25.3 or later (or latest stable release)

  1. Identify the current firmware version of the Sepcos Control And Protection Relay device
  2. Determine which version branch is currently installed (1.23.x, 1.24.x, or 1.25.x)
  3. Contact the vendor (ABB/Systeme) to obtain the latest firmware update package
  4. Follow vendor-provided instructions to securely transfer and apply the firmware update to the device
  5. After upgrade, verify the firmware version has been successfully updated to 1.23.21 or later (for 1.23.x), 1.24.8 or later (for 1.24.x), or 1.25.3 or later (for 1.25.x)
  6. Test that client-side JavaScript controls are properly enforced and authentication is required for credential changes
Caveat Firmware upgrades on safety-critical protection relays should be performed according to vendor procedures with appropriate testing and commissioning to ensure protection functions remain operational

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
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,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 $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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