dbcve.org
Industrial Automation AprolApplication · Br Automation

CVE-2019-19875

CRITICAL · 9.8 CVSS v3.1 Published 2020-11-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
An issue was discovered in B&R Industrial Automation APROL before R4.2 V7.08. Arbitrary commands could be injected (using Python scripts) via the AprolCluster script that is invoked via sudo and thus executes with root privileges, a different vulnerability than CVE-2019-16364.

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

A command injection vulnerability in B&R Industrial Automation APROL allows attackers to execute arbitrary commands through Python scripts invoked via the AprolCluster script. The script runs with root privileges through sudo, enabling full system compromise.

MitigationUpgrade APROL to R4.2 V7.08 or later. Review and restrict sudo configurations for the AprolCluster script to limit privileges and prevent unauthorized command execution.

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
Industrial Automation AprolApplication
Affected:< r4.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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if APROL is installed
    Look for B&R Industrial Automation APROL installation directories, typically under /opt/aprol or /usr/local/aprol, or check for APROL-related services running on the system
    Affected if APROL software is present on the system
  2. Check APROL version
    Locate the APROL version information, typically found in version files, about dialogs, or by running 'aprolversion' or similar command if available. Compare against the affected version range (anything before r4.2 or R4.2 V7.08)
    Affected if Installed version is r4.2 or earlier, or specifically earlier than R4.2 V7.08
  3. Locate the AprolCluster script
    Search for the AprolCluster script in common paths such as /usr/local/bin/AprolCluster, /opt/aprol/bin/AprolCluster, or within APROL installation directories
    Affected if The AprolCluster script exists on the system
  4. Inspect sudo configuration for AprolCluster
    Run 'sudo -l' or check /etc/sudoers for entries related to AprolCluster, looking for rules that permit execution with elevated privileges
    Affected if The AprolCluster script is configured to run with sudo and root privileges without full authentication requirements

The environment is affected if APROL is installed with a version earlier than r4.2 (or R4.2 V7.08) and the AprolCluster script exists with sudo privileges that could allow command injection.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade APROL to R4.2 V7.08 or later. Review and restrict sudo configurations for the AprolCluster script to limit privileges and prevent unauthorized command execution.

Recommended fix High confidence

APROL R4.2 V7.08 or later

  1. Schedule a maintenance window for the APROL system upgrade
  2. Backup the current APROL configuration, projects, and any custom scripts
  3. Obtain the official APROL R4.2 V7.08 or later release from B&R Industrial Automation (www.br-automation.com)
  4. Verify the integrity of the upgrade package using checksums provided by B&R
  5. Stop all APROL services and processes according to B&R documentation
  6. Install the APROL R4.2 V7.08 upgrade following the official B&R upgrade procedure
  7. After installation, verify that the AprolCluster script no longer allows arbitrary command injection
  8. Restore the backed-up configuration and projects
Caveat Upgrading a SCADA/ICS system may affect compatibility with existing projects, custom scripts, or integrated systems; thoroughly test in a non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Industrial Automation Aprol Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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