dbcve.org
Industrial Automation AprolApplication · Br Automation

CVE-2022-43764

CRITICAL · 9.8 CVSS v3.1 Published 2023-02-08
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
Insufficient validation of input parameters when changing configuration on Tbase server in B&R APROL versions < R 4.2-07 could result in buffer overflow. This may lead to Denial-of-Service conditions or execution of arbitrary code.

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

Insufficient validation of input parameters when changing configuration on the Tbase server in B&R APROL versions prior to R 4.2-07 allows buffer overflow exploitation. This could enable denial-of-service conditions or arbitrary code execution on the affected industrial control system.

MitigationUpgrade B&R APROL to version R 4.2-07 or later to obtain the patched Tbase server with proper input validation. Prior to upgrade, restrict network access to the Tbase server and monitor for unusual configuration change attempts.

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-07

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
    Locate APROL installation directories or check system inventory for Br Automation industrial automation software. Common locations include /opt/aprol or program files under B&R Automation.
    Affected if B&R APROL software is found on the system
  2. Determine installed APROL version
    Check version information in APROL installation directories, typically in a version file, about dialog, or system configuration. Look for version strings like R4.x or release numbers.
    Affected if Version is identified as lower than R 4.2-07 (for example, R4.2-06, R4.2, R4.1, etc.)
  3. Locate Tbase server component
    Identify the Tbase server process or service within the APROL installation. Tbase is a database server component used by APROL for configuration storage.
    Affected if Tbase server process or service is found running as part of APROL
  4. Verify Tbase server is network accessible
    Check network configuration, firewall rules, or service binding settings to determine if the Tbase server listens on network interfaces accessible to users or other systems.
    Affected if Tbase server is bound to network interfaces and accepts configuration change requests remotely
  5. Confirm configuration change capability
    Review access permissions and authentication settings for the Tbase server configuration interface to determine if unauthenticated or low-privilege users can submit configuration changes.
    Affected if Configuration parameters can be modified without proper input validation safeguards in place

If B&R APROL version R4.2-07 or later is not installed AND the Tbase server accepts remote configuration changes, the system is vulnerable to CVE-2022-43764 buffer overflow exploitation.

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 B&R APROL to version R 4.2-07 or later to obtain the patched Tbase server with proper input validation. Prior to upgrade, restrict network access to the Tbase server and monitor for unusual configuration change attempts.

Recommended fix High confidence

R 4.2-07

  1. 1. Back up all current APROL configuration data and project files before starting the upgrade process
  2. 2. Obtain the APROL R 4.2-07 upgrade package from the official B&R Automation website or your vendor distribution channel
  3. 3. Stop all running APROL services and the Tbase server
  4. 4. Run the APROL R 4.2-07 installer following the vendor's documented upgrade procedure
  5. 5. After installation, verify that the Tbase server starts successfully
  6. 6. Restore the backed-up configuration data
  7. 7. Validate that the configuration change functionality works correctly without errors
  8. 8. Confirm the installed version matches R 4.2-07 or later

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
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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