ABB B&R Automation Studio SQLite flaws enable RCE
Free public brief. The indicators, the detections with Splunk SPL already written (plus Elastic and KQL where they apply), and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.
Multiple SQLite vulnerabilities in ABB B&R Automation Studio <6.5 could enable unauthorized access or RCE; update to version 6.5 available.
ABB B&R Automation Studio versions prior to 6.5 contain 26 vulnerabilities stemming from outdated SQLite library components. The most critical issues are integer overflows in SQLite's concat_ws() function (CVE-2025-3277) leading to 4GB heap buffer overflow, memory corruption in aggregate handling (CVE-2025-6965), and heap-based buffer overflows in session handling (CVE-2023-7104). Additional flaws include use-after-free conditions, NULL pointer dereference, and denial-of-service vectors across FTS3 extension handling, ALTER TABLE operations, and query processing.
ABB reports no successful exploitation observed during testing, but states these vulnerabilities could enable unauthorized access, data exposure, or remote code execution if exploited. The product is deployed globally in critical energy infrastructure. ABB has released version 6.5 which corrects all identified vulnerabilities by replacing the outdated SQLite component. Organizations should prioritize patching on an urgent basis given the ICS deployment context and the range of attack vectors present across multiple SQLite functions.
Mentioned in this report
Detection guidance
B&R Automation Studio Spawning Script Interpreter or Shell
B&R Automation Studio launching a command shell or scripting host, which could indicate client-side exploitation of its bundled SQLite library (memory-corruption flaws fixed in 6.5). Auto-generated starting point — validate and tune in your environment before deploying. IOC matches can false-positive on shared infrastructure and decay as adversary infrastructure rotates.
title: B&R Automation Studio Spawning Script Interpreter or Shell
description: Detects the B&R Automation Studio IDE spawning a command shell, PowerShell
or a script host. Automation Studio versions before 6.5 bundle a vulnerable SQLite
library (heap overflow, use-after-free), so a malicious project or database file
could lead to code execution inside the IDE process. This is a post-exploitation
heuristic based on the parent/child relation, not a vulnerability-specific signature.
The ABB advisory reports no observed exploitation.
tags:
- attack.execution
- attack.t1203
logsource:
category: process_creation
product: windows
detection:
selection:
ParentImage|endswith: \AutomationStudio.exe
Image|endswith:
- \cmd.exe
- \powershell.exe
- \pwsh.exe
- \wscript.exe
- \cscript.exe
- \mshta.exe
- \rundll32.exe
- \regsvr32.exe
- \certutil.exe
- \bitsadmin.exe
condition: selection
falsepositives:
- Engineers running build or deployment scripts, or custom pre/post-build steps, from
within Automation Studio
- Automation Studio add-ons or installers that invoke cmd.exe for setup tasks
level: medium
id: 7b9603f5-3ac2-571c-8de8-4fb58563b1f9
status: experimental
author: Vorant
references:
- https://www.cisa.gov/news-events/ics-advisories/icsa-26-141-03
Behavioural rules are generated from public reporting — validate in your environment before deploying.
Source reporting: https://www.cisa.gov/news-events/ics-advisories/icsa-26-141-03
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its extracted indicators, its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply), the actors and CVEs it names as live profiles, and the vendor research on the same campaign — the primary source the news paraphrased, cited and read directly.
It sits in a corpus of 13,854 reports from 146 sources, 616 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.
Create a free account What it costs