dbcve.org
Sel 2241 Rtac Module FirmwareOperating system · Selinc

CVE-2023-31149

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 Improper Input Validation vulnerability in the Schweitzer Engineering Laboratories Real-Time Automation Controller (SEL RTAC) Web Interface could allow a remote authenticated attacker to execute arbitrary code. 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

Improper input validation vulnerability in the SEL RTAC web interface allows a remote authenticated attacker to inject malicious input that gets processed without proper sanitization, leading to arbitrary code execution on the affected device.

MitigationApply the vendor patch from SEL Service Bulletin (2022-11-15). If immediate patching is not feasible, implement network segmentation to restrict web interface access to trusted IP addresses only and monitor for indicators of compromise.

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:>= r132-v0, < r150-v2
Sel 3350 FirmwareOperating system
Affected:>= r148-v0, < r150-v2
Sel 3505 FirmwareOperating system
Affected:>= r132-v0, < r150-v2
Sel 3505 3 FirmwareOperating system
Affected:>= r132-v0, < r150-v2
Sel 3530 FirmwareOperating system
Affected:>= r132-v0, < r150-v2
Sel 3530 4 FirmwareOperating system
Affected:>= r132-v0, < r150-v2
Sel 3532 FirmwareOperating system
Affected:>= r132-v0, < r150-v2
Sel 3555 FirmwareOperating system
Affected:>= r134-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 device model
    Log into the device via console or SSH and run the command to display hardware and firmware information, such as 'show system' or 'version' 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. Check the installed firmware version
    Run the firmware version command, typically 'show version' or 'firmware show' via console/SSH, and locate the firmware revision number (e.g., r132-v0, r148-v0, r150-v2)
    Affected if The firmware version falls within these ranges: r132-v0 to r150-v1 (inclusive) for most models, or r134-v0 to r150-v1 for SEL 3555, or r148-v0 to r150-v1 for SEL 3350
  3. Verify the RTAC web interface is enabled
    Check the web interface configuration via the device CLI, typically using 'show http' or 'show web interface' command, or by attempting to access the device IP on port 80/443
    Affected if The HTTP or HTTPS web interface service is enabled and accessible on the network
  4. Confirm remote authentication is possible
    Check if local or remote user authentication is configured for web interface access, using 'show users' or 'show authentication' commands, or verify that web login is functional
    Affected if Users can authenticate remotely to the web interface, or the device has web-accessible user accounts configured

The device is affected if it is any of the listed SEL models, runs firmware version r150-v1 or earlier within the affected ranges, and has the web interface enabled with accessible authentication.

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 from SEL Service Bulletin (2022-11-15). If immediate patching is not feasible, implement network segmentation to restrict web interface access to trusted IP addresses only and monitor for indicators of compromise.

Recommended fix Moderate confidence

r150-v2 or later

  1. Backup the current SEL RTAC configuration before initiating any firmware update.
  2. Obtain the firmware version r150-v2 or later from the official Schweitzer Engineering Laboratories (SEL) download portal or contact SEL support.
  3. Review the SEL firmware upgrade instructions specific to your RTAC model (SEL 2241, SEL 3350, SEL 3505, SEL 3505 3, SEL 3530, SEL 3530 4, SEL 3532, or SEL 3555).
  4. Follow the standard SEL firmware upgrade procedure, which typically involves: a) Logging into the SEL RTAC web interface with administrative credentials, b) Navigating to the firmware upgrade or system maintenance section, c) Uploading the new firmware file (r150-v2 or later), d) Allowing the upgrade process to complete without interrupting power, e) Verifying the system restarts successfully.
  5. After upgrade, verify the firmware version has been updated to r150-v2 or later in the web interface.
  6. Restore the previously backed up configuration if needed.
  7. Test that the web interface and affected functionality operate normally.
Caveat Review SEL release notes for r150-v2 to check for any configuration or behavioral changes that may affect your specific deployment

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
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,320
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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