Busybox: divide-by-zero in the volume_id fat prober via a zero sectors_per_cluster value
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Red Hat | Red Hat Hardened Images | affected |
|
||||||
| Red Hat | Red Hat Enterprise Linux 6 | unknown | — |
No data.
No data.
No data available yet.
Vendor Workaround
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.187% probability within 30 days)
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A flaw was found in BusyBox. The volume identification component fails to properly validate cluster parameters when analyzing specially formatted FAT filesystems. An attacker able to present a crafted storage device or disk image can trigger a divide-by-zero condition when partition scanning utilities inspect the volume. This issue causes the probing utilities to crash unexpectedly, resulting in a Denial of Service (DoS) that can disrupt device discovery and system boot operations. | |
| Title | Busybox: divide-by-zero in the volume_id fat prober via a zero sectors_per_cluster value | |
| First Time appeared |
Redhat
Redhat hummingbird Redhat rhel Els |
|
| Weaknesses | CWE-369 | |
| CPEs | cpe:/a:redhat:hummingbird:1 cpe:/o:redhat:rhel_els:6 |
|
| Vendors & Products |
Redhat
Redhat hummingbird Redhat rhel Els |
|
| References |
| |
| Metrics |
cvssV3_1
|