dbcve.org
Automation RuntimeApplication · Br Automation

CVE-2024-5800

HIGH · 7.5 CVSS v3.1 Published 2024-08-12
Fix available
A fix is available. Upgrade to 6.0.2 or later.
See remediation →
84/100
Remediation priority · High
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
Diffie-Hellman groups with insufficient strength are used in the SSL/TLS stack of B&R Automation Runtime versions before 6.0.2, allowing a network attacker to decrypt the SSL/TLS communication.

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 · moderate confidence

B&R Automation Runtime versions before 6.0.2 use cryptographically weak Diffie-Hellman groups in their SSL/TLS implementation, allowing a network attacker to perform a downgrade attack (similar to Logjam) and force use of insufficiently strong DH parameters, enabling decryption of TLS communications.

MitigationUpgrade B&R Automation Runtime to version 6.0.2 or later. If immediate upgrade is not feasible, verify that only DH groups of 2048-bit or greater are accepted in TLS configurations, and disable support for export-grade or legacy DH groups.

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:< 6.0.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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 installed B&R Automation Runtime version
    Locate the Automation Runtime installation directory and check the version information file, or use the system information utility provided by B&R to retrieve the runtime version number
    Affected if The installed version is before 6.0.2 (e.g., 6.0.1, 5.x, or earlier)
  2. Locate TLS configuration for Automation Runtime
    Find the SSL/TLS configuration file or settings panel within the Automation Runtime installation, typically in the runtime configuration directory or system settings
    Affected if The TLS configuration file exists and is accessible for inspection
  3. Inspect DH group configuration settings
    Examine the TLS configuration for Diffie-Hellman group settings, looking for parameters that specify allowed DH group sizes or explicit DH parameters
    Affected if The configuration shows support for DH groups smaller than 2048-bit, or no minimum DH group size is enforced
  4. Check for export-grade or legacy cipher support
    Review the TLS cipher suite configuration for the presence of export-grade ciphers (such as EXP-RC4-MD5, EXP-DES-CBC-SHA) or legacy DH groups (512-bit, 768-bit, 1024-bit)
    Affected if Export-grade ciphers or weak DH groups (below 2048-bit) are listed as enabled or accepted

A system is affected if B&R Automation Runtime version is below 6.0.2 AND the TLS configuration accepts or enables Diffie-Hellman groups smaller than 2048-bit or export-grade cipher suites.

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
Upgrade available Upgrade to 6.0.2 or later
Fixed in 6.0.2
Interim mitigation

Upgrade B&R Automation Runtime to version 6.0.2 or later. If immediate upgrade is not feasible, verify that only DH groups of 2048-bit or greater are accepted in TLS configurations, and disable support for export-grade or legacy DH groups.

Recommended fix High confidence

Automation Runtime 6.0.2

  1. Consult B&R Automation documentation for upgrading Automation Runtime to version 6.0.2
  2. Obtain the Automation Runtime 6.0.2 installer from the official B&R website or authorized distribution channel
  3. Review release notes for version 6.0.2 to understand any changes or requirements
  4. Create a backup of the current automation project and configuration
  5. Follow B&R's standard upgrade procedure for Automation Runtime, which typically involves stopping the runtime, installing the update, and restarting the runtime
  6. After upgrade, verify that SSL/TLS communications are functioning correctly
  7. Confirm that the new version no longer uses weak Diffie-Hellman groups

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

Fix this in Automation Runtime Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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