dbcve.org
Sel 2241 Rtac Module FirmwareOperating system · Selinc

CVE-2023-31152

HIGH · 8.8 CVSS v3.1 Published 2023-05-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
An Authentication Bypass Using an Alternate Path or Channel vulnerability in the Schweitzer Engineering Laboratories Real-Time Automation Controller (SEL RTAC) Web Interface allows Authentication Bypass. See SEL Service Bulletin dated 2022-11-15 for more details.

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

CVE-2023-31152 is an authentication bypass vulnerability in the Schweitzer Engineering Laboratories (SEL) Real-Time Automation Controller (RTAC) web interface. The vulnerability allows attackers to access the web interface through an alternate path or channel without proper authentication, potentially gaining full control of the RTAC device.

MitigationApply the vendor patch or firmware update referenced in SEL Service Bulletin dated 2022-11-15. If a patch is unavailable, restrict network access to the RTAC web interface via firewall rules or network segmentation to limit exposure.

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
Sel 2241 Rtac Module FirmwareOperating system
Affected:>= r147-v0, < r150-v2
Sel 3350 FirmwareOperating system
Affected:>= r148-v0, < r150-v2
Sel 3505 FirmwareOperating system
Affected:>= r147-v0, < r150-v2
Sel 3505 3 FirmwareOperating system
Affected:>= r147-v0, < r150-v2
Sel 3530 FirmwareOperating system
Affected:>= r147-v0, < r150-v2
Sel 3530 4 FirmwareOperating system
Affected:>= r147-v0, < r150-v2
Sel 3532 FirmwareOperating system
Affected:>= r147-v0, < r150-v2
Sel 3555 FirmwareOperating system
Affected:>= r147-v0, < r150-v2

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 SEL RTAC device model
    Locate the model number printed on the physical device chassis or label, or access the device console and run a model information command
    Affected if The device model is one of: SEL 2241, SEL 3350, SEL 3505, SEL 3505 3, SEL 3530, SEL 3530 4, SEL 3532, or SEL 3555
  2. Determine the installed firmware version
    Log into the RTAC web interface and navigate to the About or System Information page, or access the command line and run the appropriate version display command
    Affected if The firmware version is r147-v0 or any version up to but not including r150-v2
  3. Verify web interface network exposure
    Check firewall rules or network configuration to determine if the RTAC web interface (HTTP/HTTPS ports) is accessible from external or untrusted network segments
    Affected if The web interface is reachable from network segments that are not fully trusted or controlled

The environment is affected if the device is one of the listed SEL RTAC models running firmware version r147-v0 or newer but older than r150-v2, and the web interface is network-accessible.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch or firmware update referenced in SEL Service Bulletin dated 2022-11-15. If a patch is unavailable, restrict network access to the RTAC web interface via firewall rules or network segmentation to limit exposure.

Recommended fix High confidence

r150-v2

  1. Obtain the r150-v2 firmware update from Schweitzer Engineering Laboratories (SEL) via their official support channels
  2. Follow SEL's standard firmware upgrade procedure for the affected RTAC device model
  3. After upgrading, verify the firmware version is r150-v2 or later
  4. Confirm the web interface is accessible and the authentication bypass vulnerability is resolved

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

Fix this in Sel 2241 Rtac Module Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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