dbcve.org
Sel 2241 Rtac Module FirmwareOperating system · Selinc

CVE-2023-31154

MEDIUM · 5.4 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 →
58/100
Remediation priority · Elevated
Remotely reachable

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 Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Schweitzer Engineering Laboratories Real-Time Automation Controller (SEL RTAC) Web Interface could allow a remote authenticated attacker to inject and execute arbitrary script 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

A stored cross-site scripting (XSS) vulnerability exists in the SEL RTAC Web Interface where improper input validation allows an authenticated remote attacker to inject malicious script code that executes in the context of other users' browsers when they access the compromised web page.

MitigationImplement context-aware output encoding and input validation/sanitization for all user-supplied data rendered in web pages. Apply the vendor patch from SEL Service Bulletin (2022-11-15) when available.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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 device model and firmware version
    Access the SEL RTAC Web Interface and navigate to the System or About section to view the firmware version. Alternatively, use the command-line interface and run the 'show version' or 'version' command to display the firmware version information.
    Affected if The installed firmware version falls within the affected ranges: r132-v0 to r149 (inclusive) for most models, or r134-v0 to r149 for SEL 3555, or r148-v0 to r149 for SEL 3350.
  2. Confirm the web interface is enabled
    Verify that the SEL RTAC Web Interface (HTTP or HTTPS) is accessible and running. Check the network configuration via the CLI using 'show interfaces' or by accessing the web interface directly through a browser.
    Affected if The web interface is accessible and the device is reachable over the network.
  3. Verify authentication is configured
    Log into the web interface and navigate to User Management or Security settings to confirm user accounts exist and authentication is required. Check via CLI using 'show users' or similar commands.
    Affected if The device allows authenticated user access to the web interface, as the vulnerability requires an authenticated attacker to inject the malicious script.
  4. Inspect web interface input fields for lack of encoding
    If you have administrative access, test the input validation by entering HTML or JavaScript characters (such as <script>alert(1)</script>) in web form fields like device naming, descriptions, or configuration text inputs. Observe whether the input is rendered without encoding.
    Affected if User-supplied input is rendered in web pages without proper output encoding, indicating the vulnerability is present and exploitable.

A user is affected if their SEL RTAC device runs firmware version r150-v2 or lower from the affected version ranges AND the web interface is accessible with authenticated user access.

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

Implement context-aware output encoding and input validation/sanitization for all user-supplied data rendered in web pages. Apply the vendor patch from SEL Service Bulletin (2022-11-15) when available.

Recommended fix Moderate confidence

r150-v2 or later firmware

  1. Check the current firmware version on the SEL RTAC device via the web interface or CLI
  2. Review the SEL Service Bulletin dated 2022-11-15 on selinc.com for specific upgrade instructions
  3. Backup the current device configuration before performing the upgrade
  4. Download firmware version r150-v2 or later from selinc.com
  5. Follow SEL's documented firmware upgrade procedure for the specific SEL RTAC model (SEL 2241, SEL 3350, SEL 3505, SEL 3530, SEL 3532, or SEL 3555)
  6. After upgrade, verify the firmware version is r150-v2 or later
  7. Confirm the XSS vulnerability is remediated by testing the web interface
Caveat Review SEL Service Bulletin for any configuration or behavioral changes between affected versions and r150-v2 before upgrading

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-31154 — 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-31154 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