Critical Stack Buffer Overflow in Radare2: CVE-2024-523

radare2 Updated 28 Nov 2025

Summary

01/06/2024
HIGH
No i
High
Not published

OSV-2024-523: Stack-buffer-overflow in findstrings. Affected versions are not published. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Radare2 is an open-source software framework for reverse engineering and analyzing binaries. It provides a set of utilities to facilitate tasks such as disassembly, debugging, and binary patching. This powerful tool is widely used by security researchers and developers to understand and manipulate executable files. However, it is susceptible to a critical stack buffer overflow vulnerability that can lead to severe security issues.

Vulnerability Detail

The vulnerability identified as OSV-2024-523 is a stack-buffer-overflow that occurs in the 'findstrings' function of Radare2. This issue was reported through OSS-Fuzz, a service that finds vulnerabilities in open-source software. The crash type is categorized as a 'WRITE' operation that exceeds the allocated buffer size, potentially allowing an attacker to execute arbitrary code or crash the application. The implications of this vulnerability are significant, as it can compromise the integrity and availability of systems using Radare2.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, users can avoid using the 'findstrings' function until the patch is applied. Additionally, running Radare2 in a controlled environment or sandbox can help mitigate the risk of exploitation while waiting for the update.

Conclusion

The stack buffer overflow vulnerability in Radare2 poses a significant risk to users of the software. It is crucial to update to the latest version to mitigate potential threats. By understanding the nature of this vulnerability and following the recommended steps for resolution, users can enhance the security of their applications.

See every vulnerability recorded for radare2 →

Share this vulnerability

FAQ

A stack buffer overflow occurs when data written to a buffer exceeds its allocated size, potentially overwriting adjacent memory and leading to unpredictable behavior or security vulnerabilities.

You can use Vulert, which monitors open-source vulnerabilities in real-time. By simply uploading your manifest file, such as package-lock.json, you can check for vulnerabilities without needing to access the code.

The risks include potential arbitrary code execution, application crashes, and unauthorized access to sensitive data, which can compromise the security of systems using Radare2.

Yes, users should update to the latest version of Radare2 that includes the fix for the stack buffer overflow vulnerability identified as OSV-2024-523.

You can monitor the official Radare2 repository and subscribe to security mailing lists or use tools like Vulert to receive real-time alerts about vulnerabilities.

Related vulnerabilities

Recent vulnerabilities recorded for radare2.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback