dbcve.org
2tma310010b0001 FirmwareOperating system · Abb

CVE-2024-4009

HIGH · 7.8 CVSS v3.1 Published 2024-06-05
Fix available
A fix is available. Upgrade to 1.02 or later.
See remediation →
80/100
Remediation priority · High
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
Replay Attack in ABB, Busch-Jaeger, FTS Display (version 1.00) and BCU (version 1.3.0.33) allows attacker to capture/replay KNX telegram to local KNX Bus-System

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

A replay attack vulnerability in ABB and Busch-Jaeger KNX devices (FTS Display v1.00 and BCU v1.3.0.33) allows unauthenticated attackers to capture valid KNX telegrams from the local KNX bus and replay them to execute unauthorized commands on building automation systems.

MitigationApply vendor-provided firmware updates to affected devices; implement network segmentation to isolate KNX bus from untrusted networks and monitor for anomalous repeated telegrams.

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
2tma310010b0001 FirmwareOperating system
Affected:< 1.02
2tma310011b0001 FirmwareOperating system
Affected:< 1.02
2tma310011b0002 FirmwareOperating system
Affected:< 1.02
2tma310010b0003 FirmwareOperating system
Affected:< 1.02
2tma310011b0003 FirmwareOperating system
Affected:< 1.02

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 affected ABB device models on the network
    Inventory KNX devices on the network and identify if any match these model numbers: 2tma310010b0001, 2tma310011b0001, 2tma310011b0002, 2tma310010b0003, 2tma310011b0003
    Affected if Any of these specific ABB device models are present on the KNX bus
  2. Check firmware version of identified devices
    Access the device configuration or management interface and retrieve the current firmware version. Compare against the affected range: < 1.02
    Affected if The device firmware version is below 1.02
  3. Verify device type is FTS Display or BCU
    Check the device documentation or management interface to confirm the device is an FTS Display v1.00 or BCU v1.3.0.33
    Affected if The device is an FTS Display or BCU with vulnerable firmware
  4. Assess KNX bus network exposure
    Review network segmentation configuration to determine if the KNX bus or IP gateway is accessible from untrusted network segments
    Affected if The KNX bus is reachable from untrusted or external networks without proper isolation
  5. Monitor for repeated KNX telegrams
    Use a KNX protocol analyzer or intrusion detection system to inspect bus traffic for duplicate or rapid replay of identical telegrams
    Affected if Duplicate or unusually repeated KNX telegrams are observed on the bus

A user is affected if they have any of the listed ABB device models (2tma3100xx) running firmware below version 1.02, particularly if the KNX bus is accessible from untrusted networks where an attacker could capture and replay telegrams.

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 1.02 or later
Fixed in 1.02
Interim mitigation

Apply vendor-provided firmware updates to affected devices; implement network segmentation to isolate KNX bus from untrusted networks and monitor for anomalous repeated telegrams.

Recommended fix High confidence

Firmware version 1.02 for affected 2tma31001x product variants

  1. Identify the specific ABB Busch-Jaeger device model (2tma310010b0001, 2tma310011b0001, 2tma310011b0002, 2tma310010b0003, or 2tma310011b0003) from the affected product list
  2. Check the current firmware version of the device through the device management interface or Busch-Jaeger configuration tool
  3. Download the firmware version 1.02 from ABB's official support portal at search.abb.com or through authorized ABB/Busch-Jaeger channels
  4. Follow ABB's standard firmware upgrade procedure for the specific device model - typically via the device's web interface, commissioning tool, or USB update method
  5. Verify the firmware has been successfully updated to version 1.02 or later

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

Fix this in 2tma310010b0001 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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