dbcve.org
Industrial Automation AprolApplication · Br Automation

CVE-2019-19874

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. Some web scripts in the web interface allowed injection and execution of arbitrary unintended commands on the web server, 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

This is a command injection vulnerability in B&R Industrial Automation APROL's web interface. Attackers can inject and execute arbitrary operating system commands on the web server through vulnerable web scripts. The vulnerability affects versions prior to R4.2 V7.08 and is distinct from CVE-2019-16364.

MitigationApply the APROL R4.2 V7.08 or later patch to remediate the command injection vulnerability in the web interface. As a critical industrial control system, the update should be tested in a non-production environment first and deployed during planned maintenance windows.

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 B&R APROL is installed
    Check system inventory, installed programs, or look for APROL-related services running on the system. On Windows, check Program Files for B&R folders; on Linux, check /opt or common application directories for APROL components.
    Affected if B&R Industrial Automation APROL software is present on the system
  2. Check the installed APROL version
    Locate the APROL version information in the system. This is typically found in the program files, About dialog within the application, or version files in the APROL installation directory. Compare the version number to the affected range (prior to R4.2 V7.08).
    Affected if The installed version is earlier than R4.2 V7.08 or the version cannot be determined to be at or above V7.08
  3. Verify the web interface component is enabled
    Check if the APROL web server or web interface service is running and accessible. Look for web server processes related to APROL (typically on ports 80/443 or custom ports). Try accessing the web interface URL if known.
    Affected if The APROL web interface is accessible and running
  4. Inspect web scripts for command injection points
    If you have access to the web application source or scripts, examine the input validation in web scripts. Look for areas where user input might be passed to system commands without proper sanitization. This typically requires access to the web application files.
    Affected if Web scripts exist that accept user input and pass it to system command execution functions without validation

A system is affected if it runs B&R Industrial Automation APROL with a version prior to R4.2 V7.08 and has the web interface component enabled.

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

Apply the APROL R4.2 V7.08 or later patch to remediate the command injection vulnerability in the web interface. As a critical industrial control system, the update should be tested in a non-production environment first and deployed during planned maintenance windows.

Recommended fix High confidence

APROL R4.2 V7.08 or later

  1. Schedule a maintenance window for the industrial control system upgrade
  2. Back up all critical APROL configurations, projects, and data before proceeding
  3. Download APROL R4.2 V7.08 or later upgrade package from official B&R Industrial Automation sources (www.br-automation.com)
  4. Follow B&R's official upgrade procedure documented in the APROL R4.2 release notes
  5. After upgrade, verify the web interface is functional and the vulnerability is resolved
  6. Test that command injection is no longer possible in web scripts
Caveat Industrial control system upgrades may require downtime and could affect running processes; validate all control logic and HMI configurations after upgrade in a test environment before production deployment

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

Fix this in Industrial Automation Aprol Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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