CVE-2019-19102
CVE-2019-19102 is a medium-severity vulnerability in Br-automation Automation Studio with a CVSS 3.x base score of 5.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-22.
Key facts
- Severity: Medium (CVSS 3.x base score 5.5)
- CVSS v2: 5.0
- EPSS exploit prediction: 1% (71st percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-22
- Affected product: Br-automation Automation Studio
- Published:
- Last modified:
Description
A directory traversal vulnerability in SharpZipLib used in the upgrade service in B&R Automation Studio versions 4.0.x, 4.1.x and 4.2.x allow unauthenticated users to write to certain local directories. The vulnerability is also known as zip slip.
Frequently asked questions
- What is CVE-2019-19102?
- A directory traversal vulnerability in SharpZipLib used in the upgrade service in B&R Automation Studio versions 4.0.x, 4.1.x and 4.2.x allow unauthenticated users to write to certain local directories. The vulnerability is also known as zip slip.
- How severe is CVE-2019-19102?
- CVE-2019-19102 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over local access with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is none, integrity high, and availability none.
- Is CVE-2019-19102 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (71st percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2019-19102?
- CVE-2019-19102 affects Br-automation Automation Studio. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2019-19102?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- When was CVE-2019-19102 published?
- CVE-2019-19102 was published on 2020-04-29 and last updated on 2026-06-17.
References
Affected products (1)
- cpe:2.3:a:br-automation:automation_studio:*:*:*:*:*:*:*:*
More vulnerabilities in Br-automation Automation Studio
- CVE-2019-19108 — Critical (CVSS 9.4): An authentication weakness in the SNMP service in B&R Automation Runtime versions 2.96, 3.00, 3.01, 3.06 to 3.10, 4.00…
- CVE-2024-0220 — High (CVSS 8.3): B&R Automation Studio Upgrade Service and B&R Technology Guarding use insufficient cryptography for communication to…
- CVE-2021-22282 — High (CVSS 8.3): Improper Control of Generation of Code ('Code Injection') vulnerability in B&R Industrial Automation Automation Studio…
- CVE-2020-24681 — High (CVSS 8.2): Incorrect Permission Assignment for Critical Resource vulnerability in B&R Industrial Automation Automation Studio…
- CVE-2019-19100 — High (CVSS 7.5): A privilege escalation vulnerability in the upgrade service in B&R Automation Studio versions 4.0.x, 4.1.x, 4.2.x, <…
- CVE-2021-22280 — High (CVSS 7.2): Improper DLL loading algorithms in B&R Automation Studio versions >=4.0 and <4.12 may allow an authenticated local…
All CVEs affecting Br-automation Automation Studio →
Other CWE-22 (Path Traversal) vulnerabilities
- CVE-2026-77312 — Critical (CVSS 10.0): Flyto2 Core is an execution kernel for automation and AI-agent workflows. Prior to 2.26.8, the earlier CVE-2026-67429…
- CVE-2026-121351 — Critical (CVSS 10.0): Adobe Connect is affected by an Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')…
- CVE-2026-121489 — Critical (CVSS 10.0): Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Apache Juneau. The…
- CVE-2026-122013 — Critical (CVSS 10.0): A vulnerability was detected in Comfast CF-WR632AX 2.6.0.1. Affected by this vulnerability is an unknown functionality…
- CVE-2026-61738 — Critical (CVSS 10.0): SOCFortress CoPilot focuses on providing a single pane of glass for all your security operations needs. Prior to…
- CVE-2026-112690 — Critical (CVSS 10.0): This issue was addressed with improved input validation. This issue is fixed in iOS 26.7.2 and iPadOS 26.7.2, iOS 27.2…