dbcve.org
Automation RuntimeApplication · Br Automation

CVE-2024-0323

CRITICAL · 9.8 CVSS v3.1 Published 2024-02-05
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
The FTP server used on the B&R Automation Runtime supports unsecure encryption mechanisms, such as SSLv3, TLSv1.0 and TLS1.1. An network-based attacker can exploit the flaws to conduct man-in-the-middle attacks or to decrypt communications between the affected product clients.

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

The FTP server component in B&R Automation Runtime supports deprecated and cryptographically weak encryption protocols (SSLv3, TLSv1.0, TLS1.1). These outdated protocols contain known vulnerabilities that allow a network-based attacker to perform man-in-the-middle attacks or decrypt intercepted communications, exposing sensitive data in transit.

MitigationDisable SSLv3, TLSv1.0, and TLSv1.1 on the FTP server and enforce TLSv1.2 or higher. If the affected product does not support modern TLS versions, contact B&R for a firmware update.

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
Automation RuntimeApplication
Affected:<= i4.93

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. Verify FTP server is enabled
    Inspect the Automation Runtime configuration or project settings to confirm the FTP server component is active. Check runtime logs or system services for an active FTP listener on ports 20/21 or configured FTP ports.
    Affected if FTP server is enabled and running on the affected Automation Runtime version (<= i4.93)
  2. Confirm Automation Runtime version
    Locate the Automation Runtime installation or system information panel. Check the runtime version displayed in the engineering software (Automation Studio) or on the controller's system info screen.
    Affected if Version is i4.93 or earlier (any version <= i4.93)
  3. Inspect TLS/SSL protocol settings for FTP
    Access the FTP server configuration in Automation Studio or the controller's security settings. Review the enabled protocol list for the FTP service to identify if SSLv3, TLSv1.0, or TLSv1.1 are listed as allowed options.
    Affected if SSLv3, TLSv1.0, or TLSv1.1 appear in the enabled protocols list for the FTP server
  4. Check cipher suite configuration
    Examine the cipher suite settings associated with the FTP server component. Look for weak or deprecated cipher configurations that rely on the affected protocol versions.
    Affected if Weak cipher suites tied to SSLv3, TLSv1.0, or TLSv1.1 are configured or selected by default

A system is affected if it runs Automation Runtime version <= i4.93 with the FTP server enabled and has SSLv3, TLSv1.0, or TLSv1.1 protocols available or configured for the FTP service.

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

Disable SSLv3, TLSv1.0, and TLSv1.1 on the FTP server and enforce TLSv1.2 or higher. If the affected product does not support modern TLS versions, contact B&R for a firmware update.

Recommended fix Moderate confidence

Automation Runtime > i4.93 (contact B&R for exact latest stable version)

  1. 1. Identify all B&R Automation Runtime deployments currently running version i4.93 or earlier
  2. 2. Contact B&R Automation technical support or check their official website for the latest Automation Runtime version
  3. 3. Before upgrading, backup all current configurations and project data
  4. 4. Plan maintenance window as upgrade may require system restart
  5. 5. Obtain the upgrade package from official B&R sources (www.br-automation.com)
  6. 6. Follow B&R's official upgrade procedure documentation for Automation Runtime
  7. 7. After upgrade, verify the FTP server no longer accepts SSLv3, TLSv1.0, or TLS1.1 connections
  8. 8. Test that legitimate clients can connect using TLSv1.2 or higher
Caveat Review B&R release notes for any breaking changes between i4.93 and the target version; some legacy client applications may need updating if they only support older TLS versions

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

Fix this in Automation Runtime Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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