dbcve.org
Sel 2241 Rtac Module FirmwareOperating system · Selinc

CVE-2023-31150

MEDIUM · 6.5 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 →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
A Storing Passwords in a Recoverable Format vulnerability in the Schweitzer Engineering Laboratories Real-Time Automation Controller (SEL RTAC) database system could allow an authenticated attacker to retrieve passwords. 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

The vulnerability exists in the SEL RTAC database system where passwords are stored in a recoverable format rather than being properly hashed or encrypted. An authenticated attacker with database access can retrieve these passwords in plaintext or reversibly-encrypted form.

MitigationApply the SEL service bulletin (2022-11-15) patches to update the RTAC firmware/database system. After patching, rotate all stored credentials to ensure any compromised passwords are replaced.

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:>= r122-v0, < r150-v2
Sel 3350 FirmwareOperating system
Affected:>= r148-v0, < r150-v2
Sel 3505 FirmwareOperating system
Affected:>= r122-v0, < r150-v2
Sel 3505 3 FirmwareOperating system
Affected:>= r132-v0, < r150-v2
Sel 3530 FirmwareOperating system
Affected:>= r122-v0, < r150-v2
Sel 3530 4 FirmwareOperating system
Affected:>= r122-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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 firmware version
    Access the device's web interface, console, or administrative panel and locate the firmware version information. This is typically found in System > About, Device Info, or the main status page.
    Affected if The installed firmware version falls within any of these ranges: SEL-2241: r122-v0 to r150-v2 (excluding r150-v2), SEL-3350: r148-v0 to r150-v2 (excluding r150-v2), SEL-3505: r122-v0 to r150-v2 (excluding r150-v2), SEL-3505 3: r132-v0 to r150-v2 (excluding r150-v2), SEL-3530: r122-v0 to r150-v2 (exc
  2. Verify database access is enabled
    Check if the RTAC database system is accessible. This is typically configured in the device's network settings, database configuration, or remote access settings. Confirm that database connectivity is permitted.
    Affected if The RTAC database system is accessible over the network or via local console access, regardless of authentication status.
  3. Inspect password storage format in the database
    If database access is available, query the password storage tables or files within the RTAC database system. Look for password fields and determine if they contain plaintext strings, reversible encryption patterns, or proper hashed values.
    Affected if Passwords stored in the RTAC database are in plaintext, reversibly encrypted, or otherwise recoverable format rather than being irreversibly hashed.

You are affected if your SEL RTAC device runs firmware versions below r150-v2 and an attacker with database access can retrieve stored passwords in recoverable form.

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 SEL service bulletin (2022-11-15) patches to update the RTAC firmware/database system. After patching, rotate all stored credentials to ensure any compromised passwords are replaced.

Recommended fix High confidence

Upgrade to SEL RTAC firmware r150-v2 or later

  1. 1. Identify the specific SEL RTAC model (e.g., SEL 2241, SEL 3350, SEL 3505, SEL 3530, SEL 3532, or SEL 3555)
  2. 2. Access the device console or web interface and check the current firmware version using 'version' command or system information page
  3. 3. Download the fixed firmware version r150-v2 or later from SEL's official support website (selinc.com) - you may need to register for an account
  4. 4. Review SEL's firmware upgrade instructions in the product manual or release notes
  5. 5. Back up the current device configuration before proceeding with the upgrade
  6. 6. Upload the firmware file through the device's web interface or via SCP/SFTP to the device
  7. 7. Initiate the firmware upgrade and wait for the process to complete - do not power off the device during this process
  8. 8. After reboot, verify the new firmware version is r150-v2 or later using 'version' command
Caveat Review SEL release notes for r150-v2 to check for any configuration or feature changes that may affect your deployment

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
  • 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-31150 — 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-31150 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