Refactor EPM Functionality #286
Merged
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.
This refactors the endpoint mapping (EPM) functionality defined in MS-RPCE to be more encapsulated, and thus reusable in isolation. An existing DCERPC client will now create a private DCERPC client instance specifically for the EPM service calls needed to map a service to a port for connection. This enables developers to also create their own DCERPC clients specifically for interacting with the EPM service, enabling them to control the exact parameters to the
ept_mapfunction when resolving services.This also includes an example script to demonstrate the functionality for the two protocols that are currently supported.
Demo
In this case, the target system (
192.168.159.10) is a Windows Server 2019 Domain Controller. The example script is used to resolve the GKDI and SAMR endpoints.