Security readout for executives and security teams
Plain-English summary
CVE-2018-11381 is a denial-of-service flaw in radare2 2.5.0. A specially crafted binary file can make the application crash. The business risk is mainly disruption to analysts, automation, or services that process untrusted binaries with this version.
Executive priority
Treat as a targeted availability risk for security tooling rather than an enterprise-wide emergency. Prioritize remediation where radare2 processes external or adversary-supplied files.
Technical view
The issue is in radare2 2.5.0 string_scan_range(), where crafted input can trigger a heap-based out-of-bounds read and application crash. The provided sources do not identify code execution, a CVSS score, CWE mapping, or a fixed release version beyond a referenced upstream commit.
Likely exposure
Exposure is most likely on analyst workstations, malware-analysis systems, CI pipelines, or backend services that run radare2 2.5.0 against untrusted binary files.
Exploitation context
The CVE record describes remote attackers causing a crash via crafted binary files. KEV is false, and the provided sources do not state active exploitation in the wild.
Researcher notes
Evidence is limited to the CVE description, GitHub issue, and upstream commit reference. The affected version named is radare2 2.5.0. Fixed release, CVSS, CWE, and real-world exploitation evidence are not provided in the source bundle.
Mitigation direction
- Inventory systems and workflows using radare2 2.5.0.
- Upgrade to a radare2 release containing the referenced upstream fix.
- Avoid processing untrusted binaries with vulnerable radare2 builds.
- Run binary-analysis workflows inside sandboxed, resource-limited environments.
- Check radare2 vendor guidance for the exact fixed release.
Validation and detection
- Confirm installed radare2 versions across workstations, servers, and pipelines.
- Verify deployed source or package includes the referenced upstream commit.
- Review analysis-service logs for radare2 crashes on binary input.
- Confirm untrusted-file analysis runs in isolated environments.
- Track vendor advisories for fixed-version 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.
CVE-2018-11381 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/3fcf41ed96ffa25b38029449520c8d0a198745f3CVE reference · x_refsource_MISC
- https://github.com/radare/radare2/issues/9902CVE 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.