CVE-2019-19108
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 · uneditedAn 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 to 4.63, 4.72 and above allows unauthenticated users to modify the configuration of B&R products via SNMP.
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 confidenceAn authentication weakness in the SNMP service of B&R Automation Runtime allows unauthenticated attackers to modify device configuration. The SNMP service lacks proper authentication enforcement, enabling remote configuration changes without credentials.
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>= 3.08, <= 3.10>= 4.00, <= 4.03>= 4.04, <= 4.63= 2.96= 3.00= 3.01= 3.06= 3.07= 4.72>= 4.0.0, <= 4.6.4= 2.7= 3.0.71= 3.0.80= 3.0.81= 3.0.90= 4.7.2CVSS 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
- Low
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify B&R Automation product installationDetermine if B&R Automation Runtime or Automation Studio is installed on the system by reviewing installed software or project dependenciesAffected if Either B&R Automation Runtime or Automation Studio is present
-
Check Automation Runtime versionLocate and inspect the Automation Runtime version information through system diagnostics, device management interface, or project configuration filesAffected if The installed version matches one of the affected ranges: >= 3.08 to <= 3.10; >= 4.00 to <= 4.03; >= 4.04 to <= 4.63; = 2.96; = 3.00; = 3.01; = 3.06; = 3.07; or = 4.72
-
Check Automation Studio versionLocate and inspect the Automation Studio version through the development environment about dialog or installed programs listAffected if The installed version matches one of the affected ranges: >= 4.0.0 to <= 4.6.4; = 2.7; = 3.0.71; = 3.0.80; = 3.0.81; = 3.0.90; or = 4.7.2
-
Verify SNMP service statusCheck if the SNMP service is enabled or configured on the B&R device or project through device configuration settings, network service listings, or SNMP management toolsAffected if SNMP service is actively running or configured on the affected product installation
If either B&R Automation Runtime or Automation Studio is installed with a version matching the affected ranges AND the SNMP service is enabled or configured, the environment is vulnerable to unauthenticated configuration changes via CVE-2019-19108.
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 dataApply vendor-supplied patches or firmware updates to all affected B&R Automation Runtime versions. If patching is immediately infeasible, restrict SNMP service access via network segmentation and firewall rules to prevent unauthenticated access.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19108 — 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-19108 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