dbcve.org
Sel 5036 Acselerator Bay Screen BuilderApplication · Selinc

CVE-2023-31167

HIGH · 8.1 CVSS v3.1 Published 2023-08-31
Fix available
A fix is available. Upgrade to 1.0.49152.778 or later.
See remediation →
87/100
Remediation priority · High
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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Schweitzer Engineering Laboratories SEL-5036 acSELerator Bay Screen Builder Software on Windows allows Relative Path Traversal. SEL acSELerator Bay Screen Builder software is distributed by SEL-5033 SEL acSELerator RTAC, SEL-5030 Quickset, and SEL Compass. CVE-2023-31167 and was patched in the acSELerator Bay Screen Builder release available on 20230602. Please contact SEL for additional details. This issue affects SEL-5036 acSELerator Bay Screen Builder Software: before 1.0.49152.778.

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 path traversal vulnerability in SEL-5036 acSELerator Bay Screen Builder Software allows attackers to access files outside the intended restricted directory through relative path traversal. This could enable unauthorized read/write access to sensitive system files on Windows hosts where the software is installed.

MitigationUpgrade to acSELerator Bay Screen Builder version 1.0.49152.778 or later (released 2023-06-02). Apply network segmentation and least-privilege file permissions as compensating controls until the patch can be deployed.

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 5036 Acselerator Bay Screen BuilderApplication
Affected:< 1.0.49152.778

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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Locate acSELerator Bay Screen Builder installation
    On the Windows host, check for the software in typical installation directories such as C:\Program Files\SEL\acSELerator Bay Screen Builder or C:\Program Files (x86)\SEL\acSELerator Bay Screen Builder. Also check Add/Remove Programs or the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'acSELerator Bay Screen Builder'.
    Affected if The software is found installed on the system.
  2. Determine installed version number
    Right-click the executable file (typically BayScreenBuilder.exe or similar) in the installation folder, select Properties, and view the Version tab. Alternatively, check the Windows Registry value 'DisplayVersion' under the uninstall registry key for this product.
    Affected if A version number is retrieved from the executable or registry.
  3. Compare version against affected range
    Compare the retrieved version to the affected range: versions prior to 1.0.49152.778 are vulnerable. Note that version 1.0.49152.778 is the fixed release date 2023-06-02.
    Affected if The installed version is less than 1.0.49152.778 (for example, 1.0.49152.777 or earlier).
  4. Verify the software processes external file inputs
    Examine whether the software has been used to load, import, or process screen definition files from untrusted sources, or whether it has been configured to serve files to other applications. Path traversal flaws are triggered when the software handles file paths provided by users or external systems.
    Affected if The software processes user-supplied or external file paths and is less than version 1.0.49152.778.

A Windows system is affected if acSELerator Bay Screen Builder is installed with a version number lower than 1.0.49152.778 and the software processes file paths from external or untrusted sources.

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
Upgrade available Upgrade to 1.0.49152.778 or later
Fixed in 1.0.49152.778
Interim mitigation

Upgrade to acSELerator Bay Screen Builder version 1.0.49152.778 or later (released 2023-06-02). Apply network segmentation and least-privilege file permissions as compensating controls until the patch can be deployed.

Recommended fix High confidence

Upgrade to SEL-5036 acSELerator Bay Screen Builder version 1.0.49152.778 or later

  1. Identify the currently installed version of SEL-5036 acSELerator Bay Screen Builder software
  2. Confirm the installed version is before 1.0.49152.778 (vulnerable to CVE-2023-31167)
  3. Obtain the fixed version 1.0.49152.778 or later from SEL - contact SEL directly or obtain through SEL-5033 SEL acSELerator RTAC, SEL-5030 Quickset, or SEL Compass distribution channels
  4. Back up any existing projects and configurations before upgrading
  5. Install the updated acSELerator Bay Screen Builder version 1.0.49152.778 (released 20230602) following SEL's standard upgrade procedure
  6. Verify the installation was successful and the new version is running
Caveat Review SEL release notes for any configuration or project migration requirements when upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sel 5036 Acselerator Bay Screen Builder Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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