dbcve.org
Sel 2241 Rtac Module FirmwareOperating system · Selinc

CVE-2023-31163

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

Cross-site scripting (XSS) vulnerability in the Schweitzer Engineering Laboratories Real-Time Automation Controller (SEL RTAC) Web Interface allows an authenticated remote attacker to inject and execute arbitrary JavaScript code through unsanitized user input in the web interface.

MitigationApply the vendor patch from SEL Service Bulletin (2022-11-15). Until patched, consider network segmentation and limit web interface access to trusted users only.

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:>= r113-v0, < r150-v2
Sel 3350 FirmwareOperating system
Affected:>= r148-v0, < r150-v2
Sel 3505 FirmwareOperating system
Affected:>= r119-v0, < r150-v2
Sel 3505 3 FirmwareOperating system
Affected:>= r132-v0, < r150-v2
Sel 3530 FirmwareOperating system
Affected:>= r100-v0, < r150-v2
Sel 3530 4 FirmwareOperating system
Affected:>= r108-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 model
    Log into the SEL RTAC device via console or SSH and run the command to display hardware and firmware information, typically 'ver' or 'show system information'. Alternatively, access the web interface login page and check the device identification if displayed.
    Affected if The device model matches any of the following: 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
    From the console, SSH, or web interface system information page, locate the firmware version string (for example, r113-v0, r148-v0, r150-v2). Record the full version identifier exactly as displayed.
    Affected if The firmware version begins with 'r' followed by a three-digit number and '-v' (for example, r113-v0, r119-v0, r132-v0).
  3. Check if web interface is enabled
    From the console or SSH, check the web service configuration. Common commands include 'show http' or 'show web'. If console access is unavailable, attempt to reach the device IP on ports 80 or 443 with a browser.
    Affected if The HTTP or HTTPS web service is listed as enabled, or the device responds to HTTP/HTTPS requests on its management IP.
  4. Compare version against affected ranges
    Using the recorded firmware version, check if it falls within any of these ranges: r113-v0 to r149-vx (for SEL 2241), r148-v0 to r149-vx (for SEL 3350), r119-v0 to r149-vx (for SEL 3505), r132-v0 to r149-vx (for SEL 3505 3), r100-v0 to r149-vx (for SEL 3530), r108-v0 to r149-vx (for SEL 3530 4), r132-v0 to r149-vx (for SEL 3532), r134-v0 to r149-vx (for SEL 3555). Versions r150-v2 and later are not affected. Versions before the first listed version in each range are also not affected.
    Affected if The firmware version is less than r150-v2 AND greater than or equal to the lowest version listed for that model in the affected ranges.

The device is affected if it is one of the listed SEL models, the web interface is accessible, and the firmware version falls within the affected range (any version from the starting version up to but not including r150-v2).

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). Until patched, consider network segmentation and limit web interface access to trusted users only.

Recommended fix High confidence

r150-v2 or later firmware for SEL 2241, SEL 3350, SEL 3505, SEL 3505 3, SEL 3530, SEL 3530 4, SEL 3532, SEL 3555

  1. 1. Identify the specific SEL RTAC device model (e.g., SEL 3350, SEL 3530, etc.) in your environment
  2. 2. Check the current firmware version running on the device via the web interface or CLI
  3. 3. Download the firmware version r150-v2 or later from selinc.com (refer to SEL Service Bulletin dated 2022-11-15 for official patches)
  4. 4. Back up the current device configuration
  5. 5. Upload the new firmware via the RTAC web interface or using the SEL firmware update utility
  6. 6. Verify the firmware upgrade was successful and the device is operational
  7. 7. Confirm the fix by checking that the web interface properly neutralizes user inputs
Caveat Standard firmware upgrade risks apply - ensure configuration backup and plan for brief downtime; verify compatibility with dependent systems

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
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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