Service interruption via remotely triggered deadlock
Published Feb 12, 2025 · Updated Feb 13, 2025
A deadlock in Dell BSAFE SSL-J before 6.6 and 7.0 through 7.2 allows remote attackers to interrupt service over a network. Dell identifies the failure as a deadlock but has not published the affected code path, request shape, or locking operation. No authentication or user interaction is required, but high attack complexity limits reachability; successful exploitation makes the integrating application unavailable.
Summary
What happened
A deadlock in Dell BSAFE SSL-J before 6.6 and 7.0 through 7.2 allows remote attackers to interrupt service over a network. Dell identifies the failure as a deadlock but has not published the affected code path, request shape, or locking operation. No authentication or user interaction is required, but high attack complexity limits reachability; successful exploitation makes the integrating application unavailable.
The record
- CVE
- CVE-2024-29172
- Published
- Feb 12, 2025
- Updated
- Feb 13, 2025
- Vendor
- Dell
- Product
- Dell BSAFE SSL-J
- Classifications
- CWE-833, CWE-667, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 12, 2025CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=7.0 <=7.2
- Affected versionversion=N/A <6.6
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo