CVE-2024-48989
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 · uneditedA vulnerability in the PROFINET stack implementation of the IndraDrive (all versions) of Bosch Rexroth allows an attacker to cause a denial of service, rendering the device unresponsive by sending arbitrary UDP messages.
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 confidenceA denial-of-service vulnerability exists in the PROFINET stack implementation of Bosch Rexroth IndraDrive drives across all versions. Attackers can render the device unresponsive by sending arbitrary UDP messages to the affected system, causing the PROFINET stack to fail or become unresponsive.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the device management interface or check the physical device nameplate/label for the model number. Confirm it is a Bosch Rexroth IndraDrive drive.Affected if The device is a Bosch Rexroth IndraDrive drive of any firmware version.
-
Verify PROFINET stack is enabledAccess the device configuration settings (via the drive's web interface, parameter list, or engineering software). Check if PROFINET communication or the PROFINET stack is activated or configured.Affected if PROFINET stack is enabled or configured on the device.
-
Confirm UDP network accessibilityCheck network configuration to determine if the device has an IP address on the operational network and if UDP port 34980 (PROFINET discovery) or port 34981 (PROFINET real-time) is accessible from untrusted network segments.Affected if The device is reachable via UDP on ports 34980/34981 from network segments where arbitrary packets could be sent.
-
Check firmware version if accessibleIf the firmware version is readable via the device's web interface, engineering software, or parameter read-out, note the version for inventory purposes. Note that all versions are affected per the CVE.Affected if Any firmware version is installed on a Bosch Rexroth IndraDrive with PROFINET enabled.
You are affected if you have a Bosch Rexroth IndraDrive drive with PROFINET stack enabled and the device's UDP ports (34980/34981) are accessible on your network.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply vendor-supplied firmware updates when available; until then, implement network segmentation and UDP traffic filtering to restrict unauthorized packets from reaching the IndusDrive device.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-48989 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-48989 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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