-
Notifications
You must be signed in to change notification settings - Fork 251
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Java: CodeQL query for unsafe RMI deserialization #358
Comments
Your submission is now in status SecLab review. For information, the evaluation workflow is the following: |
Your submission is now in status CodeQL review. For information, the evaluation workflow is the following: |
FYI I wrote a short blog post about the query. |
Your submission is now in status SecLab finalize. For information, the evaluation workflow is the following: |
Your submission is now in status Pay. For information, the evaluation workflow is the following: |
Created Hackerone report 1241579 for bounty 313175 : [358] Java: CodeQL query for unsafe RMI deserialization |
Your submission is now in status Closed. For information, the evaluation workflow is the following: |
Query
github/codeql#5818
CVE ID(s)
Report
RMI uses the default Java serialization mechanism (in other words, ObjectInputStream) to pass parameters in remote method invocations. If a remote method accepts complex parameters, then a remote attacker can send a malicious serialized object as one of the parameters. The malicious object gets deserialized without any check on the incoming data. In the worst case, it may let the attacker run arbitrary code remotely.
You can find more details about this attack in the following articles:
I'd like to propose a new experimental query that looks for deserialization vulnerabilities in remote objects registered in am RMI registry.
I am planning to write a blog post about detecting such issues.I wrote a short blog post about the query.
Result(s)
The text was updated successfully, but these errors were encountered: