Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2024-27758

Vulnerability in rpyc (CVE-2024-27758)

Summary

Vulnerability in rpyc (CVE-2024-27758). Confidential information can be exposed externally. Exploitable via __array__. Mitigation: upgrade to 6.0.0 or later.

Original description

The description as published by the source.

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.

Attack Vector

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

Impact

Assuming the system exposes a method that calls the attribute __array__, an attacker can execute code using the vulnerable component.

Patches

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.

Workarounds

While the recommend fix is to upgrade to RPyC 6.0.0, the workaround is to apply bba1d356 as patch.

Affected Component

The affected component is the __array__ method constructed for NetrefClass.

References

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2024-27758 has been found in rpyc.
Attackers can target a specific entry point like __array__ over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade rpyc to 6.0.0 or later.
If unsure, ask your IT team or search "rpyc CVE-2024-27758" on the vendor's site.

CVE-2024-27758 (rpyc) — CWE-306
Attack vector: remote (network-reachable) / no user interaction
Attack surface: __array__ / allow_pickle / True / NetrefClass
Patched: 6.0.0 — apply immediately
Workaround: While the recommend fix is to upgrade to RPyC 6.0.0, the workaround is to apply bba1d356 as patch.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-306) exists in rpyc. Attackers reach the vulnerable code path via __array__.

📍 Affected scope

Check the vendor advisory for the affected versions of rpyc. Attack surface: __array__ / allow_pickle / True / NetrefClass.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to 6.0.0.

🛡️ Workaround

Workaround: While the recommend fix is to upgrade to RPyC 6.0.0, the workaround is to apply bba1d356 as patch.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'rpyc' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'rpyc' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で rpyc を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    While the recommend fix is to upgrade to RPyC 6.0.0, the workaround is to [apply bba1d356 as patch.](https://github.com/tomerfiliba-org/rpyc/commit/bba1d3562e6f9f1256ec64048cc23001c0bb7516)

    パッチが適用されるまでの応急処置として、While the recommend fix is to upgrade to RPyC 6.0.0, the workaround is to apply bba1d356 as patch. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade rpyc to 6.0.0

    ステージング環境で 6.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

PyPI rpyc
[{"type":"ECOSYSTEM","events":[{"introduced":"4.0.0"},{"fixed":"6.0.0"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details