Security readout for executives and security teams
Plain-English summary
CVE-2017-9520 is a crash bug in radare2 1.5.0. A specially crafted Android DEX file can trigger a use-after-free in configuration handling and crash the application. The sources show denial of service, not code execution or data theft.
Executive priority
Prioritize remediation for teams that analyze untrusted Android files. The main business risk is disruption of reverse-engineering or malware-analysis workflows, not a confirmed compromise path.
Technical view
The CVE describes a use-after-free in r_config_set within libr/config/config.c in radare2 1.5.0, reachable when processing a crafted DEX file. The public references include a GitHub issue and fixing commit. CVSS, CWE, and structured affected-product metadata are incomplete in the provided record.
Likely exposure
Exposure is most likely where radare2 1.5.0 processes untrusted or third-party DEX files, such as malware analysis, reverse engineering, or automated file triage pipelines.
Exploitation context
No KEV listing or provided source indicates active exploitation. The documented impact is application denial of service through a crafted DEX file, with no source-backed evidence of privilege escalation or remote code execution.
Researcher notes
The record lacks CVSS, CWE, and precise CPE data. The affected version is stated in the description as radare2 1.5.0. Treat broader version exposure as unconfirmed unless validated against upstream commits or release history.
Mitigation direction
- Upgrade from radare2 1.5.0 to a maintained release containing the referenced fix.
- Check radare2 vendor guidance and release notes for the fixed version boundary.
- Analyze untrusted DEX files only in isolated, disposable environments.
- Avoid production dependency on radare2 1.5.0 for automated file triage.
Validation and detection
- Inventory systems and pipelines using radare2, especially version 1.5.0.
- Confirm whether DEX files from untrusted sources are processed automatically.
- Verify deployed radare2 builds include the referenced GitHub fix.
- Review crash handling so analyzer failures do not disrupt broader workflows.
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-2017-9520 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/f85bc674b2a2256a364fe796351bc1971e106005CVE reference · x_refsource_CONFIRM
- https://github.com/radare/radare2/issues/7698CVE reference · x_refsource_CONFIRM
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.