radareorg radare2 6.2.0/6.2.2 HTTP Sandbox Policy libr/core/rtr_http.inc.c r_core_cmd_str_pipe protection mechanism

Summaryinfo

A vulnerability was found in radareorg radare2 6.2.0/6.2.2. It has been declared as problematic. Impacted is the function r_core_cmd_str_pipe in the library libr/core/rtr_http.inc.c of the component HTTP Sandbox Policy Handler. Executing a manipulation can lead to protection mechanism. This vulnerability is handled as CVE-2026-112077. The attack can be executed remotely. There is not any exploit available. It is recommended to upgrade the affected component. The pre-requisite of the vulnerability is reflected by the CVSS vector. One of the project maintainers explains: "There is a real sandbox configuration issue here, but the report overstates it. The HTTP server defaults to http.sandbox=true, so commands received through /cmd temporarily enable cfg.sandbox. However, cfg.sandbox.grain defaults to all, which means all sandbox capabilities - including exec - remain allowed. Therefore enabling the HTTP sandbox alone does NOT prevent commands from spawning processes. This only matters when the HTTP command endpoint is reachable by someone you do not trust. It is not a remote vulnerability by default: the HTTP server must first be started and exposed to the attacker."

Detailsinfo

A vulnerability was found in radareorg radare2 6.2.0/6.2.2. It has been declared as problematic. This vulnerability affects the function r_core_cmd_str_pipe in the library libr/core/rtr_http.inc.c of the component HTTP Sandbox Policy Handler. The manipulation with an unknown input leads to a protection mechanism vulnerability. The CWE definition for the vulnerability is CWE-693. The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product. As an impact it is known to affect confidentiality, integrity, and availability.

The advisory is shared for download at github.com. This vulnerability was named CVE-2026-112077. The exploitation appears to be difficult. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available.

One of the project maintainers explains: "There is a real sandbox configuration issue here, but the report overstates it. The HTTP server defaults to http.sandbox=true, so commands received through /cmd temporarily enable cfg.sandbox. However, cfg.sandbox.grain defaults to all, which means all sandbox capabilities - including exec - remain allowed. Therefore enabling the HTTP sandbox alone does NOT prevent commands from spawning processes. This only matters when the HTTP command endpoint is reachable by someone you do not trust. It is not a remote vulnerability by default: the HTTP server must first be started and exposed to the attacker." The pre-requisite of the vulnerability is reflected by the CVSS vector.

Upgrading to version 6.2.4 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 18fd12efa98a7d1977de7bdd379d8a848777b90f is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• Programming Tool Software

Vendor

• radareorg

Name

• radare2

Version

• 6.2.0
• 6.2.2

License

• open-source

Website

• Product: https://github.com/radareorg/radare2/

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Submitinfo

Accepted

• Submit #1009600: radareorg radare2 up to 6.2.2 OS Command Injection (by lijunjie)

Once again VulDB remains the best source for vulnerability data.

Discussion