Skip to content
Fencer Intel
medium 6.5

CVE-2019-19101 json

Incomplete communication encryption and validation in B&R Automation Studio upgrade service

published 6y ago modified 4mo ago also EUVD-2019-8738

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 44%
public exploits
0
none known

Summary

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.

Patch / fix

  • br-automation automation_studio 4.3.11, 4.4.9, 4.5.5, 4.6.4, 4.7.2

Is CVE-2019-19101 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-20-093-01 updated cvss 6.5

B&R Automation Studio

  • B&R Industrial Automation Automation Studio < 4.4.9SP, < 4.6.3SP, 4.1.x, < 4.7.2
    affected: vendor fix, mitigation “Access to zip archives is controlled and access of the zip archive is limited to trusted parties only.” br-automation.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Exploit prediction

0.53% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
NVD 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N

Affected products

  • B&R Automation Studio

Classification

Weakness
  • CWE-326 Inadequate Encryption Strength
  • CWE-295 Improper Certificate Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.