CyberRota Analysis
AI-GeneratedThe vulnerability affects the Apache DRPC server, which retains function name entries in a request queue indefinitely, leading to potential heap exhaustion as an attacker can send an unlimited number of distinct function names. This critical issue, with a CVSS score of 9.8, allows unauthorized clients to exploit the server without needing credentials, potentially resulting in service disruption. Organizations using Apache DRPC should prioritize upgrading to version 3.1.0 or implement strict access controls to mitigate the risk.
Original NVD Description
Description The DRPC server kept a map from function name to request queue and created an entry the first time a function name was seen. No code path ever removed an entry: request cleanup removed the request from its queue, and the shutdown path drained queues, but the queue object and its map entry remained for the life of the process. Function names come from the client and are not constrained to functions any topology has registered, so the number of retained entries is bounded only by the number of distinct names an attacker chooses to send, and each retained entry holds the name itself. `drpc.authorizer` is unset by default, so no credentials are required to reach the endpoint. The retained state is permanent rather than a transient load spike, so the effect accumulates until the DRPC server exhausts its heap. Mitigation Upgrade to 3.1.0, where a function's queue is removed once nothing is waiting in it. Users who cannot upgrade immediately should configure `drpc.authorizer` so that only trusted principals can reach the DRPC endpoints, and should ensure the DRPC ports are not reachable from untrusted networks. Credit The ASF -- found using Claude agents to study the security of open-source projects, validated and reported by Apache Storm.