dbcve.org
2tma310010b0001 FirmwareOperating system · Abb

CVE-2024-4008

HIGH · 8.8 CVSS v3.1 Published 2024-06-05
Fix available
A fix is available. Upgrade to 1.02 or later.
See remediation →
93/100
Remediation priority · Urgent
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
FDSK Leak in ABB, Busch-Jaeger, FTS Display (version 1.00) and BCU (version 1.3.0.33) allows attacker to take control via access 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

This is a hardcoded credential (FDSK/Factory Default Security Key) vulnerability in ABB, Busch-Jaeger FTS Display v1.00 and BCU v1.3.0.33 building automation devices. An attacker with local access to the KNX bus can exploit the leaked default key to take full control of the affected devices, potentially impacting building management systems including HVAC, lighting, and security controls.

MitigationContact ABB/Busch-Jaeger for available firmware updates that address the leaked FDSK; if no update exists, implement network segmentation to isolate the KNX bus from untrusted networks and restrict physical access to bus infrastructure.

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

CVSS:3.1/AV:A/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 the device model
    Locate the device label or use the device's web interface, management console, or documentation to confirm the exact model number. Look for model identifiers such as 2tma310010b0001, 2tma310011b0001, 2tma310011b0002, 2tma310010b0003, or 2tma310011b0003.
    Affected if The device model matches one of the five listed ABB 2tma3100* variants.
  2. Check the installed firmware version
    Access the device's admin interface, use the manufacturer's diagnostic tool, or consult the device status page to retrieve the current firmware version. Compare it against the affected threshold of version 1.02.
    Affected if The firmware version is below 1.02 (for example, 1.00, 1.01, or any version number less than 1.02).
  3. Verify KNX security configuration
    Access the device's KNX settings or security configuration panel. Look for the FDSK (Factory Default Security Key) configuration or KNX IP Security settings. Check whether the default factory key is still configured or if a custom key has been applied.
    Affected if The device is using the factory default FDSK or has KNX security disabled with default credentials in use.
  4. Assess KNX bus accessibility
    Review network segmentation and physical access controls around the KNX bus infrastructure. Determine if untrusted network segments or unauthorized personnel can access the KNX bus or device management interfaces.
    Affected if The KNX bus or device management interface is accessible from untrusted networks or without proper access controls.

The environment is affected if any ABB 2tma3100* device is running firmware below version 1.02 and is still using the factory default FDSK with accessible KNX bus connections.

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

Contact ABB/Busch-Jaeger for available firmware updates that address the leaked FDSK; if no update exists, implement network segmentation to isolate the KNX bus from untrusted networks and restrict physical access to bus infrastructure.

Recommended fix High confidence

Firmware version 1.02 or later for affected 2tma31001x device variants

  1. Identify the specific ABB, Busch-Jaeger, FTS Display or BCU device model in your environment from the affected product list (2tma310010b0001, 2tma310011b0001, 2tma310011b0002, 2tma310010b0003, or 2tma310011b0003)
  2. Check the current firmware version installed on each device
  3. Download the firmware version 1.02 or later from the official ABB source at search.abb.com
  4. Follow ABB's standard firmware update procedure for the specific device model, typically involving connecting via USB or network to the device's management interface
  5. After upgrade, verify the firmware version has been successfully updated to 1.02 or later
  6. Ensure the device is reconnected to the KNX Bus-System and functioning normally

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

Fix this in 2tma310010b0001 Firmware 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 the upgrade done

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-2024-4008 — 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-4008 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