dbcve.org
Sel 2241 Rtac Module FirmwareOperating system · Selinc

CVE-2023-31157

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 · high confidence

This is a stored Cross-site Scripting (XSS) vulnerability in the SEL RTAC web interface where an authenticated attacker can inject malicious JavaScript code into web pages that will execute in the browsers of other users viewing those pages.

MitigationApply the vendor firmware update from SEL Service Bulletin (2022-11-15) when available. In the interim, restrict web interface access to trusted users only and implement 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:>= 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 SEL RTAC device model
    Log into the RTAC web interface and navigate to the System Information or Device Status page. Alternatively, check the physical device label or consult your asset inventory for the exact model number (e.g., SEL 2241, SEL 3350, SEL 3505, SEL 3530, SEL 3532, SEL 3555).
    Affected if The device model matches one of the affected models listed in the CVE.
  2. Locate the firmware version display
    In the SEL RTAC web interface, find the firmware version information typically displayed on the main dashboard, under System Setup > System Information, or in the About/Help section. The version will appear in the format rXXX-vY.
    Affected if This step enables version comparison.
  3. Compare installed firmware version against affected ranges
    Check if your installed version falls within any of these ranges: r132-v0 through r149-vX (for models r132-v0 start), or r134-v0 through r149-vX (for SEL 3555), or r148-v0 through r149-vX (for SEL 3350). Versions r150-v2 and later are not affected.
    Affected if The installed version is greater than or equal to the lower bound AND less than r150-v2 for your specific model.
  4. Verify the web interface is accessible
    Confirm the RTAC web interface is reachable on your network by attempting to access the device IP or hostname in a browser. Check if HTTP/HTTPS ports (typically 80/443 or 8080) are open via a port scan.
    Affected if The web interface is exposed and accessible to network attackers.
  5. Review web interface user access controls
    Examine the user accounts configured on the RTAC device under User Management or Access Control settings. Determine if there are any accounts with lower trust levels or if authentication is enforced for all web page interactions.
    Affected if Untrusted or unauthenticated users have access to the web interface where injected scripts could execute in other users' browsers.

You are affected if your SEL RTAC device model and installed firmware version fall within the listed ranges and the web interface is accessible to users who could inject malicious scripts.

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 firmware update from SEL Service Bulletin (2022-11-15) when available. In the interim, restrict web interface access to trusted users only and implement network segmentation to limit exposure.

Recommended fix High confidence

SEL RTAC Firmware r150-v2 (or any later stable release)

  1. 1. Backup the current SEL RTAC device configuration before performing any firmware update.
  2. 2. Obtain the firmware version r150-v2 or later from the official SEL (Schweitzer Engineering Laboratories) download portal.
  3. 3. Verify the firmware file integrity using checksums provided by SEL.
  4. 4. Access the SEL RTAC Web Interface using an authenticated account with administrative privileges.
  5. 5. Navigate to the firmware upgrade section (typically under System Administration or Maintenance).
  6. 6. Upload and apply the r150-v2 firmware file to the device.
  7. 7. After the upgrade completes, verify the device is functioning normally and the new firmware version is installed.
  8. 8. Confirm the vulnerability is remediated by checking that the XSS payload is no longer executable.
Caveat Review SEL service bulletin for any configuration changes or compatibility considerations 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
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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