A security researcher has explained how Java RMI services remain at risk of developing SSRF vulnerabilities. These vulnerabilities work under specific conditions, which, if met, can allow SSRF attacks. Securing backend services can effectively help alleviate the chances for such vulnerabilities.
SSRF Vulnerabilities Risk Java RMI Services
Elaborating the details in a blog post, the researcher Tobias Neitzel has highlighted how Java RMI services remain exposed to SSRF attacks. These attacks become possible due to SSRF vulnerabilities that may develop under specific conditions.
Describing Java RMI, the researcher stated,
Java RMI is an object-oriented RPC (Remote Procedure Call) mechanism that is available by default in most Java installations. Developers can use Java RMI to create remote objects that expose their functions on the network and allow remote clients to call them. Java RMI communication relies on serialized Java objects, which makes the protocol a prime target for attackers.
Briefly, the researcher observed how SSRF attacks become possible on these services. Although, the object-oriented RPC implementation ensures secure communication between the local and remote objects, hence exhibiting resilience to SSRF. However, the threat appears due to unsecured configurations that administrators often employ on RMI.
Thus, SSRF bugs threaten the RMI service’s security under the following conditions.
1. The SSRF vulnerability needs to allow arbitrary bytes being sent to the backend service (enables attacks on default RMI components like the RMI registry, the DGC or the Activation system).
2. The SSRF vulnerability needs to return responses from the backend service and accept arbitrary bytes within them (enables attacks on all RMI endpoints including JMX and custom remote objects)
When these conditions are met, an adversary can exploit SSRF to consume the backend service just as a direct connection.
Neitzel has shared the technical details of such attacks step-by-step in his post.
According to the researcher, the following steps may help secure RMI services to prevent vulnerabilities.
- Using the up-to-date Java version to avoid inherent vulnerabilities in older versions.
- Enabling TLS protection on RMI communications as the underlying protocol communicates data in plain text.
- Implementing user authentication.
- Using deserialization filters while ensuring that no apps or third-party libraries perform “dangerous actions during deserialization.”
Let us know your thoughts in the comments.