Export ldapjndi global variables #460
Merged
Conversation
This file contains hidden or 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
So we can inspect/use them from another package (like an exploit). Ex: Printing GlobalSerializedPayload in generatePayload().
j-baines
approved these changes
Oct 14, 2025
terrorbyte
reviewed
Oct 14, 2025
|
|
||
| // a dirty way to pass the user's desired gadget to `handleBind`. | ||
| var globalSerializedPayload string | ||
| var GlobalSerializedPayload string |
Collaborator
There was a problem hiding this comment.
Do we want the exported names to be Global*? Maybe we should name them something payload oriented?
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.
So we can inspect/use them from another package (like an exploit). Ex: Printing
GlobalSerializedPayloadingeneratePayload().