dbcve.org
Sel 2241 Rtac Module FirmwareOperating system · Selinc

CVE-2023-31153

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

A stored Cross-Site Scripting (XSS) vulnerability exists in the SEL RTAC web interface where improper input validation allows an authenticated attacker to inject malicious JavaScript code into web pages. When other authenticated users access the affected interface, the injected script executes in their browser context, potentially enabling session hijacking, credential theft, or further network reconnaissance.

MitigationApply the vendor patch from SEL Service Bulletin (2022-11-15). Restrict web interface access to only necessary personnel via network segmentation, and validate all user inputs are properly encoded before rendering in 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:>= r109-v0, < r150-v2
Sel 3530 4 FirmwareOperating system
Affected:>= r109-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
    Access the device web interface or check the physical device label to determine the exact model (e.g., SEL-2241, SEL-3350, SEL-3505, SEL-3530, SEL-3532, SEL-3555)
    Affected if The model matches any of the affected products: SEL-2241, SEL-3350, SEL-3505, SEL-3505 3, SEL-3530, SEL-3530 4, SEL-3532, SEL-3555
  2. Determine the installed firmware version
    Log into the device web interface and navigate to the System or About section to view the firmware version, or use the device CLI command to query the firmware version (typically 'show version' or similar)
    Affected if The firmware version falls within the vulnerable range: r113-v0 through r150-v1 (versions less than r150-v2)
  3. Confirm the web interface is enabled
    Access the device web interface via HTTP/HTTPS. If the login page loads, the web interface is enabled and accessible
    Affected if The web interface is accessible and accepts authentication credentials, making it possible for an attacker to inject malicious script into web pages
  4. Check for recent firmware updates
    Compare your current installed firmware version against the SEL website or release notes for the r150-v2 or later versions
    Affected if The installed version is r150-v1 or earlier, indicating the patch has not been applied

If the device model is one of the affected SEL RTAC products and the installed firmware version is r150-v1 or earlier, the environment is vulnerable to stored XSS via the web interface.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch from SEL Service Bulletin (2022-11-15). Restrict web interface access to only necessary personnel via network segmentation, and validate all user inputs are properly encoded before rendering in the web interface.

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