CVE-2024-27758High· 8.5▾ TwilightRPyC's missing security check results in code execution when using numpy.array on the server-side.
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 46.8 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Jul 8.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
0.5%
An issue in Open Source: RPyC v.4.00 thru v.5.3.1 allows a remote attacker to execute arbitrary code via a crafted script to the __array__ attribute component. This vulnerability was introduced in 9f45f826.
RPyC services that rely on the __array__ attribute used by numpy are impacted. When the server-side exposes a method that calls the attribute named __array__ for a a client provided netref (e.g., np.array(client_netref)), a remote attacker can craft a class which results in remote code execution
Assuming the system exposes a method that calls the attribute __array__, an attacker can execute code using the vulnerable component.
The fix is available in RPyC 6.0.0. The major version change is because some users may need to set allow_pickle to True when migrating to RPyC 6.
While the recommend fix is to upgrade to RPyC 6.0.0, the workaround is to apply bba1d356 as patch.
The affected component is the __array__ method constructed for NetrefClass.
rpyc >= 4.0.0, < 6.0.0Upgrade to a patched release:
rpyc 6.0.0