dbcve.org
Automation StudioApplication · Br Automation

CVE-2019-19100

HIGH · 7.1 CVSS v3.1 Published 2020-04-29
Fix available
A fix is available. Upgrade to 4.3.11 / 4.4.9 or later.
See remediation →
73/100
Remediation priority · Elevated
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
A privilege escalation vulnerability in the upgrade service in B&R Automation Studio versions 4.0.x, 4.1.x, 4.2.x, < 4.3.11SP, < 4.4.9SP, < 4.5.4SP, <. 4.6.3SP, < 4.7.2 and < 4.8.1 allow authenticated users to delete arbitrary files via an exposed interface.

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

This is a privilege escalation vulnerability in the upgrade service of B&R Automation Studio industrial control software. Authenticated users can delete arbitrary files on the system through an exposed interface, potentially allowing attackers to escalate privileges or disrupt operations. The vulnerability affects multiple version branches (4.0.x through 4.8.x) below specific patch thresholds.

MitigationUpgrade B&R Automation Studio to version 4.3.11SP or later for the 4.3 branch, 4.4.9SP or later for the 4.4 branch, 4.5.4SP or later for the 4.5 branch, 4.6.3SP or later for the 4.6 branch, 4.7.2 or later for the 4.7 branch, and 4.8.1 or later for the 4.8 branch.

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
Automation StudioApplication
Affected:>= 4.0, <= 4.0.29.87>= 4.1, <= 4.1.17.113>= 4.2, <= 4.2.14.119>= 4.3, < 4.3.11>= 4.4, < 4.4.9>= 4.5, < 4.5.4>= 4.6, < 4.6.3>= 4.7, < 4.7.2= 4.8

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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 Automation Studio version
    Open B&R Automation Studio and navigate to Help > About, or check the software installation directory for version information. The version is typically displayed in the format X.Y.Z.W where X is the major version (4.0-4.8).
    Affected if The installed version falls within any of these ranges: 4.0.0 to 4.0.29.87, 4.1.0 to 4.1.17.113, 4.2.0 to 4.2.14.119, 4.3.0 to 4.3.10, 4.4.0 to 4.4.8, 4.5.0 to 4.5.3, 4.6.0 to 4.6.2, 4.7.0 to 4.7.1, or exactly 4.8.0.
  2. Locate the upgrade service component
    Search for upgrade-related services or executables within the B&R Automation Studio installation directory. Common indicators include terms like 'Update', 'Upgrade', or 'Service' in filenames or service names.
    Affected if An upgrade service component is present and running on the system.
  3. Verify upgrade service accessibility
    Check if the upgrade service exposes a network interface or local IPC mechanism that authenticated users can access. Review service configuration files or documentation for exposed endpoints.
    Affected if The upgrade service exposes an interface that authenticated users can reach without additional authorization beyond standard login.
  4. Confirm user access to upgrade service
    Review user account permissions and determine whether standard authenticated users (non-administrators) have the ability to interact with the upgrade service functionality.
    Affected if Standard authenticated users can invoke upgrade service functions that allow file operations.

Your environment is affected if B&R Automation Studio version is 4.0 through 4.0.29.87, 4.1 through 4.1.17.113, 4.2 through 4.2.14.119, 4.3 through 4.3.10, 4.4 through 4.4.8, 4.5 through 4.5.3, 4.6 through 4.6.2, 4.7 through 4.7.1, or exactly 4.8.0, AND the upgrade service interface is accessible to authenticated 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.

From vendor data
Upgrade available Upgrade to 4.3.11 / 4.4.9 / 4.5.4 or later
Fixed in 4.3.114.4.94.5.4
Interim mitigation

Upgrade B&R Automation Studio to version 4.3.11SP or later for the 4.3 branch, 4.4.9SP or later for the 4.4 branch, 4.5.4SP or later for the 4.5 branch, 4.6.3SP or later for the 4.6 branch, 4.7.2 or later for the 4.7 branch, and 4.8.1 or later for the 4.8 branch.

Fix this in Automation Studio Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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