dbcve.org
Automation StudioApplication · Br Automation

CVE-2019-19101

MEDIUM · 5.9 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 →
68/100
Remediation priority · Elevated
Remotely reachable No privileges 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 missing secure communication definition and an incomplete TLS validation 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.5SP, < 4.6.4 and < 4.7.2 enable unauthenticated users to perform MITM attacks via the B&R upgrade server.

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

The upgrade service in B&R Automation Studio versions prior to 4.3.11SP, 4.4.9SP, 4.5.5SP, 4.6.4 and 4.7.2 lacks proper secure communication definition and performs incomplete TLS validation, allowing unauthenticated attackers to intercept and manipulate traffic between clients and the B&R upgrade server via MITM attacks.

MitigationUpgrade to B&R Automation Studio version 4.3.11SP or later for 4.0-4.2.x branches, or the respective patched versions (4.4.9SP, 4.5.5SP, 4.6.4, 4.7.2) for later branches. Network segmentation and blocking external upgrade server access can provide temporary workarounds.

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.5>= 4.6, < 4.6.4>= 4.7, < 4.7.2

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/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. Confirm B&R Automation Studio installation
    Locate the B&R Automation Studio installation on the system. Typical installation paths may include C:\Program Files\B&R Automation Studio or C:\Program Files (x86)\B&R Automation Studio. Check for the presence of Automation Studio executables or registry entries related to B&R Automation Studio.
    Affected if The product is not B&R Automation Studio or it is not installed.
  2. Determine installed Automation Studio version
    Open Automation Studio and navigate to Help > About, or check the version in the installation directory. The version information is typically displayed in the format such as 4.3.10, 4.4.8, 4.5.4, etc.
    Affected if Unable to retrieve the version number from the installation.
  3. Compare version against affected ranges
    Compare the installed version number to the following affected ranges: 4.0 through 4.0.29.87, 4.1.0 through 4.1.17.113, 4.2.0 through 4.2.14.119, 4.3.0 through 4.3.10, 4.4.0 through 4.4.8, 4.5.0 through 4.5.4, 4.6.0 through 4.6.3, or 4.7.0 through 4.7.1. Any version falling within these ranges is affected.
    Affected if The installed version falls within any of the listed affected ranges.
  4. Verify upgrade service usage
    Check if the system is configured to use the B&R upgrade service for receiving updates. This may involve examining network configuration, proxy settings, or upgrade-related configuration files within the Automation Studio installation directory.
    Affected if The upgrade service is actively used or configured to connect to upgrade servers.

The environment is affected if B&R Automation Studio is installed with a version falling within the affected ranges AND the upgrade service is used to connect to B&R upgrade servers.

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.5 or later
Fixed in 4.3.114.4.94.5.5
Interim mitigation

Upgrade to B&R Automation Studio version 4.3.11SP or later for 4.0-4.2.x branches, or the respective patched versions (4.4.9SP, 4.5.5SP, 4.6.4, 4.7.2) for later branches. Network segmentation and blocking external upgrade server access can provide temporary workarounds.

Fix this in Automation Studio Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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