LiveActive security incident?Get immediate response
CVE Record

CVE-2018-11379: The get_debug_info() function in radare2 2.5.0 allows remote attackers to cause a denial of service (heap-b...

The get_debug_info() function in radare2 2.5.0 allows remote attackers to cause a denial of service (heap-based out-of-bounds read and application crash) via a crafted PE file.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-11379 is a crash bug in radare2 2.5.0. A specially crafted Windows PE file can make the tool read outside heap bounds and crash while extracting debug information. The evidence points to denial of service, not code execution or data theft.

Executive priority

Handle as a targeted operational resilience issue. Prioritize environments where radare2 processes untrusted files automatically, because crashes can disrupt analysis pipelines. It is lower urgency than remotely exploitable code execution based on the supplied evidence.

Technical view

The CVE describes a heap-based out-of-bounds read in radare2 2.5.0 get_debug_info(). Triggering requires radare2 to parse a crafted PE file. Public references include a GitHub issue and a fixing commit, but the bundle does not provide CVSS, CWE, or a complete affected-version matrix.

Likely exposure

Exposure is most likely in reverse-engineering, malware-analysis, CI, or triage workflows that use radare2 2.5.0 on untrusted PE files. General enterprise exposure is limited unless radare2 is embedded in automated file-processing services.

Exploitation context

The source bundle does not show active exploitation, and KEV status is false. Public evidence supports a crafted-file denial-of-service condition. Treat externally supplied PE files as the practical risk path, especially where radare2 runs unattended.

Researcher notes

The CVE evidence is sparse: no CVSS, CWE, or full affected list is provided. The named vulnerable version is radare2 2.5.0, with references to issue 9926 and commit 4e1cf0d. Do not infer broader version impact without vendor confirmation.

Mitigation direction

  • Identify systems and pipelines running radare2 2.5.0.
  • Review the radare2 issue and fixing commit for vendor remediation guidance.
  • Upgrade to a radare2 release that includes the fix, where available.
  • Avoid processing untrusted PE files with vulnerable radare2 until remediated.
  • Run binary analysis tooling in isolated, resource-limited environments.

Validation and detection

  • Check radare2 versions on analyst workstations and automation hosts.
  • Inventory services that parse uploaded or externally sourced PE files with radare2.
  • Confirm remediation against the referenced radare2 fixing commit or vendor release notes.
  • Verify crash handling and job isolation in automated analysis pipelines.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CVE-2018-11379 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.