Security readout for executives and security teams
Plain-English summary
CVE-2020-27794 is a radare2 memory-management flaw. A vulnerable version may free the same memory twice, which can corrupt memory and potentially crash the program. The available sources say it was fixed in radare2 v4.4.0, but do not provide a CVSS score or evidence of active exploitation.
Executive priority
Treat this as a targeted maintenance issue, not an emergency, unless radare2 is used heavily on untrusted inputs. Prioritize updating analyst and build environments where outdated radare2 versions may still be present.
Technical view
The issue is a CWE-415 double free in radare2's cmd_info.c cmd_info() function. The CVE description says successful exploitation could modify unexpected memory locations and potentially cause a crash. The affected product is radare2, with the available source bundle identifying v4.4.0 as the fixed version.
Likely exposure
Exposure is limited to environments running radare2 versions before v4.4.0. This is most relevant for developer, reverse-engineering, malware-analysis, or CI systems where radare2 is installed. The sources do not identify broader dependent products or packaged distributions.
Exploitation context
The source bundle does not cite active exploitation, public weaponization, or CISA KEV listing. Impact is described as memory corruption and potential crash, with no confirmed remote exploitation path in the provided evidence.
Researcher notes
Evidence is sparse: no CVSS, no exploit status, and no detailed attack path are included. The strongest remediation anchor is the referenced upstream fix commit and the affected-version note stating the issue is fixed in v4.4.0.
Mitigation direction
- Upgrade radare2 to v4.4.0 or later.
- Check radare2 vendor issue and commit history for applicable downstream guidance.
- Reduce use of outdated radare2 builds on systems handling untrusted files.
- Track operating-system package updates if radare2 is installed through a distribution repository.
Validation and detection
- Inventory systems and containers for installed radare2 versions.
- Confirm radare2 reports version v4.4.0 or later.
- Review package manifests and CI images for bundled radare2 copies.
- Verify vulnerability records do not show the host running an older radare2 build.
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-415: 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-2020-27794 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/radareorg/radare2/issues/16303CVE reference · x_refsource_MISC
- https://github.com/radareorg/radare2/commit/cb8b683758edddae2d2f62e8e63a738c39f92683CVE 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.
Double Free
Double Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.