dbcve.org
Uncontrolled Search Path (DLL Hijack)Weakness · CWE-427

CVE-2024-2637

HIGH · 7.2 CVSS v3.1 Published 2024-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated

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 Uncontrolled Search Path Element vulnerability in B&R Industrial Automation Scene Viewer, B&R Industrial Automation Automation Runtime, B&R Industrial Automation mapp Vision, B&R Industrial Automation mapp View, B&R Industrial Automation mapp Cockpit, B&R Industrial Automation mapp Safety, B&R Industrial Automation VC4, B&R Industrial Automation APROL, B&R Industrial Automation CAN Driver, B&R Industrial Automation CAN Driver CC770, B&R Industrial Automation CAN Driver SJA1000, B&R Industrial Automation Tou0ch Lock, B&R Industrial Automation B&R Single-Touch Driver, B&R Industrial Automation Serial User Mode Touch Driver, B&R Industrial Automation Windows Settings Changer (LTSC), B&R Industrial Automation Windows Settings Changer (2019 LTSC), B&R Industrial Automation Windows 10 Recovery Solution, B&R Industrial Automation ADI driver universal, B&R Industrial Automation ADI Development Kit, B&R Industrial Automation ADI .NET SDK, B&R Industrial Automation SRAM driver, B&R Industrial Automation HMI Service Center, B&R Industrial Automation HMI Service Center Maintenance, B&R Industrial Automation Windows 10 IoT Enterprise 2019 LTSC, B&R Industrial Automation KCF Editor could allow an authenticated local attacker to execute malicious code by placing specially crafted files in the loading search path..This issue affects Scene Viewer: before 4.4.0; Automation Runtime: before J4.93; mapp Vision: before 5.26.1; mapp View: before 5.24.2; mapp Cockpit: before 5.24.2; mapp Safety: before 5.24.2; VC4: before 4.73.2; APROL: before 4.4-01; CAN Driver: before 1.1.0; CAN Driver CC770: before 3.3.0; CAN Driver SJA1000: before 1.3.0; Tou0ch Lock: before 2.1.0; B&R Single-Touch Driver: before 2.0.0; Serial User Mode Touch Driver: before 1.7.1; Windows Settings Changer (LTSC): before 3.2.0; Windows Settings Changer (2019 LTSC): before 2.2.0; Windows 10 Recovery Solution: before 3.2.0; ADI driver universal: before 3.2.0; ADI Development Kit: before 5.5.0; ADI .NET SDK: before 4.1.0; SRAM driver: before 1.2.0; HMI Service Center: before 3.1.0; HMI Service Center Maintenance: before 2.1.0; Windows 10 IoT Enterprise 2019 LTSC: through 1.1; KCF Editor: before 1.1.0.

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

An Uncontrolled Search Path Element vulnerability exists in multiple B&R Industrial Automation products where an authenticated local attacker can place malicious DLLs or executables in the application search path, causing the application to load and execute the attacker's code instead of the intended legitimate files. This affects library/dll loading mechanisms in the listed products.

MitigationUpdate each affected B&R product to the version specified in the CVE (e.g., Scene Viewer to 4.4.0, Automation Runtime to J4.93, VC4 to 4.73.2, etc.). As a compensating control, restrict file system permissions to prevent unauthorized users from writing to application directories in the search path.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Local
Complexity
High
Privileges
High
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:H/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 installed B&R Industrial Automation products
    Review installed programs on the system for B&R Industrial Automation software such as Scene Viewer, Automation Runtime, VC4, or other B&R utilities. Check Program Files directories for B&R folders.
    Affected if Any B&R Industrial Automation product is installed on the system
  2. Determine installed product versions
    Open the installed B&R application or check its properties in Add/Remove Programs to find the exact version number. Compare against the fixed versions referenced in the CVE documentation.
    Affected if The installed version is older than the patched versions for each product (e.g., Scene Viewer versions before 4.4.0, VC4 versions before 4.73.2)
  3. Inspect application directory permissions
    Right-click on the B&R application installation folder, go to Properties, then Security tab. Check which users or groups have Write or Modify permissions to the directory.
    Affected if Non-administrator users or the Users group have Write permissions to application directories in the search path
  4. Verify DLL loading behavior
    Review the application configuration or documentation to confirm it loads DLLs from the application directory or relative paths without strict path specification.
    Affected if The application uses implicit DLL loading from the search path rather than absolute paths
  5. Check for writable locations in search path
    Identify all directories in the application search path (check PATH environment variable and application working directory). Test write access using non-elevated user account.
    Affected if Any directory in the search path is writable by an authenticated local attacker

A user is affected if B&R Industrial Automation software is installed with a version prior to the patched releases AND the application directories or search path locations are writable by unprivileged 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

Update each affected B&R product to the version specified in the CVE (e.g., Scene Viewer to 4.4.0, Automation Runtime to J4.93, VC4 to 4.73.2, etc.). As a compensating control, restrict file system permissions to prevent unauthorized users from writing to application directories in the search path.

Recommended fix High confidence

Upgrade each product to the specific version mentioned: Scene Viewer 4.4.0, Automation Runtime J4.93, mapp Vision 5.26.1, mapp View 5.24.2, mapp Cockpit 5.24.2, mapp Safety 5.24.2, VC4 4.73.2, APROL 4.4-01, CAN Driver 1.1.0, CAN Driver CC770 3.3.0, CAN Driver SJA1000 1.3.0, Tou0ch Lock 2.1.0, B&R Si

  1. 1. Identify all affected B&R Industrial Automation products installed in your environment from the list: Scene Viewer, Automation Runtime, mapp Vision, mapp View, mapp Cockpit, mapp Safety, VC4, APROL, CAN Driver, CAN Driver CC770, CAN Driver SJA1000, Tou0ch Lock, B&R Single-Touch Driver, Serial User Mode Touch Driver, Windows Settings Changer (LTSC), Windows Settings Changer (2019 LTSC), Windows
  2. 2. Check the current installed version of each identified product
  3. 3. For each product with a version below the fixed release, obtain the updated version from B&R Industrial Automation (www.br-automation.com)
  4. 4. Schedule maintenance window as DLL hijacking requires local authenticated access
  5. 5. Backup current configurations before applying updates
  6. 6. Upgrade each affected product to its fixed version: Scene Viewer to 4.4.0+, Automation Runtime to J4.93+, mapp Vision to 5.26.1+, mapp View to 5.24.2+, mapp Cockpit to 5.24.2+, mapp Safety to 5.24.2+, VC4 to 4.73.2+, APROL to 4.4-01+, CAN Driver to 1.1.0+, CAN Driver CC770 to 3.3.0+, CAN Driver SJA1000 to 1.3.0+, Tou0ch Lock to 2.1.0+, B&R Single-Touch Driver to 2.0.0+, Serial User Mode Touch D
  7. 7. Verify the upgrade was successful by checking the new version numbers
  8. 8. Restrict file system permissions on application directories to prevent unauthorized DLL placement as an additional mitigation

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

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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