Security readout for executives and security teams
Plain-English summary
radare2 through 4.0.0 can mishandle crafted input and write where it should not. The documented result is an application crash, with unspecified other impact possible. This mainly matters where radare2 processes untrusted files or input in analyst workstations, automation, or exposed analysis services.
Executive priority
Treat as a targeted remediation item for security tooling and analysis environments, not as a confirmed widespread emergency. Prioritize any system that accepts external samples or automates radare2 processing.
Technical view
The flaw is in r_asm_pseudo_incbin in libr/asm/asm.c, where the content variable is not validated before use. The CVE describes an arbitrary write reachable through crafted input, causing denial of service or possibly other unspecified impact. No CVSS, CWE, or precise fixed version is provided in the bundle.
Likely exposure
Exposure is most likely on systems running radare2 through 4.0.0, especially where it parses untrusted binaries, scripts, or uploaded artifacts. The source bundle does not provide CPEs or a complete affected product matrix.
Exploitation context
The bundle does not cite CISA KEV listing or active exploitation. Public disclosure exists via a radare2 GitHub issue and Fedora package advisories, but exploit status and real-world abuse are not established by the provided sources.
Researcher notes
The provided data is thin: no CVSS vector, CWE, CPE list, patch commit, or exploit evidence is included. Analysis should stay anchored to radare2 through 4.0.0 and the described arbitrary write in r_asm_pseudo_incbin.
Mitigation direction
- Inventory radare2 installations and flag versions through 4.0.0.
- Update radare2 using vendor or distribution package guidance.
- Avoid feeding untrusted input to vulnerable radare2 versions.
- Run analysis tooling with least privilege and process isolation.
- Check Fedora advisories if using Fedora-packaged radare2.
Validation and detection
- Confirm installed radare2 versions across workstations, servers, and analysis pipelines.
- Review package manager history for radare2 updates after the Fedora advisories.
- Identify workflows where radare2 processes user-supplied or external files.
- Verify exposed services do not invoke vulnerable radare2 on uploads.
- Document compensating controls if immediate upgrade is not possible.
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-2019-19647 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/15545CVE reference · x_refsource_MISC
- FEDORA-2020-4a3ff78ba5CVE reference · vendor-advisory, x_refsource_FEDORA
- FEDORA-2020-acd8cdb08dCVE reference · vendor-advisory, x_refsource_FEDORA
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.