dbcve.org
Sel 2241 Rtac Module FirmwareOperating system · Selinc

CVE-2023-2310

MEDIUM · 5.3 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 →
60/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Channel Accessible by Non-Endpoint vulnerability in the Schweitzer Engineering Laboratories SEL Real-Time Automation Controller (RTAC) could allow a remote attacker to perform a man-in-the-middle (MiTM) that could result in denial of service. See the ACSELERATOR RTAC SEL-5033 Software instruction manual date code 20210915 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 Channel Accessible by Non-Endpoint vulnerability in the SEL Real-Time Automation Controller (RTAC) allows a remote attacker to intercept network communications between endpoints, enabling man-in-the-middle (MiTM) attacks that can result in denial of service.

MitigationImplement network segmentation to isolate the RTAC from untrusted networks, and ensure all communication channels use proper authentication and encryption to prevent MiTM attacks.

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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H

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 label or access the device's web interface/console to confirm the exact model number (e.g., SEL 2241, SEL 3350, SEL 3505, SEL 3530, SEL 3532, SEL 3555).
    Affected if The device model matches one of the affected products listed in the CVE.
  2. Determine the installed firmware version
    Access the device's administrative interface (web GUI or console) and navigate to the system information or firmware version page. Record the exact firmware version string (e.g., r140-v1, r148-v0).
    Affected if The installed firmware version falls within the range of >= r113-v0 (or the model-specific minimum) and < r150-v2.
  3. Compare firmware against the fixed version
    Compare your recorded firmware version to r150-v2. Versions below r150-v2 (such as r148-v0, r140-v1, r132-v0) are affected; r150-v2 and above are not.
    Affected if The firmware version is less than r150-v2.
  4. Assess network exposure of the RTAC device
    Review network firewall rules, VLAN configuration, and access control lists to determine whether the RTAC device is reachable from untrusted network segments or external IP addresses.
    Affected if The RTAC is accessible from networks that are not explicitly trusted or isolated.
  5. Verify encryption on RTAC communication channels
    Check the RTAC configuration for enabled encryption protocols (such as TLS/SSL) on all communication channels used for inter-endpoint messaging.
    Affected if Communication channels lack proper encryption or authentication, enabling the MiTM attack vector described in the CVE.

A user is affected if their SEL RTAC device runs firmware version lower than r150-v2 AND is accessible from untrusted networks without proper encryption on communications.

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

Implement network segmentation to isolate the RTAC from untrusted networks, and ensure all communication channels use proper authentication and encryption to prevent MiTM attacks.

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 current firmware version of the SEL RTAC device by accessing the device management interface or using ACSELERATOR RTAC SEL-5033 software
  2. 2. Navigate to the Schweitzer Engineering Laboratories (SEL) website (selinc.com) and locate the firmware download section for your specific RTAC model
  3. 3. Download firmware version r150-v2 or later for your SEL device model (SEL 2241, SEL 3350, SEL 3505, SEL 3505 3, SEL 3530, SEL 3530 4, SEL 3532, or SEL 3555)
  4. 4. Review the firmware release notes and any migration/upgradation instructions provided by SEL
  5. 5. Follow SEL's documented firmware upgrade procedure, typically using ACSELERATOR RTAC software or the device's web interface to upload and install the new firmware
  6. 6. After installation, verify the device is running firmware version r150-v2 or later
  7. 7. Test that the device functions normally and the vulnerability is remediated
Caveat Firmware upgrades on industrial control devices should be performed following SEL's official procedures; ensure proper backup and testing in a non-production environment before deploying to production 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
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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