Security readout for executives and security teams
Plain-English summary
CVE-2018-11382 is a radare2 2.5.0 crash issue. A specially crafted binary file can make the application read outside heap bounds and crash. Business impact is mainly denial of service for analysts or automated binary-processing systems, not proven data theft or code execution based on the provided sources.
Executive priority
Prioritize remediation where radare2 is used in automated or externally fed analysis systems. For isolated analyst workstations, handle through normal patch management unless crashes are disrupting operations.
Technical view
The issue is in radare2 2.5.0, specifically the _inst__sts() function. The CVE describes a heap-based out-of-bounds read triggered by a crafted binary file, resulting in application crash. The provided references include a GitHub issue and upstream commit, but no CVSS vector, CWE mapping, or named fixed release.
Likely exposure
Exposure is most likely where radare2 2.5.0 processes untrusted binaries, especially automated malware triage, reverse-engineering, or upload-analysis workflows. Workstations using radare2 only on trusted files have lower practical exposure.
Exploitation context
The source bundle does not show CISA KEV listing or other evidence of active exploitation. The attack condition is crafted-file processing, so exploitation depends on convincing or causing radare2 to analyze a malicious binary.
Researcher notes
Evidence is limited to the CVE description, GitHub issue, and commit reference. The provided sources identify the vulnerable function and crash class, but do not provide CVSS, CWE, broad exploit reports, or a named fixed version.
Mitigation direction
- Identify radare2 2.5.0 installations and replace them with a vendor-supported fixed build.
- Check whether deployed builds include upstream commit d04c78773f6959bcb427453f8e5b9824d5ba9eff.
- Restrict automated radare2 processing to sandboxed environments for untrusted binaries.
- Monitor vendor guidance for the fixed release containing the referenced commit.
Validation and detection
- Inventory radare2 versions across analyst workstations, CI jobs, and malware-analysis pipelines.
- Confirm whether any service accepts external binaries for radare2-based analysis.
- Review crash telemetry for radare2 failures during binary parsing.
- Verify remediation by checking build provenance against the referenced upstream fix.
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-11382 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/issues/10091CVE reference · x_refsource_MISC
- https://github.com/radare/radare2/commit/d04c78773f6959bcb427453f8e5b9824d5ba9effCVE 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.