Adding JNDI gadgets based on JDBC connection pooling classes. #16
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
These gadgets trigger an RCE by abusing the JDBC connection string to a vulnerable DB.
|
Hi Since the forceString in the org.apache.naming.factory.BeanFactory is replaced with a String setter lookup from Tomcat 9.0.63 / 8.5.79 onwards adding in a JDBC route as mentioned in the research of 浅蓝’s blogpost seems to be helpful with the newer Tomcat versions. Please note, my proficiency with of Java is quite limited and hence these additions may not have an optimal implementation / clean code, kindly let me know your input and I'll rework it as needed. Thank you Kind Regards |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These gadgets trigger an RCE by abusing the JDBC connection string to a vulnerable DB.