Security readout for executives and security teams
Plain-English summary
Radare2 can crash when parsing a malicious Mach-O file because its Mach-O rebase handling can divide by zero. Business urgency is highest where radare2 processes files from untrusted sources, such as malware triage, reverse engineering, or automated analysis pipelines.
Executive priority
Prioritize remediation for security labs, CI systems, or customer-facing analysis services that process unknown binaries. For developer-only local use, urgency is lower but updating is still appropriate because crafted files can disrupt analysis workflows.
Technical view
The CVE describes CWE-369 in radare2's Mach-O parser, specifically rebase_buffer. Affected evidence names radare2 5.3.0-git 26142 and a fixing commit reference. The stated impact is denial of service from crafted input; the bundled CVSS vector rates it critical, but the public description does not substantiate remote code execution.
Likely exposure
Exposure is likely limited to systems running affected radare2 builds that parse Mach-O files, especially automated services accepting external samples. Default product status is listed as unaffected except for the named vulnerable build evidence.
Exploitation context
The source bundle says attackers can create malicious inputs causing denial of service. It does not show CISA KEV listing or cite active exploitation. Treat exploitation status as unconfirmed, not known exploited.
Researcher notes
Evidence is narrow: the CVE names a division-by-zero in rebase_buffer and links an issue and commit. The provided data supports denial of service, not broader confidentiality or integrity compromise despite the critical CVSS vector.
Mitigation direction
- Upgrade to a vendor-fixed radare2 build containing the referenced fix.
- Check radare2 guidance for the fixed release mapping before production rollout.
- Avoid automatic parsing of untrusted Mach-O files until updated.
- Sandbox radare2 analysis jobs with least privilege and resource limits.
- Restrict file intake paths that can reach affected radare2 parsers.
Validation and detection
- Inventory radare2 deployments and embedded package copies.
- Confirm versions against 5.3.0-git 26142 and the fixing commit.
- Identify workflows that parse externally supplied Mach-O files.
- Review crash logs from radare2-based analysis services.
- Track vendor issue and commit references for patch confirmation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-369: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2021-32494 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 10 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H3.96Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
10CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Divide By Zero
Divide By Zero represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.