dbcve.org
Sel 2241 Rtac Module FirmwareOperating system · Selinc

CVE-2023-31165

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 Real-Time Automation Controller web interface. An authenticated remote attacker can inject malicious JavaScript or HTML payload into web application input fields, which then executes in the browsers of other users viewing the affected pages.

MitigationApply the vendor patch from SEL Service Bulletin (2022-11-15). Until then, restrict web interface access to trusted users only and monitor for suspicious activity.

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 device model
    Locate the physical device or check network inventory to determine the exact model number (e.g., SEL 2241, SEL 3350, SEL 3505, SEL 3530, SEL 3532, or SEL 3555)
    Affected if The model is one of the affected products listed in the CVE
  2. Determine the installed firmware version
    Access the device web interface and navigate to the system information or firmware status page, or use the device CLI command to display firmware version
    Affected if The firmware version cannot be determined or is not visible
  3. Compare firmware version against affected ranges
    Match your installed version to the vulnerable ranges: SEL 2241 (>= r113-v0, < r150-v2), SEL 3350 (>= r148-v0, < r150-v2), SEL 3505 (>= r119-v0, < r150-v2), SEL 3505 3 (>= r132-v0, < r150-v2), SEL 3530 (>= r100-v0, < r150-v2), SEL 3530 4 (>= r108-v0, < r150-v2), SEL 3532 (>= r132-v0, < r150-v2), SEL 3555 (>= r134-v0, < r150-v2)
    Affected if Your installed version falls within any of these vulnerable ranges
  4. Verify web interface is enabled
    Confirm the device web interface (HTTP/HTTPS) is accessible on the network
    Affected if The web interface is exposed and reachable
  5. Check for user accounts with web interface access
    Review device authentication configuration to determine which users have credentials to log into the web interface
    Affected if Any user accounts exist that provide web interface access

You are affected if your SEL RTAC device model and firmware version fall within the listed vulnerable ranges and the web interface is accessible to authenticated users.

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 then, restrict web interface access to trusted users only and monitor for suspicious activity.

Recommended fix High confidence

Firmware r150-v2 or later for the affected SEL RTAC models (2241, 3350, 3505, 3505 3, 3530, 3530 4, 3532, 3555)

  1. 1. Identify the specific SEL RTAC model (2241, 3350, 3505, 3505 3, 3530, 3530 4, 3532, or 3555) in your environment
  2. 2. Document the current firmware version by accessing the device through its console or web interface
  3. 3. Obtain the firmware upgrade file from SEL's official support portal (selinc.com) - specifically version r150-v2 or later
  4. 4. Review SEL Service Bulletin (dated 2022-11-15) for any specific upgrade prerequisites or procedures
  5. 5. Create a backup of the current device configuration before proceeding with the upgrade
  6. 6. Upload and apply the r150-v2 (or later) firmware through the RTAC web interface or management tool
  7. 7. After reboot, verify the new firmware version is installed and confirm the web interface is functional
  8. 8. Test that the XSS vulnerability is remediated by validating the web interface properly sanitizes input
Caveat Review SEL documentation and service bulletin for any configuration changes or compatibility considerations before upgrading; plan for potential downtime during the firmware update process

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
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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