dbcve.org
Sel 2241 Rtac Module FirmwareOperating system · Selinc

CVE-2023-31148

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 in the SEL RTAC web interface allows a remote authenticated attacker to inject and execute arbitrary code. This is a classic web application vulnerability where user-supplied input is not properly sanitized before being processed, enabling code execution on the underlying system.

MitigationApply vendor patches from SEL Service Bulletin (2022-11-15) when available. Until patched, restrict network access to the RTAC web interface to trusted IPs only, minimize the number of authenticated users, and monitor for unusual administrative activity.

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
    Locate the physical device label or check the device documentation, web interface, or management console to determine if the hardware is one of: SEL 2241, SEL 3350, SEL 3505, SEL 3505 3, SEL 3530, SEL 3530 4, SEL 3532, or SEL 3555
    Affected if The device model matches one of the eight affected models listed in the CVE
  2. Check the installed firmware version
    Access the device web interface, command line interface, or management software and locate the firmware version information. Compare the version string (e.g., r132-v0, r150-v2) against the affected ranges: r132-v0 to r150-v1 (or r148-v0 to r150-v1 for SEL 3350, r134-v0 to r150-v1 for SEL 3555)
    Affected if The firmware version falls within the affected range (>= r132-v0 or r134-v0/r148-v0 depending on model, but < r150-v2)
  3. Verify the RTAC web interface is enabled
    Check the device network configuration or web server settings to confirm the RTAC web interface is currently active and accessible
    Affected if The RTAC web interface is enabled and accessible on the network
  4. Confirm authentication is configured for the web interface
    Check the web interface user accounts or authentication settings to determine if login is required to access administrative functions
    Affected if User authentication is configured (since the vulnerability requires an authenticated attacker)

The environment is affected if the device is one of the eight listed models, runs firmware version r132-v0 through r150-v1 (or r134-v0/r148-v0 to r150-v1 for specific models), and has the RTAC web interface enabled with configured users.

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 vendor patches from SEL Service Bulletin (2022-11-15) when available. Until patched, restrict network access to the RTAC web interface to trusted IPs only, minimize the number of authenticated users, and monitor for unusual administrative activity.

Recommended fix High confidence

Upgrade to SEL RTAC firmware r150-v2 or later

  1. 1. Identify the specific SEL RTAC device model (e.g., SEL 3505, SEL 3530, etc.) currently in use
  2. 2. Check the current firmware version installed on the device through the web interface or CLI
  3. 3. Download the r150-v2 or later firmware version from the Schweitzer Engineering Laboratories (SEL) customer portal at selinc.com
  4. 4. Review the SEL Service Bulletin (dated 2022-11-15) for any specific upgrade prerequisites or instructions
  5. 5. Backup the current device configuration before initiating the firmware upgrade
  6. 6. Upload and apply the r150-v2 firmware through the SEL RTAC web interface or using the acutest utility according to SEL documentation
  7. 7. After upgrade, verify the firmware version shows r150-v2 or later
  8. 8. Confirm the web interface is functional and the vulnerability is remediated
Caveat Review SEL Service Bulletin 2022-11-15 for any configuration changes or breaking changes between affected and fixed versions

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
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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