Security readout for executives and security teams
Plain-English summary
CVE-2018-11384 is a crash vulnerability in radare2 2.5.0 when it processes a specially crafted ELF file. Business impact is mainly disruption to reverse-engineering, malware-analysis, or automated file-inspection workflows. The provided sources do not show code execution or confirmed active exploitation.
Executive priority
Treat this as a targeted operational-risk issue, not a broad enterprise emergency. Prioritize remediation where radare2 processes untrusted binaries automatically or supports security operations that cannot tolerate crashes.
Technical view
The issue is a heap-based out-of-bounds read in radare2's sh_op() function. A crafted ELF file can trigger an application crash, producing denial of service. Public references include a GitHub issue and commit, but the bundle does not provide CVSS, CWE, or a named fixed release.
Likely exposure
Exposure is most likely where radare2 2.5.0 analyzes untrusted ELF files, especially malware labs, triage sandboxes, CI pipelines, and reverse-engineering workstations. General enterprise exposure is limited unless radare2 is embedded in automated services.
Exploitation context
The source bundle describes remote attackers causing denial of service through a crafted ELF file. CISA KEV is false, and no cited source in the bundle confirms active exploitation in the wild.
Researcher notes
Evidence is sparse: the CVE description names radare2 2.5.0, sh_op(), crafted ELF input, heap out-of-bounds read, and crash. The bundle does not include CVSS, CWE, exploit maturity, or a specific fixed version.
Mitigation direction
- Inventory systems and containers for radare2 2.5.0.
- Upgrade radare2 to a vendor-fixed build when available.
- Review the referenced upstream commit and issue for fix provenance.
- Avoid processing untrusted ELF files with affected builds.
- Isolate automated analysis workers that must handle untrusted samples.
Validation and detection
- Confirm whether radare2 2.5.0 is installed or embedded.
- Identify workflows that pass external ELF files to radare2.
- Check whether the build includes commit 77c47cf873dd55b396da60baa2ca83bbd39e4add.
- Verify vendor release notes before marking the issue remediated.
- Review crash telemetry from analysis systems for related failures.
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.
CVE-2018-11384 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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 and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/radare/radare2/commit/77c47cf873dd55b396da60baa2ca83bbd39e4addCVE reference · x_refsource_MISC
- https://github.com/radare/radare2/issues/9903CVE reference · x_refsource_MISC
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.
