CVE-2024-2637

Insecure Loading of Code in B&R Products

HIGH
7.2
CVSS Score
Published: May 14, 2024 at 06:49 PM UTC
Updated: June 17, 2026 at 07:24 AM UTC
30 products affected across 2 vendorsAutomation Automation RuntimeAPROLAutomation Runtime

Using Scene Viewer by B&R Industrial Automation?

Get instant alerts when new vulnerabilities affect Scene Viewer - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.2
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 5.5.0
Affected range stops below 5.5.0, so it looks safe — our inference, not a vendor statement
v < 3.2.0
Affected range stops below 3.2.0, so it looks safe — our inference, not a vendor statement
v < 4.1.0
Affected range stops below 4.1.0, so it looks safe — our inference, not a vendor statement
v < 4.4-01
Affected range stops below 4.4-01, so it looks safe — our inference, not a vendor statement
v < J4.93
Affected range stops below J4.93, so it looks safe — our inference, not a vendor statement
v < 1.1.0
Affected range stops below 1.1.0, so it looks safe — our inference, not a vendor statement
v < 3.3.0
Affected range stops below 3.3.0, so it looks safe — our inference, not a vendor statement
v < 1.3.0
Affected range stops below 1.3.0, so it looks safe — our inference, not a vendor statement
v < 3.1.0
Affected range stops below 3.1.0, so it looks safe — our inference, not a vendor statement
v < 2.1.0
Affected range stops below 2.1.0, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.2HIGHABB
Attack Vector
LOCAL
Complexity
HIGH
Privileges
HIGH
User Interaction
REQUIRED
Scope
CHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-427

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card