CVE-2019-19102
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 · uneditedA 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.
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 confidenceA directory traversal vulnerability (zip slip) in SharpZipLib within B&R Automation Studio's upgrade service allows unauthenticated attackers to write files to arbitrary local directories by extracting malicious archive entries containing path traversal sequences (e.g., ../../../').
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>= 4.0, <= 4.0.32.15>= 4.1, <= 4.1.17.113>= 4.2, <= 4.2.14.119CVSS 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Automation Studio versionLocate the B&R Automation Studio installation on the system and retrieve its version information, typically available in the application properties, 'About' dialog, or installation directory metadataAffected if The installed version falls within any of these ranges: 4.0.0 to 4.0.32.15, 4.1.0 to 4.1.17.113, or 4.2.0 to 4.2.14.119
-
Confirm upgrade service is presentVerify that the B&R Automation Studio upgrade service component is installed or enabled on the system; this service handles archive extraction for software updatesAffected if The upgrade service is installed or active on the system alongside a vulnerable Automation Studio version
-
Check for SharpZipLib library usageInspect the Automation Studio installation directories or application components for the presence of SharpZipLib library files, which handle ZIP archive extraction in the upgrade processAffected if SharpZipLib library is present and used by the upgrade service in a version that falls within the affected Automation Studio version ranges
A system is affected if it runs B&R Automation Studio version 4.0.0 through 4.0.32.15, 4.1.0 through 4.1.17.113, or 4.2.0 through 4.2.14.119 with the upgrade service enabled and SharpZipLib in use for archive extraction
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade B&R Automation Studio to a patched version or apply vendor-provided updates; implement and enforce strict path validation to verify extracted file paths stay within the intended target directory before extraction.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19102 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-19102 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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