dbcve.org
Sel 2241 Rtac Module FirmwareOperating system · Selinc

CVE-2023-31159

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 in the SEL RTAC Web Interface allows authenticated attackers to inject malicious script code that executes when other users access the affected pages. This is a classic input validation failure where user-supplied data is rendered without proper sanitization.

MitigationApply the vendor patch or firmware update referenced in SEL Service Bulletin (2022-11-15). Until patched, monitor for suspicious user activity and consider network segmentation to limit exposure of the web interface.

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 device model
    Access the SEL RTAC web interface or check the device label/documentation to determine the exact model number (e.g., SEL 2241, SEL 3350, SEL 3505, SEL 3530, SEL 3555)
    Affected if The model is one of the affected products: SEL 2241, SEL 3350, SEL 3505, SEL 3505 3, SEL 3530, SEL 3530 4, SEL 3532, or SEL 3555
  2. Retrieve the installed firmware version
    Log into the SEL RTAC web interface and navigate to the System or Status page to view the firmware version, or use the SEL AcSELERATOR software to query the device for its firmware version information
    Affected if The firmware version is within the affected ranges: for SEL 2241: >= r113-v0, SEL 3350: >= r148-v0, SEL 3505: >= r119-v0, SEL 3505 3: >= r132-v0, SEL 3530: >= r100-v0, SEL 3530 4: >= r108-v0, SEL 3532: >= r132-v0, SEL 3555: >= r134-v0 - and all versions are affected if less than r150-v2
  3. Confirm the web interface is enabled
    Attempt to access the SEL RTAC web interface via HTTP/HTTPS on the standard ports (typically 80/443 or 4433/4434) or check the device network configuration to verify the web server is running
    Affected if The web interface is accessible and the device falls within the affected firmware version range

A user is affected if they are running any of the listed SEL device models with firmware version r150-v2 or higher, as versions below r150-v2 contain the vulnerability.

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 or firmware update referenced in SEL Service Bulletin (2022-11-15). Until patched, monitor for suspicious user activity and consider network segmentation to limit exposure of the web interface.

Recommended fix High confidence

r150-v2 or later firmware version

  1. Identify the specific SEL RTAC device model (SEL 2241, 3350, 3505, 3505 3, 3530, 3530 4, 3532, or 3555)
  2. Check the current firmware version by accessing the device's web interface or CLI
  3. Download the r150-v2 or later firmware version from selinc.com (refer to SEL Service Bulletin dated 2022-11-15 for official download)
  4. Backup the current device configuration before upgrading
  5. Upload the new firmware through the device's web interface or using SEL utility tools
  6. Verify the upgrade was successful by checking the new firmware version
  7. Confirm the XSS vulnerability is resolved by testing the web interface
Caveat Review SEL Service Bulletin for any configuration changes required after upgrade; test thoroughly in non-production environment first

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
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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